search for: libusb_set_report

...- UPS driver controller 2.4.3 Network UPS Tools - Megatec protocol driver 1.6 (2.4.3) Serial-over-USB transport layer 0.10 libusb_get_interrupt: error sending control message: Operation not permitted libusb_get_interrupt: error submitting URB: Device or resource busy Megatec protocol UPS detected. libusb_set_report: error sending control message: Device or resource busy ser_send_pace: Device detached? (error -1: error sending control message: Device or resource busy) Successfully reconnected libusb_get_interrupt: could not claim interface 0: Device or resource busy libusb_get_interrupt: error submitting URB:...

...or 0 Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.6 (2.0.3) Warning: This is an experimental driver. Some features may not function correctly. Detected a UPS: TRIPP LITE/TRIPP LITE OMNIVS1500XL Unknown protocol (2001)Attached to Tripp Lite OMNIVS1500XL Unknown value for s[2]: 0x34 libusb_set_report() returned -6 instead of 8 Error reading L value: Unknown error -6 Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.6 (2.0.3) Warning: This is an experimental driver. Some features may not function correctly. Detected a UPS: TRIPP LITE/TRIPP LITE OMNIVS1500XL Unknown protocol (2001)Att...

Model: Tripp-lite OMNIVS1500 Error: Network UPS Tools - UPS driver controller 2.2.1- Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.11 (2.2.1-) Warning: This is an experimental driver. Some features may not function correctly. Detected a UPS: unknown/unknown libusb_set_report() returned -1 instead of 8 Could not reset watchdog. Please send model information to nut-upsdev mailing list libusb_set_report() returned -1 instead of 8 Error reading protocol Driver failed to start (exit status=1) ___________________________ Chris Abel Systems and Network Administrator Wildwoo...

...0RM2U libusb_get_interrupt() returned -110 instead of 8 libusb_get_interrupt() returned 0 instead of 8 libusb_get_interrupt() returned -110 instead of 8 libusb_get_interrupt() returned -19 instead of 8 libusb_get_interrupt() returned -19 instead of 8 libusb_get_interrupt() returned -19 instead of 8 libusb_set_report() returned -19 instead of 8 Could not reset watchdog. Please send model information to nut-upsdev mailing list libusb_set_report() returned -19 instead of 8 Error reading protocol Driver failed to start (exit status=1) -- /usr/local/etc/ups.conf -- [tripplite] driver = tripplite_usb p...

...--------------------------- stream:~# upsdrvctl start Network UPS Tools - UPS driver controller 2.2.2 Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.11 (2.2.2) Warning: This is an experimental driver. Some features may not function correctly. Detected a UPS: Tripp Lite /TRIPP LITE UPS libusb_set_report() returned -32 instead of 8 Could not reset watchdog. Please check andsee if usbhid-ups(8) works with this UPS. Driver failed to start (exit status=1) ------------------------------------ stream:~# /lib/nut/tripplite_usb -a tripplite -DDDDD Checking device (09AE/1007) (004/003) - VendorID: 09ae -...

..."00 7f 00 89 0d 00 00 '.......'" 3128.236831 send_to_all: SETINFO ups.debug.D "00 7f 00 89 0d 00 00 '.......'" 3128.239120 send_cmd(msg_len=2, type='V') 3128.240055 send_cmd: sending 3a 56 a9 0d 00 00 00 00 '.V......' 3128.241548 libusb_set_report() returned 0 instead of 8 3128.243292 Error reading 'V' value: Device detached? (error 0: error sending control message: Broken pipe) 3128.244404 Reconnect attempt #1 3128.244490 ================================================== 3128.244589 = device has been disconnected, t...

...ter/drivers/tripplite_usb.c#L527 So it is trying ten times to send, and for each send attempt, it tries to receive ten times. These numbers are somewhat arbitrary, and are probably tuned more for the OMNIVS1000, but feel free to adjust them, and let me know what you find out. > 3128.241548 libusb_set_report() returned 0 instead of 8 > 3128.243292 Error reading 'V' value: Device detached? (error 0: > error sending control message: Broken pipe) > 3128.244404 Reconnect attempt #1 This one is different - "Broken pipe" does mean an actual disconnect signal, so there is n...

...how to integrate this driver with NUT and I wonder if you could give me some guidance in that sense. To be more specific: In order to communicate with this UPS both input and output have to be performed as USB interrupts I/O as this UPS doesn't recognizes Control IO, so libusb_get_report() and libusb_set_report() will not work. Looking at libusb.c I realized there's a libusb_get_interrupt() which can be used to read from the endpoint, however there's no counterpart libusb_set_interrupt() API and usb_communication_subdriver_t structure doesn't contain a *set_interrupt element as well: libusb.h...

...er:/RAID/Server-Main/Equipment/HighPoint Adapters# upsdrvctl start Network UPS Tools - UPS driver controller 2.6.4 Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.6.4) Warning: This is an experimental driver. Some features may not function correctly. Detected a UPS: unknown/unknown libusb_set_report() returned 0 instead of 8 Error reading protocol Driver failed to start (exit status=1) lsusb reports: Bus 007 Device 002: ID 09ae:0001 Tripp Lite Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at I...

...usb_open': : undefined reference to `usb_control_msg' libusb.o(.text+0x418): In function `libusb_open': : undefined reference to `usb_close' libusb.o(.text+0x4f4): In function `libusb_get_report': : undefined reference to `usb_control_msg' libusb.o(.text+0x531): In function `libusb_set_report': : undefined reference to `usb_control_msg' libusb.o(.text+0x553): In function `libusb_get_string': : undefined reference to `usb_get_string_simple' libusb.o(.text+0x5b8): In function `libusb_close': : undefined reference to `usb_release_interface' libusb.o(.text+0x5c6): In...

...68 B - Bus: 002 Trying to match device Device matches Detected a UPS: Tripp Lite /TRIPP LITE UPS send_to_all: SETINFO ups.vendorid "09ae" send_to_all: SETINFO ups.productid "1008" send_cmd(msg_len=3, type='W') send_cmd: sending 3a 57 00 a8 0d 00 00 00 '.W......' libusb_set_report() returned -32 instead of 8 Could not reset watchdog. Please check andsee if usbhid-ups(8) works with this UPS. ----------------------------------------------------------------------------------------------------------- -------------------------------------------------------------------------------...

...6f 09 6e b1 82 95 01 b1 03 09 65 b1 82 09 6d 95 01 b1 03 09 67 09 62 95 02 b1 82 95 06 b1 03 95 01 09 72 b1 82 95 01 b1 03 c0 c0 05 84 09 18 a1 02 09 20 a1 02 75 10 95 01 15 00 27 ff ff 00 00 85 17 09 55 b1 82 c0 c0 c0 Detected a UPS: Tripp Lite /TRIPP LITE UPS send_cmd(msg_len=3, type='W') libusb_set_report() returned -32 instead of 8 Could not reset watchdog. Please send model information to nut-upsdev mailing list -- --------------------------------------------------------------- Mike Greaves ITL Circuits (905) 475-6658 ext. 119 ---------------------------------------------------------------