Pavel Hofman
2022-Aug-19 10:49 UTC
[Nut-upsuser] How to change shutdown notification threshold on Fortron UPS Champs (blazer_usb)?
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. Best regards, Pavel.
Pavel Hofman
2022-Aug-29 08:18 UTC
[Nut-upsuser] 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.