JP2023513440A - Power system ordering scheme for arbitrary topologies - Google Patents

Abstract

The system and apparatus identify a first source object, a second source object, and a load bus object and determine locations of the first source object, the second source object, and the load bus object on the single-line topology. , the operating parameters of the first source object, the second source object, and the load bus object, and electrically connected between the first source object and the load bus object using a single-line topology. defining a first path containing objects, defining a second path containing all objects electrically connected between a second source object and a load bus object using a single line topology, and circuitry configured to control operation of the first path and the second path. TIFF2023513440000002.tif101128

Description

CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of priority to U.S. Provisional Patent Application No. 62/965,459, filed January 24, 2020, the entire contents of which are incorporated herein by reference. incorporated into the book.

BACKGROUND The present disclosure relates to power systems. More particularly, the present disclosure relates to systems and methods for providing coordinated control of machines and components within power systems.

SUMMARY One aspect identifies a first source object, a second source object, and a load bus object and determines the location of the first source object, the second source object, and the load bus object on a single-line topology. , the operating parameters of the first source object, the second source object, and the load bus object, and electrically connected between the first source object and the load bus object using a single-line topology. defining a first path containing objects, defining a second path containing all objects electrically connected between a second source object and a load bus object using a single line topology, and to an apparatus including circuitry configured to control the operation of the first path and the second path.

In some aspects, the circuitry is further configured to generate a route table containing all available routes.

In some aspects, controlling the first path comprises selectively activating the first path by controlling the closing behavior of switch objects included on the first path; and disabling the first path by controlling the opening action of at least one switch object thereon. In some aspects, activating the first path includes communicating with all objects on the first path and prior to initiating the closing operation of switch objects included on the first path. and coordinating the activation behavior of each object.

In some aspects, defining the first path includes connecting a first source object and a load bus object to define inclusion on the first path within an associated control circuit. includes communication with all objects electrically connected to the

In some aspects, the circuit includes:
including all objects that are different from and parallel to the first path and electrically connected between the first source object and the load bus object along the third path;
A third path is further constructed to define using a single-line topology. In some aspects, the first path defines a first priority value and the third path defines a second priority value that is higher than the first priority value. In some aspects, the first priority value is proportional to the number of switch objects included in the first path and the second priority value is proportional to the number of switch objects included in the third path. In some embodiments, only one of the first pathway and the third pathway are enabled simultaneously during continuous use after the transition period.

In some aspects, the circuitry is further constructed to disable the second path, thereby inhibiting the second path from being enabled.

Another aspect is
a first genset controller associated with a first genset and a first genset switch;
a second power plant controller associated with the second power plant and the second power plant switch;
a plant branch switch controller associated with a plant branch switch coupled to the first plant switch and the second plant switch via a plant branch bus;
A system comprising: a utility switch controller associated with a utility switch; and a load bus controller associated with a load bus coupled to the power plant branch switch and the utility switch, comprising:
a first path including a first power plant, a first power plant switch, a power plant branch bus, a power plant branch switch, and a load bus;
a second path comprising a second power plant, a second power plant switch, a power plant branch bus, a power plant branch switch and a load bus; and a third path comprising a utility switch and a load bus. A system constructed to generate a routing table that defines a route for a. The system selectively enables the first path by communicating with the first power plant controller, the power plant branch switch controller and the load bus controller. The system selectively enables the second path by communicating with the second plant controller, the plant branch switch controller and the load bus controller. The system selectively enables the third path by communicating with the utility switch controller and the load bus controller.

In some aspects, the load bus controller includes a load bus routing function that determines which of the first path, the second path, and the third path to enable or disable; A transition type function is provided to each controller associated with any switch on any path to accomplish disabling or disabling. In some aspects, the first power plant controller receives a transition type function from the load bus controller to transition the first power plant and the first power plant to achieve activation or deactivation of the first path. A switch operation processing function configured to control operation of the power plant switch is included. In some aspects, the switch operation processing function calls for activation of a synchronizer function that adjusts the voltage, frequency, and phase angle of the output of the first power plant before the first power plant switch is closed. so that it is further constructed. In some aspects, the switch processing function is configured to communicate the switch state function to the load bus routing function, and the path state function is generated by the load bus routing function based on the switch state function.

Another aspect is generating a single-line topology of the power system including source objects, switch objects, bus objects, and controller objects; populating each object with operating parameters; generating a routing table defining a route, each route including all objects electrically connected between the route's source object and a bus object; and activating the route. and controlling a power system by disabling.

In some aspects, the operating parameters for each object are selected from a library of object configurations.

In some aspects, the method also includes generating a valid route list containing a list of routes to be enabled or disabled; including the step of communicating.

In some aspects, the routing table assigns a route ID, availability attributes, route priority, and route path to each route.

In some aspects, each controller object is assigned to one or more of a source object, a switch object, and a bus object to implement control of the power system by enabling and disabling paths. .

Another aspect includes a non-transitory computer-readable medium that, when executed by circuitry of the power system, causes the power system to perform the functions of enabling and disabling paths. The present invention relates to non-transitory computer-readable media having computer-executable instructions stored thereon. The function identifies a first source object, a second source object, and a load bus object; determines the positions of the first source object, the second source object, and the load bus object on the single-line topology; Receive operating parameters of one source object, a second source object, and a load bus object, and an object electrically connected between the first source object and the load bus object using a single line topology. define a first path containing all objects electrically connected between the second source object and the load bus object using the single-line topology; and define a second path containing all objects electrically connected between the second source object and the load bus object Including controlling the operation of the first path and the second path.

Another aspect is a first controller configured to control a first power system object located on a first path of the power system and a second controller located on a second path of the power system. and a second controller configured to control the power system object. Both the first controller and the second controller are configured to perform path-level functions including coordinating the operation of the first power system object and the second power system object, the first controller being the primary controller. and the second controller is the participating controller.

In some aspects, a participating controller is prohibited from performing path-level functions.

In some aspects, the participating controller computes the output of the path-level function asynchronously with the primary controller, the output of the participating controller coordinating the operation of the first power system object and the second power system object. not used for

In some aspects, the participating controller computes the output of the path level function synchronously with the primary controller, the output of the participating controller for coordinating the operation of the first power system object and the second power system object. not used for

In some aspects, path-level functions performed by the primary controller receive input from the primary controller and participating controllers.

In some aspects, the second controller performs path-level functions when the first controller is unable to perform the path-level functions.

In some aspects, a first controller defines a first object ID, a second controller defines a second object ID that defines a higher value than the first object ID, and a primary controller is selected based on the lowest available object ID.

In some aspects, the system also includes a third controller configured to control the first power system object. The third controller is a redundant controller constructed to perform path level functions including coordinating the operation of the first power system object and the second power system object.

In some aspects, the first power system object is located on both the first path and the second path.

Another aspect includes coordinating operation of the first power system object to control a first power system object located on a first path of the power system and to receive path level input. a first controller configured to perform path level functions and to control a second power system object located on a second path of the power system and receiving path level inputs; , a second controller configured to perform path-level functions including coordinating operation of a second power system object. Path level inputs contain information about the first path and the second path, and path level functions affect the behavior of the first path and the second path.

In some aspects, the first controller is configured to receive only path level inputs related to coordinating operation of the first power system object.

In some aspects, the first controller and the second controller compute the path level function synchronously or asynchronously.

In some aspects, the system also includes a third controller configured to control the first power system object. A third controller is a redundant controller built to perform path level functions.

In some aspects, the first controller is a first power plant controller, the second controller is a second power plant controller, and the path level functions include load sharing functions. In some aspects, the first power plant controller publishes the first load value data, receives the second load value data from the second power plant controller, and publishes the first load value data and the second load value data. and calculating an average load based on the load value data of and controlling the power output of the first power system object to achieve the average load.

Another aspect is a first controller configured to control a first power system object of the power system and a second controller configured to control a second power system object of the power system. a first controller and a second controller both configured to perform a first path-level function including coordinating operation of the first power system object and the second power system object; a second controller, one controller being a primary controller and a second controller being a participating controller, to control a third power system object of the power system and receiving a path level input; A third controller constructed to perform a second path-level function including coordinating the operation of a third power system object; and a fourth controller configured to receive the level input and perform a second path level function including coordinating operation of a fourth power system object.

In some aspects, the participating controller is prohibited from performing the first path level function.

In some aspects, the participating controller computes the output of the first path level function asynchronously with the primary controller, the output of the participating controller being the operation of the first power system object and the second power system object. is not used to adjust the

In some aspects, the participating controller computes the output of the first path level function synchronously with the primary controller, the output of the participating controller dictating the operation of the first power system object and the second power system object. Not used for tuning.

In some aspects, the system also includes redundant controllers configured to perform at least one of the first path level function or the second path level function.

In some aspects, either the first controller, the second controller, the third controller, or the fourth controller can be built on shared circuitry.

Another aspect is a non-transitory computer-readable medium that, when executed by a first controller, a second controller, a third controller, and a fourth controller of a power system, activates a path and A non-transitory computer-readable medium having computer-executable instructions contained in the non-transitory computer-readable medium that cause a power system to perform a disabling function. The function is to control a first power system object of the power system with a first controller, control a second power system object of the power system with a second controller, implementing a first path-level function including coordinating the operation of the first power system object and the second power system object using the controller and the second controller, the first controller being the primary controller; and the second controller is a participating controller, performing, using the third controller to control a third power system object of the power system, and using the third controller to provide path level input performing, with a third controller, a second path-level function that includes coordinating the operation of a third power system object; and using a fourth controller, a fourth path-level function of the power system receiving path-level input with a fourth controller; and coordinating operation of the fourth power system object with the fourth controller. and performing a level function.

Another aspect includes a non-transitory computer-readable medium that, when executed by circuitry of the power system, causes the power system to perform the functions of enabling and disabling paths. The present invention relates to non-transitory computer-readable media having computer-executable instructions stored thereon. The function is to determine a plurality of source objects, each containing a source function and assigned a position on the single-line topology, and to determine one or more switch objects, each comprising a switch function and assigned a position on the single-line topology; and determining one or more busbar objects, each comprising a busbar function and assigned a position on the single-line topology. determining one or more load objects, each containing a load function and assigned a position on the single-line topology; assigning each object to one of the plurality of controllers; each of the controllers is constructed to cooperatively perform the source, switch, bus, and load functions to provide operation of the system. .

In some aspects, the source functions include one or more of source state functions, capacity manager functions, synchronizer functions, load sharing functions, source selection functions, source prioritization functions, and grid parallelization functions. The switch functions include one or more of switch status functions, synchronization check functions, and switch action processing functions. The bus functions include one or more of a bus status function, a router function, a system routing table function, a path status function, and a failed bus access function. The load functions include one or more of load status functions, load decay functions, load add/limit functions, and sensitive load disconnect functions.

