Nut upsuser - Feb 2014 - Eaton Powerware 5110 - some stats not reported

On 16/02/14 00:38, Charles Lepple wrote:
> On Feb 15, 2014, at 2:57 AM, Tim Dawson wrote:
>> The driver will poll the UPS for what variables it supports when it
starts, and then go into a polling loop. Look for a section defining the meter
map, and you should see the result, as well as the raw data.
> Tim: spot on.
>
> Greg,
>
> If you want, you can capture the -DDDD output to a file (until it starts
looping), gzip it, and post it to the list. I'm still getting up to speed on
the BCM/XCP protocol, but the meter map dump should have a few values we can
look up in the protocol spec.
Thanks!  I've attached the file to this email 
(bcmxcp_usb.output2014160926.gz), it ran for 12 seconds, and looks like 
it's looping by that time.  I'm not sure what to look for, does grepping
for 'Yes' show the variables that the driver can pull off this UPS?
> Please excuse the mess; we're in the process of converting the protocol
library over to the same format as the rest of the website for ease of
maintenance:
>
> http://old.networkupstools.org/protocols/eaton/
Not a problem at all, I am happy to help with this driver :)
> On 13/02/14 15:55, Alf H?gemark wrote:
>>> Hi
>>>
>>> On
>>> http://nutwiki.kanonbra.com/wiki/Category:Eaton_Powerware_5110
>>>
>>> you can see what is reported. The unreleased part refers to v2.7.1,
which is now released.
>> OK, from that table, should the nut cgi be showing the Battery, UPS
Temp and Battery Runtime values? Sorry, I don't know how these values are
translated into what is shown in the cgi displays.
>>
>  From that table, yes, I think so. From the upsc output you posted, no.
This mismatch is odd, because driver.version.internal is 0.28 in both cases
(this is the version of the bcmxcp_usb driver, which generally gets incremented
after changes to that driver) and the firmware versions seem to match.
>
> For reference, here's where the upsstats.cgi page gets its values:
>
>
https://github.com/networkupstools/nut/blob/master/conf/upsstats-single.html.sample
>
> There is also a template for the table of multiple UPSes, but the mapping
between NUT variables and HTML table cells isn't as obvious.
Ah, I see - I've noticed that when I browse to upsset.cgi, that there 
are no Settings reported when I select Settings and click the View 
button.  If I select the Commands function and click View, there are 
only four available:
- Turn off the load and return when power is back
- Turn off the load and remain off
- Start a battery test
- Description unavailable

I have a Belkin UPS which I was running on this system up to a few days 
ago when I figured out that the battery was totally cactus, and I put 
the Eaton back in until I get replacement batteries for the Belkin.  
(The Belkin is two 12v batteries, the Eaton is one.) Anyway, the driver 
for the Belkin actually has Settings reported, and I can't remember, but 
about 10+ different Commands.

Is the lack of Settings or Commands indicative of any problem, or is it 
the case that these just haven't been implemented on this driver?

Cheers,
Greg

p.s. The only difference I can see from the web page any my upsc output 
is that my UPS is a 700, and the driver was developed on a 500?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: bcmxcp_usb.output2014160926.gz
Type: application/x-gzip
Size: 5640 bytes
Desc: not available
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140216/0724ff9e/attachment.bin>

On Feb 15, 2014, at 6:46 PM, Greg Vickers wrote:
> Thanks!  I've attached the file to this email
(bcmxcp_usb.output2014160926.gz), it ran for 12 seconds, and looks like it's
looping by that time.  I'm not sure what to look for, does grepping for
'Yes' show the variables that the driver can pull off this UPS?
The boolean variables seem to be indicated by "Yes". I think the
"meter map" is the source of the numeric variables:

   0.566550	Index	Offset	Format	NUT
   0.566617	0027	0000	51	output.frequency
   0.566680	0028	0004	51	input.frequency
   0.566743	0033	0008	51	battery.voltage
   0.566805	0041	0012	f0	battery.voltage.low
   0.566866	0043	0016	f0	battery.charge.low
   0.566928	0047	0020	f0	ups.load
   0.566989	0056	0024	f0	input.voltage
   0.567051	0065	0028	51	output.current
   0.567113	0068	0032	51	output.current.nominal
   0.567175	0078	0036	f0	output.voltage
   0.567237	0091	0040	f0	input.quality

