similar to: Proposed apcsmart driver patch

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

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 there, I am using an old (really old) APC Smart-UPS 600. It worked fine under apcupsd but when I tried NUT it did not work. The error I was getting was: sudo /lib/nut/apcsmart -DDD /dev/ttyS1 Network UPS Tools (version 2.0.4) - APC Smart protocol driver Driver version 1.99.8, command table version 2.0 debug level is '3' Attempting firmware lookup Firmware: [D4] Not found in

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 -

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.

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

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

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

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

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

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

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

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

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

2011/2/15 Lupe Christoph > On Monday, 2011-02-14 at 21:54:20 -0000, Arnaud Quette wrote: > > I definitely need more info! > > please reply to ALL: > > > - what is the exact model and date of manufacturing? > > SmartUPS 300I NET. I have the serial number (GS9809283199) but no date. > it seems to be a recent model. > - are you sure this unit is ok? > >

2011/2/15 Lupe Christoph > On Monday, 2011-02-14 at 21:54:20 -0000, Arnaud Quette wrote: > > I definitely need more info! > > please reply to ALL: > > > - what is the exact model and date of manufacturing? > > SmartUPS 300I NET. I have the serial number (GS9809283199) but no date. > it seems to be a recent model. > - are you sure this unit is ok? > >

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:

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

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