similar to: APC Smartups protocol - Hidden Programming Mode

I need direction. I don't know what to google for anymore. I am unable to get my SmartUPS 2200XL to be recognized. My suspicions are that it's UDEV or Kernel related. I've updated the kernel to the highest version I feel comfortable with due to other things that run on the server, and I've updated UDEV a bit too. When I plug in the USB cable from the UPS into the server, I

Hi All, I have what is probably a 12 year old (or older) Compaq R3000 UPS plugged into a FreeBSD 8 system running NUT version 2.6.5 This UPS contains a total of 16 batteries in 2 banks of 8, each battery is 6 volts and the bank produces 50 volts. The UPS monitors battery voltage and the battery charger in the UPS works like this. For about 2 days it will apply a charge/float/topping

2009/5/3 Thomas Juerges > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Arnaud, > Hi Thomas, > I just checked the 2.4.1 version of nut and found that you forgot to add > my old UPS model (APC Smart-UPS 900). I guess it is because you were > busy at the time when I sent you the patch. So here it goes again. :) > uh, right sorry. I was pretty sure I applied

I have a SmartUPS 750 (SUA750) which has the temperature and humidity SmartSlot card installed. When NUT 2.2 communicates with this UPS over /dev/ttyS0 using apcsmart, using the APC Smart cable connected to the SUA750 serial port, and this ups.conf: [su700] driver=apcsmart port = /dev/ttyS0 I can see the ambient temperature and humidity data with "upsc su700 at

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

We recently had to replace an old APC SmartUPS 3000 with a newer 3000VA (the 2U one). It has both serial and USB in the back (with an RJ-45 on the end of the serial cable). I can't get the apcsmart driver to connect. I figured it should work the exact same as the old UPS, with /dev/ttyS0 as the port (I'm using the same port on the server that the last one was plugged into). I even

Ok, so another apc UPS 3000 complained about bad batteries, and I changed them out from the same order that I'd gotten in a couple of months ago. The APC SmartUPS 3000 started connecting and disconnecting the USB connection. I brought down and up the service, no joy. Finally, after googling, I found a *completely* undocumented way to start apcupsd, that a few years ago someone was told to

Hello One our customer has two Linux HP-branded servers powered from "clasic" APC Smart-UPS 2200 RM 2U (p/n SUA2200RMI2U). It is connected to first server via RS232c port with APC-branded cable. We have installed NUT 2.6.4 with apcsmart driver. This setup works fine for months. Two weeks ago all the hardware powered from the UPS started to switch off occasionally while on line

Hello, I can't make a brand new APC SmartUPS 1000 (REF SMT1000I) communicate with a ubuntu 8.04 server via usb port. NUT version 2.2.1 seems to be the last on ubuntu 8.04 Could you help me please ? Thanks Herv? Mazzilli ----------------------------------------------------------------------------------------------- root at myserver: lsusb -vvv --> Protocol spec without prior Class and

I'm trying to setup a server controlling 8 ups, 6 APC Smartups 1500 and two 1000. Because of the number of ups, i connected them using usb cables. I'm using Debian Etch AMD64 and nut 2.2.0 from testing (already tried 2.0 from stable, but had problems reading the ups serials and all the following problems of 2.2). This is my ups.conf: [ups2] driver = usbhid-ups port =

Well, here's the tale: we got a "replacement kit" for some APC SmartUPS 3000 - rackmount UPSs. The "kit", costing about half of what APC is asking, is just the batteries, and you pull the tray out, open it up, and swap out the batteries. Except, I did this on one... and the replace battery light never went out. Not using apcupsd's apctest, not pushing the button. The

On Tue, 8 Oct 2013, Philip Tait wrote: > Here is the upsc output: > > # /usr/local/ups/bin/snmp-ups -DD -a irs2-ups1 > Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) > 0.000000 debug level is '2' > 0.000327 SNMP UPS driver : entering upsdrv_initups() [snip] > 4.457750 No supported device detected I'm using a APC smart ups with a

Bonjour, Je fais suite au message que vous avez post? en 2015 : http://lists.alioth.debian.org/pipermail/nut-upsuser/2015-February/009568.html J'ai le m?me probl?me et ne trouve pas la solution. Comment vous en ?tes-vous sorti ? D'avance, merci pour votre aide. -- Cordialement Herv? BASTET Nouveau num?ro non surtax? 01 69 42 87 94 Ce message est prot?g? par les r?gles relatives au

OS: CentOS 7 NUT Version: 2.7 Installed NUT through: yum install nut UPS: APC smart UPS srt3000 with NMC I am trying to set up NUT with snmp for my apc ups. Heres the config; [ups6]                 Driver = snmp-ups                 Port: ups6.domain.name (also tried 192.168.24.9)                 Snmp_version = v3                 secLevel = authPriv                 secName = ups6

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

Hi, Can't get newhidups (2.0.5) or usbhid-ups (SVN trunk) to work 2.0.5 hidups seems to work, but I was hoping for more information... like temperature, etc. Tried newhidups and usbhid-ups, but they don't seem to detect my UPS... should I switch back to serial? Will I get more information? (trying not to move back to apcupsd, since i have a mixed environment) Here is some debug

Hi, I have the following system configuration (probably does not matter, but anyway): Ubuntu Linux x86 VM running under ESXi bare metal hypervisor. UPS is connected to the ESXi host, and VM communicates to the UPS using USB pass through option. Details of elaborated shutdown sequence are out of topic, so I skip them. NUT was installed from the package, I believe it is recent enough. NUT was set

(Note that I mentioned this *was* previously working with an older version of Nut). [irs2-ups1] driver = snmp-ups port = irs2-ups1.sum.naoj.org mibs = auto community = private irs2-ups1.sum.naoj.org responds to pings. On Tue, Oct 8, 2013 at 3:55 PM, Tim Rice <tim at multitalents.net> wrote: > On Tue, 8 Oct 2013, Philip Tait wrote: > > > Here is the upsc

Here is the upsc output: # /usr/local/ups/bin/snmp-ups -DD -a irs2-ups1 Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) 0.000000 debug level is '2' 0.000327 SNMP UPS driver : entering upsdrv_initups() 0.000341 SNMP UPS driver : entering nut_snmp_init(snmp-ups) 0.056112 SNMP UPS driver : entering load_mib2nut(auto) 0.056126 trying the new

We are configuring a server with a Tripplite SmartUPS, Web SNMP Card, and Envirosense Probe. The configuration is good using usbhid driver and we can get it to shutdown clean by producing a "power event" (pull the power cable). It is not very clear how to add or see the values associated with the external probe. We need to be able to shutdown based on the input from the probe as well as