Maybe Alf has some additional insights?
> Ah, I see - I've noticed that when I browse to upsset.cgi, that there
are no Settings reported when I select Settings and click the View button.  If I
select the Commands function and click View, there are only four available:
> - Turn off the load and return when power is back
> - Turn off the load and remain off
> - Start a battery test
> - Description unavailable
I think Settings are what you would see from "upsrw <ups>", and
Commands are listed by "upscmd -l <ups>". You're going to
make me actually install the CGI programs, aren't you? Everything else I
have been able to just look up in the source :-)
> I have a Belkin UPS which I was running on this system up to a few days ago
when I figured out that the battery was totally cactus, and I put the Eaton back
in until I get replacement batteries for the Belkin.  (The Belkin is two 12v
batteries, the Eaton is one.) Anyway, the driver for the Belkin actually has
Settings reported, and I can't remember, but about 10+ different Commands.
> 
> Is the lack of Settings or Commands indicative of any problem, or is it the
case that these just haven't been implemented on this driver?
Right, or that the protocol doesn't expose the settings or commands.
> p.s. The only difference I can see from the web page any my upsc output is
that my UPS is a 700, and the driver was developed on a 500?

The part that confuses me is why they would have the same firmware revision for
what seem to be different sets of capabilities. Usually, the only internal
difference between a 500 VA UPS and a 700 VA UPS is the size of the battery
string and maybe the power electronics module.

-- 
Charles Lepple
clepple at gmail

On 16/02/14 10:03, Charles Lepple wrote:
> On Feb 15, 2014, at 6:46 PM, Greg Vickers wrote:
>
>> Thanks!  I've attached the file to this email
(bcmxcp_usb.output2014160926.gz), it ran for 12 seconds, and looks like it's
looping by that time.  I'm not sure what to look for, does grepping for
'Yes' show the variables that the driver can pull off this UPS?
> The boolean variables seem to be indicated by "Yes". I think the
"meter map" is the source of the numeric variables:
>
>     0.566550	Index	Offset	Format	NUT
>     0.566617	0027	0000	51	output.frequency
>     0.566680	0028	0004	51	input.frequency
>     0.566743	0033	0008	51	battery.voltage
>     0.566805	0041	0012	f0	battery.voltage.low
>     0.566866	0043	0016	f0	battery.charge.low
>     0.566928	0047	0020	f0	ups.load
>     0.566989	0056	0024	f0	input.voltage
>     0.567051	0065	0028	51	output.current
>     0.567113	0068	0032	51	output.current.nominal
>     0.567175	0078	0036	f0	output.voltage
>     0.567237	0091	0040	f0	input.quality
>
> Maybe Alf has some additional insights?
>
>> Ah, I see - I've noticed that when I browse to upsset.cgi, that
there are no Settings reported when I select Settings and click the View button.
If I select the Commands function and click View, there are only four available:
>> - Turn off the load and return when power is back
>> - Turn off the load and remain off
>> - Start a battery test
>> - Description unavailable
> I think Settings are what you would see from "upsrw <ups>",
and Commands are listed by "upscmd -l <ups>". You're going
to make me actually install the CGI programs, aren't you? Everything else I
have been able to just look up in the source :-)
And correspondingly with what you say here, the same detail is returned 
by these commands:
$ sudo upsrw Powerware5110
$ (wow, nothing returned!)

$ sudo upscmd -l Powerware5110
Instant commands supported on UPS [Powerware5110]:
shutdown.return - Turn off the load and return when power is back
shutdown.stayoff - Turn off the load and remain off
test.battery.start - Start a battery test
test.system.start - Description unavailable

Bugger, huh.  Guess I'll have to use the Windows software to set the 
beeper[1] to OFF.  You don't have to install the cgi scripts, I'll be 
the guinea pig for the driver[0]!
>> I have a Belkin UPS which I was running on this system up to a few days
ago when I figured out that the battery was totally cactus, and I put the Eaton
back in until I get replacement batteries for the Belkin.  (The Belkin is two
12v batteries, the Eaton is one.) Anyway, the driver for the Belkin actually has
Settings reported, and I can't remember, but about 10+ different Commands.
>>
>> Is the lack of Settings or Commands indicative of any problem, or is it
the case that these just haven't been implemented on this driver?
> Right, or that the protocol doesn't expose the settings or commands.
>
>> p.s. The only difference I can see from the web page any my upsc output
is that my UPS is a 700, and the driver was developed on a 500?
>
> The part that confuses me is why they would have the same firmware revision
for what seem to be different sets of capabilities. Usually, the only internal
difference between a 500 VA UPS and a 700 VA UPS is the size of the battery
string and maybe the power electronics module.
[0] Hurmm, well, I'm happy to do any testing of code with this 700i model!
[1] Once I get replacement batteries for the 1200VA Belkin, the 
Powerware 5110 will be moved to hold up my weather station and wfrog 
laptop, so I can keep recording weather events if we lose power!

