<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span>Arnaud,<br></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: "Times New Roman"; background-color: transparent; font-style: normal;"><span><br></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: "Times New Roman"; background-color: transparent; font-style: normal;"><span>I was finally able to get back to this issue and would recommend adding these items to the FAQ #37 about recalibrating the UPS:</span><span><br></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: "Times New Roman"; background-color: transparent; font-style: normal;"><span><br></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: "Times New Roman"; background-color: transparent; font-style: normal;"><span>1a. It's
important that the UPS be at 100% charge before starting the procedure; starting at lower will not work at all, not just produce inaccurate numbers.<br></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: "Times New Roman"; background-color: transparent; font-style: normal;"><span> [I started the procedure when the UPS was at 91% charge. After that it would never report being more than 20% charge, even after leaving it plugged in<br></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: "Times New Roman"; background-color: transparent; font-style: normal;"><span> for hours; running the procedure in FAQ #37 never left it reporting more than 20 seconds of charge left, which I verified was incorrect.]<br></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: "Times New Roman"; background-color: transparent;
font-style: normal;"><span><br></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: "Times New Roman"; background-color: transparent; font-style: normal;"><span>1b. If for some reason the UPS never reaches 100% charge, this can be remedied (in the ACP ES-750 case), by leaving it unplugged for 1 week.<br></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: "Times New Roman"; background-color: transparent; font-style: normal;"><span> [Doing this allowed me to recover from the case in 1a above. After that the procedure below, as in : http://excessups.com/blog/manual-runtime-calibration-apc-ups/<br></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: "Times New Roman"; background-color: transparent; font-style: normal;"><span> worked fine.]<br></span></div><div style="color: rgb(0, 0, 0); font-size: 16px;
font-family: "Times New Roman"; background-color: transparent; font-style: normal;"><span><br></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: "Times New Roman"; background-color: transparent; font-style: normal;"><span>I would add that it is worth mentioning in the FAQs that often a replacement UPS costs only slightly more than the replacement battery for the old one,<br></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: "Times New Roman"; background-color: transparent; font-style: normal;"><span>as I found out after trying this procedure.<br></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: "Times New Roman"; background-color: transparent; font-style: normal;"><span><br></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: "Times New Roman"; background-color: transparent; font-style:
normal;"><span>thanks,<br></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: "Times New Roman"; background-color: transparent; font-style: normal;"><span>--jack<br></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: "Times New Roman"; background-color: transparent; font-style: normal;"><span><br></span></div> <div style="font-size: 12pt; font-family: "times new roman", "new york", "times", serif;"> <div style="font-size: 12pt; font-family: "times new roman", "new york", "times", serif;"> <div dir="ltr"> <font size="2" face="Arial"> <hr size="1"> </font>________<br></div> From: Arnaud Quette <<a ymailto="mailto:aquette.dev@gmail.com" href="mailto:aquette.dev@gmail.com">aquette.dev@gmail.com</a>><br>To: JS <<a ymailto="mailto:jshaio@yahoo.com" href="mailto:jshaio@yahoo.com">jshaio@yahoo.com</a>>; Kastus Shchuka
<<a ymailto="mailto:ks-nut@tprfct.net" href="mailto:ks-nut@tprfct.net">ks-nut@tprfct.net</a>>; Michal Soltys <<a ymailto="mailto:soltys@ziu.info" href="mailto:soltys@ziu.info">soltys@ziu.info</a>> <br>Cc: <a ymailto="mailto:nut-upsuser@lists.alioth.debian.org" href="mailto:nut-upsuser@lists.alioth.debian.org">nut-upsuser@lists.alioth.debian.org</a> <br>Sent: Monday, November 26, 2012 2:42 PM<br>Subject: Re: [Nut-upsuserAPC UPS: replacement battery always triggers shutdown] APC UPS: replacement battery always triggers shutdown<br> <br><br>Michal, Kastus, Jack,<br><br>I have a similar request sitting in the Features requests for years:<br><a href="https://alioth.debian.org/tracker/index.php?func=detail&aid=304645&group_id=30602&atid=411545" target="_blank">https://alioth.debian.org/tracker/index.php?func=detail&aid=304645&group_id=30602&atid=411545</a><br><a
href="http://lists.alioth.debian.org/pipermail/nut-upsdev/2006-June/000938.html" target="_blank">http://lists.alioth.debian.org/pipermail/nut-upsdev/2006-June/000938.html</a><br><br>would you please unite your efforts and bring a patch for NUT FAQ (or the driver(s))?<br><br>thanks a lot!<br>Arnaud<br>-- <br>NUT (Network UPS Tools) Project Leader - <a href="http://www.networkupstools.org/" target="_blank">http://www.networkupstools.org</a><br>Debian Developer - <a href="http://www.debian.org/" target="_blank">http://www.debian.org</a><br>Free Software Developer - <a href="http://arnaud.quette.fr/" target="_blank">http://arnaud.quette.fr</a><br><br><br>2012/11/11 Kastus Shchuka <<a ymailto="mailto:ks-nut@tprfct.net" href="mailto:ks-nut@tprfct.net">ks-nut@tprfct.net</a>><br><br>On Sun, Nov 11, 2012 at 07:21:35AM -0800, JS wrote:<br>>> I followed this procedure (charging the battery fully, letting it drain off a token load while UPS is grounded
on a surge protector) but it did not help.<br>>><br>>> Perhaps I missed something running this procedure; if anyone has suggestions for solving this they'd be greatly appreciated.<br>><br>>I've been in the same situation after replacing the battery in SC620I model.<br>><br>>Then I found <a href="http://old.nabble.com/SmartUPS-and-new-battery-td20678966.html" target="_blank">http://old.nabble.com/SmartUPS-and-new-battery-td20678966.html</a><br>>and followed the procedure:<br>><br>>1. Shutdown the apcupsd daemon.<br>>2. Run apctest<br>>3. Choose option 6 to enter terminal mode<br>>4. Enter Y (UPS should respond SM)<br>>5. Enter 1 (one, not el; wait 4 seconds)<br>>6. Enter 1 (one, not el; UPS should respond PROG)<br>>7. Enter 0 (zero, not oh; UPS should respond with current constant)<br>>8. Enter + (plus) or - (minus) to increment/decrement the value<br>>9. Enter R to reprogram constant value (UPS
should respond Bye)<br>>10. Enter Y (UPS should respond SM)<br>>11. Enter 0 (zero, not oh; UPS should respond with the new constant)<br>>12. Enter Esc to exit terminal mode<br>>13. Choose option 7 to exit apctest.<br>><br>>The value to store in the register 0 differs by the model. There is a table<br>>posted in the middle of the thread. I hope your model is listed there.<br>>If you cannot find your model, you may want to try experimenting with different<br>>values.<br>><br>>In my case, after updating register 0, my UPS is back to 42 min runtime.<br>><br>>Hope this helps.<br>><br>>Kastus<br>><br>><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a href="http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20121126/fda22d51/attachment-0001.html"
target="_blank">http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20121126/fda22d51/attachment-0001.html</a>><br><br>------------------------------<br><br>Message: 2<br>Date: Mon, 26 Nov 2012 19:09:54 -0800 (PST)<br>From: JS <<a ymailto="mailto:jshaio@yahoo.com" href="mailto:jshaio@yahoo.com">jshaio@yahoo.com</a>><br>To: Arnaud Quette <<a ymailto="mailto:aquette.dev@gmail.com" href="mailto:aquette.dev@gmail.com">aquette.dev@gmail.com</a>>, Kastus Shchuka<br> <<a ymailto="mailto:ks-nut@tprfct.net" href="mailto:ks-nut@tprfct.net">ks-nut@tprfct.net</a>>, Michal Soltys <<a ymailto="mailto:soltys@ziu.info" href="mailto:soltys@ziu.info">soltys@ziu.info</a>><br>Cc: "<a ymailto="mailto:nut-upsuser@lists.alioth.debian.org" href="mailto:nut-upsuser@lists.alioth.debian.org">nut-upsuser@lists.alioth.debian.org</a>"<br> <<a
ymailto="mailto:nut-upsuser@lists.alioth.debian.org" href="mailto:nut-upsuser@lists.alioth.debian.org">nut-upsuser@lists.alioth.debian.org</a>><br>Subject: Re: [Nut-upsuser] APC UPS: replacement battery always<br> triggers shutdown<br>Message-ID:<br> <<a ymailto="mailto:1353985794.23786.YahooMailNeo@web161201.mail.bf1.yahoo.com" href="mailto:1353985794.23786.YahooMailNeo@web161201.mail.bf1.yahoo.com">1353985794.23786.YahooMailNeo@web161201.mail.bf1.yahoo.com</a>><br>Content-Type: text/plain; charset="utf-8"<br><br><br><br>I forgot to mention that I was not able to test<br>the procedure in #1 below successfully because my?<br>UPS never shows more than 65% battery charge anymore. This may be the result of a<br>failed calibration run.<br><br>Jack<br><br><br><br>________________________________<br> From: JS <<a ymailto="mailto:jshaio@yahoo.com"
href="mailto:jshaio@yahoo.com">jshaio@yahoo.com</a>><br>To: Arnaud Quette <<a ymailto="mailto:aquette.dev@gmail.com" href="mailto:aquette.dev@gmail.com">aquette.dev@gmail.com</a>>; Kastus Shchuka <<a ymailto="mailto:ks-nut@tprfct.net" href="mailto:ks-nut@tprfct.net">ks-nut@tprfct.net</a>>; Michal Soltys <<a ymailto="mailto:soltys@ziu.info" href="mailto:soltys@ziu.info">soltys@ziu.info</a>> <br>Cc: "<a ymailto="mailto:nut-upsuser@lists.alioth.debian.org" href="mailto:nut-upsuser@lists.alioth.debian.org">nut-upsuser@lists.alioth.debian.org</a>" <<a ymailto="mailto:nut-upsuser@lists.alioth.debian.org" href="mailto:nut-upsuser@lists.alioth.debian.org">nut-upsuser@lists.alioth.debian.org</a>> <br>Sent: Monday, November 26, 2012 9:38 PM<br>Subject: Re: [Nut-upsuser] APC UPS: replacement battery always triggers shutdown<br> <br><br>?Arnaud,<br><br><br>I haven't been able to test Kastus' suggestion because my UPS (APC Back-UPS ES 750)
doesn't appear on the list<br><br>and I didn't want to take take the risk of disabling it by mistake.<br><br><br>However, I did make a bit of progress on this:<br><br><br>1. There is a more detailed procedure than the one in NUT FAQ #37 in: <a href="http://excessups.com/blog/manual-runtime-calibration-apc-ups/" target="_blank">http://excessups.com/blog/manual-runtime-calibration-apc-ups/</a>?<br><br>? ? ?which is summarized as:<br><br><br>? ? Follow these steps to do a proper manual calibration on your APC UPS:<br><br>? ? 1. Battery must be at 100% capacity when the Runtime Calibration is initiated/started. (charge the UPS for 24hours prior)<br>? ? 2. The UPS must have 30-34% load on it during the calibration (Constant load, try: lamps, computers, monitors. Measure load % by PowerChute)<br>? ? 3. Disconnect the serial/USB comm cable from the UPS (you don?t want PowerChute to shut down equipment)<br>? ? 4. The battery must be discharged completely
(unplug UPS from wall outlet, let the UPS to shut off completely due to a discharged battery).<br>?<br> ? 5. Remove the attached load (ie ? lights, computers)<br>? ? 6. Let the UPS charge for 8 hours while OFF (plug back into utility power, press OFF button when UPS turns ON)<br>? ? 7. Turn on UPS (run time should now be accurate)<br><br>?<br><br>2. the man page for the? usbhid-ups has an alternative, based on the battery charge instead of the estimated runtime:<br><br>? ? ?"New" units have battery.runtime.low, but depending on battery quality, firmware version, calibration and UPS load - this variable can be underestimated quite<br>? ? ?a bit - especially right after going into OB state. This in turn can cause LB to be asserted, which under normal conditions will cause NUT to initiate the<br>? ? ?shutdown. You might want to disable this condition entirely, when relying on ignorelb option (this
was actually the main<br> motivation behind introduction of<br>? ? ?such feature).<br><br>? ? ?Simple example:<br><br>? ? ?[apc]<br>? ? ?ignorelb<br>? ? ?override.battery.charge.low = 15<br>? ? ?override.battery.runtime.low = -1<br><br><br><br>I've been using this config and it works fine, allowing my system to keep running during the occasional 30-60 second AC power losses we see:<br>? ? ? ? ?[apc]<br>? ? ? ? ? driver = usbhid-ups<br>? ? ? ? ? ?port = auto<br>? ? ? ? ? desc = "APC Back-UPS ES 750"<br>? ? ? ? ? ignorelb<br>? ? ? ? ? override.battery.charge.low
= 20<br>? ?<br> ? ? ? override.battery.runtime.low = -1<br><br><br>My system is running debian (testing distribution) and unfortunately the apcupsd package with apcsmart conflicts with nut-client. I tried installing it<br>but could not get it configured properly for the Back-UPS ES 750 (which has only a USB cable with a db-9 connector for access).<br><br>thanks,<br>--jack<br><br><br>________________________________<br> From: Arnaud Quette <<a ymailto="mailto:aquette.dev@gmail.com" href="mailto:aquette.dev@gmail.com">aquette.dev@gmail.com</a>><br>To: JS <<a ymailto="mailto:jshaio@yahoo.com" href="mailto:jshaio@yahoo.com">jshaio@yahoo.com</a>>; Kastus Shchuka <<a ymailto="mailto:ks-nut@tprfct.net" href="mailto:ks-nut@tprfct.net">ks-nut@tprfct.net</a>>; Michal Soltys <<a ymailto="mailto:soltys@ziu.info" href="mailto:soltys@ziu.info">soltys@ziu.info</a>> <br>Cc: <a
ymailto="mailto:nut-upsuser@lists.alioth.debian.org" href="mailto:nut-upsuser@lists.alioth.debian.org">nut-upsuser@lists.alioth.debian.org</a> <br>Sent: Monday, November 26, 2012 2:42 PM<br>Subject: Re: [Nut-upsuser] APC UPS: replacement battery always triggers shutdown<br> <br><br>Michal, Kastus, Jack,<br><br>I have a similar request sitting in the Features requests for years:<br><a href="https://alioth.debian.org/tracker/index.php?func=detail&aid=304645&group_id=30602&atid=411545" target="_blank">https://alioth.debian.org/tracker/index.php?func=detail&aid=304645&group_id=30602&atid=411545</a><br><a href="http://lists.alioth.debian.org/pipermail/nut-upsdev/2006-June/000938.html" target="_blank">http://lists.alioth.debian.org/pipermail/nut-upsdev/2006-June/000938.html</a><br><br>would you please unite your efforts and bring a patch for NUT FAQ (or the driver(s))?<br><br>thanks a lot!<br>Arnaud<br>-- <br>NUT (Network UPS Tools)
Project Leader - <a href="http://www.networkupstools.org/" target="_blank">http://www.networkupstools.org/</a><br>Debian Developer - <a href="http://www.debian.org/" target="_blank">http://www.debian.org/</a><br>Free Software Developer - <a href="http://arnaud.quette.fr/" target="_blank">http://arnaud.quette.fr/</a><br><br><br>2012/11/11 Kastus Shchuka <<a ymailto="mailto:ks-nut@tprfct.net" href="mailto:ks-nut@tprfct.net">ks-nut@tprfct.net</a>><br><br>On Sun, Nov 11, 2012 at 07:21:35AM -0800, JS wrote:<br>>> I followed this procedure (charging the battery fully, letting it drain off a token load while UPS is grounded on a surge protector) but it did not help.<br>>><br>>> Perhaps I missed something running this procedure; if anyone has suggestions for solving this they'd be greatly appreciated.<br>><br>>I've been in the same situation after replacing the battery in SC620I model.<br>><br>>Then I found <a
href="http://old.nabble.com/SmartUPS-and-new-battery-td20678966.html" target="_blank">http://old.nabble.com/SmartUPS-and-new-battery-td20678966.html</a><br>>and followed the procedure:<br>><br>>1. Shutdown the apcupsd daemon.<br>>2. Run apctest<br>>3. Choose option 6 to enter terminal mode<br>>4. Enter Y (UPS should respond SM)<br>>5. Enter 1 (one, not el; wait 4 seconds)<br>>6. Enter 1 (one, not el; UPS should respond PROG)<br>>7. Enter 0 (zero, not oh; UPS should respond with current constant)<br>>8. Enter + (plus) or - (minus) to increment/decrement the value<br>>9. Enter R to reprogram constant value (UPS should respond Bye)<br>>10. Enter Y (UPS should respond SM)<br>>11. Enter 0 (zero, not oh; UPS should respond with the new constant)<br>>12. Enter Esc to exit terminal mode<br>>13. Choose option 7 to exit apctest.<br>><br>>The value to store in the register 0 differs by the model. There is a
table<br>>posted in the middle of the thread. I hope your model is listed there.<br>>If you cannot find your model, you may want to try experimenting with different<br>>values.<br>><br>>In my case, after updating register 0, my UPS is back to 42 min runtime.<br>><br>>Hope this helps.<br>><br>>Kastus<br>><br>><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a href="http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20121126/63faaa2d/attachment.html" target="_blank">http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20121126/63faaa2d/attachment.html</a>><br><br>------------------------------<br><br>_______________________________________________<br>Nut-upsuser mailing list<br><a ymailto="mailto:Nut-upsuser@lists.alioth.debian.org" href="mailto:Nut-upsuser@lists.alioth.debian.org">Nut-upsuser@lists.alioth.debian.org</a><br><a
href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser</a><br><br>End of Nut-upsuser Digest, Vol 89, Issue 23<br>*******************************************<br><br><br> </div> </div> </div></body></html>