Citeren Kjell Claesson kjell.claes...@epost.tidanet.se:
Hi, do we have any active developer on the powercom driver.
As far as I know, no.
It seems to support the XPCC ups. The problem seems to be
the calculation of the voltage and ups.load.
OK, nothing essential. It would be nice to have
Kjell Claesson wrote:
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
Kjell Claesson wrote:
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
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
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kjell Claesson wrote:
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
Jeffrey B. Green wrote:
I'll experiment with the driver variable options, however, if you know
the correct (or almost correct) settings, then that info would be
greatly appreciated.
Setting the line voltage variable to 120 produces:
% upsc xtreme
battery.charge: 98.1
driver.name: powercom
Great Jeff,
Jeffrey B. Green wrote:
I'll experiment with the driver variable options, however, if you know
the correct (or almost correct) settings, then that info would be
greatly appreciated.
No my baby is the bcmxcp driver, so my knowledge in the calculations done
in the powercom
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kjell Claesson wrote:
Great Jeff,
Jeffrey B. Green wrote:
I'll experiment with the driver variable options, however, if you know
the correct (or almost correct) settings, then that info would be
greatly appreciated.
No my baby is the bcmxcp
Kjell Claesson wrote:
Then you have to make a real test. Best is to load it with some light-bulbs
as
it is going to shut off. Have the communication to the computer and load it
with the bulbs until it signals LB (Low Battery). Now check if it shutting
down properly.
Sorry about that
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.
/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
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
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles Lepple wrote:
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,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey B. Green wrote:
However, they are fairly simple tools and not configurable beyond
the command line arguments specifying the serial line and polling times.
Sorry, small correction. Not polling times, rather the breakout delay
time and the
Hi Jeff,
Jeffrey B. Green wrote:
However, they are fairly simple tools and not configurable beyond
the command line arguments specifying the serial line and polling times.
Sorry, small correction. Not polling times, rather the breakout delay
time and the UPS shutdown delay time.
This
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kjell Claesson wrote:
Hi Jeff,
Jeffrey B. Green wrote:
However, they are fairly simple tools and not configurable beyond
the command line arguments specifying the serial line and polling times.
Sorry, small correction. Not polling times, rather
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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
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
20 matches
Mail list logo
