Folks,
Thanks for the quick replies. The problem is that CONEX-AGP is known to the RHEL9 Linux kernel, but the CONEX-AGAP is not.
I was able to get it working by running these commands:
modprobe ftdi_sio
echo 104d 3008 > /sys/bus/usb-serial/drivers/ftdi_sio/newid
When I plugged in the CONEG-AGAP /dev/ttyUSB0 was created. When I plugged in a second CONEX-AGAP /dev/ttyUSB1 was created.
However, that solution is temporary and does not survive a reboot.
The permanent solution was to create these 2 files:
- /etc/modules-load.d/ftdi_sio.conf containing the following single line:
ftdi_sio
- /etc/udev/rules.d /99-conex-agap.rules containing these 2 lines:
ACTION="" ATTRS{idVendor}=="104d", ATTRS{idProduct}=="3008", RUN+="/bin/sh -c 'echo 104d 3008 > /sys/bus/usb-serial/drivers/ftdi_sio/new_id'"
SUBSYSTEM=="tty", ATTRS{idVendor}=="104d", ATTRS{idProduct}=="3008", SYMLINK+="conex_agap", MODE="0666"
Thanks again,
Mark
From: James P. Withrow <jwithrow at cornell.edu>
Sent: Friday, June 20, 2025 12:19 PM
To: Mark Rivers <rivers at cars.uchicago.edu>
Cc: tech-talk EPICS <tech-talk at aps.anl.gov>
Subject: Re: Problem with Newport CONEX-AGAP FTDI device on Linux
Mark -
It looks like the issue may be that the VID/PID pair (particularly the PID) may not be included in the currently running ftdi_sio driver.
A quick Google search turned up this incantation, which may be helpful:
echo "<VID> <PID>" > /sys/bus/usb-serial/drivers/ftdi_sio/new_id
Untested, as I’m out of the office, but hopefully this may point you in the correct direction.
-Jim Withrow
62363.524320] usb 1-4: new full-speed USB device number 11 using xhci_hcd
[62363.655966] usb 1-4: New USB device found, idVendor=104d, idProduct=3008, bcdDevice= 6.00
[62363.655975] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[62363.655978] usb 1-4: Product: CONEX-AGAP
[62363.655980] usb 1-4: Manufacturer: Newport
[62363.655982] usb 1-4: SerialNumber: A694ND5H