[Nut-upsuser] XPCC XVRT-1000 driver

[Kjell Claesson]

To Arjen.
Hi, do we have any active developer on the powercom driver.
It seems to support the XPCC ups. The problem seems to be
the calculation of the voltage and ups.load.
This thread should give some info needed to make it work. 
Anything to move to dev list?
/Kjell

OK Jeff,

> Jeffrey B. Green wrote:
> >  I'll go
> > ahead and build a version of 2.4.1 for lenny (backports doesn't seem to
> > have nut in it) to see what happens...
> 
> Okay. Built it (nut 2.4.1) and put it on the server. The only type that
> works for that ups is BNT-other. When nut starts up it sees the ups on
> battery, but fairly quickly changes that to online. For example, initially:
That was fast :-)
Now see what it gives.

The startup on battery is OK. The driver is doing a battery test at start.
Don't know why they do it, but there must be a reason for that.

If type is BNT, KIN or IMP they run this.

		if (ser_send_char (upsfd, BATTERY_TEST) != 1) {
			upslogx(LOG_NOTICE, "writing error");
			dstate_datastale();
			return;
 
So it is type of detection of the right type.

> 
> % upsc xtreme
> battery.charge: 85.0
> 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: BNT-other
> driver.version: 2.4.1
> driver.version.internal: 0.12
> input.frequency: 60.09
> input.voltage: 105.2
> input.voltage.nominal: 120
> output.frequency: 60.09
> output.voltage: 18.2
> ups.load: 14.5
> ups.mfr: XPCC
> ups.model: BNT-other-0AP
> ups.model.type: BNT-other
> ups.serial: Unknown
> ups.status: OB TEST
> 
Looks OK on frequency, but input and output voltage and load seems wrong.

> 
> Then within 5-10 seconds or so,
> 
> % upsc xtreme
> battery.charge: 100.0
> 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: BNT-other
> driver.version: 2.4.1
> driver.version.internal: 0.12
> input.frequency: 60.09
> input.voltage: 103.6
> input.voltage.nominal: 120
> output.frequency: 60.09
> output.voltage: 103.6
> ups.load: 7.7
> ups.mfr: XPCC
> ups.model: BNT-other-0AP
> ups.model.type: BNT-other
> ups.serial: Unknown
> ups.status: OL
> 

The same here.
But the signaling seems OK, so it is usable for protection. But not for
reading any values from.

/Kjell