In some aspects, the function also includes determining one or more transformer objects, each containing a transformer function and assigned a position on the single-line topology.

In some aspects, the source function, the switch function, the bus function, and the load function each include a list of available algorithms, and the plurality of controllers select based on the object type and location on the single-line topology. Utilize a subset of the list of possible algorithms. In some aspects, the subset includes all available algorithms.

In some aspects, each function is configured to define the behavior of associated objects within the single-line topology.

In some aspects, the multiple controllers are constructed to perform source, switch, bus, and load functions using software common to each of the multiple controllers.

In some aspects, each function is automatically configured based on the object's specification and position on the single-line topology.

Another aspect includes a source object that includes a source state function and a synchronizer function; a bus object that includes a bus state function, a path state function, a router function, and a routing table function; and a switch state function and a switch action processing function. A single-line topology containing switch objects, load objects containing load state functions and load addition/limiting functions, and enabling and disabling routes on the single-line topology by coordinating the source, bus, switch and load objects. and a routing system that includes a router function built to be able to

In some aspects, the source state function identifies the current operating state of the source object, the synchronizer function is configured to control the frequency, voltage, and phase difference of the source object, and the router function determines the source state. Enabling and disabling routes based at least in part on functionality.

In some aspects, the bus state function determines the electrical state of the bus object, the output of the bus state function is provided to the switch operation processing function and load add/limit function, and the path state function activates the path. A routing table function defines the available routes that exist on a single-line topology, and a router function defines a bus state function, a route state function, and a routing Enabling and disabling routes based at least in part on the table.

In some aspects, the switch state function locates the switch object, the switch operation processing function controls the operation of the switch object, and the router function performs path activation or deactivation to: Providing instructions to the switch operation processing function based at least in part on the switch state function.

In some aspects, the load status function identifies the state of the load object as energized, blacked out, failed, or decaying, and the load add/shed function determines whether the load demand is high compared to the available power sources. Low, the router function enables and disables routes based at least in part on the load condition function and the load add/shed function.

In some aspects, the source object, the bus object, the switch object, and the load object exist as virtual objects on a single-line topology, and the parameters of the source object, the bus object, the switch object, and the load object are displayed in the user interface. can be entered via

In some aspects, the path control system includes one of a flow-dominant control scheme and a fully distributed control scheme.

Another aspect is identifying machines in a power system on a single-line topology and generating objects in a path-level control system, each object being associated with the identified machine; where the parameters include the operational requirements of the associated machine; positioning each object on a single-line topology; defining paths electrically connecting the objects; and controlling machine operation by enabling and disabling paths. Activation and deactivation of paths is accomplished according to the populated parameters of the object.

In some aspects, each object includes functionality that defines the behavior of the object within the single-line topology. In some aspects, objects are selected for object types including source objects, transformer objects, bus objects, switch objects, and load objects. In some aspects, creating an object in a path level control system includes selecting an object and populating a single line topology using a software tool.

In some aspects, generating the object further comprises selecting the object from an object palette library within the software tool.

In some aspects, the path level control system includes a plurality of controllers associated with the object, wherein controlling operation uses one of a flow master control scheme and a fully distributed control scheme among the plurality of controllers. to coordinate the function of the object.

This summary is merely exemplary and is in no way intended to be limiting. Other aspects, inventive features, and advantages of the devices or processes described herein are set forth herein, taken in conjunction with the accompanying figures, in which like reference numerals refer to like elements. This will become clear in the detailed description.

1 is a schematic diagram of a power system in accordance with some aspects; FIG. 2 is an object table associated with the power system of FIG. 1, according to some aspects; 2 is a schematic diagram of object functions associated with the power system of FIG. 1, in accordance with certain aspects; FIG. 1 is a schematic diagram of a power system in accordance with some aspects; FIG. 5 is an object table associated with the power system of FIG. 4, according to some aspects; 5 is a routing table associated with the power system of FIG. 4, according to some aspects; 1 is a schematic diagram of a power system in accordance with some aspects; FIG. 8 is a routing table associated with the power system of FIG. 7, according to some aspects; 8 is a functional logic map associated with the power system of FIG. 7, according to some aspects; FIG. 4 is a schematic diagram of a controller in accordance with some aspects; 1 is a schematic diagram of a power system in accordance with some aspects; FIG. 12 is an allocation table associated with the power system of FIG. 11, according to some aspects; 1 is a schematic diagram of a power system in accordance with some aspects; FIG. 1 is a schematic diagram of a power system in accordance with some aspects; FIG. 1 is a schematic diagram of a power system in accordance with some aspects; FIG. 16 is an allocation table associated with the power system of FIGS. 13-15, according to some aspects; FIG. 1 is a schematic diagram of a power system in accordance with some aspects; FIG. 18 is an allocation table associated with the power system of FIG. 17, according to some aspects; 1 is a schematic diagram of a centralized control scheme in accordance with some aspects; FIG. 1 is a schematic diagram of centralized control with a redundant controller scheme in accordance with some aspects; FIG. 1 is a schematic diagram of a flow master control scheme, according to some aspects; FIG. 22 is a schematic diagram of the flow master control scheme of FIG. 21, according to some aspects; FIG. 1 is a schematic diagram of a fully distributed control scheme in accordance with some aspects; FIG. 24 is a schematic diagram of the fully distributed control scheme of FIG. 23, according to some aspects; FIG. 1 is a schematic diagram of a redundant controller flow master control scheme, in accordance with some aspects; FIG.

DETAILED DESCRIPTION A more detailed description of various concepts related to methods, apparatus, and systems for power routing and implementations of those methods, apparatus, and systems follows. Before turning now to the figures illustrating in detail certain illustrative aspects, it is to be understood that the present disclosure is not limited to the details or methodology described in this description or illustrated in the figures. Also, it is to be understood that the terminology used herein is for the purpose of description only and should not be regarded as limiting.

As used herein, the term "power system topology" means an interconnection map of power supplies, power switches, and loads for a particular power system. As used herein, the terms "single-line diagram," "single-line diagram," or "single-line topology" refer to a simplified representation of a power system topology.

Referring generally to the figures, various aspects disclosed herein relate to systems, apparatus, and methods for power routing and distribution. Certain aspects improve existing power system control using systems, devices, and methods built to sequence, connect, disconnect, and switch sources to load buses for any power system topology. The purpose is to improve the method. Some aspects control structures for connecting and disconnecting specific load circuits. In general, aspects described herein identify power system components as objects within a system architecture. For example, a power system may include source objects (e.g., grid power connections provided by utility companies, power generation equipment, solar arrays, battery banks, etc.), bus objects (e.g., source buses, load buses, distribution buses, etc.), transformers objects (e.g. passive power transformers), switch objects (e.g. automatic transfer switches (ATS), load switches, source switches, circuit breakers, etc.), and controller objects (e.g. source controllers, load bus controllers, switch controllers). etc.). Each object is assigned an individual object identifier and introduced into a system architecture that can be represented in a single-wire topology. A path is then defined between each source and each load defined in the single-wire topology to establish a potential path for power transfer from the source to the load. For example, in some system architectures, more than one path may be available to provide power from one source to a given load. Each path is assigned an individual path identifier. Each object is then allocated or assigned a controller. Typically, objects are allocated contiguous controllers. For example, a power plant controller that is coupled to and controls the power plant source object may also be assigned to control the source bus. Once each object is assigned to one controller, the power system can control the operation of the object using a centralized controller that communicates with each individual controller object, or a distributed control scheme. For example, a flow master control scheme can be used, where one controller object in the power system acts as a centralized control for a particular task, but an individual controller object acts as a centralized control. The controller object of will change depending on the tasks required by the power system. In another aspect, a fully distributed control scheme is used in which all controller objects that implement a particular system function are equivalent. They are completely decentralized, with each controller deciding what to do for itself, rather than deciding what to do for the other controllers (as is the case with the master controller in the flow master control scheme). One feature. Redundancy is provided to the system because more than one controller object can operate the functions of the power system in both the fluid master control scheme and the fully distributed control scheme.

An object-based system architecture can simplify the design, implementation or commissioning, and operation of power systems. Each object is recognized by each controller and customized with attributes or parameters. This allows each controller to know what it is connected to, or what path each object is on, and how each object affects that path. The ability to build a system based on a single-wire topology and control using object-based paths improves design and construction efficiency while providing a more robust control scheme.

As shown in FIG. 1, a simple power system 30 includes a utility 34 that provides grid power (e.g., provides alternating current (AC)) connected to a utility source bus 38 and an alternating current (AC) to a power generation facility bus 46 . and a generator set (genset) 42 for providing electrical power. Utility source bus 38 is connected to utility source switch 50 and power plant bus 46 is connected to power plant switch 54 . In some embodiments, utility source switch 50 and power plant switch 54 are incorporated into an automatic transfer switch (ATS) connected to load bus 62 . The automatic transfer switch may be arranged or constructed to provide power to the load bus 62 from one of the utility bus 38 or the power generation facility bus 46 . A load 58 is connected to load bus 62 and is constructed to consume power provided by utility 34 or power generation facility 42 .

Generally, power system 30 operates by drawing power from utility 34 to load 58 . In the event of a power interruption to utility 34 , an ATS, including utility switch 50 and power plant switch 54 , may operate to connect the load to power plant 42 .

Power system 30 includes a power plant controller 66 and a switch controller 70 . A power plant controller 66 is primarily associated with the power plant 42 and controls the operation of the power plant 42 . Switch controller 70 is primarily associated with the ATS, including utility switch 50 and power plant switch 54 .

Section 1 - Objects As shown in Figure 2, the components of the power system 30 are identified as objects. A power system generally includes five object types: source objects, bus objects, switch objects, load objects, and transformer objects. Power system 30 does not contain transformer objects, but other power systems described later in this document do. Within power system 30, each component is identified with an object ID, object name, object type, and object subtype. Object IDs and object names are used by controllers (eg, power plant controller 66 and switch controller 70) to identify components. The object type defines which parameters of the object are configurable.

Each object type is responsible (function) for the operation of power system 30 . Each object type also has attributes that define the identity and rating of the object. Note that most, if not all, objects in power system 30 are machines. Utility source bus 38, power plant source bus 46, and load bus 62 are bus object types, important in the operation and regulation of power system 30, but technically not machines. Power system 30 itself may also be considered an object, as may controllers (eg, power plant controller 66 and switch controller 70). An object type becomes a container for the functionality it owns.

As shown in FIG. 3, each instance of an object type can include a number of functions, parameters, or attributes that can be customized to describe the behavior of individual objects within a power system (eg, power system 30). In other words, power system 74 includes the following object types: source 78, bus 82, switch 86, load 90, transformer 94, and additionally controller (not shown in FIG. 3) and power system 74 Abstracted to be constructed from itself. According to aspects disclosed herein, a power system can be configured as a collection of object instances, one instance for each occurrence of an object of that type. Each object type is a container for a superset of system control functions associated with that object type. The set of functionality contained in an object type is always the same implementation (eg, software code) regardless of where the object instance resides within the power system. The behavior of individual object instances is modified only by changing configuration settings, not by new software code (eg, "C" code).

Object instances are typically distributed to controllers around the system based on which controllers are physically connected. This allows functional abstraction from a specific controller implementation or from a specific installed controller topology. That is, objects and functions are largely decoupled from the controller in which they reside/execute. For example, a power plant controller (e.g., power plant controller 66) may control functions of an associated power plant (e.g., power plant 42) by controlling fueling, aftertreatment, etc., whereas a power plant controller may It may also control the functions of other objects, and other controllers may affect the operation of the power plant controller. Each controller can run multiple instances of different object types. All objects and their functions communicate with each other through a common global data space. A system-wide global data space can be created by network technologies and protocols such as DDS over Ethernet. Thus, the functionality in each object instance works in concert with other object types to accomplish system control and sequencing requirements for operating the power system.

This differs from conventional power system control. Conventional power systems typically rely on a centralized controller that performs power system control functions custom developed/programmed for a particular customer site installation. Object-based distributed control provides a robust control environment and reduces overall system complexity and required customization, while offering more flexible installation opportunities.

Object-specific functions are described below with respect to FIG. Functionality associated with particular object types is exemplary. Other features may be associated with the object type, including additional parameters, customizable settings, and the like. Additionally, some functions may be excluded from object types or included in different object types than those shown in FIG.

SECTION 1.1 - SOURCE OBJECTS Each source object 78 (e.g., utility 34 and power plant 42) within power system 74 includes source state 98, capacity manager 102, synchronizer 106, load sharing 110, source selection 114, and source prioritization 118. , and grid parallelization control 122 functions. In some aspects, more or less functionality may be included in each source object. In some aspects, unused features may be disabled in the control scheme or custom features may be added.

A source state function 98 identifies the current operational state of the source object. A source object needs to be informed of its current operating state for source selection and for other functions to work. Note that the source state function 98 is used by the power system control scheme and does not necessarily indicate or be used by local machine control functions. For example, power generation facility 42 may be operating in a diagnostic state and still effectively operable, but unable to provide power to power system 30 as a source. Source status function 98 then deems power generation facility 42 unavailable, even though power generation facility 42 is currently operating. In some aspects, to fully support the abstraction of source objects in the larger control scheme of power system 30, the source state should be generic regardless of the type of source. For example, a source object may include a superset of the source state, and a subset of the source state may contain details of the source object (e.g., a first subset of the source state of the power plant and a second subset of the source state of the utility). selected based on Sources also have other dynamic information (eg, current capacity, load, etc.) that they share with the power system control function as part of their "state" information. In some aspects, the source status function 98 determines whether the source is ready to be called when needed, whether the source is available based on sensors and has had time to stabilize, and whether the source has failed. and/or whether the source is unavailable (eg, due to shutdown failure or not in automatic mode).

Capacity manager function 102 provides a dynamic model of available capacity within power system 30 . Continuous management of capacity online is important. The required power capacity influences the determination of how many sources (in order of priority) are connected to a load bus object (eg, load bus 62). If there is not enough online capacity to not only carry the current load, but also to accept the additional load without overloading the power system 30 before additional sources (if available) can be brought online. not. Heavy duty applications may require an on-line backup source to cover unexpected and sudden loss of the source. Inputs to the decision to add sources or remove sources include:
-What are the individual source capacities? Some source objects can be dynamic, such as batteries, solar arrays, wind power sources.
-What is your current total online capacity?
-What is the current total load?
- What is your current online reserve capacity (total capacity - load)?
- What is the desired level of spare capacity?
- Do you need protection against unexpected loss of any one source? two sources?
-If the grid is connected, what is the grid power set point?
-Is there a notification that a large load step is coming? how much is that load?
- Is there notification that a significant loss of source capacity will occur (eg, reduced source output level, reduced solar influx, reduced wind speed, or limited battery discharge)?
-Does the source need to be intentionally offline (eg for inspection)?
-If this is a black start, how much capacity should I add first? everything? Source selected?

A synchronizer function 106 provides the parameters and status of synchronization of the source object. Traditionally, the power plant controller synchronizes itself to the bus to which it connects or to another single source such as a utility. A single plant controller performs all sensing measurements to achieve this synchronization. In a distributed power system control scheme that supports a variety of single-line topologies or configurations and source types, this functionality becomes a service that can synchronize single or multiple generation units to any sensing point in the power system. Synchronizer function 106 enables communication of synchronization parameters between controllers within power system 30 to enable comprehensive synchronization and distributed control. That is, the sensing and synchronization initiation can be done in other controllers. Additionally, the synchronizer function 106 identifies whether the source object can be synchronized. The system needs to know which sources it can call to synchronize for the purpose of parallelizing the sources to the live bus. Synchronization can include any ability to match frequency, match frequency offset, match voltage, or match phase. Synchronization is not all-inclusive.

The load sharing function 110 identifies whether a source object is capable of maintaining a nominal voltage and frequency while sharing load among other load sharing sources. Typically, the source object must also be able to form a grid to be used in load sharing.

Source selection function 114 combines source prioritization, source status, and power capacity management information to output a list of sources that should be online. If the source needs to change, the process of bringing the source online or offline is handled by other downstream functions (eg, routing and ordering control associated with the bus object).

A source prioritization function 118 provides a listed priority of available source objects. Every source has a valid priority number allocation that is used to determine in which order the sources should be called depending on the state of the other sources and how much load they have. This priority number may be dynamic or static. Priority allocation is driven by what the current objectives are for the operation of the power system. For several purposes, the control system can calculate priority. For other more complex objectives/computations, external optimization algorithms (eg cloud or edge computing devices, etc.) may set the source prioritization. Some possible locally managed purposes include:
- Implement systems to maximize contributions from renewable resources.
- Run the system so that not all machines are running at the same time for service.
- Run the system so that all machines maintain approximately equal amounts of wear.
- Execute the system to maximize the useful life of the asset.
- Run the system to minimize operating costs.
- Run the system based on dynamic prioritization set by an external optimization algorithm.

Grid parallelization control function 122 specifies which source types can be run in parallel with other source object types or subtypes. For a given power system, limitations are often imposed on which sources can operate in parallel with each other and how long they can operate. To solve the general problem of any power system, we need a source of N^2 matrices so that we can construct the permissible combinations. For example, the grid parallelization feature of the source object has the following options: OT = open transition, HCT = hard closed transition (less than 100 ms overlap), SCT = soft closed transition (limited by maximum parallel time). ), all = all modes allowed, or EP = extended parallel (no time limit).

Section 1.2 - Bus Objects Each bus object 82 (e.g., utility source bus 38, generating equipment source bus 46, and load bus 62) within power system 30 has bus status 126, path status 130, router 134, fault bus access 138, , and system routing table 142 functions. In some aspects, more or fewer functions may be included in each bus object. In some aspects, unused features may be disabled in the control scheme or custom features may be added.

A bus state function 126 of any bus object 82 is required by switch control logic and other functions such as load addition/limiting. The electrical state of each bus object 82 is determined by a bus state algorithm. Possible bus states include available, faulty, faulty, or decaying. The load bus router function can use the bus status as part of determining the transition type. The switch action processing function can use the busbar status to determine whether the switch object can be considered for closing.

Path status function 130 identifies the paths by which power can flow through power system 30 from a source to a load. A path status function 130 identifies the status or health of each available path so that the path can be activated or deactivated. Possible states include unknown, disconnected, undisconnectable, connected, and/or unconnectable. The state of each path is determined by a path state algorithm. Path status can be used by load bus routers to select viable paths. If the path cannot be connected, the load bus router can select the next highest priority path (if it is available).

One central concept of power system 30 is a sequencing control that identifies paths connecting load buses and sources and enables and/or disables paths by controlling switches between closed or open states. It is a concept. Switch logic (e.g., stored in switch controller 70) causes the switches (e.g., utility switch 50 and power plant switch 54) to be safely closed (e.g., synchronizer service request, synchronization check, fault bus closure, etc.). etc.). Router function 134 determines which routes to enable or disable based on the current source selection. The router function 134 may also determine what type of transition (eg, open transition, closed transition, etc.) is occurring and participate in sequencing the transitions. Router function 134 is shown owned by load bus object 82 . In some aspects, the router function 134 can operate as a flow master function that can run on multiple controllers for redundancy or can be associated with multiple different object types. A router function 134 functions between the load bus and the source. In power systems where the load bus has individual load feeders beneath it, the distributed load addition/shedding feature is responsible for managing the connection and disconnection of load circuits individually. Additionally, in some aspects the load itself is connected and disconnected by the router function.

In some aspects, a source object 78 or a load object 90 may request a route hold to keep a particular route connected. If no other high priority reason exists to invalidate the route, the route is allowed and remains valid until the load object 90 or source object 78 indicates that the route is no longer needed. A source object 78 may, for example, request path holding to ensure a minimum amount of running time with load, in order to prevent adverse life/maintenance impacts. A load object 90 can request path hold, for example, to ensure that the load object 90 remains powered continuously for a minimum amount of time to recharge the UPS battery. . The load object 90 can also request path hold if the power system is configured to require manual intervention for retransmission.

A fault bus access function 138 (alternatively called first start) prohibits all other source objects 78 (e.g., all other generating equipment) from closing to a fault bus, while allowing a single live source object 78 (eg, power plant 42) to its fault bus. In distributed power system control schemes that support a variety of single-wire topologies or configurations and source types, the fault bus access function 138 can be generalized and can be used between the live side and the faulty side or even between two faulty sides. It serves as a service for anywhere in power system 74 that needs to close switch/breaker object 86 anywhere in between. The fault bus access function 138 coordinates and mediates the closure of a single live source to energize the fault bus while preventing all other live sources from closing to that bus until the operation is complete. function to Fallbacks can also be included in case of failure scenarios.

A system routing table function 142 defines the available routes presented on a single-line topology. A system routing table function 142 lists all possible connection paths between load bus objects 82 and individual source objects 78 . A system routing table function 142 provides a routing table for obtaining power from source objects 78 to load bus objects 82 and is used by load bus routers. The system routing table function 142 can be programmed into all controllers or a subset of controllers in the power system 74 by tools that include a user interface. Ideally, the tool has a graphical interface and a library of system objects that can be used to draw the single-line topology. The tool can then automatically calculate the routing table.

