[Nut-upsdev] regarding Asium P700

John Hart
Mon, 21 Sep 2015 00:26:46 -0000

No, the Battery Temp does not change. It is always 25C.
I don't know why the ups.delay.start is that high.  Is that user
configurable?
Yes, I have tested the automatic shutdown.  Works well.
Yes, the instant commands work, at least those I feel comfortable testing.
Battery test work fine.
I have not enable the write to variables.  Did not know that it might be
necessary.

John Hart


----- Forwarded Message -----
*From:* Charles Lepple <clepple at gmail.com>
*To:* john hart <jsamcr at yahoo.com>
*Cc:* "nut-upsdev at lists.alioth.debian.org" <
nut-upsdev at lists.alioth.debian.org>
*Sent:* Sunday, September 20, 2015 2:52 PM
*Subject:* Re: [Nut-upsdev] [HCL] Asium P700

On Sep 19, 2015, at 10:08 AM, john hart <jsamcr at yahoo.com>
wrote:
>
> I have been using the Asium P700 for about 4 months, running Debian
Wheezy 7.9,  and would like to submit the UPS for inclusion in your list of
supported devices.
> ASIUM P700 (650VA/360W)
> <http://www.asiumpower.com/Asium-ASIUM-P700-650VA-360W/dp/B009SMEQ10>
[...]
> Not sure what the procedure might be but I am sending the dump from upsc :
>
> battery.charge: 100
> battery.voltage: 13.50
> battery.voltage.high: 13.00
> battery.voltage.low: 10.40
> battery.voltage.nominal: 12.0
> device.type: ups
> driver.name: blazer_usb
> driver.parameter.offdelay: 30
> driver.parameter.ondelay: 40
> driver.parameter.pollinterval: 2
> driver.parameter.port: auto
> driver.parameter.vendorid: 0665
> driver.version: 2.6.4
> driver.version.internal: 0.08
> input.current.nominal: 5.0
> input.frequency: 60.4
> input.frequency.nominal: 60
> input.voltage: 117.0
> input.voltage.fault: 117.0
> input.voltage.nominal: 120
> output.voltage: 117.0
> ups.beeper.status: enabled
> ups.delay.shutdown: 30
> ups.delay.start: 2400
> ups.load: 25
> ups.productid: 5161
> ups.status: OL
> ups.temperature: 25.0
> ups.type: offline / line interactive
> ups.vendorid: 0665
>
> I know that not all UPS devices can be tested and reviewed by your team,
and not all devices can be included in the list.  Just thought I would give
it a shot.

Thanks for the info. The Hardware Compatibility List (HCL) and Device Dump
Library (DDL) are both filled with user-submitted information, so we rely
on reports like this.

Before we add this, do all of the values from `upsc` look correct to you?
In particular, does `ups.temperature` ever change from 25.0? Also, the
value for ups.delay.start (2400) looks high for the requested value (40).
Have you done any shutdown testing with this UPS? Do the read/write
variables and instant commands (if any) work properly?

Reference: http://www.networkupstools.org/stable-hcl.html#footnotes and
http://www.networkupstools.org/ddl/#report-a-bad-value

Note that in later versions of NUT, the driver for your UPS will be
nutdrv_qx (a superset of several Q*-protocol drivers, including blazer_usb).

Another thing: we recently discovered that some Yahoo anti-spam measures
result in mass unsubscription of non-Yahoo email users of these lists.
Please consider submitting future information from a non-Yahoo email
address, or create an issue on the NUT Github project:
https://github.com/networkupstools/nut/issues
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20150920/6a030538/attachment.html>