search for: su2200rtxlcd2u

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

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 t...

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

...all epel-release --enablerepo=extras yum install nut And when I run it by: sbin/upsdrvctl start (that's where it installed it using the package) I had the following message: "This TrippLite device (09ae:1330) is not (or perhaps not yet) supported by usbhid-ups. [...]" but my device (SU2200RTXLCD2U) is supported, as clearly state here <http://networkupstools.org/stable-hcl.html>. Then I thought I needed the last src code (2.7.4), hence I built it for my machine, but when I run it by: /usr/local/ups/sbin/upsdrvctl start I had, in order, this message "writepid: fopen /var/state/ups...

On 06/24/2017 04:52 AM, Charles Lepple wrote: > On Jun 23, 2017, at 5:50 PM, Ambrogio Coletti <ambrojohn at gmail.com> wrote: >> "This TrippLite device (09ae:1330) is not (or perhaps not yet) supported by usbhid-ups. [...]" >> but my device (SU2200RTXLCD2U) is supported, as clearly state here. > No, the HCL also mentions "protocol 4001". For Tripp-Lite, a USB PID other than 0001 is generally the protocol number. So your SU2200* model is different. > > https://github.com/networkupstools/nut/issues/64 > >> Then I thought I n...

On Jun 23, 2017, at 5:50 PM, Ambrogio Coletti <ambrojohn at gmail.com> wrote: > > "This TrippLite device (09ae:1330) is not (or perhaps not yet) supported by usbhid-ups. [...]" > but my device (SU2200RTXLCD2U) is supported, as clearly state here. No, the HCL also mentions "protocol 4001". For Tripp-Lite, a USB PID other than 0001 is generally the protocol number. So your SU2200* model is different. https://github.com/networkupstools/nut/issues/64 > Then I thought I needed the last src co...

...; On 06/24/2017 04:52 AM, Charles Lepple wrote: > > On Jun 23, 2017, at 5:50 PM, Ambrogio Coletti <ambrojohn at gmail.com> > wrote: > >> "This TrippLite device (09ae:1330) is not (or perhaps not yet) > supported by usbhid-ups. [...]" > >> but my device (SU2200RTXLCD2U) is supported, as clearly state here. > > No, the HCL also mentions "protocol 4001". For Tripp-Lite, a USB PID > other than 0001 is generally the protocol number. So your SU2200* model is > different. > > > > https://github.com/networkupstools/nut/issues/64 > &g...

...2 AM, Charles Lepple wrote: >> > On Jun 23, 2017, at 5:50 PM, Ambrogio Coletti <ambrojohn at gmail.com> >> wrote: >> >> "This TrippLite device (09ae:1330) is not (or perhaps not yet) >> supported by usbhid-ups. [...]" >> >> but my device (SU2200RTXLCD2U) is supported, as clearly state here. >> > No, the HCL also mentions "protocol 4001". For Tripp-Lite, a USB PID >> other than 0001 is generally the protocol number. So your SU2200* model is >> different. >> > >> > https://github.com/networkupstools/n...