similar to: nut and Tripp Lite smart500rt1u on Scientific Linux 7

Hello, I am trying to get a SMART500RT1U working on CentOS and just receiving the following message when attempting to start the driver: Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.6.5) Warning: This is an experimental driver. Some features may not function correctly. Detected a UPS: Tripp Lite /TRIPP LITE SMART500RT1U Unknown input voltage range: 0x02 Unknown number of

<nut-upsuser at lists.alioth.debian.org> I am doing my best to avoid have to spend $280 for a network monitoring card to put into a $190 UPS just to have some good remote monitoring capabilities. Rather, I would like to monitor my many 1U Tripp Lite's on my network using a Raspberry Pi running Raspian and using NUT. However, I cannot seem to get it working. And I while the hardware

On March 6, 2015, at 6:17pm, Charles Leppe ,cleppe at gmail.com> wrote: If this is the same protocol 3005 that we saw in mid-2014 (USB ID: 09AE:0001), then support will be part of the upcoming NUT 2.7.3 release. You wouldn't happen to know anyone who would be able to publish the specs of that protocol, would you? ;-) That would help remove the "experimental driver" warning.

On Mar 6, 2015, at 12:51 PM, Eric Cobb <Eric_Cobb at tripplite.com> wrote: > Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.6.5) > Warning: This is an experimental driver. > Some features may not function correctly. > > Detected a UPS: Tripp Lite /TRIPP LITE SMART500RT1U > Unknown input voltage range: 0x02 > Unknown number of switchable load banks:

> Lots of good progress here! I tried to enable a few more commands for > your model. For instance, the "M" values seem to be min/max voltage, > so there is a "reset.input.minmax" command to use with upscmd. Also, > you can trigger a battery test with "test.battery.start". I assume the > work the same way as on Protocol 3003 :-) Hello Charles, The

Hello Charles, Thank you for all of your help this far. I have made some great progress. I was hung up with all sorts of USB problems which we can chalk up to a "blonde moment" for me (or more accurately, a *bald* moment). In all my starting over and screwing around, I had forgotten to reinstall libusb-compat. Duh! I am now to a point that I think we can dig a little deeper. The

Hello Charles, Thanks for the feedback. I will try to answer some of these questions: > 09AE/0001 is essentially a USB-to-serial converter, and is not > compatible with usbhid-ups. (Theoretically, we could have a companion > driver that talks the same protocols over a real RS-232 port, but the > hardware I used to develop the tripplite_usb driver only has a USB > port.) Ah, that

On Thu, Jun 26, 2014 at 10:20 PM, Steve Ballantyne <steve.ballantyne at gmail.com> wrote: >> However, we don't have all of the 09AE/0001 protocols decoded in the >> tripplite_usb driver. > > I can try to help out on this front? :-) Definitely. >> > 9.783126 Unknown input voltage range: 0x02 >> > 9.783308 Unknown number of switchable

Hello Charles, I think we are making progress! I grabbed nut using git, and applied your patch without any problems. Getting to the point that I could run a configure on my RPi - was something else. I found this blog post, which was very helpful (for anyone else that may try it): http://atelier-orchard.blogspot.com/2013/11/raspberry-pixf86-video-fbdev.html It's not in English, but you get

On Tue, Jul 1, 2014 at 9:17 AM, Steve Ballantyne <steve.ballantyne at gmail.com> wrote: > How would I go about providing you this stuff? Can you point me to > something that would help trace out the USB data? I thought I would try to make sense of the ups.debug data. All I have really figured out is that the fourth hex segment for S is a 00 for plugged in and a 01 for on-battery.

On Jul 3, 2014, at 11:29 AM, Steve Ballantyne <steve.ballantyne at gmail.com> wrote: > input.voltage.maximum: 3341 This number is coincidentally what you would get by reading 0d 0d. I'll have to check the offsets. > input.voltage.minimum: 0 This one might actually be zero, before running the reset minmax command (which also takes a few seconds to be processed). The min/max

On Tue, Jul 1, 2014 at 3:12 PM, Steve Ballantyne <steve.ballantyne at gmail.com> wrote: > On Tue, Jul 1, 2014 at 9:17 AM, Steve Ballantyne > <steve.ballantyne at gmail.com> wrote: >> How would I go about providing you this stuff? Can you point me to >> something that would help trace out the USB data? Tracing the data on Windows is not my speciality, but there are a

> Lots of good progress here! I tried to enable a few more commands for > your model. For instance, the "M" values seem to be min/max voltage, > so there is a "reset.input.minmax" command to use with upscmd. Also, > you can trigger a battery test with "test.battery.start". I assume the > work the same way as on Protocol 3003 :-) > > The attached

How is this for a conundrum? I have three Tripp-Lite SMART5001U's running in the same one rack, attached to the same host running NUT. I am running the tripplite_usb driver thanks to some crafty hacking of Charles (thank you sir!). Now you may ask, "hey dip****, why have THREE 1U UPS's stacked up, when you can have a single larger one with the capacity of three?". Don't

Hey Charles, Many months ago you assisted me in making some code changes to get my Tripp Lite up and running. Thank you for that. Those changes you committed to the repository work very well. I just built a new image for a Raspberry Pi running the latest Raspbian OS and the latest nut-master. I have everything working ... except I seem to be losing my device periodically. So if I enable my

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.

Charles, I need so major help with getting development build working and need some assistance. Here are the issues that we are running into: Number 1 change - 2.7.2 no longer has the HAL scripts that 2.6.5 has. I am working on if HAL is actually required on CentOS6.6 with the 2.7.2 code or if they have another way around it. This is code diving which is taking some time. Number 2 change -

On Jul 10, 2014, at 1:00 PM, Steve Ballantyne <steve.ballantyne at gmail.com> wrote: > How is this for a conundrum? > > I have three Tripp-Lite SMART5001U's running in the same one rack, > attached to the same host running NUT. I am running the tripplite_usb > driver thanks to some crafty hacking of Charles (thank you sir!). Sounds like we can merge that branch into

Hey 2015-04-09 1:46 GMT+02:00 Charles Lepple <clepple at gmail.com>: > On Apr 8, 2015, at 2:04 PM, Eric Cobb <Eric_Cobb at tripplite.com> wrote: > > Charles and list, > > If I leave the driver alone it does not eventually start. It continues to > report that it is unable to connect. I have to perform a upsdrvctl stop ; > upsdrvctl start (I actually just perform

Well, I have good news and bad news. I have a Tripp Lite SmartPro UPS attached to a Linux server running Ubuntu 5.10, and I'm running the just-released nut 2.0.3. I had error -71 from the UPS, which Charles Lepple correctly called out as a likely cable problem (thank you, Charles.) The cable provided with the UPS by Tripp Lite was just plain bad. Not too long, mind you- defective. I