This option provides a default value for *ups.delay.start* that will then be used by the driver in the automatic shutdown sequence (i.e. calling the driver with the *-k* option, calling linkman:upsdrvctl[8] with the *shutdown* option or when the +FSD+ flag is set and linkman:upsmon[8] enters its shutdown sequence): however you can change this value `on the fly' for the actual session, only for the use with instant commands, setting *ups.delay.start* with linkman:upsrw[8].
*offdelay =* 'value'::
Time to wait before shutting down the UPS (seconds).
This value is truncated to units of 6 seconds (less than 60 seconds) or 60 seconds (more than 60 seconds).
This option provides a default value for *ups.delay.shutdown* that will then be used by the driver in the automatic shutdown sequence (i.e. calling the driver with the *-k* option, calling linkman:upsdrvctl[8] with the *shutdown* option or when the +FSD+ flag is set and linkman:upsmon[8] enters its shutdown sequence): however you can change this value `on the fly' for the actual session, only for the use with instant commands, setting *ups.delay.shutdown* with linkman:upsrw[8].
If you set stayoff in linkman:ups.conf[5] when FSD arises the UPS will call a *shutdown.stayoff* shutting down after *ups.delay.shutdown* seconds and won't return (see <<_known_problems,KNOWN PROBLEMS>>), otherwise (standard behaviour) the UPS will call *shutdown.return* shutting down after *ups.delay.shutdown* seconds and then turn on after *ups.delay.start* seconds (if mains meanwhile returned).
Note that if you end up using the 'q1' protocol, you may want to give a try to the 'mecer', 'megatec' and 'zinto' ones setting the <<old-blazer-protocols-options,*novendor*/*norating* flags>> (only one, or both).
If your UPS doesn't report either *battery.charge* or *battery.runtime* you may want to add the following ones in order to have guesstimated values:
*default.battery.voltage.high =* 'value'::
Maximum battery voltage that is reached after about 12 to 24 hours charging.
If you want the driver to report a guesstimated *battery.charge*, you need to specify this (see <<_battery_charge,BATTERY CHARGE>>).
*default.battery.voltage.low =* 'value'::
Minimum battery voltage just before the UPS automatically shuts down.
If you want the driver to report a guesstimated *battery.charge*, you need to specify this (see <<_battery_charge,BATTERY CHARGE>>).
*default.battery.voltage.nominal =* 'value'::
*override.battery.voltage.nominal =* 'value'::
Some devices show a wrong nominal battery voltage (or none at all), so you may need to override or set a default value.
*override.battery.packs =* 'value'::
Some devices report a part of the total battery voltage.
For instance, if *battery.voltage.nominal* is 24 V, but it reports a *battery.voltage* of around 2 V, the number of *battery.packs* to correct this reading would be 12.
The driver will attempt to detect this automatically, but if this fails somehow, you may want to override this value.
*runtimecal =* 'value,value,value,value'::
Parameter used in the (optional) runtime estimation.
This takes two runtimes at different loads.
Typically, this uses the runtime at full load and the runtime at half load.
For instance, if your UPS has a rated runtime of 240 seconds at full load and 720 seconds at half load, you would enter
+
runtimecal = 240,100,720,50
+
The first load should always be higher than the second.
If you have values available for loads other than 100 and 50 % respectively, you can use those too, but keep them spaced apart as far as reasonably possible.
Just don't get too close to no load (prediction of runtime depends more on idle load for the battery then).
*chargetime =* 'value'::
The time needed to fully recharge the battery after being fully discharged.
If not specified, the driver defaults to 43200 seconds (12 hours).
Only used if *runtimecal* is also specified.
*idleload =* 'value'::
Minimum battery load used by the driver to estimate the runtime.
Some UPSes incorrectly report the `Shutdown Active' bit as always on, consequently making the driver believe the UPS is nearing a shutdown (and, as a result, ups.status always contains +FSD+... and you know what this means).
Setting this flag will make the driver ignore the `Shutdown Active' bit.
Set http://www.networkupstools.org/protocols/sola.html#_shutdown_set_command[shutdown mode functionality of Pin 1 and Pin 7] on the UPS DB9 communication port (Per Best Power's EPS-0059) to 'value' [+0..6+].
MASTERGUARD PROTOCOL
~~~~~~~~~~~~~~~~~~~~
*slave_addr =* 'value'::
Make the claim function verify it's talking to the specified 'slave address' (*ups.id*).
Safeguard against talking to the wrong one of several identical UPSes on the same USB bus.
Note that when changing *ups.id* (through linkman:upsrw[8]) the driver will continue to talk to the UPS with the new 'slave address', but won't claim it again on restart until the *slave_addr* parameter is adjusted.
Set number of batteries that make a pack to 'value' [+1..9+].
This setting will change the charge and runtime estimation reported by the UPS.
*output_phase_angle =* 'value'::
Changes output phase angle to the provided value [+000+, +120+, +180+, +240+]°.
UPS CAPABILITY SETTINGS
^^^^^^^^^^^^^^^^^^^^^^^
*reset_to_default*::
Reset capability options and their voltage and frequency limits to safe default values.
(*Doable only when the UPS is in Standby Mode*)
+
Note that setting this option will reset also *ups.start.auto*, *battery.protection*, *battery.energysave*, *ups.start.battery*, *outlet.0.switchable*, *input.transfer.high*, *input.transfer.low*, *input.frequency.high* and *input.frequency.low*.
These UPSes can be fine-tuned to suit your needs enabling or disabling the following options (the driver should tell you which one the UPS is capable of on startup: the settable ones will be reported either are 'enabled' or 'disabled' in the logs):
Enable or disable Constant Phase Angle Function (output and input phase angles are not equal) [+enabled+/+disabled+].
*limited_runtime_on_battery =* 'string'::
Enable or disable limited runtime on battery mode [+enabled+/+disabled+].
BYPASS MODE VOLTAGE/FREQUENCY LIMITS
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Variables to fine-tune voltage and frequency limits for Bypass mode.
These limits are reset to safe default values by *reset_to_default*.
If AC voltage and frequency are within acceptable range, Bypass mode will be used (If the UPS is capable of and it's enabled).
Since these values are device-specific, if your UPS support them, you will get their settable limits printed in the logs on startup.
*max_bypass_volt =* 'value'::
Maximum voltage for Bypass Mode (V).
*min_bypass_volt =* 'value'::
Minimum voltage for Bypass Mode (V).
*max_bypass_freq =* 'value'::
Maximum frequency for Bypass Mode (Hz).
*min_bypass_freq =* 'value'::
Minimum frequency for Bypass Mode (Hz).
OPTIONS SPECIFIC FOR P31 UPSES
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The following options are available only on P31 UPSes.
*work_range_type =* 'string'::
Device grid working range for P31 UPSes [+Appliance+/+UPS+].
TESTING
^^^^^^^
This protocol comes with a couple of functions that are not enabled by default because of the lack of knowledge of some part of the communication protocol used by these UPSes by your friendly neighborhood developer.
So if you are brave enough to risk your UPS and attached devices' life to help the developers, this will be very appreciated..
*Do it at your own risk*.
*testing*::
If invoked the driver will exec also commands that still need testing.
SERIAL INTERFACE ONLY
~~~~~~~~~~~~~~~~~~~~~
*cablepower =* 'string'::
By default the driver will set DTR and clear RTS ('normal').
If you find that your UPS isn't detected or the communication with the UPS is unreliable, you may try if clear DTR and set RTS ('reverse'), set DTR and RTS ('both') or clear DTR and RTS ('none') improves this situation.
USB INTERFACE ONLY
~~~~~~~~~~~~~~~~~~
*port =* 'string'::
You must set 'value' to *auto*.
*vendorid =* 'regex'::
*productid =* 'regex'::
*vendor =* 'regex'::
*product =* 'regex'::
*serial =* 'regex'::
Select a specific UPS, in case there is more than one connected via USB.
Each option specifies an extended regular expression (see *regex(7)*) that must match the UPS's entire vendor/product/serial string (minus any surrounding whitespace), or the whole 4-digit hexadecimal code for vendorid and productid.
This subdriver, meant to be used with the 'megatec' protocol, does *not* support the *shutdown.stayoff* and *load.off* commands.
Plus, the *shutdown.return* command ignores the values set in 'ups.delay.start'/*ondelay* and makes the UPS turn on the load as soon as power is back.
*'krauler' subdriver*::
This subdriver, meant to be used with the 'megatec' protocol, does *not* support the shutdown commands, i.e.: *shutdown.return*, *shutdown.stayoff* and *load.off*.
This subdriver, meant to be used with the 'megatec' protocol, does *not* support the shutdown commands, i.e.: *shutdown.return*, *shutdown.stayoff* and *load.off*.
The following instant commands are available for the 'voltronic' protocol.
Not all of them are available on all the UPSes supported by this protocol.
*beeper.enable*::
Enable the UPS beeper.
*beeper.disable*::
Disable the UPS beeper.
*test.battery.start* 'value'::
Perform a battery test for the duration of 'value' seconds [+12..5940+].
This value is truncated to units of 6 seconds (less than 60 seconds) or 60 seconds (more than 60 seconds).
*outlet.1.load.off*::
Turn off outlet 1 load immediately.
*outlet.1.load.on*::
Turn on outlet 1 load immediately.
*outlet.2.load.off*::
Turn off outlet 2 load immediately.
*outlet.2.load.on*::
Turn on outlet 2 load immediately.
*outlet.3.load.off*::
Turn off outlet 3 load immediately.
*outlet.3.load.on*::
Turn on outlet 3 load immediately.
*outlet.4.load.off*::
Turn off outlet 4 load immediately.
*outlet.4.load.on*::
Turn on outlet 4 load immediately.
*bypass.start*::
Put the UPS in ECO Mode.
*bypass.stop*::
Take the UPS out of ECO Mode.
BATTERY CHARGE
--------------
Due to popular demand, this driver will report a guesstimated *battery.charge* and optionally *battery.runtime*, provided you specified a couple of the <<_extra_arguments,EXTRA ARGUMENTS>> listed above.
If you specify both *battery.voltage.high* and *battery.voltage.low* in linkman:ups.conf[5], but don't enter *runtimecal*, it will guesstimate the state of charge by looking at the battery voltage alone.
This is not reliable under load, as this only gives reasonably accurate readings if you disconnect the load, let the battery rest for a couple of minutes and then measure the open cell voltage.
This just isn't practical if the power went out and the UPS is providing power for your systems.
battery.voltage - battery.voltage.low
battery.charge = ------------------------------------------ x 100 %
battery.voltage.high - battery.voltage.low
There is a way to get better readings without disconnecting the load but this requires one to keep track on how much (and how fast) current is going in and out of the battery.
If you specified the *runtimecal*, the driver will attempt to do this.
Note however, that this heavily relies on the values you enter and that the UPS must be able to report the load as well.
There are quite a couple of devices that report 0 % (or any other fixed value) at all times, in which case this obviously doesn't work.
The driver also has no way of determining the degradation of the battery capacity over time, so you'll have to deal with this yourself (by adjusting the values in *runtimecal*).
Also note that the driver guesses the initial state of charge based on the battery voltage, so this may be less than 100 %, even when you are certain that they are full.
There is just no way to reliably measure this between 0 and 100 % full charge.
This is better than nothing (but not by much).
If any of the above calculations is giving you incorrect readings, you are the one that put in the values in linkman:ups.conf[5], so don't complain with the author.
If you need something better, buy a UPS that reports *battery.charge* and *battery.runtime* all by itself without the help of a NUT driver.
NOTES FOR THE PREVIOUS USER OF MEGATEC DRIVERS
----------------------------------------------
The *nutdrv_qx* driver having replaced the megatec ones, some configuration changes may be required by users switching to *nutdrv_qx*.
Part of this, the following megatec options, in linkman:ups.conf[5], have to be changed:
*battvolts*::
You need to use 'default.battery.voltage.high' and 'default.battery.voltage.low'
*dtr* and *rts*::
You need to use 'cablepower'
*ignoreoff*::
This parameter can simply be discarded, since it was a wrong understanding of the specification.
NOTES FOR THE PREVIOUS USER OF BLAZER DRIVERS
---------------------------------------------
The *nutdrv_qx* driver having replaced the blazer ones, some configuration changes may be required by users switching to *nutdrv_qx*.
Part of this, the following blazer options, in linkman:ups.conf[5], have to be changed:
*ondelay*::
While the previous blazer drivers expected minutes, the new *nutdrv_qx* driver wants seconds.
The following instant command has also been changed:
*test.battery.start* 'value'::
While the old blazer drivers expected a 'value' in minutes, the *nutdrv_qx* driver wants a 'value' in seconds.
The *nutdrv_qx* driver having replaced the voltronic ones, some configuration changes may be required by users switching to *nutdrv_qx*.
Part of this, the following voltronic options, in linkman:ups.conf[5], have to be changed:
*ondelay*::
While the previous voltronic drivers expected minutes, the new *nutdrv_qx* driver wants seconds.
It no longer defaults to 0 minutes but to 3 minutes (i.e. 180 seconds) for compatibility with the users switching from the old blazer drivers.
*battnumb*::
This option has been renamed to *battery_number*.
The following options are no longer supported by this driver, you can now change them more conveniently `on the fly' calling linkman:upsrw[8] with the appropriate NUT variable - provided that your UPS supports them.
[horizontal]
*battpacks*:: -> *battery.packs*
+
Set number of battery packs in parallel [+1..99+].
This setting will change the charge and runtime estimation reported by the UPS.
*battlow*:: -> *battery.voltage.low*
+
Set minimum battery voltage just before the UPS automatically shuts down.
This setting will change the charge and runtime estimation reported by the UPS.
*auto_reboot*:: -> *ups.start.auto*
+
Enable or disable auto reboot [+enabled+/+disabled+].
If enabled, the UPS will auto recover when AC power returns.
*battery_protection*:: -> *battery.protection*
+
Enable or disable battery deep discharge protection [+enabled+/+disabled+].
*energy_saving*:: -> *battery.energysave*
+
Enable or disable Green power function [+enabled+/+disabled+].
If enabled, for energy saving, the UPS will auto off when there is no load.
*cold_start*:: -> *ups.start.battery*
+
Enable or disable Cold Start [+enabled+/+disabled+].
If enabled, the UPS can be turned on also if AC is not connected to the UPS.
*outlet_control*:: -> *outlet.0.switchable*
+
Enable or disable programmable outlets control at battery mode [+enabled+/+disabled+].
If enabled, the UPS will cut off programmable outlets after backup time (set through *outlet.*{*1*,*2*,*3*,*4*}**.delay.shutdown**) arrives.
If disabled, the UPS will provide continuous power to programmable outlets until the battery is running out.
The driver is supposed to support both "new" A series (A700/1000/2000/3000 and their -19 cousins) and E series (E60/100/200) but was tested only on A due to lack of E hardware.
Both *load.off* and *shutdown.stayoff* instant commands are known to work as expected (i.e. turn the load off indefinitely) only if mains is present, otherwise, as soon as mains returns the load will be powered.
After issuing a *shutdown.return* instant command, the UPS won't wait *ondelay* before powering on the load, provided the following conditions are met:
- if the load has been previously (no matter how long before) powered off through *load.off*/*shutdown.stayoff* _and_ powered on through *load.on*/*shutdown.stop* _and_
- if AC wasn't cut after issuing the *load.off*/*shutdown.stayoff* (i.e. the UPS didn't turn itself off) _and_
- if there's a power outage after issuing the *shutdown.return* command
In this case, as soon as mains returns the load will be powered.
*shutdown.return*, *load.off*, and *shutdown.stayoff* instant commands are known to work as expected only if mains is present, otherwise, as soon as mains returns the load will be powered.
The UPSes supported by 'voltronic' protocol report warnings through a 64bit flag (bit1bit2...bit63bit64) where 1 means that a warning arose, while 0 means no warning.
Since more than one warning at a time can be signaled, and because of the limited space in the ups.alarm variable, if the length of the warnings exceeds that of ups.alarms variable, they will be reported as bits.
If you want to know the explanation of that bit you can either watch the log or see the next table (unlisted bits equal to unknown warnings).
