similar to: Proposed addition to apcsmart driver

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

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

Hello. I have problem with connecting to APC SC1000 using NUT port for windows 2.6.5-6. Last working version is NUT 2.6.1-1. With the same config files it works well. c:\NUT\bin>apcsmart.exe -a SC1000 Network UPS Tools - APC Smart protocol driver 3.1 (Windows-v2.6.5-5-7-g72f380c) APC command table version 3.1 w32_serial_open (COM3) setting initial state on COM3 0000007C = w32_serial_open

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

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

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

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 -

Greetings all, I am getting an error message that is stifling me. Any ideas? > ## Define Directories ## > load_from <- "/home/mcc/Dropbox/abrodsky/kegg_combine_data/" > save_to <- "/home/mcc/Dropbox/abrodsky/ttest_results/" > > ############################### > ## Define Columns To Compare ## > compareA <- "log_b_rich" > compareB

Hello All, I have Samba 3.0 and 3.0.7 servers that have similar problem , the problem occures once a week ~aprox, all about 1 per minute samba server created smbd -D process with root ownership thats never die, the server stucks after about 200 such processes and I need to reboot it to release the stuck. There is someone knows why it happens Denis

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

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.

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

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.

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

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

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

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: