similar to: Unable to detect an APC Smart protocol UPS. Windows. APC Smart protocol driver 3.04 (2.6.5-3723:3731M)

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

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

Hello, I'am having huge performance problems using a application on win32 which uses alot of .DBF files. The app uses *alot* of small file reads, varying between 20-512 bytes per read. On Windows there is something, only just learned this, called fastio. This fastio acts like a cache because it reads-ahead 4096-bytes even if you want to have 1 single byte. Ok, that's all nice _but_

Hi, I'm trying to configure my ups with nut which is a locally made one. It uses a rs232 port to talk to the computer and comes with a software called "Powermanager Lite" which is provided by Richcomm and supports Windows, Linux and UNIX. According to the manual it uses the Richcomm circuitry to talk to the computer and uses a drycontact protocol. Unfortunately I couldn't

The Wine development release 1.9.21 is now available. What's new in this release (see below for details): - Initial version of the HID minidriver. - Support for lists in the RichEdit control. - System tray improvements. - Various bug fixes. The source is available from the following locations: http://dl.winehq.org/wine/source/1.9/wine-1.9.21.tar.bz2

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

Hi Charles, On Monday, 27. June 2016 08:59:02 Charles Lepple wrote: > > is there a way to query from the cmdline if the UPS data is stale? > > The "data stale" state applies to the entire set of variables for an UPS, > so if the exit code of `upsc` is zero, the data set is not stale. > > "upsc" outputs a lot of information, but not if the data is stale.

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

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

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:

Thanks for the help, with the apcsmart-old driver it works again! Didn't notice my UPS is now so "old" ;-) Here is the output of upsc with apcsmart-old driver: battery.alarm.threshold: 0 battery.charge: 100.0 battery.charge.restart: 00 battery.date: 11/22/06 battery.packs: 001 battery.packs.bad: 000 battery.runtime: 540 battery.runtime.low: 120 battery.voltage: 53.73

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

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

As I requested here: https://bugzilla.redhat.com/show_bug.cgi?id=678793 Add support for Matrix-UPS firmware 0XM/0XI with additional commands Description of problem: The attached patch adds support for Matrix-UPS revision strings 0XI and 0XM to the apcsmart driver. The revision string itself isn't completely opaque--it is made up of different parts as documented on

On Jun 13, 2013, at 7:14 AM, ML mail wrote: > I just upgraded to Network UPS Tools upsstats 2.6.4 on Debian wheezy and noticed that it does not show the battery runtime anymore, the field is simply empty. It used to work before with NUT 2.4.1. Does anyone know what could be wrong? > > I am using the apcsmart UPS driver. The apcsmart driver was overhauled, and in 2.6.x, the previous

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: just got an APC UPS on hand. it's a strange new one, not smart-ups or back-ups. it's APC Easy UPS: https://www.schneider-electric.com/en/product-range/65883-easy-ups-on-line/ I don't know what's different. this series are all online UPS and they are cheap. it comes with serial and usb interface. with serial interface I can use apcsmart to connect. but with usb

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