search for: outputvoltag

...ed > 0.078534 Can't claim USB device [10af:0001]@0/0: Entity not found > > The same for 2.74. has an endless output. > I rescue the following > 0.278176 Path: UPS.Input.Voltage, Type: Feature, ReportID: 0x20, > Offset: 0, Size: 16, Value: 2.201e-05 > 0.278274 Input/OutputVoltage = 2.201e-05 -> assuming correction factor > = 1e+07 > 0.278384 send_to_all: SETINFO input.voltage "220.1" > 0.278517 hid_lookup_usage: UPS -> 00840004 > 0.278621 hid_lookup_usage: Output -> 0084001c > 0.278769 hid_lookup_usage: Voltage -> 00840030 &...

...ed > 0.078534 Can't claim USB device [10af:0001]@0/0: Entity not found > > The same for 2.74. has an endless output. > I rescue the following > 0.278176 Path: UPS.Input.Voltage, Type: Feature, ReportID: 0x20, > Offset: 0, Size: 16, Value: 2.201e-05 > 0.278274 Input/OutputVoltage = 2.201e-05 -> assuming correction factor > = 1e+07 > 0.278384 send_to_all: SETINFO input.voltage "220.1" > 0.278517 hid_lookup_usage: UPS -> 00840004 > 0.278621 hid_lookup_usage: Output -> 0084001c > 0.278769 hid_lookup_usage: Voltage -> 00840030 &...

...quency.5 = INTEGER: 50.1 NUT-MIB::inputFrequencyNominal.1 = INTEGER: 60.0 NUT-MIB::inputFrequencyNominal.2 = INTEGER: 60.0 NUT-MIB::inputTransferBoostLow.6 = INTEGER: 185 NUT-MIB::inputTransferTrimHigh.6 = INTEGER: 265 NUT-MIB::inputPhases.4 = INTEGER: 3 NUT-MIB::inputPhases.5 = INTEGER: 3 NUT-MIB::outputVoltage.1 = INTEGER: 221.0 NUT-MIB::outputVoltage.2 = INTEGER: 221.0 NUT-MIB::outputVoltage.5 = INTEGER: 120.0 NUT-MIB::outputVoltage.6 = INTEGER: 230.0 NUT-MIB::outputVoltageNominal.6 = INTEGER: 230.0 NUT-MIB::outputFrequencyNominal.5 = INTEGER: 60.0 NUT-MIB::outputFrequencyNominal.6 = INTEGER: 50.0 NUT-...

...quency.5 = INTEGER: 50.1 NUT-MIB::inputFrequencyNominal.1 = INTEGER: 60.0 NUT-MIB::inputFrequencyNominal.2 = INTEGER: 60.0 NUT-MIB::inputTransferBoostLow.6 = INTEGER: 185 NUT-MIB::inputTransferTrimHigh.6 = INTEGER: 265 NUT-MIB::inputPhases.4 = INTEGER: 3 NUT-MIB::inputPhases.5 = INTEGER: 3 NUT-MIB::outputVoltage.1 = INTEGER: 221.0 NUT-MIB::outputVoltage.2 = INTEGER: 221.0 NUT-MIB::outputVoltage.5 = INTEGER: 120.0 NUT-MIB::outputVoltage.6 = INTEGER: 230.0 NUT-MIB::outputVoltageNominal.6 = INTEGER: 230.0 NUT-MIB::outputFrequencyNominal.5 = INTEGER: 60.0 NUT-MIB::outputFrequencyNominal.6 = INTEGER: 50.0 NUT-...

...48 00 >???? 0.368698??? PhyMax = 0, PhyMin = 0, LogMax = 1, LogMin = 0 >???? 0.368723??? Unit = 00000000, UnitExp = 0 >???? 0.368747??? Exponent = 0 >???? 0.368776??? Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x05, Offset: 0, Size: 16, Value: 0 >???? 0.368805??? Input/OutputVoltage = 0 -> assuming correction factor = 1e+07 > > offset 0, size 16 in Report[buf] is '4e 00' (0x004e == 78) but LogMax is 1 (and it should be 0xffff to match the size). > > This is annoying, because it means that we can't simply scale the values. I don't know of an ea...

Hi On 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 >????

...pe: Feature, ReportID: 0x02, Offset: 12, Size: 4, Value: 6 0.017676 Path: UPS.PowerSummary.RemainingCapacity, Type: Feature, ReportID: 0x06, Offset: 0, Size: 8, Value: 100 0.017725 Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x05, Offset: 0, Size: 16, Value: 0 0.017746 Input/OutputVoltage = 0 -> assuming correction factor = 1e+07 0.017779 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x05, Offset: 16, Size: 16, Value: 0 0.017799 ConfigVoltage = 0 -> assuming correction factor = 1e+08 0.017837 Path: UPS.PowerSummary.Discharging, Type: Feature, Repor...