similar to: patch for support Liebert GXT2 ESP2 protocol

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

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

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,

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

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)

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

Good morning, I just had the chance this morning to get my linux box tied into our network and talking to the UPS. I can now confirm that in NUT v2.4.3 snmp-ups (ietf) works with the Liebert Intellislot Web Card for the GXT2 family of UPS'. upsc output: tux ~ # upsc workups at localhost battery.charge: 100.00 battery.runtime: 2760.00 battery.runtime.low: 5 battery.voltage: 54.60 device.mfr:

Good morning, I just had the chance this morning to get my linux box tied into our network and talking to the UPS. I can now confirm that in NUT v2.4.3 snmp-ups (ietf) works with the Liebert Intellislot Web Card for the GXT2 family of UPS'. upsc output: tux ~ # upsc workups at localhost battery.charge: 100.00 battery.runtime: 2760.00 battery.runtime.low: 5 battery.voltage: 54.60 device.mfr:

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

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

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

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

Hello, 1) I'm planning on adding lots of measurements to the driver liebert-esp2 + correct support for 3-phase systems. Should I make a large patch based on the last svn head or send you the whole file? Multiple patches per change are probably not practical in this case. 2) in http://www.networkupstools.org/doc/2.2.0/new-names.html there is no crest factor variable. Crest factor is very

Attached. I also attach sample output from upsc OL & OB. I only tested it with 3-phase in/3-phase out ups. Thanks, -Spiros -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20100421/1d18bd30/attachment.htm> -------------- next part -------------- battery.current: 0.00 battery.runtime: 4860

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/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?

More detected parameters (attached), this time measurements for all 3 phases. I include only new discovered readings. Multipliers are wrong right now and need to be defined, and some commands are probably invalid/wrong, but most seem ok. I hope I find the time to implement those on the driver. What I'm missing is a way to discern between 1phase & 3phase (output) upses. output + read

hi, it seems our latest liebertgxt2 patch still missing from the just released 2.6.0. i'm attached the patch to the 2.6.0. this patch: - add the possibility to properly shutdown the ups, - can be used through usb-serial adapter cable too. could you apply it to the source. regards. -- Levente "Si vis pacem para bellum!" -------------- next part

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

Hi Guys! I'm back and work on this driver again. First, I checked out the HEAD rev and tried the liebert driver. it gave wrong model,firmware,serial, mfr date value. caused by len variable in line 97 and after I use my ups with usb -> serial converter. these patches attached Did you try the liebert-esp2 driver in ON Battery mode ? Because If I switch my ups on battery (plugged off the