search for: alarm_desc

...meter in the UPS meter block */ > } BCMXCP_METER_MAP_ENTRY_t; > > -BCMXCP_METER_MAP_ENTRY_t > +extern BCMXCP_METER_MAP_ENTRY_t > bcmxcp_meter_map[BCMXCP_METER_MAP_MAX]; > > typedef struct { /* Entry in BCM/XCP - UPS mapping table */ > @@ -366,7 +366,7 @@ > const char *alarm_desc; /* Description of this alarm */ > } BCMXCP_ALARM_MAP_ENTRY_t; > > -BCMXCP_ALARM_MAP_ENTRY_t > +extern BCMXCP_ALARM_MAP_ENTRY_t > bcmxcp_alarm_map[BCMXCP_ALARM_MAP_MAX]; > > typedef struct { /* A place to store status info and other data not for NUT */ > @@ -378,7 +3...

...se, and the UPS signals 'Building Alarm 1'. I have browsed the NUT source code, and it appears that the driver itself can detect this. But it also appears that there is a commented-out alarm_init() stub function: drivers/bcmxcp.c ... bcmxcp_alarm_map[BCMXCP_ALARM_BUILDING_ALARM_1].alarm_desc = "BUILDING_ALARM_1"; ... /* alarm_init(); Alarms are not supported by NUT */ I browsed the docs: docs/new-drivers.txt: There is no official list of alarm words as of this writing, so don't use these functions until you check with the upsdev list. So I am checking with...