Displaying 5 results from an estimated 5 matches for "gtx2".
Did you mean:
gtk2
2009 Oct 18
3
liebert GTX2 ESP-II serial support
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 Oct 20
1
Driver for Liebert
...2" ? ? ? ?"contact-closure
> cable" "liebert" (I copied it from your previous mail)
> So please help me,where should I start it ?
>
> |Thank you for all your help
the device you're mentioning above is already supported.
but you might be referring to a newer GTX2 ESP-II.
interestingly, there was a thread recently revived on this:
http://lists.alioth.debian.org/pipermail/nut-upsuser/2009-October/005529.html
there is a link pointing to some work done:
http://www.csc.liv.ac.uk/~greg/projects/liebertserial/
tell me back if you're willing to work on this,...
2010 May 20
1
Liebert driver with usb to serial converter cable
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 --------------
An HTML attachment was scrubbed.....
2009 Jan 26
1
ups emerson liebert GTX2 ESP-II serial protocol demo
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,
2010 Apr 02
7
Liebert GXT2 NUT driver
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