similar to: APC Smart UPS 900i

Hi, as scanning large repositories for each client connection causes unnecessary CPU/IO load, I want to know if is it possible to generate checksum digest files on the server, meanwhile? Best regards, Renne

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:

Hi, I've browsed the archives back for a few months and nothing has jumped out at me as being helpful, but since there doesn't seem to be a search facility it's certainly possible I've missed what I'm looking for. Anyway, I wonder if someone can help me. I've very recently installed nut 2.0.4-r1 on a gentoo box and am in the initial stages of configuration and testing.

I just installed nut, and I it is detected but I don't get any usefull information. I have the serial cable that came with it which is a 940-0024C and I tried setting that in the driver, but no difference. What can I do to get stuff like battery voltage and such? Thanks, Brian upsc ups1 at localhost driver.name: apcsmart driver.parameter.cable: 940-0024C driver.parameter.pollinterval: 2

Hello all, Rebooted my server by mistake (don't ask...) - everything was working OK before the reboot, but after the reboot, NUT stopped working - so had a look and I found I couldn't track the exact problem - I'm quite stumped as there's nothing indicating that there's a problem, but it just doesn't work... In a nutshell.... destiny:/usr/local/ups/bin# ./upsdrvctl

Hello all, Rebooted my server by mistake (don't ask...) - everything was working OK before the reboot, but after the reboot, NUT stopped working - so had a look and I found I couldn't track the exact problem - I'm quite stumped as there's nothing indicating that there's a problem, but it just doesn't work... In a nutshell.... destiny:/usr/local/ups/bin# ./upsdrvctl

Hi, I've set up Tinc in switch-mode on the three nodes "gw", "rb493g" and "v900w", but the nodes "rb493g" and "w900v" do not connect to each other. On each node port 655 is opened with TCP and UDP. "gw": static IPv4- and IPv6 address listed in the hosts-file "gw" hosts-files: "gw",

Hello. I've been running a two machine setup with a mge-shut for some time without problems, and now I'm configuring a three machine setup with an APC Smart 1500. The UPS has three machines connected to it, in a peculiar way: one windows machine is connected via USB. The second windows machine is using an agent to monitor messages from the first windows machine. Then, I have a GNU/Linux

Hey guys, I built my own 940-0024C cable as described here: http://www.networkupstools.org/cables/940-0024C.jpg My problem is that I can't receive anything. Sending (e.g. through minicom or my own application) works fine. Nut itself is not able to detect My UPS or anything else. <snip> [myups] driver = apcsmart port = /dev/ttyS0 cable = 940?0024C # also tested without cable option

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

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

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

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 -

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

Hi, we bought two Smart-UPS X 1500 FW:UPS 09.1 / ID=20 lsusb -v: Bus 002 Device 002: ID 051d:0003 American Power Conversion UPS Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor

Hi, by accident I realized RSync (version 3.0.5, Ubuntu 9.10) uses the root directory when the path value of a module is empty! This can cause loss of data (in my case RSync tried to get and delete the complete directory structure of a server instead of a FTP sub-directory, but luckily I had set uid and gid to nobody already). Is this solved in newer versions? If not, is there any bug-report?

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

First, a little history; nut has been working on this system for about two years. It was a Fedora Core 2 (3?) system that I wiped and installed SUSE 10.1 on so I'm fairly confident of the hardware. I thought I'd saved the nut configuration details before I did the reinstall, but can't find them. (D'oh!) The UPS is an APC BackUPS Pro 420. The cable is a clone of the APC

Hi everyone, I just want to know about driver support over new APC smart models. My company recently bought a Smart-Ups RT model: SURT3000XLI and a I cannot do to make work it with last version of nut software. Maybe this model it doesn?t supported yet and I want to know if so. The diference with others models like matrix or backup ones is the famous Smart Cable: 940-1525A (utp - db9). I