Tmima Pliroforikis Perifereiakis Enotitas Pierias
2012-May-10 07:11 UTC
[Nut-upsuser] battery.charge and other fixes needed for X-Power Tigra 1kVA
Hello all,
been 5 years since I posted on this list, glad to be back :)
I have a number of X-power Tigra 1kVA online UPS units. From some
knowledgeable folks working for the local distributor, I learnt that
from inside this looked like a Best 610 ups unit.
Before, I had this UPS hooked via serial to my Windows 2003 server. For
monitoring, some winpilot/upspilot software was also provided. This
software produced also a csv format log (upsdata.csv) that contained the
following lines:
05/10/2012,07:36:56,COM1,ON-LINE,1,225,999,999,231,999,999,041.1,50.0,035,029
05/10/2012,07:37:56,COM1,ON-LINE,1,225,999,999,231,999,999,041.1,50.0,036,029
05/10/2012,07:38:56,COM1,ON-LINE,1,225,999,999,231,999,999,041.1,50.0,036,029
05/10/2012,07:39:56,COM1,ON-LINE,1,225,999,999,231,999,999,041.1,50.0,036,029
05/10/2012,07:40:56,COM1,ON-LINE,1,225,999,999,231,999,999,041.1,50.0,035,029
05/10/2012,07:41:57,COM1,ON-LINE,1,225,999,999,231,999,999,041.1,50.0,036,030
05/10/2012,07:42:57,COM1,ON-LINE,1,224,999,999,231,999,999,041.1,50.0,036,030
05/10/2012,07:43:57,COM1,ON-LINE,1,225,999,999,229,999,999,041.1,50.0,036,030
05/10/2012,07:44:57,COM1,ON-LINE,1,225,999,999,231,999,999,041.1,50.0,036,030
05/10/2012,07:45:57,COM1,ON-LINE,1,225,999,999,231,999,999,041.1,50.0,035,030
So I disabled this bundled software and installed the windows version
NUT-Installer-2.6.3-3.msi, without the libusb option (since I had a
serial UPS)
In ups.conf I used the following
[ups1]
driver = bestups
port = com1
id = 610,1000,230,230,10.0,36.0
nombattvolt=41.1
battvoltmult = 18
With regard to the id option, the 2nd, 3rd and 4th options seemed ok.
Not sure about the fifth (10.0). And definitely not sure about the last
(36.0). I used 36.0 because the Best 610-1000 lists 36V as the DC bus
voltage. Not sure if that is correct or not. According to specs (
http://www.lexis.gr/upload/File/ProductBrochures/XPower/Tigrablack.pdf )
this Xpower ups has three (3) 12V batteries.
I used nombattvolt 41.1 since that seemed to be similar also to the Best
610-1000. As for battvoltmult, I must say I also experimented here.
The bestups driver seems to run ok:
C:\PROGRA~1\NUT\bin>bestups.exe -DDDDDDD -a ups1
Network UPS Tools - Best UPS driver 1.06 (2.6.3-3534:3545M)
0.000000 send_to_all: SETINFO driver.parameter.port "com1"
0.000000 send_to_all: SETINFO driver.parameter.id
"610,1000,230,230,10.0,36.0"
0.000000 send_to_all: SETINFO driver.parameter.nombattvolt
"41.1"
0.015625 send_to_all: SETINFO driver.parameter.battvoltmult
"18"
0.015625 debug level is '7'
0.015625 w32_serial_open (com1)
0.015625 setting initial state on com1
0.015625 000007AC = w32_serial_open (com1)
0.015625 Warning: no locking method is available: No error [The
operation completed successfully. ]
0.015625 vmin_ 0, vtime_ 0
0.109376 action 0
0.109376 vtime 0, vmin 1
0.125002 ReadTotalTimeoutConstant -2, ReadIntervalTimeout -1,
ReadTotalTi
meoutMultiplier -1
0.125002 send_to_all: SETINFO device.type "ups"
0.125002 send_to_all: SETINFO driver.version
"2.6.3-3534:3545M"
0.125002 send_to_all: SETINFO driver.version.internal "1.06"
0.125002 send_to_all: SETINFO driver.name "bestups"
0.328129 w32_serial_read : ulen 64, vmin_ 1, vtime_ 0, hEvent
000007A8
0.328129 w32_serial_read : Reading 8 characters
0.328129 w32_serial_read : total characters read = 8
0.328129 w32_serial_read : ulen 64, vmin_ 1, vtime_ 0, hEvent
000007A8
0.343754 w32_serial_read : characters are available on input buffer
0.343754 w32_serial_read : Reading 1 characters
0.359380 w32_serial_read : total characters read = 1
0.359380 w32_serial_read : Reading 7 characters
0.359380 w32_serial_read : total characters read = 8
0.359380 w32_serial_read : ulen 64, vmin_ 1, vtime_ 0, hEvent
000007A8
0.359380 w32_serial_read : characters are available on input buffer
0.359380 w32_serial_read : Reading 1 characters
0.390630 w32_serial_read : total characters read = 1
0.390630 w32_serial_read : Reading 7 characters
0.390630 w32_serial_read : total characters read = 8
0.390630 w32_serial_read : ulen 64, vmin_ 1, vtime_ 0, hEvent
000007A8
0.390630 w32_serial_read : characters are available on input buffer
0.390630 w32_serial_read : Reading 1 characters
0.421880 w32_serial_read : total characters read = 1
0.421880 w32_serial_read : Reading 7 characters
0.421880 w32_serial_read : total characters read = 8
0.421880 w32_serial_read : ulen 64, vmin_ 1, vtime_ 0, hEvent
000007A8
0.421880 w32_serial_read : characters are available on input buffer
0.421880 w32_serial_read : Reading 1 characters
0.453131 w32_serial_read : total characters read = 1
0.453131 w32_serial_read : Reading 7 characters
0.453131 w32_serial_read : total characters read = 8
0.453131 w32_serial_read : ulen 64, vmin_ 1, vtime_ 0, hEvent
000007A8
0.453131 w32_serial_read : characters are available on input buffer
0.468756 w32_serial_read : Reading 1 characters
0.500006 w32_serial_read : total characters read = 1
0.500006 w32_serial_read : Reading 6 characters
0.500006 w32_serial_read : total characters read = 7
0.500006 NOTE: using user-supplied ID response
0.500006 send_to_all: SETINFO input.voltage.nominal "230"
0.500006 send_to_all: SETINFO output.voltage.nominal "230"
0.515632 send_to_all: SETINFO ups.mfr "Best Power"
0.515632 send_to_all: SETINFO ups.model "610 1000"
0.515632 send_to_all: SETINFO battery.voltage.nominal "216"
Detected Best Power 610 1000 on com1
0.609383 send_to_all: ADDCMD test.battery.start
0.625008 send_to_all: ADDCMD test.battery.stop
1.015638 w32_serial_read : ulen 64, vmin_ 1, vtime_ 0, hEvent
000007A8
1.031263 w32_serial_read : Reading 51 characters
1.031263 w32_serial_read : total characters read = 51
1.031263 Communications with UPS lost: Poll failed: short read
(got 3 bytes)
1.031263 dstate_init: sock \\.\pipe\bestups-ups1 open on fd 1956
1.031263 send_to_all: SETINFO driver.parameter.pollinterval
"2"
1.031263 send_to_all: SETINFO device.mfr "Best Power"
1.031263 send_to_all: SETINFO device.model "610 1000"
1.437518 w32_serial_read : ulen 64, vmin_ 1, vtime_ 0, hEvent
000007A8
1.437518 w32_serial_read : Reading 47 characters
1.437518 w32_serial_read : total characters read = 47
1.437518 Communications with UPS re-established
1.453144 send_to_all: SETINFO battery.voltage "41.0"
1.453144 send_to_all: SETINFO input.voltage "226.5"
1.453144 send_to_all: SETINFO output.voltage "230.7"
1.453144 send_to_all: SETINFO ups.load "035"
1.453144 send_to_all: SETINFO input.frequency "50.0"
1.453144 send_to_all: SETINFO ups.temperature "34.0"
1.453144 send_to_all: SETINFO battery.charge "-24.8"
1.453144 send_to_all: SETINFO ups.status "OL"
1.453144 send_to_all: DATAOK
3.437544 w32_serial_read : ulen 64, vmin_ 1, vtime_ 0, hEvent
000007A8
3.437544 w32_serial_read : Reading 47 characters
3.437544 w32_serial_read : total characters read = 47
My questions are:
1) Any ideas on why battery.charge is set to -24.8 (note also the
negative sign)
2) Anything else that should be corrected in ups.conf, in your opinion?
3) Regardless if the battery.charge is correct, will the system shutdown
when battery charge is low?
4) In my FreeBSD installations, ups.log is written as a log, anything
similar for Windows?
I understand that this is a large number of questions, please accept my
apologies in advance.
With kind regards,
Michail.-
Frédéric Bohé
2012-May-10 07:57 UTC
[Nut-upsuser] battery.charge and other fixes needed for X-Power Tigra 1kVA
Hello Michail, On Thu, 2012-05-10 at 10:11 +0300, Tmima Pliroforikis Perifereiakis Enotitas Pierias wrote:> Hello all, > > been 5 years since I posted on this list, glad to be back :) > > I have a number of X-power Tigra 1kVA online UPS units. From some > knowledgeable folks working for the local distributor, I learnt that > from inside this looked like a Best 610 ups unit. > > Before, I had this UPS hooked via serial to my Windows 2003 server. For > monitoring, some winpilot/upspilot software was also provided. This > software produced also a csv format log (upsdata.csv) that contained the > following lines: > > 05/10/2012,07:36:56,COM1,ON-LINE,1,225,999,999,231,999,999,041.1,50.0,035,029 > 05/10/2012,07:37:56,COM1,ON-LINE,1,225,999,999,231,999,999,041.1,50.0,036,029 > 05/10/2012,07:38:56,COM1,ON-LINE,1,225,999,999,231,999,999,041.1,50.0,036,029 > 05/10/2012,07:39:56,COM1,ON-LINE,1,225,999,999,231,999,999,041.1,50.0,036,029 > 05/10/2012,07:40:56,COM1,ON-LINE,1,225,999,999,231,999,999,041.1,50.0,035,029 > 05/10/2012,07:41:57,COM1,ON-LINE,1,225,999,999,231,999,999,041.1,50.0,036,030 > 05/10/2012,07:42:57,COM1,ON-LINE,1,224,999,999,231,999,999,041.1,50.0,036,030 > 05/10/2012,07:43:57,COM1,ON-LINE,1,225,999,999,229,999,999,041.1,50.0,036,030 > 05/10/2012,07:44:57,COM1,ON-LINE,1,225,999,999,231,999,999,041.1,50.0,036,030 > 05/10/2012,07:45:57,COM1,ON-LINE,1,225,999,999,231,999,999,041.1,50.0,035,030 > > > So I disabled this bundled software and installed the windows version > NUT-Installer-2.6.3-3.msi, without the libusb option (since I had a > serial UPS) > > In ups.conf I used the following > > [ups1] > driver = bestups > port = com1 > id = 610,1000,230,230,10.0,36.0 > nombattvolt=41.1 > battvoltmult = 18 > > With regard to the id option, the 2nd, 3rd and 4th options seemed ok. > Not sure about the fifth (10.0). And definitely not sure about the last > (36.0). I used 36.0 because the Best 610-1000 lists 36V as the DC bus > voltage. Not sure if that is correct or not. According to specs ( > http://www.lexis.gr/upload/File/ProductBrochures/XPower/Tigrablack.pdf ) > this Xpower ups has three (3) 12V batteries. > > I used nombattvolt 41.1 since that seemed to be similar also to the Best > 610-1000. As for battvoltmult, I must say I also experimented here. > > The bestups driver seems to run ok: > > C:\PROGRA~1\NUT\bin>bestups.exe -DDDDDDD -a ups1 > Network UPS Tools - Best UPS driver 1.06 (2.6.3-3534:3545M) > 0.000000 send_to_all: SETINFO driver.parameter.port "com1" > 0.000000 send_to_all: SETINFO driver.parameter.id > "610,1000,230,230,10.0,36.0" > 0.000000 send_to_all: SETINFO driver.parameter.nombattvolt "41.1" > 0.015625 send_to_all: SETINFO driver.parameter.battvoltmult "18" > 0.015625 debug level is '7' > 0.015625 w32_serial_open (com1) > 0.015625 setting initial state on com1 > 0.015625 000007AC = w32_serial_open (com1) > 0.015625 Warning: no locking method is available: No error [The > operation completed successfully. ] > 0.015625 vmin_ 0, vtime_ 0 > 0.109376 action 0 > 0.109376 vtime 0, vmin 1 > > 0.125002 ReadTotalTimeoutConstant -2, ReadIntervalTimeout -1, > ReadTotalTi > meoutMultiplier -1 > 0.125002 send_to_all: SETINFO device.type "ups" > 0.125002 send_to_all: SETINFO driver.version "2.6.3-3534:3545M" > 0.125002 send_to_all: SETINFO driver.version.internal "1.06" > 0.125002 send_to_all: SETINFO driver.name "bestups" > 0.328129 w32_serial_read : ulen 64, vmin_ 1, vtime_ 0, hEvent > 000007A8 > 0.328129 w32_serial_read : Reading 8 characters > 0.328129 w32_serial_read : total characters read = 8 > 0.328129 w32_serial_read : ulen 64, vmin_ 1, vtime_ 0, hEvent > 000007A8 > 0.343754 w32_serial_read : characters are available on input buffer > 0.343754 w32_serial_read : Reading 1 characters > 0.359380 w32_serial_read : total characters read = 1 > 0.359380 w32_serial_read : Reading 7 characters > 0.359380 w32_serial_read : total characters read = 8 > 0.359380 w32_serial_read : ulen 64, vmin_ 1, vtime_ 0, hEvent > 000007A8 > 0.359380 w32_serial_read : characters are available on input buffer > 0.359380 w32_serial_read : Reading 1 characters > 0.390630 w32_serial_read : total characters read = 1 > 0.390630 w32_serial_read : Reading 7 characters > 0.390630 w32_serial_read : total characters read = 8 > 0.390630 w32_serial_read : ulen 64, vmin_ 1, vtime_ 0, hEvent > 000007A8 > 0.390630 w32_serial_read : characters are available on input buffer > 0.390630 w32_serial_read : Reading 1 characters > 0.421880 w32_serial_read : total characters read = 1 > 0.421880 w32_serial_read : Reading 7 characters > 0.421880 w32_serial_read : total characters read = 8 > 0.421880 w32_serial_read : ulen 64, vmin_ 1, vtime_ 0, hEvent > 000007A8 > 0.421880 w32_serial_read : characters are available on input buffer > 0.421880 w32_serial_read : Reading 1 characters > 0.453131 w32_serial_read : total characters read = 1 > 0.453131 w32_serial_read : Reading 7 characters > 0.453131 w32_serial_read : total characters read = 8 > 0.453131 w32_serial_read : ulen 64, vmin_ 1, vtime_ 0, hEvent > 000007A8 > 0.453131 w32_serial_read : characters are available on input buffer > 0.468756 w32_serial_read : Reading 1 characters > 0.500006 w32_serial_read : total characters read = 1 > 0.500006 w32_serial_read : Reading 6 characters > 0.500006 w32_serial_read : total characters read = 7 > 0.500006 NOTE: using user-supplied ID response > 0.500006 send_to_all: SETINFO input.voltage.nominal "230" > 0.500006 send_to_all: SETINFO output.voltage.nominal "230" > 0.515632 send_to_all: SETINFO ups.mfr "Best Power" > 0.515632 send_to_all: SETINFO ups.model "610 1000" > 0.515632 send_to_all: SETINFO battery.voltage.nominal "216" > Detected Best Power 610 1000 on com1 > 0.609383 send_to_all: ADDCMD test.battery.start > 0.625008 send_to_all: ADDCMD test.battery.stop > 1.015638 w32_serial_read : ulen 64, vmin_ 1, vtime_ 0, hEvent > 000007A8 > 1.031263 w32_serial_read : Reading 51 characters > 1.031263 w32_serial_read : total characters read = 51 > 1.031263 Communications with UPS lost: Poll failed: short read > (got 3 bytes) > 1.031263 dstate_init: sock \\.\pipe\bestups-ups1 open on fd 1956 > 1.031263 send_to_all: SETINFO driver.parameter.pollinterval "2" > 1.031263 send_to_all: SETINFO device.mfr "Best Power" > 1.031263 send_to_all: SETINFO device.model "610 1000" > 1.437518 w32_serial_read : ulen 64, vmin_ 1, vtime_ 0, hEvent > 000007A8 > 1.437518 w32_serial_read : Reading 47 characters > 1.437518 w32_serial_read : total characters read = 47 > 1.437518 Communications with UPS re-established > 1.453144 send_to_all: SETINFO battery.voltage "41.0" > 1.453144 send_to_all: SETINFO input.voltage "226.5" > 1.453144 send_to_all: SETINFO output.voltage "230.7" > 1.453144 send_to_all: SETINFO ups.load "035" > 1.453144 send_to_all: SETINFO input.frequency "50.0" > 1.453144 send_to_all: SETINFO ups.temperature "34.0" > 1.453144 send_to_all: SETINFO battery.charge "-24.8" > 1.453144 send_to_all: SETINFO ups.status "OL" > 1.453144 send_to_all: DATAOK > 3.437544 w32_serial_read : ulen 64, vmin_ 1, vtime_ 0, hEvent > 000007A8 > 3.437544 w32_serial_read : Reading 47 characters > 3.437544 w32_serial_read : total characters read = 47 > > > My questions are: > > 1) Any ideas on why battery.charge is set to -24.8 (note also the > negative sign) > > 2) Anything else that should be corrected in ups.conf, in your opinion? > > 3) Regardless if the battery.charge is correct, will the system shutdown > when battery charge is low? > > 4) In my FreeBSD installations, ups.log is written as a log, anything > similar for Windows?You can see NUT logs in the Windows' Event Viewer. Regards, Fred> > I understand that this is a large number of questions, please accept my > apologies in advance. > > With kind regards, > > > Michail.- > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser-- Eaton Opensource Team - http://opensource.eaton.com --------------------------------------------------------------------------
Charles Lepple
2012-May-10 12:17 UTC
[Nut-upsuser] battery.charge and other fixes needed for X-Power Tigra 1kVA
On May 10, 2012, at 3:11 AM, Tmima Pliroforikis Perifereiakis Enotitas Pierias wrote:> 1) Any ideas on why battery.charge is set to -24.8 (note also the negative sign)The "bestups" driver does not have a lot of debugging information, and when that driver was written, it was also not possible to anticipate the wide range of products which would use this protocol. I think it is worth trying the "blazer_ser" driver (which theoretically works with a superset of the Best UPS protocols). If nothing else, it should provide some more information on the strings returned by the UPS, so it might be easier to see where that negative number is coming from.> 3) Regardless if the battery.charge is correct, will the system shutdown when battery charge is low?It should, since the "on battery" and "battery low" states are, by default, signaled by status bits directly from the UPS (not from any calculations in the driver). But I recommend testing the UPS with a dummy load (like a lamp) to be sure. -- Charles Lepple clepple at gmail
Frédéric Bohé
2012-May-14 12:16 UTC
[Nut-upsuser] battery.charge and other fixes needed for X-Power Tigra 1kVA
On Mon, 2012-05-14 at 13:20 +0300, Tmima Pliroforikis Perifereiakis Enotitas Pierias wrote:> Hello Frederic, > > Fr?d?ric Boh? wrote: > > [snip] > >> And some more questions: > >> > >> 1) Upon reception of a shutdown command, my server takes approx. 60" for > >> shutdown. Can I set on this Windows server the ups itself to power down > >> after say 90"? According to the upsc output above, the ups has set > >> ups.delay.shutdown to 30". By adding offdelay = 120 (from the docs it > >> seems that offdelay values> 60" are rounded to multiples of 60") in > >> ups.conf or by other means will NUT as part of the shutdown procedure > >> call automatically: > >> upscmd<upsname> shutdown.return 1 > >> for it to work? Or should I insert this command somewhere to make sure > >> that the offdelay value will be respected? > > > >> From the blazer man page I see : > > > > offdelay = value > > Time to wait before shutting down the UPS (seconds). This > > value > > is truncated to units of 6 seconds (less than 60 seconds) or > > 60 > > seconds (more than 60 seconds). Defaults to 30 seconds. > > > > > > So you can try to add this to your ups.conf and see if it works. > > If the a battery low is received, the system which is connected to the > UPS initiates a shutdown successfully. However, the UPS does not power > off as configured with offdelay and it does not power up as configured > with ondelay. So it seems that a "upscmd <upsname> shutdown.return 1" > should definitely be used.Well, the blazer_ser driver should issue this command. Can you call the following command after stopping NUT (there should be no other driver running). Beware that this will likely shutdown your UPS so make sure your PC is not electrically connected to it. blazer_ser -a <ups_name> -DDDDD -k Then you can send the output to the list. Regards, Fred> > Taking into account your response about having SHUTDOWNCMD point to a > .bat file, I was considering modifying SHUTDOWNCMD to point to > myown.bat, suitibly modified to include a call to shutdown.return, as > follows: > SHUTDOWNCMD "C:\\myown.bat" > > ...where myown.bat would contain the following: > myown.bat: > =======================================> REM First start shutdown timers for UPS > <pathToUpscmc>\upscmd <upsname> shutdown.return 1 > > REM Needed sending a command to power > REM down my ESXi server elsewhere (different UPS) > SSH cmd here blah blah > > REM Finally initiate local system shutdown > C:\WINDOWS\system32\shutdown.exe -s -t 0 > =======================================> > What do you think? Any caveats I should possibly watch out? > BR, > > > Michail.- > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser-- Eaton Opensource Team - http://opensource.eaton.com --------------------------------------------------------------------------
Seemingly Similar Threads
- bug report: apcsmart (WIN) 940-0024C connect fail, problem with command 'E'
- blazer_ser problem on windows NUT 2.6.5-3780M
- blazer driver: Possible bugs with battery packs
- KIN-1500AP RM + Windows 2008 64-bit Standard R2 SP1 (nut 2.6.1)
- [windows port] blazer_ser issues, select_read() from serial semantics