search for: turbox1500

...10) > doesn't. > From the lsusb descriptor output, the 1500 seems to implement the HID Power Device Class (PDC) spec - so it might be possible to adapt usbhid-ups to work with it. What happens if you run the driver in "explore" mode? Something like the following: # ups.conf [turbox1500] driver = usbhid-ups port = auto vendorid = 0001 $ /path/to/usbhid-ups -x explore -a turbox1500 -DDD (Check your package manager for the path to usbhid-ups, or look at the output of "upsdrvctl start" in debug mode.)

Hi, I have two ups (Turbo-X 1000SD, Turbo-X 1500SD). The both report themselves as # lsusb Bus 008 Device 002: ID 0001:0000 Fry's Electronics The are produced by MEC and report MEC0002 as product (although the working one report it in dmesg but not in lsusb) The 1000 (bcdUSB 1.00) works with blazer_usb while the 1500 (bcdUSB 1.10) doesn't. I am attaching lsusb and blazer_urb output

...7.4-3 amd64 network UPS tools - clients ii nut-server 2.7.4-3 amd64 network UPS tools - core system [snip] > What happens if you run the driver in "explore" mode? Something like the > following: [snip] > $ /path/to/usbhid-ups -x explore -a turbox1500 -DDD > [snip] I added in /etc/nut/ups.conf [turbo-x] driver = usbhid-ups port = auto vendorid = 0001 productid = 0000 desc = "TURBO-X UPS-1500SD" and run # /lib/nut/usbhid-ups -DDD -x explore -a turbo-x 2>&1 | tee > delme Here is the output (stderr and stdout concate...