[Nut-upsuser] Tripp lite SMART1000LCD

Sun Jan 27 08:18:20 UTC 2008

Charles,

Running usbhid-ups -DDD -a SMART1000LCD seems
to go into an infinite loop unless the driver is supposed to 
send requests to the ups continuously. The values returned
from the USB report requests seem to be valid though, for example,
Report ID 0x32 (UPS.PowerSummary.PresentStatus) has
correct value based on present state.
Based on the error message when later  starting upsd
(Can't connect to UPS [SMART1000LCD] (usbhid-ups-SMART1000LCD): No such file or directory) has the driver not reached the point where it creates
those files ?   

The beginning of the usbhid-ups output is:

debug level is '3'
upsdrv_initups...
Checking device (09AE/2007) (004/101)
- VendorID: 09ae
- ProductID: 2007
- Manufacturer: Tripp Lite 
- Product: TRIPP LITE UPS 
- Serial Number: FW-2263 E 
- Bus: 004
Trying to match device 
Device matches
failed to claim USB device, trying 2 more time(s)...
detaching kernel driver from USB device...
trying again to claim USB device...
HID descriptor, method 1: (9 bytes) => 09 21 10 01 00 01 22 bf 01
HID descriptor, method 2: (9 bytes) => 09 21 10 01 00 01 22 59 02
Warning: two different HID descriptors retrieved (Reportlen = 447 vs. 601)
HID descriptor length 601 
Report Descriptor size = 601
Report Descriptor: (601 bytes) => 05 84 09 04 a1 01 09 24 a1 02 05 84 85 28
09 fe 75 08 95 01 26 ff 00 15 00 b1 03 85 29 09 ff b1 03 85 2b 09 fd b1 03
09 1a a1 02 09 40 85 30 b1 83 c0 85 11 09 5a b1 82 05 85 85 2a 09 89 b1 03
85 33 09 2c b1 03 27 ff ff 00 00 75 10 85 35 09 68 81 a2 85 35 09 68 b1 a2
25 64 75 08 85 34 09 66 81 a2 85 34 09 66 b1 a2 85 37 09 67 b1 03 05 84 09
02 a1 02 25 01 75 01 85 32 05 84 95 01 09 69 81 a2 09 d0 81 a2 95 03 09 44
09 45 09 4b 81 a2 95 03 81 01 85 32 05 84 75 01 95 01 09 69 b1 a2 05 85 09
d0 b1 a2 95 03 09 44 09 45 09 4b b1 a2 95 03 b1 01 c0 c0 05 84 09 10 a1 02
09 12 a1 02 85 04 09 40 75 10 95 01 27 ff ff 00 00 b1 02 05 84 09 02 a1 02
85 23 05 85 75 01 25 01 95 03 09 44 09 45 09 4b b1 82 95 05 b1 01 c0 c0 05
84 95 01 75 08 26 ff 00 09 58 85 10 b1 82 c0 05 84 09 1e a1 02 85 01 09 40
b1 03 85 02 09 42 b1 03 05 84 85 03 09 43 75 10 95 01 27 ff ff 00 00 b1 03
c0 05 84 95 01 75 08 26 ff 00 09 18 a1 02 09 20 a1 02 95 01 75 10 27 ff ff
00 00 85 15 09 57 b1 82 75 08 26 ff 00 06 ff ff 85 51 09 91 b1 82 85 52 09
92 b1 82 85 b6 09 c7 b1 82 c0 c0 06 ff ff 09 10 a1 81 75 10 95 01 27 ff ff
00 00 85 6c 09 7d b1 03 c0 06 ff ff 09 15 a1 81 75 08 95 01 26 ff 00 85 96
09 c0 b1 02 75 20 85 b4 09 d2 b1 02 75 10 85 97 09 c1 b1 02 75 08 85 98 09
c2 b1 02 75 10 85 99 09 c3 b1 02 85 9b 09 c5 b1 02 75 20 85 c2 09 d6 b1 02
85 9a 09 c4 b1 02 c0 05 84 09 24 a1 02 85 31 09 30 95 01 75 10 27 ff ff 00
00 15 00 b1 03 c0 09 10 a1 02 09 12 a1 02 85 20 09 30 b1 02 c0 c0 09 16 a1
02 09 1a a1 02 85 18 55 0f 09 30 b1 82 85 19 09 32 b1 82 c0 55 00 85 22 09
02 a1 02 75 01 95 03 25 01 05 84 09 63 09 6f 09 6e b1 82 95 01 b1 03 09 65
b1 82 09 6d 95 01 b1 03 09 67 09 62 95 02 b1 82 95 06 b1 03 95 01 09 72 b1 
82 95 01 b1 03 c0 c0 05 84 09 18 a1 02 09 20 a1 02 75 10 95 01 15 00 27 ff
ff 00 00 85 17 09 55 b1 82 c0 c0 c0
Using subdriver: TrippLite HID 0.2 (experimental)
Report[get]: (2 bytes) => 28 01
Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID: 0x28, Offset: 0, Size: 8, Value: 1.000000
Report[get]: (2 bytes) => 29 02
Path: UPS.PowerSummary.iSerialNumber, Type: Feature, ReportID: 0x29, Offset: 0, Size: 8, Value: 2.000000
Report[get]: (2 bytes) => 2b 03
Path: UPS.PowerSummary.iManufacturer, Type: Feature, ReportID: 0x2b, Offset: 0, Size: 8, Value: 3.000000
Report[get]: (2 bytes) => 30 78
Path: UPS.PowerSummary.Input.ConfigVoltage, Type: Feature, ReportID: 0x30, Offset: 0, Size: 8, Value: 120.000000 
Report[get]: (2 bytes) => 11 02
Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature, ReportID: 0x11, Offset: 0, Size: 8, Value: 2.000000
Report[get]: (2 bytes) => 2a 18
Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature, ReportID: 0x2a, Offset: 0, Size: 8, Value: 24.000000
Report[get]: (2 bytes) => 33 02
Path: UPS.PowerSummary.CapacityMode, Type: Feature, ReportID: 0x33, Offset: 0, Size: 8, Value: 2.000000
Report[get]: (3 bytes) => 35 73 05
Path: UPS.PowerSummary.RunTimeToEmpty, Type: Input, ReportID: 0x35, Offset: 0, Size: 16, Value: 1395.000000
Report[buf]: (3 bytes) => 35 73 05
Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature, ReportID: 0x35, Offset: 0, Size: 16, Value: 1395.000000
Report[get]: (2 bytes) => 34 64
Path: UPS.PowerSummary.RemainingCapacity, Type: Input, ReportID: 0x34, Offset: 0, Size: 8, Value: 100.000000
Report[buf]: (2 bytes) => 34 64
Path: UPS.PowerSummary.RemainingCapacity, Type: Feature, ReportID: 0x34, Offset: 0, Size: 8, Value: 100.000000
Report[get]: (2 bytes) => 37 64
Path: UPS.PowerSummary.FullChargeCapacity, Type: Feature, ReportID: 0x37, Offset: 0, Size: 8, Value: 100.000000
Report[get]: (2 bytes) => 32 06
Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Input, ReportID: 0x32, Offset: 0, Size: 1, Value: 0.000000
Report[buf]: (2 bytes) => 32 06
Path: UPS.PowerSummary.PresentStatus.TLACPresent, Type: Input, ReportID: 0x32, Offset: 1, Size: 1, Value: 1.000000
:
:

Thanks,

/Karl D

> Date: Sun, 27 Jan 2008 00:28:39 -0500
> From: clepple at gmail.com
> To: k_dal2 at hotmail.com
> Subject: Re: [Nut-upsuser] Tripp lite SMART1000LCD
> CC: nut-upsuser at lists.alioth.debian.org
> 
> On Jan 26, 2008 11:55 PM, Karl Dalen <k_dal2 at hotmail.com> wrote:
> >
> >  Charles,
> >
> > I know the port should work as I have used it for other devices
> > so I reconnected the ups and used a usb hub in between and
> > I got it recognized in the kernel but the nut driver did not seem
> > to attach properly:
> >
> > # dmesg:
> > :
> > usb 4-2.1: new low speed USB device using ehci_hcd and address 100
> > usb 4-2.1: configuration #1 chosen from 1 choice
> > hiddev0: USB HID v1.10 Device [Tripp Lite  TRIPP LITE UPS ] on
> > usb-0000:00:10.3-2.1
> 
> OK, good.
> 
> > I followed the instructions in the INSTALL file but I may have missed
> > something:
> >
> >
> > # /usr/local/ups/bin/upsdrvctl start
> > Network UPS Tools - UPS driver controller 2.2.1
> > Network UPS Tools: 0.29 USB communication driver - core 0.32 (2.2.1)
> >
> > Using subdriver: TrippLite HID 0.2 (experimental)
> > Startup timer elapsed, continuing...
> > ===================================================
> > Is this an error ? Shouldn't the driver usbhid-ups be referenced here
> > when my conf file is:
> 
> That is the output of usbhid-ups (starting from the line after "UPS
> driver controller).
> 
> I am not familiar with the "startup timer elapsed" message, though.
> Anyone else know what this is about?
> 
> For testing, instead of upsdrvctl, you may need to start the driver by
> hand, and pass in "-DDD" to see what is going on:
> 
> /usr/local/ups/bin/usbhid-ups -DDD -a SMART1000LCD
> 
> -- 
> - Charles Lepple

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20080127/43d495b6/attachment-0001.htm 