[please use reply-all to include the list - the headers are not mangled] On Oct 20, 2016, at 3:22 PM, Fairfax, Charles A. wrote: > > I’m having trouble with a TrippLite SU3000XLCD. I’m using a Raspberry Pi > running Raspbian (wheezy) with NUT 2.6.4. > > I can monitor my older TrippLite UPSs, mostly SU1000RT2Us, with this Pi and a > USB to serial adapter.
Interesting, we don't have that model number listed in our compatibility list[*]. Do they mostly use tripplitesu or tripplite? [*] http://networkupstools.org/stable-hcl.html?manufacturer=Tripp%20Lite > My first thought with the SU3000XLCD was to use the USB port instead of the > serial port as that’s the “modern” thing to do. When I plugged the USB cable > in to the UPS it turned off, dropping the load. The load is process control > instrumentation which, while not damaged, presented some challenges to > restart. So now I’m leery of using the USB port. > > With a long history of success monitoring UPSs via serial communication > that’s where I am now. Unfortunately NUT doesn’t see the UPS. > > My query is two part: > 1) Is there a reasonable explanation for why plugging my Pi into the > UPSs USB port caused it to turn off? Is there a proper way to connect it > that will avoid this? If so my problem is likely solved if the usbhid-ups > driver will talk to my SU3000XLCD. If I can’t assure my employers that I > won’t kill the process again USB may not be a viable option. To be honest, I would have expected the RPi to reboot when inserting the USB cable. Was the Pi plugged into a computer or a standalone USB adapter? I wonder if there was a difference in ground potential between the Pi and the UPS. The entry on the HCL for the SU3000XLCD came from NUT USB testing that Tripp Lite performed in their lab: http://article.gmane.org/gmane.comp.monitoring.nut.user/8173 . For that reason, I would think it would be reasonable to bother Tripp Lite about this issue, especially if it crops up again. > 2) Connecting to the serial port has not (yet) shut down the UPS. This > is a good start but it would be better if communication happened. Should I > be able to communicate via serial port with this SU3000XLCD with one of these > drivers? Is there another driver that’s known to work with this UPS or can > this one be “tweaked” to work? Can it be as simple as a baud rate mismatch? > I’m not having much luck querying the serial port’s settings. Although the old "tripplite_usb" driver seems to be talking to a USB-to-serial chip with a very similar protocol to the "tripplite" driver, I don't think we ever got anywhere on trying to combine the two. Also, since the SU3000XLCD is listed as compatible with the usbhid-ups driver rather than tripplite_usb, I don't know if we can draw any conclusions from the older driver. Do you have access to a spare SU3000XLCD? We could try patching the tripplite serial driver to send a protocol query, and work from there. However, I wouldn't want to experiment on the production system. Another thing to note: some UPSes don't like switching between the USB and serial ports after they have powered up. I don't remember if we ever confirmed if this affects Tripp Lite hardware, but it is something to be aware of. _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
