search for: allow_killpower

...ENT: # First report for new salicru HID subdriver from PR referenced # above for Salicru SPS 2000 ADV T. # NOTE: I (like abelgomez ) tried to set the value of # `battery.charge.low` using `upsrw`, but although the command returns # OK, no values seem to be modified. # I was able to set `driver.flag.allow_killpower`, but issuing # `upscmd? -u ** -p ** ny driver.killpower` did nothing, even though it replied #? with 'OK' # DEVICE:EOC battery.charge: 100 battery.charge.low: 0 battery.charge.warning: 20 battery.runtime: 7200 battery.runtime.low: 400 battery.type: PbAcid battery.voltage: 25.60 battery.vo...

...ery.date: 2023-11-21 >> battery.runtime: 57000.0 >> battery.runtime.low: 180 >> battery.voltage: 109.0 >> device.mfr: APC >> device.model: Smart-UPS SRT 3000 >> device.serial: AS2032296523 >> device.type: ups >> driver.debug: 0 >> driver.flag.allow_killpower: 0 >> driver.name: apcupsd-ups >> driver.parameter.pollinterval: 10 >> driver.parameter.port: localhost >> driver.parameter.synchronous: auto >> driver.state: quiet >> driver.version: 2.8.1 >> driver.version.internal: 0.71 >> input.frequency: 60.0 &gt...

...ery.date: 2023-11-21 >> battery.runtime: 57000.0 >> battery.runtime.low: 180 >> battery.voltage: 109.0 >> device.mfr: APC >> device.model: Smart-UPS SRT 3000 >> device.serial: AS2032296523 >> device.type: ups >> driver.debug: 0 >> driver.flag.allow_killpower: 0 >> driver.name: apcupsd-ups >> driver.parameter.pollinterval: 10 >> driver.parameter.port: localhost >> driver.parameter.synchronous: auto >> driver.state: quiet >> driver.version: 2.8.1 >> driver.version.internal: 0.71 >> input.frequency: 60.0 &gt...

...> battery.charge.low: 5 > battery.date: 2023-11-21 > battery.runtime: 57000.0 > battery.runtime.low: 180 > battery.voltage: 109.0 > device.mfr: APC > device.model: Smart-UPS SRT 3000 > device.serial: AS2032296523 > device.type: ups > driver.debug: 0 > driver.flag.allow_killpower: 0 > driver.name: apcupsd-ups > driver.parameter.pollinterval: 10 > driver.parameter.port: localhost > driver.parameter.synchronous: auto > driver.state: quiet > driver.version: 2.8.1 > driver.version.internal: 0.71 > input.frequency: 60.0 > input.voltage: 224.7 > outp...

...> battery.charge.low: 5 > battery.date: 2023-11-21 > battery.runtime: 57000.0 > battery.runtime.low: 180 > battery.voltage: 109.0 > device.mfr: APC > device.model: Smart-UPS SRT 3000 > device.serial: AS2032296523 > device.type: ups > driver.debug: 0 > driver.flag.allow_killpower: 0 > driver.name: apcupsd-ups > driver.parameter.pollinterval: 10 > driver.parameter.port: localhost > driver.parameter.synchronous: auto > driver.state: quiet > driver.version: 2.8.1 > driver.version.internal: 0.71 > input.frequency: 60.0 > input.voltage: 224.7 > outp...

...rom nut+apcupsd (for reference): battery.charge: 99.0 battery.charge.low: 5 battery.date: 2023-11-21 battery.runtime: 57000.0 battery.runtime.low: 180 battery.voltage: 109.0 device.mfr: APC device.model: Smart-UPS SRT 3000 device.serial: AS2032296523 device.type: ups driver.debug: 0 driver.flag.allow_killpower: 0 driver.name: apcupsd-ups driver.parameter.pollinterval: 10 driver.parameter.port: localhost driver.parameter.synchronous: auto driver.state: quiet driver.version: 2.8.1 driver.version.internal: 0.71 input.frequency: 60.0 input.voltage: 224.7 output.current: 0.00 output.frequency: 60.0 output.vol...

...rom nut+apcupsd (for reference): battery.charge: 99.0 battery.charge.low: 5 battery.date: 2023-11-21 battery.runtime: 57000.0 battery.runtime.low: 180 battery.voltage: 109.0 device.mfr: APC device.model: Smart-UPS SRT 3000 device.serial: AS2032296523 device.type: ups driver.debug: 0 driver.flag.allow_killpower: 0 driver.name: apcupsd-ups driver.parameter.pollinterval: 10 driver.parameter.port: localhost driver.parameter.synchronous: auto driver.state: quiet driver.version: 2.8.1 driver.version.internal: 0.71 input.frequency: 60.0 input.voltage: 224.7 output.current: 0.00 output.frequency: 60.0 output.vol...

