search for: lcmalarm

...oval: found !replacebatt (value: 0) 32.407369 process_boolean_info: !replacebatt There is also this LCM (Life Cycle Monitoring) part: 22.677035 hid_lookup_path: 00840004 -> UPS 22.677037 hid_lookup_path: ffff0018 -> LCMSystem 22.677039 hid_lookup_path: ffff001a -> LCMAlarm 22.677045 hid_lookup_path: 00ff0001 -> not found in lookup table 22.677049 hid_lookup_path: 00840002 -> PresentStatus 22.677052 hid_lookup_path: ffff0093 -> TimerExpired 22.677055 Path: UPS.LCMSystem.LCMAlarm.[1].PresentStatus.TimerExpired, Type: Feature, ReportID:...

On 28 May 2014, at 21:59, Charles Lepple <clepple at gmail.com> wrote: >> What would log it? > > The driver. OK. >> I could try running the driver with debugging and see if that shows anything of interest. > > That should help. Unfortunately for non-debug operation, it appears that most of the usbhid-ups instcmd messages are buried at debug level 3 or 5. That

...71, Offset: 192, Size: 16, Value: 0 5.473392 Path: UPS.HistorySystem.Event.[14].Code, Type: Feature, ReportID: 0x71, Offset: 208, Size: 16, Value: 0 5.473399 Path: UPS.HistorySystem.Event.[15].Code, Type: Feature, ReportID: 0x71, Offset: 224, Size: 16, Value: 0 5.498223 Path: UPS.LCMSystem.LCMAlarm.[1].Count, Type: Feature, ReportID: 0x51, Offset: 0, Size: 8, Value: 0 5.537897 Path: UPS.LCMSystem.LCMAlarm.[1].Interval, Type: Feature, ReportID: 0x54, Offset: 0, Size: 32, Value: 2.592e+06 5.572599 Path: UPS.LCMSystem.LCMAlarm.[1].LCMAlarmID, Type: Feature, ReportID: 0x50, Offset: 0, Size:...