similar to: Problem after reboot

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.

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

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, I can get nut to work with this UPS using the apcsmart driver, but only with limited functionality. It is only reporting the OL/OB status and that's about it. None of the other useful variables such as run time, load etc are reported and initiating battery tests does not work either. Has anyone managed to get nut to report more than these variables with a Matrix type UPS? I see

Hi, I'm running an old APC Smart UPS 900i. As there isn't any software from APC which supports this UPS anymore, I've installed NUT (Gentoo Ebuilds), but version 2.0.5 and version 2.2.2 loose connection to the UPS while version 2.4.1 and SVN version don't show any settings and there are no instant commands. The only information I can get are: driver.name: apcsmart

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

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

Hello, I am working on getting NUT working with my Smart-UPS 900 UPS (with the C c= able) For several years, I have used the apcupsd product, but because of the nagios support for nut, I am working on switching over. Under apcupsd, I get tons of information from my UPS: # /usr/local/sbin/apcaccess status DATE : Sat Jul 09 12:56:41 CDT 2005 HOSTNAME : homer RELEASE : 3.8.6 UPSNAME :

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

I have a Dell PE 2850 connected via 940-0024C cable to serial port on the UPS mentioned above. I've used apt-get to install nut-2.0.2-3 and attempted to configure based on the documentation. So far I'm getting the following when I try to start ups daemon: server:/etc/ups # /etc/init.d/ups start Starting service NUT: -> Starting UPS driver: Network UPS Tools - UPS driver controller

I have installed nut 2.0 Var/log/messages: Aug 14 16:37:26 server kernel: hiddev96: USB HID v1.10 Device [American Power Conversion Back-UPS BF500 FW:814.s3.I USB FW:s3] on usb-0000:00:1d.0-1 Aug 14 16:37:26 server kernel: hub 5-0:1.0: USB hub found Aug 14 16:37:26 server kernel: hub 5-0:1.0: 2 ports detected My ups.conf : [APC350] driver = apcsmart port = /dev/usb/hidddev96 desc =

[BackUPS] driver = apcsmart port = /dev/ttyS0 desc "Back-UPS BK-300 @ Cap a l'orignal" > ----- Original Message ----- > From: "Charles Lepple" <clepple@gmail.com> > To: "NUT-MList" <nut-upsdev@lists.alioth.debian.org> > Sent: Monday, June 19, 2006 2:38 PM > Subject: Re: [Nut-upsdev] Backups 300VA (BK-300C) Drivers >

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

Hi All, I've got two APC SmartUPS's that behave differently with nut, I have a SmartUPS1400 & a SmartUPS1250. I'm fairly sure this isn't a nut problem but more likely a problem with the age of the SmartUPS1250 and the apcsmart driver not being able to identify it. Under the APC Powerchute software the same monitoring & command parameters are available for both

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, What driver should i use with APC BK-300C ? Michale Plourde Digicom Technologies

I'm currently testing the bcmxcp driver for NUT, and it causes me some trouble. And when scanning the archives it seems like the 3110 USB problem reported recently. The bcmxcp daemon stops running, and the logs shows the following: Oct 6 14:22:32 host.dom.tld bcmxcp[82628]: Communications with UPS lost: Receive error (data): got -1 bytes instead of 28!!! Oct 6 14:22:33 host.dom.tld

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: