similar to: apcsmart and ambient data

Hi Dmitry and the list, would you (or anyone owning such a device) be able to validate the below patch: https://alioth.debian.org/tracker/index.php?func=detail&aid=310613&group_id=30602&atid=411542 Most notably, it's about the paths changes: -#define APCC_OID_IEM_TEMP ".1.3.6.1.4.1.318.1.1.10.2.3.2.1.4.0" -#define APCC_OID_IEM_TEMP_UNIT

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

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

Hi all! I'm wondering if there's anyone doing any hacking on the snmp-ups driver at the moment. I've started looking at implementing 3phase-support, and this uncovered some rather unpleasant stuff in the snmp-ups driver that I really need to fix in order to get things sane. Those of you that's allergic to SNMP might want to stop reading now, this is rather icky ;)

Hi Charles, Running upsdrvctl -D start on the host with all three configured to SNMPv3 kicks out 56 different "unhandled ASN 0x81 from ..." lines on all three but importantly they all start up and keep running. I'm starting to suspect the startup is taking so long that systemd is timing out and killing it. time -p reports real time of 133.27. I'm not a fan of systemd but

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

Has anyone had any success with this card? Thank you. Sandy.

Dear all, I'm studing how to include .c code in my .r functions . In the R-exts.pdf manual I have found the following code. At one point the author write "called from R by"... How can I load a .c file on R? ( I am using a xp windows as so.) Thank you ale void convolve(double *a, int *na, double *b, int *nb, double *ab) { int i, j, nab = *na + *nb - 1; for(i = 0; i < nab; 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

Hi Alex, since I have no knowledge of the apcsmart driver, nor much time currently, I've forwarded your msg to the NUT development list. I hope somebody can take over your call. btw, please subscribe to the list for further discussions... 2007/5/28, Alex Brodsky <abrodsky at acs.uwinnipeg.ca>: > Hi, > > My name is Alex Brodsky, I am a faculty member at University of >

Hello, the appended patch converts the reason of transfer to be human readable. How about adding this variable to the usbmon message when it detects being on battery? Michael ---------------------------------------------------------------------- --- ./drivers/apcsmart.h.orig 2009-12-09 16:52:56.000000000 +0100 +++ ./drivers/apcsmart.h 2009-12-09 16:54:34.000000000 +0100 @@ -98,6 +98,7 @@

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

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

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

Hello, We have a APC SMART-UPS 2200 which gives the following status information: battery.alarm.threshold: 0 battery.charge: 089.0 battery.charge.restart: 00 battery.date: 01/10/04 battery.packs: 000 battery.runtime: 21180 battery.runtime.low: 120 battery.voltage: 52.95 battery.voltage.nominal: 048 driver.name: apcsmart driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0

I've merged apcsmart branch with master, so it should cover past issues mentioned on the mailing list - among those: - it's possible to select canonical and non-canonical mode - with the latter functioning as in apcsmart-old - CR is back to ignored characters, as IGNCR was not honored in some cases (mainly windows machines) - mutilvalue variables are now supported - the driver can

I've merged apcsmart branch with master, so it should cover past issues mentioned on the mailing list - among those: - it's possible to select canonical and non-canonical mode - with the latter functioning as in apcsmart-old - CR is back to ignored characters, as IGNCR was not honored in some cases (mainly windows machines) - mutilvalue variables are now supported - the driver can

Michal, I ran across this Debian bug today: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707223 It's a bit of a corner case, and it's for NUT 2.6.4 (apcsmart driver v3.04), but I was wondering if it was still applicable for the latest code? "nut reports 100% battery charge after unplugging the battery on a Smart-UPS 2200 RM (SUA2200RMI2U) using apcsmart. Powerchute correctly

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