search for: timerexpir

...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: 0x5d, Offset: 0, Size: 8, Value: 1 This seems to be setting the RB flag: 65.871141 Path: UPS.LCMSystem.LCMAlarm.[2].PresentStatus.TimerExpired, Type: Feature, ReportID: 0x5d, Offset: 8, S...

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

...e: 2.592e+06 5.572599 Path: UPS.LCMSystem.LCMAlarm.[1].LCMAlarmID, Type: Feature, ReportID: 0x50, Offset: 0, Size: 8, Value: 1 5.606524 Path: UPS.LCMSystem.LCMAlarm.[1].Mode, Type: Feature, ReportID: 0x57, Offset: 0, Size: 8, Value: 0 5.643485 Path: UPS.LCMSystem.LCMAlarm.[1].PresentStatus.TimerExpired, Type: Feature, ReportID: 0x5d, Offset: 0, Size: 8, Value: 1 5.643505 Path: UPS.LCMSystem.LCMAlarm.[1].PresentStatus.TimerExpired, Type: Input, ReportID: 0x5d, Offset: 0, Size: 8, Value: 1 5.681732 Path: UPS.LCMSystem.LCMAlarm.[1].Timer, Type: Feature, ReportID: 0x5a, Offset: 0, Size: 32, V...