similar to: apcsmart update info

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, We have a several AP9612TH environmental cards (they have 2 probe connectors) inserted into our APC UPS devices which monitor temperature and humidity. The apcsmart nut module knows how to query the ambient.temperature and ambient.humidity using the 't' and 'h' commands of the UPS (refer to apcsmart.h). The results of the 't' and 'h' commands are from probe 1.

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

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

Inital tests with two apc units (2005 and pre-2000) seem to go well. See commit message for details. I'll add more detailed rationale after getting some sleep :) Michal Soltys (1): apcsmart: switch processing to ICANON + minor fixes drivers/apcsmart.c | 270 +++++++++++++++++++++++++++++++++++----------------- drivers/apcsmart.h | 127 ++++++++++++++++--------- 2 files changed, 267

Before I start any commits. In patch 2/18 - http://lists.alioth.debian.org/pipermail/nut-upsdev/2011-March/005299.html Two "custom" commands slipped in: ups.firmware.old and shutdown.return.grace. In 18/18 I tried to rename them and add remainig commands for "hackish" shutdown methods, to make them easily callable through e.g. upscmd (for example for testing). Is it

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

Hi Paul, Aha - we have both found the same. I am referring to your post from: http://lists.alioth.debian.org/pipermail/nut-upsdev/2006-November/001344.html Looking at the source code the temp value is obtained by querying the following OID: #define APCC_OID_IEM_TEMP ".1.3.6.1.4.1.318.1.1.10.2.3.2.1.4.0" notice that the OID ends with .0 (index zero). Well, looking at the

Perhaps someone else could confirm this, I have an APC UPS with a built-in network management card with environmental sensor for temp/humidity. The OID index for the sensors appears to be .1 (the last component for each of the OIDs listed below). The original source code has them at .0 drivers/apccmib.h #define APCC_OID_IEM_TEMP ".1.3.6.1.4.1.318.1.1.10.2.3.2.1.4.1" #define

Hi, We have several APC Smart UPSes (serial port/apcsmart) with the APC Temp/Humidity sensor cards (AP9612TH). The sensor cards have 2 plugs for 2 separate sensors. So far, we have only used one of the sensors in conjunction with the apcsmart module from nut. This has been working great. Example output: [nut at nut]# upsc APC11 ambient.humidity: 037.2 ambient.humidity.alarm.maximum: NO,NO

Hi Michal, I've cc'ed -upsdev, since some info could be interesting for everybody. 2011/5/27 Michal Soltys <soltys at ziu.info> > On 11-05-25 09:35, Arnaud Quette wrote: > > Hi Michal, > > > > 2011/5/25 Michal Soltys <soltys at ziu.info <mailto:soltys at ziu.info>> > >(...) > > > > I'm preparing larger patchset with

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 Aug 9, 2013, at 7:18 AM, Michal Soltys wrote: > I'm still a bit reluctant to merge it without a bit wider exposure, so if anyone has a possiblity to test it with some apc units - any feedback would be most welcome. Apparently, a lot of people are using NUT via packages, so: * users might not want to build from source if things are working * the packagers might not pick up a 2.7.x

Citeren Michal Soltys <msoltyspl-guest at alioth.debian.org>: > Log: > apcsmart: allow tearing down/setting up serial connection during > normal activity; If this is needed at all (why?), I don't think this should be handled at driver level, but this would need to be in the serial.c library. Opening/closing a serial port is independent from the protocol used (no data

Hi, I started updating smart driver with a few things I've been missing. While going through the source: - in upsdrv_shutdown(), there're loads of printfs - they kinda look like a leftover from older debug times. Shouldn't they be changed into upsdebugx() or upslogx() ?

https://alioth.debian.org/tracker/?func=detail&atid=411544&aid=311678&group_id=30602 I wanted to do it somewhat more flexibly/elegantly, so this is what I've been thinking about (or rather sitting on mostly implemented piece, still needing some testing though): - any variable that may include multiple data, would be (during runtime) split into appropriate *.N.* sets; for

Hi Michal, I'm cc'ing the NUT development mailing list. you should also subscribe to it. 2010/10/28 Michal Soltys > Greetings > > I have loads of relatively old smart upses that I currently control using a > bit patched version of apcupsd - the reason for those patches is the age of > the upses - roughly 10 years old+, which are can be a bit tricky to control. > From

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

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

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: