search for: pw_ups_off_time

...ble in bcmxcp specification : #define PW_UPS_ON .. /* UPS on command. length 1-2 */ #define PW_UPS_ON_TIME .. /* Scheduled UPS on in n minutes. length 3-4 */ #define PW_UPS_ON_AT_TIME .. /* Schedule UPS on at specified date and time. length 7-8 */ #define PW_UPS_OFF_TIME .. /* Scheduled UPS off in n minutes. length 3-4 */ #define PW_UPS_OFF_AT_TIME .. /* Schedule UPS off at specified date and time. length 7-8 */ Possibly I would also like to add support for the following, but this might not make sense : #define PW_GO_TO_BYPASS .. /*...

...following patch is an attempt at doing so. The patch is against the bcmxcp branch. Since my UPS also supports : #define PW_UPS_ON (unsigned char)0x89 /* UPS on command. length 1-2 */ #define PW_UPS_ON_TIME (unsigned char)0x91 /* Scheduled UPS on in n minutes. length 3-4 */ #define PW_UPS_OFF_TIME (unsigned char)0x93 /* Scheduled UPS off in n minutes. length 3-4 */ it is tempting to add support for these as well. But I do not think I have time for that now in the summer. From 0b01612658c1265cb6df8563e0ab7f4d720e8b0f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alf=20H=C3=B8gemark?=...

I've patched bcmxcp.c such that it can power cycle the outlet load segments independently on a Powerware PW5125 UPS. I presume that it will work for any XCP protocol UPS with 2 load segments. Should these instant commands be called outlet.1.shutdown.return outlet.2.shutdown.return ? Where do the descriptions displayed by upscmd -l come from? Presently it shows outlet.1.shutdown.return -

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