@GreenGrouch Try to move the line "p_inP14 = Pin ..." before the while instruction

I actually gave up on the FiPy for not getting this sorted out. The problem is not in the use of a GPIO to wake the board. The problem is in entering or exiting the deepsleep mode. Now reading some more in the forum I found one reference to sometinh that might be related to the issue that I experienced: @crumble said in Deep Sleep Not Waking Up: @jcaron said in Deep Sleep Not Waking Up: Also, remember that machine.deepsleep never returns. Depends :) If it behaves like the pytrack, it may never go to sleep and never increase the program counter. I assume a catched i2c issue in combination with the pytrack. If the OP has a USB volt meter, he can simply verify this. If it still draws a lot of power, it does not sleep and can therefore never wake up. The software watchdog is able to get it out of this state. On my system it is not easy to reproduce. It may need a few hundred deepsleeps before this error occurs.

Found a start of an answer here: https://forum.pycom.io/topic/3624/machine-pin_deepsleep_wakeup-function-is-not-working-in-lopy4-firmware-version-1-19-0-b2 Link to developemtn documentation on github: https://github.com/pycom/pycom-documentation/tree/development_release/firmwareapi/pycom/machine The method is renamed to pin_sleep_wakeup()

I have the same problem with some of my GPY. You are powering the GPY with 5V? Cumps,

@tschili Imho, if you trigger the wake-up just when the transmission starts, you'll have the issue that the GPY needs to little bit of time to wake-up and initialise, and you will most certainly lose and data received during that time. So you would need the SIM800L to wait until the GPY is ready to receive before it start sending the data, and some other way to wake up the GPY.

hi @sprasad, So you're interfacing orientation sensor directly with GPY, right? You could control RST pin of GPY, or control Vin(3.5V-5.5V) from your powering scheme.

@chrisi if you are using the Deep Sleep shield, then you have the relevant functions in the library that goes with it. If you are using a Pysense (and I believe the same applies to the Pytrack), then it's a lot more complex. There's only one usable pin on the I/O header, you need to patch the Pysense firmware, isolate a pin between the module and the Pysense, and change a few things in the sleep process. But it does work. Refer to https://forum.pycom.io/topic/1673/pysense-pinout-wake-on-pin/16 for details.

@amartinez said in Wake up LoPy in sleep mode with another LoPy??: What will be initiator of that action? Communication by Lora? In sleep it is not available. Only some PIN wake up - but how do you suppose some PIN go e.g. High - what can init this action?