similar to: Snmp-ups/netvision driver for Socomec UPS

Hello list, I've installed NUT on an HP blade server, and I try to get it communicating via SNMP with 2 HP R3000 UPSes, each fitted with a AF465A management card. To do this, I used the snmp-ups driver, and configured it for the "cpqpower" MIB. Communication with the UPSes is established. My problem is that both UPSes constantly return the "OL OB" status which, in

Hi Henning, note that I've cc'ed the NUT users list for info. 2015-02-04 13:47 GMT+01:00 Henning Fehrmann <henning.fehrmann at aei.mpg.de>: > Hi Arnaud, > > > the best to process the value would be to have the MIB definition for > > upsAlarmOnBattery, as for example: > > [1] >

On Oct 2, 2014, at 1:53 AM, Tarvo Tiits <Tarvo.Tiits at automaatika.ee> wrote: > On 02.10.2014 03:42, Charles Lepple wrote: >> On Oct 1, 2014, at 5:07 AM, Tarvo.Tiits at automaatika.ee wrote: >> >>> Why is ups.status empty? >> If I understand the commit log for SVN r3590, then that revision was supposed to set the status to OL if the numeric state was 9 for

On 02.10.2014 03:42, Charles Lepple wrote: > On Oct 1, 2014, at 5:07 AM, Tarvo.Tiits at automaatika.ee wrote: > >> Why is ups.status empty? > If I understand the commit log for SVN r3590, then that revision was supposed to set the status to OL if the numeric state was 9 for ECO mode. It does not appear to do that: > >

Hello, we have two UPSes - one Galaxy and one from Socomec, both monitored by the NUT server. The NUT server runs the version 2.7.2. We have roughly 3500 clients running upsmon, reading the status of both UPSes. They run mainly the version 2.6.4 and some 2.7.2. We observed the following on both client versions, regardless whether we run upsmon in the daemon or debug mode: Running upsc socomec

Hi, I am using the NUT Software 2.7.4 (Ubuntu Repository) on Ubuntu 18.04. Configuring a UPS with the snmp-ups driver and overriding the battery.runtime.low variable leads to following warnung/error: Sep 23 11:10:08 hostname snmp-ups[27115]: dstate_setflags: base variable (battery.runtime.low) is immutable Default for battery.runtime.low is 180 seconds. My idea is to increase the value to

Hi, I have UPS Socomec ITYS 3000 with Netvision card. OS is Centos 6.5 64-bit. NUT installed with yum,. nut-2.6.5-2.el6.x86_64 nut-client-2.6.5-2.el6.x86_64 Why is ups.status empty? Here is upsc output: upsc myups at localhost battery.charge: 97.00 battery.runtime: -60.00 battery.voltage: -0.10 device.mfr: Net Vision v6.01 (SN 0101414290) device.model: ITYS 3 kVA device.serial: 3I14450043

Hello, I have tried to use the blazer_ser driver to interface with my UPS. nut is not able to detect the UPS. I have not been able to find much info regarding Socomec UPS support in nut. Socomec does publish a description of the serial protocol for these UPS's, which can be found here: http://www.socomec.com/download-jbus-modbus.html(select UPS OTHER for device model, 1-5KVA for device power

Hi, I am considering purchasing a UPS and want one that I can query from bash scripts. I would assume nut to be the best tool to allow this. I have been directed to a Socomec RT 3000VA UPS. I have previously had MGE Pulsars and interfaced to them with nut's mge-utalk and mge-shut drivers with reasonable success, apart from the odd data stale error. These Socomec units have RS-232

Hello, I have an NETYS RT 1/1 UPS, which is not fully supported. Starting snmp driver displays: [root at kvm1 ~]# snmp-ups -a local Network UPS Tools - Generic SNMP UPS driver 0.66 (2.6.4) Duplicate driver instance detected! Terminating other driver! No matching MIB found for sysOID '.1.3.6.1.4.1.2254.2.4'! Please report it to NUT developers, with an 'upsc' output for your

