search for: 3024

That It may be right (I don't know), however, where could we confirm whether 3024 is already supported for 2.8.0 or newer? And let's suppose it is. Because current OpenWrt releases are built arround 2.7.4-27, what could I try to backport that (driver mod) to 2.7.4-27? ________________________________ De: Jim Klimov <jimklimov+nut at gmail.com> Enviado: s?bado, 6 de ma...

I think 3024 was added after NUT 2.7.4 release. On Thu, May 4, 2023, 18:20 Feliciano Chavez via Nut-upsuser < nut-upsuser at alioth-lists.debian.net> wrote: > Dears, > > I'm trying to connect this new version of the AVR700U to nut - 2.7.4-27 > running over OpenWrt 22.03.5, installed from...

I have a Tripp-lite AVR700U the website says it's supported but I keep getting the following error message type '-x productid=3024' option .... I'm not sure where to type '-x productid=3024' option at. user1 at user1-laptop:~$ sudo upsdrvctl start Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 This TrippLite device (09ae:3024) i...

I'm mostly not online for a few more days, so can't check directly. The general answers to the two questions would be: 1) checking if it is there: * revise if it is mentioned in the NEWS file (in sources - release tarball or on github); * check issues on github; * search/grep for 3024 in current/release-tagged codebase... 2) getting it to your system: versioning looks debianish, some distros/repos (sid, experimental?) already shipped 2.8.0, maybe you can lift such a build to your box. Otherwise, build your own (in this case current master may be preferable to a year-old release...

...e AVR700U to nut - 2.7.4-27 running over OpenWrt 22.03.5, installed from the stable release repositories, for an ath79 USB2.0 gigabit WiFi router. According to the supported list, I thought this UPS was supposed to use the USB 2010 protocol, but I guess that was an old version because now uses the 3024 protocol (perhaps it would be good to add a note for future buyers). root at Router:/# lsusb Bus 001 Device 001: ID 1d6b:0002 Linux 5.10.176 ehci_hcd EHCI Host Controller Bus 002 Device 002: ID 09ae:3024 Tripp Lite AVR700U Bus 002 Device 001: ID 1d6b:0001 Linux 5.10.176 ohci_hcd Generic Platform OH...

...ov <jimklimov+nut at gmail.com> Enviado: lunes, 8 de mayo de 2023 7:27 a. m. Para: Feliciano Chavez <chavezfeliciano at hotmail.com> Cc: Arnaud Quette via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> Asunto: Re: [Nut-upsuser] NUT support for the new Tripp Lite AVR700U (USB 3024) under OpenWrt? I'm mostly not online for a few more days, so can't check directly. The general answers to the two questions would be: 1) checking if it is there: * revise if it is mentioned in the NEWS file (in sources - release tarball or on github); * check issues on github; * search/...

...> > *Enviado:* lunes, 8 de mayo de 2023 7:27 a. m. > *Para:* Feliciano Chavez <chavezfeliciano at hotmail.com> > *Cc:* Arnaud Quette via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> > *Asunto:* Re: [Nut-upsuser] NUT support for the new Tripp Lite AVR700U > (USB 3024) under OpenWrt? > > I'm mostly not online for a few more days, so can't check directly. > > The general answers to the two questions would be: > > 1) checking if it is there: > * revise if it is mentioned in the NEWS file (in sources - release tarball > or on github)...

"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.trippl...

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 note: I use "upsdrvctl start/stop" to start a...

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", ATTR{idProduct}=="3024", \ MODE="06...

...support is really appreciated for getting it solved. Best Regards, Olaf *lsusb* Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 09ae:3024 Tripp Lite OMNIVSX850 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub config#1 in OMV: driver = usbhid-ups #driver = tripplite_usb port = auto #vendorid = 09...

...ay 20, 2020 2:11:24 PM To: Tom Cooper Cc: nut-upsuser Subject: Re: [POSSIBLE FRAUD] Re: [Nut-upsuser] [EXTERNAL] Re: Help with Tripp Lite Internet600U   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", ATTR{idProduct}=="3024", \ MODE=...

