-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Has anyone used nut with a XPCC UPS, in particular one of the XVRT units? Their supplied monitoring tool "works", but I'd really prefer to use nut if possible. I've systematically gone through each of the drivers in /lib/nut and none seem to talk with the unit properly. I'll be talking with a XPCC support person tomorrow, though I suspect he'll punt it back to me when it comes to my nut driver problem. - -jeff -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAks3tWIACgkQMfiP4rwHDZywLACffAQQvhrkW9m9PcUEfBRSkDji QdIAnRx4v2TVAgWtwaq/J/egTp2X7PMA =0v7G -----END PGP SIGNATURE-----
On Dec 27, 2009, at 2:28 PM, Jeffrey B. Green wrote:> I'll be talking with a XPCC support person tomorrow, though I suspect > he'll punt it back to me when it comes to my nut driver problem.I don't know anything about XPCC, but if you do get in touch with them, you could see if they suggest any third-party monitoring software, as a quick look around their website currently doesn't turn up a link to their recommended UPSMON tool.
OK Jeff,> Kjell Claesson wrote: > > Then if you can check the speed on the port. The powercom driver is using > > 1200 b/s. > > % stty -F /dev/ttyS0 > speed 1200 baud; line = 0; > min = 0; time = 0; > ignbrk -brkint -icrnl -imaxbel > -opost -onlcr > -isig -icanon -echo -echoe -echok -echoctl -echoke >Disregard my string in the latest mail. This is not the powercom ups answer. I was on the wrong track. But the answer your ups is giving, looks like you have a powercom protocol. But it is not recognized by the driver. The default for the driver is Trust ups and it sends 11 bytes. Yours is sending 16. So check the manual page for the powercom driver, and check if you can make it talk to it. Problem is that it may use some odd calculations for the voltage and load and frequency. /Kjell
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Kjell Claesson wrote:> Jeff, >> The previous values were under load, which I forgot to mention. It has a >> ~500W server and 10W switch on it. >> > > Then the ups.load is low also. > But you should not do the LB shutdown test with the server attached. > It may power off without a warning.The unloaded switch gives: % upsc xtreme battery.charge: 98.1 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: 59.53 input.voltage: 104.4 input.voltage.nominal: 120 output.frequency: 59.53 output.voltage: 105.2 ups.load: 0.2 ups.mfr: XPCC ups.model: XVRT-1000 ups.model.type: KIN1500AP ups.serial: Unknown ups.status: OL Flipping the on/off switch on a power strip gives: % upsc xtreme battery.charge: 204.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: 19.1 ups.load: -0.4 ups.mfr: XPCC ups.model: XVRT-1000 ups.model.type: KIN1500AP ups.serial: Unknown ups.status: OB -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAks6TxwACgkQMfiP4rwHDZwN5QCghoJ1xH/IBT5/YXB9kjWj4Qh2 Xv4An3eHyK036D77P3uJFHq8oAEcA04H =jQe+ -----END PGP SIGNATURE-----
Kjell Claesson wrote:>> The previous values were under load, which I forgot to mention. It has a >> ~500W server and 10W switch on it. >> > > Then the ups.load is low also. > But you should not do the LB shutdown test with the server attached. > It may power off without a warning.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