Justin Ellison
2008-Jan-23 05:24 UTC
[Nut-upsuser] empty ups.status on TrippLite SMART1500RMXL2U
Hello, I have a TrippLite SMART1500RMXL2U that I'm trying to get running with Nut 2.2.1. Running upsdrvctl start works, upsd works, but upsc has "issues": je-nas:~/src/nut-2.2.1# upsdrvctl start Network UPS Tools - UPS driver controller 2.2.1- Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.11 (2.2.1-) Warning: This is an experimental driver. Some features may not function correctly. Detected a UPS: TRIPP LITE/ Tripp Lite SMART1500RMXL2U Unit ID: 257 Unknown protocol (4)Attached to Tripp Lite Tripp Lite SMART1500RMXL2U je-nas:~/src/nut-2.2.1# upsd Network UPS Tools upsd 2.2.1- listening on 0.0.0.0 port 3493 Connected to UPS [UPS]: tripplite_usb-UPS //share/cmdvartab not found - disabling descriptions je-nas:~/src/nut-2.2.1# upsc UPS at localhost battery.voltage.nominal: 48 driver.name: tripplite_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.2.1- driver.version.internal: 0.11 input.voltage.nominal: 120 outlet.1.desc: Load 1 outlet.1.id: 1 outlet.1.switch: 1 outlet.1.switchable: 1 outlet.2.desc: Load 2 outlet.2.id: 2 outlet.2.switchable: 0 ups.debug.0: 00 04 58 58 58 58 0d '..XXXX.' ups.debug.D: 37 36 38 38 0d 00 00 '7688...' ups.debug.L: 30 32 43 30 45 34 0d '02C0E4.' ups.debug.load_banks: 1 ups.debug.M: 36 46 37 42 0d 00 00 '6F7B...' ups.debug.S: 31 34 30 32 31 30 0d '140210.' ups.debug.T: 38 46 30 32 35 37 0d '8F0257.' ups.debug.V: 31 30 38 31 0d 00 00 '1081...' ups.delay.shutdown: 64 ups.firmware: F0970.B ups.firmware.aux: protocol 0004 ups.id: 257 ups.mfr: Tripp Lite ups.model: Tripp Lite SMART1500RMXL2U ups.power.nominal: 150 ups.status: Here's some debug ouput from tripplite_usb: je-nas:~/src/nut-2.2.1# /bin/tripplite_usb -a UPS -DDDD Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.11 (2.2.1-) Warning: This is an experimental driver. Some features may not function correctly. debug level is '4' Checking device (0000/0000) (003/001) - VendorID: 0000 - ProductID: 0000 - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 003 Trying to match device Device does not match - skipping Checking device (09AE/0001) (002/004) - VendorID: 09ae - ProductID: 0001 - Manufacturer: TRIPP LITE - Product: Tripp Lite SMART1500RMXL2U - Serial Number: unknown - Bus: 002 Trying to match device Device matches Detected a UPS: TRIPP LITE/ Tripp Lite SMART1500RMXL2U send_cmd(msg_len=3, type='W') send_cmd(msg_len=2, type=' send_cmd(msg_len=2, type='S') send_cmd(msg_len=2, type='P') send_cmd(msg_len=2, type='F') send_cmd(msg_len=2, type='V') send_cmd(msg_len=2, type='V') send_cmd(msg_len=2, type='U') Unit ID: 257 Unknown protocol (4)Attached to Tripp Lite Tripp Lite SMART1500RMXL2U send_cmd(msg_len=2, type='S') send_cmd(msg_len=2, type='L') send_cmd(msg_len=2, type='D') send_cmd(msg_len=2, type='V') send_cmd(msg_len=2, type='M') send_cmd(msg_len=2, type='T') dstate_init: sock /var/state/ups/tripplite_usb-UPS open on fd 5 send_cmd(msg_len=2, type='S') send_cmd(msg_len=2, type='L') send_cmd(msg_len=2, type='D') send_cmd(msg_len=2, type='V') send_cmd(msg_len=2, type='M') send_cmd(msg_len=2, type='T') send_cmd(msg_len=2, type='S') send_cmd(msg_len=2, type='L') send_cmd(msg_len=2, type='D') send_cmd(msg_len=2, type='V') send_cmd(msg_len=2, type='M') send_cmd(msg_len=2, type='T') send_cmd(msg_len=2, type='S') send_cmd(msg_len=2, type='L') send_cmd(msg_len=2, type='D') send_cmd(msg_len=2, type='V') send_cmd(msg_len=2, type='M') send_cmd(msg_len=2, type='T') send_cmd(msg_len=2, type='S') send_cmd(msg_len=2, type='L') send_cmd(msg_len=2, type='D') send_cmd(msg_len=2, type='V') send_cmd(msg_len=2, type='M') send_cmd(msg_len=2, type='T') Signal 2: exiting Any tips on getting this working fully? Is it something I've done, or does the code just not know exactly how to talk to this particular model? Justin
Charles Lepple
2008-Jan-23 12:31 UTC
[Nut-upsuser] empty ups.status on TrippLite SMART1500RMXL2U
On Jan 23, 2008 12:24 AM, Justin Ellison <justin at techadvise.com> wrote:> Hello, > > I have a TrippLite SMART1500RMXL2U that I'm trying to get running with > Nut 2.2.1.[...]> je-nas:~/src/nut-2.2.1# upsc UPS at localhost > battery.voltage.nominal: 48 > driver.name: tripplite_usb > driver.parameter.pollinterval: 2 > driver.parameter.port: auto > driver.version: 2.2.1- > driver.version.internal: 0.11 > input.voltage.nominal: 120 > outlet.1.desc: Load 1 > outlet.1.id: 1 > outlet.1.switch: 1 > outlet.1.switchable: 1 > outlet.2.desc: Load 2 > outlet.2.id: 2 > outlet.2.switchable: 0 > ups.debug.0: 00 04 58 58 58 58 0d '..XXXX.' > ups.debug.D: 37 36 38 38 0d 00 00 '7688...' > ups.debug.L: 30 32 43 30 45 34 0d '02C0E4.' > ups.debug.load_banks: 1 > ups.debug.M: 36 46 37 42 0d 00 00 '6F7B...' > ups.debug.S: 31 34 30 32 31 30 0d '140210.' > ups.debug.T: 38 46 30 32 35 37 0d '8F0257.' > ups.debug.V: 31 30 38 31 0d 00 00 '1081...' > ups.delay.shutdown: 64 > ups.firmware: F0970.B > ups.firmware.aux: protocol 0004 > ups.id: 257 > ups.mfr: Tripp Lite > ups.model: Tripp Lite SMART1500RMXL2U > ups.power.nominal: 150 > ups.status:The key here is that I have never seen a protocol value other than 1001, 2001, 3003 or 3004 (going from memory here, but basically I would not expect to see "0004"). ups.power.nominal seems like it should be 1500 instead of 150. Is the input voltage actually 120 VAC? How are the outlets grouped? (That is, how many are switchable, and how many are on all the time?) Also, what are the USB product and vendor IDs (available from lsusb)? If you are mainly concerned with on-battery/on-line and low battery indications, just hook up the unit with a dummy load (so as not to crash the computer when the batteries die) and run the batteries down while monitoring the "ups.debug.S" line. Even better would be to compare values directly with what the Tripp Lite software returns, if you have a Windows system available. If you go that route, we could also look at a USB protocol dump. Let me know how it goes. -- - Charles Lepple