Hello! I am currently having issues monitoring a Tripp-Lite AVR900U. First, here are a few system details: > Manjaro Linux - kernel 5.4.30-1 > network-ups-tools 2.7.4-5 (built from Arch User Repository) > (lsusb output) Bus 003 Device 003: ID 09ae:3024 Tripp Lite AVR900U Contents of /etc/ups/ups.conf: > [tripplite] > driver =  usbhid-ups > port = auto Contents of /etc/udev/rules.d/50-ups.rules: > SUBSYSTEM=="usb", ATTR{idVendor}=="09ae", ATTR{idProduct}=="3024", SYMLINK+="ups0", GROUP=&q...

...Q&m=xxqnPehnxbPZyMn7Y4l3qE4tQqpQ88lYY6CCnQ2qVrU&s=nbzYFun_NHdb-5EB7VMlWNFsqwWbA2-VLKNlBKWFVUQ&e=> Much thanks to David Zomaya for coming up with the recipe! Nut.conf: * Just have MODE=standalone UPS.conf * [tripplite] driver = usbhid-ups port = auto productid=3024 desc = "Tripp Lite Internet600U" upsd.conf * LISTEN 127.0.0.1 3493 LISTEN ::1 3493 [tripplite] driver = usbhid-ups port = auto Create a new udev ruleset: cat /etc/udev/rules.d/90-nut-ups.rules Put this rule in place # /etc/udev/rules.d/90-nut-ups.rules ACTION==&qu...

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=302...

The fix: Was following a howto here: https://raymondjdouglas.com/blog/2018/ups-monitoring/ Much thanks to David Zomaya for coming up with the recipe! Nut.conf: Just have  MODE=standalone UPS.conf [tripplite]      driver = usbhid-ups      port = auto      productid=3024      desc = "Tripp Lite Internet600U" upsd.conf  LISTEN 127.0.0.1 3493  LISTEN ::1 3493 [tripplite]      driver = usbhid-ups      port = auto Create a new udev ruleset: cat /etc/udev/rules.d/90-nut-ups.rules Put this rule in place # /etc/udev/rules.d/90-nut-ups...

...o vi /etc/nut/ups.conf pi at elmer:/home/macbackup $ sudo vi /etc/nut/upsd.conf pi at elmer:/home/macbackup $ sudo upsdrvctl start Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 Can't claim USB device [09ae:3024]: could not detach kernel driver from interface 0: Operation not permitted Driver failed to start (exit status=1) Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 Can't claim USB device [09ae:3024]: could not detach kernel driver from interface 0: Operation...

...ot convinced that I coule come up with a formula to make a working rule. Is there a simple sample I can copy to help figure out elevated privileges? ---- On Wed, 20 May 2020 14:56:14 -0400 David Zomaya <David_Zomaya at tripplite.com> wrote ---- "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.trip...

...Q&m=xxqnPehnxbPZyMn7Y4l3qE4tQqpQ88lYY6CCnQ2qVrU&s=nbzYFun_NHdb-5EB7VMlWNFsqwWbA2-VLKNlBKWFVUQ&e=> Much thanks to David Zomaya for coming up with the recipe! Nut.conf: * Just have MODE=standalone UPS.conf * [tripplite] driver = usbhid-ups port = auto productid=3024 desc = "Tripp Lite Internet600U" upsd.conf * LISTEN 127.0.0.1 3493 LISTEN ::1 3493 [tripplite] driver = usbhid-ups port = auto Create a new udev ruleset: cat /etc/udev/rules.d/90-nut-ups.rules Put this rule in place # /etc/udev/rules.d/90-nut-ups.rules ACTION==&qu...

...day, May 20, 2020 2:11:24 PM To: Tom Cooper Cc: nut-upsuser Subject: Re: [POSSIBLE FRAUD] Re: [Nut-upsuser] [EXTERNAL] Re: Help with Tripp Lite Internet600U 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", ATTR{idProduct}=="3024", \ MODE="06...