similar to: APC Measure UPS support

I sent this to the NUT users list and no response so I thought I'd send it here next.. It's a pretty easy issue really: > Hey all, > > I have a measure-UPS card and the external cabled module. > > They're supposed to operate the same... does NUT auto detect them when using the apcsmart driver or are there config parms required? > > The the smart-slot unit is

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, We have several APC Smart UPSes (serial port/apcsmart) with the APC Temp/Humidity sensor cards (AP9612TH). The sensor cards have 2 plugs for 2 separate sensors. So far, we have only used one of the sensors in conjunction with the apcsmart module from nut. This has been working great. Example output: [nut at nut]# upsc APC11 ambient.humidity: 037.2 ambient.humidity.alarm.maximum: NO,NO

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

Hi, We have a several AP9612TH environmental cards (they have 2 probe connectors) inserted into our APC UPS devices which monitor temperature and humidity. The apcsmart nut module knows how to query the ambient.temperature and ambient.humidity using the 't' and 'h' commands of the UPS (refer to apcsmart.h). The results of the 't' and 'h' commands are from probe 1.

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

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 have two types of UPS devices and one of them (APC) gave me a false "low battery" alert. I can't reproduce the problem... Also, there was nothing apparently wrong with the UPS at the time of the false alert. All I could do was grab the driver values within a minute after the "low battery" notification. These are the values: battery.runtime.low : 120

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

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

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

I'm looking to buy some new UPSs and am thinking of parting ways with APC to explore other brands. Can anyone suggest another brand that handles doing calibration runs (or maybe another brand doesn't need them) that I can automate with NUT? Thanks, -Ben

On Dec 17, 2014, at 3:46 AM, Frantz de Germain <frantz at info.univ-angers.fr> wrote: > This seems to me a little bit complicated :-( Instead, can I use the > apcsmart driver with the provided 940-0625a c?ble (RJ45/DB9 connectors) ? Or > do I need to acquire an AP9620 SmartSlot expansion card, as I've seen in the > Hardware compatibility list page ? It sounds like you might

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

On 2016-01-18 6:07 PM, Charles Lepple wrote: > [please use reply-all to include the list. thanks!] > > On Jan 18, 2016, at 5:08 PM, Ben Kamen <bkamen at benjammin.net> wrote: >> >> (is the USBHID worth using?) > > - - - > > Sounds like you are on the right track with the text protocol. There are two different sscanf() format strings - it looks like yours

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

Hey all, I ended up picking up the module listed in Subject line. I switched over my config but apparently not all going smoothly. My config is: [office] driver = powerpanel port = /dev/ttyS0 desc = "Office UPS" When I test the driver running power-panel as a test, I get: > [root at cornelius init.d]# powerpanel -a office -D -D -D -D >

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

Hi all, Thought I'd forward this on, as the apcsmart driver doesn't appear to have any support for this (admittedly obscure) setting and it doesn't seem to be listed at http://www.networkupstools.org/protocols/apcsmart.html. Hope someone finds it useful. Later, Russ -- Russell Odom http://www.gloomytrousers.co.uk/ Fast, cheap, good: pick two. -------- Original Message --------