Nut upsuser - Nov 2009 - Tripp Lite SmartPro SMX500RT1U incompatibility

Greetings to all,

I recently connected a Tripp Lite SMX500RT1U unit to a Synology NAS (basically a
Marvell ARM equipped box running a custom 2.6.24 Linux). I tried using the
tripplite_usb driver contained in nut 2.4.1 with not much luck.

It does read the model ID and VA rating properly, but fails at everything else -
mains voltage (this is a 230VAC EU model), battery config, unit status etc.
Seems expected though, since as reported, this model is using yet another Tripp
Lite protocol (3005).

It also seems that quite frequently (approx 1s every 10), communication to the
UPS is lost and I am getting "data stale" errors. I can't really
say if it affects normal operation.

The actual unit details (as per PowerAlert software and product specs):

Manufacturer:	Tripp Lite
Model:	SMX500RT1U
Nominal Input Voltage:	230VAC
Nominal Frequency:	50Hz
VA Rating:	500VA
Load Banks Controllable:	1
Load Banks Total:	2
Nominal Battery Voltage:	12VDC
Battery Set:	2x 6VDC batteries
Firmware Version:	3344 Rev 3

--- On Sun, 22/11/09, George Stratigis <george_stratigis at yahoo.co.uk>
wrote:
> From: George Stratigis <george_stratigis at yahoo.co.uk>
> Subject: [Nut-upsuser] Tripp Lite SmartPro SMX500RT1U incompatibility
> To: nut-upsuser at lists.alioth.debian.org
> Date: Sunday, 22 November, 2009, 22:03
> Greetings to all,
> 
> I recently connected a Tripp Lite SMX500RT1U unit to a
> Synology NAS (basically a Marvell ARM equipped box running a
> custom 2.6.24 Linux). I tried using the tripplite_usb driver
> contained in nut 2.4.1 with not much luck.
> 
> It does read the model ID and VA rating properly, but fails
> at everything else - mains voltage (this is a 230VAC EU
> model), battery config, unit status etc. Seems expected
> though, since as reported, this model is using yet another
> Tripp Lite protocol (3005).
> 
> It also seems that quite frequently (approx 1s every 10),
> communication to the UPS is lost and I am getting "data
> stale" errors. I can't really say if it affects normal
> operation.
> 
> From what I understand, the tripplite_usb driver is
> implemented by reverse engineering the UPS's responses to
> certain commands. I could provide any debug and other info
> needed to interpret protocol 3005.
> 
> DiskStation> ./upsdrvctl -u root start
> Network UPS Tools - UPS driver controller 2.4.1
> Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver
> 0.20 (2.4.1)
> Warning: This is an experimental driver.
> Some features may not function correctly.
> Detected a UPS: TRIPP LITE/TRIPP LITE SMX500RT1U
> Unknown input voltage range: 0x06
> Unknown number of switchable load banks: 0x01
> Unit ID: 0
> Unknown protocol (3005)Attached to Tripp Lite SMX500RT1U
> Unknown value for s[1]: 0x01
> 
> DiskStation> ./upsc ups
> battery.voltage.nominal: 0
> driver.name: tripplite_usb
> driver.parameter.pollinterval: 2
> driver.parameter.port: auto
> driver.version: 2.4.1
> driver.version.internal: 0.20
> input.voltage.nominal: 120
> ups.debug.0: 30 05 58 58 58 58 0d '0.XXXX.'
> ups.debug.D: 00 e3 00 90 0d 00 00 '.......'
> ups.debug.L: 14 00 00 07 58 58 0d '....XX.'
> ups.debug.load_banks: 0
> ups.debug.M: 00 00 00 ed 0d 00 00 '.......'
> ups.debug.P: 30 30 35 30 30 58 0d '00500X.'
> ups.debug.S: 01 00 00 00 64 00 0d '....d..'
> ups.debug.T: 2d 00 01 f4 00 58 0d '.....X.'
> ups.debug.V: 06 00 0c 01 58 58 0d '....XX.'
> ups.delay.shutdown: 64
> ups.firmware: F334403
> ups.firmware.aux: protocol 3005
> ups.id: 0
> ups.mfr: Tripp Lite
> ups.model: SMX500RT1U
> ups.power.nominal: 500
> ups.productid: 0001
> ups.status:
> ups.vendorid: 09ae
> 
> 
> 
> George
> 
> 
> ? ? ? 
> 
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
>