On Sat, 16 May 2009 22:34:34 +0200, Arnaud Quette wrote: > 2009/5/16 Jean Delvare <kh...@linux-fr.org> > > I see the following: > > > > Path: UPS.Battery.Test, Type: Input, ReportID: 0x16, Offset: 0, Size: 8, > > Value: 6.000000 > > Path: UPS.Battery.Test, Type: Feature, ReportID: 0x16, Offset: 0, Size: 8, > > Value: 6.000000 > > > > but as far as I can see this is already mapped to ups.test.result, > > which shows in the output of upsc as: > > > > ups.test.result: No test initiated > > right. the only thing I see is through the unresolved paths (ie containing > ff86xxxx) > > the most interesting are these: > Path: UPS.Battery.ff86001a, Type: Feature, ReportID: 0x1b, Offset: 0, Size: > 8, Value: 0.000000 > Path: UPS.Battery.ff86001b, Type: Feature, ReportID: 0x1c, Offset: 0, Size: > 8, Value: 0.000000 > Path: UPS.Battery.ff860024, Type: Feature, ReportID: 0x47, Offset: 0, Size: > 8, Value: 251.000000 > Path: UPS.Battery.ff860018, Type: Feature, ReportID: 0x48, Offset: 0, Size: > 32, Value: -1592617470.000000 > Path: UPS.ff860027, Type: Feature, ReportID: 0x3e, Offset: 0, Size: 32, > Value: 0.000000 > Path: UPS.ff860028, Type: Feature, ReportID: 0x3f, Offset: 0, Size: 32, > Value: 0.000000 > Path: UPS.ff860001.ff860023, Type: Feature, ReportID: 0x60, Offset: 0, Size: > 16, Value: 0.000000 > Path: UPS.ff860001.ff860026, Type: Feature, ReportID: 0x61, Offset: 0, Size: > 8, Value: 134.000000 > Path: UPS.ff860001.ff860025, Type: Feature, ReportID: 0x62, Offset: 0, Size: > 32, Value: 50462976.000000 > > but these should also be resolved: > Path: UPS.PowerSummary.PresentStatus.ff860080, Type: Input, ReportID: 0x07, > Offset: 12, Size: 1, Value: 0.000000 > Path: UPS.PowerSummary.PresentStatus.ff860080, Type: Feature, ReportID: > 0x07, Offset: 12, Size: 1, Value: 0.000000 > Path: UPS.Input.ff860052, Type: Feature, ReportID: 0x21, Offset: 0, Size: 8, > Value: 8.000000 > Path: UPS.Input.ff860061, Type: Feature, ReportID: 0x22, Offset: 0, Size: 8, > Value: 1.000000 > Path: UPS.Input.ff860024, Type: Feature, ReportID: 0x42, Offset: 0, Size: 8, > Value: 119.000000 > Path: UPS.PresentStatus.ff860080, Type: Feature, ReportID: 0x33, Offset: 12, > Size: 1, Value: 0.000000 > Path: UPS.PowerConverter.ff860024, Type: Feature, ReportID: 0x51, Offset: 0, > Size: 8, Value: 124.000000 > > there are 2 (complementary) ways to guess what these are: > - (I just found that one) look at apcupsd/examples/rpt/ and grep for ff86 > then try to guess
I took a look at these files but I don't understand what I am supposed to "guess"? > - usbsnoop on windows and capture the USB frame during ops (like batt. > test). then check it to have the report ID I just did this, I have a 1.5 MB log file including a battery test request. I've made the file available at: http://jdelvare.pck.nerim.net/linux/usbsnoop-apc-back-ups-rs800-battery-test-1.log I've taken a look but so far I am totally clueless as to how I am supposed to match the contents of this log file with the features listed by the usbhid-ups nut driver. Any hint? Thanks, -- Jean Delvare _______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser