Network UPS Tools
Power Devices support
Table of Contents

Click here to see reports of other supported models from Powercom.

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.5

Report #1 with driver usbhid-ups (detailed comments available)

This device is known to work with driver usbhid-ups.

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.charge

100

battery.charge.low

10

battery.charge.warning

30

battery.date

2010/01/01

battery.runtime

2432

battery.type

PbAc

device.mfr

POWERCOM Co.,LTD

device.model

UPS IMP--525AP FW3.A2

device.serial

3A2-0000-0001

device.type

ups

driver.name

usbhid-ups

driver.parameter.pollfreq

30

driver.parameter.pollinterval

2

driver.parameter.port

auto

driver.version

2.6.5

driver.version.data

PowerCOM HID 0.3

driver.version.internal

0.37

input.frequency

50.0

input.voltage

230.0

input.voltage.nominal

220

output.frequency

50.0

output.voltage

230.0

output.voltage.nominal

220

ups.beeper.status

enabled

ups.date

2010/01/01

ups.load

0

ups.mfr

POWERCOM Co.,LTD

ups.model

UPS IMP--525AP FW3.A2

ups.productid

00a2

ups.serial

3A2-0000-0001

ups.status

OL

ups.test.result

Done and passed

ups.vendorid

0d9f

Known supported commands

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

  • beeper.toggle

    The beeper is not disabled.

    The ability to disable the beeper had been added by Powercom in 2010 only. So UPS devices built after 2010 should support this option.

    It turned out that according to the UPS serial number it had been manufactured in 2012. So, the device should support the ability to disable the beeper. But still I can not disable the beeper using the latest version of UPSMON Plus in Windows.

    However, beeper can be disabled with the button on the UPS (except when the device starts and the battery capacity is 0 the beeper should/will work); NUT gets the correct value now:

    $ upsc powercom ups.beeper.status
    disabled
  • test.battery.start.quick

2.4.1

Report #1 with driver usbhid-ups (detailed comments available)

This device is known to work with driver usbhid-ups.

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.charge

100

battery.charge.low

10

battery.charge.warning

30

battery.date

2010/01/01

battery.runtime

2432

battery.type

PbAc

device.mfr

POWERCOM Co.,LTD

device.model

UPS IMP--525AP FW2.A2

device.serial

2A2-0000-0001

device.type

ups

driver.name

usbhid-ups

driver.parameter.pollfreq

30

driver.parameter.pollinterval

2

driver.parameter.port

auto

driver.parameter.productid

00a2

driver.parameter.vendorid

0d9f

driver.version

2.4.1-2300

driver.version.data

PowerCOM HID 0.2

driver.version.internal

0.34

input.frequency

50.0

input.voltage

214.0

input.voltage.nominal

220

output.frequency

50.0

output.voltage

214.0

output.voltage.nominal

220

ups.beeper.status

enabled

ups.date

2010/01/01

ups.delay.shutdown

20

ups.delay.start

60

ups.load

3

ups.mfr

POWERCOM Co.,LTD

ups.model

UPS IMP--525AP FW2.A2

ups.productid

00a2

ups.serial

2A2-0000-0001

ups.status

OL

ups.test.result

Done and passed

ups.timer.shutdown

0

ups.timer.start

0

ups.vendorid

0d9f