Section 1.3 - Switch Objects Each switch object 86 (e.g., utility switch 50 and power plant switch 54) within the power system 74 implements three switch functions, including switch state 146, synchronization check 150, and switch action processing 154 functions. Define. In some aspects, more or less functionality may be included in each switch object 86 . In some aspects, unused features may be disabled in the control scheme or custom features may be added.

The switch state function 146 indicates the position of the switch object 86 if the switch object 86 is in use, the position of the main contacts of the switch object 86, if a closing motion is pending, and/or if the switch object 86 is Identify the switch fault if it is prohibited to close.

Synchronization check function 150 synchronizes the two live circuits by verifying that voltage, frequency, and phase angle are matched to levels that are safe for the installation (e.g., mechanical/electrical stress) and do not cause unacceptable power fluctuations. Allow closure of the source object 78. Synchronization check function 150 is typically performed using measurements of both source objects 78 made in a single controller. This synchronization check function 150 can be a completely local function in the associated controller with sensing access or visibility to both sides of the connected switch object 86 .

Switch operation processing function 154 controls the operation of switch object 86 . Based on the system routing table function 142 , the switch object 86 is opened, closed, or does nothing based on the switch action processing function 154 . The switch action processing function 154 also initiates subsequent actions such as a sync check function or a fault bus access function 138 to wait for the completion of an unloaded output change to close or allow opening. . Additionally, switch operation processing function 154 monitors bus reserve capacity by calculating the capacity available on bus object 82 (eg, the difference between the source capacity rating and the amount of load currently on the bus). . Bus reserve capacity can be used to determine whether to allow pending closures to occur. If there is not enough spare capacity upstream of the switch object 86 to carry the downstream load, the switch will not close. Some scenarios where it applies are in any switch object 86 that energizes a faulted load when closed.

Section 1.4 - Each load object 90 (e.g., load 58) within the load object power system 74 includes a load condition function 158, a load decay function 162, a load add/limit function 166, and a sensitive load disconnect function 170.4 Define one load function. In some aspects, more or less functionality may be included in each load object 90 . In some aspects, unused features may be disabled in the control scheme or custom features may be added.

The load status function 158 identifies the status of load objects 90 as energized, blacked out, failed, or decaying, and determines all load objects 90 connected to a common or shared bus object 82 . Once the load state function 158 has determined which load objects 90 are connected, the current state of all connected load objects 90 is determined.

The load decay function 162 determines when the load object 90 has been unpowered and disconnected from the source long enough to allow reconnection of the load object 90 to the live source. For example, time is given for the motor load to stop rotating before reenergizing the motor load to avoid undesirable operational/equipment stress.

The load add/limit function 166 determines whether the load demand (i.e., from the connected source objects 78) is high or low compared to the available power, and adjusts the current on the common bus object 82 accordingly. may be interfaced with the load dampening function 162 to interrupt the The load add/limit function 166 serves to add (ie, connect) load circuits as capacity permits and limit (ie, disconnect) load circuits when system capacity is overloaded. Load addition/limiting function 166 may be an independent function or may utilize router function 134 .

The sensitive load disconnect function 170 controls when a sensitive load is directly connected to the load bus object 82 . In the sensitive load object 90 scenario, the sensitive load disconnect function 170 works with the upstream switch object 86 to control the opening, closing, and other actions to give control to the sensitive load object 90 . connect. In other words, if a load circuit has a sensitive load designation, rather than remain connected to a potentially only partially failed source, such as a brownout or single-phase operating conditions, , immediately disconnects (i.e. opens) upon detection of a power failure.

Section 1.5 - Transformer Objects Each transformer object 94 within the power system 74 defines four transformer functions, including ratio 174, winding type 178, X/R ratio 182, and rating 186 functions. In some aspects, more or less functionality may be included in each transformer object 94 . In some aspects, unused features may be disabled in the control scheme or custom features may be added. A transformer object 94 may be responsible for determining and communicating its current state. In many aspects, the transformer object 94 has no direct control action. Power system performance benefits from (electrically) knowing the location of the transformer object 94 and from knowing the transformer object 94 specifications. For example, a sync/sync check may want to know about transformer object 94 for a 30 degree shift in delta-y. The +30 or -30 decision is automatically made depending on the transformer type designation. Synchronization/synchronization check also wants to know the transformation ratio function 174 for voltage matching. Power flow management may want to know the X/R ratio function 182 in order to better balance load sharing when there are different X/Rs in the source paths.

Section 2 - System Architecture The object-based abstraction described above can be applied to any power system architecture. FIG. 4 shows power system 190 that includes more components/objects than power system 30 shown in FIG. The object ID, object name, object type, and object subtype for each object in power system 190 are shown in FIG. Power system 190 includes four source objects, including utility 194 , first power plant 198 , second power plant 202 , and third power plant 206 .

Power system 190 includes nine switch objects. The five switch objects are source switches, utility switch 210 connected to utility 194, first power plant switch 214 connected to first power plant 198, and second power plant 202. a second power plant switch 218 connected to a third power plant switch 222 connected to a third power plant 206; and a power plant branch switch 226 coupled to each. The four switch objects are load switches, including first load switch 230 , second load switch 234 , third load switch 238 and fourth load switch 242 .

A transformer object 246 is connected between the third generator switch 222 and the power plant branch switch 226 . In some aspects, power system 190 may include more than one transformer object.

Power system 190 includes eleven busbar objects. The power plant branch bus 250 is connected between the first power plant switch 214, the second power plant switch 218, the transformer 246 and the power plant branch switch 226, and the transformer bus 254 is connected to the third power plant switch. Connected between switch 222 and transformer 246, load branch bus 258 is connected between utility switch 210 and power plant branch switch 226, and between first load switch 230, second load switch 234 and third load switch 234. A utility bus 262 is connected between the utility 194 and the utility switch 210, and a first generating set bus 266 is connected between the first generating set load switch 238 and a fourth load switch 242. 198 and the first power plant switch 214, the second power plant bus 270 is connected between the second power plant 202 and the second power plant switch 218, and the third power plant A facility bus 274 is connected between the third power plant 206 and the third power plant switch 222, and a first load bus 278 is connected between the first load and the first load switch 230. , a second load bus 282 is connected between the second load and the second load switch 234, and a third load bus 286 is connected between the third load and the third load switch 238. , and a fourth load bus 290 is connected between the fourth load and the fourth load switch 242 .

The power system 190 also includes a first power plant controller 294, a second power plant controller 298, a third power plant controller 302, a utility switch controller 306, a power plant branch switch controller 310, and a load branch controller 314. Contains 6 controller objects. Control of all objects within power system 190 is accomplished using controller objects, and the functionality of each object type is assigned to a specific controller, as described in more detail below. Coordination and implementation of object functionality can be done through a distributed control scheme that utilizes all or some of the controller objects. The distributed control scheme is also described in more detail below.

Each of the objects in power system 190 can be configured using settings within the controller to represent the actual machine and bus function. This allows the power system 190 to be accurately controlled using settings and configurations designed based on the single wire topology, rather than requiring a custom programmed control system.

Section 3 - The Path Power System 190 includes a number of interconnected objects that provide pathways or pathways through which power can flow from source objects to load objects. As shown in FIG. 6, a system routing table (eg, created by the system routing table function 142 of the bus object) lists all possible routings between load buses and individual sources for a given power system. List routes. Enabled attributes are settings that allow a route to be disabled. The Path ID attribute is a combination of a Load Bus Identifier and a Source Identifier. Path priority is the setting used when there is more than one path from the load bus to the source. Route priority has a default value derived from the number of switches on the route, but may be changeable by the user. For example, the more switches, the lower the priority.

The system routing table provides information to the load bus routers so that they know which route to reach the various sources (so the load bus router can choose which route to connect the desired sources to). to know if it should be enabled). The system routing table is also used by the switch action process so that it knows what routes it "is" on so that the switch action process can respond appropriately to the valid route list generated by the router function. used by

The power system 190 shown in FIG. 4 defines four available paths depicted in FIG. These paths define all available power paths to provide power to the load branch bus 258 from available source objects. Although all paths in FIG. 6 are shown as available (Y), in some aspects paths may be used if the source object is offline (e.g., a shutdown has occurred in utility 194). Not possible (N). A first route 320 is given route ID LB1.G1, route priority 1, and defines route path LB1-SW4-B1-SWG1-G1. The path ID generally indicates a point-to-point path (e.g., LB1.G1 indicates that the path connects first power plant 198 and load branch bus 258) or another naming standard as desired. can be used. Path priority is set to 1 because multiple paths between sources and loads are not possible in power system 190 . The path path of first path 320 is that power flows from first power plant 198 through first power plant switch 214 , power plant branch bus 250 , power plant branch switch 226 , and to load branch bus 258 . Define

A second path 324 is given a path ID LB1.G2, generally indicating that power flows from the second power plant 202 to the load branch bus 258 . The route is activated and has a priority of 1. The route path shows that power flows from the second power plant 202, through the second power plant switch 218, the power plant branch bus 250, the power plant branch switch 226, and to the load branch bus 258, LB1-SW4. -B1-SWG2-G2.

The third path 328 is given path ID LB1.G3, generally indicating that power flows from the third power plant 206 to the load branch bus 258 . The route is activated and has a priority of 1. The route path shows that power flows from the third power plant 206, through the third power plant switch 222, the power plant branch bus 250, the power plant branch switch 226, and to the load branch bus 258, LB1-SW4. -B1-SWG3-G3. As illustrated by the third path path, passive objects such as transformer 246 may be excluded from the path path. In some aspects, passive objects, or all objects, may be included in the route path definition.

A fourth path 332 is given a path ID LB1.U1, generally indicating that power flows from the utility 194 to the load branch bus 258. FIG. The route is activated and has a priority of 1. The routing path is LB1-SWU1-U1, indicating that power flows from utility 194 through utility switch 210 to load branch bus 258. FIG.

Therefore, the routing table for power system 190 includes four possible routes: first route 320 , second route 324 , third route 328 and fourth route 332 . a power plant controller 294, a second plant controller 298, a third plant controller 302, a utility switch controller 306, a plant branch switch controller 310, and a load branch controller 314; The control system of system 190 utilizes path tables to efficiently control all objects in various paths to achieve the desired results. For example, when utility 194 is taken offline, power system 190 recognizes the need for more power and switches first path 320, second path 324, and third path 328 to generate power. Either can be enabled. Path path validation provides an automated and coordinated solution to the actuation or control of all objects residing on the validated path path.

