search for: pw_set_req_only_mode

...K_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 all the commands listed in bcmxcp.h. It should be some more listed in the bcmxcp.h, like...

Hi, Got this mail. It looks like he has a ups with revision before K, and need another startup. The 'PW_SET_REQ_ONLY_MODE' is not implemented, so to make it work we have to follow the protocol and send a 'PW_ID_BLOCK_REQ'. This in comsetup of bcmxcp_ser.c Also the standard id block ends with 'Statistics Map', so we have to Skip after reading the length of the 'Size of the Alarm History Block...

Fellows, time has come for a new NUT release: I'm planning on 2.6.1 next week (max Friday 27), and I'm currently processing remaining patches. If you have some more on your side, please send in. cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer -

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