Welcome to the Pycom forum Forum
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • Login

    Explore Pybytes | Official Documentation | Report a Firmware Bug/Issue | GitHub

    LoPy deep sleep mode ?

    Scheduled Pinned Locked Moved LoPy
    38 Posts 17 Posters 21.1k Views 21 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P Offline
      pform @Fred
      last edited by

      @Fred I have been looking across at the ESP32 forum and found this. Is this not what we/you are looking for?

      1 Reply Last reply Reply Quote 0
      • D Offline
        daniel
        last edited by

        @pform that's some of what we need, but last time we tested it, it was not working properly after enabling Bluetooth and WiFi (current was dropping but only to like 20mA). So, that's why we are waiting for the fix to switch off the radios promised by Espressif. Also, deep sleep does not have memory retention, which means that the application resumes from reset point.

        Other than that we also need/want the light sleep modes which are a lot more flexible.

        1 Reply Last reply Reply Quote 0
        • B Offline
          blsmith
          last edited by blsmith

          I am reading ~10 mA draw when LoPy is in deepsleep. This seems high to me...

          Has anyone else got a measurement for a reality check?

          I am measuring while running on pure battery, in series with a battery lead. LiPo, currently charged and providing 3.96VDC.

          I am also assuming (hard to really tell from this thread) that deepsleep is currently functional. If we are still waiting on a firmware update then please ignore.

          1 Reply Last reply Reply Quote 0
          • J Offline
            juriw @Fred
            last edited by

            @Fred We are also having issues with this in my team regarding deepsleep on Sipy running at 17mah. This is not good. Looking forward to an update.

            F 1 Reply Last reply Reply Quote 0
            • F Offline
              Fred administrators @juriw
              last edited by

              @juriw Hi, I have asked Daniel to check latest and come back with some input. Thanks! Fred

              1 Reply Last reply Reply Quote 0
              • D Offline
                daniel
                last edited by

                @juriw @blsmith deepsleep current should be in the range of uA. Do you have anything else connected to the board or the GPIO pins? is the RGB LED off? Is the module mounted on the expansion board or on a custom PCB?

                Cheers,
                Daniel

                J 1 Reply Last reply Reply Quote 0
                • B Offline
                  blsmith
                  last edited by

                  Just went back and doublechecked.

                  Nothing connected to LoPy.

                  RBGLED and board led are both off.

                  It is installed on the "official" expansion board.

                  Getting 10.1 mA passing through battery lead.

                  1 Reply Last reply Reply Quote 0
                  • D Offline
                    daniel
                    last edited by

                    What if you place the LoPy on a bread board and measure via the battery lead powering via 5V?

                    Can you also power the LoPy directly on the 3V3 pins (with a regulated 3V3 supply) and measure again? Thanks

                    Cheers,
                    Daniel

                    1 Reply Last reply Reply Quote 0
                    • J Offline
                      juriw @daniel
                      last edited by juriw

                      Hi, @daniel we have just tested SiPy without anything attached to it, with 5V input and deepsleep still pull 14.7mAh. That is unacceptable.
                      The IoT product we are developing on your platform is taking our calculations for battery lifetime from around +7 years down to a couple of days. It seems useless at the moment.

                      We tested the energy consumption with the following code

                      import machine
                      import time
                      
                      while(True):
                         
                         print("Starting Deepsleep")
                         machine.deepsleep(10000)
                         print("Deepsleep ended")
                         time.sleep(10)
                      
                      1 Reply Last reply Reply Quote 0
                      • S Offline
                        swohl
                        last edited by

                        I can confirm that in my case as well the Lopy in deepsleep mode is pulling ~10mAh while in the expansion board . Also the expansion board seems to pull ~140uAh with the Lopy unplugged. Could this be a result of the quiescent current of the BQ24040?

                        With the lopy not in the expansion board it seems to be pulling ~5.5mAh. It is an improvement, but still orders out from the specification.

                        I have a real world main.py running, so the lora, wifi and the adc are turned on while not in deepsleep, but when in deepsleep I assumed these peripherals would go into standby or be turned off.

                        For my application the current battery consumption renders the device well outside what could be deemed usable or practical to prototype with. Hopefully I am doing something terribly wrong, or this could be fixed in a firmware update.

                        1 Reply Last reply Reply Quote 0
                        • D Offline
                          daniel
                          last edited by Fred

                          Hello,

                          We know this is very important so we are working on sorting out this deep sleep current issue ASAP. We'll come back with feedback shortly.

                          Cheers,
                          Daniel

                          J 2 Replies Last reply Reply Quote 3
                          • J Offline
                            juriw @daniel
                            last edited by

                            @daniel Sounds good! We are really looking forward to this. We are doing a master thesis that is currently not working and we need to get our devices out asap :)

                            1 Reply Last reply Reply Quote 0
                            • J Offline
                              juriw @daniel
                              last edited by

                              Hi @daniel Any news? We need to get our prototype out next week.

                              1 Reply Last reply Reply Quote 1
                              • D Offline
                                daniel
                                last edited by

                                Hello @juriw both Espressif and us are working on the problem, it is top priority for us, but we cannot commit to an specific date for a resolution.

                                S 1 Reply Last reply Reply Quote 0
                                • S Offline
                                  swohl @daniel
                                  last edited by

                                  @daniel can you indicate if it is a hardware or software related? Before going down the road of writing libraries for sensors and such, building boards for the lopy it would be comforting to know if lowering power consumption is achievable through firmware updates, and what the power consumption would be. Using the specification from your datasheet of 25 uA, my question is this still the current goal of lopy version 1?

                                  1 Reply Last reply Reply Quote 1
                                  • D Offline
                                    daniel
                                    last edited by

                                    @swohl we have followed all the design guidelines recommended by Espressif and manufactured according to their specs. We are working with them to find a firmware resolution for this issue but we cannot give any more details at the moment.

                                    Cheers,
                                    Daniel

                                    B 1 Reply Last reply Reply Quote 1
                                    • B Offline
                                      blsmith @daniel
                                      last edited by

                                      @daniel

                                      Bump...any update?

                                      1 Reply Last reply Reply Quote 0
                                      • D Offline
                                        daniel
                                        last edited by

                                        We are homing-in on a few areas to solve the deep-sleep mode and expect to have an update for you next week. This is an Espressif / Pycom joint-effort and unfortunately we lost 3 days this week due to the Chinese bank holidays. We understand it's urgent and we are working as fast as possible to resolve it.

                                        Cheers,
                                        Daniel

                                        C 1 Reply Last reply Reply Quote 0
                                        • C Offline
                                          ccceeefff @daniel
                                          last edited by

                                          @daniel is there any significant difference between the ESP32 base module versus the LoPy implementation? Seems that deep sleep is working on an ESP-WROOM32 module which achieves ~5uA draw. Do you know if the ESP32 on the LoPy itself is still consuming power while in deep sleep or is it something else on the board?

                                          J 1 Reply Last reply Reply Quote 0
                                          • J Offline
                                            jasonriedy @ccceeefff
                                            last edited by

                                            @ccceeefff @daniel This raises an interesting point: Are you considering just the LoPy or the LoPy plus the expansion board? I know my tiny volume use needs to rely on the expansion board. But we can swap batteries every few months, so our needs also are not as stringent. (And we may need to switch to LTE-M, which should be easy on your platform.)

                                            1 Reply Last reply Reply Quote 0

                                            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                                            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                                            With your input, this post could be even better 💗

                                            Register Login
                                            • 1
                                            • 2
                                            • 2 / 2
                                            • First post
                                              Last post

                                            Pycom on Twitter

                                            Pycom