To further demonstrate the routing table concept, a complex power system 336 is shown in FIG. 7 in a single-line topology, either grid-based or otherwise provided from an external source (eg, a power plant). It includes a first utility 340 and a second utility 344, which may be a power source. Power system 336 also includes first power plant 348 , second power plant 352 , and third power plant 356 . In some aspects, the power plant is diesel-powered or powered by an internal combustion engine that burns another fuel type. Power system 336 also includes a solar array or solar station 360 and a battery bank 364 . Other power sources such as wind power, water power, and any other power source may be connected to the power systems contemplated herein. Power system 336 includes seven source objects. In some aspects, more or less than eight source objects are included.

Power system 336 also selects first utility switch 368 selectively coupling first utility 340 , second utility switch 372 selectively coupling second utility 344 , first power plant 348 . first power plant switch 376 selectively coupling, second power plant switch 380 selectively coupling second power plant 352, third power plant switch selectively coupling third power plant 356 384 , a solar switch 388 that selectively couples the solar station 360 , and a battery switch 392 that selectively couples the battery bank 364 , including seven corresponding source switches.

The power plant branch bus 393 is connected to the first power plant 348 via the first power plant switch 376, the second power plant 352 via the second power plant switch 380, and the third power plant switch 384. and configured to communicate with the third power generation facility 356 via transformer 394 . Plant switches 376 , 380 , 384 provide selective coupling between plant source objects and plant branch bus 393 .

The power plant branch bus 393 is in selective communication with the first load bus 396 via the first power plant branch switch 398 and the second load bus 400 via the second power plant branch switch 402 . built to Load bus switch 404 provides selective communication (ie, connection) between first load bus 396 and second load bus 400 .

Four load switches 408, 412, 416, 420 are connected to the first load bus 396 and selectively provide power to four corresponding loads. Four load switches 424, 428, 432, 436 are connected to the second load bus 400 to selectively provide power to four corresponding loads. Although four loads are shown coupled to each load bus, more or less than four loads are contemplated. Each of the loads may include a single power consumer or may include a load system (eg, a microgrid supplied by power system 336).

Each of the objects defined on the single-line topology shown in FIG. 7 has attributes or parameters as described above when the object is added to the single-line topology such that the functionality of the object is known within power system 336. Allocated. An object table is created that provides the object name (eg, the first power plant 348 is named S1, etc.) and the parameter list. Additionally, power system 336 includes controllers associated with various objects for operating and controlling components.

Power system 336 includes more path dynamics than power system 190 shown in FIG. Power system 336 defines 24 separate paths shown in FIG. Eleven paths connecting the first load bus 396 are shown in FIG. The path connecting the second load bus 400 is not shown in FIG. 7 for greater clarity. The path defined by power system 336 more clearly illustrates the concept of priority. For example, path R1.7 connects first plant branch switch 398, plant branch bus 393, and second plant branch switch 398 to couple first load bus 396 with second utility 344. Since it contains 402, it contains route priority 2. Alternatively, route R1.8 contains route priority 1 because the path is more direct between first load bus 396 and second utility 344 .

In the example shown in FIGS. 7 and 8, the load bus router (eg, load bus router 134 described above) for each of the paths is assigned to the associated load bus. In other words, all paths terminating on the first load bus 396 are controlled by the load bus router associated with the first load bus 396, and all paths terminating on the second load bus 400 are controlled by the second load bus 400. is controlled by the load bus router associated with the load bus 400 of . One tenant of the ordering control concept is that there exists a path connecting the load bus and the source, and that enabling or disabling the path functions to open or close a switch on the path. . The switch logic is responsible for controlling each individual switch (eg, to close according to a desired sequencing including synchronizer service requests, synchronization checks, fault bus closures, etc.). The load bus router decides which routes to enable or disable based on the current source object selection. The load bus router may also determine what type of transition (open transition, closed transition, etc.) is occurring and participate in sequencing the transitions. A load bus router function is owned by or assigned to a load bus object and can act as a flow master function that can run on multiple controllers for redundancy. Note that the load bus router functions between the load bus and the sources. In applications where the load bus has individual load feeders underneath, the distributed load addition/limiting feature may be responsible for managing the connection/disconnection of the load circuits individually. In some aspects, the load itself is connected and disconnected by the router function 134 .

Individual source or load objects may request route holding to keep a particular route connected. If no other high priority reason exists to invalidate the route, route retention is allowed and the route remains valid until the load or source object indicates that the route is no longer needed. . A source may require path holding to ensure a minimum amount of run time with load, eg, to prevent adverse life/maintenance impacts. A load object may request path hold to ensure that the load object remains powered continuously for a minimum amount of time, for example to recharge a UPS battery. A load object may also request route preservation if the system is configured to require manual intervention for retransmission.

In some aspects, the default route priority is simply the sum of the number of switches in the route. If there are multiple paths to a source, the algorithm for choosing which path to invoke depends on many factors, including path priority. Other factors in route selection may include the current state of the system and switches. For example, if there are more open switches on paths set to high priority (i.e. low priority number) compared to paths with low priority (i.e. high priority number), then high priority It may make sense to use a lower priority path with degrees (eg, select route R1.7 instead of route R1.8). In some aspects, the following factors are used: 1) select a route using the fewest open switches, or 2) use the number of switches in the path, or 3) custom priority settings. can be included in route selection, such as using Failure modes can also be taken into account. If a higher priority path with a lower priority number fails to connect, the power system will attempt a next priority path with a higher priority number, provided other conditions allow the path to become active. It can return to a lower path (eg, path connections do not cause any source or operating mode conflicts).

The load bus router may also resolve conflicts that may arise. Conflicts are generally resolved by a clear definition of priority. Sources have priorities, loads have priorities, routes can have priorities (e.g. route priority number if there are redundant paths), reasons to act have a priority hierarchy There is In some aspects, a load bus router may handle contention. For example, load bus routers may inhibit loops (ie, parallel paths) that can occur when a system has redundant paths and multiple load buses requiring paths. Some loops may allow rapid overlapping transitions between paths.

The use of paths allows for increased control efficiency and increases the reliability of power system configuration and commissioning.

SECTION 4 - SIGNAL FLOW Operation of a power system according to the present disclosure identifies separate objects in the system architecture, and authority for controlling operation of the system can be distributed among various controllers of the power system. The details of distributed control are further detailed below. FIG. 9 shows a high level logic scheme 440 for controlling power delivery from a source object to a load bus object using the path level functions for controlling paths described above. As used herein, the phrase "path-level functionality" refers to functionality performed by objects of the power system to achieve coordinated functionality of the power system. The path-level functions of each object are detailed further below. Generally, the source manager is responsible for indicating to the load bus router which sources should be connected to the load bus. The load bus router enables and disables routes to specified sources. The switch action processing function determines for each switch to open, close, or do nothing depending on which path is enabled or disabled. The following description refers to functional blocks (eg, path-level functions) that interact to implement control of the power system.

As shown in Figure 9, the source manager 444 is responsible for monitoring the status of all sources, selecting sources, and ensuring that there is sufficient capacity. One of the primary outputs of source manager 444 is load bus source list 448 (ie, desired source connection list), which lists sources that should be connected to the load bus. The source compatibility matrix 446 defines what types of transitions are allowed between two sources and which sources can be effectively parallelized. For example, a system with N sources has 1/2*(N^2-N) combinations to define fitness. Source compatibility matrix 446 is used by both source manager 444 and load bus router 452 . In some aspects, the source manager 444 uses the source compatibility matrix 446 to avoid selecting disallowed source combinations.

If the load bus source list 448 does not match the sources currently connected (or expected to be connected) to the load bus, the load bus router 452 diagnoses the mismatch and identifies the currently connected sources. Determine the next step in the matching load bus source list 448 procedure. There are several possible scenarios in which the currently connected sources and the load bus source list 448 do not match. For example, 1) a source has failed and is replaced by another source, 2) extra capacity is needed and so a source is added, or 3) a test transmission with a load is started. . Once the next steps have been determined, load bus router 452 updates two primary outputs: valid path list 456 and transition type 460 . Valid route list 456 contains only routes that should be connected (ie, desired routes). The transition type 460 is then received by a switch action processing function 464 that determines the required changes to the valid path list 456 based on the transition type 460 . Values for transition type 460 include none, open transition, hard closed transition, soft closed transition, or extended parallel. In some aspects, one switch operation processing function 464 resides in each switch controller. In some aspects, there may be multiple instances of switch action processing function 464 (e.g., one per switch object, many per controller object, etc.) such that, in total, there is a switch action per switch in the system. There is one instance of processing function 464 . Additionally, in some aspects, the load bus router 452 uses the source compatibility matrix 446 when a full source transition is requested. The load bus router 452 checks the source suitability matrix 446 for all combinations of sources involved and selects the lowest common denominator of transition type. In some embodiments, the source manager 444 can override the results of the source suitability matrix 446 and use the reason output signal to choose fewer transition types. Options for setting the source compatibility matrix 446 may include the following. OT = open transition source cannot be parallelized, HCT = hard closed transition - source can only be parallelized for less than 100ms, SCT = soft closed transition - achieve load transition that changes output (maximum parallel time applies) and/or EP = Enhanced Parallelism - the source can be parallelized indefinitely. Other options or configuration details may vary depending on system implementation.

Switch action processing function 464 determines whether the associated switch should be closed, opened, or left in its current state based on valid path list 456 . The switch action processing function 464 knows on which path the switch "is" (ie, the path the switch is part of), which the switch action processing function 464 obtains from the system routing table 468 .

When switch action processing function 464 determines that the switch should be closed, switch action processing function 464 first determines if the switch is positioned on the valid path and is currently open. If the switch is on the valid path and is open, the switch action handler 464 must take appropriate action to ensure that the switch is safely closed. Bus status 472 on both sides of the switch determines what can happen. Closure can occur only under bus state 472 conditions of available-failed, available-available, or failed-failed. Once the bus status 472 conditions are met, such as obtaining an exclusive fault bus closure grant 476, meeting the synchronization check condition 480, and checking for sufficient upstream capacity 484 to carry the downstream load. Additional conditions are required. When the conditions are met, the switch is called to close, and mechanism-specific logic (eg, automatic transfer switch (ATS), circuit breaker, contactor, etc.) in power switch control 488 functions to close the switch.

If switch action processing function 464 determines that the switch should be open, switch action processing function 464 first determines whether the switch is closed and not positioned on a valid path. If the transition type 456 is an enhanced parallel or soft close transition, the switch is commanded to open by the power switch control 488 after the load output change status 492 indicates that the load power down through the switch is complete. be. If the transition type 456 is a hard closed transition or open transition, the switch is commanded to open immediately.

Switch state 496 is determined by a switch state algorithm. Possible switch state 496 values include unknown, open, unable to open, closed, and unable to close. The switch state 496 is processed by the switch action processing function 464 through the valid route list 456 and system routing table 468 to determine whether to attempt to open the switch, close the switch, or do nothing to the switch. used in combination with

