Wayne Thomas
2011-Jun-02 18:42 UTC
[Nut-upsuser] [HCL] Hardware Compatibility List - PowerWalker VI 850 LCD
Hello list, just a quick email to report that the following UPS was supported (mostly) out of the box: Model: PowerWalker VI 850 LCD Driver: blazer_usb upsc Output (please note I have manually populated the high and low voltages): battery.charge: 100 battery.voltage: 13.50 battery.voltage.high: 13.5 battery.voltage.low: 10 battery.voltage.nominal: 12.0 beeper.status: enabled 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: 3.0 input.frequency: 50.1 input.frequency.nominal: 50 input.voltage: 228.2 input.voltage.fault: 228.2 input.voltage.nominal: 220 output.voltage: 228.2 ups.delay.shutdown: 30 ups.delay.start: 180 ups.load: 63 ups.productid: 5161 ups.status: OL ups.type: offline / line interactive ups.vendorid: 0665 upsrw Output (I can confirm that the username and password were correct): $ upsrw -s beeper.status=disabled myups Username (backend): xxxxxxx Password: Unexpected response from upsd: ERR ACCESS-DENIED upscmd Output (as above username and password were correct): upscmd myups beeper.toggle Username (backend): xxxxxxx Password: Unexpected response from upsd: ERR ACCESS-DENIED Shutdown testing sequence: Sorry, I don't have any logs (and am reluctant to shutdown now) but I can confirm it worked as designed. Internet Link (its the one in the middle) http://www.powerwalker.com/line-interactive.asp?VA_level=850 Please note, I am not subscribed to the list so if you have any questions please reply direct. Cheers Wayne -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20110602/8a77a7c8/attachment.html>
Arnaud Quette
2011-Jun-04 10:24 UTC
[Nut-upsuser] [HCL] Hardware Compatibility List - PowerWalker VI 850 LCD
Hi Wayne, 2011/6/2 Wayne Thomas <waynethomas69 at gmail.com>> Hello list, > just a quick email to report that the following UPS was supported (mostly) > out of the box: > > Model: PowerWalker VI 850 LCD >thanks, applied to the trunk (r3026)> Driver: blazer_usb > > upsc Output (please note I have manually populated the high and low > voltages): > battery.charge: 100 > battery.voltage: 13.50 > battery.voltage.high: 13.5 > battery.voltage.low: 10 > battery.voltage.nominal: 12.0 > beeper.status: enabled > 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: 3.0 > input.frequency: 50.1 > input.frequency.nominal: 50 > input.voltage: 228.2 > input.voltage.fault: 228.2 > input.voltage.nominal: 220 > output.voltage: 228.2 > ups.delay.shutdown: 30 > ups.delay.start: 180 > ups.load: 63 > ups.productid: 5161 > ups.status: OL > ups.type: offline / line interactive > ups.vendorid: 0665 > > upsrw Output (I can confirm that the username and password were correct): >as per http://www.networkupstools.org/docs/man/upsd.users.html, have you also set 'actions' and 'instcmds'?> $ upsrw -s beeper.status=disabled myups > Username (backend): xxxxxxx > Password: > Unexpected response from upsd: ERR ACCESS-DENIED > > upscmd Output (as above username and password were correct): > upscmd myups beeper.toggle > Username (backend): xxxxxxx > Password: > Unexpected response from upsd: ERR ACCESS-DENIED > > Shutdown testing sequence: > Sorry, I don't have any logs (and am reluctant to shutdown now) but I can > confirm it worked as designed. >including the UPS being powered off? Internet Link (its the one in the middle)> http://www.powerwalker.com/line-interactive.asp?VA_level=850 >note that, as per the menu entry in the above link (top of the page), you have a 8500VA ;-) thanks for your report. 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20110604/86edc948/attachment.html>
Arnaud Quette
2011-Jun-12 17:12 UTC
[Nut-upsuser] [HCL] Hardware Compatibility List - PowerWalker VI 850 LCD
(please keep the traffic on the list) 2011/6/4 Wayne Thomas <waynethomas69 at gmail.com>> Hi Arnaud, > >Hi Wayne> as per http://www.networkupstools.org/docs/man/upsd.users.html, have you >> also set 'actions' and 'instcmds'? >> > > Um, no. I do now!!! > > $ upsrw -s beeper.status=disabled myups > Username (backend): upsuser > Password: > Unexpected response from upsd: ERR READONLY > > I'm not sure what settings should work, but the ones I tried all reported > back as being read-only >calling upsrw with no params will give you the list of supported settings. ie: $ upsrw myups> $ upscmd myups beeper.toggle > Username (backend): upsuser > Password: > OK >the same goes for upscmd with the "-l" option> including the UPS being powered off? >> > > I use upssched with three separate scripts when mains power dies (one > immediate, one after 30 seconds, and one when the UPS is critical). Here is > the syslog when I unplugged the ups and plugged it back in a few seconds > later; is this sufficient? > > Jun 4 14:38:07 backend upsmon[30606]: UPS myups at localhost on battery > Jun 4 14:38:07 backend upssched[1557]: Executing command: power-off > Jun 4 14:38:07 backend upssched-cmd: Uh oh, power is off > Jun 4 14:38:09 backend upssched[1579]: Timer daemon started > Jun 4 14:38:09 backend upssched[1579]: New timer: power-still-off (30 > seconds) > Jun 4 14:38:12 backend upsmon[30606]: UPS myups at localhost on line power > Jun 4 14:38:12 backend upssched[1579]: Cancelling timer: power-still-off > Jun 4 14:38:12 backend upssched[1594]: Executing command: power-on > Jun 4 14:38:12 backend upssched-cmd: Yay, power is back on > Jun 4 14:38:25 backend upssched[1579]: Timer queue empty, exiting >knowing that your UPS support the "low battery" notion is enough. the rest is on the NUT side. cheers, Arno -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20110612/03c3b0bf/attachment-0001.html>