[Nut-upsuser] Eaton Powerware 5110 - some stats not reported

Sun Feb 16 06:15:04 UTC 2014

Hi

In the summer of 2013, I spent some time reading the bcmxcp spec, and I
tried to map every possibly supported meter to a "upsc supported
variable".
Some bcmxcp meters I was not able to map, and some "upsc supported
variable" I was not able to map.

This shows what "measurements / meters" the driver support.
   0.566550    Index   
Offset    Format    NUT
   0.566617    0027   
0000    51    output.frequency
   0.566680    0028   
0004    51    input.frequency
   0.566743    0033   
0008    51    battery.voltage
   0.566805    0041   
0012    f0    battery.voltage.low
   0.566866    0043   
0016    f0    battery.charge.low
   0.566928    0047   
0020    f0    ups.load
   0.566989    0056   
0024    f0    input.voltage
   0.567051    0065   
0028    51    output.current
   0.567113    0068   
0032    51    output.current.nominal
   0.567175    0078   
0036    f0    output.voltage
   0.567237    0091   
0040    f0    input.quality
   0.567294   

This shows what alarms the unit will trigger
   0.567355    Length of alarm map: 24
   0.567414    Index   
Alarm    Supported
   0.567509    -001   
INVERTER_AC_OVER_VOLTAGE    No
   0.567573    -001   
INVERTER_AC_UNDER_VOLTAGE    No
   0.567634    -001   
INVERTER_OVER_OR_UNDER_FREQ    No
   0.567695    -001   
BYPASS_AC_OVER_VOLTAGE    No
...

   0.576274    -001   
BYPASS_FAILURE    No
   0.576305    -001   
AUTO_OFF_COMMAND_EXECUTED    No
   0.576335    -001   
AUTO_ON_COMMAND_EXECUTED    No
   0.576366    0010   
BATTERY_TEST_FAILED    Yes
   0.576396   

This is some useful info, I would like to know what models
supports statistics map and alarm history log. My new 9130 has
"alarm history", but it is not available using the
"bcmxcp" driver.
   0.576427    Length of Config_block: 64
   0.576458    Length of statistics map: 0
   0.576489    Length of alarm history log: 0
   0.576519    Length of topology block: 3
   0.576550    Length of max supported command
length: 8
   0.576581    Length of command list: 22
   0.576611    Length of outlet_block: 0
   0.576642    Length of alarm_block: 11

This shows what "commands" the UPS supports.
   0.853277    Command list block supported.
   0.853340    Number of commands implemented in
ups 20
   0.853400    Index    Cmd
byte    Description
   0.853466    000   
31    PW_ID_BLOCK_REQ
   0.853528    001   
33    PW_STATUS_REQ
   0.853590    002   
34    PW_METER_BLOCK_REQ
   0.853652    003   
35    PW_CUR_ALARM_REQ
   0.853714    004   
36    PW_CONFIG_BLOCK_REQ
   0.853775    005   
3b    PW_BATTERY_REQ
   0.853837    006   
3c    PW_LIMIT_BLOCK_REQ
   0.853898    007   
3f    PW_TEST_RESULT_REQ
   0.854022    008   
40    PW_COMMAND_LIST_REQ
   0.854085    009   
43    PW_UPS_TOP_DATA_REQ
   0.854147    010   
89    PW_UPS_ON
   0.854209    011   
8a    PW_LOAD_OFF_RESTART
   0.854270    012   
8b    PW_UPS_OFF
   0.854332    013   
91    PW_UPS_ON_TIME
   0.854394    014   
93    PW_UPS_OFF_TIME
   0.854480    015   
95    PW_SET_CONF_COMMAND
   0.854544    016   
a0    PW_SET_REQ_ONLY_MODE
   0.854605    017   
b1    PW_INIT_BAT_TEST
   0.854668    018   
b2    PW_INIT_SYS_TEST
   0.854730    019   
cf    PW_AUTHORIZATION_CODE
   0.854803    Added support for instcmd
shutdown.return
   0.854874    Added support for instcmd
shutdown.stayoff
   0.854944    Added support for instcmd
test.battery.start

The bcmxcp supports "set / get" commands according to the bcmxcp
spec, it was next on my list for enhancing the driver, but I have not had
time to do so.
That would add support for settings to "upsrw" and
"upscmd".
I seem to remember that the "PW_SET_CONF_COMMAND" is needed for
"setting variable values". It is all quite well documented in
the protocol documentation.

This is what I have as output from a previous debug log of my 5110 500VA
:
   0.413194    Index   
Offset    Format    NUT
   0.413200    0027   
0000    51    output.frequency
   0.413206    0028   
0004    51    input.frequency
   0.413212    0033   
0008    51    battery.voltage
   0.413218    0041   
0012    f0    battery.voltage.low
   0.413224    0043   
0016    f0    battery.charge.low
   0.413229    0047   
0020    f0    ups.load
   0.413235    0056   
0024    f0    input.voltage
   0.413241    0065   
0028    51    output.current
   0.413246    0068   
0032    51    output.current.nominal
   0.413252    0078   
0036    f0    output.voltage
   0.413258    0091   
0040    f0    input.quality
That unit died last autumn, so I no longer have it availble.

This is what I get from my new Eaton PW 9130:
   1.081608    Index   
Offset    Format    NUT
   1.081621    0021   
0000    f0    None
   1.081632    0023   
0004    f0    ups.power
   1.081642    0027   
0008    41    output.frequency
   1.081652    0028   
0012    41    input.frequency
   1.081662    0030   
0016    41    None
   1.081671    0033   
0020    51    battery.voltage
   1.081681    0034   
0024    f0    battery.charge
   1.081691    0035   
0028    e2    battery.runtime
   1.081700    0047   
0032    f0    ups.load
   1.081710    0053   
0036    51    None
   1.081720    0056   
0040    51    input.voltage
   1.081729    0062   
0044    f0    ambient.temperature
   1.081739    0063   
0048    f0    ups.temperature
   1.081749    0065   
0052    41    output.current
   1.081758    0068   
0056    41    output.current.nominal
   1.081768    0071   
0060    f0    None
   1.081777    0072   
0064    e0    ups.date
   1.081787    0073   
0068    e1    ups.time
   1.081796    0074   
0072    51    None
   1.081806    0075   
0076    51    None
   1.081816    0078   
0080    51    output.voltage
   1.081825    0091   
0084    f0    input.quality
Regards
Alf

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140216/c6187f77/attachment-0001.html>