similar to: output of Liebert driver

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

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

Hi Guys! I would like use my ups with ub 77 usb to serial cable, because I don't have enough serial port. After the revision 2431 liebert(gtx2 /esp-2) drivers have bugs and I use rev2431 driver (liebertgtx2). It doesn't work with this cable. The Liebert App(Multilink) works with this cable. Do you have any idea ? Thanks your help. -- Best Regards, Robert -------------- next part

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

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)

I assume this is the best way to get in contact with the developers of the snmp-ups driver for nut. We have a Liebert AP300 Series UPS with an SNMP Card. I'm trying to write a new header file for nut so we can support our UPS with nut. I've got the driver to compile with Nut 2.2.0 source on RedHat EL v4 and some of the info is correct, but the main thing the power/battery status is not.

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

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

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

As I'm trying to find the correct values for other UPS models and I only see correct values, please use the attached driver while compiling nut and please give me an output from upsc. I would like you to give me the output from upsc along with the correct values you get from Multilink or the LCD. The only thing that must be wrong are the multipliers. Thanks for your effort, -Spiros

Hi, I saw your email here http://lists.alioth.debian.org/pipermail/nut-upsdev/2005-October/000243.html about the Liebert UPS protocol and I was wondering if it actually got in the NUT tree? I had a look in the 2.2.2 tree but I can only find the closed contact stuff :( -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing

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 all! I checked out the rev2366(it's stable NUT 2.4.3) and patched last liebert-esp2 revision + spiros last code. After, I used autoreconf --install and I gave the follow error msg: configure.in:86: error: possibly undefined macro: AC_C_FLEXIBLE_ARRAY_MEMBER If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.in:87:

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

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,

Liebert GXT4-1500RT120 upsc output: battery.charge: 100 battery.charge.low: 30 battery.charge.warning: 40 battery.type: PbAcbattery.voltage: 54 battery.voltage.nominal: 48 device.mfr: Emerson Network Power device.model: Liebert GXT4 device.serial: 1710600384AFBA3 device.type: ups driver.debug: 0 driver.flag.allow_killpower: 0 driver.flag.ignorelb: enableddriver.name: usbhid-ups

Hi! My Liebert Power Sure PSPXT 450 with standard driver doesn't works, so I've done this modification and now it's works. # diff liebert_MY.c liebert.c 178 < ser_set_speed(upsfd, device_path, B9600); --- That is, I've only setup the port's speed. Can you update SVN code? Thanks Bye Beppe Ursino -------------- next part -------------- An HTML attachment was

Hello The page https://networkupstools.org/ddl/Liebert/PSA_1500.html don't contain all information about UPS series PSA. First, the variable "*device.serial*" is dummy, it is always empty , and "*ups.serial*" also always empty. Second, configuration file for the all UPS "PSA" contain these lines: [PSA] ??? driver = "usbhid-ups" ?? ?port =

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