similar to: APC Smart UPS 3000 LCD & Eaton Evolution S 3000

After installing NUT, I've noticed that the belkin driver capabilities are rather basic. We have a Belkin Regulator Pro 1400VA (F6C1400-EUR), so I've updated the driver to support control of the buzzer & tests, as well as adding test result reporting. I've attached the following patches. Hopefully they can be added to any upcoming versions. -- John Bayly Systems Administrator

Hello list. I'm contemplating buying new batteries and putting an older APC Smart-UPS 3000XL back into service. Would that work well with NUT? Any drawbacks to consider? Thank you, Tobias -- Tobias Balle-Petersen Kontrapunkt Group / System Administrator

My first posting had typos. Here is the corrected version: You can lower the float charge voltage that APC Smart UPS units such as SU1000NET or SU700NET supply to the battery. This is important to prevent overcharging when when substituting Lead Acid Deep Cycle batteries for the usual sealed maintenance free batteries provided. Instructions: 1) Only do this if you're fully trained and

You can lower the float charge voltage that APC Smart UPS units such as SU1000NET or SU700NET supply to the battery. This is important when substituting Lead Acid Deep Cycle batteries for the usual sealed maintenance free batteries provided. Here are the instructions: 1) Only do this if you are fully trained and qualified to work on Lead Acid powered UPS. These units contain lethal voltages

Just my experiences speaking, look at another brand. I use MGE/Eaton and have had much better life and the quality has been much better. APC does not release the protocol for comunicating with the UPS and so to get NUT to work you have to sniff the traffic and then figure out what the commands and responses mean.(thus reverse engineered) APC also will change the protocol between models. (Thus why

I have a Smart-UPS RT 3000 XL connected via serial cable to TrueNAS TrueNAS-9.2.1.2-RELEASE-x64 (002022c) which runs on FreeBSD 9.2-RELEASE-p3. When I start the NUT service, I get the message: Oct 20 01:53:50 truenas notifier: very old or unknown APC model, support will be limited Which I interpret as an indicator of less than optimal operating mode. I suspect that the model identifier is not

Hi all, I have an APC/Smart-UPS 3000 RM that I am trying to connect to nut via the usb port. I have nut running just fine on several other machines using APC ups's via the serial ports but this usb thing is making me crazy. If I do a "/sbin/newhidups -u root -D -a PS1" it recgonizes the ups and dumps a bunch of information like below: (porky pts12) # /sbin/newhidups -u root -D -D

Hi all, I am completely new to NUT and setting up a UPS shut down in Linux. I am looking at buying a APC Smart-UPS X 3000. When I look this device up in the compatibility list this specific model is not listed, only a generic entry for "Smart-UPS". It says to use the *apcsmart* driver. The legend shows this as "protocol based on reverse engineering". What does this

Hi Chad, Thanks for your report. Everything seems fine, apart from the battery.date (2052/00/36), which vaguely recall me something... I've added this info to the Testing and trunk driver.list Arnaud -- Please note my new email address: arnaudquette at eaton.com -- Linux / Unix Expert R&D - MGE Office Protection Systems - http://www.mgeops.com Network UPS Tools (NUT) Project Leader -

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

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 all, I just changed my old MGE ellipse for a evolution 850 (now eaton). I can connect using mge-shut (newmge-shut doesn't work). But I have a few issues. I lloked around on NUT web-site and googled with no luck. Using debian lenny on 2.6.18 kernel (due to some ISDN driver that doesn't work with earlier kernels) 1) the most annoying is that I cannot shutdown the UPS. here is a trace :

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

Has anyone been able to get an APC Smart UPS C1000 to work with NUT on pfSense? I can't figure it out. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20120830/d1f5b864/attachment.html>

Dear Sir, Please tell me if u have any method to increase the charging current of APC smart 1000/1400VA with and without external battery bank option. I am using externally 40 and 80 Amp lead acid batteries but charging time is too long. Please help me ASAP. Regards, Afzaal Ahmad UPS Engineer afzaal.ahmad at sbp.org.pk -------------- next part -------------- An HTML

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

> > On Fri, 2010-01-29 at 16:53 -0500, m.roth at 5-cent.us wrote: <battery change tale o' woe snipped> >> But the idiot light's still on. <snip> Well, I followed the link to the NUT info, and tried a "manual" calibration, and still no joy. Swapping in a cartridge that's still good, the light goes out, so it's not the unit. However, googling for

I'm trying to use a rackmount Smart-UPS from APC with the USB connector, and I'm running into some issues. They seem to stem from the fact that the Report Descriptor is much larger than any other UPS I've seen (61939 bytes). Here is the quick fix that I put in libusb.c after getting the HID descriptor, and before getting the Report descriptor, which seems to work okay:

Peter, if you're back, I was wondering if you might have a chance to look into the issues I reported last month. I'm back to using hidups right now, but I would prefer to use a current, maintained driver. Thanks!

Hi all, when I try to get infos from this ups, the only variables that upsc print is: # upsc Smart-UPS@localhost driver.name: apcsmart driver.version: 2.0.0 driver.version.internal: 1.99.6 ups.mfr: APC ups.status: OL Is it not possible to get voltage and other infos from that model of UPS? Thanks. Regards, Dio.