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

    Deep sleep with Pysense - Different APIs

    Scheduled Pinned Locked Moved Discussion
    pysensedeepsleepfipy
    3 Posts 2 Posters 872 Views 2 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.
    • H Offline
      Henning
      last edited by

      I'm using a FiPy with a PySense board. It reads a sensor value every few minutes and sends it via WiFi. In the remaing time I want to send it to sleep (based on a wakeup timer).
      Now I found two different Docs on that:
      https://docs.pycom.io/chapter/datasheets/boards/deepsleep/api.html
      https://docs.pycom.io/chapter/pytrackpysense/apireference/sleep.html
      And in some posts I saw "machine.go_to_sleep()".

      Can someone give a me short overview over the difference between these methods? Whats the correct way for this use case?

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

        If you are using a LoPy 1 (not LoPy 4), a SiPy or a WiPy 2 (not WiPy 3), there is an issue with the "native" deep sleep (machine.deepsleep) which has a higher power consumption than wanted.

        For those boards, and only those, if you want to achieve very low power deep sleep (on the order of 10 µA), you need something else to completely power down the board. This could be a deep sleep shield, a Pysense, or a Pytrack, which have a way to control power to the board. That's the goal of the Deep Sleep API and the Deep Sleep features of the PyTrack and PySense APIs.

        If you use one of the newer boards (including WiPy 3, LoPy4, FiPy), as in your case, you can use the native deep sleep directly, see https://docs.pycom.io/chapter/firmwareapi/pycom/machine/#machinedeepsleeptimems

        H 1 Reply Last reply Reply Quote 1
        • H Offline
          Henning @jcaron
          last edited by

          @jcaron
          Thanks a lot for the explanation! That solved the question for me.

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

          Pycom on Twitter

          Pycom