[Nut-upsuser] TrippLite SMART1000LCD

[Arjen de Korte]

Citeren Greg Oliver <oliver.greg op gmail.com>:

> These patches allow this device to function in nut..
>
> diff --git a/trunk/drivers/tripplite-hid.c b/new/drivers/tripplite-hid.c
> index c36da98..dddd13c 100644
> --- a/trunk/drivers/tripplite-hid.c
> +++ b/new/drivers/tripplite-hid.c
> @@ -71,6 +71,8 @@ static usb_device_id_t tripplite_usb_device_table[] = {
>        { USB_DEVICE(TRIPPLITE_VENDORID, 0x2005), battery_scale_0dot1 },
>        /* e.g. TrippLite OMNI900LCD */
>        { USB_DEVICE(TRIPPLITE_VENDORID, 0x2007), battery_scale_0dot1 },
> +       /* e.g. TrippLite Smart1000LCD */
> +       { USB_DEVICE(TRIPPLITE_VENDORID, 0x2009), battery_scale_0dot1 },
>        /* e.g. TrippLite smart2200RMXL2U */
>        { USB_DEVICE(TRIPPLITE_VENDORID, 0x3012), battery_scale_1dot0 },
>        /* e.g. ? */

Thanks for the patch. I've included it in the development version.

> diff --git a/src/nut/nut-2.4.3/scripts/udev/52-nut-usbups.rules
> b/etc/udev/rules.d/52-nut-usbups.rules
> index c8f0437..fbb03df 100644
> --- a/src/nut/nut-2.4.3/scripts/udev/52-nut-usbups.rules
> +++ b/etc/udev/rules.d/52-nut-usbups.rules
> @@ -92,6 +92,8 @@ ATTR{idVendor}=="09ae", ATTR{idProduct}=="1008",
> MODE="664", GROUP="nut"
>  ATTR{idVendor}=="09ae", ATTR{idProduct}=="2005", MODE="664", GROUP="nut"
>  #  e.g. TrippLite OMNI900LCD  - usbhid-ups
>  ATTR{idVendor}=="09ae", ATTR{idProduct}=="2007", MODE="664", GROUP="nut"
> +#  e.g. TrippLite SMART1000LCD  - usbhid-ups
> +ATTR{idVendor}=="09ae", ATTR{idProduct}=="2009", MODE="664", GROUP="nut"
>  #  e.g. TrippLite smart2200RMXL2U  - usbhid-ups
>  ATTR{idVendor}=="09ae", ATTR{idProduct}=="3012", MODE="664", GROUP="nut"
>  #  e.g. ?  - usbhid-ups

This is not needed. These rules are generated automatically by 'make  
dist' once we release a new version.

> Everything *works*, but the only  thing is it thinks there is no
> battery installed even though it can get the values from it..  Maybe
> the battery_scale is different for this one.  I'll play with it more
> later..

This is probably due to an incorrect mapping in the tripplite-hid  
subdriver. I have my doubts about this, so for the moment I have  
commented it out. Most likely the UPS is just wanting to tell you that  
the inverter is not being used, instead of a missing battery.

Best regards, Arjen
-- 
Please keep list traffic on the list (off-list replies will be rejected)