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

    Pysense 2.0X: How to keep the module's RTC active in (deep) sleep so time can be kept?

    Scheduled Pinned Locked Moved Comments & Feedback
    6 Posts 2 Posters 66 Views 3 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.
    • J Offline
      jand
      last edited by jand

      I figured out how to use the Pysense 2.0 X board to monitor other sensors (by connecting them to the external IO header), and it is a great product because it has the onboard sensors, the MicroSD card, and a well functioning sleep mode that powers down everything (including the sensors). But the Pysense's go_to_sleep() command also powers down the LoPy4/GPy,/WiPy/.. module and hence time is no longer kept during the sleep which is a major limitation. The problem is well described here: [https://forum.pycom.io/topic/4382/restore-rtc-value-after-pysense-go_to_sleep] But the workaround suggested is not entirely satisfying.

      Is there a way to first power down the MicroSD card and all sensors (using commands like py.sensor_power(False) included in pycoproc.py) without powering down the module? And next to bring the module in deepsleep mode using the machine.deepsleep() function? The trouble is the lack of documentation on how this pic processor on the Pysense is used.

      1 Reply Last reply Reply Quote 1
      • G Offline
        Gijs
        last edited by

        Hi,
        We are currently working on providing a solution for the other issue and taking this in account there as well! I hope we can publish something after Christmas

        Gijs

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

          Hi Gijs,
          Thanks very much. I look forward to the solution.
          Jan

          1 Reply Last reply Reply Quote 0
          • G Offline
            Gijs
            last edited by

            I was looking for this last week, but could not remember where I saw it. My colleague already published a sneak preview here: https://github.com/pycom/pycom-libraries/issues/132#issuecomment-748895114
            Gijs

            J 1 Reply Last reply Reply Quote 2
            • J Offline
              jand @Gijs
              last edited by

              @Gijs Thanks very much. I will try this and report back.
              Jan

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

                @Gijs
                Unfortunately I got stuck when doing the Pysense 2.0X firmware update. See my call for help in https://github.com/pycom/pycom-libraries/issues/132#issuecomment-748895114
                Looks like I am not the first Pycom user running into this trouble, but I can't find a clear solution on the forum.

                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