Matthew Sund
2014-Nov-29 22:01 UTC
[Nut-upsuser] nut and Tripp Lite smart500rt1u on Scientific Linux 7
I installed nut from the epel repository on Scientific Linux 7. I would like to get my smart500rt1u working, but # upsc smart500 at localhost gives the following output: battery.voltage.nominal: 0 device.mfr: Tripp Lite device.model: SMART500RT1U device.type: ups driver.name: tripplite_usb driver.parameter.pollinterval: 5 driver.parameter.port: auto driver.version: 2.7.2 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 7c 00 8b 0d 00 00 '.......' ups.debug.L: 1d 00 00 07 58 58 0d '....XX.' ups.debug.load_banks: 0 ups.debug.M: 00 00 00 7e 0d 00 00 '.......' ups.debug.P: 30 30 35 30 30 58 0d '00500X.' ups.debug.S: 01 04 00 00 64 00 0d '....d..' ups.debug.T: 25 00 02 58 01 58 0d '...X.X.' ups.debug.V: 02 00 0c 01 58 58 0d '....XX.' ups.delay.shutdown: 64 ups.firmware: F334400 ups.firmware.aux: protocol 3005 ups.id: 0 ups.mfr: Tripp Lite ups.model: SMART500RT1U ups.power.nominal: 500 ups.productid: 0001 ups.status: ups.vendorid: 09ae As you can see, the ups.status line is blank, and there is no battery voltage.? If I try to have the machine automatically shut down, I would need to use ups.status, according to the manual.? I have had the stale data error as well.? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20141129/6d532a84/attachment.html>
Charles Lepple
2014-Dec-02 02:08 UTC
[Nut-upsuser] nut and Tripp Lite smart500rt1u on Scientific Linux 7
On Nov 29, 2014, at 5:01 PM, Matthew Sund <mattsund at yahoo.com> wrote:> I installed nut from the epel repository on Scientific Linux 7. I would like to get my smart500rt1u working, but # upsc smart500 at localhost gives the following output: > > > battery.voltage.nominal: 0 > device.mfr: Tripp Lite > device.model: SMART500RT1U > device.type: ups > driver.name: tripplite_usb...> ups.firmware.aux: protocol 3005Support for protocol 3005 was not added until this summer, and we have not yet released a version of NUT which includes this. However, depending on how easy it is to rebuild packages in Scientific Linux, you may be able to download a snapshot of NUT (labeled "2.7.2.5", but that is just a placeholder version number for the autobuilder) and rebuild. When you say "epel repository", is it the same as for RHEL/Fedora? Theoretically, you should be able to download the SRPM from here: https://dl.fedoraproject.org/pub/epel/7/SRPMS/n/ install to /usr/src (or something) and rebuild with a NUT snapshot: http://buildbot.networkupstools.org/snapshots If you have questions, let us know - I'm sure there are other users of RPM-based distributions on the list. -- Charles Lepple clepple at gmail
Apparently Analagous Threads
- Problems communicating with Tripp Lite SMART500RT1U via USB with CentOS 6.6 and NUT 2.6.5
- The dreaded Tripp Lite SMART500RT1U and NUT
- Problems communicating with Tripp Lite SMART500RT1U via USB with CentOS 6.6 and NUT 2.6.5
- Problems communicating with Tripp Lite SMART500RT1U via USB with CentOS 6.6 and NUT 2.6.5
- The dreaded Tripp Lite SMART500RT1U and NUT