[Nut-upsuser] XPCC XVRT-1000 driver
Kjell Claesson
kjell.claesson at epost.tidanet.se
Wed Dec 30 01:22:59 UTC 2009
OK.
> The readings just before the nut initiated server shutdown due to LB was:
>
> % upsc xtreme
> battery.charge: 47.9
> driver.name: powercom
> driver.parameter.linevoltage: 120
> driver.parameter.manufacturer: XPCC
> driver.parameter.modelname: XVRT-1000
> driver.parameter.pollinterval: 2
> driver.parameter.port: /dev/ttyS0
> driver.parameter.type: KIN1500AP
> driver.version: 2.2.2
> driver.version.internal: $ Revision: 0.5 $
> input.frequency: 0.00
> input.voltage: 0.0
> input.voltage.nominal: 120
> output.frequency: 59.53
> output.voltage: 13.3
> ups.load: 85.5
> ups.mfr: XPCC
> ups.model: XVRT-1000
> ups.model.type: KIN1500AP
> ups.serial: Unknown
> ups.status: FSD OB LB BOOST
>
>
> The battery.charge dropped in increments of 5.0.
>
> It started at:
>
> % upsc xtreme
> battery.charge: 146.9
> driver.name: powercom
> driver.parameter.linevoltage: 120
> driver.parameter.manufacturer: XPCC
> driver.parameter.modelname: XVRT-1000
> driver.parameter.pollinterval: 2
> driver.parameter.port: /dev/ttyS0
> driver.parameter.type: KIN1500AP
> driver.version: 2.2.2
> driver.version.internal: $ Revision: 0.5 $
> input.frequency: 0.00
> input.voltage: 0.0
> input.voltage.nominal: 120
> output.frequency: 59.53
> output.voltage: 14.1
> ups.load: 67.1
> ups.mfr: XPCC
> ups.model: XVRT-1000
> ups.model.type: KIN1500AP
> ups.serial: Unknown
> ups.status: OB
This looks god. Status signaling is working, so now it is only the
calculation of the values returned from the ups.
The tricky thing is that you use an 'old' driver. The version of nut
is up to 2.4.1 stable. And is soon going to 2.6.x.
Your internal revision is 0.5 of the powercom driver, and it is 0.11 in
2.4.1 as I can see.
In svn trunk it is up to 0.12. And there have been changes around KIN
models in 0.8, so the new driver may give you better readings.
This need to be tested before talking to the developer list about adding
support for the XPCC.
Checked the svn and the changes to 0.12 is only structural so it would not
add any functional changes.
Is it possible for you to upgrade to nut-2.4.1 ?
/Kjell
More information about the Nut-upsuser
mailing list