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 firmware?

    Scheduled Pinned Locked Moved Firmware
    otherlopy
    5 Posts 3 Posters 1.4k 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
      JuanMa
      last edited by

      Is Pysense firmware going to be released in the near future? It is a little frustrating to work with a black box. I think Pycom should release it the same way the development board firmware was released. It makes no sense the contrary.
      Thanks,
      JuanMa

      1 Reply Last reply Reply Quote 1
      • sebS Offline
        seb
        last edited by

        Hi,

        Open sourcing the Pysense/Pytrack firmware is something we are looking into but I am afraid I cannot provide an exact timeline. If there are any missing features that you require I can pass this on to the team.

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

          Thanks for the answer.
          The only bug I have notticed is related with the wake_reason after py.go_to_sleep(). In this code:

          if py.get_wake_reason() == WAKE_REASON_TIMER:
              # some code
          elsif py.get_wake_reason() == WAKE_REASON_PUSH_BUTTON
              #some code
          else
              #some code
          

          If the Lopy is reset inside deepsleep, the WAKE_REASON will be WAKE_REASON_TIMER. Am I doing something wrong? Should it not be a POWER_ON_RESET?
          Same happen if Lopy is reset inside the elsif code (WAKE_REASON_PUSH_BUTTON), but this time the wake reason is PUSH_BUTTON.

          Thanks again,

          JuanMa

          catalinC 1 Reply Last reply Reply Quote 0
          • catalinC Offline
            catalin @JuanMa
            last edited by

            Hi @juanma,
            Thanks for pointing out these scenarios, they have to be verified.
            The WAKE_REASON_PUSH_BUTTON is returned if Pysense Reset button is pressed.
            Another note is that after py.go_to_sleep(), the next python code is not executed; at wakeup, the micropython is reset.

            Catalin,

            Have you checked out our docs for the answer? (Now with an easy search function) https://docs.pycom.io
            Check out our newly revamped device management platform, Pybytes! https://pybytes.pycom.io/

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

              Thanks very much. From my experience, it is like if some flag is not reset when you press the reset button or you call machine.reset().

              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