Hello, I have an NETYS RT 1/1 UPS, which is not fully supported. Starting snmp driver displays: [root at kvm1 ~]# snmp-ups -a local Network UPS Tools - Generic SNMP UPS driver 0.66 (2.6.4) Duplicate driver instance detected! Terminating other driver! No matching MIB found for sysOID '.1.3.6.1.4.1.2254.2.4'! Please report it to NUT developers, with an 'upsc' output for your

On Oct 1, 2014, at 5:07 AM, Tarvo.Tiits at automaatika.ee wrote: > Why is ups.status empty? If I understand the commit log for SVN r3590, then that revision was supposed to set the status to OL if the numeric state was 9 for ECO mode. It does not appear to do that: https://github.com/networkupstools/nut/commit/9cb2de3d9568aa382cc118b4385d97d5664c457b Is your UPS set to ECO mode? Can you do

hello, I have a few UPSes (NETYS PR 3000, 2000, 1000), with no SNMP-adapter installed. There are serial ports only. I tried to use megatec and powercom drivers. They don't work. Which driver to use? Thanks. -- wbr

Hello i tried to connect my netys 2000 pr ups to ubuntu 11.10 and i have a problem connecting it. After readin a few post i realized to dianosse the connection. I need help resolving the connextion issue So here is the response to??/lib/nut/usbhid-ups -u root -DDDDD -a netys: Network UPS Tools - Generic HID driver 0.35 (2.6.1) USB communication driver 0.31 ? ?0.000000 ? ? send_to_all: SETINFO

2014-02-12 10:13 GMT+01:00 <hamid.nabil at coop.no>: > Arnaud, > > > > I see your name all over when I look for Netvision MIB. Thought maybe you > can help me. I want the MIB for our UPS (SOCOMEC) with NetVision 6.0 > > > > I appreciate your help in advanceJ > > Regards > > Hamid Nabil > > > Hello Hamid, the procedure describing how to do

Hi All, About a month ago APC announced they were including MODBUS protocol support in their new APC UPSes. The technical note on this is here: http://www.apcmedia.com/salestools/MPAO-98KJ7F/MPAO-98KJ7F_R0_EN.pdf "Application Note #176 Modbus Implementation in APC Smart-UPS" The APC "announcement" appeared on their site in their user blogs by an APC employee, here:

Hi all, I recently upgraded an ubuntu jaunty machine with nut 2.4.1 to lucid LTS. The previously working nut configuration is a no-go, but I got it up and running using the snmp-ups executable from the previous install. What it happens (from what I can see at least) is that the status has been changed and it's not read as before. In the 2.4.1 release I had an "OL" string (online, I

Dear Sirs, I'm Massimo Zampieri responsible for the software and connectivity accessories for Riello UPS. I would like to list our UPS to NUT. For this porpoise we will provide to you all the information requested as serial protocols, end even some ups in case. We have 2 way to communicate with our ups via RS232 and USB (with our driver, but the source code will be provided in case) and via

Here's the first update of ups.status: 0.102449 getting data: ups.status (.1.3.6.1.4.1.232.165.3.4.5.0) 0.102546 su_ups_get: ups.status .1.3.6.1.4.1.232.165.3.4.5.0 0.102646 nut_snmp_get(.1.3.6.1.4.1.232.165.3.4.5.0) 0.104539 SNMP UPS driver : entering su_status_set() 0.104641 su_find_infoval: found OL (value: 3) 0.104730 => value: 3 0.104823 getting data: ups.status

Hi Saulius, The spec you sent me is simply a Megatec excerpt: http://www.networkupstools.org/protocols/megatec.html So Socomec is simply a megatec rebranding (selling by simply putting its name on). As per the NUT compatibility list (http://www.networkupstools.org/compat/stable.html), Sicon are supported by the powercom driver. But since it's a megatec unit, you should preferably try the