[Nut-upsuser] Tripp Lite SU5000RT3U

[Michael]

Charles,

I followed the instructions on github, and my upsc UPSNAME command output
did not change (I don't have any statuses for the ups.status line).

The output is as follows:

upsc Tripp-Lite
Init SSL without certificate database
battery.voltage.nominal: 48
device.mfr: Tripp Lite
device.model: TRIPP LITE UPS
device.type: ups
driver.name: tripplite_usb
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: no
driver.version: 2.7.4-480-g14301bdb
driver.version.internal: 0.29
input.voltage.nominal: 208
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.switch: 1
outlet.2.switchable: 1
outlet.3.desc: Load 3
outlet.3.id: 3
outlet.3.switch: 1
outlet.3.switchable: 1
outlet.4.desc: Load 4
outlet.4.id: 4
outlet.4.switch: 1
outlet.4.switchable: 1
outlet.5.desc: Load 5
outlet.5.id: 5
outlet.5.switch: 1
outlet.5.switchable: 1
outlet.6.desc: Load 6
outlet.6.id: 6
outlet.6.switch: 1
outlet.6.switchable: 1
outlet.7.desc: Load 7
outlet.7.id: 7
outlet.7.switch: 1
outlet.7.switchable: 1
outlet.8.desc: Load 8
outlet.8.id: 8
outlet.8.switch: 1
outlet.8.switchable: 1
outlet.9.desc: Load 9
outlet.9.id: 9
outlet.9.switchable: 0
ups.debug.0: 00 05 58 58 58 58 0d '..XXXX.'
ups.debug.D: 36 45 38 37 0d 00 00 '6E87...'
ups.debug.L: 31 35 35 41 30 31 0d '155A01.'
ups.debug.load_banks: 8
ups.debug.M: 30 30 37 31 0d 00 00 '0071...'
ups.debug.P: 30 35 30 30 0d 00 00 '0500...'
ups.debug.S: 31 34 30 30 30 30 0d '140000.'
ups.debug.T: 39 46 32 35 38 31 0d '9F2581.'
ups.debug.V: 33 30 38 38 0d 00 00 '3088...'
ups.delay.shutdown: 64
ups.firmware: F1114.A
ups.firmware.aux: protocol 0005
ups.id: 65535
ups.mfr: Tripp Lite
ups.model: TRIPP LITE UPS
ups.power.nominal: 500
ups.productid: 0001
ups.status:
ups.vendorid: 09ae


We are going to pull the plug on the UPS, and I will run the command again.
I'm hoping the changes in the output will be enough to reverse engineer
this with you.

Thanks,
Mike

On Fri, May 11, 2018 at 8:50 PM, Charles Lepple <clepple at gmail.com> wrote:

> On May 8, 2018, at 10:05 PM, Charles Lepple <clepple at gmail.com> wrote:
> >
> >> I'm new to this, so let me know what you need from me and I will try my
> best. This UPS does power our production servers, so shutting things down
> aren't an easy task, but this weekend might open up some opportunity for
> that if need be. If I need to test it by unplugging the main power, that I
> can do without problems.
> >
> > The first thing to try is building the latest NUT code from source.
> Version 2.7.4 is the latest released version, but after that, we'll switch
> to a new branch to add in the features for protocol 0005. Here are some
> instructions (not yet tested for Ubuntu 18.04):
> >
> > https://github.com/networkupstools/nut/wiki/Building-NUT-on-Debian,-
> Raspbian-and-Ubuntu
> >
> > There is always some level of risk with testing new code on an UPS, but
> if things didn't shut down before, you should be okay. You can try building
> this week, but I'd still wait until the weekend to test the new driver.
> >
> If you have a chance to build the master branch to test, you can also try
> the tripplite_0005 branch. I need to dig out the OMNIVS1000 for regression
> testing, and of course I don't have a SU5000 to test with, but it should
> work based on the debug information you provided.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20180525/c03abcd8/attachment.html>