Patent Application
20050149280
The invention relates to providing a means for obtaining an indication of the operational condition of a battery located at a remote location.
Batteries are used in backup situations for temporary absence of normally supplied alternating current power. While such backup batteries are used for many applications, such as emergency lighting in buildings and so forth, a substantial number of backup batteries are used in connection with the telecommunications industry. When normally supplied alternating current electric power fails, it is very important that telephones and other communication equipment remain operable. The communications equipment is typically scattered throughout the area being serviced and the number of battery sites used for backup can number in the thousands.
While useful battery life is typically from 2 to 10 years, a battery can fail suddenly at anytime. One approach to minimizing backup power failure has been to replace all backup batteries when they have been used for 2 years. Such an approach is not only expensive from a cost of battery standpoint, but is also expensive from the standpoint of the wages paid to technicians used to deliver and replace the batteries. Such an approach does not eliminate the potential problems associated with premature failure of a battery in less than 2 years.
It is known in the prior art that a visual presentation in the form of a curve can be generated illustrating the voltage of a battery, that has been placed under loaded conditions, over a period of time. If such a curve is compared with the form of a similarly generated curve from a known good battery, or alternatively with a curve previously generated from the battery under test, a reasonably good determination can be made as to the condition of the battery and thus of the likelihood of failure of the battery in the near future. It is also known that the form of the curve and the values of the curve are both temperature and load sensitive. Thus when any comparisons, of prior and present curves are made, any differences in battery temperatures and battery loads must be taken into consideration.
It is known in the prior art to install wiring from a central location to a remote set of batteries and test the batteries by loading the batteries with a precision electronic load and measuring the voltage and current under such condition. This test is known in the industry as a conductance measurement. Such a test setup is not widely used because of the cost of installation of both wiring and circuitry as well as problems of maintenance.
There is therefore a need to be able to devise a method whereby battery condition testing can be performed at each remote site under predetermined conditions and/or situations not subject to continuous supervision by a centrally situated entity. There is a further need for the capability of apparatus whereby a central entity could, at anytime, ascertain the condition of any specific battery and/or alternatively be informed by circuitry at the remote site that a given battery has a high probability of failure in the near future.
The present invention comprises using a CPU (computer or central processing unit) in combination one or more batteries at remote locations to maintain a history of battery tests that can be retrieved over a communication path by an interested entity at a different location.
For a more complete understanding of the present invention, and its advantages, reference will now be made in the following Detailed Description to the accompanying drawings, in which:
In the remainder of this description, a processing unit (PU) may be a sole processor of computations in a device. In such a situation, the PU is typically referred to as a CPU (central processing unit).
In the following discussion, numerous specific details are set forth to provide a thorough understanding of the present invention. However, those skilled in the art will appreciate that the present invention may be practiced without such specific details. In other instances, well-known elements have been illustrated in schematic or block diagram form in order not to obscure the present invention in unnecessary detail. Additionally, for the most part, details concerning network communications, electro-magnetic signaling techniques, and the like, have been omitted inasmuch as such details are not considered necessary to obtain a complete understanding of the present invention, and are considered to be within the understanding of persons of ordinary skill in the relevant art.
It is further noted that, unless indicated otherwise, all functions described herein may be performed in either hardware or software, or some combination thereof. In a preferred embodiment, however, the functions are performed by a processor, such as a computer or an electronic data processor, in accordance with code, such as computer program code, software, and/or integrated circuits that are coded to perform such functions, unless indicated otherwise.
In
Although not shown specifically, a technician at the site, represented by block 100, may have a terminal interconnected to controller 102 to provide instructions to or receive data from controller 102. Such a terminal may be connected through the network 118, such as by satellite or other means, or connected directly to controller 102.
For ease in describing the operation of the system, the switches within block 112 will be designated as 120, 122 and 124. Switch 120 is shown connected to and in series with a current measuring resistor 130 within block 110 and a battery 140 within block 108. In a similar manner, a switch 122 is connected is series with a current measuring resistor 132 and a battery 142.
The system controller 102 plays a central role in the overall battery test and management scheme. This controller 102 will typically be equipped with an intelligent processor and associated memory. This memory is represented by a sub-block within 102 labeled MEM. The controller 102 is used to initiate any battery test by sending an appropriate control signal to other system slave components such as block 104, 108, 110, 112 and 114 via communication links designated as 148, 150 and 152. For the duration of any test, the controller 102 receives data or information from the slave devices through one of the illustrated system communication buses. The system controller 102 processes this information in real time for calculation of various battery performance related parameters. The controller 102 also communicates with one or more remote monitoring stations, shown as block 120, via the user's network 118 in real time. The controller 102 can also store certain information in controller memory (not specifically shown) for future access by a local or remote terminal. In addition, the controller 102 can abort or stop the test based on the occurrence of certain pre-defined conditions detected during the test. These conditions include, completion of test time, occurrence of any system alarm including those generated by the test, or user abort from the local or remote terminal.
The rectifier block 104 typically comprises several AC/DC converters other wise known as rectifiers. These rectifiers, typically in combination with a smoothing filter, convert the incoming AC input line to an isolated DC output. The value of the output DC voltage will normally be of a value which will be adequate for powering the electronic equipment represented by block 106. In addition to that, the rectifier block 104 normally provides a continuous charge current to the batteries 108. The system output voltage is maintained at a level to provide adequate charging of the batteries with out causing any undesirable stress to the batteries. This set point voltage level is also known a “float” voltage. Under normal conditions, the system controller 102 supplies a command to the rectifier block 104 to set the appropriate float voltage and monitors for any special condition existing in them. At the beginning of the battery test, the system controller 102 operates to set the output voltage of the rectifier block 104 at a level, which is considerably lower than the level at which the batteries were floating. This lower voltage setpoint forces the batteries 108 to take over the system load. The testing will normally be of a specific battery such as 142. In such a situation, the switches 120 and 124 will be commanded to open and the switch 122 will be closed. This starts the battery discharge cycle for the battery test of battery 142. Because the rectifier 104 is still providing an output voltage, although at a lower than normal level, the system load 106 is not exposed to the possibility of losing DC power in the event of a catastrophic problem such as the battery 142 being damaged to the extent that it cannot support the load.
The battery monitoring unit 114 operates to continuously monitor certain battery parameters such as battery voltage and current. The information obtained during the monitoring operation is provided to the system controller 102 during battery test for further processing, storage, and transmission to the remote terminal(s) represented by block 120. In addition to monitoring, the battery control unit can disconnect any or all battery strings, of block 108, from the system load 106 though the disconnect switches or contactor shown in block 112.
The system load block 106 represents the naturally occurring load on the DC power plant or rectifier 104. The battery discharge test utilizes the load represented by block 106 to “load” or discharge the batteries for a pre-defined time. This test is used to ascertain a battery parameter known in the art as a measurement of “amp-hour” capacity. As will be realized, the system load can vary during different hours of operation of the system. Thus a preferable time to perform any battery testing is during a period when past history has shown the system load to be fairly uniform.
As indicated previously, the discharge pattern of a battery will vary based on the state of the battery cells. Further, environmental factors such as battery temperature and instantaneous current drawn will have an effect on the discharge pattern of the battery being tested. Thus the system controller 102 must be equipped to be informed to various conditions during the test and compensate for these factors when attempting to ascertain the condition of the battery for which testing has just been completed.
To minimize the load on the network, the controller 102 will typically retain a history of the discharge pattern of each battery at a given remote location. Such a history will facilitate the determination of whether the battery is approaching a state wherein the battery tested is likely to fail in the near future.
Referring now to
After a new remote agent is accepted in a block 210, existing BDT history is sent to the agent in accordance with the step of block 210. The next step, in a decision block 215, is to ascertain if a BDT is presently active. In other words, “is a test presently being performed?” If yes, the BDT data presently being obtained is synchronized with any new remote agent(s). The next step, beyond block 220, is to input A of
A decision block 250 represents the interpretation of two additional commands that may be received from a remote agent. An abort BDT command would cause the software to send a STOP BDT command to the BDT controller as set forth in a block 255. The command is sent to a B input of
A start BDT command, from a remote agent, would cause a test ID# to be assigned as set forth in a block 260 and prepare all remote agents to receive data for this new test as set forth in a block 265. A start BDT command would be sent to the controller 102, from a block 270 to an A input of
Reference will now be made to the controller software steps of
A check is made, in a decision block 320, as to whether or not one or more remote agents 120 are active and wish to receive the data being generated. If not, a monitoring step represented by a block 325 is entered. The step 325 is essentially the same as the step of block 305. Then a determination is made, in block 320, that one or more remote agents are active, data is sent to the remote agent as set forth in a block 330, as it is being generated or at the completion of the test in accordance with software design or request of the remote agent operator. A decision block 335 maintains a check on the BDT activity and maintains a closed loop back through the block 315 for the duration of the test. It may be noted that the BDT status step of block 325 may also be entered from block 255 of
When BDT activity ceases, due to completion of the test or termination at the request of a remote agent, the process proceeds to a block 405 to capture or retrieve all the stored data for the most recent test. As set forth in a block 410, a history list, of all recently performed tests whose data is still contained in memory, is updated. A check is then made, in a decision block 415, to ascertain if any remote agents 120 are presently active. If not, the controller software returns to monitoring any BDT status in block 305. On the other hand, if the remote agent is still active, the BDT results are sent to the remote agent, as set forth in a block 420. Then, as set forth in a block 425, an updated BDT history list is sent to the remote agent before returning to block 225 of
Although not specifically shown, in a preferred embodiment, the controller box 100 at a battery site will include a switch or other manually operated means for an on site technician to activate a BDT with using a remote agent computer terminal. The controller box will also have an output signal or display to inform the technician whether the BDT ascertained the batteries to be good or to have failed the test.
If a failure indication is provided in response to a manually activated test, the technician may request further testing, via a remote agent terminal, to obtain more information as to which battery has failed or alternatively a graphical display of the specific data that resulted in the failure indication.
A given history item comprises a set of data including temperature of the batteries at the time of the BDT, the current being drawn by load 106 and a series of battery voltages and the time from the start of the BDT that the battery voltage was ascertained. In
A curve 520 represents a graph of a depleted battery that needs to be replaced. The voltage of the depleted battery drops far below the rated value of the battery as soon as a load is applied. As set forth above, the load is applied by dropping the voltage output by rectifier 104 to a given standby voltage. As shown, the initial drop of the depleted battery is to about 45.5 volts after about 50 seconds. Rather than rising sharply, the output voltage of a depleted battery either rises minimally or does rise at all. As shown, the battery represented by curve 520 rises to 46 volts after about 1000 seconds and then declines rapidly to the predetermined set value of 44 volts after about 2300 seconds. For the purposes of illustration, the curve is shown proceeding to the 40 volt output of rectifier 104 at about 4600 seconds.
The criteria used for replacing a battery can be set to any of various factors or parameters. It can be the time for it to reach the predetermined minimum, taking into account the temperature and load current for a given test. As may be noted the decaying voltage slope for the battery represented by curve 520 is much steeper than the good battery from 1000 seconds until the set voltage of 44 volts is reached. Thus the slope of battery voltage over time can be used. Also the voltage after a nominal time into the test, such as 200 seconds can be used as an indication of when to replace batteries. All of the aforementioned criteria may be used separately or in some combination for used or supposedly good or new batteries. If a battery being tested has a history of tests stored in the MEM section of controller 102, the decline in voltage from any previous test may also be used in ascertaining that a given battery needs to be replaced.
In summary, the system controller 102, in each the remote locations, periodically tests each of the battery strings in block 108. This test is referred to above as a BDT. A BDT will typically be performed on some type of schedule such as daily, weekly or monthly.
A discharge curve obtained, as a result of the BDT, is compared with previously obtained curves, stored in the memory portion of controller 102, as well as compared to a standardized curve for batteries of this type. Compensation is made for environmental conditions that will affect the discharge curve such as temperature of the battery. The data obtained in each series of tests is transmitted through network 118 to a centralized data storage block 122. The controller 102 will also run a test when the battery monitor detects an anomaly such as a sudden change in current to an individual battery string. Such a change may be due to an open condition in a cell or a shorted condition in a cell. When one or more battery strings in block 108 is ascertained to have a discharge curve falling outside predetermined parameters, the controller 102 transmits this information to an administrator at a centrally located computer workstation 120. This information is also available to any other remote agent that is presently actively connected to the controller 102 at a specific battery site 100. The administrator user at workstation may request more tests or may simply dispatch a technician to the site of the failed battery to replace same.
It may be noted that when the test is performed in response to an internal schedule, the results are merely stored in memory and a history list is updated unless the controller software detects that one or more remote agent(s) are actively connected and communicating with the remote battery site controller. When the controller software detects that a remote agent is active, whether or not the remote agent has specifically requested a BDT, the latest BDT data is supplied to the remote agent as well as the most recent history list.
As mentioned above, the remote agent may also abort a presently running BDT, delete specific BDTs from the battery site controller memory and retrieve data relating to specific prior BDTs. After retrieval of BDT data, software on the remote agent computer may be used to display the data in graph form whereby action may be initiated to minimize any battery problems that could occur at the battery site.
Although the invention has been described with reference to a specific embodiment, the description is not meant to be construed in a limiting sense. Various modifications of the disclosed embodiment, as well as alternative embodiments of the invention, will become apparent to persons skilled in the art upon reference to the description of the invention. It is therefore contemplated that the claims will cover any such modifications or embodiments that fall within the true scope and spirit of the invention.
