The present disclosure relates generally to power distribution systems. More particularly, the present disclosure relates to a protection system for power distribution systems.
Industrial power distribution systems commonly divide incoming power into a number of branch circuits. The branch circuits supply power to various equipment (i.e., loads) in the industrial facility. Circuit breakers are typically provided in each branch circuit to facilitate protecting equipment within the branch circuit. Circuit breakers are designed to open and close a circuit by non-automatic means and to open the circuit automatically on a predetermined over-current without damage to itself when properly applied within its rating. The circuit breakers commonly include supplementary protectors enclosed within the body of the circuit breaker. One common type of supplementary protector is known as an electronic trip unit. The circuit breaker and its supplementary protector have proven useful at managing the protection of the loads on the circuit.
However, it can be desired to integrate the load management of the branch circuits to one another. Further, it can be desired to integrate the management of the loads on the branch circuits with the management of the power feeds feeding the branch circuits. Still further, it can be desired to provide for monitoring of the system.
In order to provide this integrated protection and monitoring, prior power distribution systems have required costly and difficult to implement solutions. Today, each of these functions is performed by separate hardware often with separate sensors necessary to measure system parameters and auxiliary devices in power circuit interrupters to switch the power circuits. In such prior systems, hard wire connections between all of the electronic trip units in the system was required in order to coordinate the load control decisions of each independent trip unit with the other trip units in the system. Further, hard wire connections were also required to provide information for the independent electronic trip units to the separate system performing feed management decisions. The control decisions by the separate system performing feed management decisions is made more complex because the information from the various independent electronic trip unit is typically out of phase with one another. Additionally, another hardware device is required to then provide the desired monitoring functionality.
Accordingly, there is a continuing need for power distribution systems having a fully integrated protection system. Moreover, there is continuing need for low cost, easy to install, and easy to upgrade fully integrated protection system for power distribution systems.
In one exemplary embodiment, a protection system for a power distribution system is provided. The protection system includes a central computer, a plurality of data modules, and a data network. The data modules are each in communication with a different circuit breaker of the power distribution system. The data network communicates between the central computer and the plurality of data modules. The central computer sends an instruction to the plurality of data modules over the data network to aid in synchronization of sampling of a power condition at the plurality of data modules.
In another exemplary embodiment, a method of protecting a power distribution system is provided. The method includes sending a synchronization instruction to a plurality of data modules; sampling a power condition from the power distribution system in part based upon the synchronization instruction, each of the plurality of data modules being in communication with a different set of separable contacts in the power distribution system; transmitting a first message containing the power condition from each of the plurality of data modules to a central computer; determining a second message the central computer based upon the first message; and transmitting the second message to each of the plurality of data modules so that one or more of the plurality of data modules operates the different set of separable contacts in response to the second message.
In yet another exemplary embodiment, a power distribution system is provided. The power distribution system includes a processing unit, a first power bus, a first data module, a second data module, and a data network. The first power bus powers a first branch circuit through a first circuit breaker and a second branch circuit through a second circuit breaker. The first data module operates the first circuit breaker and samples a first parameter from the first branch circuit. Similarly, the second data operates the second circuit breaker and samples a second parameter from the second branch circuit. The data network links the first and second data modules to the processing unit. The processing unit performs all primary power distribution functions for the power distribution system based on the first and second parameters. The processing unit communicates a synchronization signal to the first and second data modules so that the first and second data modules sample the first and second parameters, respectively, within a predetermined time-window.
The above-described and other features and advantages of the present disclosure will be appreciated and understood by those skilled in the art from the following detailed description, drawings, and appended claims.
Referring now to the drawings and in particular to
Power bus 12 is illustrated by way of example as a three-phase power system having a first phase 18, a second phase 20, and a third phase 22. Power bus 12 can also include a neutral phase (not shown). System 10 is illustrated for purposes of clarity distributing power from power bus 12 to four circuits 16 by four breakers 14. Of course, it is contemplated by the present disclosure for power bus 12 to have any desired number of phases and/or for system 10 to have any desired number of circuit breakers 14.
Each circuit breaker 14 has a set of separable contacts 24 (illustrated schematically). Contacts 24 selectively place power bus 12 in communication with at least one load (also illustrated schematically) on circuit 16. The load can include devices, such as, but not limited to, motors, welding machinery, computers, heaters, lighting, and/or other electrical equipment.
Power distribution system 10 is illustrated in
Thus, system 26 can include protection and control schemes that consider the value of electrical signals, such as current magnitude and phase, at one or all circuit breakers 14. Further, system 26 integrates the protection, control, and monitoring functions of the individual breakers 14 of power distribution system 10 in a single, centralized control processor (e.g., CCPU 28). System 26 provides CCPU 28 with all of a synchronized set of information available through digital communication with modules 30 and circuit breakers 14 on network 32 and provides the CCPU with the ability to operate these devices based on this complete set of data.
Specifically, CCPU 28 performs all primary power distribution functions for power distribution system 10. Namely, CCPU 28 performs all instantaneous overcurrent protection (10C), sort time overcurrent, longtime overcurrent, relay protection, and logic control as well as digital signal processing functions of system 26. Thus, system 26 enables settings to be changed and data to be logged in single, central location, i.e., CCPU 28. CCPU 28 is described herein by way of example as a central processing unit. Of course, it is contemplated by the present disclosure for CCPU 28 to include any programmable circuit, such as, but not limited to, computers, processors, microcontrollers, microcomputers, programmable logic controllers, application specific integrated circuits, and other programmable circuits.
As shown in
Module 30 sends and receives one or more second signals 38 to and/or from circuit breaker 14. Second signals 38 can be representative of one or more conditions of breaker 14, such as, but not limited to, a position of separable contacts 24, a spring charge switch status, and others. In addition, module 30 is configured to operate circuit breaker 14 by sending one or more third signals 40 to the breaker to open/close separable contacts 24 as desired. In a first embodiment, circuit breakers 14 cannot open separable contacts 24 unless instructed to do so by system 26.
System 26 utilizes data network 32 for data acquisition from modules 30 and data communication to the modules. Accordingly, network 32 is configured to provide a desired level of communication capacity and traffic management between CCPU 28 and modules 30. In an exemplary embodiment, network 32 can be configured to not enable communication between modules 30 (i.e., no module-to-module communication).
In addition, system 26 can be configured to provide a consistent fault response time. As used herein, the fault response time of system 26 is defined as the time between when a fault condition occurs and the time module 30 issues an trip command to its associated breaker 14. In an exemplary embodiment, system 26 has a fault response time that is less than a single cycle of the 60 Hz (hertz) waveform. For example, system 26 can have a maximum fault response time of about three milliseconds.
The configuration and operational protocols of network 32 are configured to provide the aforementioned communication capacity and response time. For example, network 32 can be an Ethernet network having a star topology as illustrated in
In this configuration, network 32 provides a data transfer rate of at least about 100 Mbps (megabits per second). For example, the data transfer rate can be about 1 Gbps (gigabits per second). Additionally, communication between CCPU 28 and modules 30 across network 32 can be managed to optimize the use of network 32. For example, network 32 can be optimized by adjusting one or more of a message size, a message frequency, a message content, and/or a network speed.
Accordingly, network 32 provides for a response time that includes scheduled communications, a fixed message length, full-duplex operating mode, and a switch to prevent collisions so that all messages are moved to memory in CCPU 28 before the next set of messages is scheduled to arrive. Thus, system 26 can perform the desired control, monitoring, and protection functions in a central location and manner.
It should be recognized that data network 32 is described above by way of example only as an Ethernet network having a particular configuration, topography, and data transmission protocols. Of course, the present disclosure contemplates the use of any data transmission network that ensures the desired data capacity and consistent fault response time necessary to perform the desired range of functionality. The exemplary embodiment achieves sub-cycle transmission times between CCPU 28 and modules 30 and full sample data to perform all power distribution functions for multiple modules with the accuracy and speed associated with traditional devices.
CCPU 28 can perform branch circuit protection, zone protection, and relay protection interdependently because all of the system information is in one central location, namely at the CCPU. In addition, CCPU 28 can perform one or more monitoring functions on the centrally located system information. Accordingly, system 26 provides a coherent and integrated protection, control, and monitoring methodology not considered by prior systems. For example, system 26 integrates and coordinates load management, feed management, system monitoring, and other system protection functions in a low cost and easy to install system.
For purposes of clarity, the load management capabilities of system 26 are described with reference to
An exemplary embodiment of module 30 is illustrated in
Power supply 48 is configured to receive power from a first source 52 and/or a second source 54. First source 52 can be one or more of an uninterruptible power supply (not shown), a plurality of batteries (not shown), a power bus (not shown), and other sources. In the illustrated embodiment, second source 54 is the secondary current available from sensors 34.
Power supply 48 is configured to provide power 56 to module 30 from first and second sources 52, 54. For example, power supply 48 can provide power 56 to microprocessor 42, data bus 42, network interface 44, and memory devices 50. Power supply 48 is also configured to provide a fourth signal 58 to microprocessor 42. Fourth signal 58 is indicative of what sources are supplying power to power supply 48. For example, fourth signal 58 can indicate whether power supply 48 is receiving power from first source 52, second source 54, or both of the first and second sources.
Network interface 46 and memory devices 50 communicate with microprocessor 42 over data bus 44. Network interface 46 can be connected to network 32 so that microprocessor 42 is in communication with CCPU 28.
Microprocessor 42 receives digital representations of first signals 36 and second signals 38. First signals 36 are continuous analog data collected by sensors 34, while second signals 38 are discrete analog data from breaker 14. Thus, the data sent from modules 30 to CCPU 28 is a digital representation of the actual voltages, currents, and device status. For example, first signals 36 can be analog signals indicative of the current and/or voltage in circuit 16.
Accordingly, system 26 provides the actual raw parametric or discrete electrical data (i.e., first signals 36) and device physical status (i.e., second signal 38) to CCPU 28 via network 32, rather than processed summary information sampled, created, and stored by devices such as trip units, meters, or relays. As a result, CCPU 28 has complete, raw system-wide data with which to make decisions and can therefore operate any or all breakers 14 on network 32 based on information derived from as many modules 30 as the control and protection algorithms resident in CCPU 28 require.
Module 30 has a signal conditioner 60 and an analog-digital converter 62. First signals 36 are conditioned by signal conditioner 60 and converted to digital signals 64 by A/D converter 62. Thus, module 30 collects first signals 36 and presents digital signals 64, representative of the raw data in the first signals, to microprocessor 42. For example, signal conditioner 60 can includes a filtering circuit (not shown) to improve a signal-to-noise ratio first signal 36, a gain circuit (not shown) to amplify the first signal, a level adjustment circuit (not shown) to shift the first signal to a predetermined range, an impedance match circuit (not shown) to facilitate transfer of the first signal to A/D converter 62, and any combination thereof. Further, A/D converter 62 can be a sample-and-hold converter with external conversion start signal 66 from microprocessor 42 or a clock circuit 68 controlled by microprocessor 42 to facilitate synchronization of digital signals 64.
It is desired for digital signals 64 from all of the modules 30 in system 26 to be collected at substantially the same time. Specifically, it is desired for digital signals 64 from all of the modules 30 in system 26 to be representative of substantially the same time instance of the power in power distribution system 10.
Modules 30 sample digital signals 64 based, at least in part, upon a synchronization signal or instruction 70 as illustrated in
Modules 30 use synchronization instruction 70 to modify a resident sampling protocol. For example, each module 30 can have a synchronization algorithm resident on microprocessor 42. The synchronization algorithm resident on microprocessor 42 can be a software phase-lock-loop algorithm. The software phase-lock-loop algorithm adjusts the sample period of module 30 based, in part, on synchronization instructions 70 from CCPU 28. Thus, CCPU 28 and modules 30 work together in system 26 to ensure that the sampling (i.e., digital signals 64) from all of the modules in the system are synchronized.
Accordingly, system 26 is configured to collect digital signals 64 from modules 30 based in part on synchronization instruction 70 so that the digital signals are representative of the same time instance, such as being within a predetermined time-window from one another. Thus, CCPU 28 can have a set of accurate data representative of the state of each monitored location (e.g., modules 30) within the power distribution system 10. The predetermined time-window can be less than about ten microseconds. For example, the predetermined time-window can be about five microseconds.
The predetermined time-window of system 26 can be affected by the port-to-port variability of network 32. In an exemplary embodiment, network 32 has a port-to-port variability of in a range of about 24 nanoseconds to about 720 nanoseconds. In an alternate exemplary embodiment, network 32 has a maximum port-to-port variability of about 2 microseconds.
It has been determined that control of all of modules 30 to this predetermined time-window by system 26 enables a desired level of accuracy in the metering and vector functions across the modules, system waveform capture with coordinated data, accurate event logs, and other features. In an exemplary embodiment, the desired level of accuracy is equal to the accuracy and speed of traditional devices. For example, the predetermined time-window of about ten microseconds provides an accuracy of about 99% in metering and vector functions.
Second signals 38 from each circuit breaker 14 to each module 30 are indicative of one or more conditions of the circuit breaker. Second signals 38 are provided to a discrete I/O circuit 74 of module 30. Circuit 74 is in communication with circuit breaker 14 and microprocessor 42. Circuit 74 is configured to ensure that second signals 38 from circuit breaker 14 are provided to microprocessor 42 at a desired voltage and without jitter. For example, circuit 74 can include de-bounce circuitry and a plurality of comparators.
Microprocessor 42 samples first and second signals 36, 38 as synchronized by CCPU 28. Then, converter 62 converts the first and second signals 36, 38 to digital signals 64, which is packaged into a first message 76 having a desired configuration by microprocessor 42. First message 76 can include an indicator that indicates which synchronization signal 70 the first message was in response to. Thus, the indicator of which synchronization signal 70 first message 76 is responding to is returned to CCPU 28 for sample time identification.
CCPU 28 receives first message 76 from each of the modules 30 over network 32 and executes one or more protection and/or monitoring algorithms on the data sent in all of the first messages. Based on first message 76 from one or more modules 30, CCPU 28 can control the operation of one or more circuit breakers 14. For example, when CCPU 28 detects a fault from one or more of first messages 76, the CCPU sends a second message 78 to one or more modules 30 via network 32.
In response to second message 78, microprocessor 42 causes third signal 40 to operate (e.g., open contacts 24) circuit breaker 14. Circuit breaker 14 can include more than one operation mechanism. For example, circuit breaker 14 can have a shunt trip 80 and a magnetically held solenoid 82. Microprocessor 42 is configured to send a first output 84 to operate shunt trip 80 and/or a second output 86 to operate solenoid 82. First output 84 instructs a power control module 88 to provide third signal 40 (i.e., power) to shunt trip 80, which can separate contacts 24. Second output 86 instructs a gating circuit 90 to provide third signal 40 to solenoid 82 (i.e., flux shifter) to separate contacts 24. It should be noted that shunt trip 80 requires first source 52 to be present, while solenoid 82 can be operated only when second source 54 is present. In this manner, microprocessor 42 can operate circuit breaker 14 in response to second message 78 regardless of the state of first and second sources 52, 54.
In addition to operating circuit breaker 14, module 30 can communicate to one or more local input and/or output devices 94. For example, local output device 94 can be a module status indicator, such as a visual or audible indicator. In one embodiment, device 94 is a light emitting diode (LED) configured to communicate a status of module 30. In another embodiment, local input device 94 can be a status-modifying button for manually operating one or more portions of module 30. In yet another embodiment, local input device 94 is a module interface for locally communicating with module 30.
Accordingly, modules 30 are adapted to sample first signals 36 from sensors 34 as synchronized by the CCPU. Modules 30 then package the digital representations (i.e., digital signals 64) of first and second signals 36, 38, as well as other information, as required into first message 76. First message 76 from all modules 30 are sent to CCPU 28 via network 32. CCPU 28 processes first message 76 and generates and stores instructions to control the operation of each circuit breaker 14 in second message 78. CCPU 28 sends second message 78 to all of the modules 30. In an exemplary embodiment, CCPU 28 sends second message 78 to all of the modules 30 in response to synchronization instruction 70.
Accordingly, system 26 can control each circuit breaker 14 based on the information from that breaker alone, or in combination with the information from one or more of the other breakers in the system 26. Under normal operating conditions, system 26 performs all monitoring, protection, and control decisions at CCPU 28.
Since the protection and monitoring algorithms of system 26 are resident in CCPU 28, these algorithms can be enabled without requiring hardware or software changes in circuit breaker 14 or module 30. For example, system 26 can include a data entry device 92, such as a human-machine-interface (HMI), in communication with CCPU 28. In this embodiment, one or more attributes and functions of the protection and monitoring algorithms resident on CCPU 28 can easily be modified from data entry device 92. Thus, circuit breaker 14 and module 30 can be more standardized than was possible with the circuit breakers/trip units of prior systems. For example, over one hundred separate circuit breakers/trip units have been needed to provide a full range of sizes normally required for protection of a power distribution system. However, the generic nature of circuit breaker 14 and module 30 enabled by system 26 can reduce this number by over sixty percent. Thus, system 26 can resolve the inventory issues, retrofittability issues, design delay issues, installation delay issues, and cost issues of prior power distribution systems.
It should be recognized that system 26 is described above as having one CCPU 28 communication with modules 30 by way of a single network 32. However, it is contemplated by the present disclosure for system 26 to have redundant CCPUs 26 and networks 32 as illustrated in phantom in
Modules 30 can further include one or more backup systems for controlling breakers 14 independent of CCPU 28. For example, system 26 may be unable to protect circuit 16 in case of a power outage in first source 52, during the initial startup of CCPU 28, in case of a failure of network 32, and other reasons. Under these failure conditions, each module 30 includes one or more backup systems to ensure that at least some protection is provided to circuit breaker 14. The backup system can include one or more of an analog circuit driven by second source 54, a separate microprocessor driven by second source 54, and others.
Referring now to
In this example, system 26 includes twenty-four modules 30 each connected to a different circuit breaker 14. Each module 30 is scheduled by the phase-lock-loop algorithm and synchronization instruction 70 to sample its first signals 36 at a prescribed rate of 128 samples per cycle. Sample time 96 includes four sample intervals 101 of about 0.13 milliseconds (ms) each. Thus, sample time 96 is about 0.52 ms for data sampling and packaging into first message 76.
Receive/validate time 97 is initiated at the receipt of synchronization instruction 70. In an exemplary embodiment, receive/validate time 97 is a fixed time that is, for example, the time required to receive all first messages 76 as determined from the latency of data network 32. For example, receive/validate time 97 can be about 0.25 ms where each first message 76 has a size of about 1000 bits, system 26 includes twenty-four modules 30 (i.e., 24,000 bits), and network 32 is operating at about 100 Mbps. Accordingly, CCPU 28 manages the communications and moving of first messages 76 to the CCPU during receive/validate time 97.
The protection processes (i.e., process time 98) starts at the end of the fixed receive/validate time 97 regardless of the receipt of first messages 76. If any modules 30 are not sending first messages 76, CCPU 28 flags this error and performs all functions that have valid data. Since system 26 is responsible for protection and control of multiple modules 30, CCPU 28 is configured to not stop the entire system due to the loss of data (i.e., first message 76) from a single module 30. In an exemplary embodiment, process time 98 is about 0.27 ms.
CCPU 28 generates second message 78 during process time 98. Second message 78 can be twenty-four second messages (i.e., one per module 30) each having a size of about 64 bits per module. Alternately, it is contemplated by the present disclosure for second message 78 to be a single, multi-cast or broadcast message. In this embodiment, second message 78 includes instructions for each module 30 and has a size of about 1600 bits.
Transmit time 99 is the time necessary to transmit second message 78 across network 32. In the example where network 32 is operating at about 100 Mbps and second message 78 is about 1600 bits, transmit time 99 is about 0.016 ms.
It is also contemplated for second message 78 to include a portion of synchronization instruction 70. For example, CCPU 28 can be configured to send second message 78 upon receipt of the next synchronization instruction 70 from clock 72. In this example, the interval between consecutive second messages 76 can be measured by module 30 and the synchronization information in the second message, if any, can be used by the synchronization algorithm resident on microprocessor 42.
Once modules 30 receive second message 78, each module decodes the message and executes its instructions (i.e., send third signals 40), if any, in decode/execute time 100. For example, decode/execute time 100 can be about 0.05 ms.
In this example, response time 95 is about 1.11 ms. Of course, it should be recognized that system response time 95 can be accelerated or decelerated based upon the needs of system 26. For example, system response time 95 can be adjusted by changing one or more of the sample period, the number of samples per transmission, the number of modules 30, the message size, the message frequency, the message content, and/or the network speed.
It is contemplated by the present disclosure for system 26 to have response time 95 of up to about 3 milliseconds. Thus, system 26 is configured to open any of its circuit breakers within about 3 milliseconds from the time sensors 34 sense conditions outside of the set parameters.
Accordingly, system 26 is centrally controlled by CCPU 28 to protect power distribution system 10 during the distribution of power to the loads (i.e., circuits 16). In addition to this load management capability, system 26 can also provide integrated feed management capabilities to a power distribution system 110 as illustrated in
Power distribution system 110 has a first feed 102 and a second feed 104. Power is supplied to first and second feeds 102, 104 from a source (not shown) such as, an electric generator driven by a prime mover locally, or a power grid of an electric utility. The prime mover may be powered from, for example, but not limited to, a turbine or an internal combustion engine. In an exemplary embodiment, power is supplied to first feed 102 from a first point on a power grid, while power is supplied to second feed 104 from a second point on the power grid.
Power from first feed 102 is connectable to a first bus 112 by a first main breaker 114. First bus 112 is divided into a number of circuits 116 by sub-breakers 14. Thus, circuits 116 can be provided with power from first feed 102 by closing first main breaker 114 and sub-breakers 14 on first bus 112.
Similarly, power from second feed 104 is connectable to a second power bus 212 by a second main breaker 214. Second bus 212 is divided into a number of circuits 216 by sub-breakers 14. Thus, circuits 216 can be provided with power from second feed 102 by closing second main breaker 214 and sub-breakers 14 on second bus 212. First and second buses 112, 212 are also connectable to one another by a tie-breaker 314.
Power distribution system 110 is provided with system 26. Specifically, each breaker 14, 114, 214, and 314 in power distribution system 110 includes module 30 communicating with CCPU 28 via network 32. Advantageously, system 26 manages the distribution of power from power feeds 102, 104 using the same set of data as used for the load management. Further, system 26 manages the distribution of power from power feeds 102, 104 simultaneous with the load management control decisions. In this manner, system 26 can integrate the load management decisions with the feed management decisions and, thus, can provide for more precise control of power distribution system 110 than previously possible.
In the case of a loss of power in either first or second feeds 102, 104, first and second buses 112, 212 can be powered by the other bus through the closing of tie-breaker 314. For example, if power from first feed 102 is unavailable, CCPU 28 can open first main breaker 114 and close tie-breaker 314 to provide power to first bus 112 from second bus 212 (e.g., a throw over). Further, once power becomes available from first feed 102, CCPU 28 can close first main breaker 114 and open tie-breaker 314 to provide power to first bus 112 from the first source (e.g., a throw back).
Conversely, if power from second feed 104 is unavailable, CCPU 28 can open second main breaker 214 and close tie-breaker 314 to provide power to second bus 212 from first bus 112. Again, once power becomes available from second feed 104, CCPU 28 can close second main breaker 114 and open tie-breaker 314 to provide power to second bus 212 from the second source.
Accordingly, system 26 also provides for seamless integration in the management among feeds 102, 104 in power distribution system 110 (e.g., throw-over and throw-back). Advantageously, system 26 can manage the throw-over and/or throw-back among feeds 102, 104 without interrupting power to circuits 116, 216.
For example, when power from second feed 104 is feeding both second bus 212 and first bus 112, both second main breaker 214 and tie-breaker 314 are in a closed state, while first main breaker 114 is in an open state. Once power to main feed 102 is restored, system 26 ensures that power feeds 102, 104 are equal in magnitude, frequency, and phase at CCPU 28 via data from modules 30 at main breakers 114, 214, respectively. Once system 26 detects that power feeds 102, 104 are equal, CCPU 28 can close first main breaker 114 before or substantially simultaneously to opening tie-breaker 314. It is contemplated by the present disclosure for system 26 to open tie-breaker 314 within 100 milliseconds of closing first main breaker 114.
In this configuration, system 26 can provide over-current protection at any circuit breaker 14 even in the event that sensor 34 at that circuit breaker malfunctions. Take for example the instance where power from first feed 102 is supplied only to first bus 112 (i.e., tie-breaker 314 is open). In this situation, system 26 can provide over current protection to first main breaker 114 even in the event that sensor 34 at the first main breaker malfunctions. Here, the over-current functions of first main breaker 114 would be directed to function with the sum of the current signals of all the breakers 14 on first bus 112.
System 26 can also allow first main breaker 114 to be configured to handle the maximum current that first bus 112 may carry. Additionally, first main breaker 114 can include a current setting equal to that of each of breakers 14 on first bus 112 and a time characteristic that allows the first main breaker to provide backup protection to each individual breaker at that breaker's setting. In this example, CCPU 28 would simultaneously monitor the current at first bus 112 and each of the branch circuits 116, reacting to an undesirable current at any point. Thus, system 26 can provide each branch circuit 116 with secondary backup protection optimally set to supplement the primary protection with no compromise needed to achieve selectivity or to allow the bus current to flow unimpeded.
Accordingly, system 26 integrates the load management of the branch circuits to one another. Further, system 26 integrates the management of the loads on the branch circuits with the management of the power feeds feeding the branch circuits. Still further, system 26 provides this integrated functionality in a single central processor. This allows system 26 to adjust the protection functions of each breaker 14, 114, 214, 314 in the system based on the state of that breaker as sampled by first and second signals 38, 40, as well as based on the status of any and/or all of the other breakers in the system.
It should also be noted that the terms “first”, “second”, “third”, “upper”, “lower”, and the like may be used herein to modify various elements. These modifiers do not imply a spatial, sequential, or hierarchical order to the modified elements unless specifically stated.
While the instant disclosure has been described with reference to one or more exemplary embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope thereof. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the disclosure without departing from the scope thereof. Therefore, it is intended that the disclosure not be limited to the particular embodiment(s) disclosed as the best mode contemplated for carrying out this invention, but that the invention will include all embodiments falling within the scope of the appended claims.
This application is related to U.S. Patent Application No. 60/359,544 filed on Feb. 25, 2002 for “Integrated Protection, Monitoring, and Control” the contents of which are incorporated by reference herein. This application is also related to U.S. Patent Application No. 60/438,159 filed on Jan. 6, 2003 for “Single Processor Concept for Protection and Control of Circuit Breakers in Low-Voltage Switchgear” the contents of which are incorporated by reference herein.
Number | Name | Date | Kind |
---|---|---|---|
3772505 | Massell | Nov 1973 | A |
3938007 | Boniger et al. | Feb 1976 | A |
3956671 | Nimmersjo | May 1976 | A |
3963964 | Mustaphi | Jun 1976 | A |
4001742 | Jencks et al. | Jan 1977 | A |
4245318 | Eckart et al. | Jan 1981 | A |
4291299 | Hinz et al. | Sep 1981 | A |
4301433 | Castonguay et al. | Nov 1981 | A |
4311919 | Nail | Jan 1982 | A |
4415968 | Maeda et al. | Nov 1983 | A |
4423459 | Stich et al. | Dec 1983 | A |
4432031 | Premerlani | Feb 1984 | A |
4455612 | Girgis et al. | Jun 1984 | A |
4468714 | Russell | Aug 1984 | A |
4589074 | Thomas et al. | May 1986 | A |
4612594 | Yamaura et al. | Sep 1986 | A |
4623949 | Salowe et al. | Nov 1986 | A |
4631625 | Alexander et al. | Dec 1986 | A |
4642724 | Ruta | Feb 1987 | A |
4652966 | Farag et al. | Mar 1987 | A |
4672501 | Bilac et al. | Jun 1987 | A |
4672555 | Hart et al. | Jun 1987 | A |
4674062 | Premerlani | Jun 1987 | A |
4689712 | Demeyer | Aug 1987 | A |
4709339 | Fernandes | Nov 1987 | A |
4751653 | Junk et al. | Jun 1988 | A |
4752853 | Matsko et al. | Jun 1988 | A |
4754407 | Nolan | Jun 1988 | A |
4777607 | Maury et al. | Oct 1988 | A |
4783748 | Swarztrauber et al. | Nov 1988 | A |
4796027 | Smith-Vaniz | Jan 1989 | A |
4833592 | Yamanaka | May 1989 | A |
4849848 | Ishii | Jul 1989 | A |
4855671 | Fernandes | Aug 1989 | A |
4862308 | Udren | Aug 1989 | A |
4964058 | Brown, Jr. | Oct 1990 | A |
4979122 | Davis et al. | Dec 1990 | A |
4983955 | Ham, Jr. et al. | Jan 1991 | A |
4996646 | Farrington | Feb 1991 | A |
5053735 | Ohishi et al. | Oct 1991 | A |
5060166 | Engel et al. | Oct 1991 | A |
5101191 | MacFadyen et al. | Mar 1992 | A |
5134691 | Elms | Jul 1992 | A |
5136458 | Durivage, III | Aug 1992 | A |
5162664 | Haun et al. | Nov 1992 | A |
5166887 | Farrington et al. | Nov 1992 | A |
5170310 | Studtmann et al. | Dec 1992 | A |
5170360 | Porter et al. | Dec 1992 | A |
5179376 | Pomatto | Jan 1993 | A |
5182547 | Griffith | Jan 1993 | A |
5185705 | Farrington | Feb 1993 | A |
5196831 | Bscheider | Mar 1993 | A |
5214560 | Jensen | May 1993 | A |
5216621 | Dickens | Jun 1993 | A |
5225994 | Arinobu et al. | Jul 1993 | A |
5231565 | Bilas et al. | Jul 1993 | A |
5237511 | Caird et al. | Aug 1993 | A |
5247454 | Farrington et al. | Sep 1993 | A |
5253159 | Bilas et al. | Oct 1993 | A |
5272438 | Stumme | Dec 1993 | A |
5301121 | Garverick et al. | Apr 1994 | A |
5305174 | Morita et al. | Apr 1994 | A |
5311392 | Kinney et al. | May 1994 | A |
5323307 | Wolf et al. | Jun 1994 | A |
5353188 | Hatakeyama | Oct 1994 | A |
5361184 | El-Sharkawi et al. | Nov 1994 | A |
5367427 | Matsko et al. | Nov 1994 | A |
5369356 | Kinney et al. | Nov 1994 | A |
5381554 | Langer et al. | Jan 1995 | A |
5384712 | Oravetz et al. | Jan 1995 | A |
5402299 | Bellei | Mar 1995 | A |
5406495 | Hill | Apr 1995 | A |
5414635 | Ohta | May 1995 | A |
5420799 | Peterson et al. | May 1995 | A |
5422778 | Good et al. | Jun 1995 | A |
5440441 | Ahuja | Aug 1995 | A |
5451879 | Moore | Sep 1995 | A |
5487016 | Elms | Jan 1996 | A |
5490086 | Leone et al. | Feb 1996 | A |
5493468 | Hunter et al. | Feb 1996 | A |
5530738 | McEachern | Jun 1996 | A |
5534782 | Nourse | Jul 1996 | A |
5534833 | Castonguay et al. | Jul 1996 | A |
5537327 | Snow et al. | Jul 1996 | A |
5544065 | Engel et al. | Aug 1996 | A |
5559719 | Johnson et al. | Sep 1996 | A |
5560022 | Dunstan et al. | Sep 1996 | A |
5576625 | Sukegawa et al. | Nov 1996 | A |
5581471 | McEachern et al. | Dec 1996 | A |
5587917 | Elms | Dec 1996 | A |
5596473 | Johnson et al. | Jan 1997 | A |
5600527 | Engel et al. | Feb 1997 | A |
5608646 | Pomatto | Mar 1997 | A |
5613798 | Braverman | Mar 1997 | A |
5619392 | Bertsch et al. | Apr 1997 | A |
5627716 | Lagree et al. | May 1997 | A |
5627717 | Pein et al. | May 1997 | A |
5627718 | Engel et al. | May 1997 | A |
5629825 | Wallis et al. | May 1997 | A |
5631798 | Seymour et al. | May 1997 | A |
5638296 | Johnson et al. | Jun 1997 | A |
5650936 | Loucks et al. | Jul 1997 | A |
5661658 | Putt et al. | Aug 1997 | A |
5666256 | Zavis et al. | Sep 1997 | A |
5670923 | Gonzalez et al. | Sep 1997 | A |
5694329 | Pomatto | Dec 1997 | A |
5696695 | Ehlers et al. | Dec 1997 | A |
5719738 | Singer et al. | Feb 1998 | A |
5734576 | Klancher | Mar 1998 | A |
5736847 | Van Doorn et al. | Apr 1998 | A |
5737231 | Pyle et al. | Apr 1998 | A |
5742513 | Bouhenguel et al. | Apr 1998 | A |
5751524 | Swindler | May 1998 | A |
5754033 | Thomson | May 1998 | A |
5754440 | Cox et al. | May 1998 | A |
5768148 | Murphy et al. | Jun 1998 | A |
5784237 | Velez | Jul 1998 | A |
5784243 | Pollman et al. | Jul 1998 | A |
5786699 | Sukegawa et al. | Jul 1998 | A |
5812389 | Katayama et al. | Sep 1998 | A |
5821704 | Carson et al. | Oct 1998 | A |
5825643 | Dvorak et al. | Oct 1998 | A |
5828576 | Loucks et al. | Oct 1998 | A |
5828983 | Lombardi | Oct 1998 | A |
5831428 | Pyle et al. | Nov 1998 | A |
5867385 | Brown et al. | Feb 1999 | A |
5872722 | Oravetz et al. | Feb 1999 | A |
5872785 | Kienberger | Feb 1999 | A |
5890097 | Cox | Mar 1999 | A |
5892449 | Reid et al. | Apr 1999 | A |
5903426 | Ehling | May 1999 | A |
5905616 | Lyke | May 1999 | A |
5906271 | Castonguay et al. | May 1999 | A |
5926089 | Sekiguchi et al. | Jul 1999 | A |
5936817 | Matsko et al. | Aug 1999 | A |
5946210 | Montminy et al. | Aug 1999 | A |
5958060 | Premerlani | Sep 1999 | A |
5963457 | Kanoi et al. | Oct 1999 | A |
5973481 | Thompson et al. | Oct 1999 | A |
5973899 | Williams et al. | Oct 1999 | A |
5982595 | Pozzuoli | Nov 1999 | A |
5982596 | Spencer et al. | Nov 1999 | A |
5995911 | Hart | Nov 1999 | A |
6005757 | Shvach et al. | Dec 1999 | A |
6005758 | Spencer et al. | Dec 1999 | A |
6018451 | Lyke et al. | Jan 2000 | A |
6038516 | Alexander et al. | Mar 2000 | A |
6047321 | Raab et al. | Apr 2000 | A |
6054661 | Castonguay et al. | Apr 2000 | A |
6055145 | Lagree et al. | Apr 2000 | A |
6061609 | Kanoi et al. | May 2000 | A |
6084758 | Clarey et al. | Jul 2000 | A |
6138241 | Eckel et al. | Oct 2000 | A |
6139327 | Callahan et al. | Oct 2000 | A |
6141196 | Premerlani et al. | Oct 2000 | A |
6157527 | Spencer et al. | Dec 2000 | A |
6167329 | Engel et al. | Dec 2000 | A |
6175780 | Engel | Jan 2001 | B1 |
6185482 | Egolf et al. | Feb 2001 | B1 |
6185508 | Van Doorn et al. | Feb 2001 | B1 |
6186842 | Hirschbold et al. | Feb 2001 | B1 |
6195243 | Spencer et al. | Feb 2001 | B1 |
6198402 | Hasegawa et al. | Mar 2001 | B1 |
6212049 | Spencer et al. | Apr 2001 | B1 |
6233128 | Spencer et al. | May 2001 | B1 |
6236949 | Hart | May 2001 | B1 |
6242703 | Castonguay et al. | Jun 2001 | B1 |
6268991 | Criniti et al. | Jul 2001 | B1 |
6285917 | Sekiguchi et al. | Sep 2001 | B1 |
6288882 | DiSalvo et al. | Sep 2001 | B1 |
6289267 | Alexander et al. | Sep 2001 | B1 |
6291911 | Dunk et al. | Sep 2001 | B1 |
6292340 | O'Regan et al. | Sep 2001 | B1 |
6292717 | Alexander et al. | Sep 2001 | B1 |
6292901 | Lys et al. | Sep 2001 | B1 |
6297939 | Bilac et al. | Oct 2001 | B1 |
6313975 | Dunne et al. | Nov 2001 | B1 |
6341054 | Walder et al. | Jan 2002 | B1 |
6347027 | Nelson et al. | Feb 2002 | B1 |
6351823 | Mayer et al. | Feb 2002 | B1 |
6356422 | Bilac et al. | Mar 2002 | B1 |
6356849 | Jaffe | Mar 2002 | B1 |
6369996 | Bo | Apr 2002 | B1 |
6377051 | Tyner et al. | Apr 2002 | B1 |
6385022 | Kulidjian et al. | May 2002 | B1 |
6396279 | Gruenert | May 2002 | B1 |
6397155 | Przydatek et al. | May 2002 | B1 |
6405104 | Dougherty | Jun 2002 | B1 |
6406328 | Attarian et al. | Jun 2002 | B1 |
6411865 | Qin et al. | Jun 2002 | B1 |
6441931 | Moskovich et al. | Aug 2002 | B1 |
6459997 | Anderson | Oct 2002 | B1 |
6496342 | Horvath et al. | Dec 2002 | B1 |
6535797 | Bowles et al. | Mar 2003 | B1 |
6549880 | Willoughby et al. | Apr 2003 | B1 |
6553418 | Collins et al. | Apr 2003 | B1 |
6892115 | Berkcan et al. | May 2005 | B1 |
20010010032 | Ehlers et al. | Jul 2001 | A1 |
20010032025 | Lenz et al. | Oct 2001 | A1 |
20010044588 | Mault | Nov 2001 | A1 |
20010048354 | Douville et al. | Dec 2001 | A1 |
20010055965 | Delp et al. | Dec 2001 | A1 |
20020010518 | Reid et al. | Jan 2002 | A1 |
20020032535 | Alexander et al. | Mar 2002 | A1 |
20020034086 | Scoggins et al. | Mar 2002 | A1 |
20020045992 | Shincovich et al. | Apr 2002 | A1 |
20020059401 | Austin | May 2002 | A1 |
20020063635 | Shincovich | May 2002 | A1 |
20020064010 | Nelson et al. | May 2002 | A1 |
20020091949 | Ykema | Jul 2002 | A1 |
20020094799 | Elliott et al. | Jul 2002 | A1 |
20020107615 | Bjorklund | Aug 2002 | A1 |
20020108065 | Mares | Aug 2002 | A1 |
20020109722 | Rogers et al. | Aug 2002 | A1 |
20020111980 | MIller et al. | Aug 2002 | A1 |
20020116092 | Hamamatsu et al. | Aug 2002 | A1 |
20020124011 | Baxter et al. | Sep 2002 | A1 |
20020146076 | Lee | Oct 2002 | A1 |
20020146083 | Lee et al. | Oct 2002 | A1 |
20020147503 | Osburn, III | Oct 2002 | A1 |
20020159402 | Binder | Oct 2002 | A1 |
20020162014 | Przydatek et al. | Oct 2002 | A1 |
20020163918 | Cline | Nov 2002 | A1 |
20020165677 | Lightbody et al. | Nov 2002 | A1 |
20020181174 | Bilac et al. | Dec 2002 | A1 |
20020193888 | Wewalaarachchi et al. | Dec 2002 | A1 |
20030043785 | Liu et al. | Mar 2003 | A1 |
20030212515 | Fletcher et al. | Nov 2003 | A1 |
Number | Date | Country |
---|---|---|
0718948 | Jun 1996 | EP |
0949734 | Oct 1999 | EP |
Number | Date | Country | |
---|---|---|---|
20040019410 A1 | Jan 2004 | US |
Number | Date | Country | |
---|---|---|---|
60359544 | Feb 2002 | US | |
60438159 | Jan 2003 | US |