similar to: UPS Product additions to NUT HCL list for compatible Tripp Lite UPS systems

On Oct 15, 2013, at 3:40 PM, Eric Cobb wrote: > My name is Eric Cobb and I am a Product Specialist with Tripp Lite. We have tested your latest NUT distributions against our HID USB compatible UPS systems and would like to know what is needed and/or who is needed to contact in order to updated the listing of compatible Tripp Lite UPS systems in your HCL list? Hi Eric, From end users of NUT,

Hello Mr. Leppe, See the attached excel file that covers the current Tripp Lite HID compatible UPS systems. There is also an attached Word document covering the UPSC / UPSCMD / UPSRW information from the specific UPS systems. Let me know if this is adequate to get our additional HID compatible products added to the NUT HCL listing. Tripp Lite Eric K. Cobb Product Management Specialist 1111

On Oct 30, 2013, at 11:29 AM, Eric Cobb wrote: > See the attached excel file that covers the current Tripp Lite HID compatible UPS systems. There is also an attached Word document covering the UPSC / UPSCMD / UPSRW information from the specific UPS systems. Let me know if this is adequate to get our additional HID compatible products added to the NUT HCL listing. Mr. Cobb, Thanks, that is

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 -

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

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

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

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

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,

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:

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 22:17, Thu 25 Sep 14, Charles Lepple wrote: > > I think the OMNIVS800 protocol 2012 entry came from Tripp Lite test results. (There have definitely been naming collisions in the past; hence, the messages in the drivers if you accidentally choose the wrong one.) > > Confusingly, if the USB ProductID is 0001, the Tripp Lite specific "Protocol" number (shown in

> > battery.charge: 3 > battery.charge.low: 10 > battery.charge.warning: 30 > battery.runtime: 93 > battery.temperature: 32.9 > battery.type: PbAC > battery.voltage: 46.4 > battery.voltage.nominal: 48.0 Is it possible that battery.charge is really 30% rather than 3%? The 3016 protocol models have issues with scaling on some of the voltages and frequencies. You can see

I'm having trouble with a TrippLite SU3000XLCD. I'm using a Raspberry Pi running Raspbian (wheezy) with NUT 2.6.4. I can monitor my older TrippLite UPSs, mostly SU1000RT2Us, with this Pi and a USB to serial adapter. My first thought with the SU3000XLCD was to use the USB port instead of the serial port as that's the "modern" thing to do. When I plugged the USB cable in

Charles, Thanks again for your help. We were able to have a 2.7.2.6 build complied into a working RPM for CENTOS 6.6. There is one more issue that needs to be addressed: The init script no longer works so a new script needs to be written to enable and disable the ups functionality, however it is communicating with the UPS properly. The question I have at this point is, is there a way I can

Tripp Lite SMART1300LCDT # upsc ups battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 30 battery.runtime: 2951 battery.type: PbAC battery.voltage: 0.0 battery.voltage.nominal: 24.0 device.mfr: Tripp Lite device.model: TRIPP LITE UPS device.serial: 2250AVLSM872100251 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

Thank you for your answer. I will try to investigate the possibility that the Tripplite serial cable has a different pinout than a standard RS-232 serial cable. I wouldn't use the NUT at this point because I don't think I will be able to write a software update to adapt the NUT to my needs. My idea was first to test the protocol via a serial terminal client directly connected to the UPS,

Greetings all, Anyone have a clue on this behavior (see below) on this behavior with FreeNAS-8.3.0-RELEASE-x64 (r12701M) on a TrippLite 1500LCD UPS? NUT version is 2.6.5 Using the following profile: Tripp-Lite ups 2 Smart1500LCD USB (usbhid-ups) I get the following: Dec 10 21:40:12 nas6 kernel: uhid0: <Tripp Lite TRIPP LITE UPS, class 0/0, rev 1.10/0.02, addr 2> on usbus1 Dec 10 21:40:12

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