Does deepsleep work at all

[chumelnicu]

@chumelnicu Hi Daniel, sorry for late update but i was in holliday until yesterday.

I did try deepsleep with new DeepSleep library and llopy behive same. After 14-15 DS cycles program stop running.

I use lopy with DS Shield powered from USB and nothing on Pin12.
Condition to wake up, is time, w-up after 10 minutes.
Do u have any ideea what is wrong?

Thx !

[tmz]

@daniel The result is the same. Stops after (5 - 20) cycles. How do i run in more verbose way? There is no error, it's jumps into REPL.

[chumelnicu]

@daniel Could you tell me how and when DeepSleep will work ? Im not only one who claim about this problem and I think is really time to clarify with your team what is happening

Thank you !

[Robin]

@adam_IoTK

I have the same problem with a LoPy + Deep sleep shield.
My code runs for 20-40 times and then stops. Issue reported here: https://forum.pycom.io/topic/1685/lopy-with-deep-sleep-shield-is-unstable

This is a blocker for any real world deployment.
Not having seen any useful response from the Pycom team on the forum about this issue i am considering moving to another platform to get my project finished.

[daniel]

Hello,

The instability has been fixed here: https://github.com/pycom/pycom-libraries/commit/ea3e22c14884671801bcd1cfe49c703bc63c7078

We are now working on reducing the deep sleep current.

Cheers,
Daniel

[tmz]

@daniel
Thank you! The issues seems to be fixed after this fix.
Is > 8h without interruption.

LoPy v1.7.9.b3
Expansion board (with deep sleep shield)
Fix: https://github.com/pycom/pycom-libraries/commit/ea3e22c14884671801bcd1cfe49c703bc63c7078

[Robin]

@daniel Seems to work for me too now.
Adding the garbage collector statements in the calling code seems to be crucial through.

[johncaipa]

@daniel I'm testing the deepsleep example but I get the following errors:

Traceback (most recent call last):
File "main.py", line 7, in <module>
File "/flash/lib/deepsleep.py", line 143, in get_wake_status
File "/flash/lib/deepsleep.py", line 76, in peek
IndexError: bytes index out of range

I am doing something wrong?
thanks

[tmz]

@johncaipa

Try the latest - https://github.com/pycom/pycom-libraries/blob/master/deepsleep/deepsleep.py

[johncaipa]

@tmz that is the library I'm using, and which errors are generated

[Arnaud]

@tmz said in Does deepsleep work at all:

https://github.com/pycom/pycom-libraries/blob/master/deepsleep/deepsleep.py

Just tried the deepsleep example on Sipy 1.0 - Pytrack 1.0 with latest deepsleep.py and after firmware upgrade to 1.7.9b3 and got the same error than John.

I understood that Pytrack serves as deepsleep shield.
All this deepsleep troubles merged with lack of documentation is really frustrating...

[daniel]

@Arnaud with pytrack or pysense simply use their own libraries which also provide the deepsleep functionality:

https://github.com/pycom/pycom-libraries/tree/master/pytrack

[Arnaud]

Nice to hear that! Please help us with a bit more explicit documentation. You might be aware of this now based on the comments, you're building up hours of frustration which is not was intended at first I'm sure with the beautiful specs of your products.

BTW, I think deepsleep example lacks an import deepsleep for constants.

[Arnaud]

@daniel I've tried the latest pytrack lib for deepsleep with very simple main.py:
from pytrack import Pytrack

print( "Waking up")

Some job

print( "Going to sleep")

pytrack = Pytrack()
pytrack.setup_sleep( 10 )
pytrack.go_to_sleep()

Waking up with a buton press works.
Board never wakes up on timer.

[jcaron]

Just to make sure, you have the latest firmware (0.0.4 I believe) on the Pytrack? You can check with pytrack.read_fw_version().

[Arnaud]

@jcaron read_fw_version returns 2.
Since I haven't done any pytrack firmware upgrades since June, I'll assume I have to.

This might be a hint for improving docs:
Required Pytrack Firmware: x.y.z

[Arnaud]

@jcaron
I have updated the pytrack firmware to 0.0.4 with DFU-util (Mac OSX).

From there:
The hearbeat (blue led) is not active anymore.
I have a lot of troubles gettting a console connection to the board.
Sometimes, the board executes main.py, prints a few lines but hangs on while printing firmware version and connection is lost.

[jmarcelino]

@Arnaud
Can you try another USB cable?

[daniel]

@Arnaud, I think the firmware upgrade failed. Just tried it again using the DFU procedure.

Cheers,
Daniel

[Arnaud]

@daniel Got this during Pytrack firmware upgrade:
Match vendor ID from file: 04d8
Match product ID from file: f014
Deducing device DFU version from functional descriptor length
Opening DFU capable USB device...
ID 04d8:f014
Run-time device DFU version 0100
Claiming USB DFU Runtime Interface...
Determining device status: state = dfuIDLE, status = 0
dfu-util: WARNING: Runtime device already in DFU state ?!?
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 0100
Device returned transfer size 64
Copying data from PC to DFU device
Download [=========================] 100% 16384 bytes
Download done.
state(2) = dfuIDLE, status(0) = No error condition is present
Done!