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 not working.

    Scheduled Pinned Locked Moved Expansion Board
    6 Posts 2 Posters 290 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.
    • S Offline
      sandris
      last edited by

      So I got a couple off GPys and pytracks.
      Mostly everything works ok, however some of my pytrack seems to be dead.
      When I connect GPy to some of the pytracks, pymakr is stuck on
      "Connecting to COM30..." and the program on the GPy is not starting, program start with lighting the LED.
      The problem persist trough several GPys, (verified to work on other pytracks) computers and cables.
      Any help would be appreciated.

      robert-hhR 1 Reply Last reply Reply Quote 0
      • robert-hhR Offline
        robert-hh @sandris
        last edited by

        @sandris Did you check if they evetually register at a different COM port?

        S 1 Reply Last reply Reply Quote 0
        • S Offline
          sandris @robert-hh
          last edited by

          @robert-hh
          Not sure if I understand what you mean. My main issue is not that I cannot connect to the com port, it's that the pytrack module seems to be unable to power the gpy correctly, it's like the pytrack is stuck in a sort of error state.
          I have tried to update the pytrack, and can see that it changes into the bootloader state, and back.

          robert-hhR 1 Reply Last reply Reply Quote 0
          • robert-hhR Offline
            robert-hh @sandris
            last edited by

            @sandris Can you measure the voltage at Vin?

            S 1 Reply Last reply Reply Quote 0
            • S Offline
              sandris @robert-hh
              last edited by

              @robert-hh
              Ahaha, that's seems to be the issue.
              Without a GPy it's at 4.8, while only at 3.4 V, with the GPy connected.
              This is powered by USB, it drops even lower when battery powered.

              robert-hhR 1 Reply Last reply Reply Quote 0
              • robert-hhR Offline
                robert-hh @sandris
                last edited by

                @sandris That looks like a hardware problem on the pytrack. For power saving, it can switch off the power to the Vin pin. So this switching logic seems to fail. There is a package with imprints of J13 and 1731G close to the battery connector, which seems to switch the power. But I do not know what part number it is.
                B.t.w.: A stable 3.4 V supply is sufficient to run a Pycom development module, so I assume it will drop further.

                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