[Nut-upsuser] Eaton Powerware 5110 - some stats not reported
tadawson at tpcsvc.com
Sun Feb 16 02:01:42 UTC 2014
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.
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
>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.
>clepple at gmail
>Nut-upsuser mailing list
>Nut-upsuser at lists.alioth.debian.org
"Gaff tape can't fix "Stupid", but it can muffle the sound . . ."
Sent via Android
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Nut-upsuser