Network UPS Tools - IRT-3K-2U

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

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

Report #1 with driver nutdrv_qx (detailed comments available)

This device is known to 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.charge	`100`
battery.voltage	`2.29`
battery.voltage.high	`78.00`
battery.voltage.low	`62.40`
battery.voltage.nominal	`72.0`
device.mfr	`UPSONIC`
device.model	`IRT-3K 2U`
device.type	`ups`
driver.name	`nutdrv_qx_cyber`
driver.parameter.pollfreq	`30`
driver.parameter.pollinterval	`2`
driver.parameter.port	`auto`
driver.parameter.synchronous	`no`
driver.version	`2.7.4`
driver.version.data	`Upsonic 0.06`
driver.version.internal	`0.28`
input.current.nominal	`14.0`
input.frequency	`49.9`
input.frequency.nominal	`50`
input.voltage	`229.0`
input.voltage.fault	`120.0`
input.voltage.nominal	`240`
output.voltage	`240.0`
ups.beeper.status	`enabled`
ups.delay.shutdown	`30`
ups.delay.start	`180`
ups.firmware	`MP001155`
ups.load	`49`
ups.productid	`0000`
ups.status	`OL`
ups.temperature	`20.0`
ups.type	`online`
ups.vendorid	`ffff`

About this device

Reported at:

Further system data or configuration example:

Data sample

My UPS, model "UPSONIC IRT-3K 2U" is about 10 years old.
The equivalent current model appears to be
https://www.upsonic.com.au/upsonic-esart-rack-or-tower-series-ups/

With NUT 2.7.4 it is subject to the protocol issue (replies not terminated
by CR) which should be addressed with NUT 2.8.0 release. It also worked
previously with NUT 2.4.3-1ubuntu3.2 and `megatec_usb` driver which was
not as strict about the protocol nuances as NUT 2.7.4.

Packages:

cyber@light:~$ dpkg-query -W nut* nut-cgi nut-client 2.7.4-13 nut-ipmi nut-monitor nut-server 2.7.4-13 nut-snmp nut-xml