similar to: Tripp Lite OMNIVS1500XL, tripplite_usb, Error reading {L, S, B} value

Good afternoon, I'm trying without much success to monitor a Tripp Lite OMNIVS1500XL using NUT. I checked the compatibility list and saw that this UPS is supported by tripplite_usb. The system is running Debian Stable, but I've downloaded NUT 2.0.3 and compiled from source since the packaged 2.0.1 doesn't include tripplite_usb. I compiled --with-user=nut. My first attempt at

Hi, When I start upsd under normal conditions, I get this: -------------------------------------------------------------------------------- Network UPS Tools upsd 2.0.4 /etc/nut/upsd.conf is world readable Can't connect to UPS [tripplite] (tripplite_usb-auto): No such file or directory /etc/nut/upsd.users is world readable Synchronizing........ giving up

All, I recently purchased a Tripp-Lite OmniVS1500XL and am running NUT on a Centos-based system. Based on the compatibility list I specified the tripplite_usb driver. When I query the unit I get: [root@chryxus ~]# upsc UPS@localhost battery.voltage.nominal: 24 driver.name: tripplite_usb driver.version: 2.0.3-pre2 driver.version.internal: 0.6 input.voltage.nominal: 120

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

Arnaud: I just wanted to chime in here to say that getting these TrippLite USB UPS's supported under a NUT driver would be fantastic! They are simple, inexpensive UPS's (under $100 for 1000VA at Costco) and it would be quite the "deal of the year" to be able to buy these units so cheaply and monitor them directly via Linux. I already have 5 of these units and have

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

i just purchased a tripp lite OMNIVS1500XL and have been attempting to get it working with the usb drivers since it doesn't have a serial port. it hasn't been anywhere near successful and i was hoping someone might be able to point me in the right direction. i run gentoo and this is what i currenlty have installed: nut 2.0.2 libusb 0.1.10a (gentoo modified) usbutils 0.11-r5

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 -

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

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.

Test machine: Windows 7 Pro x64, NUT 2.6.5-3 UPS model: Tripp-Lite Internet Office UPS (INTERNET525U) I needed a UPS and I had this old, but lightly used Tripp-Lite in storage. On the compatibility list I see a (?similar?) INTERNETOFFICE700 using the tripplite_usb driver. But the driver is not liking this particular model that I have. I'll be receiving a 3S550 soon, so I'm not

I'm trying to get a SMART2200CRMXL to work with nut, using a USB cable. tripplite_usb -a upsname returns: Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.11.1 (2.2.2) Warning: This is an experimental driver. Some features may not function correctly. No matching USB/HID UPS found My system info: CentOS 5.5 nut installed from repo upsd version 2.2.2 TrippLite SMART2200CRMXL

On May 15, 2014, at 9:39 PM, Stefan Bruda wrote: > What bugs be though is that I cannot seem to be able to read the > remaining run time on battery. The battery charge is also widely > inaccurate (it drops to zero really fast and stays there). I read > somewhere that the usb.debug numbers may hold the key to this (at > least to the running time that is), but I don't know what

Hello, I own an older Tripp Lite SMART3000RM2U (protocol 3003). It does not work with usbhid-ups but it mostly works with the tripplite_usb driver (nut 2.7.1, the latest in the Gentoo tree), in the sense that the status (on line, on battery, etc.) is detected correctly, the machine is shut down on critical battery, and I can even get some information from the UPS. This is how it all looks:

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

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

This is a USB only ups. I could not make it work with nut. So I put this daemon together. Get it from http://www.vsys.org/sventura/dev/ at the bottom of the page. Init scripts are gentoo based but I think it should be easy to adjust them to any distro. I am planning to integrate it with nut if I can find the time and there is enough interest on it to justify the project. This is a very entry

On May 24, 2014, at 5:49 PM, Stefan Bruda wrote: >> Don't worry about the battery physical properties for now - the >> problem there is that we don't have enough information from the UPS >> to do a proper calculation. With the V_interval[] settings, you can >> tweak the new state-of-charge calculation to match what you see via >> upsc when the battery is

Hello, At 15:42 -0400 on 2014-6-1 Charles Lepple wrote: > > On May 24, 2014, at 5:49 PM, Stefan Bruda wrote: > > >> Don't worry about the battery physical properties for now - the > >> problem there is that we don't have enough information from the UPS > >> to do a proper calculation. With the V_interval[] settings, you can > >> tweak

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