Re: Problem with Newport CONEX-AGAP FTDI device on Linux

["Dmitry Yu. Bolkhovityanov via Tech-talk" <tech-talk at aps.anl.gov>]

Hi Mark!

I suppose the problem is in product's ID.

Newport-CONEX-AGP's "idProduct=3006" *is* listed among supported IDs in 
ftdi_sio_ids.h, see https://urldefense.us/v3/__https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/usb/serial/ftdi_sio_ids.h?h=v6.16-rc2__;!!G_uCfscf7eWS!cEIzCUjhW53L-KKEAV3e3SDEZCubl_LXE7ev4lxhWZfS5l5_fb1Uvx73nAo1Qmei1z1rHE3YjXYUZg_-sksd1QU4UU-cxedRxvU$ 

#define NEWPORT_CONEX_AGP_PID		0x3006

(and in ftdi_sio.c driver too)

while CONEX-AGAP's "idProduct=3008" is not, even in the latest kernel 
version 6.16 (AFAIR, RHEL9 uses Linux kernet 5.14).

With best regards,
Dmitry



On Fri, 20 Jun 2025, Mark Rivers via Tech-talk wrote:

> Folks,
>
> I have an older Newport-CONEX-AGP controller that works fine on Linux.
> https://urldefense.us/v3/__https://www.newport.com/f/agilis-piezo-linear-stage-with-conex-controller__;!!G_uCfscf7eWS!esBpnKdccckn_TlnsWE5ruJncpjWNfxHfi8SNZ2M5qWp8ab4wjlgsB18EO_4YOzuwREd1qW6ipequMg2cHFGxsaFyd4$
>
> The device has a USB interface and uses FTDI.  When I plug in the device on my RHEL 9 machine I see these messages in dmesg:
>
> [62289.315988] usb 1-4: new full-speed USB device number 10 using xhci_hcd
> [62289.447505] usb 1-4: New USB device found, idVendor=104d, idProduct=3006, bcdDevice= 6.00
> [62289.447514] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [62289.447518] usb 1-4: Product: CONEX-AGP
> [62289.447520] usb 1-4: Manufacturer: Newport
> [62289.447522] usb 1-4: SerialNumber: A6UJN7YS
> [62289.450490] ftdi_sio 1-4:1.0: FTDI USB Serial Device converter detected
> [62289.450536] usb 1-4: Detected FT232R
> [62289.451085] usb 1-4: FTDI USB Serial Device converter now attached to ttyUSB0
>
> The device is now available on /dev/ttyUSB0.
>
> I expected to be able to do the same thing with a newer CONEX-AGAP controller.
> https://urldefense.us/v3/__https://www.newport.com/f/conex-piezo-absolute-positioning-mirror-mount__;!!G_uCfscf7eWS!esBpnKdccckn_TlnsWE5ruJncpjWNfxHfi8SNZ2M5qWp8ab4wjlgsB18EO_4YOzuwREd1qW6ipequMg2cHFG2VO-mdQ$
>
> However, when I plug in the device on my RHEL 9 machine I see these messages in dmesg:
>
> [62360.327898] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
> [62360.327934] ftdi_sio 1-4:1.0: device disconnected
> [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
>
> Note that I do not get the messages about ftdi_sio detected or the message about attaching to ttyUSBx.
>
> The new CONEX-AGAP works fine on Windows, where it appears as a COM port.  I can configure the COM port with EPICS:
>
> drvAsynSerialPortConfigure("serial1", "COM5", 0, 0, 0)
> asynOctetSetInputEos("serial1",0,"\r\n")
> asynOctetSetOutputEos("serial1",0,"\r\n")
> asynSetOption("serial1",0,"baud","921600")
> asynSetOption("serial1",0,"bits","8")
> asynSetOption("serial1",0,"stop","1")
> asynSetOption("serial1",0,"parity","none")
> asynSetOption("serial1",0,"clocal","Y")
> asynSetOption("serial1",0,"crtscts","N")
>
> Given the behavior on Windows, I think the CONEX-AGAP is also an FTDI device.  But if so, then why is Linux not recognizing it as such?
>
> Thanks,
> Mark
	_________________________________________
	  Dmitry Yu. Bolkhovityanov
	  The Budker Institute of Nuclear Physics
	  Novosibirsk, Russia