Nut upsuser - Jan 2013 - Eaton 5PX1500RT

Windows 7 x64
NUT 2.6.5-4
Eaton 5PX1500RT

Using explore did not yield any additional output. This UPS is on the 
compatibility list, so hopefully not a big deal. I double-checked that 
the 3S still works with the same USB cable.

I'll check mge-shut over serial next.

Regards.
-------------- next part --------------
Network UPS Tools - Generic HID driver 0.37 (2.6.5-3780M)
USB communication driver 0.31
   0.000000	debug level is '5'
   0.000000	upsdrv_initups...
   0.000000	Checking device (0463/FFFF) (bus-0/\\.\libusb0-0001--0x0463-0xffff)
   0.281250	- VendorID: 0463
   0.281250	- ProductID: ffff
   0.281250	- Manufacturer: EATON
   0.281250	- Product: Eaton 5PX
   0.281250	- Serial Number: G090C25071
   0.281250	- Bus: bus-0
   0.281250	Trying to match device
   0.281250	Device matches
   0.343750	HID descriptor, method 1: (9 bytes) => 09 21 10 01 21 01 22 14 0a
   0.343750	i=0, extra[i]=09, extra[i+1]=21
   0.343750	HID descriptor, method 2: (9 bytes) => 09 21 10 01 21 01 22 14 0a
   0.343750	HID descriptor length 2580
   4.343750	Unable to get Report descriptor: No error [The I/O operation has
been aborted because of either a thread exit or an application request. ]
   4.343750	No appropriate HID device found
   4.343750	No matching HID UPS found

Kris Jordan wrote, On 1/10/2013 2:50 PM:
> Windows 7 x64
> NUT 2.6.5-4
> Eaton 5PX1500RT
>
> Using explore did not yield any additional output. This UPS is on the 
> compatibility list, so hopefully not a big deal. I double-checked that 
> the 3S still works with the same USB cable.
>
> I'll check mge-shut over serial next.
Looks like mge-shut is working, even over a USB-serial adapter. I have a 
lot to test, but I'd rather do that with usbhid, unless you think 
mge-shut is preferable for some reason?

I'm not using SSL, but now when I run upsc I get...

"upscli not initialized, force initialisation without SSL configuration
Init SSL without certificate database
Can not connect to localhost in SSL, continue uncrypted"

Something apparently changed in 2.6.5 with SSL.

Regards.