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

[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
battery.runtime: 2902
battery.runtime.low: 300
battery.type: PbAcid
battery.voltage: 26.9
battery.voltage.nominal: 24
device.mfr: CPS
device.model: CP1500AVRLCDa
device.serial: CTHGN200xxxx
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.product: CP1500AVRLCDa
driver.parameter.productid: 0501
driver.parameter.serial: CTHGN200xxxx
driver.parameter.synchronous: no
driver.parameter.vendorid: 0764
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
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.delay.start: 30
ups.load: 18
ups.mfr: CPS
ups.model: CP1500AVRLCDa
ups.productid: 0501
ups.realpower.nominal: 900
ups.serial: CTHGN200xxxx
ups.status: OL
ups.test.result: No test initiated
ups.timer.shutdown: -60
ups.timer.start: -60
ups.vendorid: 0764



Results of upscmd -l

beeper.disable - Disable the UPS beeper
beeper.enable - Enable the UPS beeper
beeper.mute - Temporarily mute the UPS beeper
beeper.off - Obsolete (use beeper.disable or beeper.mute)
beeper.on - Obsolete (use beeper.enable)
load.off - Turn off the load immediately
load.off.delay - Turn off the load with a delay (seconds)
load.on - Turn on the load immediately
load.on.delay - Turn on the load with a delay (seconds)
shutdown.return - Turn off the load and return when power is back
shutdown.stayoff - Turn off the load and remain off
shutdown.stop - Stop a shutdown in progress
test.battery.start.deep - Start a deep battery test
test.battery.start.quick - Start a quick battery test
test.battery.stop - Stop the battery test



Note that the load.off delay is specified in seconds, but internally it
is divided by 60, using integer division, to get the number of minutes.
I said the following in a prior message about a different Cyber Power
UPS model:

==When I specify a 59 second delay on the command line, the UPS shuts off
immediately.

  59 second delay specified - immediate shutoff
  60 second delay specified - exactly one minute delay, then shutoff
  80 second delay specified - exactly one minute delay, then shutoff
 115 second delay specified - exactly one minute delay, then shutoff
 128 second delay specified - exactly two minute delay, then shutoff

So if I had to guess, I would offer that the UPS is doing an integer
divide by 60 on the number of seconds given by the command.  That is why
the request for a 59 second delay resulted in no delay at all.
==
I see the same behavior with this model.



The following command excerpts from the upssched.conf file work as expected:

AT LOWBATT ups2 at 127.0.0.1 START-TIMER  ups2-lowbattwarn       1
AT ONBATT  ups2 at 127.0.0.1 START-TIMER  ups2-onbatt-early     60
AT ONBATT  ups2 at 127.0.0.1 START-TIMER  ups2-onbatt-final    180
AT ONBATT  ups2 at 127.0.0.1 EXECUTE      ups2-start-batt
AT ONLINE  ups2 at 127.0.0.1 CANCEL-TIMER ups2-onbatt-early
AT ONLINE  ups2 at 127.0.0.1 CANCEL-TIMER ups2-onbatt-final
AT ONLINE  ups2 at 127.0.0.1 EXECUTE      ups2-end-batt

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.
> 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?
> 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"?

-- 
Charles Lepple
clepple at gmail

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