Nut upsuser - Sep 2022 - How to change shutdown notification threshold on Fortron UPS Champs (blazer_usb)?

Dne 19. 08. 22 v 12:49 Pavel Hofman napsal(a):
> Hi,
> 
> I am trying to configure the shutdown threshold for Fortron UPS Champs.
> 
> upsc reports:
> 
> Init SSL without certificate database
> battery.charge: 100
> battery.voltage: 55.20
> battery.voltage.high: 52.00
> battery.voltage.low: 41.60
> battery.voltage.nominal: 48.0
> device.mfr:
> device.model: WPHVT2K0
> device.type: ups
> driver.name: blazer_usb
> driver.parameter.pollinterval: 2
> driver.parameter.port: /dev/hidraw2
> driver.parameter.synchronous: no
> driver.version: 2.7.4
> driver.version.internal: 0.12
> input.current.nominal: 8.0
> input.frequency: 50.0
> input.frequency.nominal: 50
> input.voltage: 234.5
> input.voltage.fault: 234.5
> input.voltage.nominal: 230
> output.voltage: 229.7
> ups.beeper.status: enabled
> ups.delay.shutdown: 30
> ups.delay.start: 180
> ups.firmware: 01060.07
> ups.load: 46
> ups.mfr:
> ups.model: WPHVT2K0
> ups.productid: 5161
> ups.status: OL
> ups.temperature: 26.3
> ups.type: online
> ups.vendorid: 0665
> 
> 
> Please note there is no battery.charge.low, the battery.charge is 
> provided by the blazer_usb driver 
>
https://networkupstools.org/docs/man/blazer_usb.html#_notes_for_the_previous_user_of_megatec_drivers
> 
> 
> I tried to configure override.battery.charge.low for the device in 
> ups.conf (after ignorelb), nothing reported in upsc.
> 
> I do not need any times, just being able to set? charge level or voltage 
> level at which NUTS will issue the shutdown command to my servers 
> connected to the UPS a communicating with the nuts-server (their 
> shutdown takes a while). I could not find any info how to do that apart 
> of 
> https://github.com/networkupstools/nut/issues/561#issuecomment-398791357 
> which did not work for me (no battery.charge.low info appeared in upcs 
> after this setting and reloading all nuts-related daemons (server, 
> client, monitor), nothing found in the logs.
> 
> Thank you very much for any help or hints.
> 
I tried to increase debug_min = 10 in non-driver/global section of 
ups.conf and no extra logs appeared in /var/log/syslog. Neither did with 
debug_min = 0 or 1, no effect. I do not know if the number should be 
high or low, could not find it in any docs online.

Thanks a lot,

Pavel.

On Mon, 29 Aug 2022, Pavel Hofman wrote:

blazer_usb reports:
>> ups.model: WPHVT2K0
>> ups.productid: 5161
The Fortron site https://energy.fsp-europe.com/uninterruptible-power-supply/ has
no mention of these references.  I wonder where blazer_usb found them?
>> ups.status: OL
If you unplug the UPS from the wall, and run it down, maybe with a dummy load, 
do you see OB, LB, other statuses?
>> battery.voltage.high/nominal/low: 52.00/48.0/41.60
Does the battery.voltage drop regularly as the UPS exhausts itself?

If battery.charge.low is not available, perhaps it is possible to get the same 
effect by watching the voltage drop to a critical value.  This needs upssched 
and a custom upssched-cmd script.

The alternative is to shutdown after a fixed time in status OB.  Its my 
preferred solution since I live in an area with a lot of lightning strikes, but 
few people seem to do it.

Roger

Hi Roger,

Thanks a lot for your hints.

Dne 29. 08. 22 v 15:14 Roger Price napsal(a):
> On Mon, 29 Aug 2022, Pavel Hofman wrote:
> 
> blazer_usb reports:
> 
>>> ups.model: WPHVT2K0
>>> ups.productid: 5161
> 
> The Fortron site 
> https://energy.fsp-europe.com/uninterruptible-power-supply/ has no 
> mention of these references.? I wonder where blazer_usb found them?
It just (auto)magically works :-)
> 
>>> ups.status: OL
> 
> If you unplug the UPS from the wall, and run it down, maybe with a dummy 
> load, do you see OB, LB, other statuses?
Yes, OB -> OL
> 
>>> battery.voltage.high/nominal/low: 52.00/48.0/41.60
> 
> Does the battery.voltage drop regularly as the UPS exhausts itself?
Yes, the voltage drops as the battery discharges.
> 
> If battery.charge.low is not available, perhaps it is possible to get 
> the same effect by watching the voltage drop to a critical value.? This 
> needs upssched and a custom upssched-cmd script.
I see. IIUC since I basically want to "override" the LOWBATT event,
not
to react to it, I will have to periodically parse upsc output and check 
for the current battery.voltage level when OB. It means basically doing 
all the work ups-monitor actually does, but with a different threshold 
(which I do not see how to change in ups-monitor). Do I assume correctly 
I cannot force/script ups-monitor to do that for me since it already has 
all the parsed data available?

Can I at least call some ups-monitor feature to start the controlled 
shutdown on all the NUTS networked clients?
> 
> The alternative is to shutdown after a fixed time in status OB.? Its my 
> preferred solution since I live in an area with a lot of lightning 
> strikes, but few people seem to do it.
Thanks. I do not know the times exactly, checking the battery voltage 
with a standalne script will probably work fine.

Best regards,

Pavel.