similar to: debian etch and the Tripplite SU1000RTXL2U

Displaying 20 results from an estimated 5000 matches similar to: "debian etch and the Tripplite SU1000RTXL2U"

2016 Oct 20
2
TrippLite SU3000XLCD
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. 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
2006 May 18
1
Tripplite SU2200XL
Can anyone help getting a Tripplite SU2200XL to work with nut 2.0.3 using the supplied serial cable? Starting the ups service yields: Starting tripplitesu: Network UPS Tools - Tripp Lite SmartOnline driver 0.02 (2.0.3) Unable to detect Tripp Lite SmartOnline UPS on port /dev/ttyS0 I also have Tripplite's PowerAlert 12 software installed and when run it finds the UPS without a problem. So
2007 Jan 04
1
Tripp Lite Smart Pro UPS
I have several Tripplite SU2200RMXL2U and SU3000RM2U units that I would like to monitor using Nut. I have tried to attach to the units using a serial cable with the tripplite and tripplitesu drivers with no success. The drivers simply seem to not recognize the UPS. I then tried using the tripplite_usb driver with the usb cable. It definitely sees the UPS but I am getting errors which told me
2009 Mar 06
2
Question about Tripplite SU10KRT3U
Hello list! I can't seem to get this running via RS232 monitoring; I've been told that NUT won't support serial connections, and find this hard to verify. Does anyone else have this running on the SU10KRT3U via RS232? If so, what driver did you use? I'm getting no satisfaction from the "tripplite" driver; upon upsdrvctl start, I get "Failed to find UPS - giving
2009 Nov 04
1
New to nut project
I have tried to support a TrippLite Internet350SER UPS using a serial cable (The only connection on this model) using the 2.4 code branch. It uses the Protocol 1004 from the tripplite specification that can be use either used on serial or USB device. Since my device was only serial, I worked only on the serial integration. Since I found nothing in tripplite.c, tripplite-hid.c, tripplitesu.c to
2016 Oct 21
0
TrippLite SU3000XLCD
[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
2009 Nov 09
2
[PATCH] New to nut project
---------- Forwarded Message ---------- Subject: [PATCH] New to nut project Date: Friday, 6. November 2009 From: Patrick Levesque <patrickl at verint.com> To: Thomas Jarosch <thomas.jarosch at intra2net.com> As requested, here is my patch file including all my modification to the 2.4.1 tarball from the web site. On Friday 06 November 2009 05:41:29 you wrote: > Hello Patrick,
2005 Sep 15
2
Driver for Tripp Lite SmartPro SLT
I have a new SMART1050SLT Tripp Lite UPS that both tripplite and tripplitesu drivers hate. Both simply time out with a "can't find" message. Does anyone know about the SmartPro series?
2005 Dec 19
1
tripplitesu driver fix
The 2.0.2+ tripplitesu drivers do not recognize SmartOnLine SU2200XL and possibly other SmartOnLine UPSes. Here is a one-line fix. Lee --- ../nut-2.0.2/drivers/tripplitesu.c Thu Jan 27 08:33:21 2005 +++ drivers/tripplitesu.c Sat Oct 1 13:38:51 2005 @@ -227,7 +227,7 @@ buffer[4] = '\0'; if (!strcmp(buffer, "~00D")) { - if (ser_get_buf_len(upsfd, buffer, 4, 3, 0) <=
2009 Sep 20
2
TrippLite Eco Series UPS
I purchased a TrippLite ECO550UPS from Amazon a few days ago thinking I was going to use it for my Windows Media Center HTPC. I've since changed my mind and decided to use Mythbuntu but it I can't get my UPS working with nut. I've tried all of the tripplite drivers and the usbhid-ups driver. The tripplite_usb and usbhid_ups output is listed below. The tripplite and tripplitesu drivers
2007 May 20
1
Sweex 1000VA UPS (was: powermust usb)
--- Arjen de Korte <nut+users at de-korte.org> wrote: > > > I also did: > > > > # ./megatec_usb -DDDDD -x vendor=06da -x mfr=OMRON > > /dev/usb/hiddev0 > > Please have a look at 'man 8 megatec_usb' again. > > You probably need to specify the '-x vendorid' and > '-x productid' options > and most likely, the
2007 May 20
1
Sweex 1000VA UPS (was: powermust usb)
--- Arjen de Korte <nut+users at de-korte.org> wrote: > > > I also did: > > > > # ./megatec_usb -DDDDD -x vendor=06da -x mfr=OMRON > > /dev/usb/hiddev0 > > Please have a look at 'man 8 megatec_usb' again. > > You probably need to specify the '-x vendorid' and > '-x productid' options > and most likely, the
2023 Sep 16
1
Nut-upsdev Digest, Vol 206, Issue 5
It seems the `libmodbus` library or headers were not found, or something similar - so the driver against it was not built. Did you install `libmodbus-dev` before the build? What does `config.log` in the build root say (and.or the summary shown after you run the `configure` script)? On Sat, Sep 16, 2023 at 7:46?PM FatGear <fatgear1 at free.fr> wrote: > Hi, > > I don't know what
2023 Sep 19
1
Nut-upsdev Digest, Vol 206, Issue 5
Hello there, I don't think that's working,? I have done all your repo but i don't know how it's supposed to work. I have a idea, change vendor id and product id? to make the driver try to connect to the ups, what do you think of that ? With this driver maybe : usbhid-ups FatGear Le 16/09/2023 ? 20:40, Jim Klimov a ?crit?: > It seems the `libmodbus` library or headers were
2007 Sep 21
2
TrippLite 1500XL problems, continued.
So a month or more ago, I posted about continual disconnect messages from this UPS (roughly 2/hour), using nut 2.2.0 on debian etch. Now, I've finally gotten around to running tripplite_usb in debug mode, and these are the results: ... send_cmd(msg_len=2, type='L') send_cmd(msg_len=2, type='S') send_cmd(msg_len=2, type='B') send_cmd(msg_len=2, type='L')
2007 Aug 10
1
TrippLite OMNIVS1500XL Segmentation Fault
I am running Debian Etch, with the nut 2.0.4 packages, and I get a segmentation fault from tripplite_usb. # /lib/nut/tripplite_usb -u root -DDDDD auto Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.6 (2.0.4) Warning: This is an experimental driver. Some features may not function correctly. debug level is '5' Checking device (09AE/0001) (002/004) - VendorID: 09ae -
2007 Nov 20
2
Mustek Powermust 600VA
Hi, I'm having a hard time configuring a Mustek Powermust 600VA ups to work via USB with nut. I read somewhere that nut works OK via the rs232 cable, but unfortunately I don't have a COM port in my computer. The kernel detects the ups as an Xbox pad :) and loads the xpad module. I tried running /lib/nut/megatec with different /dev/ttySx but it displays megatec protocol UPS was not
2007 Dec 30
1
Constant "on battery" and "on line power" status changes
Good afternoon all, I have a Tripp-Lite SmartOnline SU1500RTXL2ua UPS that I had previously tried to get up and running with NUT earlier this year. Peter Selinger had been working with this, but he had to devote time to more important things, and I did too, so it got pushed to the back burner. I saw in the release announcement of 2.2 that the UPS is now supported and decided I would try once
2016 Dec 09
1
Windows usbhid-ups driver
I'm having trouble with the usbhid-ups driver and Windows. NUT won't connect to an APC SmartUPS 3000 via USB. I've had good success with NUT and Raspbian as well as NUT and Windows using the tripplitesu driver. The current system is: Windows 7 Enterprise 64 bit NUT 2.6.5-6 installed from MSI installer downloaded from networkupstools.org libusb-win32-bin-1.2.6.0 installed and
2005 Nov 08
1
adding libusb CFLAGS to generic-hid.c rule
Peter, attached is a proposed patch to fix compilation of generic-hid.c when libusb's usb.h is not in /usr/include (but the -I flag is provided by "libusb-config --cflags"). It fixes the build under OS X, where Fink installs libusb with --prefix=/sw. I changed "usb.h" to <usb.h> so that 'make depend' wouldn't generate a dependency on 'usb.h' with