similar to: Help with Tripp Lite Internet600U

If I installed and tested against Ubuntu, how useful would that be in general and in this specific case? I think we've seen a few reports of issues with the newer 3024 protocols and I'd like to help get them sorted out. Thank you, David Zomaya Tripp Lite ________________________________ From: Nut-upsuser <nut-upsuser-bounces+david_zomaya=tripplite.com at

That would be great.  If there is something I can do to collect data or troubleshoot, please let me know. ---- On Wed, 20 May 2020 08:51:14 -0400 David Zomaya <David_Zomaya at tripplite.com> wrote ---- I'm still working remotely, but I should be able to get something set up soon. I'll reply all here once I have something to report. Thank you, David Zomaya Tripp

I'm running Raspbian Buster, but given that the error seems to be "higher order" than a hardware issue - one of parsing the protocol?  I suspect that Ubuntu would be a decent "lookalike" to model the issue.  ---- On Tue, 19 May 2020 22:31:56 -0400 David Zomaya <David_Zomaya at tripplite.com> wrote ---- If I installed and tested against Ubuntu, how useful would

Tested a Ubuntu 18.04 LTS virtual machine with NUT 2.7.4 and a 3024 protocol Tripp Lite UPS (mine is a INTERNET550U, but same protocol) :/etc/nut$ lsusb | grep Tripp Bus 002 Device 004: ID 09ae:3024 Tripp Lite I it got generally working (outputting reasonable responses to upsc, although there are some issues with variables like frequency) by adding productid=3024 to my ups.conf. Like this:

"Can't claim USB device [09ae:3024]: could not detach kernel driver from interface 0: Operation not permitted" Is probably an issue with NUT grabbing the UPS... can you disconnect and reconnect the USB cable and try again? If that fails, maybe a udev rule will help. Thank you, David Zomaya Tripp Lite <http://www.tripplite.com/> ________________________________ From:

My thoughts for a test: * Just have MODE=standalone in nut.conf * Put [tripplite] driver = usbhid-ups port = auto productid=3024 desc = "Tripp Lite Internet600U" In ups.conf * Put LISTEN 127.0.0.1 3493 LISTEN ::1 3493 [tripplite] driver = usbhid-ups port = auto in upsd.conf That may be suboptimal but will probably work for a test. Side

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:

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

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

On 9/24/2020 9:05 AM, David Zomaya wrote: > Update from my end: > > I found the old thread where I posted a possible resolution for a similar issue on CentOS 7.6 with the same protocol (2012): > https://alioth-lists.debian.net/pipermail/nut-upsuser/2019-June/011451.html > https://alioth-lists.debian.net/pipermail/nut-upsdev/2019-June/007440.html > > Some of my initial steps

I haven't tried it on RaspberryPi, but if there's some specific Tripp Lite information I can help with, let me know. David Zomaya Tripp Lite ________________________________ From: Nut-upsuser <nut-upsuser-bounces+david_zomaya=tripplite.com at alioth-lists.debian.net> on behalf of Charles Lepple <clepple at gmail.com> Sent: Sunday, December 8, 2019 8:36 PM To: Layne Fowler

I'm still working remotely, but I should be able to get something set up soon. I'll reply all here once I have something to report. Thank you, David Zomaya Tripp Lite<http://www.tripplite.com/> ________________________________ From: Tom Cooper <tom at cooperfamily.xyz> Sent: Wednesday, May 20, 2020 7:48:32 AM To: David Zomaya Cc: nut-upsuser Subject: Re: [EXTERNAL] Re:

Will do. Ball in my court for now. Thank you, David Zomaya Tripp Lite<http://www.tripplite.com/> ________________________________ From: Tom Cooper <tom at cooperfamily.xyz> Sent: Wednesday, May 20, 2020 8:47:28 AM To: David Zomaya Cc: nut-upsuser Subject: Re: [EXTERNAL] Re: [Nut-upsuser] Help with Tripp Lite Internet600U That would be great. If there is something I can do to

I wouldn't be surprised if they both use the same driver. I think they are essentially the same model, but with one having a slightly larger battery. My issue is primarily with the UPS turning back on after having shut off like it should. @Scott Colby if you take a look at the config files I posted in the github issue I created, perhaps that will give you some hints on your issue. Maybe

this probably has no relevance to the subject but i have run a OMNIVS1500XL with the tripplite_usb driver for several years with no problem i am using a a powered usb hub if that make any difference

David, That's exciting - but I am not seeing similar results.  I *must* be doing something dumb - but I can't see it. I've got nut-2.7.4-8 installed on my pi Hope you can help. Tom pi at elmer:/home/macbackup $ lsusb | grep ipp Bus 001 Device 004: ID 09ae:3024 Tripp Lite pi at elmer:/home/macbackup $ sudo cat /etc/nut/nut.conf # Network UPS Tools: example nut.conf #

Hello List, David: I’ thanking you … :-) I’m using the tripplite_usb driver and the barcode on mine says: 9347AIOBC470902728 or 9347A10BC470902728. with pictures… https://drive.google.com/file/d/1SJWDr0g95KOD-FpbOPHUyl9bsbOKePlD/view?usp=sharing https://drive.google.com/file/d/1SFMT-GbZRcRO03gEy_7SszZ43-LYmEZM/view?usp=sharing

David, I appreciate the quick feedback! If I didn't fat finger any of the parameters you sent me, it's still not working. Here's the output from the attempt to start.  (BTW - nothing appears in the daemon.log when I use the upsdrvctl command.) pi at elmer:/home/macbackup $ sudo vi /etc/nut/nut.conf pi at elmer:/home/macbackup $ sudo vi /etc/nut/ups.conf pi at

Hi David On 4/29/20 3:28 PM, David Zomaya wrote: > Is NUT using the same SNMP v3 user as your SNMP Set or a different one? > > If it is a different one (e.g. an SNMP v1 or v2c string) does that user > / community string have read/write access? I tried setting them all with -x thing= arguments as well as letting it pull from ups.conf, same result. It's all SNMPv3 settings. sudo