[Nut-upsuser] Battery test feature of APC Back-UPS RS series

[Arnaud Quette]

2009/5/16 Jean Delvare <khali at linux-fr.org>

> Hi Arnaud,
>

Jean,


> On Sat, 16 May 2009 13:11:31 +0200, Arnaud Quette wrote:
> > no need ATM. just fire the driver using "usbhid-ups -D -a ..." and post
> back
> > the tree dumped.
>
> Here you go:
>
> debug level is '1'
> upsdrv_initups...
> Using subdriver: APC HID 0.93
> (...)
> > check for a string path that matches battery.test.
>
> 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
- usbsnoop on windows and capture the USB frame during ops (like batt.
test). then check it to have the report ID

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[]

cheers,
Arnaud
-- 
Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20090516/4070f140/attachment.htm>