1BLAZER(8) NUT Manual BLAZER(8)
2
6 blazer - Driver for Megatec/Q1 protocol serial (blazer_ser) and USB
7 (blazer_usb) based UPS equipment
8
10 This man page only documents the hardware-specific features of the
11 blazer driver. For information about the core driver, see nutupsdrv(8).
12
14 The blazer driver is known to work with various UPSes from Blazer,
15 Energy Sistem, Fenton Technologies, Mustek and many others. The NUT
16 compatibility table lists all the known supported models. Keep in mind,
17 however, that other models not listed there may also be supported, but
18 haven’t been tested.
19 All devices with a serial interface (use the blazer_ser driver) and
21 many with a USB interface (use the blazer_usb driver) are supported.
22
24 You may need to override or provide defaults for some values, depending
25 on the make and model of your UPS. The following are the ones that most
26 likely will need changing (see ups.conf(5)):
27 default.battery.voltage.high = value
29 Maximum battery voltage that is reached after about 12 to 24 hours
30 charging. If you want the driver to report a guesstimated
31 battery.charge, you need to specify this (see BATTERY CHARGE).
32 default.battery.voltage.low = value
34 Minimum battery voltage just before the UPS automatically shuts
35 down. If you want the driver to report a guesstimated
36 battery.charge, you need to specify this (see BATTERY CHARGE).
37 default.battery.voltage.nominal = value,
39 override.battery.voltage.nominal = value
40 Some devices show a wrong nominal battery voltage (or none at all),
41 so you may need to override or set a default value.
42 override.battery.packs = value
44 Some devices report a part of the total battery voltage. For
45 instance, if battery.voltage.nominal is 24 V, but it reports a
46 battery.voltage of around 2 V, the number of battery.packs to
47 correct this reading would be 12. The driver will attempt to detect
48 this automatically, but if this fails somehow, you may want to
49 override this value.
50 ondelay = value
52 Time to wait before switching on the UPS (minutes). Note that a
53 value below 3 minutes, may cause earlier firmware versions to not
54 switch on automatically, so it defaults to 3 minutes.
55 offdelay = value
57 Time to wait before shutting down the UPS (seconds). This value is
58 truncated to units of 6 seconds (less than 60 seconds) or 60
59 seconds (more than 60 seconds). Defaults to 30 seconds.
60 norating
62 Some UPSes will lock up if you attempt to read rating information
63 from them. Setting this flag will make the driver skip this step.
64 novendor
66 Some UPSes will lock up if you attempt to read vendor information
67 from them. Setting this flag will make the driver skip this step.
68 protocol = string
70 Skip autodetection of the protocol to use and only use the one
71 specified. Supported values megatec, megatec/old, mustek and zinto.
72 runtimecal = value,value,value,value
74 Parameter used in the (optional) runtime estimation. This takes two
75 runtimes at different loads. Typically, this uses the runtime at
76 full load and the runtime at half load. For instance, if your UPS
77 has a rated runtime of 240 seconds at full load and 720 seconds at
78 half load, you would enter
79 runtimecal = 270,100,720,50
81 The first load should always be higher than the second. If you have
83 values available for loads other than 100 and 50 % respectively,
84 you can use those too, but keep them spaced apart as far as
85 reasonably possible. Just don’t get too close to no load
86 (prediction of runtime depends more on idle load for the battery
87 then).
88 chargetime = value
90 The time needed to fully recharge the battery after being fully
91 discharged. If not specified, the driver defaults to 43200 seconds
92 (12 hours). Only used if runtimecal is also specified.
93 idleload = value
95 Minimum battery load used by the driver to estimate the runtime. If
96 not specified, the driver defaults to 10%. Only used if runtimecal
97 is also specified.
98
100 cablepower = string
101 By default the driver will set DTR and clear RTS (normal). If you
102 find that your UPS isn’t detected or the communication with the UPS
103 is unreliable, you may try if clear DTR and set RTS (reverse), set
104 DTR and RTS (both) or clear DTR and RTS (none) improves this
105 situation.
106
108 vendorid = regex, productid = regex, vendor = regex, product = regex,
109 serial = regex
110 Select a specific UPS, in case there is more than one connected via
111 USB. Each option specifies an extended regular expression (see
112 regex(7)) that must match the UPS’s entire vendor/product/serial
113 string (minus any surrounding whitespace), or the whole 4-digit
114 hexadecimal code for vendorid and productid. Try -DD for finding
115 out the strings to match.
116 Examples:
118 -x vendor="Foo.Corporation.*"
120 -x vendorid=051d # (APC)
122 -x product=".*(Smart|Back)-?UPS.*"
124 bus = regex
126 Select a UPS on a specific USB bus or group of busses. The argument
127 is a regular expression that must match the bus name where the UPS
128 is connected (e.g. bus="002", bus="00[2-3]").
129 subdriver = string
131 Select a serial-over-USB subdriver to use. You have a choice
132 between phoenix, ippon, cypress, and krauler. When using this
133 option, it is mandatory to also specify the vendorid and productid.
134
136 This driver supports some instant commands (see upscmd(8)):
137 beeper.toggle
139 Toggle the UPS beeper. (Not available on some hardware.)
140 load.on
142 Turn on the load immediately.
143 load.off
145 Turn off the load immediately (see KNOWN PROBLEMS).
146 shutdown.return [value]
148 Turn off the load and return when power is back. Uses the timers
149 defined by ondelay and offdelay.
150 shutdown.stayoff [value]
152 Turn off the load and remain off (see KNOWN PROBLEMS). Uses the
153 timer defined by offdelay.
154 shutdown.stop
156 Stop a shutdown in progress.
157 test.battery.start.deep
159 Perform a long battery test (Not available on some hardware.)
160 test.battery.start.quick
162 Perform a (10 second) battery test.
163 test.battery.start value
165 Perform a battery test for the duration of value seconds (truncated
166 to units of 60 seconds).
167 test.battery.stop
169 Stop a running battery test (not available on some hardware.)
170
172 Due to popular demand, this driver will report a guesstimated
173 battery.charge and optionally battery.runtime, provided you specified a
174 couple of the EXTRA ARGUMENTS listed above.
175 If you specify both battery.voltage.high and battery.voltage.low in
177 ups.conf(5), but don’t enter runtimecal, it will guesstimate the state
178 of charge by looking at the battery voltage alone. This is not reliable
179 under load, as this only gives reasonably accurate readings if you
180 disconnect the load, let the battery rest for a couple of minutes and
181 then measure the open cell voltage. This just isn’t practical if the
182 power went out and the UPS is providing power for your systems.
183 battery.voltage - battery.voltage.low
185 battery.charge = ------------------------------------------ x 100 %
186 battery.voltage.high - battery.voltage.low
187 There is a way to get better readings without disconnecting the load
189 but this requires to keep track on how much (and how fast) current is
190 going in- and out of the battery. If you specified the runtimecal, the
191 driver will attempt to do this. Note however, that this heavily relies
192 on the values you enter and that the UPS must be able to report the
193 load as well. There are quite a couple of devices that report 0 % (or
194 any other fixed value) at all times, in which case this obviously
195 doesn’t work.
196 The driver also has no way of determining the degradation of the
198 battery capacity over time, so you’ll have to deal with this yourself
199 (by adjusting the values in runtimecal). Also note that the driver
200 guesses the initial state of charge based on the battery voltage, so
201 this may be less than 100 %, even when you are certain that they are
202 full. There is just no way to reliably measure this between 0 and 100 %
203 full charge.
204 This is better than nothing (but not by much). If any of the above
206 calculations is giving you incorrect readings, you are the one that put
207 in the values in ups.conf(5), so don’t complain with the author. If you
208 need something better, buy a UPS that reports battery.charge and
209 battery.runtime all by itself without the help of a NUT driver.
210
212 The blazer drivers having replaced the megatec ones, some configuration
213 changes may be required by users switching to blazer.
214 Part of this, the following megatec options, in ups.conf, have to be
216 changed:
217 battvolts
219 You need to use default.battery.voltage.high and
220 default.battery.voltage.low
221 dtr and rts
223 You need to use cablepower
224 ignoreoff
226 This parameter can simply be discarded, since it was a wrong
227 understanding of the specification.
228
230 Some UPS commands aren’t supported by all models. In most cases, the
231 driver will send a message to the system log when the user tries to
232 execute an unsupported command. Unfortunately, some models don’t even
233 provide a way for the driver to check for this, so the unsupported
234 commands will silently fail.
235 Both the load.off and shutdown.stayoff instant commands are meant to
237 turn the load off indefinitely. However, some UPS models don’t allow
238 this.
239 Some models report a bogus value for the beeper status (will always be
241 enabled or disabled). So, the beeper.toggle command may appear to have
242 no effect in the status reported by the driver when, in fact, it is
243 working fine.
244 The temperature and load value is known to be bogus in some models.
246
248 Arjen de Korte <adkorte-guest at alioth.debian.org>, Alexander Gordeev
249 <lasaine at lvk.cs.msu.su>
250
252 nutupsdrv(8), upsc(8), upscmd(8), upsrw(8)
253 Internet Resources:
255 The NUT (Network UPS Tools) home page: http://www.networkupstools.org/
256Network UPS Tools 09/15/2011 BLAZER(8)