Imported Upstream version 2.7.2
This commit is contained in:
Laurent Bigonville
parent
0121794af9
commit
a356b56d11
263 changed files with 6039 additions and 8151 deletions
|
|
@ -17,7 +17,7 @@ For information about the core driver, see linkman:nutupsdrv[8].
|
|||
SUPPORTED HARDWARE
|
||||
------------------
|
||||
|
||||
The *nutdrv_qx* driver is known to work with various UPSes from 'Blazer', 'Energy Sistem', 'Fenton Technologies', 'General Electric', 'Mustek', 'Voltronic Power' (rebranded by many, many - have I said many? - others.. Long story short: if your UPS came with a software called 'Viewpower', chances are high that it works with this driver with the 'voltronic' <<_extra_arguments,protocol>>) and many others.
|
||||
The *nutdrv_qx* driver is known to work with various UPSes from 'Blazer', 'Energy Sistem', 'Fenton Technologies', 'General Electric', 'Mustek', 'Voltronic Power' (rebranded by many, many - have I said many? - others.. Long story short: if your UPS came with a software called 'Viewpower', chances are high that it works with this driver with one of the <<_extra_arguments,'voltronic*' protocols or with the 'mecer' one>>) and many others.
|
||||
|
||||
The <<_internet_resources,NUT compatibility table>> lists all the known supported models.
|
||||
Keep in mind, however, that other models not listed there may also be supported, but haven't been tested.
|
||||
|
|
@ -35,22 +35,26 @@ The following are the ones that most likely will need changing (see linkman:ups.
|
|||
*ondelay =* 'value'::
|
||||
Time to wait before switching on the UPS (seconds).
|
||||
This value is truncated to units of 60 seconds.
|
||||
The acceptable range is +0..599940+ seconds.
|
||||
+
|
||||
Note that a value below 3 minutes, may cause earlier firmware versions to not switch on automatically, so it defaults to 3 minutes (i.e. 180 seconds).
|
||||
+
|
||||
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).
|
||||
Defaults to 30 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].
|
||||
|
||||
*stayoff*::
|
||||
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, 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).
|
||||
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).
|
||||
|
||||
*protocol =* 'string'::
|
||||
Skip autodetection of the protocol to use and only use the one specified.
|
||||
Supported values 'mecer', 'megatec', 'megatec/old', 'mustek', 'voltronic' and 'zinto'.
|
||||
Supported values: 'mecer', 'megatec', 'megatec/old', 'mustek', 'q1', 'voltronic', 'voltronic-qs' and 'zinto'.
|
||||
+
|
||||
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).
|
||||
|
||||
*pollfreq =* 'value'::
|
||||
Set polling frequency, in seconds, to reduce the data flow.
|
||||
|
|
@ -99,9 +103,13 @@ If not specified, the driver defaults to 10%.
|
|||
Only used if *runtimecal* is also specified.
|
||||
|
||||
|
||||
[[old-blazer-protocols-options]]
|
||||
MECER, MEGATAEC, MEGATEC/OLD, MUSTEK, ZINTO PROTOCOLS
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
*ondelay*::
|
||||
The acceptable range is +0..599940+ seconds.
|
||||
|
||||
*offdelay*::
|
||||
The acceptable range is +12..600+ seconds.
|
||||
|
||||
|
|
@ -114,12 +122,35 @@ Some UPSes will lock up if you attempt to read vendor information from them.
|
|||
Setting this flag will make the driver skip this step.
|
||||
|
||||
|
||||
Q1 PROTOCOL
|
||||
~~~~~~~~~~~
|
||||
|
||||
*ondelay*::
|
||||
The acceptable range is +0..599940+ seconds.
|
||||
|
||||
*offdelay*::
|
||||
The acceptable range is +12..600+ seconds.
|
||||
|
||||
|
||||
VOLTRONIC-QS PROTOCOL
|
||||
~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
*ondelay*::
|
||||
The acceptable range is +60..599940+ seconds.
|
||||
|
||||
*offdelay*::
|
||||
The acceptable range is +12..540+ seconds.
|
||||
|
||||
|
||||
VOLTRONIC PROTOCOL
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
The following options are supported only by the 'voltronic' protocol.
|
||||
Not all of them are available on all the UPSes supported by this protocol.
|
||||
|
||||
*ondelay*::
|
||||
The acceptable range is +0..599940+ seconds.
|
||||
|
||||
*offdelay*::
|
||||
The acceptable range is +12..5940+ seconds.
|
||||
|
||||
|
|
@ -317,13 +348,21 @@ Stop a running battery test.
|
|||
(Not available on some hardware)
|
||||
|
||||
|
||||
MECER, MEGATEC, MEGATEC/OLD, MUSTEK, ZINTO PROTOCOLS
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
MECER, MEGATEC, MEGATEC/OLD, MUSTEK, Q1, ZINTO PROTOCOLS
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
*test.battery.start* 'value'::
|
||||
Perform a battery test for the duration of 'value' seconds (truncated to 60 seconds) [+60..5940+].
|
||||
|
||||
|
||||
VOLTRONIC POWER P98 UNITS (WITH MECER PROTOCOL)
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
*test.battery.start* 'value'::
|
||||
Perform a battery test for the duration of 'value' seconds (truncated to 60 seconds) [+12..5940+].
|
||||
This value is truncated to units of 6 seconds (less than 60 seconds) or 60 seconds (more than 60 seconds).
|
||||
|
||||
|
||||
VOLTRONIC PROTOCOL
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
|
|
@ -540,6 +579,20 @@ So, the *beeper.toggle* command may appear to have no effect in the status repor
|
|||
The temperature and load value is known to be bogus in some models.
|
||||
|
||||
|
||||
VOLTRONIC-QS UNITS
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
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.
|
||||
|
||||
|
||||
UPS WARNINGS (VOLTRONIC PROTOCOL)
|
||||
---------------------------------
|
||||
|
||||
|
|
@ -548,68 +601,68 @@ Since more than one warning at a time can be signaled, and because of the limite
|
|||
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).
|
||||
|
||||
.UPS Warnings for 'voltronic' UPSes
|
||||
[cols="5>,95",options="autowidth,header",frame="topbot",align="center",caption=""]
|
||||
[cols="5>,95",options="autowidth,header",frame="topbot",grid="rows",align="center",caption=""]
|
||||
|====
|
||||
|# |Corresponding Warning
|
||||
|1 |Battery disconnected
|
||||
|2 |Neutral not connected
|
||||
|3 |Site fault
|
||||
|4 |Phase sequence incorrect
|
||||
|5 |Phase sequence incorrect in bypass
|
||||
|6 |Input frequency unstable in bypass
|
||||
|7 |Battery overcharged
|
||||
|8 |Low battery
|
||||
|9 |Overload alarm
|
||||
|10 |Fan alarm
|
||||
|11 |EPO enabled
|
||||
|12 |Unable to turn on UPS
|
||||
|13 |Over temperature alarm
|
||||
|14 |Charger alarm
|
||||
|15 |Remote auto shutdown
|
||||
|16 |L1 input fuse not working
|
||||
|17 |L2 input fuse not working
|
||||
|18 |L3 input fuse not working
|
||||
|19 |Positive PFC abnormal in L1
|
||||
|20 |Negative PFC abnormal in L1
|
||||
|21 |Positive PFC abnormal in L2
|
||||
|22 |Negative PFC abnormal in L2
|
||||
|23 |Positive PFC abnormal in L3
|
||||
|24 |Negative PFC abnormal in L3
|
||||
|25 |Abnormal in CAN-bus communication
|
||||
|26 |Abnormal in synchronous signal circuit
|
||||
|27 |Abnormal in synchronous pulse signal circuit
|
||||
|28 |Abnormal in host signal circuit
|
||||
|29 |Male connector of parallel cable not connected well
|
||||
|30 |Female connector of parallel cable not connected well
|
||||
|31 |Parallel cable not connected well
|
||||
|32 |Battery connection not consistent in parallel systems
|
||||
|33 |AC connection not consistent in parallel systems
|
||||
|34 |Bypass connection not consistent in parallel systems
|
||||
|35 |UPS model types not consistent in parallel systems
|
||||
|36 |Capacity of UPSs not consistent in parallel systems
|
||||
|37 |Auto restart setting not consistent in parallel systems
|
||||
|38 |Battery cell over charge
|
||||
|39 |Battery protection setting not consistent in parallel systems
|
||||
|40 |Battery detection setting not consistent in parallel systems
|
||||
|41 |Bypass not allowed setting not consistent in parallel systems
|
||||
|42 |Converter setting not consistent in parallel systems
|
||||
|43 |High loss point for frequency in bypass mode not consistent in parallel systems
|
||||
|44 |Low loss point for frequency in bypass mode not consistent in parallel systems
|
||||
|45 |High loss point for voltage in bypass mode not consistent in parallel systems
|
||||
|46 |Low loss point for voltage in bypass mode not consistent in parallel systems
|
||||
|47 |High loss point for frequency in AC mode not consistent in parallel systems
|
||||
|48 |Low loss point for frequency in AC mode not consistent in parallel systems
|
||||
|49 |High loss point for voltage in AC mode not consistent in parallel systems
|
||||
|50 |Low loss point for voltage in AC mode not consistent in parallel systems
|
||||
|51 |Warning for locking in bypass mode after 3 consecutive overloads within 30 min
|
||||
|52 |Warning for three-phase AC input current unbalance
|
||||
|53 |Warning for a three-phase input current unbalance detected in battery mode
|
||||
|54 |Warning for Inverter inter-current unbalance
|
||||
|55 |Programmable outlets cut off pre-alarm
|
||||
|56 |Warning for Battery replace
|
||||
|57 |Abnormal warning on input phase angle
|
||||
|58 |Warning!! Cover of maintain switch is open
|
||||
|62 |EEPROM operation error
|
||||
|# |Corresponding Warning
|
||||
|1 |Battery disconnected
|
||||
|2 |Neutral not connected
|
||||
|3 |Site fault
|
||||
|4 |Phase sequence incorrect
|
||||
|5 |Phase sequence incorrect in bypass
|
||||
|6 |Input frequency unstable in bypass
|
||||
|7 |Battery overcharged
|
||||
|8 |Low battery
|
||||
|9 |Overload alarm
|
||||
|10 |Fan alarm
|
||||
|11 |EPO enabled
|
||||
|12 |Unable to turn on UPS
|
||||
|13 |Over temperature alarm
|
||||
|14 |Charger alarm
|
||||
|15 |Remote auto shutdown
|
||||
|16 |L1 input fuse not working
|
||||
|17 |L2 input fuse not working
|
||||
|18 |L3 input fuse not working
|
||||
|19 |Positive PFC abnormal in L1
|
||||
|20 |Negative PFC abnormal in L1
|
||||
|21 |Positive PFC abnormal in L2
|
||||
|22 |Negative PFC abnormal in L2
|
||||
|23 |Positive PFC abnormal in L3
|
||||
|24 |Negative PFC abnormal in L3
|
||||
|25 |Abnormal in CAN-bus communication
|
||||
|26 |Abnormal in synchronous signal circuit
|
||||
|27 |Abnormal in synchronous pulse signal circuit
|
||||
|28 |Abnormal in host signal circuit
|
||||
|29 |Male connector of parallel cable not connected well
|
||||
|30 |Female connector of parallel cable not connected well
|
||||
|31 |Parallel cable not connected well
|
||||
|32 |Battery connection not consistent in parallel systems
|
||||
|33 |AC connection not consistent in parallel systems
|
||||
|34 |Bypass connection not consistent in parallel systems
|
||||
|35 |UPS model types not consistent in parallel systems
|
||||
|36 |Capacity of UPSs not consistent in parallel systems
|
||||
|37 |Auto restart setting not consistent in parallel systems
|
||||
|38 |Battery cell over charge
|
||||
|39 |Battery protection setting not consistent in parallel systems
|
||||
|40 |Battery detection setting not consistent in parallel systems
|
||||
|41 |Bypass not allowed setting not consistent in parallel systems
|
||||
|42 |Converter setting not consistent in parallel systems
|
||||
|43 |High loss point for frequency in bypass mode not consistent in parallel systems
|
||||
|44 |Low loss point for frequency in bypass mode not consistent in parallel systems
|
||||
|45 |High loss point for voltage in bypass mode not consistent in parallel systems
|
||||
|46 |Low loss point for voltage in bypass mode not consistent in parallel systems
|
||||
|47 |High loss point for frequency in AC mode not consistent in parallel systems
|
||||
|48 |Low loss point for frequency in AC mode not consistent in parallel systems
|
||||
|49 |High loss point for voltage in AC mode not consistent in parallel systems
|
||||
|50 |Low loss point for voltage in AC mode not consistent in parallel systems
|
||||
|51 |Warning for locking in bypass mode after 3 consecutive overloads within 30 min
|
||||
|52 |Warning for three-phase AC input current unbalance
|
||||
|53 |Warning for a three-phase input current unbalance detected in battery mode
|
||||
|54 |Warning for Inverter inter-current unbalance
|
||||
|55 |Programmable outlets cut off pre-alarm
|
||||
|56 |Warning for Battery replace
|
||||
|57 |Abnormal warning on input phase angle
|
||||
|58 |Warning!! Cover of maintain switch is open
|
||||
|62 |EEPROM operation error
|
||||
|====
|
||||
|
||||
|
||||
|
|
@ -637,6 +690,7 @@ linkman:upsdrvctl[8],
|
|||
linkman:upsmon[8],
|
||||
linkman:upsrw[8]
|
||||
|
||||
|
||||
Internet Resources:
|
||||
~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue