similar to: about Smart-Ups RT

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 all I've a brand-new APC box, model Smart-UPS RT 5000, which comes with a black cable RJ48 in one side (10P4C) and RS232-DB9 in the other. The cable reads "940-1525A" in the DB9 side. Which is the best setting (driver and options) to connect this UPS to my computer? It seems not to be recognized by a typical apcsmart driver setting. Many thanks Noel Torres er Envite

Hi I am running FC5 with nut coming from the fc5 extras repositories. I am trying to configure a Gamatronic D-Compact ups. The cable that came with the ups has a serial connector on one end and a usb on the other. cat /proc/bus/usb/devices produces T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 4 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P:

On Aug 30, 2018, at 6:54 AM, Ong, Kevin wrote: > > I'm very sorry for the delay here, I've been very swamped with work. Here's the relevant information you guys need: > > "upsc APC_BR1500GI" output: https://pastebin.com/rH3W0dbz > "upsrw APC_BR1500GI" output: https://pastebin.com/tEWv8a3d > "upscmd -l APC_BR1500GI" output:

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

Hi all, I just got myself 2 APC Back-UPS CS 350 I downloaded the stable nut tar.gz installed it. This is not the first time i install and configure nut so i used the same configuration as on my other server as i always did. Then i made the 2 required modification. I changed these 2 thing: driver = apcsmart port = /dev/hiddev0 # ls -al /dev/hiddev0 crw------- 1 nut nut 180, 96

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

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 :

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

I can start the driver successfully manually, after the machine is up and running, but at boot time, it can't find my UPS. My init script makes sure that the usbfs is up (by checking for the existence of /proc/bus/usb/devices), and I can't think of what else could be different with the boot-time failure versus the manual startup after logging in. I'll include my configuration at the

Hi all - I'm new to both UPS setup and SNMP on linux - so I'd appreciate any help I can get....I'm stuck! I'm running fedora core 5, and have installed net-snmp and nut. I'm trying to get my network connected UPS to this linux machine. My /etc/ups/ups.conf looks like this: [upsnetwork] driver = snmp-ups port = 172.31.254.7 community = public desc="Network

An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20091231/c46cc3c9/attachment.htm>

On Dec 16, 2014, at 9:45 AM, Frantz de Germain <frantz at info.univ-angers.fr> wrote: > Bye the way I just realize that I can't retrieve the ups.load, among other > thing :-( To the best of my knowledge, Microlink is not supported by any third-party tools (including NUT), but some variables are exposed via standard USB HID. Apparently, ups.load is not one of them. Your UPS might

Hi, I am trying to set up NUT on a mini-ITX system running OpenBSD 5.5. I have an APC Smart-UPS SC620 which runs perfectly well on Ubuntu, with nut-2.2.1. Ubuntu system uses ASUS motherboard. On mini-ITX system, I have Intel d2500cc motherboard with 4 serial ports. I've tested ports by connecting them with a null-modem cable and running cu in 2 terminals. Type in one terminal, output shows

Hi all, I'm currently trying to install a APC Back-UPS ES 700 on FreeBSD. This UPS has a usb connection to the PC and is recognized as: ugen0: APC Back-UPS ES 700 FW:829.D2 .I USB FWD2 rev 1.10/1.06, addr 2 my ups.conf looks like: [back-ups] driver = usbhid-ups port = auto desc = "server" When I now run /usr/local/libexec/nut/upsdrvctl start the output is: Network UPS Tools

On Aug 30, 2018, at 10:05 AM, Ong, Kevin wrote: > > The battery.mfr.date is actually the correct value I'm looking for. That is the exact date the battery was last replaced. And yes, it is the correct value displayed in apcupsd. I think we're on the same page for the battery date. What about the date of manufacture for the UPS - does 2012 seem reasonable? > > For the debug

Le Tue, 16 Dec 2014 20:38:50 -0500 Charles Lepple <clepple at gmail.com> ?crivait: > On Dec 16, 2014, at 9:45 AM, Frantz de Germain <frantz at info.univ-angers.fr> wrote: > > > Bye the way I just realize that I can't retrieve the ups.load, among other > > thing :-( > > To the best of my knowledge, Microlink is not supported by any third-party tools

It seems the `libmodbus` library or headers were not found, or something similar - so the driver against it was not built. Did you install `libmodbus-dev` before the build? What does `config.log` in the build root say (and.or the summary shown after you run the `configure` script)? On Sat, Sep 16, 2023 at 7:46?PM FatGear <fatgear1 at free.fr> wrote: > Hi, > > I don't know what