Hi, Just got it working by changing the driver to blazer_usb.
This is the output from upsc. battery.voltage: 27.20 battery.voltage.nominal: 24.0 beeper.status: enabled device.mfr: device.model: PSA device.type: ups driver.name: blazer_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.6.0 driver.version.internal: 0.03 input.current.nominal: 0.0 input.frequency: 50.0 input.frequency.nominal: 50 input.voltage: 242.5 input.voltage.fault: 140.0 input.voltage.nominal: 230 output.voltage: 240.0 ups.delay.shutdown: 30 ups.delay.start: 180 ups.firmware: VT17077Q ups.load: 14 ups.mfr: ups.model: PSA ups.productid: 0000 ups.status: OL ups.temperature: 30.0 ups.type: offline / line interactive ups.vendorid: ffff I don't see the battery level status, does this mean it may not be able to detect the critical battery level? On Sun, Jul 31, 2011 at 2:51 AM, John Huong <[email protected]> wrote: > Sorry about that. Must have missed that out. > > Anyway attached is the output from lsusb -vv -d FFFF:0000 > output.txt > > Does this confirm the blazer_usb type? > > > On Sun, Jul 31, 2011 at 1:40 AM, Arnaud Quette <[email protected]> wrote: >> Hi, >> >> first, please keep the NUT users list copied, and subscribe if necessary. >> >> 2011/7/28 John Huong <[email protected]> >>> >>> Yes just did that. >>> >>> This is the output. >>> >>> Network UPS Tools - Generic HID driver 0.35 (2.6.0) >>> USB communication driver 0.31 >>> 0.000000 send_to_all: SETINFO driver.parameter.port "auto" >>> 0.000377 debug level is '5' >>> 0.001409 upsdrv_initups... >>> 0.177071 Checking device (FFFF/0000) (005/003) >>> 0.177175 - VendorID: ffff >>> 0.177198 - ProductID: 0000 >>> 0.177217 - Manufacturer: unknown >>> 0.177235 - Product: unknown >>> 0.177252 - Serial Number: unknown >>> 0.177270 - Bus: 005 >>> 0.177287 Trying to match device >>> 0.177320 Device does not match - skipping >>> 0.177350 Checking device (1D6B/0001) (005/001) >>> 0.177403 - VendorID: 1d6b >>> 0.177447 - ProductID: 0001 >>> 0.177467 - Manufacturer: unknown >>> 0.177485 - Product: unknown >>> 0.177502 - Serial Number: unknown >>> 0.177521 - Bus: 005 >>> 0.177538 Trying to match device >>> 0.177558 Device does not match - skipping >>> 0.177584 Checking device (1D6B/0001) (004/001) >>> 0.177637 - VendorID: 1d6b >>> 0.177658 - ProductID: 0001 >>> 0.177676 - Manufacturer: unknown >>> 0.177695 - Product: unknown >>> 0.177712 - Serial Number: unknown >>> 0.177730 - Bus: 004 >>> 0.177747 Trying to match device >>> 0.177767 Device does not match - skipping >>> 0.177793 Checking device (1D6B/0001) (003/001) >>> 0.177846 - VendorID: 1d6b >>> 0.177868 - ProductID: 0001 >>> 0.177886 - Manufacturer: unknown >>> 0.177904 - Product: unknown >>> 0.177921 - Serial Number: unknown >>> 0.177939 - Bus: 003 >>> 0.177956 Trying to match device >>> 0.177976 Device does not match - skipping >>> 0.178002 Checking device (1D6B/0001) (002/001) >>> 0.178054 - VendorID: 1d6b >>> 0.178075 - ProductID: 0001 >>> 0.178093 - Manufacturer: unknown >>> 0.178112 - Product: unknown >>> 0.178129 - Serial Number: unknown >>> 0.178147 - Bus: 002 >>> 0.178164 Trying to match device >>> 0.178184 Device does not match - skipping >>> 0.178210 Checking device (1D6B/0002) (001/001) >>> 0.178261 - VendorID: 1d6b >>> 0.178282 - ProductID: 0002 >>> 0.178300 - Manufacturer: unknown >>> 0.178318 - Product: unknown >>> 0.178336 - Serial Number: unknown >>> 0.178354 - Bus: 001 >>> 0.178371 Trying to match device >>> 0.178391 Device does not match - skipping >>> 0.178415 No appropriate HID device found >>> 0.178440 No matching HID UPS found >> >> Liebert USB vendor ID is 06D5, which I don't see above! >> I'd first like to see an "lsusb -vvv -d<VID>:<PID> >> >> my opinion is that your device is FFFF:0000 (not hard to guess), which is a >> blazer_usb supported device. >> in that case, you will want to read the manpage: >> http://www.networkupstools.org/docs/man/blazer.html >> >> please report back your testing results, including upsc/upsrw/upscmd output, >> and shutdown sequence. >> >> >>> On Thu, Jul 28, 2011 at 8:10 PM, Arnaud Quette <[email protected]> >>> wrote: >>> > Hi John >>> > >>> > 2011/7/28 John Huong <[email protected]> >>> >> >>> >> Hi, >>> >> >>> >> Does anyone have a similar configuration or have used the same model >>> >> with Ubuntu before with success? >>> >> >>> >> Strange my system can't seem to detect the UPS and I can see >>> >> >>> >> usbhid 2-1.1:1.0: couldn't find an input interrupt endpoint >>> >> >>> >> in dmesg when I plug in the UPS. >>> >> >>> >> Hope can share your experience on this. >>> > >>> > this is probably a warning and not an error, since interrupt endpoint >>> > are >>> > similar to SNMP traps (ie just a complementary channel, where the UPS >>> > can >>> > send info without any request from the PC) >>> > >>> > have you tried running usbhid-ups and check if it works? >>> > trying in debug mode (ie /lib/nut/usbhid-ups -DDDDD -a <ups_name>) is a >>> > good >>> > option. >>> > >>> > cheers, >>> > Arnaud >> >> cheers, >> Arnaud >> -- >> Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com >> Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ >> Debian Developer - http://www.debian.org >> Free Software Developer - http://arnaud.quette.free.fr/ >> >> > _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
