David, Thank you. I created a Github issue (https://github.com/networkupstools/nut/issues/808). I don't know who monitors those tickets, but no one has responded to my previous issue on that project repository about the AVRX550U, so it's unclear if the right person is going to see this one. Can you tell me what other models use the 3024 protocol? Listing those may help provide motivation. -----Original Message----- From: David Zomaya <David_Zomaya at tripplite.com> Sent: Friday, July 24, 2020 12:58 AM To: nut-upsuser at alioth-lists.debian.net; objecttothis at gmail.com Subject: Re: [EXTERNAL] OMNIVSX1000D Compatibility Oh, I did not mean to imply you won't end up getting a protocol doc (or vice versa). I just expect you'll get some response from support soon. Generally, I agree with the idea both sides can benefit from Network UPS Tools working even better with Tripp Lite products. I'm just not quite sure what is the best way to achieve that. e.g. what the NUT developers need, any open source gotchas, right channel to engage with the developers (I have that dev mailing list thread going, maybe I need to move to GitHub?), etc. Anyone reading who can help with that, feel free to reach out. From: objecttothis <objecttothis at gmail.com> Sent: Thursday, July 23, 2020 3:28 PM To: David Zomaya; nut-upsuser at alioth-lists.debian.net Subject: [EXTERNAL] OMNIVSX1000D Compatibility This is an EXTERNAL email. Please take a moment and think before clicking any links or opening any attachments from this email. If suspicious, please forward to ishelpdesk at tripplite.com for review. ______________________________________________________________________ Thank you David. I think the end goal of making this UPS compatible with NUT helps both Tripp-Lite and NUT users in that greater compatibility insures more users purchase Tripp-Lite products. I do understand Tripp-Lite wanting to do their due diligence to protect IP, however, it seems like unless NUT devs can get a hold of some sort of documentation, it's more difficult to make this and similar models compatible. Is the reason that 2012 and other protocol documentation is released and not 3024 because 3024 is a current protocol and others are not? I'm not familiar enough with the code base to know all of what's needed, but perhaps Tripp-lite can avoid the situation altogether by publishing API interface documentation without publishing inner-workings of the protocol. -----Original Message----- From: David Zomaya <David_Zomaya at tripplite.com> Sent: Friday, July 24, 2020 12:19 AM To: nut-upsuser at alioth-lists.debian.net; objecttothis at gmail.com Subject: Re: [EXTERNAL] AVRX750/500 issues>>> I also have a Tripp Lite OMNIVSX1000D with SN 2904AVLOM87E400114. That model is not on NUT compatibility list and I have an open ticket (#00681437) to get the relevant protocol information so that I can then submit it to NUT >>> and see about getting support added to it, but the ticket has been open since May 28 and no protocol information from Tripp Lite. Any chance you could kick the tires to see what the delay is?>>>>2904AVLOM87E400114 is protocol 3024 which would overlap with that development list request I have in. >>>>I can look into that case, feel free to nudge me if I don't follow up in a day or two. As an FYI, the few issues I link out to in the post below include the general workaround we've seen for 3024 and the usbhid-ups driver. Update on the above: I chatted with support about case 00681437, I expect you'll hear back later today or tomorrow if you have not already. I think one of the issues we ran into before is the protocol documents are not open source per se and have a disclaimer about not disclosing without written consent. I think Charles and I corresponded about something to that effect. ________________________________ 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. ________________________________ 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.
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 On Fri, Jul 24, 2020, at 01:34, objecttothis wrote:> David, > Thank you. I created a Github issue (https://github.com/networkupstools/nut/issues/808). I don't know who monitors those tickets, but no one has responded to my previous issue on that project repository about the AVRX550U, so it's unclear if the right person is going to see this one. Can you tell me what other models use the 3024 protocol? Listing those may help provide motivation. > > -----Original Message----- > From: David Zomaya <David_Zomaya at tripplite.com> > Sent: Friday, July 24, 2020 12:58 AM > To: nut-upsuser at alioth-lists.debian.net; objecttothis at gmail.com > Subject: Re: [EXTERNAL] OMNIVSX1000D Compatibility > > Oh, I did not mean to imply you won't end up getting a protocol doc (or vice versa). I just expect you'll get some response from support soon. > > Generally, I agree with the idea both sides can benefit from Network UPS Tools working even better with Tripp Lite products. > > I'm just not quite sure what is the best way to achieve that. e.g. what the NUT developers need, any open source gotchas, right channel to engage with the developers (I have that dev mailing list thread going, maybe I need to move to GitHub?), etc. Anyone reading who can help with that, feel free to reach out. > > > > > > > > > From: objecttothis <objecttothis at gmail.com> > Sent: Thursday, July 23, 2020 3:28 PM > To: David Zomaya; nut-upsuser at alioth-lists.debian.net > Subject: [EXTERNAL] OMNIVSX1000D Compatibility > > This is an EXTERNAL email. Please take a moment and think before clicking any links or opening any attachments from this email. If suspicious, please forward to ishelpdesk at tripplite.com for review. > > ______________________________________________________________________ > Thank you David. I think the end goal of making this UPS compatible with NUT helps both Tripp-Lite and NUT users in that greater compatibility insures more users purchase Tripp-Lite products. I do understand Tripp-Lite wanting to do their due diligence to protect IP, however, it seems like unless NUT devs can get a hold of some sort of documentation, it's more difficult to make this and similar models compatible. > > Is the reason that 2012 and other protocol documentation is released and not 3024 because 3024 is a current protocol and others are not? I'm not familiar enough with the code base to know all of what's needed, but perhaps Tripp-lite can avoid the situation altogether by publishing API interface documentation without publishing inner-workings of the protocol. > > -----Original Message----- > From: David Zomaya <David_Zomaya at tripplite.com> > Sent: Friday, July 24, 2020 12:19 AM > To: nut-upsuser at alioth-lists.debian.net; objecttothis at gmail.com > Subject: Re: [EXTERNAL] AVRX750/500 issues > > >>> I also have a Tripp Lite OMNIVSX1000D with SN 2904AVLOM87E400114. That model is not on NUT compatibility list and I have an open ticket (#00681437) to get the relevant protocol information so that I can then submit it to NUT >>> and see about getting support added to it, but the ticket has been open since May 28 and no protocol information from Tripp Lite. Any chance you could kick the tires to see what the delay is? > >>>>2904AVLOM87E400114 is protocol 3024 which would overlap with that development list request I have in. > >>>>I can look into that case, feel free to nudge me if I don't follow up in a day or two. As an FYI, the few issues I link out to in the post below include the general workaround we've seen for 3024 and the usbhid-ups driver. > > Update on the above: I chatted with support about case 00681437, I expect you'll hear back later today or tomorrow if you have not already. > I think one of the issues we ran into before is the protocol documents are not open source per se and have a disclaimer about not disclosing without written consent. I think Charles and I corresponded about something to that effect. > > > > > ________________________________ > 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. > > > ________________________________ > 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 > Nut-upsuser at alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
David Zomaya
2020-Jul-26 18:59 UTC
[Nut-upsuser] [EXTERNAL] Re: OMNIVSX1000D Compatibility
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.com at alioth-lists.debian.net> on behalf of Scott Colby <scott at scolby.com> Sent: Saturday, July 25, 2020 4:11 PM To: nut-upsuser at alioth-lists.debian.net 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.