similar to: please this driver if you have liebert/emerson ESP-II capable ups

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,

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?

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

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

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

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 =

Hi On 10/06/2014 03:04 PM, Charles Lepple wrote:> I think I see what is going on. > >???? 0.368670??? Report[buf]: (5 bytes) => 05 4e 00 48 00 >???? 0.368698??? PhyMax = 0, PhyMin = 0, LogMax = 1, LogMin = 0 >???? 0.368723??? Unit = 00000000, UnitExp = 0 >???? 0.368747??? Exponent = 0 >???? 0.368776??? Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x05, Offset:

On Nov 9, 2014, at 6:58 AM, Marcelo Fernandez <marcelo.fidel.fernandez at gmail.com> wrote: > I'm attaching a new debug log with this modification, just in case, > but I'm still seeing the lines you've pointed at: > > 0.062308 Path: UPS.PowerSummary.Voltage, Type: Feature, > ReportID: 0x05, Offset: 0, Size: 16, Value: 1 > 0.062336 Report[buf]: (5

Hello, this is to let you know I will start working on a modbus driver for the PhoenixContact QUINT-UPS industrial DC UPS, model 2320461. https://www.phoenixcontact.com/online/portal/us?uri=pxc-oc-itemdetail:pid=2320461&library=usen&pcck=P-22-07-01-01&tab=1 I will reuse some parts of the nutdrv-modbus branch, but this will be a model specific driver, not a generic one. Unfortunately

On Nov 6, 2014, at 5:56 PM, Marcelo Fernandez <marcelo.fidel.fernandez at gmail.com> wrote: > battery.voltage: 10000000. > battery.voltage.nominal: 0.0 Well, these are certainly interesting values ;-) I suspect the correction for earlier units has failed. Can you please start the driver with "-DDD", let it run for a minute, then gzip and attach the resulting log? --

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

On Nov 9, 2014, at 8:13 AM, Marcelo Fernandez <marcelo.fidel.fernandez at gmail.com> wrote: > 2014-11-09 9:59 GMT-03:00 Charles Lepple <clepple at gmail.com>: >> >> Strange, I would have thought that the "Value: 0" would show the actual number. Does it look like drivers/libhid.o got rebuilt? > > Yes, at first I thought the same (that I did something

Hi, thanks for your helpful reply. I've added the productid in the ups.conf and it seems to work (better) now. > After starting the driver and upsd, what does "upsc ups" return? If you can also include "upsrw ups" and "upscmd -l ups" output, we can update the DDL. #upsc ups Init SSL without certificate database battery.charge: 100 battery.charge.low: 20

hieverybody I'd like to ask if anybody have any experience with above products? and positive outcomewhen coupled with nut? thanks

On Jun 4, 2017, at 8:32 PM, zefanjas <nut at zefanjas.de> wrote: > > Hi, > > thanks for your helpful reply. I've added the productid in the ups.conf > and it seems to work (better) now. > > >> After starting the driver and upsd, what does "upsc ups" return? If you can also include "upsrw ups" and "upscmd -l ups" output, we can

Hi, >> #upsc ups >> >> Init SSL without certificate database >> battery.charge: 100 >> battery.charge.low: 20 >> battery.charge.warning: 0 >> battery.type: PbAc >> battery.voltage: 1.0 >> battery.voltage.nominal: 0.0 > > Similar to Mike's report on the CPS UPS, the HID descriptor for this device is buggy: > > Logical