Cheers,
Greg

The meter map is basically a bitmap that indicates what variables are output
(and in what format) by the UPS.  You will likely see a variable, 'not
mapped' or nothing.  The variables and 'not mapped' items are output
by the UPS in the measurement block, and the map tells nut how to read it. 
'Unmapped' means that there is a variable there that nut is ignoring,
and the xcp spec can tell you what it is, so you can determine if it is useful
(that was the case on my Prestige - plain 'output voltage' was not
present in the map, but 'phase 1 output voltage' was, which was unmapped
and not used.  I tweaked the maps, and was good.
>From what you posted, charge percentage is not in the map for your unit, but
you may find something else useful that is unmapped.
And yeah, I spent too much time in the serial side of this driver getting my
unit to work, but the good news is that the code is pretty easy to follow, and
with very good debug output.

- Tim

On February 15, 2014 6:03:53 PM CST, Charles Lepple <clepple at gmail.com>
wrote:
>On Feb 15, 2014, at 6:46 PM, Greg Vickers wrote:
>
>> Thanks!  I've attached the file to this email
>(bcmxcp_usb.output2014160926.gz), it ran for 12 seconds, and looks like
>it's looping by that time.  I'm not sure what to look for, does
>grepping for 'Yes' show the variables that the driver can pull off
this
>UPS?
>
>The boolean variables seem to be indicated by "Yes". I think the
"meter
>map" is the source of the numeric variables:
>
>   0.566550	Index	Offset	Format	NUT
>   0.566617	0027	0000	51	output.frequency
>   0.566680	0028	0004	51	input.frequency
>   0.566743	0033	0008	51	battery.voltage
>   0.566805	0041	0012	f0	battery.voltage.low
>   0.566866	0043	0016	f0	battery.charge.low
>   0.566928	0047	0020	f0	ups.load
>   0.566989	0056	0024	f0	input.voltage
>   0.567051	0065	0028	51	output.current
>   0.567113	0068	0032	51	output.current.nominal
>   0.567175	0078	0036	f0	output.voltage
>   0.567237	0091	0040	f0	input.quality
>
>Maybe Alf has some additional insights?
>
>> Ah, I see - I've noticed that when I browse to upsset.cgi, that
there
>are no Settings reported when I select Settings and click the View
>button.  If I select the Commands function and click View, there are
>only four available:
>> - Turn off the load and return when power is back
>> - Turn off the load and remain off
>> - Start a battery test
>> - Description unavailable
>
>I think Settings are what you would see from "upsrw <ups>",
and
>Commands are listed by "upscmd -l <ups>". You're going
to make me
>actually install the CGI programs, aren't you? Everything else I have
>been able to just look up in the source :-)
>
>> I have a Belkin UPS which I was running on this system up to a few
>days ago when I figured out that the battery was totally cactus, and I
>put the Eaton back in until I get replacement batteries for the Belkin.
>(The Belkin is two 12v batteries, the Eaton is one.) Anyway, the driver
>for the Belkin actually has Settings reported, and I can't remember,
>but about 10+ different Commands.
>> 
>> Is the lack of Settings or Commands indicative of any problem, or is
>it the case that these just haven't been implemented on this driver?
>
>Right, or that the protocol doesn't expose the settings or commands.
>
>> p.s. The only difference I can see from the web page any my upsc
>output is that my UPS is a 700, and the driver was developed on a 500?
>
>
>The part that confuses me is why they would have the same firmware
>revision for what seem to be different sets of capabilities. Usually,
>the only internal difference between a 500 VA UPS and a 700 VA UPS is
>the size of the battery string and maybe the power electronics module.
>
>-- 
>Charles Lepple
>clepple at gmail
>
>
>
>
>_______________________________________________
>Nut-upsuser mailing list
>Nut-upsuser at lists.alioth.debian.org
>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

---
Tim Dawson
Lewisville, TX

"Gaff tape can't fix "Stupid", but it can muffle the sound .
. ."
Sent via Android
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140215/09d8ded2/attachment.html>