<br><div class="gmail_quote">2009/5/16 Jean Delvare <span dir="ltr"><<a href="mailto:khali@linux-fr.org">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;">
Hi Arnaud,<br>
<div class="im"></div></blockquote><div><br>Jean,<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
On Sat, 16 May 2009 13:11:31 +0200, Arnaud Quette wrote:<br>
> no need ATM. just fire the driver using "usbhid-ups -D -a ..." and post back<br>
> the tree dumped.<br>
<br>
</div>Here you go:<br>
<br>
debug level is '1'<br>
upsdrv_initups...<br>
Using subdriver: APC HID 0.93<br>
(...)<div class="im"><br>
> check for a string path that matches battery.test.<br>
<br>
</div>I see the following:<br>
<br>
Path: UPS.Battery.Test, Type: Input, ReportID: 0x16, Offset: 0, Size: 8, Value: 6.000000<br>
Path: UPS.Battery.Test, Type: Feature, ReportID: 0x16, Offset: 0, Size: 8, 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>
<div class="im"></div></blockquote><div><br>right. the only thing I see is through the unresolved paths (ie containing ff86xxxx)<br><br>the most interesting are these:<br>Path: UPS.Battery.ff86001a, Type: Feature, ReportID: 0x1b, Offset: 0, Size: 8, Value: 0.000000<br>
Path: UPS.Battery.ff86001b, Type: Feature, ReportID: 0x1c, Offset: 0, Size: 8, Value: 0.000000<br>Path: UPS.Battery.ff860024, Type: Feature, ReportID: 0x47, Offset: 0, Size: 8, Value: 251.000000<br>Path: UPS.Battery.ff860018, Type: Feature, ReportID: 0x48, Offset: 0, Size: 32, Value: -1592617470.000000<br>
Path: UPS.ff860027, Type: Feature, ReportID: 0x3e, Offset: 0, Size: 32, Value: 0.000000<br>Path: UPS.ff860028, Type: Feature, ReportID: 0x3f, Offset: 0, Size: 32, Value: 0.000000<br>Path: UPS.ff860001.ff860023, Type: Feature, ReportID: 0x60, Offset: 0, Size: 16, Value: 0.000000<br>
Path: UPS.ff860001.ff860026, Type: Feature, ReportID: 0x61, Offset: 0, Size: 8, Value: 134.000000<br>Path: UPS.ff860001.ff860025, Type: Feature, ReportID: 0x62, Offset: 0, Size: 32, Value: 50462976.000000<br><br></div></div>
but these should also be resolved:<br>Path: UPS.PowerSummary.PresentStatus.ff860080, Type: Input, ReportID: 0x07, Offset: 12, Size: 1, Value: 0.000000<br>Path: UPS.PowerSummary.PresentStatus.ff860080, Type: Feature, ReportID: 0x07, Offset: 12, Size: 1, Value: 0.000000<br>
Path: UPS.Input.ff860052, Type: Feature, ReportID: 0x21, Offset: 0, Size: 8, Value: 8.000000<br>Path: UPS.Input.ff860061, Type: Feature, ReportID: 0x22, Offset: 0, Size: 8, Value: 1.000000<br>Path: UPS.Input.ff860024, Type: Feature, ReportID: 0x42, Offset: 0, Size: 8, Value: 119.000000<br>
Path: UPS.PresentStatus.ff860080, Type: Feature, ReportID: 0x33, Offset: 12, Size: 1, Value: 0.000000<br>Path: UPS.PowerConverter.ff860024, Type: Feature, ReportID: 0x51, Offset: 0, 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>- usbsnoop on windows and capture the USB frame during ops (like batt. test). then check it to have the report ID<br><br>another options is obviously to ask APC to disclose their HID naming (which isn't at all a sensible data!) to complete drivers/apc-hid.c->apc_usage_lkp[]<br>
<br>cheers,<br>Arnaud<br>-- <br>Linux / Unix Expert R&D - Eaton - <a href="http://www.eaton.com/mgeops">http://www.eaton.com/mgeops</a><br>Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org/">http://www.networkupstools.org/</a><br>
Debian Developer - <a href="http://www.debian.org">http://www.debian.org</a><br>Free Software Developer - <a href="http://arnaud.quette.free.fr/">http://arnaud.quette.free.fr/</a><br><br>