similar to: Liebert Intellislot support

Hi, Just started using NUT with a Liebert PSI-XR 3000 with an Intellislot web card. It seems I can't get it to run properly. I am using NUT 2.6.0 built from source on Ubuntu 8.0.4 . My build parameters are : ./configure --enable-strip --with-linux-hiddev=/usr/include/linux/hiddev.h --with-udev-dir=/lib/udev \ --prefix=/usr \ --exec-prefix=/ \ --sysconfdir=/etc/nut \

OpenBSD 5.6 nut-2.7.2 (bin package) Liebert IntelliSlot Unity Card IS-UNITY-DP ups.conf: ...... ? mibs = ietf ? snmp_version = v1 ...... The problem is that the card responds to other snmp (v1,2c,3) requests normally but not to the 1.3.6.1.2.1.33.1.1.1.0 (UPS-MIB.upsIdentManufacturer). # snmp-ups -a laes2ups -DDDDDDD Network UPS Tools - Generic SNMP UPS driver 0.72 (2.7.2) ?? 0.000000???? debug

Hi All, Attached is a patch against nut-2.4.1 that adds a driver for the ESP2 protocol, as used by the serial port found on the Liebert GXT2. This driver is mostly based on: http://www.csc.liv.ac.uk/~greg/projects/liebertserial with additional bit field information from Spiros Ioannou. liebert.c at the above url has been tested by a few people to return the correct status data. Besides me,

Is this the best place to get into contact with the snmp-ups driver developers? I am trying to get the snmp-ups driver to work with a Liebert GXT2 UPS, and it works for knowing when it goes on battery and such, but when it comes to shutting down the Liebert UPS, it doesn't work. Any suggestions or docs that I need to read? -- Ronald Reed Manager of Computer Operations ARM SGP ACRF Site

Hi, I have a Liebert GXT2-1000RT230 UPS that is connected to my server using a serial cable. I have no idea to what port exactly it is connected so my first question is: how do I find out what /dev/tty** should I use? Do I need to install a device driver for it? Where do I find it? What should I use and how do I do so the server shuts down if the battery level is low? Yes, I'm a newby,

2009/10/19 Jobbagy Robert > |Hi Arnaud! Hi Robert, > I'm a hungarian developer and I need make a linux driver for this ups: > "Liebert" ? ? ? "ups" ? "5" ? ? "UPStation GXT2" ? ? ? ?"contact-closure > cable" "liebert" (I copied it from your previous mail) > So please help me,where should I start it ? > > |Thank

Hi John, do you have the device (which one? An old SNMP WEB or new UNITY DP or something else?) Or you like to buy one? If you have (or you can buy) the old one SNMP WEB - then nut should work fine with it via generic snmp driver and you don't need anything else. If you have (or you must buy) the new one UNITY DP - then I can share my snmp subdriver for it, and you should insert this

2009/1/22 Spiros Ioannou <sivann at gmail.com> > Cher Arnaud, > Hi Spiros, > I send you a demo that reads info from an Emerson Liebert > GXT2-10000T230 through the RS-232 port. This uses the "ESP-II (ESP 2) > Protocol". > Current supported data includes: measurements (voltage, temperature, > etc) , ID strings (serial number, etc), status flags (inverter on,

Good Day, I was wondering what the status was on support for the Liebert GXT2 family of UPS units? I've noted that the contact closure mode is supported along with experimental support for the 3000VA/230v model which I assume is the serial 'smart' signaling? I have several GXT2-1500's which I'm interested in getting supported in Linux and, as I have access to both the USB

Hi guys, I wrote for Arnaud that I tested the liebertgxt2 driver in 2.4.3. I compare output of Richard's code, Spiros code and nut 2.4.3. Output of Richard and Spiros codes was same and right. Output of Liebertgxt2 driver isn't. Examples: Our UPS : Liebert GXT2-1000RT230 Model Name,Firmware version,SN,date of manufactured values was right. Fields

I am working with three Liebert GXT2 UPSes connected via local TCP/IP under Linux 2.6.25.1 and getting a series of messages. First, at start, the drivers complains that the Liebert apparently extract information from certain MIBs in the ietf MIB file.... Network UPS Tools - UPS driver controller 2.2.2 Network UPS Tools - Multi-MIBS SNMP UPS driver 0.421 (2.2.2) Warning: This is an experimental

hi, we working together with robert to make liebert ups with nut. there was a good revision 2431 which gives a good result for us. this revision call the driver gxt2. after that you change the name to esp2. unfortunately this version (and the current head too) contains the same bug what was previously fixed in the gxt2 branch. it'd be useful to port the fixes to the new esp2 branch too. the

hello in first sorry for my poor english i've got a new ups "leibert GXT2-6000RT230" and i would like to use nut to make shutdown some server plugged on it. I bought a card with this ups "opencomms web card". I dont know where to plug the serial cable, directly on the serial port on the ups or on the serial port on the opencomms card, and with wich cable. I've got a

This mib used to work, so is there a way to go back to the version prior to this one without downgrading the whole package? * Starting UPS drivers... Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - Generic SNMP UPS driver 0.44 (2.4.1) Detected GXT2-2000RT120 on host upswallleft (mib: ietf 1.3) [upswallleft] nut_snmp_get: 1.3.6.1.2.1.33.1.4.4.1.4.0: Error in

based on r2432, i took this with "svn diff --revision HEAD liebert-esp2.c" fixes: 1) new way to initialize model, firmware etc. variables, the strok way failed because some vars had spaces. (e.g. model "Liebert NX") 2) new multipliers for: frequency, nominal power. I get correct readings now, before I had 500 Hz, and 200VA and now it's ok for me. Test with your models. 3)

2009/10/15 Farkas Levente <lfarkas at lfarkas.org> > hi, > i read your thread at: > > http://lists.alioth.debian.org/pipermail/nut-upsdev/2009-January/003772.html > > http://lists.alioth.debian.org/pipermail/nut-upsdev/2009-January/003775.html > we've got exactly the same problem that we need a nut driver for liebert > ups. is there any progress in this field?

Hi guys, I found the troblue and fix it! I attached the patch. The trouble was in the command reply buffer use. You compute the value that value = reply[6]*256+reply[5] <- it's wrong The right solution: value = reply[5] * 256 + reply[6]; And other bug, battery.runtime compute, you divide this value 60 <- it's wrong right value: divide 1.0 I continue the work on this

Hi, I'm trying connect a device: * OS name and version: root at nut:/etc/nut# hostnamectl Static hostname: nut Icon name: computer-vm Chassis: vm Machine ID: d7a3b7fc724f4fe1a79a3d0eeff08f72 Boot ID: 40a561c464064b5184150f5909af0aa7 Virtualization: vmware Operating System: Debian GNU/Linux 9 (stretch) Kernel: Linux 4.9.0-9-amd64 Architecture: x86-64 * NUT version

I have a need to use NUTS on a Windows 2016 Server however as all the resources are Linux orientated I am having serious issues getting things to behave. We have a serial Port COM4 attached to a Liebert GXT2-3000RT230 using its dedicated cable. It worked fine when we could use JAVA and the windows 'Multilink' software which came with it. Only MSI I could find in download section -

This patch adds support for the following ups to liebert-hid.c: $ lsusb | grep Liebert Bus 007 Device 005: ID 10af:0001 Liebert Corp. PowerSure PSA UPS Using this patch, I'm able to obtain information about the ups via upsc: $ upsc upsname battery.charge: 100 battery.runtime: 1012 battery.type: PbAc battery.voltage: 1172 battery.voltage.nominal: 12 driver.name: usbhid-ups