similar to: Socomec Sicon NETYS PR series

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

Hello We have an Socomec Sicon Netys PR3000 UPS equipped with NetVision Web/SNMP adaptor. I try to monitor the ups using snmp-ups driver and netvision mibs set. The snmp-ups driver starts correctly and connects to the UPS, upsd confirms it, but upsmon constantly shows "No communication" error I think the cause is the SNMP adapter reports the UPS status as "ECO mode"

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

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

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

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

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, I have in production one big ups of 30 kVA (MAS-MC 330). I bought recently one Netvision SNMP card and NUT is working with snmp-ups driver: battery.charge: 100.0 battery.runtime: -60.0 battery.voltage: 483.8 driver.name: snmp-ups driver.parameter.mibs: netvision driver.parameter.port: xxx.xxx.xxx.xxx driver.version: 2.0.2 driver.version.internal: 0.41 input.voltage: 219.0 output.current:

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

2011/11/5 Arnaud Quette <aquette.dev at gmail.com> > Hi Greg, > > 2011/11/4 Charles Lepple <clepple at gmail.com> > >> On Thu, Nov 3, 2011 at 12:23 AM, Greg Trounson <gregt at maths.otago.ac.nz> >> wrote: >> > These Socomec units have RS-232 connectors and claim to support JBUS. >> > On the nut compatibility page I only see one Socomec

Hoi all, First of all thanks for all the great work on NUT. I have two identical Socomec UPS Netys 1000PE. One is connected to an Ubuntu Hardy 64bit system and is detected just fine by the driver (v1.5.9), see below. The other one is connected to a Debian Etch 32bit system and is not detected by the driver (v1.5.9), see below. Would you have any idea how I could further debug this issue? Could

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

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

Hi, colleagues! Something strange happens with a server. I am attempting to connect management interface of UPS with server via USB. In console I see a lot of errors: Mar? 7 13:42:04 xxx kernel: ugen2.2: <POWERCOM Co.,LTD HID UPS Battery> at usbus2 Mar? 7 13:42:05 xxx kernel: uhid0 on uhub6 Mar? 7 13:42:05 xxx kernel: uhid0: <POWERCOM Co.,LTD HID UPS Battery, class 0/0, rev 1.10/0.02,

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:

Hello Ted, 2013/9/11 Ted Mittelstaedt <tedm at mittelstaedt.us> > 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<http://www.apcmedia.com/salestools/MPAO-98KJ7F/MPAO-98KJ7F_R0_EN.pdf>

Dear Mr Claesson, prepare for quite a long letter from me. I hope you will have time to read it. I bestowed a whole morning on trying to identify the correct upstype. Here are the results: root@marto:/home/marto# /usr/local/ups/bin/powercom -DD -u root -a Inform -x type=KP625AP Network UPS Tools - PowerCom and similars protocol UPS driver $ Revision: 0.5 $ (2.0.4) debug level is '2'