salut Jean,<br><br><div class="gmail_quote">2009/5/17 Jean Delvare <span dir="ltr"><<a href="mailto:khali@linux-fr.org" target="_blank">khali@linux-fr.org</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>On Sat, 16 May 2009 22:34:34 +0200, Arnaud Quette wrote:<br>
> 2009/5/16 Jean Delvare <<a href="mailto:khali@linux-fr.org" target="_blank">khali@linux-fr.org</a>><br>
</div><div><div></div><div>> > I see the following:<br>
> ><br>
> > Path: UPS.Battery.Test, Type: Input, ReportID: 0x16, Offset: 0, Size: 8,<br>
> > Value: 6.000000<br>
> > Path: UPS.Battery.Test, Type: Feature, ReportID: 0x16, Offset: 0, Size: 8,<br>
> > Value: 6.000000<br>
> ><br>
> > but as far as I can see this is already mapped to ups.test.result,<br>
> > which shows in the output of upsc as:<br>
> ><br>
> > ups.test.result: No test initiated<br>
><br>
> right. the only thing I see is through the unresolved paths (ie containing<br>
> ff86xxxx)<br>
><br>
> the most interesting are these:<br>
> Path: UPS.Battery.ff86001a, Type: Feature, ReportID: 0x1b, Offset: 0, Size:<br>
> 8, Value: 0.000000<br>
> Path: UPS.Battery.ff86001b, Type: Feature, ReportID: 0x1c, Offset: 0, Size:<br>
> 8, Value: 0.000000<br>
> Path: UPS.Battery.ff860024, Type: Feature, ReportID: 0x47, Offset: 0, Size:<br>
> 8, Value: 251.000000<br>
> Path: UPS.Battery.ff860018, Type: Feature, ReportID: 0x48, Offset: 0, Size:<br>
> 32, Value: -1592617470.000000<br>
> Path: UPS.ff860027, Type: Feature, ReportID: 0x3e, Offset: 0, Size: 32,<br>
> Value: 0.000000<br>
> Path: UPS.ff860028, Type: Feature, ReportID: 0x3f, Offset: 0, Size: 32,<br>
> Value: 0.000000<br>
> Path: UPS.ff860001.ff860023, Type: Feature, ReportID: 0x60, Offset: 0, Size:<br>
> 16, Value: 0.000000<br>
> Path: UPS.ff860001.ff860026, Type: Feature, ReportID: 0x61, Offset: 0, Size:<br>
> 8, Value: 134.000000<br>
> Path: UPS.ff860001.ff860025, Type: Feature, ReportID: 0x62, Offset: 0, Size:<br>
> 32, Value: 50462976.000000<br>
><br>
> but these should also be resolved:<br>
> Path: UPS.PowerSummary.PresentStatus.ff860080, Type: Input, ReportID: 0x07,<br>
> Offset: 12, Size: 1, Value: 0.000000<br>
> Path: UPS.PowerSummary.PresentStatus.ff860080, Type: Feature, ReportID:<br>
> 0x07, Offset: 12, Size: 1, Value: 0.000000<br>
> Path: UPS.Input.ff860052, Type: Feature, ReportID: 0x21, Offset: 0, Size: 8,<br>
> Value: 8.000000<br>
> Path: UPS.Input.ff860061, Type: Feature, ReportID: 0x22, Offset: 0, Size: 8,<br>
> Value: 1.000000<br>
> Path: UPS.Input.ff860024, Type: Feature, ReportID: 0x42, Offset: 0, Size: 8,<br>
> Value: 119.000000<br>
> Path: UPS.PresentStatus.ff860080, Type: Feature, ReportID: 0x33, Offset: 12,<br>
> Size: 1, Value: 0.000000<br>
> Path: UPS.PowerConverter.ff860024, Type: Feature, ReportID: 0x51, Offset: 0,<br>
> Size: 8, Value: 124.000000<br>
><br>
> there are 2 (complementary) ways to guess what these are:<br>
> - (I just found that one) look at apcupsd/examples/rpt/ and grep for ff86<br>
> then try to guess<br>
<br>
</div></div>I took a look at these files but I don't understand what I am supposed<br>
<div>to "guess"?</div></blockquote><div><br>well, you're supposed to guess what to guess ;-)<br>ahah, hem, well to be serious, the game is to identify the report used when doing a battery test.<br>
so the best would be to only fire usbsnoop when doing that, in order to find the frame more easily and the matching report.<br><br></div></div>cheers<br>Arnaud<br>-- <br>Linux / Unix Expert R&D - Eaton - <a href="http://www.eaton.com/mgeops" target="_blank">http://www.eaton.com/mgeops</a><br>
Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org/" target="_blank">http://www.networkupstools.org/</a><br>
Debian Developer - <a href="http://www.debian.org" target="_blank">http://www.debian.org</a><br>Free Software Developer - <a href="http://arnaud.quette.free.fr/" target="_blank">http://arnaud.quette.free.fr/</a><br>