2016-10-01 17:59 GMT+02:00 MATHIEU Clement <[email protected]>: > Hello > > i need your help regarding the following issue : > > i have a hero touch ups from infosec. it is connected via USB to a raspberry > pi 3. > i’ve configure ups.conf file as below > > [HERO] > driver = blazer_usb > vendorid = 0665 > productid = 5161 > > either with > port = auto > or > port = /dev/hidraw0 > or > port = /dev/ttySo > > the connection never works
The 'blazer_usb' driver (like others based on libusb) don't actually use the 'port' argument, but, since it is still required by NUT, you should set it to 'auto'. > > i get the following log from command line : > sudo /lib/nut/blazer_usb -a HERO -DDD -u root > Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2) > 0.000000 debug level is '3' > 0.003947 Checking device (0665/5161) (001/116) > 0.016760 - VendorID: 0665 > 0.017245 - ProductID: 5161 > 0.017686 - Manufacturer: INNO TECH > 0.018127 - Product: USB to Serial > 0.018598 - Serial Number: unknown > 0.019086 - Bus: 001 > 0.019540 Trying to match device > 0.020136 Device matches > 0.020655 failed to claim USB device: could not claim interface 0: Device > or resource busy > 0.021625 detached kernel driver from USB device... > 0.022676 Trying megatec protocol... > 0.025291 send: Q1 > 0.153928 read: N > 0.154751 blazer_status: short reply > 0.155441 Status read 1 failed > 0.156783 send: Q1 > 0.286922 read: N > 0.287605 blazer_status: short reply > 0.288335 Status read 2 failed > 0.289796 send: Q1 > 0.419969 read: N > 0.420052 blazer_status: short reply > 0.420081 Status read 3 failed > 0.420107 Trying mustek protocol... > 0.420818 send: QS > 1.654899 read: could not claim interface 0: Device or resource busy > 1.655782 blazer_status: short reply > 1.656445 Status read 1 failed > 1.657598 send: QS > 2.891901 read: could not claim interface 0: Device or resource busy > 2.892810 blazer_status: short reply > 2.893497 Status read 2 failed > 2.894755 send: QS > 4.129250 read: could not claim interface 0: Device or resource busy > 4.129411 blazer_status: short reply > 4.129503 Status read 3 failed > 4.129590 Trying megatec/old protocol... > 4.130286 send: D > 4.254420 read: N > 4.254520 blazer_status: short reply > 4.254608 Status read 1 failed > 4.255296 send: D > 4.379452 read: N > 4.379601 blazer_status: short reply > 4.379692 Status read 2 failed > 4.380447 send: D > 4.504477 read: N > 4.504631 blazer_status: short reply > 4.504725 Status read 3 failed > 4.504812 Trying zinto protocol... > 4.505581 send: Q1 > 4.635465 read: N > 4.635565 blazer_status: short reply > 4.635654 Status read 1 failed > 4.636344 send: Q1 > 4.766481 read: N > 4.766580 blazer_status: short reply > 4.766668 Status read 2 failed > 4.767360 send: Q1 > 4.897519 read: N > 4.897659 blazer_status: short reply > 4.897749 Status read 3 failed > 4.897835 No supported UPS detected > any idea ? This seems like something that might be supported by 'nutdrv_qx' driver with 'voltronic-qs-hex' protocol, an early version of which is part of the 2.7.3 release, while an improved version with support for more devices is available in 2.7.4. If possible, give it a try. _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
