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 4 - Current consumption and Deep Sleep

    Scheduled Pinned Locked Moved LoPy
    lopylopy4deepsleepconsumptioncurrent
    23 Posts 7 Posters 10.5k Views 7 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.
    • C Offline
      cduplouy @livius
      last edited by

      @livius

      Here's a picture of the two different devices

      0_1518769185177_LoPy4.jpeg

      J 1 Reply Last reply Reply Quote 2
      • J Offline
        jmarcelino @cduplouy
        last edited by

        Hi @cduplouy

        Can you post photos of the back of the device please. Since it may have serial numbers please email it to me at jmarcelino@pycom.io

        Also please let me know where you purchased them.

        Thank you.

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

          Just an update, we do have both devices internally (I'm still checking why there are two stickers). We've tested and both should give good deepsleep results.

          Can you confirm you are doing exactly the same deepsleep test on both devices? If so it's possible there is some physical problem with the higher current one.

          However the problem is not related to which sticker your device has.

          C 2 Replies Last reply Reply Quote 0
          • G Offline
            Gomez
            last edited by

            Hi,
            same for me with FiPy and expansion board. Tested with a battery pack made of 2 x 18650, during deepsleep power consumption is around 18-30 ma. Also tried to remove the RTS,CTS and LED jumper as suggested in other post ( RTS e CTS to avoid the TTL to USB converter maybe stay in high power "consumption mode" ) ans 180 ma during main.py processing and Sigfox transmission.
            Regards, Andrea

            J 1 Reply Last reply Reply Quote 0
            • J Offline
              jmarcelino @Gomez
              last edited by jmarcelino

              Hi @gomez,

              The FiPy issue is completely unrelated, that's due to in some cases the LTE modem not being properly put into deepsleep (airplane mode). We're working on it. Please see this post: https://forum.pycom.io/post/15268

              1 Reply Last reply Reply Quote 0
              • C Offline
                cduplouy @jmarcelino
                last edited by

                @jmarcelino
                Thanks for the update.

                I confirm I use the same files to make my tests.

                I got 3 other LoPy 4. I'm going to run some tests on them as well and I'll keep you updated.

                1 Reply Last reply Reply Quote 0
                • C Offline
                  cduplouy @jmarcelino
                  last edited by

                  @jmarcelino

                  Seems like I was really unlucky ...
                  There's only one LoPy 4 that doesn't work in Deep Sleep mode !

                  I am around 40 to 50 uA with all of the other LoPy 4.
                  Do you know if that is the lowest we can get ?

                  J 1 Reply Last reply Reply Quote 0
                  • J Offline
                    jmarcelino @cduplouy
                    last edited by jmarcelino

                    @cduplouy
                    That's expected, are you using machine.pin_deepsleep_wakeup()? I found that increases consumption a bit more compared to timer deepsleep.

                    There's also around 16 μA loss due to going through the voltage regulator. For even lower power consumption we recommend the OEM module which can be powered directly at 3.3V. (don't power the LoPy4 without going through the regulator on Vin, unless you physically remove it)

                    If you get our OEM reference board and the OEM module you can also remove a resistor to disconnect the voltage regulator.

                    C 1 Reply Last reply Reply Quote 1
                    • C Offline
                      cduplouy @jmarcelino
                      last edited by

                      @jmarcelino

                      I tried with my power supply through the Vin Pin at 3.7V. I get 40 to 50 uA in Deepsleep
                      Then I tried with my power suply at 3.3V and indeed i had like 24 uA !

                      Thank you again for your help

                      C 1 Reply Last reply Reply Quote 0
                      • C Offline
                        chippy mathew @cduplouy
                        last edited by

                        @cduplouy I am also getting around 15mA during deepsleep. I tried with 3.3v and 3.7v using resistor but then it is not sufficient power for the pycom to run.

                        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
                        • 1 / 2
                        • First post
                          Last post

                        Pycom on Twitter

                        Pycom