search for: 1500sd

Displaying 5 results from an estimated 5 matches for "1500sd".

Did you mean: 1500s
2016 Sep 16
1
blazer_usb MEC0002 problem Fry's Electronics (Turbo-X) [HID PDC?]
> that string shows up here, among other places: > > https://github.com/networkupstools/nut/blob/master/drivers/nutdrv_qx.c#L764 > > but if the upsilon screen isn't showing many values, I'm not sure if that > version is going to help. Are there any other settings to select a > different model or protocol? Here is the output of #/etc/upsilon/upsilon config hope
2016 Sep 15
2
blazer_usb MEC0002 problem Fry's Electronics (Turbo-X) [HID PDC?]
...wed a text screen with most of the info unavailable. So I can't tell if it is really working. Hope that help you decipher this UPS Thank you for your support so far Regards Vassilis Virvilis -------------- next part -------------- A non-text attachment was scrubbed... Name: ups-turbo-x-1500sd.log.gz Type: application/gzip Size: 5818 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20160915/e4a11a98/attachment.bin>
2016 Sep 08
2
blazer_usb MEC0002 problem Fry's Electronics (Turbo-X) [HID PDC?]
> You could also try adding "-x usb_set_altinterface" to the command line > (or adding it to ups.conf). The lsusb output implies that the only valid > setting is 0 (bAlternateSetting), but it might need to be set explicitly. I checked with -x usb_set_altinterface and it says nut_usb_set_altinterface: usb_set_altinterface() should not be necessary - please email the
2016 Sep 08
2
blazer_usb MEC0002 problem Fry's Electronics (Turbo-X)
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'...
2016 Sep 08
2
blazer_usb MEC0002 problem Fry's Electronics (Turbo-X)
...s 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 concatenated) 0.000000 debug level is '3' 0.000550 upsdrv_initups... 0.333611 Checking device (067B/2305) (008/006) 0.333663 - VendorID: 067b 0...