[Nut-upsdev] Liebert GXT2 NUT driver - patch, multiple fixes

[Richard Gregory]

This mornings svn 2432 produces reasonable output on a 3KW GXT2, no 
extra scaling required. upsc output below.

Comparing the current command sequences to those of Spiros obtained, 
input.voltage is actually the bypass voltage. Spiros, did you find the 
input voltage command?


Richard

+--                               --+
|  Biological Sciences, Room 231    |
|  http://www.csc.liv.ac.uk/~greg   |
+--                               --+

battery.charge: 90
battery.current: 0.00
battery.runtime: 660
battery.voltage: 80.8
battery.voltage.nominal: 82.8
device.mfr: Liebert
device.model: GXT2-3000RT230
device.serial: 0228100092AF491
device.type: ups
driver.name: liebert-esp2
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/ttyS0
driver.version: 2.4.3
driver.version.internal: 0.02
input.bypass.voltage: 231.8
input.frequency: 49.9
input.frequency.nominal: 49.9
input.voltage: 233.2
output.current: 5.6
output.frequency: 49.9
output.voltage: 230.4
ups.firmware: GXT2MR15D-2K3K
ups.load: 57
ups.mfr: Liebert
ups.mfr.date: 07OCT02
ups.model: GXT2-3000RT230
ups.power: 1314
ups.power.nominal: 3000
ups.realpower: 1206
ups.serial: 0228100092AF491
ups.status: OL
ups.temperature: 35.0


Arjen de Korte wrote:
> Citeren Spiros Ioannou <sivann at gmail.com>:
> 
>> 1) new way to initialize model, firmware etc. variables, the strok way
>> failed because some vars had spaces. (e.g. model "Liebert NX")
> 
> Thanks for this patch. I adopted this idea and committed a slightly  
> modified version to the development version.
> 
>> 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.
> 
> I would like to get some upsc output (latest development version, no  
> patches) from Liebert NX and GXT2 owners before committing this. I'm  
> not quite sure we got everything right now. Check *all* returned  
> values from the upsc output if they are reasonable. If not, provide  
> the debug output (-DDD) as well to see the raw output from the UPS.
> 
>> 3) added battery temperature
> 
> Committed, thanks.
> 
>> 4) removed battery.charge. BATTERY_CAPACITY != charge, BATTERY_CAPACITY
>> means how much the battery has lost its original energy capacity from aging.
> 
> Same as the above.
> 
> Note that we prefer to break up patches to contain only a single  
> modification. So it would have been better to break up this change in  
> four patches, each changing one of the above.
> 
> I also noticed you changed the 'ups.temperature' to  
> 'ambient.temperature'. Note that this change requires an external  
> sensor to be attached to the UPS, otherwise we consider this to be the  
> device (UPS) temperature.
> 
> Best regards, Arjen