Hi Roberto,<br><br><div><span class="gmail_quote">2006/7/24, Roberto Alcântara <<a href="mailto:roberto@microsol.com.br">roberto@microsol.com.br</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Dear nut-upsdev,<br><br>I writed one small function to test if batteries was really bad (using solis<br>driver). Isn't so acurated but it's what we need.<br>Just wait 100% batteries charge, turn off input, wait some time (10% from
<br>previst autonomy) and turn on input again.<br>Looking startAutonomy - stopAutonomy we can know the basic batteries state.<br><br>To scheduler the tests I have one new parameter on driver config file (days<br>between tests) and to record my last batteries test date I created one file
<br>at conf_path/BATT_SCHED_NAME. It's working fine, but I would like know if is<br>it the best way to store this value.<br><br>The first ideia was use crond jobs but I don't would like use crond, then<br>I'm looking for "time to run" inside driver.
<br><br>Let me know what you think about.</blockquote><div><br>I'm not sure to understand your mail.<br></div>Maybe submitting a patch will help.<br></div><br>BTW, I see that you're working for Microsol.<br>You should get in touch with Silvino B. Magalhães, who has written the solis and rhino drivers.
<br clear="all"><br>Official manufacturer support in an important point for NUT, and the NUT users. So your help would be welcome...<br><br>Arnaud<br>-- <br>Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt<br>Network UPS Tools (NUT) Project Leader -
<a href="http://www.networkupstools.org/">http://www.networkupstools.org/</a><br>Debian Developer - <a href="http://people.debian.org/~aquette/">http://people.debian.org/~aquette/</a><br>OpenSource Developer - <a href="http://arnaud.quette.free.fr/">
http://arnaud.quette.free.fr/</a>