NUT can't properly access OMNI1500LCDT

Status
Not open for further replies.

Tsaukpaetra

Patron
Joined
Jan 7, 2014
Messages
215
For some reason, I can't get NUT to initialize communications with my UPS.
The debug log says it can't get a HID or Report descriptor:
Code:
   0.009457     Checking device (09AE/3016) (/dev/usb//dev/ugen1.3)
   0.032819     - VendorID: 09ae
   0.032824     - ProductID: 3016
   0.032826     - Manufacturer: Tripp Lite
   0.032828     - Product: TRIPP LITE UPS
   0.032830     - Serial Number: unknown
   0.032832     - Bus: /dev/usb
   0.032833     Trying to match device
   0.032841     Device matches
   0.033593     Unable to get HID descriptor (Unknown error)
   0.033608     HID descriptor, method 2: (9 bytes) => 09 21 11 01 00 01 22 6e 03
   0.033614     HID descriptor length 878
   0.034236     Unable to get Report descriptor: Input/output error


So even though it knows the UPS is correct, it can't talk to it for some reason. Someone else mentioned the dev/ugen* files should be writable by whichever user is running nut, so I tried making those links world writable temporarily (with no effect).

Any ideas? (I should probably mention I'm currently on FreeNAS-9.2.2-ALPHA-a0adc15-x64)
 

Tsaukpaetra

Patron
Joined
Jan 7, 2014
Messages
215
Yep, it's supported by usbhid-ups, protocol 3016 if I recall correctly.
Actually, nut wouldn't acknowledge the ups at all if it didn't support it... (no match)
 

Tsaukpaetra

Patron
Joined
Jan 7, 2014
Messages
215
Actually, I think this UPS was working for me before the upgrade to the latest nightly, which was what prompted me to ask. ;)

Here's a debug log from a system I plugged the UPS into just now that's still running FreeNAS-9.2.1.3-RELEASE-x86 (dc0c46b)
http://pastebin.com/aq8Vjnae
Code:
storagesrv1# ./usbhid-ups -a ups
 
Network UPS Tools - Generic HID driver 0.38 (2.7.1)
 
USB communication driver 0.32
 
Using subdriver: TrippLite HID 0.81
 
D

dlavigne

Guest
In that case, please create a bug report at bugs.freenas.org and post the issue number here. Include both of those outputs in the report.
 
Status
Not open for further replies.
Top