What would be best is if they could just publish a protocol spec, or
mail you a copy with permission to add to nut docs.
___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuse
I suppose, this approach may be apply to some other data from that UPS.
I could check another values and ask powercom support for other data
items to explain interpretation, if it will help.
On 13.01.23 14:22, Greg Troxel wrote:
That makes sense to me. The field needs to be split into bytes.
That makes sense to me. The field needs to be split into bytes. The
low byte is the integer part of voltags, and the high part is units of
10 mV. And this is per cell.
Probably the unit is measuring the total and then dividing by 36. But
volts per cell will have the same interpretation for va
Hello!
I left this line uncommented in powercom-hid.c for battery voltage:
{ "battery.voltage", 0, 0, "UPS.Battery.Voltage", NULL, "%.2f", 0, NULL },
and got some data different from the input voltage values
The Powercom support staff gave the following response to my question:
Dear Alex,
First
Please email nut-upsuser@alioth-lists rather than nut-upsuser-owner, thanks!
> On Jan 10, 2023, at 12:58 PM, Alex Rydzewski wrote:
>
> Yes, You right) battery.voltage
>
> I found these data among other
>
>0.522942 [D5] hid_lookup_path: 00840004 -> UPS
>0.522950 [D5] hid_lookup_