The path state 500 for each path is determined by a path state algorithm. Possible path states 500 include unknown, disconnected, undisconnected, connected, and unconnectable. Path state 500 is used by load bus router 452 to select a viable path. If the path cannot be connected, load bus router 452 selects the next highest priority path if it is available.

A synchronizer function 504 resides in or is assigned to a source that has the ability to adjust the voltage, frequency, and phase angle output of the source to match the capabilities of another source (eg, a power plant). The switch operation process 464 requests this function when attempting to close between two live/available sources.

Section 5.1 - Controller As shown in FIG. 10, controller 508 represents the controller used by the power system in control scheme 440 . Controller 508 may be separate from or included in at least one other controller in the power system. As discussed further below, the control distribution schemes considered herein are computational power, redundancy, and the ability to perform general control computations within a single controller circuit or multiple controllers within a power system. allow sharing between The function and structure of controller 508 are described in more detail in FIG.

Referring now to FIG. 10, a schematic diagram of controller 508 is shown in accordance with an illustrative aspect. As shown in FIG. 10, the controller 508 includes a processing circuit 512 having a processor 516 and a memory device 520, a control system 524 having a circuit A 528, a circuit B 532 and a circuit C 536, and a communication interface 540. . In general, the controller 508 is constructed to control the operation of associated objects to work with the larger power routing control scheme 440 .

In one configuration, Circuit A 528 , Circuit B 532 , and Circuit C 536 are embodied as a machine-readable or computer-readable medium executable by a processor, such as processor 516 . As described herein, among other uses, machine-readable media facilitate performing certain operations to enable the transmission and reception of data. For example, a machine-readable medium may provide instructions (eg, instructions, etc.) for obtaining data, for example. In this regard, the machine-readable medium may include programmable logic that defines the frequency of data acquisition (or data transmission). The computer-readable medium can be written in any programming language, including but not limited to Java, and any conventional procedural programming language, such as the "C" programming language or similar programming languages. may contain code. Computer readable program code may be executed on one processor or on multiple remote processors. In the latter scenario, the remote processors can be connected to each other via any type of network (eg, CAN bus, etc.).

In another configuration, Circuit A 528, Circuit B 532, and Circuit C 536 are embodied as a hardware unit, such as an electronic control unit. As such, Circuit A 528, Circuit B 532, and Circuit C 536 may be one or more including, but not limited to, processing circuitry, network interfaces, peripheral devices, input devices, output devices, sensors, and the like. can be embodied as a circuit component of In some aspects, circuit A 528, circuit B 532, and circuit C 536 are one or more analog circuits, electronic circuits (e.g., integrated circuits (ICs), discrete circuits, system-on-chips (SOCs)). circuits, microcomputers, etc.), communication circuits, hybrid circuits, and other types of "circuits." In this regard, Circuit A 528, Circuit B 532, and Circuit C 536 may include any type of component for implementing or facilitating the performance of the operations described herein. For example, the circuits described herein may include one or more transistors, logic gates (eg, NAND, AND, NOR, OR, XOR, NOT, XNOR, etc.), resistors, multiplexers, registers, capacitors, inductors, diodes, wires, etc.). Circuit A 528, Circuit B 532, and Circuit C 536 may also include programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, and the like. Circuit A 528, Circuit B 532, and Circuit C 536 may include one or more memory devices for storing instructions executable by the processors of Circuit A 528, Circuit B 532, and Circuit C 536. One or more memory devices and processors may have the same definitions given below with respect to memory device 520 and processor 516 . In some hardware unit configurations, Circuit A 528, Circuit B 532, and Circuit C 536 may be geographically distributed throughout separate locations in the power system. Alternatively, as shown, Circuit A 528 , Circuit B 532 , and Circuit C 536 may be embodied in or within a single unit/enclosure, shown as controller 508 .

In the depicted example, controller 508 includes processing circuitry 512 having a processor 516 and a memory device 520 . Processing circuitry 512 may be constructed or configured to execute or implement the instructions, directives, and/or control processes described herein with respect to circuitry A 528, circuitry B 532, and circuitry C 536. The depicted configuration represents Circuit A 528, Circuit B 532, and Circuit C 536 as a machine or computer readable medium. However, as described above, in the present disclosure, Circuit A 528, Circuit B 532, and Circuit C 536, or at least one of Circuit A 528, Circuit B 532, and Circuit C 536 are configured as hardware units. This example is not intended to be limiting, as other aspects are also contemplated. All such combinations and variations are intended to be included within the scope of this disclosure.

Hardware and data processing components (e.g., processors) used to implement the various processes, operations, exemplary logic, logic blocks, modules, and circuits described in connection with the aspects disclosed herein. 516) may be general purpose single chip processors or general purpose multichip processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete gates or transistor logic. , discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, or any conventional processor or state machine. A processor may also be implemented as a combination of computing devices, such as a combination DSP and microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. obtain. In some aspects, one or more processors may be shared by multiple circuits (eg, Circuit A 528, Circuit B 532, and Circuit C 536 may, in some exemplary aspects, have different memory may include or otherwise share the same processor(s) that may execute the instructions stored or otherwise accessed by the region). Alternatively or additionally, one or more processors may perform or otherwise be configured to perform certain operations independently of one or more co-processors. In other exemplary aspects, two or more processors may be coupled via a bus to enable independent, parallel, pipelined, or multithreaded instruction execution. All such variations are intended to be included within the scope of this disclosure.

Memory device 520 (e.g., memory, memory unit, storage device) is one or more for storing data and/or computer code for completing or facilitating the various processes, layers, and modules described in this disclosure. It may include multiple devices (eg, RAM, ROM, flash memory, hard disk storage devices). A memory device 520 may be communicatively coupled to processor 516 for providing computer code or instructions to processor 516 for performing at least some of the processes described herein. Moreover, memory device 520 may be or include tangible, non-transitory, volatile or non-volatile memory. Thus, memory device 520 may include database components, object code components, script components, or any other type of information structure to support the various activities and information structures described herein.

Circuit A 528 is responsible for the operation of associated machines or objects 544 . For example, Circuit A 528 may control the operation of a power plant, aftertreatment system, battery bank, switch, or any other object type. Control actions determined by circuit A 528 are communicated to object 544 via communication interface 540 .

Circuit B 532 is responsible for determining the object controls assigned to Circuit B 532 . In power systems utilizing distributed control, Circuit B 532 may communicate with other controllers 548 and/or sensors 552 to determine which objects are under the direction and control of controller 508 .

Circuit C 536 is responsible for implementing power routing control 440 and communicates with external systems via communication interface 540 to enable/disable paths and complete other operations of power routing control scheme 440. connect.

Although various circuits with specific functions are illustrated in FIGS. 9 and 10, it is understood that controller 508 can include any number of circuits to accomplish the functions described herein. should. For example, the activities and functions of Circuit A 528, Circuit B 532, and Circuit C 536 may be combined in multiple circuits or as a single circuit. Additional circuitry with additional functionality may also be included. Additionally, the controller 508 may further control other operations beyond the scope of this disclosure. In some aspects, the circuits described herein are one or more memory devices coupled to one or more processors such that when executed by the one or more processors, the present including one or more processing circuits including one or more memory devices configured to store instructions that cause one or more processors to perform the operations performed herein and described in connection with the circuits obtain.

As noted above, in one configuration the "circuitry" may be implemented on a machine-readable medium for execution by various types of processors, such as processor 516 of FIG. An identified circuit of executable code may, for example, comprise one or more physical or logical blocks of computer instructions which may, for example, be organized as an object, procedure, or function. Nonetheless, the executable code of the specified circuit need not be physically located together, but when logically combined with each other, contains the circuit and accomplishes the circuit's stated purpose. , may contain entirely different instructions stored in different locations. In fact, a circuit of computer readable program code can be a single instruction, or many instructions, and even be divided into several different code segments, among several different programs, and across several memory devices. You can disperse. Similarly, operational data may be identified and illustrated herein within circuits, may be embodied in any suitable form, and may be organized within any suitable type of data structure. Operational data may be collected as a single data set, or may be distributed in different locations, including different storage devices, and may, at least in part, simply exist as electronic signals on a system or network.

Although the term "processor" is defined briefly above, the terms "processor" and "processing circuitry" are intended to be interpreted broadly. In this regard, as noted above, a "processor" is provided by one or more general purpose processors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs), or memory It may be implemented as any other suitable electronic data processing component constructed to execute instructions. The one or more processors may take the form of single-core processors, multi-core processors (eg, dual-core processors, triple-core processors, quad-core processors, etc.), microprocessors, and the like. In some aspects, one or more processors may be external to the device, eg, one or more processors may be remote processors (eg, cloud-based processors). Alternatively or additionally, one or more processors may be internal and/or local to the device. In this regard, a given circuit or component thereof may be used locally (e.g., as part of a local server, local computing system, etc.) or remotely (e.g., as part of a remote server, such as a cloud-based server). ) can be placed. As such, "circuitry" as described herein may include components dispersed throughout one or more locations.

Aspects within the scope of the present disclosure include program products including machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media may include RAM, ROM, EPROM, EEPROM, or other optical disk storage devices, magnetic disk storage devices, or other magnetic storage devices, or any other desired medium in the form of machine-executable instructions or data structures. and can include any other medium that can be used to hold or store the program code of and can be accessed by a general purpose or special purpose computer or other machine with a processor. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions include, for example, instructions and data that cause a general purpose computer, special purpose computer, or special purpose processing machine to perform a certain function or group of functions.

Section 5.2 - Controller Allocation Controllers are typically dedicated to one machine. In some cases, a controller may support multiple machines. One concept considered here is that each power system object instance in the power system is most directly associated with a controller, typically an object (i.e. has some IO associated with the object). ) is to be "owned" by the controller. In some cases, the object is a copy or replicated control that runs on multiple controllers and provides redundancy using a distributed master model of distributed control for functions that require master control. Accompanied by

The object model described above allows flexibility of application. For some power systems there is more than one way to allocate controllers to objects. This may be due to deliberate choices in the design of the power system or due to the machines involved. In some embodiments, one controller can possibly handle four switches if load monitoring is not required for each load, otherwise one controller for every one or two switches. can be required.

In a conventional ATS+ power plant system, there are two controllers with assigned objects as shown in FIG. Power system 556 includes utility 560 that provides grid power (e.g., provides alternating current (AC)) and power generation facility 568 that provides alternating current power to power generation facility bus 572 , connected to utility source bus 564 . include. Utility source bus 564 and power generation facility bus 572 are connected to automatic transfer switch (ATS) switch 576 . ATS 576 is also connected to load bus 580 . Automatic transfer switch 576 may be arranged or constructed to provide power to load bus 580 from one of utility bus 564 or power generation facility bus 572 . A load 584 is connected to load bus 580 and consumes power provided by utility 560 or power generation facility 568 . Power system 556 also includes a power plant controller 588 and a switch controller 592 . The power plant controller 588 is primarily associated with the power plant 568 and controls the operation of the power plant 568 . Switch controller 592 is primarily associated with ATS 576 .

