similar to: Tripplite OMNIVS1500 Woes

Hello All, This is my first post to the list & I have tried to do as much searching and debugging on my own as I can bear. Please HELP! I am currently using up to date Centos 5.2 32-bit - kernel version: 2.6.18-92.1.10.el5PAE #1 SMP. I am using a Tripplite OMNIVS1500 via usb connection. I am using the tripplite_usb driver. I have tried to user versions 2.2.0 from an rpm, 2.2.2 & and the

I'm having problems creating a UPS connection to my Tripp Lite UPS System: Ubuntu 8.04.2 Nut 2.4.1 freshly compiled from source. When I do upsdrvctl start everything appears to work and I get :Detected a UPS: TRIPP LITE/TRIPP LITE UPS Using OMNIVS 2001 protocol (2001) Unit ID not retrieved (not available on all models) Attached to Tripp Lite UPS But

Leslie, This message is most appropriate for the NUT user list. I kept Rik Faith's and Nicholas Kain's copyright information because the tripplite_usb driver borrows heavily from the tripplite (serial) driver, but they are not responsible for the mess that I made in the USB driver. See below. On Dec 28, 2008, at 5:28 PM, Lelsie Rhorer wrote: > Gentlemen, > >

Using this UPS in the UK on 240V mains. Connected via USB: Bus 001 Device 002: ID 09ae:0001 Tripp Lite Requires tripplite_usb driver as it is (Product ID: 0001). There is an entry in the compatibity list for OMNIVS800 USB (protocol 2012) using usbhid-ups which is little misleading (although I guess maybe correct for some instances of the UPS). OMNIVS1000 USB (older; product ID: 0001) is

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

Got one of these up and running with the tripplite_usb driver on Ubuntu Server 12.04 x64. This particular model has product code 0x1000. Setup and installation was pretty standard. The only hiccup was I had to create a udev rule to give the nut group access to USB devices. If anyone has any questions let me know. Here's what I am got back from the upsc command: battery.charge: 100

Model: Tripp-lite OMNIVS1500 Error: Network UPS Tools - UPS driver controller 2.2.1- Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.11 (2.2.1-) Warning: This is an experimental driver. Some features may not function correctly. Detected a UPS: unknown/unknown libusb_set_report() returned -1 instead of 8 Could not reset watchdog. Please send model information to nut-upsdev mailing

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.

Device manufacturer and name: Tripp-Lite OmniSmart500 upsc output: matt at backup:/etc$ sudo upsc tripplite battery.charge: 100 battery.test.status: Battery OK battery.voltage: 14.56 battery.voltage.nominal: 12 device.mfr: Tripp Lite device.model: OMNISMART500 device.type: ups driver.name: tripplite_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.4.3

On Sep 25, 2014, at 5:51 PM, Dave Williams <dave at opensourcesolutions.co.uk> wrote: > Using this UPS in the UK on 240V mains. > > Connected via USB: > Bus 001 Device 002: ID 09ae:0001 Tripp Lite > > Requires tripplite_usb driver as it is (Product ID: 0001). There is an > entry in the compatibity list for OMNIVS800 USB (protocol 2012) using > usbhid-ups which is

Hi, I am trying to configure my Tripp Lite SU5000RT3U on Ubuntu 18.04 as I am not able to completely get all the data from the UPS. After installing all required packages from the Ubuntu repos (had to run sudo apt-get install dkms, I had to install the displaylink drivers from displaylink.org by doing sudo ./displaylink-driver-4.2.29.run, and I created a sim link by doing the following: sudo ln

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

<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

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

Hello, I have a TrippLite SMART1500RMXL2U that I'm trying to get running with Nut 2.2.1. Running upsdrvctl start works, upsd works, but upsc has "issues": je-nas:~/src/nut-2.2.1# upsdrvctl start Network UPS Tools - UPS driver controller 2.2.1- Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.11 (2.2.1-) Warning: This is an experimental driver. Some features may not

Howdy, I had this working with lots of help for a developer before (Charles Lepple), but after upgrading to a somewhat more current version of FreeBSD the patched-up version stopped working. Seeing as this was more than a few years ago, I thought I'd give a new libusb and NUT a try to see if it might work out of the box. So far, no luck. Some info: FreeBSD 6.3 libusb 0.1.12 NUT 2.4.1

I'm working on a gentoo server with Nut 2.0.5-r1 and libusb-0.1.12. I originally tried the hidups driver which seemed to work, but produced a large amount of unhandled events. Then I tried the newhidups which told me my ups wasn't supported. When I try using tripplite_usb -u root -DDDD /proc/bus/usb/002/002 I get that there isn't a match. But when I try using tripplite_usb -DDDD

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:

Hey all, I have a triplite 1050 and when I did a test today I saw that the battery bounce from 100 to 80 to 90 to 91 percent before UPSD lost its connection to the UPS. The server then decided that it was time to shut off. The UPS sat at 91% for about 5 min before UPSD lost its connection, so I'm not sure if it wasn't updating its battery.charge... I wasn't sure if this is

On Sep 26, 2014, at 8:31 AM, Dave Williams <dave at opensourcesolutions.co.uk> wrote: > On 08:09, Fri 26 Sep 14, Charles Lepple wrote: >> Well, I ended up linking to the latest version of those files, so this shows the change better: >> >> https://github.com/networkupstools/nut/commit/f61edb5161de97944074867832edc014323340b1 >> >> Still a magic constant,