Displaying 5 results from an estimated 5 matches for "pw_id_block_req".
2007 Sep 19
1
Programming problem.
...use this in the driver. For 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_SE...
2011 Jan 14
2
Fwd: Question about Network UPS Tools bcmxcp driver
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'
in bcmxcp.c ( se my replay).
Kjell
-------------- next part --------------
An embedded message was s...
2011 May 19
2
Scheduling NUT 2.6.1
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 -
2014 Feb 16
1
Eaton Powerware 5110 - some stats not reported
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
2011 Oct 03
2
patch: Replace many usleep and some sleep calls with nanosleep
...er_send_char(upsfd, 0x1d); /* last retry is preceded by a ESC.*/
- usleep(250000);
+ struct timespec delay = {0, 250e6}; nanosleep(&delay, NULL);
}
sent = ser_send_buf(upsfd, sbuf, command_length);
@@ -255,6 +255,7 @@ void pw_comm_setup(const char *port)
unsigned char id_command = PW_ID_BLOCK_REQ;
unsigned char answer[256];
int i = 0, baud, mybaud = 0, ret = -1;
+ struct timespec delay;
if (getval("baud_rate") != NULL)
{
@@ -273,12 +274,14 @@ void pw_comm_setup(const char *port)
ser_set_speed(upsfd, device_path, mybaud);
ser_send_char(upsfd, 0x1d); /* send ESC t...