thr3ads.net - Nut upsuser - [Nut-upsuser] Tripp Lite SU5000RT3U [May 2018]

If this information is useful, please help other people find it:
Share via:

Charles Lepple

2018-May-12 01:50 UTC

[Nut-upsuser] Tripp Lite SU5000RT3U

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.

Michael

2018-May-25 21:20 UTC

head link

[Nut-upsuser] Tripp Lite SU5000RT3U

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>

Michael

2018-May-25 21:31 UTC

head link

[Nut-upsuser] Tripp Lite SU5000RT3U

Charles,

We saw some changes. I've included some pipes of before and after the
unplug. It smells like hex code to me in the debug area.

Thanks,
Mike

On Fri, May 25, 2018 at 4:20 PM, Michael <fax12345 at gmail.com> wrote:
> 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/5629cb88/attachment-0001.html>
-------------- next part --------------
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: 30 30 37 44 0d 00 00 '007D...'
ups.debug.L: 31 39 30 30 30 30 0d '190000.'
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 31 30 30 0d '140100.'
ups.debug.T: 39 45 30 30 30 31 0d '9E0001.'
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
-------------- next part --------------
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: 30 30 37 44 0d 00 00 '007D...'
ups.debug.L: 31 39 30 30 30 30 0d '190000.'
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 31 30 30 0d '140100.'
ups.debug.T: 39 45 30 30 30 31 0d '9E0001.'
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
-------------- next part --------------
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: 30 30 37 43 0d 00 00 '007C...'
ups.debug.L: 31 39 30 30 30 30 0d '190000.'
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 31 30 30 0d '140100.'
ups.debug.T: 39 45 30 30 30 31 0d '9E0001.'
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
-------------- next part --------------
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: 30 30 37 43 0d 00 00 '007C...'
ups.debug.L: 31 39 30 30 30 30 0d '190000.'
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 31 30 30 0d '140100.'
ups.debug.T: 39 46 30 30 30 31 0d '9F0001.'
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
-------------- next part --------------
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: 30 30 38 30 0d 00 00 '0080...'
ups.debug.L: 31 39 31 34 30 30 0d '191400.'
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 31 30 30 0d '140100.'
ups.debug.T: 39 46 30 30 30 31 0d '9F0001.'
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
-------------- next part --------------
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 33 35 41 30 31 0d '135A01.'
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 37 31 0d '9F2571.'
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

Charles Lepple

2018-May-25 22:01 UTC

head link

[Nut-upsuser] Tripp Lite SU5000RT3U

On May 25, 2018, at 5:20 PM, Michael <fax12345 at gmail.com>
wrote:> 
> driver.version: 2.7.4-480-g14301bdb
> 
I might not have provided enough information on the branch. 14301bdb corresponds
to a commit on the master branch, rather than the tripplite_0005 branch that has
the new code. What does "git status" say?

The hex debug output is probably still useful, but I haven't looked at all
of the files.

Charles Lepple

2018-Jun-06 01:14 UTC

head link

[Nut-upsuser] Tripp Lite SU5000RT3U

> On Jun 5, 2018, at 4:23 PM, Michael <fax12345 at gmail.com> wrote:
> 
> Hey Charles,
> 
> Where and how do you want me to run that query? 
In general, after cloning, git commands can be run in the "working
copy" directory and deeper. So following the wiki instructions, it's
inside the "nut" directory that was created after running "git
clone".

It will probably say something like this:

$ git status
On branch master
Your branch is up to date with 'github/master'.


To test the tripplite_0005 branch, run "git checkout tripplite_0005"
and run "make".
> 
> Thanks,
> Mike
> 
> On Fri, May 25, 2018 at 5:01 PM, Charles Lepple <clepple at gmail.com
<mailto:clepple at gmail.com>> wrote:
> On May 25, 2018, at 5:20 PM, Michael <fax12345 at gmail.com
<mailto:fax12345 at gmail.com>> wrote:
> > 
> > driver.version: 2.7.4-480-g14301bdb
> > 
> 
> I might not have provided enough information on the branch. 14301bdb
corresponds to a commit on the master branch, rather than the tripplite_0005
branch that has the new code. What does "git status" say?
> 
> The hex debug output is probably still useful, but I haven't looked at
all of the files.
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20180605/052ec4b5/attachment.html>

Michael

2018-Jun-06 18:41 UTC

head link

[Nut-upsuser] Tripp Lite SU5000RT3U

Hi Charles,

Here's a screen grab of what I ran:

ubuntu at intranet:~/upsmonitor/nut$ git checkout tripplite_0005
Already on 'tripplite_0005'
Your branch is up to date with 'origin/tripplite_0005'.
ubuntu at intranet:~/upsmonitor/nut$ git status
On branch tripplite_0005
Your branch is up to date with 'origin/tripplite_0005'.

nothing to commit, working tree clean

After I ran "make" and ran "git status", I have:


ubuntu at intranet:~/upsmonitor/nut$ git status
On branch tripplite_0005
Your branch is up to date with 'origin/tripplite_0005'.

nothing to commit, working tree clean




What do you need to do next?

Thanks,
Mike

On Tue, Jun 5, 2018 at 8:14 PM, Charles Lepple <clepple at gmail.com>
wrote:
> On Jun 5, 2018, at 4:23 PM, Michael <fax12345 at gmail.com> wrote:
>
> Hey Charles,
>
> Where and how do you want me to run that query?
>
>
> In general, after cloning, git commands can be run in the "working
copy"
> directory and deeper. So following the wiki instructions, it's inside
the
> "nut" directory that was created after running "git
clone".
>
> It will probably say something like this:
>
> $ git status
> On branch master
> Your branch is up to date with 'github/master'.
>
> To test the tripplite_0005 branch, run "git checkout
tripplite_0005" and
> run "make".
>
>
> Thanks,
> Mike
>
> On Fri, May 25, 2018 at 5:01 PM, Charles Lepple <clepple at
gmail.com> wrote:
>
>> On May 25, 2018, at 5:20 PM, Michael <fax12345 at gmail.com>
wrote:
>> >
>> > driver.version: 2.7.4-480-g14301bdb
>> >
>>
>> I might not have provided enough information on the branch. 14301bdb
>> corresponds to a commit on the master branch, rather than the
>> tripplite_0005 branch that has the new code. What does "git
status" say?
>>
>> The hex debug output is probably still useful, but I haven't looked
at
>> all of the files.
>
>
>
>-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20180606/b8b8677b/attachment.html>

Apparently Analagous Threads

Search for more maybe matching threads

Nut upsuser - May 2018 - Tripp Lite SU5000RT3U

[Nut-upsuser] Tripp Lite SU5000RT3U

[Nut-upsuser] Tripp Lite SU5000RT3U

[Nut-upsuser] Tripp Lite SU5000RT3U

[Nut-upsuser] Tripp Lite SU5000RT3U

[Nut-upsuser] Tripp Lite SU5000RT3U

[Nut-upsuser] Tripp Lite SU5000RT3U

Apparently Analagous Threads