USB/ekey bug? - Printable Version +- Logic Machine Forum (https://forum.logicmachine.net) +-- Forum: LogicMachine eco-system (https://forum.logicmachine.net/forumdisplay.php?fid=1) +--- Forum: Gateway (https://forum.logicmachine.net/forumdisplay.php?fid=10) +--- Thread: USB/ekey bug? (/showthread.php?tid=3529) |
USB/ekey bug? - morkovka - 27.08.2021 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: Quote:Aug 26 10:03:30 wiser kern.err kernel: [78950.816576] ftdi_sio ttyUSB0: usb_serial_generic_write_bulk_callback - nonzero urb status: -71 If I re-plug the USB adapter to wiser, it detects the adapter and assigns it to /dev/ttyUSB1: Quote:Aug 26 10:03:40 wiser kern.info kernel: [78961.098810] usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB1 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? RE: USB/ekey bug? - admin - 27.08.2021 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. RE: USB/ekey bug? - morkovka - 27.08.2021 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. RE: USB/ekey bug? - agris - 30.08.2021 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. |