Since you have it working on Windows how feasible is it to sniff the connection and reverse engineer the protocol. I think that it has been done in the past when all else failed in getting documentation. I am not sure how much of the existing driver is working and how much is not but if it is not too many commands it may be worth a try. I know wireshark has a USB sniffer built into the latest build.
Just a passing thought... and like the wind it's gone..... On Fri, Jul 31, 2020 at 12:12 AM Scott Colby <[email protected]> wrote: > > No, I had not! I'll take a look at the protocol docs. > > My problem is the opposite: all the permutations that NUT can send of "turn > off but turn back on later" either do nothing or turn the UPS off in such a > way that it requires me pressing the physical power button to bring it back > on. (I guess I haven't tested trying commands to turn it back on, but that's > not so helpful if the controlling device is powered by the UPS.) > > Thanks, > Scott > > On Sun, Jul 26, 2020, at 14:59, David Zomaya wrote: > > Did you see what objecttothis posted on GitHub already? > > In any event, your issue with NUT and the 3024 AVR750U is that the UPS > reboots output instead of shutting off when the shutdown command is sent, > correct? > > Good suggestion on the driver authors, thanks. > > > > > Thank you, > David Zomaya > > > > > > From: Nut-upsuser > <nut-upsuser-bounces+david_zomaya=tripplite....@alioth-lists.debian.net> on > behalf of Scott Colby <[email protected]> > Sent: Saturday, July 25, 2020 4:11 PM > To: [email protected] > Subject: [EXTERNAL] Re: [Nut-upsuser] OMNIVSX1000D Compatibility > > > ______________________________________________________________________ > Hi, > > I can confirm that with my AVR750U connected to my Windows machine > using the TrippLite Power Alert software, I can configure it to do > the behavior I want: turn off at a low power level and turn back > on when the power is reconnected, so I guess it's now a question > of if NUT can be adapted to the 3024 protocol. > > I am not the most experienced C programmer out there, but given > there are extensive examples in the rest of the NUT USB drivers, I > would be willing to take a stab at a Pull Request to integrate the > protocol once the documentation has been provided. I also noticed > that there are some names at the top of the TrippLite USB HID driver > source file. Perhaps it would be worth reaching out to them for > advice. > > Scott > > ________________________________ > This message is for the addressee's use only. It may contain confidential > information. If you receive this message in error, please delete it and > notify the sender. Tripp Lite disclaims all warranties and liabilities, and > assumes no responsibility for viruses which may infect an email sent to you > from Tripp Lite and which damage your electronic systems or information. It > is your responsibility to maintain virus detection systems to prevent damage > to your electronic systems and information. > > > _______________________________________________ > Nut-upsuser mailing list > [email protected] > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser _______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
