search for: pw_status_req

...example ' a ups that don't support battery_test would not have this command enabled.' The hex responce look like this from a PW3105: 0c <-- first byte is the number of commands (12) 01 <-- How many bytes reported below for each command 31 <-- PW_ID_BLOCK_REQ 33 <-- PW_STATUS_REQ 34 <-- PW_METER_BLOCK_REQ 35 <-- PW_CUR_ALARM_REQ 36 <-- PW_CONFIG_BLOC_REQ 3c <-- PW_LIMIT_BLOCK_REQ 40 <-- PW_COMMAND_LIST_REQ (this command) 43 <-- PW_UPS_TOP_DATA_REQ 8a <-- PW_LOAD_OFF_RESTART 8b <-- PW_UPS_OFF a0 <-- PW_SET_REQ_ONLY_MODE cf <...

The meter map is basically a bitmap that indicates what variables are output (and in what format) by the UPS. You will likely see a variable, 'not mapped' or nothing. The variables and 'not mapped' items are output by the UPS in the measurement block, and the map tells nut how to read it. 'Unmapped' means that there is a variable there that nut is ignoring, and the xcp