Well, I have good news and bad news. I have a Tripp Lite SmartPro UPS attached to a Linux server running Ubuntu 5.10, and I'm running the just-released nut 2.0.3. I had error -71 from the UPS, which Charles Lepple correctly called out as a likely cable problem (thank you, Charles.) The cable provided with the UPS by Tripp Lite was just plain bad. Not too long, mind you- defective. I won't bore you with the steps I used to prove it- but trust me, I proved it, positively. So the uhci_hcd module now loads peacefully. lsusb spots the ups. The vendor id is 09ae, product id 0001- correct. And starting tripplite_usb as root, port auto, says: Detected a UPS: TRIPP LITE/TRIPP LITE SMART1050SLT HOWEVER... then there are a splash of "unknown" messages, of which the killer is: Unknown protocol (3004) attached to Tripp Lite SMART1050SLT Uh-oh. 3004 is new. tripplite_usb only speaks 3003. Yes, Tripp Lite has a shiny new undocumented protocol, folks. It is probably based on 3003- but who knows? One step forward, two steps back.
On 2/8/06, Kenneth Tindle <ktindle@uky.edu> wrote:> Unknown protocol (3004) attached to Tripp Lite SMART1050SLT > > Uh-oh. 3004 is new. tripplite_usb only speaks 3003. > > Yes, Tripp Lite has a shiny new undocumented protocol, folks. It is > probably based on 3003- but who knows?Two options here: 1) edit source code, replace 3003 with 3004, see what breaks 2) connect up the Windows software, capture some traffic, help debug the resulting changes to the driver. In either case, make sure that the equipment plugged into that UPS is not critical. It's a sad state of affairs, but that's what appen when the manufacturers keep their protocols proprietary. -- - Charles Lepple
At 12:59 PM 2/8/2006 -0500, Charles Lepple wrote:>1) edit source code, replace 3003 with 3004, see what breaksPretty much everything. I changed to 3004, and got fake happy messages. But all the items the driver enumerates by messages at startup are wrong (like input and battery voltages of zero, etc.) Of course, the really critical thing is to see if the OL status does or does not change to reflect reality. I'll have to finish the installation of nut to tell- I'm not optimistic. BTW, there is a 3005 protocol as well, used in the new LCD display desktop UPS systems from Tripp Lite. Isn't that sweet?
After simply changing 3003 to 3004, recompiling, and getting both tripplite_usb and upsd resident, a upsc ups.status command returns "Error: data stale" So, to whom it may concern: The 3004 protocol completely breaks the existing 2.0.3 tripplite_usb driver. This is used in the Tripp Lite Smart Pro XL and SLT models. All Smart Pros do not speak the same language. Bummer.