similar to: Nut and liebert ups

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:

Hello, I was able to get the Vertiv/Liebert UPS (Vertiv Liebert PSA5 1500VA 900W - PSA5-1500MT120) to start working with NUT and "usbhid" driver, but would appreciate help to get it to work properly. Here's the output from the "upsc" command for a Cyberpower UPS I have: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS

Bruce Pleat via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes: > Here's the (far less lengthy) output for the Vertiv Liebert: > > device.mfr: Vertiv Co > device.model: Liebert PSA5 > device.serial: 22223106602D04C > device.type: ups > driver.name: usbhid-ups > driver.parameter.pollfreq: 30 > driver.parameter.pollinterval: 2 >

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

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

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 all, I?ve a UPS Liebert GXT3 500-3000VA with USB port. I?ve install NUT version 2.2.2 from repository packages for Debian Lenny. Linux kernel 2.6.26 I?ve try to use usbhid-ups driver in ups.conf [liebert] driver=usbhid-ups port=/dev/usb/hiddev0 Debian get the usb: # lsusb -v Bus 001 Device 002: ID 10af:0008 Liebert Corp. PowerSure Interactive UPS Device Descriptor: bLength

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

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

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

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

Replaced ups with a new Liebert UPS and it seems the device may not be known to nut. Below is output of lsusb: ID 10af:0002 Liebert Corp. PowerSure PST UPS Sent from Outlook<http://aka.ms/weboutlook> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20231204/7c08a727/attachment.htm>

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,

Begin forwarded message: > From: "Paul Smith" > Subject: Liebert PSA UPS problem. > Date: July 31, 2013 4:42:33 PM EDT > To: <nut-upsuser at lists.alioth.debian.org> > > Hi all, > A brief summary: > > I have a new Liebert PSA UPS which I wanted to help support my FreeNAS box (a FreeBSD 8 variant). Unfortunately the nut-ups implementation here for

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

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

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.