Root causes of high deep sleep current [LoPy1, WiPy2 and SiPy], all the new modules **do not have deepsleep issues**

[Fred]

Dear All,

A quick update on this topic to confirm we are currently testing the Pilot Run samples in Eindhoven. All going well and we expect to have shields to ship circa 2 to 3 weeks e.g. 5/6 June. Photo enclosed of first unit.

Best wishes Fred

[irvinvp]

Hi @Fred, There are any updates about the shields? Thanks

[danielm]

When can we expect that the shields will be shipped to us?

[_peter]

Firmware and board will be available in early June?

[jomifo]

@Fred Considering getting a pysense and pysense case. Will this setup work with my Lopy+deep sleep shield?

[bucknall]

Hi @jomifo,

If you use a Pysense or Pytrack, you do not need to use the deep sleep shield as the Pysense/track already have this feature built in!

[_peter]

Unfortunately, the solution to an alternative expansion board is not good for me. I'll have to mount it on an ad hoc card. Question: The OEM Reference Board (https://www.pycom.io/product/oem-reference-board/) + L01 OEM Module (https://www.pycom.io/product/l01/) can solve the problem ? I saw this: https://www.pycom.io/l01-oem-module-deep-sleep-test/. The OEM reference board has the same Lopy pinout?

[bucknall]

@_peter The only modules affected by the deep sleep issue is the Development versions of the WiPy 2.0, LoPy and SiPy. All of the OEM modules are not affected by this issue as they do not use the same power regulation as found on the affected modules. This includes the OEM Reference Board.

Thanks!

[_peter]

@bucknall Thank you, I apologize but I do not find any documentation on the OEM Reference Board. Do you know where to find it?

[bucknall]

@_peter We currently have the OEM baseboard reference design available here - https://docs.pycom.io/pycom_esp32/pycom_esp32/datasheets.html#oem-baseboard-reference-design

[danielm]

@bucknall
When are you planning to ship deep sleep shields to your customers?

[daniel]

@_peter the OEM reference board does have the same LoPy pin out, with the only difference that P12 is also used there to drive the RF switch (you can see that on the schematics).

[bucknall]

@danielm The Deep Sleep Shields should be arriving in the 3rd week of June. We will ship them as soon as we receive them. Thanks for your patience!

[_peter]

@danielm I have to deliver a LoRaWan sensor node within about 15 days giving me the chance to deep-sleep for 10 minutes and that when it wake up do not join again. is possible ?

[irvinvp]

@bucknall Thank you, we are waiting for the shields.

[bucknall]

@_peter If you're using a LoPy (Development Kit), you can currently get deep sleep with a Pytrack or Pysense - without these you'll need to wait until the Deep Sleep Sheild arrives

[_peter]

@bucknall I designed the board for Lopy and thought of replacing it with the oem expansion board + oem module. According to you is it possible?

[bucknall]

@_peter Yes, this is possible. The footprint of the board is slightly wider than the LoPy but the functionality and pinout is identical to that of the LoPy. This is can be used as an exact replacement for the LoPy!

[RobTuDelft]

Is the script for the PIC also somewhere available?

[mcook]

@Fred

Hi,

I received my PyTrack boards today. I have attached my LoPy to one of them. I am powering the PyTrack via USB. The USB is plugged into a USB multimeter. With the WiFi on, I see it is drawing about 125 mA at 5 VDC. After entering deep sleep, I see the current is reduced to ~48 mA. Is there some configuration that needs to be done in the code in order for the PyTrack boards to work properly with Deep Sleep?

Mike