[Nut-upsdev] [nut-commits] svn commit r1210 - in trunk: . drivers

[Arjen de Korte]

>> byte 0, bit 0-6: unused
>> byte 0, bit 7:   UPS.PowerSummary.PresentStatus.InternalFailure
>> byte 1, bit 0:   unused
>> byte 1, bit 1:   UPS.PowerSummary.PresentStatus.ShutdownImminent
>> byte 1, bit 2-7: unused
>> byte 2, bit 0:   UPS.PowerSummary.PresentStatus.ACPresent
>> byte 2, bit 1:   unused
>> byte 2, bit 2:
>> UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit
>> byte 2, bit 3:   UPS.PowerSummary.PresentStatus.FullyCharged
>> byte 2, bit 4:   UPS.PowerSummary.PresentStatus.Charging
>> byte 2, bit 5:   UPS.PowerSummary.PresentStatus.Discharging
>> byte 2, bit 6:   UPS.PowerSummary.PresentStatus.FullyDischarged
>> byte 2, bit 7:   UPS.PowerSummary.PresentStatus.NeedReplacement
>
> Is it the same UPS as mentioned in this email?
>
> http://lists.alioth.debian.org/pipermail/nut-upsdev/2005-November/000316.html
>
> That one has additional status bits like Buck, Boost and Overload.

It is a different one (09AE:4003), but it does have another Feature report
with the variables you mentioned:

Path: UPS.PowerConverter.PresentStatus.VoltageOutOfRange, Type: Feature,
ReportID: 0x22, Offset: 0, Size: 1, Value: 0.000000
Path: UPS.PowerConverter.PresentStatus.Buck, Type: Feature, ReportID:
0x22, Offset: 1, Size: 1, Value: 0.000000
Path: UPS.PowerConverter.PresentStatus.Boost, Type: Feature, ReportID:
0x22, Offset: 2, Size: 1, Value: 0.000000
Path: UPS.PowerConverter.PresentStatus.00000000, Type: Feature,
ReportID: 0x22, Offset: 3, Size: 1, Value: 0.000000
Path: UPS.PowerConverter.PresentStatus.Overload, Type: Feature,
ReportID: 0x22, Offset: 4, Size: 1, Value: 0.000000
Path: UPS.PowerConverter.PresentStatus.Used, Type: Feature, ReportID:
0x22, Offset: 5, Size: 1, Value: 1.000000
Path: UPS.PowerConverter.PresentStatus.OverTemperature, Type: Feature,
ReportID: 0x22, Offset: 6, Size: 1, Value: 0.000000
Path: UPS.PowerConverter.PresentStatus.InternalFailure, Type: Feature,
ReportID: 0x22, Offset: 7, Size: 1, Value: 0.000000
Path: UPS.PowerConverter.PresentStatus.00000000, Type: Feature,
ReportID: 0x22, Offset: 8, Size: 1, Value: 0.000000
Path: UPS.PowerConverter.PresentStatus.00000000, Type: Feature,
ReportID: 0x22, Offset: 9, Size: 1, Value: 0.000000
Path: UPS.PowerConverter.PresentStatus.00000000, Type: Feature,
ReportID: 0x22, Offset: 10, Size: 1, Value: 0.000000
Path: UPS.PowerConverter.PresentStatus.00000000, Type: Feature,
ReportID: 0x22, Offset: 11, Size: 1, Value: 0.000000
Path: UPS.PowerConverter.PresentStatus.00000000, Type: Feature,
ReportID: 0x22, Offset: 12, Size: 1, Value: 0.000000
Path: UPS.PowerConverter.PresentStatus.00000000, Type: Feature,
ReportID: 0x22, Offset: 13, Size: 1, Value: 0.000000
Path: UPS.PowerConverter.PresentStatus.AwaitingPower, Type: Feature,
ReportID: 0x22, Offset: 14, Size: 1, Value: 0.000000
Path: UPS.PowerConverter.PresentStatus.00000000, Type: Feature,
ReportID: 0x22, Offset: 15, Size: 1, Value: 0.000000

which boils down to

byte 0, bit 0:   UPS.PowerConverter.PresentStatus.VoltageOutOfRange
byte 0, bit 1:   UPS.PowerConverter.PresentStatus.Buck
byte 0, bit 2:   UPS.PowerConverter.PresentStatus.Boost
byte 0, bit 3:   unused
byte 0, bit 4:   UPS.PowerConverter.PresentStatus.Overload
byte 0, bit 5:   UPS.PowerConverter.PresentStatus.Used
byte 0, bit 6:   UPS.PowerConverter.PresentStatus.OverTemperature
byte 0, bit 7:   UPS.PowerConverter.PresentStatus.InternalFailure
byte 1, bit 0-5: unused
byte 1, bit 6:   UPS.PowerConverter.PresentStatus.AwaitingPower
byte 1, bit 7:   unused

> I am wondering if the parser is handling the "stacked" Usage elements
> in the descriptor.

I don't know, but the above doesn't look obviously off to me and I think
we can safely ignore the 'unused' ones.

Best regards, Arjen