similar to: My APC ups shutdown but doesn't start again

Hello, I want to manage my SMART APC with nut 2.0.3 on Fedora Core 4. But i have this output at start of my ups: D?marrage de apcsmart :Network UPS Tools (version 2.0.3) - APC Smart protocol driver Driver version 1.99.7, command table version 2.0 Detected Smart-UPS SC1500 [5S0713T66466] on /dev/ttyS0 [ OK ] D?marrage de upsd

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:

Dear all- I have a dataset (see a sample below - but the whole dataset is June 2005 - June 2008). The "LST" format is "YYMMDDHHmm" and I would like to get the hourly average of the "mph" for the summer months (spanning all years). I have been trying to use "aggregate" but am not having much success at all! any thoughts would be greatly appreciated.

Hi folks, Today I installed nut on my Dell Poweredge 1800 server running Ubuntu 8.04 Server, with an APC Smart-UPS 1500 connected to it with the black APC cable. I used apt to install nut, upsd -v gives me "Network UPS Tools upsd 2.2.1-" I then copied and configured the config files. Most of the setup seems OK; I get console messages for line power fail / good, and I can do instant

Hello. I have this UPS: Krauler UP-D1200VA Megatec USB protocol Vendor ID: 0x0001, Device ID: 0x0000 #KRAULER UP-D1200VA VER6.00 #220.0 004 23.50 50.0 Currently I have nut 2.2.0 installed from sources. Installation was successful except that I had to change a string in 52-nut-usbups.rules from: SUBSYSTEM!="usb_device", GOTO="nut-usbups_rules_end" to:

Hello, I have a question regarding a way to control the appreance of output exported by R when I use capture.output( x, file = "Directory/file.txt") , I get a text file which when I paste to a word file looks like the first table below. The following table has its clumns spaced closely so when I paste it to a word file it looks continuous. Is there any option in R to make the outputs

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:

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

Using nut v2.2.2, and the APC serial cable. I have a client who's APC SMART-UPS 1500 (circa 2000) is always reporting LB. The batteries were old so they were replaced two weeks ago with brand new batteries. UPS still reported low batteries... I ran a calibration and a test on the unit (using the nut upscmd utility) During those tests, the battery charge on the unit goes to zero and slowly

Hello, I am not able to get NUT working with a APC SC1500. The ups has only a serial port and came with a 940-0272a serial to usb cable. The cable has a fake Prolific chip in it, so only works by downgrading the driver to version 3.2. I tested a 940-0024C cable without success as well. The ups works with powerchute and apcupsd with the 940-0272a cable. Have not tested it with the other one. OS:

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

Hello, I have just installed nut_2.6.0 from Debian testing, do anyone know the correct driver for this ups? The blazer_usb don't report battery-charge, the bundled software report charge and runtime. root at pluto<~>upsc powerwalker battery.voltage: 40.86 battery.voltage.nominal: 36.0 beeper.status: enabled device.mfr: device.model: HV 1K device.type: ups driver.name: blazer_usb

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.

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

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

Hi, I'm running this command: # upsrw -s "battery.date=2013Jun7" -u ups-mon-IT "IT-APC-BOTTOMRIGHT at 127.0.0.1" Password: OK but I'm getting this listing: # upsc IT-APC-BOTTOMRIGHT at 127.0.0.1 battery.alarm.threshold: 0 battery.charge: 100.0 battery.charge.restart: 15 battery.date: 01/10/06 battery.packs: 000 battery.runtime: 1440 battery.runtime.low: 120

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

Hi, One of my APC devices reports: "unacceptable utility voltage rate of change". I believe it has something to do with input voltage fluctuating too fast maybe even beneath or over the input voltage thresholds. Should I worry about this? should I measure input voltage? (I suppose I'd need more than multimeter readings. Maybe an oscilloscope or a multimeter that can record

Hi, I have two types of UPS devices and one of them (APC) gave me a false "low battery" alert. I can't reproduce the problem... Also, there was nothing apparently wrong with the UPS at the time of the false alert. All I could do was grab the driver values within a minute after the "low battery" notification. These are the values: battery.runtime.low : 120