similar to: Old APC SmartUPS 1250, Nut 2.2.2 Fedora 9

Hello, I can get nut to work with this UPS using the apcsmart driver, but only with limited functionality. It is only reporting the OL/OB status and that's about it. None of the other useful variables such as run time, load etc are reported and initiating battery tests does not work either. Has anyone managed to get nut to report more than these variables with a Matrix type UPS? I see

2009/5/3 Thomas Juerges > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Arnaud, > Hi Thomas, > I just checked the 2.4.1 version of nut and found that you forgot to add > my old UPS model (APC Smart-UPS 900). I guess it is because you were > busy at the time when I sent you the patch. So here it goes again. :) > uh, right sorry. I was pretty sure I applied

Hello One our customer has two Linux HP-branded servers powered from "clasic" APC Smart-UPS 2200 RM 2U (p/n SUA2200RMI2U). It is connected to first server via RS232c port with APC-branded cable. We have installed NUT 2.6.4 with apcsmart driver. This setup works fine for months. Two weeks ago all the hardware powered from the UPS started to switch off occasionally while on line

I need direction. I don't know what to google for anymore. I am unable to get my SmartUPS 2200XL to be recognized. My suspicions are that it's UDEV or Kernel related. I've updated the kernel to the highest version I feel comfortable with due to other things that run on the server, and I've updated UDEV a bit too. When I plug in the USB cable from the UPS into the server, I

I have a SmartUPS 750 (SUA750) which has the temperature and humidity SmartSlot card installed. When NUT 2.2 communicates with this UPS over /dev/ttyS0 using apcsmart, using the APC Smart cable connected to the SUA750 serial port, and this ups.conf: [su700] driver=apcsmart port = /dev/ttyS0 I can see the ambient temperature and humidity data with "upsc su700 at

G'day y'all, Here's a tiny patch set for drivers/apcsmart.c and drivers/apcsmart.h. Adds APC SmartUPS 1250 ("8QD" case) + 940-0024C recognition to apcsmart. (Unpatched apcsmart.c v1.99.8 misidentifies the SmartUPS 1250 as a "dumb" UPS.) For NUT 2.0.5+. NUT 2.0.5: Patches apply successfully. Builds successfully. Works as expected under Ubuntu 7.04. NUT 2.2:

Sorry for a bit longer delay than I anticipated, I was stuffed with the work. This is the next iteration of the patch adding some functionality to apcsmart driver, and relying on 'ignorelb' recently added. Follow up from previous thread: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02331.html Main differences is that V3 is split into many small patches, so the

Hey guys, I built my own 940-0024C cable as described here: http://www.networkupstools.org/cables/940-0024C.jpg My problem is that I can't receive anything. Sending (e.g. through minicom or my own application) works fine. Nut itself is not able to detect My UPS or anything else. <snip> [myups] driver = apcsmart port = /dev/ttyS0 cable = 940?0024C # also tested without cable option

We recently had to replace an old APC SmartUPS 3000 with a newer 3000VA (the 2U one). It has both serial and USB in the back (with an RJ-45 on the end of the serial cable). I can't get the apcsmart driver to connect. I figured it should work the exact same as the old UPS, with /dev/ttyS0 as the port (I'm using the same port on the server that the last one was plugged into). I even

This patch introduces a handful of new options, I mentioned earlier in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02088.html See the large commit message in the follow-up for the details and rationale. I realize it's a bit larger diff - so if it's required I can split it into few smaller ones. Michal Soltys (1): APC smart driver update and new features.

This is 2nd version of the earlier patch featuring a few new features and fixes to the apcsmart driver, following the remarks in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02294.html Major changes from v1: - handle battery.charge and battery.runtime checks at main.c level - handle "immutable but writable" conflict gracefully at driver level -

Hello. Trouble to communicate with APC SmartUPS via serial port. UPS connected to the com1 port on windows host. Communication witch hyperterm works well. There is a log: YSM ^ASmart-UPS SC1000 n5S0713T63247 m03/29/07 L240.0 B27.10 apcupsd also can communicate with the UPS and works well. running apcsmart -a ups gives the following: com1: device reports different attributes than what were set

I have a new APC Smart-UPS SUA2200RM2U. I've had no success with the manufacturer's PowerChute software and smart signaling, so I have decided to try NUT. The smartups driver can't make contact through the serial port. Since this is rack-mounted, it comes with a 940-1524 serial cable. As far as I can tell, this is supposed to work with smart signaling. Here's my ups.conf:

On 2014-01-14 10:12, dstrr wrote: > Hello. > Trouble to communicate with APC SmartUPS via serial port. > UPS connected to the com1 port on windows host. > Communication witch hyperterm works well. > There is a log: > > YSM > ^ASmart-UPS SC1000 > n5S0713T63247 > m03/29/07 > L240.0 > B27.10 > > apcupsd also can communicate with the UPS and works well. >

I get the following errors constantly in my messages log: Sep 21 11:53:37 cgydc002 upsd[22659]: Connection from 127.0.0.1 Sep 21 11:53:37 cgydc002 upsd[22659]: Host 127.0.0.1 disconnected (read failure) Sep 21 11:53:37 cgydc002 upsd[22659]: Connection from 127.0.0.1 Sep 21 11:53:37 cgydc002 upsd[22659]: Host 127.0.0.1 disconnected (read failure) Sep 21 11:53:37 cgydc002 upsd[22659]: Connection

Dear Ladies and Gentlemen, I have several old, yet functioning APC Smart-UPS (Model 600LS, Part AP600I, Firmware 6JI, no EEPROM, from 1991). They are not supported by Powerchute any more. I run NUT 2.6.5-4 on Windows XP SP3. I use COM1 port with cable 940-0024C. The connection fails with APC Smart protocol driver 3.0 (2.6.3-3534:3540M), APC command table version 3.0 or higher - it works with APC

I'm trying to setup a server controlling 8 ups, 6 APC Smartups 1500 and two 1000. Because of the number of ups, i connected them using usb cables. I'm using Debian Etch AMD64 and nut 2.2.0 from testing (already tried 2.0 from stable, but had problems reading the ups serials and all the following problems of 2.2). This is my ups.conf: [ups2] driver = usbhid-ups port =

Hey Jarett, 2009/2/24 <jarett.stevens at usermail.com> > After upgrading to the 2.4.1 version, I wasn't able to read as many > variables from my UPS. After a bit of experimentation, I determined that > the firmware on my UPS was different than what is currently in the > apcsmart driver, though it had worked before. I located my firmware > version (5ZM), and added in

Hi folks, Today I installed nut on my Dell Poweredge 1800 server running Ubuntu 8.04 Server, with an APC Smart-UPS 1500 connected to it with the black APC cable. I used apt to install nut, upsd -v gives me "Network UPS Tools upsd 2.2.1-" I then copied and configured the config files. Most of the setup seems OK; I get console messages for line power fail / good, and I can do instant

Hello! I've ran into this annoying issue when setting up a new server. I have an APC SmartUPS hooked up on a USB-serial converter on /dev/ttyUSB0. This works nicely, until: hub 3-0:1.0: port 1 disabled by hub (EMI?), re-enabling... pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0 usb 3-1: pl2303 converter now attached to ttyUSB1 apcsmart gets into an infinite loop of this: