ESP8266 Community Forum

- Sun Jun 28, 2015 3:47 am #21889 So we have managed to put it to sleep with :

"node.dsleep(0, 2)"

the reset and GPIO16 are connected to pins in the MCU which are on HIGH .

In order to wake it i am taking these pins on the MCU to LOW , for 100-500ms . its not working .

How long should be the falling edge to wake it up -and connect to the internet again ?
What mode should i put the module so on waking it will connect to router as fast as possible ?

thanks .

- Tue Jun 30, 2015 12:02 pm #22067 I do not use node 16 but I assume the underlying stack does the same functionality.
GPIO16 is an output I think, it drives the reset low to wake up the device. so you probably do not need it.
i have looked at the pulse from gpio16 at wake time and it is very short, a few uS only from memory.
but .. I think there is both software and hardware doing things at wake time, if you do not have gpio16 connected to rst then there is still output from the serial port when the timer expires.
perhaps if the timer is not expiring then the device goes straight back to sleep ? not sure.
what if you disconnect gpio16 and only use a short sleep then pulse the reset line as required ?

pretty sure RF_CAL will be slower than RF_DEFAULT. I use default and if problems connecting then sleep with rf_cal next time.

- Tue Jun 30, 2015 1:37 pm #22074 Why do you want to use deepsleep, when you have an external uC connected? It would be much simpler to connect CH_PD to an I/O pin on your uC and directly control the ESPs state.