Left here for archival purposes.

User avatar
By Markus Gritsch
#15624 Hi,

if I run

Code: Select allwifi.sleeptype(wifi.MODEM_SLEEP)
node.dsleep(1000000, 4)

my ESP-12 module goes to sleep for one second and after waking up, it comsumes only 13.2 mA with the modem turned off (compared to about 70 mA with the modem turned on).

It also stays in this 13.2 mA consumption mode, when I reset the module via the reset pin.

Now the strange part: After happily working in this mode for exactly 20 minutes (1200 seconds), the current rises to 15.3 mA for 3 seconds and then the WDT kicks in and resets the module. After this reset caused by the WDT, the current consumption is about 70 mA.

The phenomenon is reproducible every time.

Here is the output log after the 20 minutes:

Code: Select all ets Jan  8 2013,rst cause:4, boot mode:(3,7)

wdt reset
load 0x40100000, len 31916, room 16
tail 12
chksum 0xea
ho 0 tail 12 room 4
load 0x3ffe8000, len 2888, room 12
tail 12
chksum 0x8d
ho 0 tail 12 room 4
load 0x3ffe8b50, len 15452, room 12
tail 0
chksum 0x22
csum 0x22
User avatar
By cal
#15813 Moin,

in what mode is the module when consuming 70mA?
Did it startup nodemcu?
Do you have any useful messages at 115200 baud?
Do you have any "Fatal exception" messages?

Maybe some kind of wifi refresh kicks after 20m.
Maybe it should not because modem sleeps but let assume the unlikely presence of bugs.
The firmware runs on an error (I would expect a fatal exception error now but maybe it gets just stuck)
and maybe damages wifi config.
The watchdog bites.
Wifi config is damaged and uses some power.

Does someone know HOW the watchdog bites? Does it cause some interrupt or reset or ???
I managed to intercept exceptions and print registers, stack and memory when they happen.
I would like to have similiar information in case of watchdog events.

Cal
User avatar
By Markus Gritsch
#15818
cal wrote:in what mode is the module when consuming 70mA?
Did it startup nodemcu?
Do you have any useful messages at 115200 baud?

The terminal is set to 115200 baud and the message it prints when the WDT bites is at the end of my previous post. Nothing else, no "Fatal exception".
User avatar
By cal
#15820
Markus Gritsch wrote:
cal wrote:in what mode is the module when consuming 70mA?
Did it startup nodemcu?
Do you have any useful messages at 115200 baud?

The terminal is set to 115200 baud and the message it prints when the WDT bites is at the end of my previous post. Nothing else, no "Fatal exception".


Is the ESP 12 different to ESP 01 when printing the boot message?
My ESP 01 print the boot message at 74880 baud, then switch to 115200 (normally no output if boots ok, RTC MEM CHECK errors sometimes or FATAL EXCEPTION on dsleep wakeup (see other thread))
and then switch to the baud rate defined in the nodemcu startup code, typically 9600 baud.

I didn't managed to play with my ESP 12 yet.

Cal