Nut upsuser - Jun 2017 - [HCL] Cyber Power Systems CP1500AVRLCDa supported by usbhid-ups

On 5/21/2017 10:39 AM, Charles Lepple wrote:
> Mike,
> 
> Thanks for the info. I have enough to add an entry to the DDL, but I have a
few more questions inline.
> 
> On May 14, 2017, at 1:21 PM, Mike wrote:
>>
>> [updated]
>>
>> OpenBSD 6.1/amd64
>> NUT 2.7.4p0 (from OpenBSD package)
>>
>>
>> Results of upsc:
>>
>> battery.charge: 100
>> battery.charge.low: 10
>> battery.charge.warning: 20
>> battery.mfr.date: CPS
> 
> Let me know if you're interested in figuring out if the
battery.mfr.date value is stored somewhere else.
Of course.   The UPS is in production (ie., powering the servers in my
house), so it may be a few days before I can ~play~.  Let me know what I
need to do.
> 
>> device.mfr: CPS
>> device.model: CP1500AVRLCDa
>> device.serial: CTHGN200xxxx
> ...
>> driver.version: 2.7.4
>> driver.version.data: CyberPower HID 0.4
>> driver.version.internal: 0.41
>> input.voltage: 121.0
>> input.voltage.nominal: 120
>> output.voltage: 137.0
> 
> The output voltage seems a little high. Is this UPS configured to boost
voltage? Do either the input or output voltages match the values on the LCD?
The LCD values look fine (usually 118 to 121 volts).   I just measured
the output voltage at the UPS outlets (using an HP 974a DVM), it was
118.9 volts.  The voltage from the wall outlet going into the UPS was
also 118.9 volts.  While I was reading those values, the output.voltage
value was 142.

I didn't change any configuration from the factory default values,
though the UPS blurbs do mention "voltage boosting."

It's looking as if the output.voltage value is not correct.  ;)
> 
>> Results of upscmd -l
> 
> Thanks, I'll add the timer info to the documentation:
https://github.com/networkupstools/nut/issues/432
> 
> Also, what about the output of "upsrw"?
Results from upsrw:

[battery.charge.low]
Remaining battery level when UPS switches to LB (percent)
Type: STRING
Maximum length: 10
Value: 10

[battery.runtime.low]
Remaining battery runtime when UPS switches to LB (seconds)
Type: STRING
Maximum length: 10
Value: 300

[ups.delay.shutdown]
Interval to wait after shutdown with delay command (seconds)
Type: STRING
Maximum length: 10
Value: 20

[ups.delay.start]
Interval to wait before (re)starting the load (seconds)
Type: STRING
Maximum length: 10
Value: 30

On May 22, 2017, at 11:13 AM, Mike <the.lists at mgm51.com>
wrote:
> 
> On 5/21/2017 10:39 AM, Charles Lepple wrote:
>> 
>> Let me know if you're interested in figuring out if the
battery.mfr.date value is stored somewhere else.
> 
> Of course.   The UPS is in production (ie., powering the servers in my
> house), so it may be a few days before I can ~play~.  Let me know what I
> need to do.
Apologies for the delay - busy week, and a holiday weekend surrounded by fewer
keyboards than normal.

The units supported by the usbhid-ups driver are usually solid enough that you
can do preliminary debugging without manually shutting everything down (or
worrying that stray commands will trigger an inadvertent shutdown). You would
just have a few gaps in the logs, if you are recording the values continuously.
Plus, there's the obvious advice not to do this when the weather forecast is
looking grim.

Even though the CPS sub-driver has been written already, I would like to take a
look at the raw "explore" mode output:

http://new.networkupstools.org/docs/developer-guide.chunked/ar01s04.html#_writing_a_subdriver

The usual recommendations apply (let it run for 30 seconds, and gzip the logs),
but the serial numbers might be labeled differently - so perhaps grep for the
first few characters, rather than relying on a "serial" label.
> 
>> 
>>> device.mfr: CPS
>>> device.model: CP1500AVRLCDa
>>> device.serial: CTHGN200xxxx
>> ...
>>> driver.version: 2.7.4
>>> driver.version.data: CyberPower HID 0.4
>>> driver.version.internal: 0.41
>>> input.voltage: 121.0
>>> input.voltage.nominal: 120
>>> output.voltage: 137.0
>> 
>> The output voltage seems a little high. Is this UPS configured to boost
voltage? Do either the input or output voltages match the values on the LCD?
> 
> The LCD values look fine (usually 118 to 121 volts).   I just measured
> the output voltage at the UPS outlets (using an HP 974a DVM), it was
> 118.9 volts.  The voltage from the wall outlet going into the UPS was
> also 118.9 volts.  While I was reading those values, the output.voltage
> value was 142.
> 
> I didn't change any configuration from the factory default values,
> though the UPS blurbs do mention "voltage boosting."
> 
> It's looking as if the output.voltage value is not correct.  ;)
Found this thread:

