Thank you for your answer. I will try to investigate the possibility that the Tripplite serial cable has a different pinout than a standard RS-232 serial cable. I wouldn't use the NUT at this point because I don't think I will be able to write a software update to adapt the NUT to my needs. My idea was first to test the protocol via a serial terminal client directly connected to the UPS, and then write some simple code from scratch to implement the protocol and use it for my basic needs. Do you think that is a feasible approach? Ambrogio On Mon, Jul 3, 2017 at 10:17 AM Larry Fahnoe <fahnoe at fahnoetech.com> wrote:> I don't have the Tripp-Lite model that you have, however the NUT HCL > http://networkupstools.org/stable-hcl.html suggests that the SU2200RTXLCD2U > ought to work via USB. Tripp-Lite sometimes uses proprietary serial > cables, so you may need to hunt down a pinout for the serial cable this > unit requires. If you need to use a serial connection, I'd start by > looking at how their PowerAlert software connects to the UPS and then go > from there to see if you can provide a similar connection to your NUT > master. > > --Larry > > On Mon, Jul 3, 2017 at 10:38 AM, Ambrogio Coletti <ambrojohn at gmail.com> > wrote: > >> Hello >> >> I asked Tripplite the serial protocol implemented in the UPS model >> SU2200RTXLCD2U. >> >> The protocol is the 4006, which is not supported by the NUT. >> >> I connected my UPS unit to a serial terminal client (both from a Windows >> machine and a Linux machine), set the communication parameters to those >> indicated in the protocol spec, and tried to open the communication, >> unfortunately with no success. >> >> I couldn't get much support from Tripplite. They couldn't even tell me if >> I should expect to be able to connect that way an see any type of "welcome >> message" as the device communication is open. >> >> So I am asking you guys, do you know if I am supposed to be able to open >> a straight serial connection with the UPS as described above, using a >> normal serial terminal cliente (e.g. Putty)? >> >> Regards >> Ambrogio >> >> _______________________________________________ >> Nut-upsuser mailing list >> Nut-upsuser at lists.alioth.debian.org >> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser >> > > > > -- > Larry Fahnoe, Fahnoe Technology Consulting, fahnoe at FahnoeTech.com > Minneapolis, Minnesota www.FahnoeTech.com >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170703/d5d6d05a/attachment.html>
> > My idea was first to test the protocol via a serial terminal client > directly connected to the UPS, and then write some simple code from scratch > to implement the protocol and use it for my basic needs.That sounds like a lot of work to me, particularly when NUT is already a well thought out and highly flexible tool to manage UPS connected systems. I'd suggest reading the NUT documentation and then trying to use the USB interface with your UPS. --Larry On Mon, Jul 3, 2017 at 11:48 AM, Ambrogio Coletti <ambrojohn at gmail.com> wrote:> Thank you for your answer. > I will try to investigate the possibility that the Tripplite serial cable > has a different pinout than a standard RS-232 serial cable. > > I wouldn't use the NUT at this point because I don't think I will be able > to write a software update to adapt the NUT to my needs. > > My idea was first to test the protocol via a serial terminal client > directly connected to the UPS, and then write some simple code from scratch > to implement the protocol and use it for my basic needs. > > Do you think that is a feasible approach? > > Ambrogio > > On Mon, Jul 3, 2017 at 10:17 AM Larry Fahnoe <fahnoe at fahnoetech.com> > wrote: > >> I don't have the Tripp-Lite model that you have, however the NUT HCL >> http://networkupstools.org/stable-hcl.html suggests that the SU2200RTXLCD2U >> ought to work via USB. Tripp-Lite sometimes uses proprietary serial >> cables, so you may need to hunt down a pinout for the serial cable this >> unit requires. If you need to use a serial connection, I'd start by >> looking at how their PowerAlert software connects to the UPS and then go >> from there to see if you can provide a similar connection to your NUT >> master. >> >> --Larry >> >> On Mon, Jul 3, 2017 at 10:38 AM, Ambrogio Coletti <ambrojohn at gmail.com> >> wrote: >> >>> Hello >>> >>> I asked Tripplite the serial protocol implemented in the UPS model >>> SU2200RTXLCD2U. >>> >>> The protocol is the 4006, which is not supported by the NUT. >>> >>> I connected my UPS unit to a serial terminal client (both from a Windows >>> machine and a Linux machine), set the communication parameters to those >>> indicated in the protocol spec, and tried to open the communication, >>> unfortunately with no success. >>> >>> I couldn't get much support from Tripplite. They couldn't even tell me >>> if I should expect to be able to connect that way an see any type of >>> "welcome message" as the device communication is open. >>> >>> So I am asking you guys, do you know if I am supposed to be able to open >>> a straight serial connection with the UPS as described above, using a >>> normal serial terminal cliente (e.g. Putty)? >>> >>> Regards >>> Ambrogio >>> >>> _______________________________________________ >>> Nut-upsuser mailing list >>> Nut-upsuser at lists.alioth.debian.org >>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser >>> >> >> >> >> -- >> Larry Fahnoe, Fahnoe Technology Consulting, fahnoe at FahnoeTech.com >> Minneapolis, Minnesota www.FahnoeTech.com >> >-- Larry Fahnoe, Fahnoe Technology Consulting, fahnoe at FahnoeTech.com Minneapolis, Minnesota www.FahnoeTech.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170703/7a6139a8/attachment-0001.html>
On Jul 3, 2017, at 12:48 PM, Ambrogio Coletti wrote:> > I wouldn't use the NUT at this point because I don't think I will be able to write a software update to adapt the NUT to my needs. > > My idea was first to test the protocol via a serial terminal client directly connected to the UPS, and then write some simple code from scratch to implement the protocol and use it for my basic needs. >Ambrogio, If you are considering writing serial code from scratch, I don't think it is that much more complicated to modify the existing NUT drivers (if that is even needed). In general, protocol revisions from Tripp Lite have not been very different from the previous versions. First, which OS and distribution are you using? Rudimentary support for the 4006 protocol over USB has been in the usbhid-ups driver since NUT 2.6.0, but since that information was apparently added from another project, we don't have an entry in the HCL for that protocol. So I would try the USB connection first. Bear in mind that some UPS firmware cannot switch between USB and serial without first powering down completely (including disconnecting AC). We don't have good data on which UPSes require this low-level reset, but it is something to try. I have an older Tripp-Lite UPS that uses a different driver, so when I run "lsusb -d 09ae:", I see the following: $ lsusb -d 09ae: Bus 006 Device 002: ID 09ae:0001 Tripp Lite Yours will probably say "09ae:4006" instead. A note: drivers/tripplite_usb.c was written for older models which seem to have a rudimentary USB-to-serial converter built in. Some of the commands and responses match those in drivers/tripplite.c (which talks to a serial port). It would be interesting to see where your UPS fails during detection with the drivers/tripplite.c code. I seem to remember it does not have much in the way of debugging (but strace should work). You mentioned "set the communication parameters to those indicated in the protocol spec" - is this published somewhere? Larry, Thanks for the kind words! - Charles
Hi Larry and thanks for your answer. I will have a look. Tripplite will send you the pdf of the protocol if you communicate them the UPS serial number. Ambrogio On Mon, Jul 3, 2017 at 2:16 PM Charles Lepple <clepple at gmail.com> wrote:> On Jul 3, 2017, at 12:48 PM, Ambrogio Coletti wrote: > > > > I wouldn't use the NUT at this point because I don't think I will be > able to write a software update to adapt the NUT to my needs. > > > > My idea was first to test the protocol via a serial terminal client > directly connected to the UPS, and then write some simple code from scratch > to implement the protocol and use it for my basic needs. > > > > Ambrogio, > > If you are considering writing serial code from scratch, I don't think it > is that much more complicated to modify the existing NUT drivers (if that > is even needed). In general, protocol revisions from Tripp Lite have not > been very different from the previous versions. > > First, which OS and distribution are you using? > > Rudimentary support for the 4006 protocol over USB has been in the > usbhid-ups driver since NUT 2.6.0, but since that information was > apparently added from another project, we don't have an entry in the HCL > for that protocol. So I would try the USB connection first. > > Bear in mind that some UPS firmware cannot switch between USB and serial > without first powering down completely (including disconnecting AC). We > don't have good data on which UPSes require this low-level reset, but it is > something to try. > > I have an older Tripp-Lite UPS that uses a different driver, so when I run > "lsusb -d 09ae:", I see the following: > > $ lsusb -d 09ae: > Bus 006 Device 002: ID 09ae:0001 Tripp Lite > > Yours will probably say "09ae:4006" instead. > > A note: drivers/tripplite_usb.c was written for older models which seem to > have a rudimentary USB-to-serial converter built in. Some of the commands > and responses match those in drivers/tripplite.c (which talks to a serial > port). It would be interesting to see where your UPS fails during detection > with the drivers/tripplite.c code. I seem to remember it does not have much > in the way of debugging (but strace should work). > > You mentioned "set the communication parameters to those indicated in the > protocol spec" - is this published somewhere? > > Larry, > Thanks for the kind words! > > - Charles > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170703/cb04f975/attachment.html>