search for: smart500rt1u

...003 :-) Hello Charles, The patch that you provided appears to have worked. The first patch probably worked too ... but I left the driver running throughout the rebuilding process (woops). Some new commands being demonstrated ... pi at raspberrypi ~/nut $ /usr/local/ups/bin/upscmd -u pi -p pi -l SMART500RT1U at localhost Instant commands supported on UPS [SMART500RT1U]: load.off - Turn off the load immediately load.on - Turn on the load immediately reset.input.minmax - Reset minimum and maximum input voltage status shutdown.return - Turn off the load and return when power is back test.battery.start -...

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:...

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 SMART500RT...

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: 0x01 > Unit ID: 65535 > Unknown protocol (3005) 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...

...to get this unit to communicate with the current version of NUT for CentOS? -Eric Cobb From: Charles Lepple [mailto:clepple at gmail.com] Sent: Friday, March 06, 2015 6:17 PM To: Eric Cobb Cc: Nut-upsuser at lists.alioth.debian.org Subject: Re: [Nut-upsuser] Problems communicating with Tripp Lite SMART500RT1U via USB with CentOS 6.6 and NUT 2.6.5 On Mar 6, 2015, at 12:51 PM, Eric Cobb <Eric_Cobb at tripplite.com<mailto: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 func...

...ardware compatibility list says that it is supported - I certainly have my doubts. According to the list, I should be using the usbhid-ups driver. But when I do that, it fails and tells me that I should be using tripplite_usb instead. pi at raspberrypi ~ $ sudo /lib/nut/usbhid-ups -DDD -u root -a SMART500RT1U Network UPS Tools - Generic HID driver 0.37 (2.6.4) USB communication driver 0.32 0.000000 debug level is '3' 0.007268 upsdrv_initups... 0.011293 Checking device (09AE/0001) (001/009) 0.015827 - VendorID: 09ae 0.017073 - ProductID: 0001 0.018406 - M...

...or=softlayer-ams" -O libusb-compat-0.1.4.tar.bz2 tar -xjf libusb-compat-0.1.4.tar.bz2 cd libusb-compat-0.1.4 ./configure && sudo make install cd .. #get back to home root cd .. #download nut from dev repo git clone git://github.com/networkupstools/nut.git cd nut #patch for TrippLite SMART500RT1U wget http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140628/a7e23666/attachment.bin -O charles-tripplite.patch patch -p1 < charles-tripplite.patch echo "Running autogen ..." ./autogen.sh #create some groups and directories and mod some persmissions sudo groupadd nu...

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 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

...ier, I can diff it against Git master. Hello Charles, Thanks for the patch! It went down cleanly. I then did: make clean, make, and make install. Everything went fine. But I'm not able to access those additional commands ... pi at raspberrypi ~/nut $ /usr/local/ups/bin/upscmd -u pi -p pi SMART500RT1U at localhost reset.input.minmax Unexpected response from upsd: ERR CMD-NOT-SUPPORTED pi at raspberrypi ~/nut $ /usr/local/ups/bin/upscmd -u pi -p pi SMART500RT1U at localhost test.battery.start Unexpected response from upsd: ERR CMD-NOT-SUPPORTED pi at raspberrypi ~/nut $ /usr/local/ups/bin/upscmd...

...; 9.472899 send_cmd(msg_len=2, type='P') > > 9.473087 send_cmd: sending 3a 50 af 0d 00 00 00 00 '.P......' > > 9.575667 send_cmd: received 50 30 30 35 30 30 58 0d 'P00500X.' (OK) > > 9.576026 send_to_all: SETINFO ups.model "SMART500RT1U" > > 9.576848 send_to_all: SETINFO ups.power.nominal "500" > > 500W sounds right based on the name. Yes! It is a 500W, for sure. > > 9.577346 send_cmd(msg_len=2, type='F') > > 9.578194 send_cmd: sending 3a 46 b9 0d 00 00 00 00...

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

...to the LD_FLAGS. So - here I am starting up nut in debugging level 5, and it looks "promising"? :-) =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2014.06.28 21:54:46 =~=~=~=~=~=~=~=~=~=~=~= ]0;pi at raspberrypi: ~/nut[01;32mpi at raspberrypi [01;34m~/nut $ sudo ./drivers/tripplite_usb -u root -a SMART500RT1U -DDDDD Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.24 (2.7.2-signed-19-g90e2790) Warning: This is an experimental driver. Some features may not function correctly. 0.000000 debug level is '5' 0.009251 Checking device (067B/2303) (001/010) 0.012869 - VendorID...

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.

...are identical ... I cannot get nut to tell them apart and so I can only monitor one of them at a time! Before I go writing a script that bounces between the three of them, is there a way I can get all three to work? It seems that I can use 'sudo /usr/local/ups/bin/upsrw -u pi -p pi -s ups.id=1 SMART500RT1U-1 at localhost' to change the id (from the default of zero). But then when I load up the next one, nut says "oh, I remember this one ... it has an id of 1!". So it assigns '1' as the id of the second UPS, then dropping the first. UGH. Then I was looking at using the driver...

..., add a hub in front of one UPS, and plug the other UPS directly into the host. Beware that you are adding an additional point of failure, and will need probably to power this hub if it is not bus-powered. > It seems that I can use 'sudo /usr/local/ups/bin/upsrw -u pi -p pi -s > ups.id=1 SMART500RT1U-1 at localhost' to change the id (from the default > of zero). But then when I load up the next one, nut says "oh, I > remember this one ... it has an id of 1!". So it assigns '1' as the > id of the second UPS, then dropping the first. UGH. Something like that......

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

...cting itself, which wouldn't surprise me. These devices are not known for their grand monitoring abilities. The word "Smart" probably doesn't belong in the title. But they are 1U, cheap, and the batteries last around 3+ years. I ran this ... /usr/local/ups/bin/tripplite_usb -a SMART500RT1U -u pi -DDDDD 2>&1 | tee driver-debug-log.txt Does this snippet of a failure tell you anything? Is there something I can do to tell the libusb to wait a little longer for the device to come back? 3116.403776 send_cmd(msg_len=2, type='P') 3116.403858 send_cmd: sending 3a 50...

...and, it should still be possible to grab the SRPM for NUT, extract it to /usr/src, change the version number to 2.7.whatever, rebuild the binary RPMs, and reinstall. I am really a newbie when it comes to the building of packages. Where do I get that SRPM for the NUT version that will work with the SMART500RT1U? Does anyone have a RPM of 2.7.2.6 that is built for Centos 6.6 that I could try? Here is the environment- OS: Centos 6.6 Kernel: 2.6.32-504.8.1.el6.x86_64 Nut Version: nut-2.6.5-2.el6.x86_64 Eric K. Cobb Product Management Specialist [Tripp Lite] 1111 W. 35th Street | Chicago IL 60609 USA...

On Thu, Jul 10, 2014 at 10:33 PM, Charles Lepple <clepple at gmail.com> wrote: > Sounds like we can merge that branch into master? I thought I had discovered a firmware difference (or something) because I couldn't get the battery tests to run. But then I realized that I wasn't running the actual test under the right user, with the right permissions. Duh. So I then went back