hello, for those who have used this module before, is it reliable in long term use for 2 way communication using esp now ? i mean if it resets sometimes after a while suddenly
also what pins i would be able to use to control 3 relays and a button, because i've seen that some are unusable, some may cause falut at boot up if pulled low or high and some are booting high causing a short inmpulse on the relay
The most likely reason for unexpected reset is the circuitry around it, the wiring, the connections, denoised or not solenoids....
RF interference power supply and contactors can cause ?
why nrf for example doesn't reset
Can't speak to ESP-NOW, but I have an ESP8266 pushing data to Thingspeak that has been running for a year or so. It reset once, but that was due to an area-wide power failure.
1 Like
that's great then, any advice on the code? i am not that experienced also it is my first time using this module..
maybe someone could analyze my code after it is done
Can't compare apples with oranges.
The ESP8266 (NodeMCU) has a radio and a processor with running code.
An NRF24 is just a radio, no MCU.
My ESP modules are running without problems 24/7.
It all has to do with a clean supply, proper code and non-interfering peripherals.
Leo..
1 Like
what supply do u recommend, for the tx module can i use a phone battery pack of 10Ah ?
I have used a WeMos D1 mini on a powerbank before, and it worked fine for the 6 months I did.
But I guess it's depending on the make of the powerbank. Most/all of them have a shut-off circuit. The 5Ah I used stayed on with the ~100mA that the ESP draws.
Leo..
The answer to your question is to find the MTBF or failure rate figures for the chip. However, I've searched google and can't find any data for the ESP8266. It has probably never been measured.
As a rough guide, you might assume an MTBF of 500,000 hours (this ball-park figure is reasonable for ICs of comparable complexity). Thus there is a 1-in-500,000 chance of it failing in any one hour, or a 1-in-570 chance of it failing in any one year.
1 Like
I have had a pair of Nodemcu's for r/c'ing my garage door going on 2 years without failure.
1 Like
that means they still work and didn't defect or that they never reseted
The reports of unexpected resets I see here usually have one of two causes:
Watchdog
The board will reset if the sketch code blocks the watchdog timer handling. Information here:
https://arduino-esp8266.readthedocs.io/en/3.0.2/faq/a02-my-esp-crashes.html#watchdog
Power supply
The ESP8266 intermittently draws significant current while doing Wi-Fi communication. This can result in confusing problems if the power supply is inadequate because the board seems to be working well when running basic sketches, and probably even some successful Wi-Fi communication may be working, but then every once in a while it resets or just fails to communicate.
This is more often a problem for the people who are trying to power a module from the voltage regulator on another Arduino board. I think the built in power supply on your board is sufficient for when it is powered over USB, but it could be a problem for a project which is finally powered in another way.
Is your shift-key broken?
Schematic! Without a schematic of your project, NO ONE can help you make power decisions.
The size of the board has nothing to do with the power requirements. The NodeMCU and the Wemos D1 Mini both use the ESP8266 processor.
Reliable? The majority of Sonoff products use the ESP8266 or ESP8265 (same chip, less RAM). We're probably talking about millions of units around the world.
i have disabled wtd and i feed it in the loop every time , should i add capacitors for the psu problem ?
No, that NodeMCU board draws only a fraction more than the bare ESP8266 module (metal enclosure) mounted on it. 100mA average (with very short ~400mA peaks during transmit).
Leo..
1 Like
i meant the standalone board it draws more.
And not the reliability of chip itself but the module put together with all of it's parts and functions
Unless you start using proper sentence structure, I will not be assisting you further.
What is WTD? Do you mean WDT? You should not need to disable WDT in the ESP processor because the normal loop() housekeeping feeds the WDT itself anyway. You don't have to do anything but write your sketch without blocking code.
PSU: How do you know that you have a power problem?
but i have tested and disabled watchdog with ESP.wdtDisable(); commands and run the code without any feed in the loop, i've got many random resets but if i add the feed command ESP.wdtFeed(); at the beginning of the loop i won't get resets anymore
void loop() {
ESP.wdtFeed();
}
blocking code means one that take much time to execute or have to many delays ? may i call feed in betwen delays where i need them