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

[constantinos]

@Fred Very Nice! Can you provide us also a schematic of the solution in order to fix our custom boards?

Thanks in advance
Constantinos

[daniel]

@jasonriedy what you need to do is to plugin the LiPo and attach the deep sleep shield that we just announced. The LiPo battery on the expansion board powers the module via the VIN (3.6-5.5V) pin, not via the 3V3 pin. Deep sleep with the shield will work on a transparent way when you issue the machine.deep_sleep() instruction.

[daniel]

@ssmith @constantinos we will make the schematics available later today.

[Fred]

@constantinos Hi, I can confirm that we will be releasing the schematic later today. Thanks Fred

[daniel]

Hello,

The schematics for the deep sleep shield are now available here: https://docs.pycom.io/pycom_esp32/_downloads/Deep-Sleep-Shield_Schematic.pdf

Cheers,
Daniel

[robert-hh]

@daniel Thank you very much. Will you also publish the code for the PIC controller?

[daniel]

@robert-hh yes, it will be open source too.

[frankb]

What are the dimensions of the 'deep sleep shield'? Will it still fit in a standard housing together with the v1.0 expansion board?

[daniel]

@frankb it's going to be around 12mm tall. It's not going to fit inside the Pycase, but it most likely will fit inside the IP67 case. We will confirm this shortly.

[Kean]

@daniel any timeline for release of the PIC source? I should have all the parts to build one of these on protoboard so I can continue with a project evaluation, except the code. Even a beta code in a hex file I can program via a PICkit3/ICD3.

[daniel]

@Kean I don't have precise timelines yet, we are still busy with the PIC code and we are not ready to share it yet. I should be able to share some more info next week.

[Kean]

@daniel Thanks!

[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!