search for: configvoltage

...ained that NUT was reporting impossibly low 'output.voltage.nominal'). So I don't think there is something *broken* here. What is probably *missing* is the HID path that is reporting the battery on Charles' UPS, so that the driver won't have to fallback to "UPS.PowerSummary.ConfigVoltage". Alternatively, if this UPS doesn't report nominal or actual battery voltage, we may need to ignore these values. We may also wish to add "UPS.PowerSummary.ConfigVoltage" as a fallback when "UPS.Flow.[4].ConfigVoltage" can't be found. But since it can have two mea...

...ough to diagnose that weird value. Here is the problem: Starting at 0.062904 (reformatted): Report[buf]: (5 bytes) => 05 51 00 48 00 Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x05, Offset: 0, Size: 16, Value: 1 Report[buf]: (5 bytes) => 05 51 00 48 00 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x05, Offset: 16, Size: 16, Value: 0 ConfigVoltage = 0 -> assuming correction factor = 1e+08 The Voltage of 0x51 (81 V) and ConfigVoltage of 0x48 (72 V) seem reasonable, but somewhere else in the HID Report Descriptor, the voltages are getting scaled to a "Logica...

...ere is the problem: > > Starting at 0.062904 (reformatted): > > Report[buf]: (5 bytes) => 05 51 00 48 00 > Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x05, Offset: 0, Size: 16, Value: 1 > > Report[buf]: (5 bytes) => 05 51 00 48 00 > Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x05, Offset: 16, Size: 16, Value: 0 > > ConfigVoltage = 0 -> assuming correction factor = 1e+08 > > The Voltage of 0x51 (81 V) and ConfigVoltage of 0x48 (72 V) seem reasonable, but somewhere else in the HID Report Descriptor, the voltages are getting scaled...

2014-11-07 0:16 GMT-03:00 Charles Lepple <clepple at gmail.com>: > On Nov 6, 2014, at 5:56 PM, Marcelo Fernandez <marcelo.fidel.fernandez at gmail.com> wrote: > >> battery.voltage: 10000000. >> battery.voltage.nominal: 0.0 > > Well, these are certainly interesting values ;-) > > I suspect the correction for earlier units has failed. Can you please start

