I purchased a TrippLite ECO550UPS from Amazon a few days ago thinking I was going to use it for my Windows Media Center HTPC. I've since changed my mind and decided to use Mythbuntu but it I can't get my UPS working with nut. I've tried all of the tripplite drivers and the usbhid-ups driver. The tripplite_usb and usbhid_ups output is listed below. The tripplite and tripplitesu drivers gave me an "Unable to open auto: No such file or directory". My UPS isn't listed in the supported hardware documentation but I thought I might get lucky and one of the drivers work anyways. Are there any plans to add support? I'll happily get whatever information is needed. Thanks! Lindsey ----------------------------------------------------------------------------------------------------------- output from /lib/nut/tripplite_usb -DDDDD -a tripplite_usb -u root -x productid=1008 Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.4.1) Warning: This is an experimental driver. Some features may not function correctly. send_to_all: SETINFO driver.parameter.port "auto" send_to_all: SETINFO driver.parameter.productid "1008" debug level is '5' Checking device (1D6B/0002) (001/001) - VendorID: 1d6b - ProductID: 0002 - Manufacturer: Linux 2.6.28-15-generic ehci_hcd - Product: EHCI Host Controller - Serial Number: 0000:00:04.1 - Bus: 001 Trying to match device Device does not match - skipping Checking device (413C/2001) (002/005) - VendorID: 413c - ProductID: 2001 - Manufacturer: NMB - Product: Dell USB 7HK Keyboard - Serial Number: unknown - Bus: 002 Trying to match device Device does not match - skipping Checking device (413C/1001) (002/004) - VendorID: 413c - ProductID: 1001 - Manufacturer: NMB - Product: Dell USB Keyboard Hub - Serial Number: unknown - Bus: 002 Trying to match device Device does not match - skipping Checking device (15C2/0038) (002/003) - VendorID: 15c2 - ProductID: 0038 - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 002 Trying to match device Device does not match - skipping Checking device (09AE/1008) (002/002) - VendorID: 09ae - ProductID: 1008 - Manufacturer: Tripp Lite - Product: TRIPP LITE UPS - Serial Number: FW-2368 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. ----------------------------------------------------------------------------------------------------------- ----------------------------------------------------------------------------------------------------------- output from /lib/nut/usbhid-ups -DDDDD -a usbhid-ups -u root -x productid=1008 Network UPS Tools - Generic HID driver 0.34 (2.4.1) USB communication driver 0.31 send_to_all: SETINFO driver.parameter.port "auto" send_to_all: SETINFO driver.parameter.productid "1008" debug level is '5' upsdrv_initups... Checking device (1D6B/0002) (001/001) - VendorID: 1d6b - ProductID: 0002 - Manufacturer: Linux 2.6.28-15-generic ehci_hcd - Product: EHCI Host Controller - Serial Number: 0000:00:04.1 - Bus: 001 Trying to match device Device does not match - skipping Checking device (413C/2001) (002/005) - VendorID: 413c - ProductID: 2001 - Manufacturer: NMB - Product: Dell USB 7HK Keyboard - Serial Number: unknown - Bus: 002 Trying to match device Device does not match - skipping Checking device (413C/1001) (002/004) - VendorID: 413c - ProductID: 1001 - Manufacturer: NMB - Product: Dell USB Keyboard Hub - Serial Number: unknown - Bus: 002 Trying to match device Device does not match - skipping Checking device (15C2/0038) (002/003) - VendorID: 15c2 - ProductID: 0038 - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 002 Trying to match device Device does not match - skipping Checking device (09AE/1008) (002/002) - VendorID: 09ae - ProductID: 1008 - Manufacturer: Tripp Lite - Product: TRIPP LITE UPS - Serial Number: FW-2368 B - Bus: 002 Trying to match device This Tripp Lite device (09ae:1008) is not (or perhaps not yet) supported by usbhid-ups. Please make sure you have an up-to-date version of NUT. If this does not fix the problem, try running the driver with the '-x productid=1008' option. Please report your results to the NUT user's mailing list <nut-upsuser at lists.alioth.debian.org>. Device does not match - skipping Checking device (1D6B/0001) (002/001) - VendorID: 1d6b - ProductID: 0001 - Manufacturer: Linux 2.6.28-15-generic ohci_hcd - Product: OHCI Host Controller - Serial Number: 0000:00:04.0 - Bus: 002 Trying to match device Device does not match - skipping No appropriate HID device found No matching HID UPS found ----------------------------------------------------------------------------------------------------------- -- Lindsey Chesnutt
Citeren Lindsey Chesnutt <mrchesnutt op gmail.com>: [...]> This Tripp Lite device (09ae:1008) is not (or perhaps not yet) supported > by usbhid-ups. Please make sure you have an up-to-date version of NUT. If > this does not fix the problem, try running the driver with the > '-x productid=1008' option. Please report your results to the NUT user's > mailing list <nut-upsuser op lists.alioth.debian.org>.You didn't follow the above advice, did you? Best regards, Arjen -- Please keep list traffic on the list
Citeren Lindsey Chesnutt <mrchesnutt op gmail.com>:> I've attached the requested output.Although it didn't make it to the list (because we don't allow attachments larger than 40 kB), I received it directly.> 0.272003 HID descriptor, method 1: (9 bytes) => 09 21 10 01 00 01 22 c9 01 > 0.272075 i=0, extra[i]=09, extra[i+1]=21 > 0.272146 HID descriptor, method 2: (9 bytes) => 09 21 10 01 00 01 22 c9 01 > 0.272212 HID descriptor length 457 > 0.766975 Report Descriptor size = 457That's a fairly short report descriptor for a HID PDC device. It is a valid one though, but it just doesn't have a lot of reports in it. I think we already support most of it as it is and that it doesn't report battery voltage. The only report that comes close is> 0.968349 Entering libusb_get_report > 0.984961 Report[get]: (3 bytes) => 31 b9 04 > 0.985031 PhyMax = 0, PhyMin = 0, LogMax = 65535, LogMin = 0 > 0.985099 Unit = 00000000, UnitExp = 0 > 0.985164 Exponent = 0 > 0.985230 hid_lookup_path: 00840004 -> UPS > 0.985298 hid_lookup_path: 00840024 -> PowerSummary > 0.985365 hid_lookup_path: 00840002 -> PresentStatus > 0.985432 hid_lookup_path: 00840030 -> Voltage > 0.985520 Path: UPS.PowerSummary.PresentStatus.Voltage, Type: > Feature, ReportID: 0x31, Offset: 0, Size: 16, Value: 1209.000000This could be the battery voltage times 100, but in that case the value is surprisingly low (a few tenths of a second before, it reported a fully charged battery). It could also mean the input or output voltage (or something completely unrelated). There is no way to tell without digging deeper into this. The remainder of the reports are either already supported or vendor specific ones. If you're willing to work with us, we might attempt to figure out what these mean. Please let us know if you're able to do so (this will probably require frequent updates of the driver with lot of debugging enabled) and we'll continue on the development mailing list. Best regards, Arjen -- Please keep list traffic on the list