similar to: apcsmart and #311678 feature request thoughts

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.

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

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

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

Hi, The devel branch has some long standing updates implemented - mostly a result from past bug/issue reports. Among those: - selectable normal / canonical mode (useful in windows and perhaps with some problematic usb/rs cards) - some compat entries - certain (old) class of psus returning something else through 'b' treated as a whole set - can handle mutlivalue entries (e.g.

Hi, The devel branch has some long standing updates implemented - mostly a result from past bug/issue reports. Among those: - selectable normal / canonical mode (useful in windows and perhaps with some problematic usb/rs cards) - some compat entries - certain (old) class of psus returning something else through 'b' treated as a whole set - can handle mutlivalue entries (e.g.

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() ?

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 Paul, > I have another NUT client for your client-projects[1] page: MonAMI[2]. > > MonAMI aims to be a "universal sensor framework". The data gathered from > MonAMI's NUT plugin can be sent to any of the output plugins. Currently, > these include Ganglia, Nagios, KSysguard and a file-logger (amongst others). interesting though I've not had time to

Citeren Michal Soltys <msoltyspl-guest at alioth.debian.org>: > @@ -417,10 +414,12 @@ > if (flags & SER_CC) { > iset = IGN_CCCHARS; > aset = ""; > + sec = 6; usec = 0; > } > if (flags & SER_CS) { > iset = IGN_CSCHARS; > aset = ""; > + sec = 6; usec = 0; > } > > memset(buf, '\0', buflen);

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

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

Citeren Michal Soltys <msoltyspl-guest at alioth.debian.org>: > @@ -251,14 +251,14 @@ > if (do_lock_port) { > errno = 0; > ret = 0; > -#ifdef HAVE_UU_LOCK > + #ifdef HAVE_UU_LOCK > ret = uu_lock(xbasename(device_path)); > -#elif defined(HAVE_FLOCK) > + #elif defined(HAVE_FLOCK) > ret = flock(fd, LOCK_EX | LOCK_NB); > -#elif

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 -

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

Namely something like: ups.runtime - amount of seconds since powering up The reason is essentially "side effect" of this bug report: http://article.gmane.org/gmane.comp.monitoring.nut.user/7705 Where T denotes total time since ups' power up. On upses with AP9612TH it's used for dual temperature sensors (which top of apcsmart branch should gracefully support). Either way,

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

Michal, Could we make this error a warning, or make the readback configurable? - Charles On Oct 21, 2011, at 7:56 PM, <nut-bugs at alioth.debian.org> <nut-bugs at alioth.debian.org > wrote: > Bugs item #313395, was opened at 2011-10-21 16:56 by Jesse Peterson > You can respond by visiting: >

I got around to unplugging my UPS and I found it doesn't last nearly as long as estimated. Is the "upsmon[1446]: UPS desktop_ups at localhost battery is low" logged when "battery.runtime:" = "battery.runtime.low: 120"? Does any make better batteries that don't go down faster when they get old? battery.charge: 100 battery.charge.low: 10