...se follow the HID PDC specifications if you name them like this (and break terribly in the process). In NUT we can (for now) easily implement the PowerCOM specific formatting rules, but not all applications may be able to do so. The same goes for UPS.PowerSummary.Voltage, UPS.PowerSummary.ConfigVoltage, UPS.Battery.Voltage and UPS.Battery.ConfigVoltage. These should deal with the battery voltage, not the output voltage like implemented in the PowerCOM HID now. If in the future (?) PowerCOM has newer UPS designs that unlike the present one are native HID PDC from the start (instead of a ser...

...case, > but I'm still seeing the lines you've pointed at: > > 0.062308 Path: UPS.PowerSummary.Voltage, Type: Feature, > ReportID: 0x05, Offset: 0, Size: 16, Value: 1 > 0.062336 Report[buf]: (5 bytes) => 05 51 00 48 00 > 0.062352 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, > ReportID: 0x05, Offset: 16, Size: 16, Value: 0 > 0.062379 ConfigVoltage = 0 -> assuming correction factor = 1e+08 Strange, I would have thought that the "Value: 0" would show the actual number. Does it look like drivers/libhid.o got rebuilt? Can you retr...

Hi, thanks for your helpful reply. I've added the productid in the ups.conf and it seems to work (better) now. > After starting the driver and upsd, what does "upsc ups" return? If you can also include "upsrw ups" and "upscmd -l ups" output, we can update the DDL. #upsc ups Init SSL without certificate database battery.charge: 100 battery.charge.low: 20

...t 2. Do the following ones return punctual data, or only the nominal value? If the latter, do they change, or they are static? - ups.realpower / UPS.Output.ConfigActivePower - ups.realpower / UPS.Flow.ConfigApparentPower 3. Are the following ones static? - input.voltage.nominal / UPS.Input.ConfigVoltage - input.voltage.nominal / UPS.Flow.ConfigVoltage - battery.voltage.nominal / UPS.PowerSummary.ConfigVoltage - battery.voltage.nominal / UPS.BatterySystem.Battery.ConfigVoltage 4. What's the reason for not using DEFAULT_OFFDELAY and DEFAULT_ONDELAY in the 'dfl' field of the load...

...mmary.RunTimeToEmpty, Type: Input, Value: 5722.000000 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature, Value: 5722.000000 Path: UPS.PowerSummary.RemainingTimeLimit, Type: Input, Value: 300.000000 Path: UPS.PowerSummary.RemainingTimeLimit, Type: Feature, Value: 300.000000 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, Value: 12.000000 Path: UPS.PowerSummary.Voltage, Type: Feature, Value: 20.900000 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, Value: 1.000000 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Input, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.Discharging,...

...o the driver. I'd recommend using "upsc" or the driver logs. > > To that end, the .ac.txt and .bat.txt files both show 24.0 V: > > 0.081935 Entering libusb_get_report > 0.082018 Report[get]: (2 bytes) => 09 f0 > 0.082029 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x09, Offset: 0, Size: 8, Value: 24 > 0.082035 Entering libusb_get_report > 0.082115 Report[get]: (2 bytes) => 0a f0 > 0.082124 Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x0a, Offset: 0, Size: 8, Value: 24 I know there are t...

...ttery.voltage: 1.0 >> battery.voltage.nominal: 0.0 > > Similar to Mike's report on the CPS UPS, the HID descriptor for this device is buggy: > > Logical Maximum(1) > Logical Minimum(0) > ... > Report ID(5) > Usage Page(Power Device) > Usage(Voltage) > Usage(ConfigVoltage) > > I think the Logical Min/Max are responsible for the battery voltages, since there are larger values in the log: > > 0.240091 Report[buf]: (5 bytes) => 05 51 00 48 00 > 0.240097 Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x05, Offset: 0, Size: 16, Value:...

...Summary.RunTimeToEmpty, Type: Input, Value: 240.000000 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature, Value: 240.000000 Path: UPS.PowerSummary.RemainingTimeLimit, Type: Input, Value: 300.000000 Path: UPS.PowerSummary.RemainingTimeLimit, Type: Feature, Value: 300.000000 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, Value: 12.000000 Path: UPS.PowerSummary.Voltage, Type: Feature, Value: 21.200001 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, Value: 1.000000 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Input, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.Discharging,...

...9;m still seeing the lines you've pointed at: >> >> 0.062308 Path: UPS.PowerSummary.Voltage, Type: Feature, >> ReportID: 0x05, Offset: 0, Size: 16, Value: 1 >> 0.062336 Report[buf]: (5 bytes) => 05 51 00 48 00 >> 0.062352 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, >> ReportID: 0x05, Offset: 16, Size: 16, Value: 0 >> 0.062379 ConfigVoltage = 0 -> assuming correction factor = 1e+08 > > Strange, I would have thought that the "Value: 0" would show the actual number. Does it look like drivers/libhid.o got rebui...

...ecommend using "upsc" or the driver logs. >> >> To that end, the .ac.txt and .bat.txt files both show 24.0 V: >> >> 0.081935 Entering libusb_get_report >> 0.082018 Report[get]: (2 bytes) => 09 f0 >> 0.082029 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x09, Offset: 0, Size: 8, Value: 24 >> 0.082035 Entering libusb_get_report >> 0.082115 Report[get]: (2 bytes) => 0a f0 >> 0.082124 Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x0a, Offset: 0, Size: 8, Value: 24 > >...

...ther issue). Then, I started looking into the MGE subdriver and the debug output: mge-hid.c, line 344: { "battery.voltage", 0, 0, "UPS.PowerSummary.Voltage", NULL, "%.1f", 0, NULL }, { "battery.voltage.nominal", 0, 0, "UPS.BatterySystem.ConfigVoltage", NULL, "%.0f", HU_FLAG_STATIC, NULL }, { "battery.voltage.nominal", 0, 0, "UPS.PowerSummary.ConfigVoltage", NULL, "%s", HU_FLAG_STATIC, mge_battery_voltage_nominal }, Here are some of the UPS.PowerSummary lines from running with "-DD"...

...r only the nominal > > value? If the latter, do they change, or they are static? > > - ups.realpower / UPS.Output.ConfigActivePower > > - ups.realpower / UPS.Flow.ConfigApparentPower > > 3. Are the following ones static? > > - input.voltage.nominal / UPS.Input.ConfigVoltage > > - input.voltage.nominal / UPS.Flow.ConfigVoltage > > - battery.voltage.nominal / UPS.PowerSummary.ConfigVoltage > > - battery.voltage.nominal / UPS.BatterySystem.Battery.ConfigVoltage > > 4. What's the reason for not using DEFAULT_OFFDELAY and > > DEFA...

...n 10/03/2014 03:42 PM, Charles Lepple wrote:> On Oct 3, 2014, at 7:50 AM, paul.chavent at fnac.net wrote: > > > This is what I was referring to (from the belkin-hid log): > >???? 1.325782??? Report[buf]: (5 bytes) => 05 53 00 48 00 >???? 1.325799??? Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x05, Offset: 16, Size: 16, Value: 0 >???? 1.325814??? ConfigVoltage = 0 -> assuming correction factor = 1e+08 > > You may need to bump the debug level to 5 to see the full exponent processing (cf get_unit_expo() in libhid.c). Please gzip the log - it will be...

...fset: 0, Size: 8, Value: 1 0.728179 Path: UPS.PowerSummary.iSerialNumber, Type: Feature, ReportID: 0x29, Offset: 0, Size: 8, Value: 2 0.745042 Path: UPS.PowerSummary.iManufacturer, Type: Feature, ReportID: 0x2b, Offset: 0, Size: 8, Value: 3 0.761738 Path: UPS.PowerSummary.Input.ConfigVoltage, Type: Feature, ReportID: 0x30, Offset: 0, Size: 8, Value: 120 0.778460 Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature, ReportID: 0x11, Offset: 0, Size: 8, Value: 2 0.795076 Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature, ReportID: 0x2a, Offset: 0, Size: 8, Value: 2...

...fset: 0, Size: 8, Value: 1 0.023013 Path: UPS.PowerSummary.iSerialNumber, Type: Feature, ReportID: 0x29, Offset: 0, Size: 8, Value: 5 0.024007 Path: UPS.PowerSummary.iManufacturer, Type: Feature, ReportID: 0x2b, Offset: 0, Size: 8, Value: 3 0.025006 Path: UPS.PowerSummary.Input.ConfigVoltage, Type: Feature, ReportID: 0x30, Offset: 0, Size: 8, Value: 120 0.025997 Path: UPS.PowerSummary.Input.Voltage, Type: Feature, ReportID: 0x31, Offset: 0, Size: 16, Value: 0.001233 0.027006 Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature, ReportID: 0x11, Offset: 0, Size: 8, Val...

...eportID: 0x29, Offset: 0, Size: 8, Value: 3 0.059619 Path: UPS.PowerSummary.iManufacturer, Type: Feature, ReportID: 0x2b, Offset: 0, Size: 8, Value: 1 0.060167 Path: UPS.PowerSummary.ffff00d9, Type: Feature, ReportID: 0xc0, Offset: 0, Size: 8, Value: 5 0.060709 Path: UPS.PowerSummary.Input.ConfigVoltage, Type: Feature, ReportID: 0x30, Offset: 0, Size: 8, Value: 120 0.061316 Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature, ReportID: 0x11, Offset: 0, Size: 8, Value: 2 0.061905 Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature, ReportID: 0x2a, Offset: 0, Size: 8, Value: 4 0.06...