That's a shame! I was excited to have such an easy solution for a
decidedly annoying problem... I can't help much on the Windows side
of things unfortunately. Are the devices off-the-shelf products or
are they something custom built for your application?
In the past I have used this udev rule to create symlinks that
helped me map out the devices. If you use the PROGRAM={} you can run
a script that produces the name of the device instead of using the
symlink.
# udev rule for AWARE MCCM G2 serial interfaces
#identify FTDI devices with VID/PID pair and create a convent
symlink in /dev
SUBSYSTEM=="usb", ATTRS{idVendor}=="0403", GROUP="plugdev",
SYMLINK+="%s{product}_%s{serial}"
On 3/8/2018 8:56 PM, Robert Poor wrote:
@Ryan:
I was trying to ditch the pyserial lib specifically because
of problems on Windows, notably:
[Disclaimer: I'm using the pylibftdi library as my
sole access to the libftdi library, so pardon any
translation errors...]
I'm running in an environment where there may be
multiple FTDI devices plugged in. And I'm running
other code (a Modbus library) that needs to know the
port names (i.e. /dev/cu.usbxxx on unix/osx or COMxx
on Windows) for each FTDI device.
I'm using ftdi_usb_find_all() (via pylibftdi's
Device.list_devices()) to get the list of serial
numbers -- that works. But I need to know the port
names for each device.
Is there a call in libftdi that will produce the port
name for a given serial number?
