Nut upsuser - Oct 2009 - 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? can you tell me the current
status
> etc?
> thank you for your help in advance.
> regards.
>
I've had no news from Spiros since the above mails...
so the status of this has not changed, at least from my point of view.

  Levente                               "Si vis pacem para
bellum!"
>
si vis libre, para proprietarum ;-)

cheers,
Arnaud
-- 
Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20091018/538c4d74/attachment.htm>

Really sorry for the silence, I found your last requests in a ton of spam
while searching for "liebert" while trying to reply to R.Gregory who
did the
initial sniffing. We changed offices and I no longer had access to both the
PC with the sources and the serial ups. I finally recovered the PC from the
old building and found inside the UPS sources.

It's not a driver but it allows to query lots of parameters. Unfortunately I
have no more access to serial UPS. Only snmp now. The code worked correctly
but it's not in a driver form.

I attach the file (upsesp2.c) and a sample output.txt I had from my ups. It
queries all parameters in a loop. If no parameter is specified, it tries to
query everything, and when it fails (no response from ups) it marks the
parameter as "not supported". In the next loop it ignores the
"not
supported" stuff.
I really hope it proves useful.

-Spiros


On Sun, Oct 18, 2009 at 5:57 PM, Arnaud Quette <arnaud.quette at
free.fr>wrote:
>
> 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? can you tell me the current
status
>> etc?
>> thank you for your help in advance.
>> regards.
>>
>
> I've had no news from Spiros since the above mails...
> so the status of this has not changed, at least from my point of view.
>
>    Levente                               "Si vis pacem para
bellum!"
>>
>
> si vis libre, para proprietarum ;-)
>
> cheers,
> Arnaud
> --
> Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops
> Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
> Debian Developer - http://www.debian.org
> Free Software Developer - http://arnaud.quette.free.fr/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20100219/c5414b0a/attachment-0001.htm>
-------------- next part --------------
BATTERY_TIME_REMAIN: 47.0
BATTERY_VOLTAGE: 260.0
BATTERY_VOLTAGE_NOMINAL: 275.0
BATTERY_CURRENT: 0.0
BATTERY_CAPACITY: 100.0
BYPASS_VOLTAGE: 232.0
MAX_LOAD: 10000.0
LOAD_WATTS: 1119.0
LOAD_VA: 1382.0
LOAD_PERCENT: 15.0
INPUT_FREQUENCY: 50.0
OUTPUT_FREQUENCY: 50.0
BYPASS_FREQUENCY: 50.0
INVERTER_TEMP: 0.0
BATTERY_TEMP: 0.0
PFC_TEMP: 0.0
AMBIENT_TEMP: 24.9
EXPECTED_RUNTIME: 47.0
OUTPUT_VOLTAGE: 230.0
OUTPUT_CURRENT: 5.0
MODEL_NAME: GXT2-10000T230
FW_VER: GXT2-00896V04
SN: 08009R0056BW932     
MANUF_DATE: 04JAN08 
PFC_ON: YES
DC_DC_CONVERTER_STATE: NO
ON_INVERTER: YES
UTILITY_STATE: NO
INRUSH_LIMIT_ON: NO
OVERTEMP_WARNING: NO
BATTERY_TEST_STATE: NO
INPUT_OVERVOLTAGE: NO
ON_BATTERY: NO
ON_BYPASS: NO
BATTERY_CHARGED: YES
BATTERY_LIFE_ENHANCER_ON: NO
REPLACE_BATTERY: NO
BOOST_ON: NO
DIAG_LINK_SET: NO
BUCK_ON: NO
UPS_OVERLOAD: NO
BAD_INPUT_FREQ: NO
SHUTDOWN_PENDING: NO
CHARGER_FAIL: NO
LOW_BATTERY: NO
OUTPUT_UNDERVOLTAGE: NO
OUTPUT_OVERVOLTAGE: NO
BAD_BYPASS_PWR: NO
CHECK_AIR_FILTER: NO
AMBIENT_OVERTEMP: NO
MAIN_CONTROL_MODULE_FAILED: NO
REDUNDANT_CONTROL_MODULE_FAILED: NO
UI_MODULE_FAILED: NO
REDUNDANT_POWER_MODULE_ALARM: NO
REDUNDANT_BATTERY_MODULE_ALARM: NO
USER_MAX_LOAD_ALARM: NO
TRANSFORMER_OVERTEMP_ALARM: NO
INTERNAL_COMMS_LOST: NO
PWR_MOD_FAILED: NO
BAT_MOD_FAILED: NO
Error getting OPTION_CARD_FAIL_1:marking as not supported
OPTION_CARD_FAIL_1 not supported on this UPS
Error getting OPTION_CARD_FAIL_2:marking as not supported
OPTION_CARD_FAIL_2 not supported on this UPS
Error getting OPTION_CARD_FAIL_3:marking as not supported
OPTION_CARD_FAIL_3 not supported on this UPS
Error getting OPTION_CARD_FAIL_4:marking as not supported
OPTION_CARD_FAIL_4 not supported on this UPS
Error getting OPTION_CARD_FAIL_5:marking as not supported
OPTION_CARD_FAIL_5 not supported on this UPS
Error getting OPTION_CARD_FAIL_6:marking as not supported
OPTION_CARD_FAIL_6 not supported on this UPS
Error getting OPTION_CARD_FAIL_7:marking as not supported
OPTION_CARD_FAIL_7 not supported on this UPS
Error getting OPTION_CARD_FAIL_8:marki
-------------- next part --------------
A non-text attachment was scrubbed...
Name: upsesp2.c
Type: application/octet-stream
Size: 16608 bytes
Desc: not available
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20100219/c5414b0a/attachment-0001.obj>

Citeren Spiros Ioannou <sivann op gmail.com>:
> I attach the file (upsesp2.c) and a sample output.txt I had from my ups. It
> queries all parameters in a loop. If no parameter is specified, it tries to
> query everything, and when it fails (no response from ups) it marks the
> parameter as "not supported". In the next loop it ignores the
"not
> supported" stuff.
> I really hope it proves useful.
In the mean time, the liebertgxt2 driver has been added to the  
development version, which will be released as the next stable  
nut-2.4.2 release in a few days time. It would be nice if you could  
try this out sometime.

A quick look at it tells me that most variables you decoded will be  
supported, but there are conflicts with some of the ones Richard  
Gregory found. Without a device to check which ones are the correct  
ones, I think we should not mess with this in the upcoming version,  
but leave that for later.

Best regards, Arjen
-- 
Please keep list traffic on the list

2010/2/19 Arjen de Korte <nut+users at
de-korte.org>:
> Citeren Spiros Ioannou <sivann at gmail.com>:
>
>> I attach the file (upsesp2.c) and a sample output.txt I had from my
ups.
>> It
>> queries all parameters in a loop. If no parameter is specified, it
tries
>> to
>> query everything, and when it fails (no response from ups) it marks the
>> parameter as "not supported". In the next loop it ignores the
"not
>> supported" stuff.
>> I really hope it proves useful.
>
> In the mean time, the liebertgxt2 driver has been added to the development
> version, which will be released as the next stable nut-2.4.2 release in a
> few days time.
a few hours!
> It would be nice if you could try this out sometime.
>
> A quick look at it tells me that most variables you decoded will be
> supported, but there are conflicts with some of the ones Richard Gregory
> found. Without a device to check which ones are the correct ones, I think
we
> should not mess with this in the upcoming version, but leave that for
later.
right, it will be for 2.6.0 now.

Arnaud