[Nut-upsdev] Tripp Lite USB UPS

[Patrick Krepps]

Hi Peter,

Glad I was able to provide something that helped. If I understand what you are 
saying, the UPS is reporting that it needs replacing? Or the battery? Either 
way that is upsetting as this UPS is just over 5 weeks old. Anything else I 
can do to help determine the source of the problem?

Thanks for the update and info,
Patrick

PS I've trimmed my long original message to keep things from getting too 
large.

On Monday 26 February 2007 00:23, you wrote:
> Hi Patrick,
>
> the debug output you sent is useful. I think it shows that the bug is
> likely in the device, not the driver. I parsed the report descriptor
> (1028 bytes), and it defines, among other things, a report number 50
> (0x32) ("Feature" or "Input") with the following format:
>
> 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-3: UPS.PowerSummary.PresentStatus.00850046
> byte 2, bit 4-7: UPS.PowerSummary.PresentStatus.NeedReplacement
>
> Bits are counted from least to most significant, i.e.: 76543210.
>
> Now during the initial data collection run, we see report 50 as
>
> follows:
> > Report[r]: (4 bytes) => 32 00 00 11
>
> Here the first byte is the report number (0x32 = 50). The remaining
> bytes are the payload data. By the above scheme, this translates to:
> UPS.PowerSummary.PresentStatus.InternalFailure = 0
> UPS.PowerSummary.PresentStatus.ShutdownImminent = 0
> UPS.PowerSummary.PresentStatus.ACPresent = 1
> UPS.PowerSummary.PresentStatus.NeedReplacement = 1 (why?)
>