Deep sleep and wake up using interrupt

[shayo]

Hi,

I saw the option to enter deep sleep for a predefined amount of time ( ESP.deepSleep)
Is it possible to wake up during that time with an external interrupt?
If so, how?

Thanks,

Shay

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[chaeplin]

check esp api in https://github.com/esp8266/Arduino/blob/master/doc/libraries.md#esp-specific-apis

ESP.deepSleep(microseconds, mode) will put the chip into deep sleep. mode is one of 
WAKE_RF_DEFAULT, WAKE_RFCAL, WAKE_NO_RFCAL, WAKE_RF_DISABLED.

 (GPIO16 needs to be tied to RST to wake from deepSleep.)

[shayo]

That doesn't really answer my question. I understand that if order to wake up from a deep sleep timer, GPIO16 needs to be wired to RST, but is it possible to wake up before that, using an external event on some GPIO line?

[chaeplin]

@shayo
No, you can't use an external event on some GPIO line.
In deepSleep state, only rtc is on(cpu and system clock is off).
GPIO16 generate a short pule to reset esp.
So any reset pulse will wake up esp.

With ESP.deepSleep(0), esp will be going to sleep forever.

[duncan-a]

But, if GPIO16 triggers the 'wake from deep sleep' by firing a Reset, why can't a Low pulse on RST achieve the same result?

Am I missing something?

CHAE-PIL LIM notifications@github.com wrote:

@shayo
No, you can't use an external event on some GPIO line.

—
Reply to this email directly or view it on GitHub.

[Links2004]

GPIO16 is connected to CH_DP for deepSleep.
and pulled low during deepSleep.
if CH_DP goes high the chip wakes up.
for what reason the high signal comes from does not mater.
can be the RTC timer or any other electrical stuff connected to CH_DP.
so adding a pullup to CH_DP and a switch that is normally close to GPIO16 will work fine.

[chaeplin]

@duncan-a External interrupt to rst is ok. But @shayo's question is "using an external event on some GPIO line".

@Links2004 GPIO16 is in HIGH during deepSleep.

I will use CH_DP when I use esp-01.

GPIO16 to RST has one advantage when wake up---> wifi connect with static ip : 150 ~ 210msec

reset switch for deepsleep.

edited)
flip-flop version --> monostable flip flop

[me-no-dev]

As an option, you can have the ESP in deep sleep waiting for the RTC to trigger pin 16 for wakeup and use the reset button at the same time as manual reset. Reading the reset cause can tell you which event woke up the ESP :) then you can programmatically split and act different on both.

[Humancell]

@chaeplin ... thanks for the schematic and comments.

I'm curious ... when you say "flip flop" does this mean it fires the reset on both opening AND closing the switch?

[chaeplin]

@Humancell It's monostable flip flop. check here -> http://www.bowdenshobbycircuits.info/page9.htm
http://www.bowdenshobbycircuits.info/mono.gif
http://chaeplin.github.io/project-01-button.html

[Humancell]

Thank you ... I saw that you had posted about your solution here also: https://github.com/chaeplin/esp8266_and_arduino/tree/master/_48-door-alarm-deepsleep

I"m working on a similar idea, and am curious ... with your door sensor, it appears that you have the deep sleep timer still working, but then you can be triggered by the reed switch opening ... or closing?

And with the added circuitry (did you use the monostable flip-flop with your reed switch door sensor?) what is the final deep sleep current that you are seeing? Do any of these components add to the current draw during deep sleep?

[chaeplin]

@Humancell Trigged when opening, cause the type of reed switch is normally opened(Q3 is added to invert signal).

With C2, R4 and R9, a low signal is converted to reset pulse(Arduino reset method), so no more monostable flip-flop is needed.

My µCurrent GOLD shows 0A while in deepsleep.

[Humancell]

Ok ... this makes sense. So the reed you are using is open, and then closes with the magnet nearby?

If I need to do the reset on the reed switch both opening AND closing? I want to create an event when the door opens ... AND when it closes ... which obviously adds complexity. Is this where the flip-flop comes into play?

Sorry for being slow on this ...

[chaeplin]

@Humancell _48-door-alarm-deepsleep is doing what you want.
I can't make a reset signal when door is closing, So I use modem sleep and light sleep while door is opened.

I think attiny85 with pin change interrupt is more easier than R/C/TR circuit.
attiny85 : gpio 1) reed sw. gpio 2) to esp reset. gpio 3) to esp gpio
esp : deepsleep.

https://github.com/chaeplin/esp8266_and_arduino/tree/master/_28-attiny85-nrf24-3pin-ir
http://www.gammon.com.au/interrupts

sch : attiny85 + esp01
http://imgur.com/MooQJV9

[Humancell]

Thank you for the wealth of links and information. This is exactly what I was looking for. Now I can dedicate an ATtiny85 to be a strictly "interrupt-woken" peripheral that will produce the low-pulse required to wake the ESP-12F. I can then also use the ESP-12F deep sleep timer to wake at regular intervals to produce "heartbeats" from the sensor when the door is open or closed for extended periods.

With your suggestion on pins above, would I be passing the ESP deep sleep sugnal on pin 16 through the ATtiny85 also? Is that what your pin #3 is above? So teh ATtiny85 would wake on either the reed switch to ESP GPIO wake signal?

[chaeplin]

@Humancell I use esp-01 for the circuit. Pin no 3 is used to present state of door to esp GPIO 1(Attiny85 control debounce). As you use ESP-12F, GPIO16 can be used to signal ATtiny85 as your suggestion.