As shown in FIG. 12, power system 556 objects are assigned to power plant controllers 588, ATS controllers 592, or both. The only allocation overlap in power system 556 occurs at power generation facility bus 572 (BG1). The overlap occurs because both the plant controller 588 (C1) and the ATS controller 592 (C2) perform sensing of the plant bus 572 (BG1). Therefore, the object-based power routing control scheme described above is implemented for the power plant controller 588 for the power plant 568 and the power plant bus 572, and the object-based power routing control scheme is implemented for the remaining objects. It is implemented on the ATS controller 592 for this purpose.

As shown in FIG. 13, a circuit breaker based, single transmission pair, single generating station power system 596 provides grid power (e.g., alternating current (AC )) and a power generation facility 608 that provides AC power to the power generation facility bus 612 . Utility source bus 604 is connected to utility source breaker 616 and power plant bus 612 is connected to power plant breaker 620 . A circuit breaker is a switch-type object. Utility source breaker 616 and power plant switch 620 are connected to load bus 624 and load 628 is connected to load bus 624 . A single controller 632 (e.g., a power plant controller) manages the entire power system 596 and thus has all the IOs necessary to interface with all five power system objects, as shown in FIG. It owns all functions related to those objects, as shown in the allocation chart.

As shown in FIG. 14, power system 596' is similar to power system 596 of FIG. 13 and is shown with primed numbered components. The power system 596 ′ includes two controllers, a power plant controller 636 and a utility circuit breaker controller 640 . This can occur because the utility circuit breaker 616' is located far from the power plant 608' and the power plant circuit breaker 620'. One advantage of power system 596' is its ability to verify and measure the condition of load bus 624 (LB1). As shown in FIG. 16, the power plant 608 ′, power plant breaker 620 ′, load bus 624 ′, power plant bus 612 ′, and load 628 ′ are assigned to power plant controller 636 . Utility 600 ′, utility breaker 616 ′, load bus 624 ′, utility bus 604 ′, and load 628 ′ are assigned to utility breaker controller 640 .

As shown in FIG. 15, power system 596'' is similar to power system 596 of FIG. 13 and is shown with components numbered with double primes. Power system 596 ″ includes three controllers: power plant controller 644 , utility breaker controller 648 , and power plant breaker controller 652 . This arrangement may be desirable because the utility breaker 616'' and the power plant breaker 620'' are located far from the power plant 608'' and from each other. As shown in FIG. 16, power plant 608 ″ and power plant bus 612 ″ are assigned to power plant controller 636 . Utility 600 ″, utility breaker 61 ″, load bus 624 ″, utility bus 604 ″, and load 628 ″ are assigned to utility breaker controller 648 . The plant breaker 620 ″, the load bus 624 ″, the plant bus 612 ″, and the load 628 ″ are assigned to the plant breaker controller 652 .

As shown in FIG. 17, a power system 190' similar to power system 190 described above with respect to FIG. In addition to illustrating the communication paths, Figure 17 also illustrates the assignment of objects to each controller 294', 298', 302', 306', 310', 314'. For example, the first power plant controller 294' receives information from the power plant branch bus 250', the first power plant bus 266', and the first power plant switch 214', and also receives information from the first power plant switch 214'. Provides information or control signals to switch 214'. No communication arrows are provided for the second power plant controller 298' and the third power plant controller 302' for clarity of illustration. Figure 17 also shows how the load bus router functionality is shared between the utility switch controller 306', the plant branch switch controller 310' and the load bus controller 314'. Similarly, FIG. 17 shows that the load sharing function is distributed between the first power plant controller 294', the second power plant controller 298' and the third power plant controller 302'. . FIG. 18 shows the allocation of objects in power system 190'.

Section 5.3 - Object and Functional Implementation Different methods can be used to implement objects in the power system controller described above. A power system object in this disclosure is a container for functionality related to that object that operates at the level of power system control.

One method of object realization is to have an embedded software application for the controller hard-coded (e.g., compiled) with a fixed (e.g., maximum) number of each type of object along with the full set of functionality each object contains. include. For example, a controller can support up to 2 source objects, 3 bus objects, 2 switch objects, and 2 load objects. In some aspects, a controller may support or be associated with more or fewer objects. If desired, available object options can be left unused. For example, some installations may not require the maximum number of available objects. Which of the object instances available in the controller is used is set at commissioning or configuration time.

Alternatively, the controller may have a more advanced operating system and instantiate objects at runtime only as needed.

An object-based approach allows improved activation and configuration by setup tools. All controllers involved in the power system must know what objects/functions are needed, what objects the controller is responsible for (i.e. allocation), and what objects are in the system's single-line topology (i.e. path map or table). The same object/function software configured to define some further adjustment of behavior by the user with various other settings (e.g. source power output, time limits, capacity, etc.) including code. A computer-based setup tool can be used to define and configure the power system. A setup tool can contain a palette library of all possible system objects and variants thereof. The user selects objects from the library and drags the objects onto the drawing area to create the single-line topology of the power system. Once the user draws the power system and includes where the controller is located, each object is given identification information and other relevant settings by the user. The setup tool can then derive the system routing table. Once the system routing table is generated, the setup tool connects to the power system network where the controllers are on and sends configuration data to each of the controllers. Once the configuration data is uploaded to the controller, control based on the single-line topology and objects begins.

In this method, the object-oriented approach draws a single-line topology, sets all the required attributes for each object, then automatically connects to the system and transfers the appropriate settings to all controllers from a single point of connection. used by the tool to download to The tool contains a palette library of all supported power system objects.

In typical control of power plants and microgrids, power plant scheduling, power routing, transmission control, and load shedding are typically controlled by highly trained and experienced personnel during design and configuration simulations. , often requiring extensive testing to confirm proper operation of the microgrid and sequencing for system stability. Designs are often not transferable to other sites or implementations and subsequent changes or updates to the microgrid system may also require the same level of design and testing, requiring programming and/or configuration. Difficulty and lack of system redundancy.

The tool suggests attributes for each object and allows the user/designer to change the attributes. The tool automatically connects to the system and downloads the appropriate settings to all controllers from a single point of connection to the microgrid so there is no need to go from system to manually configuring the controllers. Tools support the commissioning process and the simulation and/or testing of the resulting designs.

Section 6.1 - Centralized Control The power system described above operates in an object-based framework that provides communication and coordination between objects to implement sophisticated control schemes that improve ease of commissioning and reliability. This section describes various control schemes that can be implemented within the power system framework described above.

As shown in FIG. 19, centralized control scheme 656 includes one controller, conventionally referred to as master controller 660, responsible for telling other controllers 664 what to do. Other controllers 664 are conventionally referred to as slave controllers. The master controller 660 collects all necessary inputs from the other controllers 664 and itself, then executes its algorithms (eg, functions) and then produces outputs that direct the operation of the other controllers 664. Generate. Operation of the power system is entirely dependent on master controller 660 .

As shown in Figure 20, centralized control in a redundant controller scheme 668 includes a master controller 672 and a backup master controller 676 is added to provide redundancy should the master controller 672 fail. Typically, both the master controller 672 and backup 676 execute the same code at the same time and function to check each other. One is called primary master 672 and the other is called secondary master 676 . If the primary master 672 fails, the secondary master 676 will immediately step in and take over control of the other controller 680 . This method can eliminate the single point of failure vulnerability of the centralized control scheme 656 .

In FIGS. 19 and 20, the lines connecting the master and slave controllers indicate that only the master has some communication with the slaves. Slave controllers do not communicate with each other. Communication can include transmission of information and/or signals through a hardwired architecture using a communication link or another communication system.

Section 6.2 - Distributed Control Distributed control in this disclosure refers to control schemes that do not rely on a single controller for the operation of the entire power system. That is, the loss of a single controller can result in a power system regression, but does not render the power system completely inoperable. Figures 21-25 depict three distributed control schemes by which a robust and redundant distributed control power system can be constructed together with an object-based approach.

Section 6.3 - Flow Master Control As shown in Figure 21, the flow master control scheme 684 includes a number of controllers 688 each capable of performing a specific system function, whose function can be any given Such that it only needs to be performed by one "brain" or motion controller at a time. Thus, there is a form of control that can be called centralized control if it is effectively only for individual tasks or functions. The operational controller currently responsible for performing the function is referred to as primary controller 692 . Other controllers 688 that are possible but not currently active primary controller 692 are called participating controllers. Whenever the primary controller 692 fails or is otherwise unable to fulfill its duties to the power system, one of the participating controllers seamlessly steps in and takes over the role of the primary controller 692 . This behavior is described as flow master in that the master controller can flow to any controller 688 that can perform its function.

Each controller 688 currently in a participant's role for a particular system function has three options for how to handle the system function. First, the controller 688 can refuse to perform functions and only begin performing functions when the controller 688 becomes the primary controller 692 . If there is no need for seamlessness when the controller 688 assumes the role of primary controller 692, execution denial will occur. Second, the controller 688 can perform functions asynchronously (relative to the current primary controller 692) and compute outputs even if the outputs are not currently being used. In asynchronous operation, when the controller 688 becomes the primary controller 692, the controller 688 is typically in the same state at the same output as the previous primary controller 692 in a repeat of execution. Third, the controller 688 can operate in lockstep synchronously with the main controller 692 so that any handover is completely seamless.

As shown in FIG. 22, the current primary controller 692 collects all input from all participating controllers 688 and itself. The main controller 692 then calculates outputs/commands for transmission to all participating controllers 688 and itself. Each participating controller 688 may be doing exactly the same as the primary controller 692, except that the algorithm output of the participating controller 688 is not used.

The selection of primary controller 692 may be automatically determined among the controllers in the power system. In some aspects, each controller 688 includes a unique controller or object ID, and the controller 688 with the lowest object ID number is selected as the primary controller 692 .

Section 6.4 - Fully Distributed Control Some power system functions are better suited to a fully distributed control model than master/participant. As shown in Figure 23, in a fully distributed control scheme 696, all controllers 700 that perform a particular system function are equivalent. One feature that makes the controllers 700 completely distributed is that each controller 700 decides what to do for itself, rather than also deciding what to do for the other controllers as is the case with the master controller in flow master control scheme 684. It is to be. A fully distributed control scheme 696 is sometimes referred to as a self-determining approach.

