Hi Martin. Martin Weinelt wrote: > I recently bought an Upek Eikon from Amazon > (http://www.amazon.de/Upek-Fingerabdruck-Leseger%C3%A4t-Windows-Betriebssystem/dp/B001C3H4MQ/ref=sr_1_1?ie=UTF8&s=ce-de&qid=1226349133&sr=8-1) > which I supposed would be running by the upekts driver, as noted in the > "Supported Devices" listing. > > Unfortunately it is recognized as a 147e:2016 Device in lsusb, without > any naming: > > Bus 003 Device 005: ID 147e:2016
Thanks for looking into this. I looked at the logs you sent to this list, they are not immediately useful because they do not capture the device initialization sequence. Please try doing it like this: - Run SniffUsb - Enable auto refresh (every 1 second) - Plug device in - Install filter in SniffUsb - Unplug device - Plug device in again, logs should start growing, wait for 30 seconds - Unplug again Then upload that log somewhere. Also, UPEK have released a Linux driver for this hardware called BSAPI. If you could run that while capturing the output using usbmon that would be ideal. I'm assuming that BSAPI supports this device. This would actually be better than the windows sniff, because I think BSAPI uses a simpler protocol (or less security) and this is how I reverse engineered my device to produce upeksonly. Thanks, Daniel _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
