Nut upsdev - Oct 2012 - [HCL] Apollo 1085VC Supported by blazer_usb

As per request by Arnaud in the users list

Device manufacturer: Apollo
Device name: 1085VC (Retailer's product page:
http://shop.esquire.co.za/ProductDescription.aspx?id=583072)

upsc on mains power:
> $ upsc apollo
> battery.voltage: 13.50
> battery.voltage.nominal: 12.0
> beeper.status: enabled
> device.mfr:
> device.model:
> device.type: ups
> driver.name: blazer_usb
> driver.parameter.pollinterval: 2
> driver.parameter.port: auto
> driver.version: 2.6.3
> driver.version.internal: 0.04
> input.current.nominal: 3.0
> input.frequency: 50.0
> input.frequency.nominal: 50
> input.voltage: 225.0
> input.voltage.fault: 225.0
> input.voltage.nominal: 230
> output.voltage: 225.0
> ups.delay.shutdown: 30
> ups.delay.start: 180
> ups.firmware: B1.12_APFB
> ups.load: 12
> ups.mfr:
> ups.model:
> ups.productid: 5161
> ups.status: OL
> ups.temperature: 31.0
> ups.type: offline / line interactive
> ups.vendorid: 0665
>
After killing power:
> Broadcast Message from nut at xxxx
>
>         (somewhere) at 10:01 ...
>


UPS apollo at localhost on battery

upsc on battery power:
> $ upsc apollo
> battery.voltage: 12.30
> battery.voltage.nominal: 12.0
> beeper.status: enabled
> device.mfr:
> device.model:
> device.type: ups
> driver.name: blazer_usb
> driver.parameter.pollinterval: 2
> driver.parameter.port: auto
> driver.version: 2.6.3
> driver.version.internal: 0.04
> input.current.nominal: 3.0
> input.frequency: 0.0
> input.frequency.nominal: 50
> input.voltage: 0.0
> input.voltage.fault: 0.0
> input.voltage.nominal: 230
> output.voltage: 230.0
> ups.delay.shutdown: 30
> ups.delay.start: 180
> ups.firmware: B1.12_APFB
> ups.load: 12
> ups.mfr:
> ups.model:
> ups.productid: 5161
> ups.status: OB
> ups.temperature: 31.0
> ups.type: offline / line interactive
> ups.vendorid: 0665


Shutdown sequence (test)
> $ sudo upsdrvctl -t shutdown
> Network UPS Tools - UPS driver controller 2.6.3
> *** Testing mode: not calling exec/kill
>    0.000000
> If you're not a NUT core developer, chances are that you're told to
enable
> debugging
> to see why a driver isn't working for you. We're sorry for the
confusion,
> but this is
> the 'upsdrvctl' wrapper, not the driver you're interested in.
> Below you'll find one or more lines starting with 'exec:'
followed by an
> absolute
> path to the driver binary and some command line option. This is what the
> driver
> starts and you need to copy and paste that line and append the debug flags
> to that
> line (less the 'exec:' prefix).
>    0.000380 Shutdown UPS: apollo
>    0.000419 exec:  /lib/nut/blazer_usb -a apollo -k

Forced shutdown:
> $ sudo upsmon -c fsd
> Network UPS Tools upsmon 2.6.3
>
>
> Broadcast Message from nut at xxxx
>
>         (somewhere) at 10:27 ...
>
>
>
> UPS apollo at localhost: forced shutdown in progress
>
>
>
>
>
> Broadcast Message from nut at xxxx?u?
>
>         (somewhere) at 10:28 ...
>
>
>
> Executing automatic power-fail shutdown
>
>
>
>
>
>
>
> Broadcast Message from nut at xxxx?{?
>
>         (somewhere) at 10:28 ...
>
>
>
> Auto logout and shutdown proceeding
>
>
>
>
>
> Broadcast Message from nut at xxxx
>
>         (somewhere) at 10:28 ...
>
>
>
> Executing automatic power-fail shutdown
>
>
>
>
>
>
>
> Broadcast Message from nut at xxxx
>
>         (somewhere) at 10:28 ...
>
>
>
> Auto logout and shutdown proceeding
>
>
>
> Broadcast message from root at xxxx
> (unknown) at 10:28 ...
> The system is going down for halt NOW!
> Broadcast message from root at xxxx
> (unknown) at 10:28 ...
> The system is going down for halt NOW!

UPS Switched off
> Broadcast Message from nut at xxxx
>
>         (somewhere) at 10:32 ...
>
>
>
> UPS apollo at localhost on battery
> Broadcast Message from nut at xxxx
>
>         (somewhere) at 11:03 ...
>
>
>
> UPS apollo at localhost battery is low
>
>
>
>
>
> Broadcast Message from nut at xxxx
>
>         (somewhere) at 11:03 ...
>
>
>
> Executing automatic power-fail shutdown
>
>
>
>
>
>
>
> Broadcast Message from nut at xxxx
>
>         (somewhere) at 11:03 ...
>
>
>
> Auto logout and shutdown proceeding
>
>
>
> Broadcast message from root at xxxx
> (unknown) at 11:03 ...
>

Shutdown successfully

Cheers
Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20121019/844842dc/attachment-0001.html>

Mike

2012/10/19 Mike Raath <raathm at gmail.com>
> As per request by Arnaud in the users list
>
> Device manufacturer: Apollo
> Device name: 1085VC (Retailer's product page:
> http://shop.esquire.co.za/ProductDescription.aspx?id=583072)
> (...)
>
as per the page, the device name is actually " Apollo 850VA"
"1085C" is a stock code (manufacturer product ref.)

I've just committed the following entry to the HCL:
trac.networkupstools.org/projects/nut/changeset/3764

thanks for your feedback.

cheers,
Arnaud
-- 
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.fr
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20121019/c0bfe77e/attachment.html>