USB/ekey bug?

[morkovka]

Hi,

I'm using eKey FSX app connected to an ekey using a USB-RS485 adapter, which uses /dev/ttypUSB0 as it's the only 'usb device' connected to Wiser.  Most of the time everything works fine, but sometimes I noticed my ekey gets disconnected - and when I check the logs I see a storm of:

Aug 26 10:03:30 wiser kern.err kernel: [78950.816576] ftdi_sio ttyUSB0: usb_serial_generic_write_bulk_callback - nonzero urb status: -71
Aug 26 10:03:29 wiser kern.err kernel: [78949.817573] ftdi_sio ttyUSB0: usb_serial_generic_write_bulk_callback - nonzero urb status: -71
Aug 26 10:03:28 wiser kern.err kernel: [78948.815564] ftdi_sio ttyUSB0: usb_serial_generic_write_bulk_callback - nonzero urb status: -71
Aug 26 10:03:27 wiser kern.err kernel: [78947.808566] ftdi_sio ttyUSB0: usb_serial_generic_write_bulk_callback - nonzero urb status: -71
Aug 26 10:03:26 wiser kern.err kernel: [78946.809623] ftdi_sio ttyUSB0: usb_serial_generic_write_bulk_callback - nonzero urb status: -71
Aug 26 10:03:25 wiser kern.err kernel: [78945.809576] ftdi_sio ttyUSB0: usb_serial_generic_write_bulk_callback - nonzero urb status: -71
Aug 26 10:03:24 wiser kern.err kernel: [78944.809573] ftdi_sio ttyUSB0: usb_serial_generic_write_bulk_callback - nonzero urb status: -71
Aug 26 10:03:23 wiser kern.err kernel: [78943.808560] ftdi_sio ttyUSB0: usb_serial_generic_write_bulk_callback - nonzero urb status: -71
Aug 26 10:03:22 wiser kern.err kernel: [78942.809568] ftdi_sio ttyUSB0: usb_serial_generic_write_bulk_callback - nonzero urb status: -71
Aug 26 10:03:21 wiser kern.err kernel: [78941.809606] ftdi_sio ttyUSB0: usb_serial_generic_write_bulk_callback - nonzero urb status: -71
.....
repeats once a second while USB adapter is connected

If I re-plug the USB adapter to wiser, it detects the adapter and assigns it to /dev/ttyUSB1:

Aug 26 10:03:40 wiser kern.info kernel: [78961.098810] usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB1
Aug 26 10:03:40 wiser kern.info kernel: [78961.097070] usb 1-1: Detected FT232RL
Aug 26 10:03:40 wiser kern.info kernel: [78961.096879] ftdi_sio 1-1:1.0: FTDI USB Serial Device converter detected
Aug 26 10:03:40 wiser kern.info kernel: [78961.091624] usb 1-1: SerialNumber: A10KNCJH
Aug 26 10:03:40 wiser kern.info kernel: [78961.091613] usb 1-1: Manufacturer: FTDI
Aug 26 10:03:40 wiser kern.info kernel: [78961.091601] usb 1-1: Product: FT232R USB UART
Aug 26 10:03:40 wiser kern.info kernel: [78961.091589] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug 26 10:03:40 wiser kern.info kernel: [78961.091561] usb 1-1: New USB device found, idVendor=0403, idProduct=6001
Aug 26 10:03:40 wiser kern.info kernel: [78960.945855] usb 1-1: new full-speed USB device number 3 using ci_hdrc
Aug 26 10:03:30 wiser kern.info kernel: [78951.178812] ftdi_sio 1-1:1.0: device disconnected
Aug 26 10:03:30 wiser kern.info kernel: [78951.178743] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
Aug 26 10:03:30 wiser kern.info kernel: [78951.176855] usb 1-1: USB disconnect, device number 2

eKey still won't work in this case because it's expecting the fingerprint reader to be on /dev/ttyUSB0.

The only 'solution' is to reboot Wiser which then comes back up with everything working - USB adapter assigned to /dev/ttyUSB0 and consequently ekey detecting the fingerprint reader - everything is okay until the next time the above kernel messages appear.

I have tried 2 different USB-RS485 adapters and the problem occurs in both. 

Is this a bug in the kernel / USB driver? how do I get this resolved?

[admin]

This is a hardware not a software issue. What is the USB cable length or does this adapter plug directly into the USB port? There are many counterfeit FTDI adapters which might be unreliable.

[morkovka]

Okay, thank you for the response.  The length is very small and it does plug directly into USB, but I cannot be 100% sure the adapter is not to blame.

[agris]

Try to change diferent USB adapter location in the tab "Scanners" data block 'Configuration' by entering:
http://__your_lm_ip_address_/apps/data/ekey/admin.lp
Than start the ekey App daemon again.