...groups for both UPS(outlet.group.count: 2). but SMT2200RM2U has only one outlet group. since the new driver can not shutdown the ups, I wonder what's the fastest method to test the function (previously I setup the ups and unplug the utility from the ups for testing). is "upsrw driver.flag.allow_killpower=1" then "upscmd driver.killpower" the correct testing procedure? 5. the default/actual shutdown delay for both ups is 90 seconds(when real testing under apcupsd). the "upsrw -l myups" has value "90" for the attribute "outlet.group.1.delay.shutdown". but...

...groups for both UPS(outlet.group.count: 2). but SMT2200RM2U has only one outlet group. since the new driver can not shutdown the ups, I wonder what's the fastest method to test the function (previously I setup the ups and unplug the utility from the ups for testing). is "upsrw driver.flag.allow_killpower=1" then "upscmd driver.killpower" the correct testing procedure? 5. the default/actual shutdown delay for both ups is 90 seconds(when real testing under apcupsd). the "upsrw -l myups" has value "90" for the attribute "outlet.group.1.delay.shutdown". but...

Got an update for APC Modbus users: a new PR is waiting for real-life testing for settable variables and instant commands support. https://github.com/networkupstools/nut/pull/2184 As before, a custom build of libmodbus may be needed for USB support (detailed in the earlier PR), but Serial and TCP may already be well served by a distro near you! Jim On Sun, Oct 22, 2023, 01:08 Jim Klimov

Got an update for APC Modbus users: a new PR is waiting for real-life testing for settable variables and instant commands support. https://github.com/networkupstools/nut/pull/2184 As before, a custom build of libmodbus may be needed for USB support (detailed in the earlier PR), but Serial and TCP may already be well served by a distro near you! Jim On Sun, Oct 22, 2023, 01:08 Jim Klimov

Thanks again, Great to see confirmations of more and more things working! > I wonder what's the fastest method to test the function (previously I setup the ups and unplug the utility from the ups for testing). > is "upsrw driver.flag.allow_killpower=1" then "upscmd driver.killpower" the correct testing procedure? At least by intent of this new feature -- yes. Normally the drivers are not allowed to pass these dangerous commands unless started specifically for killpower handling late in the system shutdown. Since NUT v2.8.1 howe...

Thanks again, Great to see confirmations of more and more things working! > I wonder what's the fastest method to test the function (previously I setup the ups and unplug the utility from the ups for testing). > is "upsrw driver.flag.allow_killpower=1" then "upscmd driver.killpower" the correct testing procedure? At least by intent of this new feature -- yes. Normally the drivers are not allowed to pass these dangerous commands unless started specifically for killpower handling late in the system shutdown. Since NUT v2.8.1 howe...

Hello fellow NUTs :) It is my great pleasure to get a bit of sunshine from other people's work, and announce that the initial pull request for `apc_modbus` NUT driver has recently been merged to the main NUT codebase, so it would be part of an eventual 2.8.1 release. Great thanks go to Axel Gembe for the implementation, and to numerous community members for testing as well as their bug-fix

Hello fellow NUTs :) It is my great pleasure to get a bit of sunshine from other people's work, and announce that the initial pull request for `apc_modbus` NUT driver has recently been merged to the main NUT codebase, so it would be part of an eventual 2.8.1 release. Great thanks go to Axel Gembe for the implementation, and to numerous community members for testing as well as their bug-fix

Cheers, With https://github.com/networkupstools/nut/pull/1906 and https://github.com/networkupstools/nut/pull/1912 (and probably some more later), I've been enhancing NUT driver framework with support for live reload of configuration, primarily to acknowledge changes to debug_min setting in ups.conf - but made in a generic fashion that specific drivers may take advantage of for their

Cheers, With https://github.com/networkupstools/nut/pull/1906 and https://github.com/networkupstools/nut/pull/1912 (and probably some more later), I've been enhancing NUT driver framework with support for live reload of configuration, primarily to acknowledge changes to debug_min setting in ups.conf - but made in a generic fashion that specific drivers may take advantage of for their

...ge.low: 10 battery.mfr.date: 2001/01/01 battery.runtime: 659 battery.runtime.low: 120 battery.type: PbAc battery.voltage: 27.3 battery.voltage.nominal: 24.0 device.mfr: American Power Conversion device.model: Back-UPS BX1600MI device.serial: 9B2339A15993 device.type: ups driver.debug: 0 driver.flag.allow_killpower: 0 driver.name: usbhid-ups driver.parameter.poll freq: 30 driver.parameter.poll interval: 2 driver.parameter.port : auto driver.parameter.synchronous: auto driver.state: quiet driver.version: 2.8.1-884-gf2fc47067 driver.version.data: APC HID 0.100 driver.version.internal: 0.52 driver.version.usb: l...