Nut upsuser - May 2014 - Resetting replace battery status on Pulsar 1500

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>

On May 27, 2014, at 9:59 PM, Daniel O'Connor wrote:
> 
> 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?
The driver.
> I could try running the driver with debugging and see if that shows
anything of interest.
That should help. Unfortunately for non-debug operation, it appears that most of
the usbhid-ups instcmd messages are buried at debug level 3 or 5. That should
probably be addressed when we increase the verbosity for OL/OB events. (Github
issue #79) The syslog() level LOG_INFO should show up in most syslog
configurations.
>> 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.

-- 
Charles Lepple
clepple at gmail

On 28 May 2014, at 21:59, Charles Lepple <clepple at gmail.com>
wrote:
>> What would log it?
> 
> The driver.
OK.
>> I could try running the driver with debugging and see if that shows
anything of interest.
> 
> That should help. Unfortunately for non-debug operation, it appears that
most of the usbhid-ups instcmd messages are buried at debug level 3 or 5. That
should probably be addressed when we increase the verbosity for OL/OB events.
(Github issue #79) The syslog() level LOG_INFO should show up in most syslog
configurations.
FYI is the mge-shut driver (over RS232)

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.

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 :)

--
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/20140529/ee09b5bc/attachment.sig>