Nut upsuser - Oct 2020 - Can't get CyberPower UPS to work with Raspberry Pi 4

On Monday 26 October 2020 09:01:31 Charles Lepple wrote:
> On Oct 25, 2020, at 11:52 AM, Robert Stocker <kneadtoknow at
gmail.com>
wrote:
> > Init SSL without certificate database
> > battery.charge: 100
> > battery.charge.low: 10
> > battery.charge.warning: 20
> > battery.mfr.date: CPS
> > battery.runtime: 15690
> > battery.runtime.low: 300
> > battery.type: PbAcid
> > battery.voltage: 24.0
> > battery.voltage.nominal: 24
>
> I don't have the citation handy, but I think another user reported
> that the battery.voltage returned by the UPS is a constant 24.0 V,
> regardless of the actual battery voltage.
>
> > device.mfr: CPS
> > device.model: CST135XLU
> > device.serial: CR7EO2003120
> > device.type: ups
> > driver.name: usbhid-ups
> > driver.parameter.pollfreq: 30
> > driver.parameter.pollinterval: 5
> > driver.parameter.port: auto
> > driver.parameter.synchronous: no
> > 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
>
> Given the description on the product page you sent earlier, the UPS is
> likely not providing 137.0 V, but is bypassing the transformer since
> the power is good.
>
> https://www.cyberpowersystems.com/product/ups/battery-backup/cst135xlu
>/
>
> This is another known CyberPower issue, and fixing it properly
> requires making some changes deep in the core USB HID code (that would
> require a lot of testing on other vendors' equipment) for what is
> basically a cosmetic issue:
>
> https://github.com/networkupstools/nut/issues/439
>
> > ups.beeper.status: disabled
> > ups.delay.shutdown: 20
> > ups.delay.start: 30
>
> For these delays, note there seems to be an issue with
> ondelay/ups.delay.start:
>
> https://github.com/networkupstools/nut/issues/625
>
> and rounding of the timers down to the next lower minute:
>
> https://github.com/networkupstools/nut/blob/f3a40e4595c1f18368f89b9af3
>38bfe52dd06846/docs/man/usbhid-ups.txt#L53-L78
>
> so basically I'd recommend testing shutdown extensively.
>
> > ups.load: 4
> > ups.mfr: CPS
> > ups.model: CST135XLU
> > ups.productid: 0501
> > ups.realpower.nominal: 810
> > ups.serial: CR7EO2003120
> > ups.status: OL
> > ups.test.result: No test initiated
> > ups.timer.shutdown: -60
> > ups.timer.start: -60
> > ups.vendorid: 0764
> >
> > If you run systemctl, you should see something like this:
> >
> > And here's what I got from that:
> >
> >  nut-driver.service       loaded active running   Network UPS Tools
> > - power device driver controller nut-monitor.service       loaded
> > active running   Network UPS Tools - power device monitor and
> > shutdown controller nut-server.service       loaded active running  
> > Network UPS Tools - power devices information server
>
I think it may be dependent on thhe ups. I have a 625 WA cyberpower on an 
rpi4, and I believe its more truthfull. Is this helpfull?

pi at rpi4:/media/pi/workspace $ upsc myups
Init SSL without certificate database
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 20
battery.mfr.date: CPS
battery.runtime: 4410
battery.runtime.low: 300
battery.type: PbAcid
battery.voltage: 14.5
battery.voltage.nominal: 12
device.mfr: CPS
device.model: CP625HGa
device.type: ups
driver.name: usbhid-ups
driver.parameter.offdelay: 120
driver.parameter.ondelay: 0
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: no
driver.version: 2.7.4
driver.version.data: CyberPower HID 0.4
driver.version.internal: 0.41
input.transfer.high: 0
input.transfer.low: 0
input.voltage: 124.0
input.voltage.nominal: 120
output.voltage: 124.0
ups.beeper.status: enabled
ups.delay.shutdown: 120
ups.delay.start: 0
ups.load: 8
ups.mfr: CPS
ups.model: CP625HGa
ups.productid: 0501
ups.realpower.nominal: 375
ups.status: OL
ups.test.result: No test initiated
ups.timer.shutdown: -60
ups.timer.start: 0
ups.vendorid: 0764

It has to hold up the pi, but only long enough for the 20kw nat gas fired 
generac outside the back garage door to start, nominally 5 seconds 
according to its -wall broadcasts. It shuts down if unplugged in only a 
couple minutes, but will not accept a longer timeout. It does do the job 
I bought it to do. The pi's draw and the interface card is about 13 or 
14 WA.
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

On Oct 26, 2020, at 9:38 AM, Gene Heskett <gheskett at shentel.net>
wrote:
> 
>>> battery.voltage: 24.0
>>> battery.voltage.nominal: 24
>> 
>> I don't have the citation handy, but I think another user reported
>> that the battery.voltage returned by the UPS is a constant 24.0 V,
>> regardless of the actual battery voltage.
[...]
> I think it may be dependent on thhe ups. I have a 625 WA cyberpower on an 
> rpi4, and I believe its more truthfull. Is this helpfull?
> 
You're right, the lack of a battery voltage sensor isn't true for all
CPS hardware.

I was trying to make the point that the 24.0 V reading is suspect, while
covering the cases where broken scaling means that NUT displays it as 16.0 V.

However, back in January, we discussed the input.transfer.high/.low issue:
https://alioth-lists.debian.net/pipermail/nut-upsuser/2020-January/011668.html

The root cause of that is closer to some of the other CPS issues, like the
"output.voltage: 137.0" that Robert posted.

That upsc dump is useful. For completeness, could you (and Robert) please post
the output of "upsrw myups" and "upscmd -l myups"?

I manually grep through upsc output to find these sorts of things, but some day,
I'd like the DDL[*] to be able to show a table of UPS models and their
supported NUT variables. (Something like a hardware comparison on a vendor
website, but from the perspective of what NUT can read.)

[*] e.g. https://networkupstools.org/ddl/Cyber_Power_Systems/

On Wednesday 28 October 2020 21:32:02 Charles Lepple wrote:
> On Oct 26, 2020, at 9:38 AM, Gene Heskett <gheskett at shentel.net>
wrote:
> >>> battery.voltage: 24.0
> >>> battery.voltage.nominal: 24
> >>
> >> I don't have the citation handy, but I think another user
reported
> >> that the battery.voltage returned by the UPS is a constant 24.0 V,
> >> regardless of the actual battery voltage.
>
> [...]
>
> > I think it may be dependent on thhe ups. I have a 625 WA cyberpower
> > on an rpi4, and I believe its more truthfull. Is this helpfull?
>
> You're right, the lack of a battery voltage sensor isn't true for
all
> CPS hardware.
>
> I was trying to make the point that the 24.0 V reading is suspect,
> while covering the cases where broken scaling means that NUT displays
> it as 16.0 V.
>
> However, back in January, we discussed the input.transfer.high/.low
> issue:
> https://alioth-lists.debian.net/pipermail/nut-upsuser/2020-January/011
>668.html
>
> The root cause of that is closer to some of the other CPS issues, like
> the "output.voltage: 137.0" that Robert posted.
>
> That upsc dump is useful. For completeness, could you (and Robert)
> please post the output of "upsrw myups"
pi at rpi4:/media/pi/workspace $ upsrw myups
[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

[input.transfer.high]
High voltage transfer point (V)
Type: STRING
Maximum length: 10
Value: 0

[input.transfer.low]
Low voltage transfer point (V)
Type: STRING
Maximum length: 10
Value: 0

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

[ups.delay.start]
Interval to wait before (re)starting the load (seconds)
Type: STRING
Maximum length: 10
Value: 0
> and "upscmd -l myups"? 
pi at rpi4:/media/pi/workspace $ upscmd -l myups
Instant commands supported on UPS [myups]:

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

Which looks very incomplete to me.  OTOH, its not a very big UPS but 
neither is the pi.  I have tested that, and it shuts off long before it 
outouts a LB signal.

But as the old saw says, its not my job to blow the whistle. I'm just 
happy that it protects the pi while the Generac is being started.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>