[Nut-upsuser] Resetting replace battery status on Pulsar 1500
doconnor at gsoft.com.au
Thu May 29 05:28:33 UTC 2014
On 29 May 2014, at 13:17, Charles Lepple <clepple at gmail.com> wrote:
>> FYI is the mge-shut driver (over RS232)
> Ah, right. The "MGE HID" part threw me off. Bear in mind that the rest of this email is conjecture.
>> I ran the driver at debug level 5 (ie sudo /usr/local/libexec/nut/mge-shut -a ups1 -D -D -D -D -D -u uucp |& tee /tmp/mge-shut.log) and issued the deep & quick battery test commands.
> looks like the instcmd()s are at 61.999 and 82.685 seconds.
>> The log file is at http://www.gsoft.com.au/~doconnor/mge-shut.log
>>>>> 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.
>>> Definitely let us know. It is certainly possible that we are not sending the battery test command correctly, or that something is preventing it from being sent.
>> OK, hopefully you can glean some intelligence from the log :)
> It's pretty cryptic...
Hah, glad it's not just me then :)
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...
Size: 195 bytes
Desc: Message signed with OpenPGP using GPGMail
More information about the Nut-upsuser