As shown in FIG. 24, in a generalized case of information flow for a fully distributed control scheme 696, each controller 700 may collect all required inputs and compute only its own commands/outputs. provided. Although FIG. 24 only shows what a single controller 700 is doing, each controller 700 is calculating at the same time.

Section 6.5 - Redundant Control Fluid Master Control Scheme 684 and Fully Distributed Control Scheme 696 reduce the impact of a single point controller failure on power system control in many scenarios, but the loss of a single controller can lead to loss of power system power. There is still the potential for significant functional impact. As shown in FIG. 25, a redundant flow master scheme 704 includes multiple controllers 708 each capable of functioning as a master controller 712 . In addition, redundant controllers 716 are installed at key locations in the power system topology. A scheme similar to flow primary control scheme 684 is then used to determine which controller 708 or redundant controller 716 is currently serving as primary controller 712 .

In Figures 21, 23 and 25, the lines between the controllers are intended to represent that each controller communicates with every other controller. The roughly circular representation simplifies the appearance of the system, but is intended to connect each controller with every other controller.

Section 6.6 - Examples Returning now to Figure 17, the power system 190' includes a bus object that includes a load bus router function configured as a flow master type function. Utility switch controller 306', load bus controller 314', and power plant branch switch controller 310' all "own" or are assigned load bus 258', and therefore any of them , may be the primary controller for the load bus router function of load bus 258'. Utility switch controller 306' is identified as the primary controller using a scheme that selects the controller with the lowest ID as the primary controller.

In some aspects, the first power plant controller 294', the second power plant controller 298', or the third power plant controller 302' may also be utilized as the primary controller for the load bus router function. However, the main controller for the load bus router function advantageously provides voltage sensing of the load bus 258' capabilities. The only controllers that provide voltage sensing on the load bus 258' are the utility switch controller 306', the load bus controller 314', and the power plant branch switch controller 310'. If each of these controllers fails, the other controllers cannot serve their purpose of performing the load bus router function. Therefore, in practice, not all controllers are equal, and functions requiring primary control may be drawn from different subsets of all controllers in the power system (depending on function).

Also shown in FIG. 17 is a load sharing function that exists in all source objects and functions in a fully distributed manner. Each of the first power plant controller 294', the second power plant controller 298', or the third power plant controller 302' owns a source object. Each of these three controllers 294', 298', 302' performs an instance of the load sharing function by consuming data from other controllers and from itself, and then for its own use. Calculate the result.

In a more specific example of a distributed control scheme, the purpose of the load sharing function is to have each source share the load evenly. The controller at each source publishes its current load value data. The first power plant controller 294' sums all the loads on the first power plant 198', the second power plant 202' and the third power plant 206' to calculate the average load. The first power plant controller 294' then compares its current load value to the average load. If the current load is less than the average load, the load is not being fully borne. The first power plant controller 294' then functions to increase the power output of the first power plant 198'. The second power plant controller 298' is doing the same thing, determining its own necessary corrections, and so is the third power plant controller 302'. Thus, each controller is simply determining its own behavior, not what other controllers need to do.

A fully distributed or flow-dominant algorithm can have multiple instances within a single controller. Referring to the full distribution example above, a single controller can own two source objects and thus have two separate instances of the load sharing functionality. This still means that each instance of the functionality, even though done in one controller, works in a fully distributed manner. Both sources are lost by the loss of the controller.

For a liquidator function with two instances in a controller, there are two participants that can act as liquidator in that one controller. If that controller fails, there are two fewer participants in the feature's pool.

As used herein, the terms “approximately,” “about,” “substantially,” and like terms have common and accepted usage by those of ordinary skill in the art to which the subject matter of this disclosure pertains. intended to have a broad and harmonious meaning. It is understood that these terms are intended to allow for the description and description of the specific features claimed without limiting the scope of those features to the precise numerical ranges provided. should be understood by those skilled in the art to consider. As such, these terms are intended to indicate that any insubstantial or insubstantial modification or variation of the described and claimed subject matter is to be considered within the scope of the disclosure set forth in the appended claims. should be interpreted.

When used herein to describe various aspects, the term "exemplary" and variations thereof are intended to indicate that such aspects are possible examples, representations, or illustrations of possible aspects. (and such terminology is not intended to imply that such aspects are necessarily particular or best examples).

As used herein, the term "coupled" and variations thereof means that two members are directly or indirectly joined together. Such joints may be stationary (eg, permanent or fixed) or movable (eg, removable or releasable). Such joining may be by two members directly joined together, by two members joined together using one or more separate intermediate members, or by one of the two members and one unitary unit. It can be accomplished by two members joined together using a formed intermediate member. When "coupled" or variations thereof are modified by additional terms (e.g., directly coupled), the general definition of "coupled" provided above should be used in conjunction with the plain language of the additional terms. (e.g., "directly coupled" means the joining of two members without any separate intermediate member), and the generic term for "coupled" provided above Brings a narrower definition than a definition. Such coupling can be mechanical, electrical, or fluid. For example, a circuit A that is communicatively “coupled” to circuit B may communicate with circuit B directly (i.e., without an intermediary) or indirectly with circuit B (e.g., one or more through an intermediary).

References herein to the position of elements (e.g., "top", "bottom", "upper", "lower", etc.) are merely used to describe the orientation of the various elements in the figures. It should be noted that the orientation of various elements may differ according to other exemplary aspects, and such variations are intended to be encompassed by the present disclosure.

Although the figures and descriptions may show a specific order of method steps, the order of such steps may differ from that depicted and described, unless otherwise specified above. Also, unless specified otherwise above, two or more steps may be performed concurrently or with partial concurrence. Such variations may depend, for example, on the software and hardware systems chosen and on designer choice. All such variations are within the scope of this disclosure. Similarly, software implementations of the described methods use standard programming techniques using rule-based and other logic to implement the various connecting, processing, comparing, and determining steps. can be realized.

It is important to note that the configurations and arrangements of power systems, objects and control schemes shown in various exemplary aspects are exemplary only. Additionally, any element disclosed in one aspect may be combined or utilized with any other aspect disclosed herein. Additionally, elements from one section described above (e.g. Section 1.4 - Load Objects) may be combined or utilized with other elements described in another section (e.g. Section 4 - Signal Flow). can be For example, the object parameters and functions of the exemplary aspects described with respect to FIG. 3 (eg, Section 1-Objects) are shown in FIGS. (eg, Section 5.2—Assignment of Controllers). Although only one example of elements of one aspect that can be incorporated into or utilized in another aspect has been described above, other elements of various aspects can be incorporated into other aspects disclosed herein. It should be understood that it can be combined with or utilized with either.

Claims (20)

identifying a first source object, a second source object, and a load bus object;
determining locations of the first source object, the second source object, and the load bus object on a single-line topology;
receiving operating parameters of the first source object, the second source object, and the load bus object;
defining a first path including objects electrically connected between the first source object and the load bus object using the single-line topology;
defining a second path including all objects electrically connected between the second source object and the load bus object using the single-line topology; and A device comprising a circuit constructed to control the operation of the second pathway. 2. The apparatus of claim 1, wherein said circuitry is further configured to generate a route table containing all available routes. Control of the first pathway includes
selectively activating the first path by controlling closing actions of switch objects included on the first path;
and disabling the first path by controlling the opening of at least one switch object on the first path. activating the first path,
communicating with all objects on the first path;
4. The apparatus of claim 3, comprising coordinating an enabling action of each object prior to initiating the closing action of the switch objects included on the first path. Defining the first path defines an electrical path between the first source object and the load bus object to be included on the first path within an associated control circuit. 2. The apparatus of claim 1, comprising communication with all statically connected objects. the circuit
all objects different from and parallel to said first path and electrically connected between said first source object and said load bus object along a third path; include,
further constructed to define the third path using the single-line topology;
11. The device of claim 1. 7. The apparatus of claim 6, wherein the first path defines a first priority value and the third path defines a second priority value higher than the first priority value. 4. The first priority value is proportional to the number of switch objects included in the first path, and the second priority value is proportional to the number of switch objects included in the third path. 7. The device according to 7. 7. The device of claim 6, wherein only one of said first path and said third path is enabled simultaneously during continuous use after a transition period. the circuit
2. The apparatus of claim 1, further configured to disable said second path, thereby inhibiting said second path from being activated. a first genset controller associated with a first genset and a first genset switch;
a second power plant controller associated with the second power plant and the second power plant switch;
a power plant branch switch controller associated with a power plant branch switch coupled to the first power plant switch and the second power plant switch via a power plant branch bus;
a utility switch controller associated with a utility switch; and a load bus controller associated with a load bus coupled to the power plant branch switch and the utility switch;
a first path including the first power plant, the first power plant switch, the power plant branch bus, the power plant branch switch, and the load bus;
a second path including the second power plant, the second power plant switch, the power plant branch bus, the power plant branch switch, and the load bus; and the utility switch and the load. constructed to generate a path table defining a third path, including a generatrix and;
selectively activating the first path by communicating with the first power plant controller, the power plant branch switch controller, and the load bus controller;
selectively enabling the second path by communicating with the second power plant controller, the power plant branch switch controller, and the load bus controller;
selectively enabling the third path by communicating with the utility switch controller and the load bus controller;
system. The load bus controller,
a load bus routing function that determines which of said first path, said second path, and said third path should be activated or deactivated; and to accomplish activation or deactivation. , providing migration-type functionality to each controller associated with any switch on any path,
12. The system of claim 11. The first power generation equipment controller
receiving the transition type function from the load bus controller;
and a switch operation processing function configured to control operation of said first power plant and said first power plant switch to effect said activation or deactivation of said first path. 12. The system of claim 12. The switch operation processing function is
13. Further constructed to require activation of a synchronizer function that adjusts voltage, frequency and phase angle of the output of the first power plant before the first power plant switch is closed. System as described. 14. The switch processing function of claim 13, wherein the switch processing function is configured to communicate a switch state function to the load bus routing function, and a path state function is generated by the load bus routing function based on the switch state function. system. generating a single-line topology of the power system including source objects, switch objects, bus objects and controller objects;
populating each object with operating parameters;
generating a routing table defining available paths between a source object and a bus object, each path including all electrically connected paths between the source object and the bus object of said path; A method comprising: an object; and controlling the power system by enabling and disabling paths. 17. The method of claim 16, wherein the operating parameters for each object are selected from a library of object configurations. 17. The method of claim 16, further comprising: generating a valid route list containing a list of routes to be enabled or disabled; and communicating a transition type to a switch object to control the route enable or disable list. the method of. 17. The method of claim 16, wherein the routing table assigns a route ID, availability attributes, route priority, and route path to each route. each controller object is assigned to one or more of the source object, the switch object, and the bus object to implement control of the power system by enabling and disabling paths; 17. The method of paragraph 16.

Images