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

    External IO Header connections

    Scheduled Pinned Locked Moved Comments & Feedback
    pytrackpin
    9 Posts 6 Posters 3.2k Views 6 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.
    • E Offline
      Emmanuel Goudot
      last edited by

      I am trying to understand connections of pytrack (mine is labeled "V1.0") as shown here: https://docs.pycom.io/pycom_esp32/_downloads/pytrackPinoutComp.pdf
      Ext IO header pin 2 labeled "PWR_EN" should be connected to LoPy (or other) pin P3 (PWR_EN), but it is not the case.
      Ext IO header pin 9 "EXT_IO_4" is in fact connected to P4 SD_CMD
      Ext IO header pin 10 "EXT_IO_5" is in fact connected to P8 SD_DAT

      pytrackPinoutComp.pdf is quite misleading and components are also not as received board.
      Would it be possible to get updated and correct documentation ?

      G 1 Reply Last reply Reply Quote 2
      • B Offline
        bucknall
        last edited by

        @Emmanuel-Goudot Verifying this with the team - will make the corrections asap! Thanks!

        Developer Evangelist - Pycom

        J 1 Reply Last reply Reply Quote 0
        • T Offline
          this.wiederkehr
          last edited by

          @bucknall, is there an update on this topic?

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

            As discussed here:
            https://forum.pycom.io/topic/1673/pysense-pinout/4

            The documentation is quite incorrect.

            On the Pysense:

            • pins 3 and 4 are reversed (pin 4 is the power to the board, pin 3 power to the module)
            • pin 5 (EXT_IO0) is connected to P2 / G23 / RGB_LED
            • pin 9 (EXT_IO4) is connected to G11 / P4 / SD_CMD
            • pin 10 (EXT_IO5) is connected to P8 / G15 / SD_DAT

            Pins EXT_IO4 and EXT_IO5 are NOT connected to the PIC.

            Pins EXT_IO0, EXT_IO1 and EXT_IO2 are connected to the PIC. However they are all connected to port C, which does not allow interrupts. So the sentence:

            Interrupts EXT_IO0, EXT_IO4 & EXT_IO5 are connected to a PIC and are accessible via Pycom Libraries

            is completely incorrect. No interrupts, wrong pins.

            The situation seems to be quite similar for the Pytrack.

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

              This post is deleted!
              1 Reply Last reply Reply Quote 0
              • J Offline
                jmahesh @bucknall
                last edited by

                @bucknall Any update on the topic..?

                I wanna connect a Buzzer with IO Header.
                Please suggest a topic to refer..

                1 Reply Last reply Reply Quote 0
                • G Offline
                  gregcope @Emmanuel Goudot
                  last edited by

                  @emmanuel-goudot I have just wasted a load of time working out the same thing.

                  Can someone at Pycom change/improve the pytrack documentation/PINout diag;

                  https://pycom.io/wp-content/uploads/2017/04/pytrackPinoutCompN3.pdf

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

                    @gregcope Where did you get that link from? The current doc (https://docs.pycom.io/chapter/datasheets/downloads/pytrack-pinout.pdf) linked from https://docs.pycom.io/chapter/datasheets/boards/pytrack.html is correct. You seem to have a link to a previous version of the pinout.

                    @seb: you should probably remove the old document and/or redirect the old URL to the new one?

                    G 1 Reply Last reply Reply Quote 0
                    • G Offline
                      gregcope @jcaron
                      last edited by

                      @jcaron Ahhhhhhh. Thanks.

                      I have been using this;

                      https://pycom.io/product/pytrack/

                      "PIN OUT" link

                      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