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

    OSX Pymakr Atom plugin, not seeing lopy

    Scheduled Pinned Locked Moved LoPy
    ftdiusbosxlopypymakr
    8 Posts 2 Posters 2.2k 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.
    • sorenS Offline
      soren
      last edited by

      Hi,

      I'm on OSX 10.12.6, I removed Apples FTDI drivers, completely, and I've JUST installed the latest D2XX (1.4.4) and VCP driver (2.4.2) from FTDI (rebooted also) as well as the d2xx helper.
      I then updated Pymakr to the latest version 1.2.1, and I STILL have this annoying issue where every time I connect a different lopy (also different expansion board) atom will not see the lopy anymore. A reboot is then required. I'm in a setup where I'm configuring many LoPy's so this is extremely time consuming.

      Did anyone else experience this ?

      1 Reply Last reply Reply Quote 0
      • sorenS Offline
        soren
        last edited by

        no-one? ...

        1 Reply Last reply Reply Quote 0
        • R Offline
          Ralph
          last edited by

          Hi @soren. There is indeed a problem with FTDI on mac, that causes the com port to fail whenever you unplug your expansion board while there is an open connection to it. It'll completely disappear from the /dev folder. It's annoying but not much we can do about it, and I'm not sure if changing all the drivers helps (I guess it didn't, seeing you are posting this).

          A thing to keep in mind is to always close the connection (collapsing the pymakr terminal) before disconnecting the device. If you forget it once, you can switch to a different USB port, until you run out of those and you indeed need to reboot.

          sorenS 3 Replies Last reply Reply Quote 0
          • sorenS Offline
            soren @Ralph
            last edited by

            @ralph OK, good to know that closing the connection is at least an option. Will save me a lot of time, thank you!

            1 Reply Last reply Reply Quote 0
            • sorenS Offline
              soren @Ralph
              last edited by

              @ralph hmm even after closing the connection - i got this problem again.

              R 1 Reply Last reply Reply Quote 0
              • R Offline
                Ralph @soren
                last edited by

                @soren Really? So after changing to a different expansion board, The 'more > Get serial ports' shows no ports at all? And after switching to a different USB port, does it re-appear again in this list?

                1 Reply Last reply Reply Quote 0
                • sorenS Offline
                  soren @Ralph
                  last edited by

                  @ralph

                  so after a pause from the lopy, coming back - with the absolute same setup - i'm getting this issue again, but this time closing the connection does not make a difference: all pymakr will show me, ever, when showing serials is this:

                  Found 3 serialports
                  /dev/cu.lpss-serial2 (copied to clipboard)
                  /dev/cu.iPhone-WirelessiAP
                  /dev/cu.JabraStylev130-CSRGAIA

                  why does it pick the lpss-serial2? that port is there also when the lopy is not connected. I've tried different usb cables as well.

                  R 1 Reply Last reply Reply Quote 0
                  • R Offline
                    Ralph @soren
                    last edited by

                    @soren Sorry for the late reply. Atom currently always copies the top option in the list. If there is an actual Pycom serial detected, it will place that one at the top. Anyway, this is just a result of your issue, not the cause.

                    So just to be sure, after rebooting your mac, you are able to connect to your device? Then when switching out to a different lopy, the comport disappears from the list of serials, even when closing the connection during the swap? Do you switch expansionboards, or just the lopy? You could even hot-swap your lopy while keeping the expansion board connected, see if that helps.

                    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