Re: [Nut-upsuser] Can't get CyberPower UPS to work with Raspberry Pi 4

[Gene Heskett]

On Wednesday 28 October 2020 21:32:02 Charles Lepple wrote:

> On Oct 26, 2020, at 9:38 AM, Gene Heskett  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@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@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 

___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] NUT uses port 3493 for everything

[Charles Lepple]

On Oct 24, 2020, at 3:20 PM, Roger Price  wrote:
> 
> The NUT project uses port 3493 to receive traffic to the upsd server. Unlike 
> the protocols http (80) and https (443), NUT has no specific port for 
> encrypted traffic.  For the upsdTLS.py daemon. I squatted port 563, but it 
> would be much better to have an officially assigned port.
> 
> Port 3494 was at one time assigned to
>  ibm34943494/tcp # IBM 3494  [Jeffrey_Pilch]
>  ibm34943494/udp # IBM 3494  [Jeffrey_Pilch]
> 
> The IBM 3494 is a huge tape cartridge device.  Over 6000 cartridges at a 
> time! It was announced 1995, withdrawn from marketing 2006 and service was 
> discontinued 2018.
> 
> I see that the port 3494 has disappeared from /etc/services in Debian 9.  Is 
> it possible to aquire the port for NUT?

I think Russell Kroll registered port 3493 before I started using NUT. (If 
others have more information, please jump in.) My understanding is that TCP 
port assignments are handled by IANA:

https://www.iana.org/form/ports-services



___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Can't get CyberPower UPS to work with Raspberry Pi 4

[Charles Lepple]

On Oct 27, 2020, at 2:45 PM, Robert Stocker  wrote:
> 
> Thanks so much for all the help! It looks like at present I've at least got a 
> working configuration that I need to test and fine-tune, am I interpreting 
> this correctly?

Yes. If you're good with the default NUT behavior of shutting down when the UPS 
signals LB (low battery; per upsc, seems to be at 10% charge or 300 seconds 
left, whichever comes first), it's just a matter of testing the shutdown 
command, and any power sequencing (including any auto power-on settings on the 
motherboard) issues on the way back up.

If not, there are ways to either adjust the UPS low power thresholds, or ignore 
them completely. Roger Price has a good enumeration of alternate shutdown 
strategies in his Configuration Examples document linked here: 
http://rogerprice.org/NUT/

As I just mentioned in my reply to Gene, it would be handy to have the output 
of "upsrw" and "upscmd -l" for your UPS. Those commands show the read/write 
variables and instant commands that the NUT driver detects, respectively.
___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Can't get CyberPower UPS to work with Raspberry Pi 4

[Charles Lepple]

On Oct 26, 2020, at 9:38 AM, Gene Heskett  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/
___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser