Hi Markus<br><br><div class="gmail_quote">2009/9/6 Markus Wildi<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>
<div><div></div><div class="h5"><br>
<br>
On Sunday 06 September 2009 15:44:58 you wrote:<br>
> 2009/9/5 Markus Wildi<br>
><br>
> > Good morning Arnaud<br>
><br>
> hi Markus<br>
><br>
> > find attached the output of the driver (debug level 5).<br>
> ><br>
> ><br>
> > Here is an output of apcupsd command apcaccess status<br>
> ><br>
> ><br>
> > <a href="https://azug.minpet.unibas.ch/wikiobsvermes/index.php/Apcupsd#Useful_Comm" target="_blank">https://azug.minpet.unibas.ch/wikiobsvermes/index.php/Apcupsd#Useful_Comm</a><br>
> >ands<br>
> ><br>
> > Have a look at<br>
> > LASTXFER : Low line voltage<br>
> ><br>
> > and here an excerpt of the log file<br>
> ><br>
> > Feb 19 17:28:51 obsvermes apcupsd[2055]: UPS Self Test switch to battery.<br>
> > Feb 19 17:28:58 obsvermes apcupsd[2055]: UPS Self Test completed: Battery<br>
> > OK<br>
><br>
> ok, I see why: currently, there are few values that are not mapped due to<br>
> the boolean mechanism used in usbhid-ups to process (either outvolt or<br>
> outfreq or nothing).<br>
> these values are commented in the code (your unit is currently reporting "5<br>
> => self test"):<br>
><br>
> /* these input.transfer.reason can't be mapped at the moment... */<br>
> Â Â { 3, "ripple", NULL }, Â Â Â Â /* Ripple */<br>
> Â Â { 5, "self test", NULL }, Â Â /* Self Test or Discharge Calibration<br>
> commanded<br>
> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â * Test usage, front button, or 2 week self<br>
> test */<br>
> Â Â { 6, "forced", NULL }, Â Â Â Â /* DelayBeforeShutdown or<br>
> APCDelayBeforeShutdown */<br>
> Â Â { 10, "forced", NULL }, Â Â Â Â /* Graceful shutdown by accessories */<br>
> Â Â { 11, "self test", NULL }, Â Â /* Test usage invoked */<br>
> Â Â { 12, "self test", NULL }, Â Â /* Front button initiated self test */<br>
> Â Â { 13, "self test", NULL }, Â Â /* 2 week self test */<br>
><br>
> adding support for these would means changing some more code, and I'm not<br>
> sure it's forth just for reporting the above...<br>
<br>
</div></div>Ok, that is a decision you have to take. But from my point of view I think<br>
it is a good information specifically if the self-test did not pass. That<br>
event should go to a log file.<br></blockquote><div><br>I've logged a feature request to address that later:<br><a href="https://alioth.debian.org/tracker/index.php?func=detail&aid=311944&group_id=30602&atid=411545">https://alioth.debian.org/tracker/index.php?func=detail&aid=311944&group_id=30602&atid=411545</a><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">
> moreover, the data you reported are not coherent: considering the log file,<br>
> LASTXFER should have the value "Self Test" and not "Low line voltage"...<br>
<br>
</div>That is correct. The wiki link provides an output to show you, what apcupsd<br>
reports on my UPS. The excerpt of the log file reports the self test.<br></blockquote><div>Â <br>ok<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">
> just to be sure, apart from transfer.reason, everything is equivalent to<br>
> apcupsd?<br>
</div>I'm not the UPS expert and to me it appears ok.<br>
<div class="im"></div></blockquote><div>Â <br>yep, everything seems fine.<br>btw, you can put "auto" for the port.<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">> btw, what is that eeprom thing in apcupsd? is it equivalent to upsrw?<br>
</div>I checked the current release of apcupsd and I do not find a command<br>
eeprom any more. There is no target named eeprom in the Makefiles.<br>
I know, that it did not work properly but I remember<br>
that it is used to store values directly in the UPS's eeprom.<br></blockquote><div>Â <br>ok, so it's indeed equivalent to upsrw.<br><br>cheers,<br></div><div>Arnaud<br></div></div>-- <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>