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

    Pytrack power consumption

    Scheduled Pinned Locked Moved Expansion Board
    pytrackexpansionlopypower
    4 Posts 2 Posters 628 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.
    • J Offline
      james.matthews
      last edited by

      Hi all,

      The power consumption for the LoPy4 is very well documented, but nothing exists for the Pytrack. Could anyone tell me what the idle power is, or what the power is during gps acquisition etc?

      Thanks

      J 1 Reply Last reply Reply Quote 0
      • J Offline
        jcaron @james.matthews
        last edited by

        @james-matthews Your best bet is probably to look up each individual chip's datasheets. There are quite a few possible combinations of use of the various chips on board and of their respective modes of operation.

        J 1 Reply Last reply Reply Quote 0
        • J Offline
          james.matthews @jcaron
          last edited by

          @jcaron said in Pytrack power consumption:

          @james-matthews Your best bet is probably to look up each individual chip's datasheets. There are quite a few possible combinations of use of the various chips on board and of their respective modes of operation.

          OK thanks for that. I'll do that. Any idea what the idle power of the board is?

          J 1 Reply Last reply Reply Quote 0
          • J Offline
            jcaron @james.matthews
            last edited by

            @james-matthews Depends what you mean by "idle". In Pytrack-assisted deep sleep it should be somewhere in the range of 10-20 µA. Once you wake up the ESP32 and/or radios whatever the Pytrack uses is drowned in the consumption of those.

            Note that in my experience, keeping the accelerometer active for wake-on-fall/tap/movement already brings power draw to several hundred µA rather than a few dozen as expected (but that was on the Pysense, and I haven't much investigated the cause for the issue since). I expect the GPS to be a lot more power-hungry, though there are probably standby modes and the like.

            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