On Tue, Feb 14, 2012 at 8:51 PM, Charles Lepple <[email protected]> wrote: > On Feb 14, 2012, at 12:56 PM, Matt Schulte wrote: > >> Why does it say "battery.test.status: Battery bad - replace?" > > Not to be too literal, but it comes from this block of code in > tripplite_usb.c, which may or may not be accurate for your specific model. > > if(tl_model == TRIPP_LITE_SMARTPRO || tl_model == > TRIPP_LITE_OMNIVS_2001 || tl_model == TRIPP_LITE_SMART_0004) { > switch(s_value[2]) { > case '0': > dstate_setinfo("battery.test.status", "Battery > OK"); > break; > case '1': > dstate_setinfo("battery.test.status", "Battery > bad - replace"); > break; > case '2': > status_set("CAL"); > break; > case '3': > status_set("OVER"); > dstate_setinfo("battery.test.status", > "Overcurrent?"); > break; > case '4': > /* The following message is confusing, and may > not be accurate: */ > /* dstate_setinfo("battery.test.status", > "Battery state unknown"); */ > break; > > Usually, after you first plug in the UPS, the status bit says "4", which > apparently means that the battery charger hasn't seen much of the slope of > the charge or discharge curve yet. (If the battery is just being topped off, > you can't really tell its capacity by the instantaneous current or voltage.) > > After a deep discharge cycle, the charging circuit has seen both the rate of > discharge as well as the rate of charge, and it can guess as to whether the > battery is close to the end of its life. Lead-acid batteries are usually good > for 3-5 years. > Any idea why it would decide to throw the "bad" flag on a new battery? I recently (as in maybe two weeks ago) had to replace the battery in the UPS.
Matt _______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
