<br><div class="gmail_quote">2009/9/3 Markus Wildi <span dir="ltr"><<a href="mailto:wildi.markus@bluewin.ch">wildi.markus@bluewin.ch</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;">
Hello Arnaud<br></blockquote><div><br>Hi Markus,<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I checked out and compiled r1952.<br>
<br>
Find below the answers,<br>
<br>
bye wildi<br>
<div class="im"><br>
<br>
On Thursday 03 September 2009 14:00:39 you wrote:<br>
> 2009/9/2 Markus Wildi <<a href="mailto:wildi.markus@bluewin.ch">wildi.markus@bluewin.ch</a>><br>
><br>
> > Hello Arnaud<br>
><br>
> Hi Markus,<br>
><br>
> thanks for having cc'ed the list ;-)<br>
</div>It was my fault, this time it appears on the list.<br>
<div class="im"><br>
> > I compiled the source of nut-2.4.1 and you'll<br>
> > find the output of usbhid-ups -D -a apcsmart<br>
> > below.<br>
> ><br>
> > The UPS did regularly report a self-test while<br>
> > running under apcupsd. It reports in addition<br>
> > e.g. the last reason for a on battery event.<br>
><br>
> if apcupsd can do it, NUT can do it too ;-)<br>
<br>
</div>Yes, indeed :-))<br>
<div class="im"><br>
> the last self test report should already be available through<br>
> ups.test.result (linked to the HID path UPS.Battery.Test, with the current<br>
> value "No test initiated").<br>
</div>Here the result (see the whole output below):<br>
0.379454 Path: UPS.Battery.Test, Type: Input, ReportID: 0x16, Offset:<br>
<div class="im">0, Size: 8, Value: 6.000000<br>
</div> 0.379961 Path: UPS.Battery.Test, Type: Feature, ReportID: 0x16, Offset:<br>
<div class="im">0, Size: 8, Value: 6.000000<br>
<br>
<br>
</div><div class="im">> I've just commited a patch that adds:<br>
> - input.transfer.reason<br>
> - input.sensitivity (which is settable)<br>
<br>
</div>I see only the variable input.sensitivity (see below). With upsrw I see<br>
[battery.charge.low]<br>
[battery.runtime.low]<br>
[input.sensitivity]<br>
[ups.delay.shutdown]<br>
<br></blockquote><div><br>perfect. the sensitivity is settable.<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">
> can you test the development version (Subversion trunk, r1952) to validate<br>
> this.<br>
> Some helpful info are available here:<br>
> <a href="http://buildbot.ghz.cc/%7Ebuildbot/docs/r1950-97/website/download.html" target="_blank">http://buildbot.ghz.cc/~buildbot/docs/r1950-97/website/download.html</a><br>
><br>
> please send back an upsc output too.<br>
<br>
<br>
</div>obsvermes:/etc/init.d # /usr/local/ups/bin/upsc apcsmart@localhost<br>
battery.charge: 100<br>
battery.charge.low: 10<br>
battery.charge.warning: 50<br>
battery.mfr.date: 2006/06/30<br>
battery.runtime: 2160<br>
battery.runtime.low: 120<br>
battery.temperature: 21.1<br>
battery.type: PbAc<br>
battery.voltage: 27.4<br>
battery.voltage.nominal: 24.0<br>
device.mfr: American Power Conversion<br>
device.model: Smart-UPS 750 RM<br>
device.serial: AS0627130223<br>
device.type: ups<br>
<a href="http://driver.name" target="_blank">driver.name</a>: usbhid-ups<br>
driver.parameter.pollfreq: 30<br>
driver.parameter.pollinterval: 2<br>
driver.parameter.port: /dev/hiddev0<br>
driver.version: 2.4.1-1952M<br>
driver.version.data: APC HID 0.93<br>
driver.version.internal: 0.34<br>
input.sensitivity: high<br>
input.voltage: 234.7<br>
output.voltage: 234.7<br>
output.voltage.nominal: 230.0<br>
ups.beeper.status: disabled<br>
ups.delay.shutdown: 20<br>
ups.firmware: 619.3.I<br>
ups.firmware.aux: 8.1<br>
ups.load: 31.2<br>
ups.mfr: American Power Conversion<br>
ups.mfr.date: 2006/06/30<br>
ups.model: Smart-UPS 750 RM<br>
ups.productid: 0002<br>
ups.serial: AS0627130223<br>
ups.status: OL<br>
ups.test.result: No test initiated<br>
ups.timer.reboot: -1<br>
ups.timer.shutdown: -1<br>
ups.vendorid: 051d<br>
<div class="im"><br>
<br></div></blockquote><div><br>it's strange that we don't see input.transfer.reason!<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">
<br>
><br>
> if you still see differences with apcupsd, please tell me back. It's quite<br>
> possible that I've missed something more about how APC units work.<br>
</div></blockquote><div><br>is the test result coherent with what you see in apcupsd or powerchute?<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">(...)<br>0.882610 Path: UPS.Input.APCLineFailCause, Type: Feature, ReportID:<br>
</div><div class="im">0x21, Offset: 0, Size: 8, Value: 5.000000<br>
</div></blockquote><div> </div></div>strange indeed. the data is there, and now know.<br><br>I've made a minor fix (r1955).<br>please test it and tell me back if input.transfer.reason appears now.<br>otherwise, please send me back a debug level 5 output of the driver, ie using -DDDDD<br>
<br>cheers,<br clear="all">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>