similar to: patch for old APC Smart-UPS 600

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

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:

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 -

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

Hi, I am trying to set up NUT on a mini-ITX system running OpenBSD 5.5. I have an APC Smart-UPS SC620 which runs perfectly well on Ubuntu, with nut-2.2.1. Ubuntu system uses ASUS motherboard. On mini-ITX system, I have Intel d2500cc motherboard with 4 serial ports. I've tested ports by connecting them with a null-modem cable and running cu in 2 terminals. Type in one terminal, output shows

Hi, The patch below adds support for a pair of old (circa 1993) APC Smart-UPS 600 devices that I have. They don't support the query mechanism of newer APC devices but do respond to the full Smart-UPS command set: battery.alarm.threshold: 0 battery.charge: 100.0 battery.charge.restart: 00 battery.date: 02/22/93 battery.runtime: 2040 battery.runtime.low: 120 battery.voltage: 27.67

On May 2, 2014, at 3:26 AM, Kastus Shchuka wrote: > Hi, > > I am trying to set up NUT on a mini-ITX system running OpenBSD 5.5. > > I have an APC Smart-UPS SC620 which runs perfectly well on Ubuntu, > with nut-2.2.1. Ubuntu system uses ASUS motherboard. > > On mini-ITX system, I have Intel d2500cc motherboard with 4 serial ports. > I've tested ports by connecting

On May 3, 2014, at 5:20 AM, Charles Lepple wrote: > On May 2, 2014, at 3:26 AM, Kastus Shchuka wrote: > >> Hi, >> >> I am trying to set up NUT on a mini-ITX system running OpenBSD 5.5. >> >> I have an APC Smart-UPS SC620 which runs perfectly well on Ubuntu, >> with nut-2.2.1. Ubuntu system uses ASUS motherboard. >> >> On mini-ITX system, I

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

Arnaud, I was finally able to get back to this issue and would recommend adding these items to the FAQ #37 about recalibrating the UPS: 1a. It's important that the UPS be at 100% charge before starting the procedure; starting at lower will not work at all, not just produce inaccurate numbers. ? ? ? [I started the procedure when the UPS was at 91% charge. After that it would never report

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:

Hi All, I've got two APC SmartUPS's that behave differently with nut, I have a SmartUPS1400 & a SmartUPS1250. I'm fairly sure this isn't a nut problem but more likely a problem with the age of the SmartUPS1250 and the apcsmart driver not being able to identify it. Under the APC Powerchute software the same monitoring & command parameters are available for both

Hi all, I just got myself 2 APC Back-UPS CS 350 I downloaded the stable nut tar.gz installed it. This is not the first time i install and configure nut so i used the same configuration as on my other server as i always did. Then i made the 2 required modification. I changed these 2 thing: driver = apcsmart port = /dev/hiddev0 # ls -al /dev/hiddev0 crw------- 1 nut nut 180, 96

Listmates, After wrangling with the voltage value on the CyberPower 1000AVRLCD and now having 2 of them working, I though it would be a simple matter to move my APC BP650 from apcupsd to nut so that all 3 servers would be monitored on the same web interface. The APC is attached to an older box running openSuSE 11.0 with nut-2.2.2-66.1. (nut-classic). The APC BP650 uses a serial connection

I just installed nut, and I it is detected but I don't get any usefull information. I have the serial cable that came with it which is a 940-0024C and I tried setting that in the driver, but no difference. What can I do to get stuff like battery voltage and such? Thanks, Brian upsc ups1 at localhost driver.name: apcsmart driver.parameter.cable: 940-0024C driver.parameter.pollinterval: 2

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

As I requested here: https://bugzilla.redhat.com/show_bug.cgi?id=678793 Add support for Matrix-UPS firmware 0XM/0XI with additional commands Description of problem: The attached patch adds support for Matrix-UPS revision strings 0XI and 0XM to the apcsmart driver. The revision string itself isn't completely opaque--it is made up of different parts as documented on

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

On several occasions I have seen the apcsmart process runaway using 100% CPU while filling my syslog partition by logging the following syslog entries at an incredible rate. I have seen up to 21,800 log entries PER SECOND of the following nature: --[snip]-- Jun 25 10:06:38 servername apcsmart[4012]: Communications with UPS lost: Communications with UPS lost - check cabling Jun 25 10:06:38