nutdrv_qx \- Driver for Q* protocol serial and USB based UPS equipment
.SH"NOTE"
.sp
This man page only documents the hardware\-specific features of the \fBnutdrv_qx\fR driver\&. For information about the core driver, see \fBnutupsdrv\fR(8)\&.
The \fBnutdrv_qx\fR driver is known to work with various UPSes from \fIArmac\fR, \fIBlazer\fR, \fIEnergy Sistem\fR, \fIFenton Technologies\fR, \fIGeneral Electric\fR, \fIHunnox\fR, \fIMasterguard\fR, \fIMustek\fR, \fIPowercool\fR, \fIVoltronic Power\fR (rebranded by many, many \- have I said many? \- others\&...
Long story short: if your UPS came with a software called \fIViewpower\fR, chances are high that it works with this driver with one of the \fIvoltronic*\fR protocols or with the \fImecer\fR one), and many others\&.
.sp
The 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\(cqt been tested or reported back\&.
Time to wait before switching on the UPS (seconds)\&. This value is truncated to units of 60 seconds\&.
.sp
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)\&.
that will then be used by the driver in the automatic shutdown sequence (i\&.e\&. calling the driver with the
\fB\-k\fR
option, calling
\fBupsdrvctl\fR(8)
with the
\fBshutdown\fR
option or when the
FSD
flag is set and
\fBupsmon\fR(8)
enters its shutdown sequence): however you can change this value \(oqon the fly\(cq for the actual session, only for the use with instant commands, setting
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\&.
that will then be used by the driver in the automatic shutdown sequence (i\&.e\&. calling the driver with the
\fB\-k\fR
option, calling
\fBupsdrvctl\fR(8)
with the
\fBshutdown\fR
option or when the
FSD
flag is set and
\fBupsmon\fR(8)
enters its shutdown sequence): however you can change this value \(oqon the fly\(cq for the actual session, only for the use with instant commands, setting
If your UPS doesn\(cqt report either \fBbattery\&.charge\fR or \fBbattery\&.runtime\fR you may want to add the following ones in order to have guesstimated values:
Some devices show a wrong nominal battery voltage (or none at all), so you may need to override or set a default value\&.
.RE
.PP
\fBoverride\&.battery\&.packs =\fR\fIvalue\fR
.RS4
Some devices report a part of the total battery voltage\&. For instance, if
\fBbattery\&.voltage\&.nominal\fR
is 24 V, but it reports a
\fBbattery\&.voltage\fR
of around 2 V, the number of
\fBbattery\&.packs\fR
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\&.
.RE
.PP
\fBruntimecal =\fR\fIvalue,value,value,value\fR
.RS4
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
.sp
.ifn\{\
.RS4
.\}
.nf
runtimecal = 240,100,720,50
.fi
.ifn\{\
.RE
.\}
.sp
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\(cqt get too close to no load (prediction of runtime depends more on idle load for the battery then)\&.
.RE
.PP
\fBchargetime =\fR\fIvalue\fR
.RS4
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
\fBruntimecal\fR
is also specified\&.
.RE
.PP
\fBidleload =\fR\fIvalue\fR
.RS4
Minimum battery load used by the driver to estimate the runtime\&. If not specified, the driver defaults to 10%\&. Only used if
Some UPSes incorrectly report the \(oqShutdown Active\(cq 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 \(oqShutdown Active\(cq bit\&.
The following options are supported only by the \fIvoltronic\fR protocol\&. Not all of them are available on all the UPSes supported by this protocol\&.
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 \fIenabled\fR or \fIdisabled\fR in the logs):
Enable or disable alarm (BEEP!) [enabled/disabled]\&. Settable also \(oqon the fly\(cq with
\fBbeeper\&.enable\fR
and
\fBbeeper\&.disable\fR
instant commands\&.
.RE
.PP
\fBbypass_alarm =\fR\fIstring\fR
.RS4
Enable or disable alarm (BEEP!) at Bypass Mode [enabled/disabled]\&.
.RE
.PP
\fBbattery_alarm =\fR\fIstring\fR
.RS4
Enable or disable alarm (BEEP!) at Battery Mode [enabled/disabled]\&.
.RE
.PP
\fBbypass_when_off =\fR\fIstring\fR
.RS4
Enable or disable bypass when the UPS is Off [enabled/disabled]\&. If enabled, AC will directly provide power to connected devices when the UPS is off\&.
.RE
.PP
\fBbypass_forbidding =\fR\fIstring\fR
.RS4
Enable or disable Bypass Forbidding [enabled/disabled]\&. If enabled, the UPS will not transfer to bypass mode under any condition\&.
.RE
.PP
\fBconverter_mode =\fR\fIstring\fR
.RS4
Enable or disable Converter Mode [enabled/disabled]\&. When input frequency is within 40 Hz to 70 Hz, the UPS can be set at a constant output frequency, 50 Hz or 60 Hz\&. The UPS will still charge battery under this mode\&.
.RE
.PP
\fBeco_mode =\fR\fIstring\fR
.RS4
Enable or disable ECO Mode [enabled/disabled]\&. When input voltage/frequency are within acceptable range, the UPS will bypass voltage to output for energy saving\&. PFC and INVERTER are still active at this mode\&. Settable also \(oqon the fly\(cq with
\fBbypass\&.start\fR
and
\fBbypass\&.stop\fR
instant commands\&.
.RE
.PP
\fBadvanced_eco_mode =\fR\fIstring\fR
.RS4
Enable or disable Advanced ECO Mode [enabled/disabled]\&. When input voltage/frequency are within acceptable range, the UPS will bypass voltage to output for energy saving\&. PFC and INVERTER are off at this mode\&.
.RE
.PP
\fBbattery_open_status_check =\fR\fIstring\fR
.RS4
Enable or disable Battery Open Status Check [enabled/disabled]\&. If enabled, when the UPS is turned on, it will check if the battery is connected or not\&.
.RE
.PP
\fBsite_fault_detection =\fR\fIstring\fR
.RS4
Enable or disable site fault detection [enabled/disabled]\&. If enabled, the UPS will beep when the input neutral and hot wires are reversed\&.
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\&. Since these functions are supposed to be queries to the UPS for some kind of information, they \fIshould\fR not make your UPS go boom\&. So if you are brave enough to risk your UPS and attached devices\*(Aq life to help the developers, this will be very appreciated\&.\&. \fBDo it at your own risk\fR\&.
If invoked the driver will exec also commands that still need testing\&.
.RE
.RE
.SS"SERIAL INTERFACE ONLY"
.PP
\fBcablepower =\fR\fIstring\fR
.RS4
By default the driver will set DTR and clear RTS (\fInormal\fR)\&. If you find that your UPS isn\(cqt detected or the communication with the UPS is unreliable, you may try if clear DTR and set RTS (\fIreverse\fR), set DTR and RTS (\fIboth\fR) or clear DTR and RTS (\fInone\fR) improves this situation\&.
Select a specific UPS, in case there is more than one connected via USB\&. Each option specifies an extended regular expression (see
\fBregex(7)\fR) that must match the UPS\(cqs entire vendor/product/serial string (minus any surrounding whitespace), or the whole 4\-digit hexadecimal code for vendorid and productid\&. Try
Select a UPS on a specific USB bus or group of buses\&. The argument is a regular expression that must match the bus name where the UPS is connected (e\&.g\&.
Select a UPS on a specific USB device or group of devices\&. The argument is a regular expression that must match the device name where the UPS is connected (e\&.g\&.
device="001",
device="00[1\-2]")\&. Note that device numbers are not guaranteed by the OS to be stable across re\-boots or device re\-plugging\&.
The Armac communication subdriver reproduces a communication protocol used by an old release of "PowerManagerII" software, which doesn\(cqt seem to be Armac specific: its banner is "2004 Richcomm Technologies, Inc\&. Dec 27 2005 ver 1\&.1\&." Maybe other Richcomm UPSes would work with this \(em maybe better than with the older standalone
seconds (truncated to 60 seconds) [0\&.\&.5940]\&. This value is truncated to units of 6 seconds (less than 60 seconds) or 60 seconds (more than 60 seconds)\&.
\fBVOLTRONIC POWER P98 UNITS (WITH MECER PROTOCOL)\fR
.RS4
.PP
\fBtest\&.battery\&.start\fR\fIvalue\fR
.RS4
Perform a battery test for the duration of
\fIvalue\fR
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)\&.
The following instant commands are available for the \fIvoltronic\fR protocol\&. Not all of them are available on all the UPSes supported by this protocol\&.
.PP
\fBbeeper\&.enable\fR
.RS4
Enable the UPS beeper\&.
.RE
.PP
\fBbeeper\&.disable\fR
.RS4
Disable the UPS beeper\&.
.RE
.PP
\fBtest\&.battery\&.start\fR\fIvalue\fR
.RS4
Perform a battery test for the duration of
\fIvalue\fR
seconds [12\&.\&.5940]\&. This value is truncated to units of 6 seconds (less than 60 seconds) or 60 seconds (more than 60 seconds)\&.
.RE
.PP
\fBoutlet\&.1\&.load\&.off\fR
.RS4
Turn off outlet 1 load immediately\&.
.RE
.PP
\fBoutlet\&.1\&.load\&.on\fR
.RS4
Turn on outlet 1 load immediately\&.
.RE
.PP
\fBoutlet\&.2\&.load\&.off\fR
.RS4
Turn off outlet 2 load immediately\&.
.RE
.PP
\fBoutlet\&.2\&.load\&.on\fR
.RS4
Turn on outlet 2 load immediately\&.
.RE
.PP
\fBoutlet\&.3\&.load\&.off\fR
.RS4
Turn off outlet 3 load immediately\&.
.RE
.PP
\fBoutlet\&.3\&.load\&.on\fR
.RS4
Turn on outlet 3 load immediately\&.
.RE
.PP
\fBoutlet\&.4\&.load\&.off\fR
.RS4
Turn off outlet 4 load immediately\&.
.RE
.PP
\fBoutlet\&.4\&.load\&.on\fR
.RS4
Turn on outlet 4 load immediately\&.
.RE
.PP
\fBbypass\&.start\fR
.RS4
Put the UPS in ECO Mode\&.
.RE
.PP
\fBbypass\&.stop\fR
.RS4
Take the UPS out of ECO Mode\&.
.RE
.SH"BATTERY CHARGE"
.sp
Due to popular demand, this driver will report a guesstimated \fBbattery\&.charge\fR and optionally \fBbattery\&.runtime\fR, provided you specified a couple of the EXTRA ARGUMENTS listed above\&.
.sp
If you specify both \fBbattery\&.voltage\&.high\fR and \fBbattery\&.voltage\&.low\fR in \fBups.conf\fR(5), but don\(cqt enter \fBruntimecal\fR, 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\(cqt practical if the power went out and the UPS is providing power for your systems\&.
.sp
.ifn\{\
.RS4
.\}
.nf
battery\&.voltage \- battery\&.voltage\&.low
battery\&.charge = \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- x 100 %
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 \fBruntimecal\fR, 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\(cqt work\&.
.sp
The driver also has no way of determining the degradation of the battery capacity over time, so you\(cqll have to deal with this yourself (by adjusting the values in \fBruntimecal\fR)\&. 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\&.
.sp
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 \fBups.conf\fR(5), so don\(cqt complain with the author\&. If you need something better, buy a UPS that reports \fBbattery\&.charge\fR and \fBbattery\&.runtime\fR all by itself without the help of a NUT driver\&.
.SH"NOTES FOR THE PREVIOUS USER OF MEGATEC DRIVERS"
.sp
The \fBnutdrv_qx\fR driver having replaced the megatec ones, some configuration changes may be required by users switching to \fBnutdrv_qx\fR\&.
.sp
Part of this, the following megatec options, in \fBups.conf\fR(5), have to be changed:
.PP
\fBbattvolts\fR
.RS4
You need to use
\fIdefault\&.battery\&.voltage\&.high\fR
and
\fIdefault\&.battery\&.voltage\&.low\fR
.RE
.PP
\fBdtr\fR and \fBrts\fR
.RS4
You need to use
\fIcablepower\fR
.RE
.PP
\fBignoreoff\fR
.RS4
This parameter can simply be discarded, since it was a wrong understanding of the specification\&.
.RE
.SH"NOTES FOR THE PREVIOUS USER OF BLAZER DRIVERS"
.sp
The \fBnutdrv_qx\fR driver having replaced the blazer ones, some configuration changes may be required by users switching to \fBnutdrv_qx\fR\&.
.sp
Part of this, the following blazer options, in \fBups.conf\fR(5), have to be changed:
.PP
\fBondelay\fR
.RS4
While the previous blazer drivers expected minutes, the new
\fBnutdrv_qx\fR
driver wants seconds\&.
.RE
.sp
The following instant command has also been changed:
.SH"NOTES FOR THE PREVIOUS USER OF VOLTRONIC DRIVERS"
.sp
The \fBnutdrv_qx\fR driver having replaced the voltronic ones, some configuration changes may be required by users switching to \fBnutdrv_qx\fR\&.
.sp
Part of this, the following voltronic options, in \fBups.conf\fR(5), have to be changed:
.PP
\fBondelay\fR
.RS4
While the previous voltronic drivers expected minutes, the new
\fBnutdrv_qx\fR
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\&.
.RE
.PP
\fBbattnumb\fR
.RS4
This option has been renamed to
\fBbattery_number\fR\&.
.RE
.sp
The following options are no longer supported by this driver, you can now change them more conveniently \(oqon the fly\(cq calling \fBupsrw\fR(8) with the appropriate NUT variable \- provided that your UPS supports them\&.
.TS
tab(:);
lt lt
lt lt
lt lt
lt lt
lt lt
lt lt
lt lt
lt lt
lt lt
lt lt
lt lt
lt lt
lt lt
lt lt
lt lt
lt lt.
T{
.sp
\fBbattpacks\fR
T}:T{
.sp
→ \fBbattery\&.packs\fR
.sp
Set number of battery packs in parallel [1\&.\&.99]\&. This setting will change the charge and runtime estimation reported by the UPS\&.
T}
T{
.sp
\fBbattlow\fR
T}:T{
.sp
→ \fBbattery\&.voltage\&.low\fR
.sp
Set minimum battery voltage just before the UPS automatically shuts down\&. This setting will change the charge and runtime estimation reported by the UPS\&.
T}
T{
.sp
\fBauto_reboot\fR
T}:T{
.sp
→ \fBups\&.start\&.auto\fR
.sp
Enable or disable auto reboot [enabled/disabled]\&. If enabled, the UPS will auto recover when AC power returns\&.
T}
T{
.sp
\fBbattery_protection\fR
T}:T{
.sp
→ \fBbattery\&.protection\fR
.sp
Enable or disable battery deep discharge protection [enabled/disabled]\&.
T}
T{
.sp
\fBenergy_saving\fR
T}:T{
.sp
→ \fBbattery\&.energysave\fR
.sp
Enable or disable Green power function [enabled/disabled]\&. If enabled, for energy saving, the UPS will auto off when there is no load\&.
T}
T{
.sp
\fBcold_start\fR
T}:T{
.sp
→ \fBups\&.start\&.battery\fR
.sp
Enable or disable Cold Start [enabled/disabled]\&. If enabled, the UPS can be turned on also if AC is not connected to the UPS\&.
T}
T{
.sp
\fBoutlet_control\fR
T}:T{
.sp
→ \fBoutlet\&.0\&.switchable\fR
.sp
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 \fBoutlet\&.\fR{\fB1\fR,\fB2\fR,\fB3\fR,\fB4\fR}\fB\&.delay\&.shutdown\fR) arrives\&. If disabled, the UPS will provide continuous power to programmable outlets until the battery is running out\&.
T}
T{
.sp
\fBmax_eco_volt\fR
T}:T{
.sp
→ \fBinput\&.transfer\&.high\fR
.sp
Maximum voltage for ECO Mode (V)\&. If AC voltage is within acceptable range, ECO mode will be used (If the UPS is capable of and it\(cqs enabled)\&.
T}
T{
.sp
\fBmin_eco_volt\fR
T}:T{
.sp
→ \fBinput\&.transfer\&.low\fR
.sp
Minimum voltage for ECO Mode (V)\&. If AC voltage is within acceptable range, ECO mode will be used (If the UPS is capable of and it\(cqs enabled)\&.
T}
T{
.sp
\fBmax_eco_freq\fR
T}:T{
.sp
→ \fBinput\&.frequency\&.high\fR
.sp
Maximum frequency for ECO Mode (Hz)\&. If AC frequency is within acceptable range, ECO mode will be used (If the UPS is capable of and it\(cqs enabled)\&.
T}
T{
.sp
\fBmin_eco_freq\fR
T}:T{
.sp
→ \fBinput\&.frequency\&.low\fR
.sp
Minimum frequency for ECO Mode (Hz)\&. If AC frequency is within acceptable range, ECO mode will be used (If the UPS is capable of and it\(cqs enabled)\&.
T}
T{
.sp
\fBoutlet1_delay\fR
T}:T{
.sp
→ \fBoutlet\&.1\&.delay\&.shutdown\fR
.sp
Delay time before programmable outlet 1 shuts down the load when on battery mode [0\&.\&.59940] (seconds)\&.
T}
T{
.sp
\fBoutlet2_delay\fR
T}:T{
.sp
→ \fBoutlet\&.2\&.delay\&.shutdown\fR
.sp
Delay time before programmable outlet 2 shuts down the load when on battery mode [0\&.\&.59940] (seconds)\&.
T}
T{
.sp
\fBoutlet3_delay\fR
T}:T{
.sp
→ \fBoutlet\&.3\&.delay\&.shutdown\fR
.sp
Delay time before programmable outlet 3 shuts down the load when on battery mode [0\&.\&.59940] (seconds)\&.
T}
T{
.sp
\fBoutlet4_delay\fR
T}:T{
.sp
→ \fBoutlet\&.4\&.delay\&.shutdown\fR
.sp
Delay time before programmable outlet 4 shuts down the load when on battery mode [0\&.\&.59940] (seconds)\&.
T}
T{
.sp
\fBbatt_type\fR
T}:T{
.sp
→ \fBbattery\&.type\fR
.sp
Battery type (for P31 UPSes only) [Li/Flooded/AGM]\&.
T}
.TE
.sp1
.SH"KNOWN PROBLEMS"
.sp
Some UPS commands aren\(cqt supported by all models\&. In most cases, the driver will send a message to the system log when the user tries to execute an unsupported command\&. Unfortunately, some models don\(cqt even provide a way for the driver to check for this, so the unsupported commands will silently fail\&.
.sp
Both the \fBload\&.off\fR and \fBshutdown\&.stayoff\fR instant commands are meant to turn the load off indefinitely\&. However, some UPS models don\(cqt allow this\&.
.sp
Some models report a bogus value for the beeper status (will always be \fIenabled\fR or \fIdisabled\fR)\&. So, the \fBbeeper\&.toggle\fR command may appear to have no effect in the status reported by the driver when, in fact, it is working fine\&.
.sp
The temperature and load value is known to be bogus in some models\&.
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 \fBload\&.off\fR and \fBshutdown\&.stayoff\fR 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\&.
.sp
After issuing a \fBshutdown\&.return\fR instant command, the UPS won\(cqt wait \fBondelay\fR before powering on the load, provided the following conditions are met:
.sp
.RS4
.ien\{\
\h'-04'\(bu\h'+03'\c
.\}
.el\{\
.sp-1
.IP\(bu2.3
.\}
if the load has been previously (no matter how long before) powered off through
\fBshutdown\&.return\fR, \fBload\&.off\fR, and \fBshutdown\&.stayoff\fR 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 \fIvoltronic\fR 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)\&.
.sp
.it1an-trap
.nran-no-space-flag1
.nran-break-flag1
.br
.BTable\\&1.\\&UPSWarningsfor\fIvoltronic\fRUPSes
.TS
allbox tab(:);
rtB ltB.
T{
#
T}:T{
Corresponding Warning
T}
.T&
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt
rt lt.
T{
.sp
1
T}:T{
.sp
Battery disconnected
T}
T{
.sp
2
T}:T{
.sp
Neutral not connected
T}
T{
.sp
3
T}:T{
.sp
Site fault
T}
T{
.sp
4
T}:T{
.sp
Phase sequence incorrect
T}
T{
.sp
5
T}:T{
.sp
Phase sequence incorrect in bypass
T}
T{
.sp
6
T}:T{
.sp
Input frequency unstable in bypass
T}
T{
.sp
7
T}:T{
.sp
Battery overcharged
T}
T{
.sp
8
T}:T{
.sp
Low battery
T}
T{
.sp
9
T}:T{
.sp
Overload alarm
T}
T{
.sp
10
T}:T{
.sp
Fan alarm
T}
T{
.sp
11
T}:T{
.sp
EPO enabled
T}
T{
.sp
12
T}:T{
.sp
Unable to turn on UPS
T}
T{
.sp
13
T}:T{
.sp
Over temperature alarm
T}
T{
.sp
14
T}:T{
.sp
Charger alarm
T}
T{
.sp
15
T}:T{
.sp
Remote auto shutdown
T}
T{
.sp
16
T}:T{
.sp
L1 input fuse not working
T}
T{
.sp
17
T}:T{
.sp
L2 input fuse not working
T}
T{
.sp
18
T}:T{
.sp
L3 input fuse not working
T}
T{
.sp
19
T}:T{
.sp
Positive PFC abnormal in L1
T}
T{
.sp
20
T}:T{
.sp
Negative PFC abnormal in L1
T}
T{
.sp
21
T}:T{
.sp
Positive PFC abnormal in L2
T}
T{
.sp
22
T}:T{
.sp
Negative PFC abnormal in L2
T}
T{
.sp
23
T}:T{
.sp
Positive PFC abnormal in L3
T}
T{
.sp
24
T}:T{
.sp
Negative PFC abnormal in L3
T}
T{
.sp
25
T}:T{
.sp
Abnormal in CAN\-bus communication
T}
T{
.sp
26
T}:T{
.sp
Abnormal in synchronous signal circuit
T}
T{
.sp
27
T}:T{
.sp
Abnormal in synchronous pulse signal circuit
T}
T{
.sp
28
T}:T{
.sp
Abnormal in host signal circuit
T}
T{
.sp
29
T}:T{
.sp
Male connector of parallel cable not connected well
T}
T{
.sp
30
T}:T{
.sp
Female connector of parallel cable not connected well
T}
T{
.sp
31
T}:T{
.sp
Parallel cable not connected well
T}
T{
.sp
32
T}:T{
.sp
Battery connection not consistent in parallel systems
T}
T{
.sp
33
T}:T{
.sp
AC connection not consistent in parallel systems
T}
T{
.sp
34
T}:T{
.sp
Bypass connection not consistent in parallel systems
T}
T{
.sp
35
T}:T{
.sp
UPS model types not consistent in parallel systems
T}
T{
.sp
36
T}:T{
.sp
Capacity of UPSs not consistent in parallel systems
T}
T{
.sp
37
T}:T{
.sp
Auto restart setting not consistent in parallel systems
T}
T{
.sp
38
T}:T{
.sp
Battery cell over charge
T}
T{
.sp
39
T}:T{
.sp
Battery protection setting not consistent in parallel systems
T}
T{
.sp
40
T}:T{
.sp
Battery detection setting not consistent in parallel systems
T}
T{
.sp
41
T}:T{
.sp
Bypass not allowed setting not consistent in parallel systems
T}
T{
.sp
42
T}:T{
.sp
Converter setting not consistent in parallel systems
T}
T{
.sp
43
T}:T{
.sp
High loss point for frequency in bypass mode not consistent in parallel systems
T}
T{
.sp
44
T}:T{
.sp
Low loss point for frequency in bypass mode not consistent in parallel systems
T}
T{
.sp
45
T}:T{
.sp
High loss point for voltage in bypass mode not consistent in parallel systems
T}
T{
.sp
46
T}:T{
.sp
Low loss point for voltage in bypass mode not consistent in parallel systems
T}
T{
.sp
47
T}:T{
.sp
High loss point for frequency in AC mode not consistent in parallel systems
T}
T{
.sp
48
T}:T{
.sp
Low loss point for frequency in AC mode not consistent in parallel systems
T}
T{
.sp
49
T}:T{
.sp
High loss point for voltage in AC mode not consistent in parallel systems
T}
T{
.sp
50
T}:T{
.sp
Low loss point for voltage in AC mode not consistent in parallel systems
T}
T{
.sp
51
T}:T{
.sp
Warning for locking in bypass mode after 3 consecutive overloads within 30 min
T}
T{
.sp
52
T}:T{
.sp
Warning for three\-phase AC input current unbalance
T}
T{
.sp
53
T}:T{
.sp
Warning for a three\-phase input current unbalance detected in battery mode
