similar to: Problem detecting USB/HID UPS

I am running Debian Etch, with the nut 2.0.4 packages, and I get a segmentation fault from tripplite_usb. # /lib/nut/tripplite_usb -u root -DDDDD auto Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.6 (2.0.4) Warning: This is an experimental driver. Some features may not function correctly. debug level is '5' Checking device (09AE/0001) (002/004) - VendorID: 09ae -

The Compatibility page lists the OMNIVS1000 as supported, but the tripplite_usb driver doesn't seem to recognize my UPS. Below is the debug dump from attempting to load the driver. I am using the nut package from Debian: 2.2.1-2.1 and I was wondering if this was a known issue? maroon:/lib/nut# /lib/nut/tripplite_usb -DDDDD -a usbups Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver

Hi Greg, I haven’t but I will give that a shot later this week and advise. Thanks for the tip. Thank you, David Zomaya Technical Support [cid:image007.png at 01D525AF.B38D63F0] 1111 W. 35th Street | Chicago, IL 60609 USA 773.869.1156 | david_zomaya at tripplite.com [cid:image008.png at 01D525AF.B38D63F0]<http://www.tripplite.com/> From: Nut-upsuser

<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

Ok, so I have made some progress that seems to suggest the initial “fix” I stumbled upon isn’t required. I haven’t yet worked backwards to figure out reasons why our customers have had similar complaints or solve the problem on the CentOS VM yet, but that is on the todo list. I am hoping it ends up just being not enabling the service on startup, but I can’t say that explains away all the symptoms

Hi, I'm running Fedora Core 6 and need to monitor a Tripp Lite SMART2200RMXL2U. I've loaded the nut-2.0.3-2.1 RPM. The UPS is connected via the provided USB cable, and that much appears to work: # dmesg | grep -i tripp hiddev96: USB HID v1.10 Device [Tripp Lite TRIPP LITE SMART2200RMXL2U ] on usb-0000:00:1f.4-2 # lspci | grep -i usb 00:1f.4 USB Controller: Intel Corporation 82801BA/BAM

Hi Patrick, in February, you tried to post the below message to the nut-upsuser list, but the post was rejected because you were not subscribed to the list. Unfortunately, you did not subscribe and re-post it. Anyway, I have been working on Tripp-Lite support for newhidups recently, and I wonder if you have any feedback. Did you ever get this device to work? >From the information you sent,

To all, I attempted to configure the UPS tools for the Tripp-Lite SmartOnline 1500VA 2U rackmount UPS. I followed the instructions from the 'upsdrvctl start' output and posted the diagnostic information below. Is my UPS using an unknown product ID as reported? From the mailing list archive, I have found another posting for the same UPS with device model '09AE/4003', whereas

I purchased a TrippLite ECO550UPS from Amazon a few days ago thinking I was going to use it for my Windows Media Center HTPC. I've since changed my mind and decided to use Mythbuntu but it I can't get my UPS working with nut. I've tried all of the tripplite drivers and the usbhid-ups driver. The tripplite_usb and usbhid_ups output is listed below. The tripplite and tripplitesu drivers

Has anyone gotten this model of tripp-lite to work? sudo /usr/local/bin/upsdrvctl -DDDDD -u root start Network UPS Tools - UPS driver controller 2.0.5 Starting UPS: tripplite exec: /usr/local/bin/tripplite_usb -a tripplite Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.7 (2.0.5) Warning: This is an experimental driver. Some features may not function correctly. Detected a UPS: TRIPP

Hi Network UPS Tools Support, I'm not sure if this is a question for the "user group" or the developer group". My name is David Zomaya and I work at Tripp Lite in our technical support department. Copied on this email are Eric Cobb from our Product Management group & Jonathan Manzanilla tech support subject matter expert for our single phase UPS product lines. Recently,

Hi Network UPS Tools Support, I'm not sure if this is a question for the "user group" or the developer group". My name is David Zomaya and I work at Tripp Lite in our technical support department. Copied on this email are Eric Cobb from our Product Management group & Jonathan Manzanilla tech support subject matter expert for our single phase UPS product lines. Recently,

As I understand it from looking through the archives of this mailing list and the source for the driver, tripplite_usb should work for this device. I tried to go through the source as best I could to see if I could add support myself, but got a bit lost. Anyhow, here's hoping that someone has some experience with this model. My system is using the latest CVS checkout of the Development branch

I'm running FreeBSD 6.2 with Nut 2.0.5 installed from ports... I have a TrippLite OmniVS1500XL plugged in, but I'm having little luck with the tripplite_usb module. I have already built and booted a new kernel with UHID disabled so that libusb can grab /dev/ugen0. At first I was able to get the following out of the driver: # USB_DEBUG=5 /usr/local/libexec/nut/tripplite_usb -u root

Good afternoon, I am trying to communicate with a new Tripp-Lite UPS via usb and having little luck. After more than a week on this I've decided to ask for help. I am very inexperienced at posting information to message boards, so hopefully I'm doing this right. I assume this is the correct place to post this message. I will start with the equipment I have. I am using Debian Sarge

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:

Thanks for the inputs. I’ll get CentOS 7.6 installed on a physical machine this week and follow up. Few responses and notes below in the interim. ”The log format looks okay, but I may not have been clear that I was looking for the log at the same time as when the kernel errors occur. So without the udev rules would be good.” Ah, sorry. Attached are these two files: 1-

Borrowing from our friends at Ask Ubuntu ( https://askubuntu.com/a/276637 ) there is. I've modified it for use with a Tripp Lite UPS and 3024 protocol below. Try disconnect/reconnect after and see what happens. :/etc/nut$ cat /etc/udev/rules.d/90-nut-ups.rules # /etc/udev/rules.d/90-nut-ups.rules ACTION=="add", \ SUBSYSTEM=="usb", \ ATTR{idVendor}=="09ae",

Wow - you're doing all the work for me! Thanks for the rule set.  I can't easily reboot that box just now, so I'm working on reloading the rules. When I try  udevadm control --reload-rules && udevadm trigger May 20 15:19:01 elmer systemd-udevd[3413]: Process '/sbin/crda' failed with exit code 234. May 20 15:19:01 elmer systemd-udevd[3413]: Using default