[Nut-upsuser] Resetting replace battery status on Pulsar 1500

Daniel O'Connor doconnor at gsoft.com.au
Wed May 28 01:59:16 UTC 2014

On 28 May 2014, at 10:54, Charles Lepple <clepple at gmail.com> wrote:
> On May 26, 2014, at 8:21 PM, Daniel O'Connor wrote:
>> However if I do either of the tests upscmd just reports 'OK' and nothing happens.
> Anything in syslog?

Not that I can see :(

What would log it?

I could try running the driver with debugging and see if that shows anything of interest.

> These commands should result in a self-test similar to the periodic one (the Evolution 500 does it every two weeks), but the "OK" from upscmd doesn't actually wait for the command to be executed.

I think the new batteries will have been in for 2 weeks in a day or 2 so it will be interesting to see if anything changes.

Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140528/a0ce6d89/attachment.sig>

More information about the Nut-upsuser mailing list