https://github.com/networkupstools/nut/issues/337#issuecomment-257284089

Unfortunately, I am not seeing a common factor here.

If it were the input voltage, I would recommend experimenting with a variac, but
you are probably not going to see much of a range on the output before the
buck/boost circuits kick in. So it's still an option, but it might not be
worth the trouble for an UPS in service (or if you don't have a variac
handy).
> Results from upsrw:
Thanks! Committed (though the website has not yet been rebuilt):
https://github.com/networkupstools/nut-ddl/commit/8268252b294

On 5/30/2017 10:47 PM, Charles Lepple wrote:
> On May 22, 2017, at 11:13 AM, Mike <the.lists at mgm51.com> wrote:
>>
>> On 5/21/2017 10:39 AM, Charles Lepple wrote:
[snip]
> 
> The units supported by the usbhid-ups driver are usually solid enough that
you can do preliminary debugging without manually shutting everything down (or
worrying that stray commands will trigger an inadvertent shutdown). You would
just have a few gaps in the logs, if you are recording the values continuously.
Plus, there's the obvious advice not to do this when the weather forecast is
looking grim.


I have another CyberPower UPS I can swap in for a while so that I can
play with the CP1500AVRLCDa, the stand-in's batteries won't last as
long, but I'll be home so that won't be a problem.

I do have a variac.  Probably the last time I used it was somewhere
around 30-35 years ago.

 :)


I have some time this coming weekend, so I'll shoot for that.

On 5/30/2017 10:47 PM, Charles Lepple wrote:
> On May 22, 2017, at 11:13 AM, Mike <the.lists at mgm51.com> wrote:
>>
>> On 5/21/2017 10:39 AM, Charles Lepple wrote:
[snip]
> Even though the CPS sub-driver has been written already, I would like to
take a look at the raw "explore" mode output:
> 
>
http://new.networkupstools.org/docs/developer-guide.chunked/ar01s04.html#_writing_a_subdriver

When I ran:

drivers/usbhid-ups -DD -u root -x explore -x vendorid=0764 auto

it balked at "auto":

Network UPS Tools - Generic HID driver 0.41 (2.7.4)
USB communication driver 0.33
   0.000000     Error: too many non-option arguments. Try -h for help.


so I added a -a parameter to point to the ups name configured in
ups.conf, and that worked.  The output from that command is zipped and
attached.


[snip]
> 
> If it were the input voltage, I would recommend experimenting with a
variac, but you are probably not going to see much of a range on the output
before the buck/boost circuits kick in. So it's still an option, but it
might not be worth the trouble for an UPS in service (or if you don't have a
variac handy).

Here's the results of the varying voltage tests:

input   output       UPS        output.voltage  input.voltage
to UPS  from UPS     display
119.9   120.4        119            136.0          120.0
115.2   115.6        114            138.0          114.0
127.3   128.0        127            136.0          127.0
135.5   136.4        135            136.0          135.0
100.4   100.5        100            140.0          100.0
 94.9   105.1         95            137.0           96.0
120.7   121.1        120            142.0          118.0
140.8   122.8        139            136.0          139.0
121.7   122.1        121            136.0          120.0


Notes:

1) the input to UPS was measured by a Kill-A-Watt device, the output
from UPS was measured by a HP 974a DVM.  Prior to these tests, I ran
them from the same source, and they tracked pretty well, with the 974a
usually about 0.5 volts higher than the Kill-A-Watt.  For the purpose of
this test, I figured that would be OK.

2) output.voltage and input.voltage were from the upsc command

3) the readings were taken about 30 to 45 seconds apart.  That's how
long it took me to set a new voltage on the Powerstat.

4) when I went down to 95 volts, the "AVR" kicked in to boost the
voltage without going to battery.  This was indicated by a "click"
from
the UPS and an indication on the UPS display.

5) When I went up to 140 volts, the UPS switched over to batteries.

Hope this helps.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ups-test.zip
Type: application/octet-stream
Size: 2576 bytes
Desc: not available
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170603/fad12f74/attachment.obj>