similar to: Liebert PSIXR 3000 intellislot web card support with NUT 2.6.0

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 \

OpenBSD 5.6 nut-2.7.2 (bin package) Liebert IntelliSlot Unity Card IS-UNITY-DP ups.conf: ...... ? mibs = ietf ? snmp_version = v1 ...... The problem is that the card responds to other snmp (v1,2c,3) requests normally but not to the 1.3.6.1.2.1.33.1.1.1.0 (UPS-MIB.upsIdentManufacturer). # snmp-ups -a laes2ups -DDDDDDD Network UPS Tools - Generic SNMP UPS driver 0.72 (2.7.2) ?? 0.000000???? debug

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:

Hi, Does anyone have a similar configuration or have used the same model with Ubuntu before with success? Strange my system can't seem to detect the UPS and I can see usbhid 2-1.1:1.0: couldn't find an input interrupt endpoint in dmesg when I plug in the UPS. Hope can share your experience on this.

Hey all, We're looking at XPCC UPS's and realized they're not listed on the NUT HCL. However, in my experience a lot of manufacturers use technology that is bought/licensed from someone else. So a driver for "XPCC" might not exist, but the XPCC brand might actually use a driver of a different name. The last mention in the list archives of "XPCC" is several years

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Has anyone used nut with a XPCC UPS, in particular one of the XVRT units? Their supplied monitoring tool "works", but I'd really prefer to use nut if possible. I've systematically gone through each of the drivers in /lib/nut and none seem to talk with the unit properly. I'll be talking with a XPCC support person tomorrow, though

Hi, I'm trying connect a device: * OS name and version: root at nut:/etc/nut# hostnamectl Static hostname: nut Icon name: computer-vm Chassis: vm Machine ID: d7a3b7fc724f4fe1a79a3d0eeff08f72 Boot ID: 40a561c464064b5184150f5909af0aa7 Virtualization: vmware Operating System: Debian GNU/Linux 9 (stretch) Kernel: Linux 4.9.0-9-amd64 Architecture: x86-64 * NUT version

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 -

I'm running a PDC on Samba 3.60. Just freshly upgraded it from Samba 3.028a with the purpose of supporting Windows 7. However though all the existing users and computers are running fine, I'm stumped trying to join a new Windows 7 machine to it. I have applied the DomainCompatibility registry fix. When I try to join a Windows 7 workstation I will get this message : The join operation

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

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

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

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.

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

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)