search for: pw_ups_top_data_req

...(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 <-- Autorisation command So this ups does not need to list unused functions like: batt_test sys_test set_config set_outlet e.t.c when you ask for possible commands. But if you connect a PW5125 it have...

...@ #define PW_COMMAND_LIST_REQ (unsigned char)0x40 /* Available commands. length 1 */ #define PW_OUT_MON_BLOCK_REQ (unsigned char)0x41 /* Outlet monitor request length 1 */ #define PW_COM_CAP_REQ (unsigned char)0x42 /* Request communication capabilities. length 2 */ -#define PW_UPS_TOP_DATA_REQ (unsigned char)0x43 /* Requsest ups topology data requset. length 1 */ +#define PW_UPS_TOP_DATA_REQ (unsigned char)0x43 /* Request ups topology data requset. length 1 */ -/* Need autorisation before this commands */ +/* Need autorisation before these commands */ #define PW_UPS_ON...

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