[Nut-upsuser] TrippLite Eco Series UPS

[Lindsey Chesnutt]

I'd be happy to work with you. My linux skills aren't the greatest in
the world but I'm pretty good at figuring things out (i.e. googling)
so if you're willing to bear with me I'm willing to help.

I'll send outputs directly to you in the future unless you would
rather handle it differently.



On Mon, Sep 21, 2009 at 2:09 PM, Arjen de Korte <nut+users at de-korte.org> wrote:
> Citeren Lindsey Chesnutt <mrchesnutt at gmail.com>:
>
>> I've attached the requested output.
>
> Although it didn't make it to the list (because we don't allow attachments
> larger than 40 kB), I received it directly.
>
>>  0.272003      HID descriptor, method 1: (9 bytes) => 09 21 10 01 00 01 22
>> c9 01
>>  0.272075      i=0, extra[i]=09, extra[i+1]=21
>>  0.272146      HID descriptor, method 2: (9 bytes) => 09 21 10 01 00 01 22
>> c9 01
>>  0.272212      HID descriptor length 457
>>  0.766975      Report Descriptor size = 457
>
> That's a fairly short report descriptor for a HID PDC device. It is a valid
> one though, but it just doesn't have a lot of reports in it. I think we
> already support most of it as it is and that it doesn't report battery
> voltage. The only report that comes close is
>
>>  0.968349      Entering libusb_get_report
>>  0.984961      Report[get]: (3 bytes) => 31 b9 04
>>  0.985031      PhyMax = 0, PhyMin = 0, LogMax = 65535, LogMin = 0
>>  0.985099      Unit = 00000000, UnitExp = 0
>>  0.985164      Exponent = 0
>>  0.985230      hid_lookup_path: 00840004 -> UPS
>>  0.985298      hid_lookup_path: 00840024 -> PowerSummary
>>  0.985365      hid_lookup_path: 00840002 -> PresentStatus
>>  0.985432      hid_lookup_path: 00840030 -> Voltage
>>  0.985520      Path: UPS.PowerSummary.PresentStatus.Voltage, Type:
>> Feature, ReportID: 0x31, Offset: 0, Size: 16, Value: 1209.000000
>
> This could be the battery voltage times 100, but in that case the value is
> surprisingly low (a few tenths of a second before, it reported a fully
> charged battery). It could also mean the input or output voltage (or
> something completely unrelated). There is no way to tell without digging
> deeper into this.
>
> The remainder of the reports are either already supported or vendor specific
> ones. If you're willing to work with us, we might attempt to figure out what
> these mean. Please let us know if you're able to do so (this will probably
> require frequent updates of the driver with lot of debugging enabled) and
> we'll continue on the development mailing list.
>
> Best regards, Arjen
> --
> Please keep list traffic on the list
>
>
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
>



-- 
Lindsey Chesnutt