similar to: Liebert ESP II protocol

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.

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

I see there has been some Liebert work here recently. I have a Liebert UPS that has no USB, just RS-232. I reverse engineered the ESP-II protocol, at least as far as normal MultiLink monitoring goes, which was pretty simple. The protocol provides a table of parameter types and index ranges. So, I can read and (if I dare) write the parameter tables. We might be able to share info between

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

On Jun 2, 2017, at 8:28 AM, zefanjas <nut at zefanjas.de> wrote: > I couldn't get the GXT4 working with usbhid-ups driver. So I need some > advise to continue to get this device working. The GXT3 seems to be > working ok with NUT (http://networkupstools.org/ddl/Liebert/GXT3.html). > > Here is my ups.conf > > [ups] > driver = usbhid-ups > port =

Hello, we have a Emerson Liebert GXT4, that we like to connect to our servers to shut them down if there is a power failure (which happens quite often in our area). I couldn't get the GXT4 working with usbhid-ups driver. So I need some advise to continue to get this device working. The GXT3 seems to be working ok with NUT (http://networkupstools.org/ddl/Liebert/GXT3.html). Here is my

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?

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

Hello, I (now) own an Emerson Liebert GXT3 6000VA conected via USB. I've searched the web trying to configure nut (nut-2.6.5-1.el6.x86_64 epel rpm on CentOS 6.3) to monitor the UPS, but couldn't find a successful configuration. I'm running kernel 2.6.32-279.14.1.el6.x86_64. The UPS is connected with an USB cable: Bus 004 Device 002: ID 10af:0008 Liebert Corp. PowerSure Interactive

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,

Kris Jordan <nut.kj <at> sagebrushnetworks.com> writes: > > Marcelo Roccasalva wrote, On 3/1/2013 12:10 PM: > > On Thu, Feb 28, 2013 at 6:17 PM, Marcelo Roccasalva <roccas <at> gmail.com> wrote: > >> On Tue, Feb 26, 2013 at 10:56 PM, Charles Lepple <clepple <at> gmail.com> wrote: > >>> On Feb 21, 2013, at 6:21 PM, Marcelo

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

I know this isn't exactly the right place to ask, but I figure at least *someone* on this list has done it once. I recently acquired an AP9617 web/snmp management board for my UPS. The web and telnet part of it work great. However, I can't get *anything* from the snmp interface. I've triple-checked the community name and access settings (currently are wide open). I've ensured

[please keep the list CC'd.] On Aug 20, 2013, at 12:50 AM, Korviakov Andrey wrote: > Yes, it's my mistake: UPS used USB cable for communication, but i think that it's simple usb-com cable because nut work with liebert driver on ttyS0 port. If that is the case, I doubt that usbhid-ups will be able to retrieve any additional information. > In ups.conf i tried: > >

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

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)

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.

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