similar to: Liebert ESP-II protocol

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

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

Hello, I have a Liebert UPSTation GXT UPS and i'm trying to get it to work with NUT(using a Multilink serial cable) but without any success so far. I am aware about the liebert contact-closure driver but this does not suit my needs as I need to get detailed status on the ups (voltage levels, temperature, load, etc.) I have tried every driver that ships with NUT 2.0.5 with no result.

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

Hello. I have Liebert GXT3 UPS connected to CentOS Linux with kernel 2.6.32-131.0.15.el6.x86_64 and nut version 2.6.5-2. lsusb: Bus 002 Device 003: ID 10af:0000 Liebert Corp. UPS And this UPS detected only with this section in ups.conf: [liebert] driver = liebert port = /dev/ttyS0 but only this variables available: device.mfr: Liebert device.model: MultiLink device.type: ups

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,

About 8 months ago there was some noise on the mailing list about ESP II protocol for UPStation GXT and similar Liebert models -- someone had at least decoded part of the protocol. Has any work at all been done to facilitate using these units with NUT? I came upon, for free, a GXT 1500 and external battery pack. This unit is colossal: on-line protection and a great runtime to boot. But enough

I have a 64 bit Gentoo, with a Liebert UPS. The last NUT working version was sys-power/nut-2.4.1-r1 (I also tried sys-power/nut-2.4.3-r2 but downgraded, don't remember the reason). Anyway with the upgrade to sys-power/nut-2.6.0 I started to see this error message when I try to start upsdrv: [root at aemaeth:/etc/nut]$ /etc/init.d/upsdrv start * Starting UPS drivers ... Network UPS Tools -

[FAQ on USB-connected UPSes] > Remember: this is brand new *experimental* software and is probably > very broken. Do us a favor and report successes or failures to > the mailing lists. No problem ... : UPS: Liebert PowerSure PSA 500 NUT: Version 2.0.2 Kernel: 2.6.11.5, with CONFIG_USB_HID, CONFIG_USB_HIDINPUT, and CONFIG_USB_HIDDEV compiled in (statically)

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

Hello everyone, Charles suggested (about a week ago) that I repost to this list. I took a moment to run some additional tests ... The basics: -- UPS: Liebert PowerSure PSA 500 (from the 230 VAC / 50 Hz line) -- Kernel: 2.6.11.5 (from sources), USB support (down to and including CONFIG_USB_HIDDEV) compiled in statically (not as a module) -- Rest of OS: Basically still from the original SuSE

A little while ago I changed my UPS to Leibert and installed NUT. Everything worked as expected. Today I tried to use the MultiLink Viewer icon from the desktop, but it simply accepted the root password without apparently doing anything. I can run the viewer directly (as root) from a file manager. The icon is owned by me, but the application is set to run as root. I suspect that 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! Trying to set up NUT on Centos 5 to monitor a CyberPower 1500AVR UPS. There seem to be many documents, all of which seem to be not fully consistent with each other, and most of them aren't up to date. I'm guessing I should be using udev rather than hal, but I'm somewhat stumped on how to figure out what device it should be monitoring. there are a bunch of udev rules installed

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

On Aug 19, 2013, at 12:58 PM, Korviakov Andrey wrote: > I have Liebert GXT3 UPS connected to CentOS Linux with kernel 2.6.32-131.0.15.el6.x86_64 and nut version 2.6.5-2. > lsusb: Bus 002 Device 003: ID 10af:0000 Liebert Corp. UPS > > And this UPS detected only with this section in ups.conf: > > [liebert] > driver = liebert > port = /dev/ttyS0 I am confused.

Hi, I've been trying (unsuccessfully) to interact with the above UPS using its USB/HID interface and have come to the conclusion that it's not going to be as "easy" as I'd first thought :( My attempts have all been on FreeBSD-5 (kernel as of today) using NUT v2.0.2 and fiddling with newhidups -- I tried the simple approach of adding the IDs and "seeing what

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,