Network UPS Tools
Power Devices support
Table of Contents

Click here to see reports of other supported models from GE Digital Energy.

Note

When a user reports that a variable/command is not right then it will be highlighted by a red underline.

Bad values/ranges/etc… will get a red dashed outline or red solid left border.

The accompanying explaining comment - if provided - will be emphasized through a red dotted border on the left.

2.6.0

Report #1 with driver blazer_ser (detailed comments available)

This device is known to work with driver blazer_ser. It may also work with driver nutdrv_qx.

You can grab a dummy-ups compliant .dev file to simulate this device clicking here.

Some more detailed comments are available after the "Known supported…" sections.

Known supported variables

This device is known to support the following variables (values are just examples):

battery.voltage

252.00

battery.voltage.nominal

240.0

beeper.status

disabled

device.type

ups

driver.name

blazer_ser

driver.parameter.cablepower

none

driver.parameter.pollinterval

2

driver.parameter.port

/dev/ttyS0

driver.version

2.6.0

driver.version.internal

1.51

input.current.nominal

27.0

input.frequency

50.0

input.frequency.nominal

50

input.voltage

236.0

input.voltage.fault

140.0

input.voltage.nominal

220

output.voltage

220.0

ups.delay.shutdown

30

ups.delay.start

180

ups.load

1

ups.status

OL

ups.temperature

31.5

ups.type

online

About this device

Reported at:

Report #2 with driver blazer_usb (detailed comments available)

This device is known to work with driver blazer_usb. It may also work with driver nutdrv_qx.

You can grab a dummy-ups compliant .dev file to simulate this device clicking here.

Some more detailed comments are available after the "Known supported…" sections.

Known supported variables

This device is known to support the following variables (values are just examples):

battery.voltage

272.40

battery.voltage.nominal

240.0

beeper.status

disabled

device.type

ups

driver.name

blazer_usb

driver.parameter.bus

004

driver.parameter.pollinterval

2

driver.parameter.port

auto

driver.version

2.6.0

driver.version.internal

0.03

input.current.nominal

27.0

input.frequency

50.0

input.frequency.nominal

50

input.voltage

233.0

input.voltage.fault

140.0

input.voltage.nominal

220

output.voltage

220.0

ups.delay.shutdown

30

ups.delay.start

180

ups.load

2

ups.productid

00c9

ups.status

OL

ups.temperature

32.0

ups.type

online

ups.vendorid

14f0

Known supported commands

This device is known to support the following NUT’s instant commands:

  • beeper.toggle

    Returns OK, but seems to have no effect

  • load.off

    Returns OK, but seems to have no effect

  • load.on

    Returns OK, but seems to have no effect

  • shutdown.return

    Returns OK, but seems to have no effect

  • shutdown.stayoff

    Returns OK, but seems to have no effect

  • shutdown.stop

    Returns OK, but seems to have no effect

  • test.battery.start

    Returns OK, starts a test, UPS status changes to OL CAL (didn’t wait for the test to finish)

  • test.battery.start.deep

    Returns OK, starts a test, UPS status changes to OL CAL (didn’t wait for the test to finish)

  • test.battery.start.quick

    Returns OK, starts a test, UPS status changes to OL CAL for a short time

  • test.battery.stop

    Returns OK, stops a test, UPS status changes back to OL

About this device

Issuing several test.battery.start* commands without test.battery.stop kills USB communication. The UPS needs to be disconnected and re-connected to USB before communication can be re-established.

Reported at: