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

    FTDI drivers with FiPy+PyTrack in Win 7

    Scheduled Pinned Locked Moved FiPy
    replftdiwindows
    14 Posts 4 Posters 3.1k Views 4 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.
    • H Offline
      halli50 @jmarcelino
      last edited by

      @jmarcelino, I have a Pytrack which seems okay (installed pytrack_0.0.8.dfu succesfully), but my Pysense never appears in my Device Manger (installed pysense_0.0.8.dfu with apparent success using the command window method). The Pysense, however, seems to be stone-cold dead!
      I'll give this a rest until the new year, but will probably be back with my problems on jan.2nd 2018.
      Until then, I wish you a happy new year!

      1 Reply Last reply Reply Quote 0
      • S Offline
        sandipg @jmarcelino
        last edited by

        Hey @jmarcelino ,
        I've installed the PyTrack driver already - I see the COM port when the PyTrack is connected. However I am unable to establish a serial connection to the board (with PuTTY).
        Thanks for your help.

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

          @sandipg Did you disable flow control in Putty?

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

            @robert-hh Not at first, but I tried now with Flow control set to 'None' - still no connection..
            Parity is set to None, Baud rate is 9600, Data bits 8, Stop bits 1.

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

              @sandipg the baud rate should be 115200, but may be not matter. In any case, 115200 is a good choice.

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

                @robert-hh Hmm..it worked with 115200 baud rate. Thanks!

                1 Reply Last reply Reply Quote 0
                • S Offline
                  sandipg
                  last edited by

                  I did a soft reset via the Serial connection by pressing Ctrl+D. Now, when I plug back the USB, the COM port is no longer visible. Any ideas on this?

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

                    @sandipg Soft reset and COM device visibility are not related at all. But when you say re-plug USB, it means that you also unplugged it, which may windows cause to assign a different COM port on re-plugging, especially when you use a different USB socket. Did by chance now a new COM port show up?

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

                      @robert-hh No, the same COM port showed up after a few tries. Its probably an OS or cable issue..

                      I'm considering getting a LiPo battery 3.7V for powering the PyTrack+FiPy and accessing the device over WLAN. Would this battery be ok for that purpose: https://www.conrad.de/de/modellbau-akkupack-lipo-37-v-600-mah-zellen-zahl-1-30-c-tattu-stick-molex-stecksystem-1542426.html

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

                        @sandipg
                        The voltage and capacity are OK but it's the wrong connector, you want a JST PH-2 (also check the polarity as there is no standard)

                        For Germany perhaps check out these two from HobbyKing: (the higher capacity 2000mAh is cheaper as it's on sale, but see dimensions etc)

                        https://hobbyking.com/de_de/turnigy-2000mah-1s-1c-lipoly-w-2-pin-jst-ph-connector.html

                        https://hobbyking.com/de_de/turnigy-1200mah-1s-1c-lipoly-w-2-pin-jst-ph-connector.html

                        1 Reply Last reply Reply Quote 2

                        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