On Mar 8, 2015, at 1:27 AM, Eric Cobb <[email protected]> wrote:
> On March 6, 2015, at 6:17pm, Charles Leppe ,[email protected]> wrote: > > >> If this is the same protocol 3005 that we saw in mid-2014 (USB ID: >> 09AE:0001), then support will be part of the upcoming NUT 2.7.3 release. >> >> You wouldn't happen to know anyone who would be able to publish the specs of >> that protocol, would you? ;-) That would help remove the "experimental >> driver" warning. > > There are a few questions I have since I do have somewhat of time-sensitive > request to get this working: > > What specifics are required from the protocol in order to establish > communication? > If the protocol can be provided, how soon can it be made available to test > with CentOS? > Is the protocol all that is required to get this unit to communicate with the > current version of NUT for CentOS? Actually, I think we are a bit further along than that. The details are a bit of a distraction for your current request, but in short, we got the development version of NUT (Git, after July 2014) to talk to a SMART500RT1U (Protocol 3005) with the tripplite_usb driver. We just haven't done all the usual polishing for a 2.7.3 release. Since we do continuous integration of the build process (just not hardware testing), we have snapshot *.tar.gz files that should be representative of the upcoming release. The protocol specification for 3005 would be more of a confirmation of what some of the observed values actually mean. I haven't really used RedHat products regularly since before they started the Fedora project, but from what I understand, it should still be possible to grab the SRPM for NUT, extract it to /usr/src, change the version number to 2.7.whatever, rebuild the binary RPMs, and reinstall. > From: Charles Lepple [mailto:[email protected]] > Sent: Friday, March 06, 2015 6:17 PM > To: Eric Cobb > Cc: [email protected] > Subject: Re: [Nut-upsuser] Problems communicating with Tripp Lite > SMART500RT1U via USB with CentOS 6.6 and NUT 2.6.5 > > On Mar 6, 2015, at 12:51 PM, Eric Cobb <[email protected]> wrote: > > > Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.6.5) > Warning: This is an experimental driver. > Some features may not function correctly. > > Detected a UPS: Tripp Lite /TRIPP LITE SMART500RT1U > Unknown input voltage range: 0x02 > Unknown number of switchable load banks: 0x01 > Unit ID: 65535 > Unknown protocol (3005) > > If this is the same protocol 3005 that we saw in mid-2014 (USB ID: > 09AE:0001), then support will be part of the upcoming NUT 2.7.3 release. > > You wouldn't happen to know anyone who would be able to publish the specs of > that protocol, would you? ;-) That would help remove the "experimental > driver" warning. > > -- > Charles Lepple > clepple@gmail > > > > 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. -- Charles Lepple clepple@gmail
_______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
