similar to: Fwd: Fun with TrippLite

Hi Jonathan and Charles, yes, the Tripp-Lite HID subdriver was under development. I started it based on the debug output posted by somebody on this list a few weeks ago, but then I either didn't get the information I needed, or got too busy to act on it. That driver is still incomplete, in the sense that there are many unmapped device variables. Jonathan, if you run this driver, could you

Hey I recently picked up a couple SMART1000LCD TrippLite UPS's. These are similar to other usb ups's that have been mentioned on the list in the past few months. I tried a few patches posted last month and got some amount of success. That being said, I am thus far unable to get much love from the actual upsd itself. Any pointers in terms of what I may need to change or what help I can

I'm read through the archives trying to figure out how to get a Tripplite SmartPro SLT 1500 configured with NUT using the USB interface (it also has a serial interface but I'd rather not). The thread which this link belonged to seemed most instructive: http://lists.alioth.debian.org/pipermail/nut-upsdev/2007-January/001656.html and I followed it as best I could. I'm running a

These patches allow this device to function in nut.. diff --git a/trunk/drivers/tripplite-hid.c b/new/drivers/tripplite-hid.c index c36da98..dddd13c 100644 --- a/trunk/drivers/tripplite-hid.c +++ b/new/drivers/tripplite-hid.c @@ -71,6 +71,8 @@ static usb_device_id_t tripplite_usb_device_table[] = { { USB_DEVICE(TRIPPLITE_VENDORID, 0x2005), battery_scale_0dot1 }, /* e.g. TrippLite

While working on the mge-hid subdriver, I wanted to add the 'beeper.mute' command. Unfortunately, the description I intended to use was used already by the 'beeper.off' instcmd: CMDDESC beeper.off "Temporarily mute the UPS beeper" Now of course we could add another instcmd 'beeper.reallyoff', but instead I would prefer to bite the buller and do the following:

I?m setting up a new system and installed a new UPS with nut. System Specifics: OS: Debian 3.16.36 Nut version: 2.7.2 Install method: apt-get Device: TRIPPLITE SMART1300LCDT using usbhid-ups driver Problem: The output from upsc has a few incorrect values. They appear to be a matter of scale. root at server:/etc/nut# upsc tripplite at localhost Init SSL without certificate database

Thanks, now I started getting messages from the list. As you advised, I renamed the mib file NETCARD.mib to Tripplite and ran command ./gen-snmp-subdriver.sh -H 10.200.254.39 -c public -n Tripplite Here is what it says: snmp_build: unknown failuresnmpget: Error building ASN.1 representation (Can't build OID for variable) COUNT = 0 / 0 Creating tripplite-mib.h Creating tripplite-mib.c Done.

Hello, I am hoping someone can point me in the right direction. I am setting up a new UPS, most things seem to be working except the UPS turns off immediately during a test shutdown using///"//upsmon -c fsd".//No delay before the UPS turns itself off leaving no time for the server to shutdown properly. I have attempted to set the delay higher using "upsrw -s

Just started using NUT and having a problem. I'm not sure if it is even NUT that is causing the issue. I'm running the latest FreeNAS 9.3 release. Network UPS Tools upsmon 2.7.2. The UPS is a Tripplite SU6000RT4UHVPM with the SNMPwebcard installed. I'm trying to use the SNMPwebcard, not USB or Serial. I've updated the SNMPwebcard to the latest firmware version (see below). In

I think I'm going to have the slightly rejigger the tripplite-hid.c driver to 'properly' support all of the data I know about it's outlets. A given UPS may have 'n' output loads. I could have 5, I could have 10, I won't know until I actually ask the UPS. But in order to use the hid to nut struct, I'm actually going to have to modify that struct dynamically, or

Joel Peshkin wrote: > > I hacked in the following additonal changes... > > Index: newhidups.c > =================================================================== > RCS file: /cvsroot/nut/nut/drivers/newhidups.c,v > retrieving revision 1.1.1.1.8.6.2.21 > diff -u -r1.1.1.1.8.6.2.21 newhidups.c > --- newhidups.c 7 Nov 2005 22:14:20 -0000 1.1.1.1.8.6.2.21 > +++

Hey all, I am trying to use NUT for a Tripplite Smart1200 LCD on a fresh copy of Debian 6.0.2.1. I installed NUT version 2.4.3 and I have pored through pages and pages of other posts, but for the life of me I can not get it to recognize the Tripplite. I know its an 09ae:2009 device and I've tried to add a rule in /lib/udev/rules.d/52-nut-usbups.rules as according to some posts, but to no

No, it's not. I'd defer to the list for tips on that one. First thing I'd try if no one else has ideas is checking lsusb and restarting the service. Thank you, David Zomaya Tripp Lite<http://www.tripplite.com/> ________________________________ From: Tom Cooper <tom at cooperfamily.xyz> Sent: Wednesday, May 20, 2020 7:00 PM To: David Zomaya Cc: nut-upsuser

Hello, Control HP R1500 G2 with nut via USB. Ubuntu 14.04.5 LTS (GNU/Linux 4.4.0-72-generic x86_64) nut V2.7.1 installed from repository /etc/nut/ups.conf [HPR1500] driver=usbhid-ups port=auto After dealing hours with this, hope this will help some : rename udev rule to higher priority and move it to its right location, reload udev rules mv /lib/udev/rules.d/52-nut-usbups.rules

Hi, Nut-upsusers, I am having problem configuring NUT to work with Tripplite UPS through SNMP. There is a Tripplite SmartOnline SU10KRT3/1X and attempts to monitor it using NUT though SNMP are failing... OS: Enterprise Linux 6, Nut version: 2.6.5. ups.conf is configured: [trippliteups] driver = snmp-ups port = 10.200.254.39 desc = "ProductionServer"

Glad to hear it's working, thanks Tom. Network UPS Tools team: is fixing this as simple as me telling you what new UPS protocols are HID-PDC compliant? Thank you, David Zomaya Tripp Lite<http://www.tripplite.com/> ________________________________ From: Tom Cooper <tom at cooperfamily.xyz> Sent: Wednesday, May 20, 2020 2:42 PM To: David Zomaya Cc: nut-upsuser Subject: Re:

On Feb 10, 2014, at 1:16 AM, ??? ????? wrote: > Thanks for you reply. Concerning the subscribtion list, I have earlier filled in the fields and sent request to subscribe to this list, but still haven't got an answer. I added you manually, but check your spam folder just in case it ended up there. > Yes, I do have a MIB file that was on CD that came with the UPS, attached it to this

Hi, With recent revision, it's impossible to get upsdrvctl started: [root at teevee nut]# /usr/local/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.3.0-1352 Network UPS Tools: 0.29 USB communication driver - core 0.33 (2.3.0-1352) Warning: This is an experimental driver. Some features may not function correctly. Using subdriver: TrippLite HID 0.2 (experimental)

OpenBSD 6.1/amd64 nut-2.7.4p0 (from OpenBSD package) UPS: Tripp-Lite OMNI1500LCDT I cannot get the driver for the UPS to load without error. Here are the commands, with the output, and the config files: ======================================================= # upsdrvctl start Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication

Hello Nut Devs, I'm working with usbhid-ups and a Tripplite OMNI1000LCD. I used a USB packet sniffer to discover something cool about the watchdog feature in this unit. (not sure if the other OMNI-X-LCD models work the same or not.) Basically there's a single HID variable at Report ID 0x52 (UPS.OutletSystem.Outlet.ffff0092) that's one byte (0-255 int) and it contains the Watchdog