System and method for providing coordinated control

Abstract

Systems and apparatuses include circuitry configured to identify a first power object, a second power object, and a load bus object, determine locations of the first power object, the second power object, and the load bus object on a single-line topology, receive operating parameters of the first power object, the second power object, and the load bus object, define a first route using the single-line topology, the first route including objects electrically connected between the first power object and the load bus object, define a second route using the single-line topology, the second route including all objects electrically connected between the second power object and the load bus object, and control operation of the first route and the second route.

Description

[0001] Cross-references to related applications This application claims 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. Technical Field

[0002] This disclosure relates to the power system. Background Technology

[0003] More specifically, this disclosure relates to systems and methods for providing coordinated control of machines and components within a power system. Summary of the Invention

[0004] One embodiment relates to an apparatus including circuitry configured to: identify a first source object, a second source object, and a load bus object; determine the positions of the first source object, the second source object, and the load bus object on a one-line topology; receive operating parameters for the first source object, the second source object, and the load bus object; define a first route using the one-line topology, the first route including objects electrically connected between the first source object and the load bus object; define a second route using the one-line topology, the second route including all objects electrically connected between the second source object and the load bus object; and control the operation of the first route and the second route.

[0005] In some embodiments, the circuit is also configured to generate a routing table that includes all available routes.

[0006] In some embodiments, controlling the first route includes selectively activating the first route by controlling the closing action of switch objects included on the first route, and deactivating the first route by controlling the opening action of at least one switch object on the first route. In some embodiments, activating the first route includes communicating with all objects on the first route and coordinating the activation action of each object before initiating the closing action of a switch object included on the first route.

[0007] In some embodiments, defining a first route includes communicating with all objects electrically connected between the first power object and the load bus object to define inclusions on the first route within the associated control circuitry.

[0008] In some embodiments, the circuit is further configured to define a third route using a single-wire topology, which is distinct from and parallel to the first route, and includes all objects electrically connected along the third route between the first power object and the load bus object. In some embodiments, the first route defines a first priority value, while the third route defines a second priority value that is higher than the first priority value. In some embodiments, the first priority value is proportional to the number of switching objects included in the first route, while the second priority value is proportional to the number of switching objects included in the third route. In some embodiments, only one of the first and third routes is simultaneously activated during continuous use after the transition time.

[0009] In some embodiments, the circuit is also configured to disable the second route, thereby preventing the second route from being activated.

[0010] Another embodiment relates to a system including a first generator set controller associated with a first generator set and a first generator set switch; a second generator set controller associated with a second generator set and a second generator set switch; a generator set branch switch controller associated with a generator set branch switch coupled to the first and second generator set switches via a generator set branch bus; a utility switch controller associated with a utility switch; and a load bus controller associated with a load bus coupled to the generator set branch switch and the utility switch, wherein the system is configured to generate routing tables defining a first route, a second route, and a third route, the first route including the first generator set, the first generator set switch, the generator set branch bus, and the load bus, the second route including the second generator set, the second generator set switch, the generator set branch bus, the generator set branch switch, and the load bus, and the third route including the utility switch and the load bus. The system selectively activates the first route by communicating with the first generator set controller, the generator set branch switch controller, and the load bus controller. The system selectively activates the second route by communicating with the second generator set controller, the generator set branch switch controller, and the load bus controller. The system selectively activates the third route by communicating with the utility switch controller and the load bus controller.

[0011] In some embodiments, the load bus controller includes a load bus routing function that determines which of the first, second, and third routes should be activated or deactivated, and provides a transition type function to each controller associated with any switch on any route to enable or disable the route. In some embodiments, the first generator set controller includes a switch action processing function configured to receive the transition type function from the load bus controller and control the operation of the first generator set and its switch to enable or disable the first route. In some embodiments, the switch action processing function is further configured to request activation of a synchronizer function before the first generator set switch is closed, the synchronizer function adjusting the voltage, frequency, and phase angle of the first generator set's output. In some embodiments, the switch action processing function is configured to transmit a switch state function to the load bus routing function, and the load bus routing function generates a route state function based on the switch state function.

[0012] Another embodiment relates to a method comprising generating a single-line topology of a power system including power objects, switch objects, bus objects, and controller objects; populating each object with operating parameters; generating a routing table defining available routes between power objects and bus objects, each route including all objects electrically connected between the power objects and bus objects of the route; and controlling the power system by activating and deactivating routes.

[0013] In some embodiments, operation parameters for each object are selected from a library of object configurations.

[0014] In some embodiments, the method further includes generating an active route list that includes a list of routes to be activated or deactivated, and passing a conversion type to a switch object to control the activation or deactivation of routes.

[0015] In some embodiments, the routing table assigns the route ID, enable attribute, route priority, and route path to each route.

[0016] In some embodiments, each controller object is assigned to one or more of a power object, a switch object, and a bus object to enact control of the power system by activating and deactivating routing.

[0017] Another embodiment relates to a non-transitory computer-readable medium containing computer-executable instructions that, when executed by circuitry of a power system, cause the power system to perform functions to activate and deactivate routing. These functions include: identifying a first power object, a second power object, and a load bus object; determining the locations of the first power object, the second power object, and the load bus object on a single-wire topology; receiving operational parameters for the first power object, the second power object, and the load bus object; defining a first route using the single-wire topology, the first route including objects electrically connected between the first power object and the load bus object; defining a second route using the single-wire topology, the second route including all objects electrically connected between the second power object and the load bus object; and controlling the operation of the first and second routes.

[0018] Another embodiment relates to a system comprising: a first controller configured to control a first power system object located on a first route of a power system; and a second controller configured to control a second power system object located on a second route of a power system. Both the first and second controllers are configured to perform route-level functions including coordinating the actions of the first and second power system objects, and the first controller is a principal controller, while the second controller is a participant controller.

[0019] In some embodiments, the participant controller is prohibited from performing routing-level functions.

[0020] In some embodiments, the participant controller asynchronously computes the output of the routing-level function with the principal controller, and the output of the participant controller is not used to coordinate the actions of the first power system object and the second power system object.

[0021] In some embodiments, the participant controller calculates the output of the routing-level function synchronously with the principal controller, and the output of the participant controller is not used to coordinate the actions of the first power system object and the second power system object.

[0022] In some embodiments, routing-level functions performed by the principal controller receive input from both the principal controller and the participant controller.

[0023] In some embodiments, if the first controller is unable to perform routing-level functions, the second controller performs routing-level functions.

[0024] In some embodiments, the first controller defines a first object ID, while the second controller defines a second object ID, which has a higher value than the first object ID, and the principal controller is selected based on the lowest available object ID.

[0025] In some embodiments, the system further includes a third controller configured to control the first power system object. The third controller is a redundant controller configured to perform routing-level functions, including coordinating the actions of the first and second power system objects.

[0026] In some embodiments, the first power system object is arranged on both the first route and the second route.

[0027] Another embodiment relates to a system comprising: a first controller configured to control a first power system object located on a first route of a power system, and receiving routing-level inputs and performing routing-level functions including coordinating actions of the first power system object; and a second controller configured to control a second power system object located on a second route of the power system, and receiving routing-level inputs and performing routing-level functions including coordinating actions of the second power system object. The routing-level inputs include information about the first and second routes, while the routing-level functions affect the operation of the first and second routes.

[0028] In some embodiments, the first controller is configured to receive only routing-level inputs relevant to coordinating the actions of the first power system object.

[0029] In some embodiments, the first controller and the second controller compute routing-level functions synchronously or asynchronously.

[0030] In some embodiments, the system further includes a third controller configured to control the first power system object. The third controller is a redundant controller configured to perform routing-level functions.

[0031] In some embodiments, the first controller is a first generator set controller, and the second controller is a second generator set controller, and the routing-level functionality includes load sharing functionality. In some embodiments, the first generator set controller is configured to: publish first load value data, receive second load value data from the second generator set controller, calculate average load based on the first load value data and the second load value data, and control the power output of the first power system object to achieve average load.

[0032] Another embodiment relates to a system comprising: a first controller configured to control a first power system object of an electric system; a second controller configured to control a second power system object of the electric system, both the first and second controllers being configured to perform a first routing-level function, the first routing-level function including coordinating actions of the first and second power system objects, wherein the first controller is a principal controller and the second controller is a participant controller; a third controller configured to control the third power system object of the electric system, and receiving routing-level inputs and performing a second routing-level function, the second routing-level function including coordinating actions of the third power system object; and a fourth controller configured to control the fourth power system object of the electric system, and receiving routing-level inputs and performing a second routing-level function, the second routing-level function including coordinating actions of the fourth power system object.

[0033] In some embodiments, the participant controller is prohibited from performing first-level routing functions.

[0034] In some embodiments, the participant controller asynchronously computes the output of the first routing level function with the principal controller, and the output of the participant controller is not used to coordinate the actions of the first power system object and the second power system object.

[0035] In some embodiments, the participant controller calculates the output of the first routing level function synchronously with the principal controller, and the output of the participant controller is not used to coordinate the actions of the first power system object and the second power system object.

[0036] In some embodiments, the system further includes a redundant controller configured to perform at least one of a first routing-level function or a second routing-level function.

[0037] In some embodiments, any one of the first controller, the second controller, the third controller, or the fourth controller may be configured on a shared circuit.

[0038] Another embodiment relates to a non-transitory computer-readable medium containing computer-executable instructions that, when executed by a first, second, third, and fourth controller of a power system, cause the power system to perform functions to activate and deactivate routing. These functions include: controlling a first power system object of the power system using the first controller; controlling a second power system object of the power system using the second controller; performing a first routing-level function, which includes coordinating the actions of the first and second power system objects using the first and second controllers, wherein the first controller is a principal controller and the second controller is a participant controller; controlling a third power system object of the power system using the third controller, and receiving routing-level input using the third controller; performing a second routing-level function, which includes coordinating the actions of the third power system object using the third controller; controlling a fourth power system object of the power system using the fourth controller; receiving routing-level input using the fourth controller; and performing a second routing-level function, which includes coordinating the actions of the fourth power system object using the fourth controller.

[0039] Another embodiment relates to a non-transitory computer-readable medium containing computer-executable instructions that, when executed by circuitry of a power system, cause the power system to perform functions to activate and deactivate routing. These functions include: identifying a plurality of power objects, each including power functions and assigned a location on a single-line topology; identifying one or more switch objects, each including switch functions and assigned a location on a single-line topology; identifying one or more bus objects, each including bus functions and assigned a location on a single-line topology; identifying one or more load objects, each including load functions and assigned a location on a single-line topology; and assigning each object to one of a plurality of controllers, each controller configured to cooperatively perform the power functions, switch functions, bus functions, and load functions to provide operation of the system.

[0040] In some embodiments, power functions include one or more of the following: power status functions, capacity manager functions, synchronizer functions, load sharing functions, power selection functions, source prioritization functions, and grid paralleling functions. Switching functions include one or more of the following: switching status functions, synchronization check functions, and switching action processing functions. Bus functions include one or more of the following: bus status functions, router functions, system routing table functions, routing status functions, and dead bus access functions. Load functions include one or more of the following: load status functions, load decay functions, load add / remove functions, and sensitive load disconnection functions.

[0041] In some embodiments, the function further includes identifying one or more transformer objects, each transformer object including transformer functionality and assigned a location on a single-line topology.

[0042] In some embodiments, each of the power function, switching function, bus function, and load function includes a list of available algorithms, and multiple controllers utilize a subset of the list of available algorithms based on object type and location on a single-line topology. In some embodiments, this subset includes all available algorithms.

[0043] In some embodiments, each function is configured to define the operation of the associated object within a single-line topology.

[0044] In some embodiments, multiple controllers are configured to perform power functions, switching functions, bus functions, and load functions using software common to each of the multiple controllers.

[0045] In some embodiments, each function is automatically configured based on the object's specifications and its location on a single-line topology.

[0046] Another embodiment relates to a system comprising a single-line topology including: a power object including power status functions and a synchronizer function; a bus object including bus status functions, routing status functions, router functions, and routing table functions; a switch object including switch status functions and switch action processing functions; a load object including load status functions and load add / remove functions; and a routing control system including router functions configured to activate and deactivate routing on the single-line topology via coordination with the power object, bus object, switch object, and load object.

[0047] In some embodiments, the power state function identifies the current operating state of a power object, the synchronizer function is configured to control the frequency, voltage, and phase difference of the power object, and the router function activates and deactivates routing based at least in part on the power state function.

[0048] In some embodiments, the bus status function determines the electrical state of a bus object, and the output of the bus status function is provided to the switch action processing function and the load add / remove function. The routing status function identifies the state of each available route, so that the route can be activated or deactivated. The routing table function defines the available routes existing on a single-line topology, and the router function activates and deactivates routes based at least in part on the bus status function, the routing status function, and the routing table.

[0049] In some embodiments, the switch state function identifies the position of the switch object, the switch action processing function controls the actuation of the switch object, and the router function provides instructions to the switch action processing function at least in part based on the switch state function to implement the activation and deactivation of the route.

[0050] In some embodiments, the load status function identifies the status of a load object as powered, power failure, unpowered, or degraded; the load add / remove function determines whether the load demand is high or low compared to the available power supply; and the router function activates and deactivates routing based at least in part on the load status function and the load add / remove function.

[0051] In some embodiments, power objects, bus objects, switch objects, and load objects exist as virtual objects on a single-line topology, and parameters of power objects, bus objects, switch objects, and load objects can be input via a user interface.

[0052] In some embodiments, the routing control system includes one of a floating subject control scheme and a fully distributed control scheme.

[0053] Another embodiment relates to a method that includes identifying machines in a power system on a single-line topology; generating objects in a routing-level control system, each object being associated with an identified machine; populating parameters for each object, wherein the parameters include operational requirements of the associated machine; locating each object on the single-line topology; defining routes that electrically connect the objects; and controlling machine operation by activating and deactivating the routes. Activation and deactivation of the routes are implemented based on the populated parameters of the objects.

[0054] In some embodiments, each object includes functionality that defines the operation of that object within a single-line topology. In some embodiments, objects are selected based on object types including power objects, transformer objects, bus objects, switch objects, and load objects. In some embodiments, generating objects in a routing-level control system includes using software tools to select objects and populate the single-line topology.

[0055] In some embodiments, generating an object also includes selecting an object from an object palette library within the software tool.

[0056] In some embodiments, the routing-level control system includes multiple controllers associated with an object, and the control operations include coordinating the object's functionality among the multiple controllers using either a floating principal control scheme or a fully distributed control scheme.

[0057] This overview is illustrative only and is not intended to be limiting in any way. Other aspects, inventive features, and advantages of the apparatus or process described herein will become apparent from the detailed description set forth herein in conjunction with the accompanying drawings, in which similar reference numerals refer to similar elements. Attached Figure Description

[0058] Figure 1 This is a schematic diagram of a power system according to some embodiments.

[0059] Figure 2 Based on some embodiments and Figure 1 The object table associated with the power system.

[0060] Figure 3 Based on some embodiments and Figure 1 A schematic diagram of the functions of objects associated with the power system.

[0061] Figure 4 This is a schematic diagram of a power system according to some embodiments.

[0062] Figure 5 Based on some embodiments and Figure 4 The object table associated with the power system.

[0063] Figure 6 Based on some embodiments and Figure 4 The routing table associated with the power system.

[0064] Figure 7 This is a schematic diagram of a power system according to some embodiments.

[0065] Figure 8 Based on some embodiments and Figure 7 The routing table associated with the power system.

[0066] Figure 9 Based on some embodiments and Figure 7 Functional logic diagram related to the power system.

[0067] Figure 10 This is a schematic diagram of a controller according to some embodiments.

[0068] Figure 11 This is a schematic diagram of a power system according to some embodiments.

[0069] Figure 12 Based on some embodiments and Figure 11 The allocation table associated with the power system.

[0070] Figure 13 This is a schematic diagram of a power system according to some embodiments.

[0071] Figure 14 This is a schematic diagram of a power system according to some embodiments.

[0072] Figure 15 This is a schematic diagram of a power system according to some embodiments.

[0073] Figure 16 Based on some embodiments and Figures 13-15 The allocation table associated with the power system.

[0074] Figure 17 This is a schematic diagram of a power system according to some embodiments.

[0075] Figure 18 Based on some embodiments and Figure 17 The allocation table associated with the power system.

[0076] Figure 19 This is a schematic diagram of a centralized control scheme according to some embodiments.

[0077] Figure 20 This is a schematic diagram of centralized control with a redundant controller scheme according to some embodiments.

[0078] Figure 21 This is a schematic diagram of a floating body control scheme according to some embodiments.

[0079] Figure 22 According to some embodiments Figure 21 A schematic diagram of the control scheme for the floating body.

[0080] Figure 23 This is a schematic diagram of a fully distributed control scheme according to some embodiments.

[0081] Figure 24 According to some embodiments Figure 23A schematic diagram of a fully distributed control scheme.

[0082] Figure 25 This is a schematic diagram of a redundant controller floating body scheme according to some embodiments. Detailed Implementation

[0083] The following is a more detailed description of various concepts related to methods, apparatuses, and systems for power routing, and of implementations of such methods, apparatuses, and systems. Before turning to the accompanying drawings, which detail certain exemplary embodiments, it should be understood that this disclosure is not limited to the details or methods set forth in the specification or shown in the drawings. It should also be understood that the terminology used herein is for descriptive purposes only and should not be considered limiting.

[0084] As used herein, the term "power system topology" refers to the interconnection diagram of power sources, power switches, and loads for a particular power system. As used herein, the terms "single line diagram," "one-line diagram," or "single-line topology" refer to a simplified representation of the power system topology.

[0085] Referring generally to the accompanying drawings, the various embodiments disclosed herein relate to systems, apparatuses, and methods for power routing and distribution. Some embodiments aim to improve existing power system control schemes, wherein systems, apparatuses, and methods are configured to sequence and connect, disconnect, and transfer power to load buses for any arbitrary power system topology. Some embodiments control structures for connecting and disconnecting specific load circuits. Generally, the embodiments discussed herein identify components of the power system as objects within a system architecture. For example, a power system may include power source objects (e.g., grid power connections provided by a utility company, generator sets, solar arrays, battery packs, etc.), bus objects (e.g., power buses, load buses, distribution buses, etc.), transformer objects (e.g., passive power transformers), switch objects (e.g., automatic transfer switches (ATS), load switches, power switches, circuit breakers, etc.), and controller objects (e.g., power controllers, load bus controllers, switch controllers, etc.). Each object is assigned a separate object identifier and is inserted into a system architecture that can be represented by a single-line topology. Then, routes are defined between each power source and each load on a single-line topology to establish potential routes for power transfer from power source to load. For example, in some system architectures, more than one route may be available to provide power from a power source to a given load. Each route is assigned a separate route identifier. Each object is then assigned or allocated to a controller. Typically, objects will be assigned to adjacent controllers. For example, a generator controller coupled to and controlling a generator power object may also be assigned to control the power bus. Once each object is assigned to a controller, the power system can control the operation of the object using a centralized controller or a distributed control scheme that communicates with each individual controller object. For example, a floating principal control scheme can be used, where one controller object within the power system acts as centralized control for a specific task, but the individual controller object acting as centralized control changes according to the task required by the power system. In other embodiments, a fully distributed control scheme is employed, where all controller objects performing a specific system function are equivalent. A characteristic that makes them fully distributed is that each controller determines its own action to take, rather than determining actions for other controllers (as is the case with the principal in a floating principal control scheme). Both the floating entity control scheme and the fully distributed control scheme provide redundancy in the system because more than one controller object can operate the functions of the power system.

[0086] Object-based system architecture simplifies the design, implementation, commissioning, and operation of power systems. Each object is identified by each controller and customized with attributes or parameters. This allows each controller to identify what it is connected to, or on which route each object exists, and how each object affects that route. The ability to build systems based on single-line topologies and control using object-based routing improves the efficiency of design and construction while providing more robust control schemes.

[0087] like Figure 1 As shown, the simple power system 30 includes a utility 34 and a genset 42. The utility 34 provides grid power (e.g., alternating current (AC)) and is connected to a utility power bus 38. The genset 42 provides AC power to a genset bus 46. The utility power bus 38 is connected to a utility power switch 50, while the genset bus 46 is connected to a genset switch 54. In some embodiments, the utility power switch 50 and the genset switch 54 are combined in an automatic transfer switch (ATS) connected to a load bus 62. The ATS may be arranged or configured to provide power to the load bus 62 from either the utility bus 38 or the genset bus 46. A load 58 is connected to the load bus 62 and is configured to consume power provided by either the utility 34 or the genset 42.

[0088] Generally, the power system 30 operates by drawing power from the utility 34 to the load 58. In the event of a power outage at the utility 34, the ATS, including the utility switch 50 and the generator switch 54, can be actuated and the load connected to the generator set 42.

[0089] The power system 30 includes a generator set controller 66 and a switch controller 70. The generator set controller 66 is primarily associated with the generator set 42 and controls its operation. The switch controller 70 is primarily associated with an ATS (Automatic Transfer System) including a utility switch 50 and a generator set switch 54.

[0090] Section 1 - Objects like Figure 2 As shown, components of power system 30 are identified as objects. Power systems typically include five object types: power source objects, bus objects, switch objects, load objects, and transformer objects. Power system 30 does not include transformer objects, but other power systems described later in this document do include transformer objects. Within power system 30, each component is identified by an object ID, object name, object type, and object subtype. Controllers (e.g., generator controller 66 and switch controller 70) use the object ID and object name to identify components. The object type defines which parameters of the object are configurable.

[0091] Each object type has its own responsibilities (functions) in the operation of power system 30. Each object type also has attributes that define its identity and ratings. Note that most (but not all) objects are machines within power system 30. The utility power bus 38, generator power bus 46, and load bus 62 are bus object types and are important in the operation and coordination of power system 30, but they are not technically machines. Power system 30 itself can also be considered an object, as can controllers (e.g., generator controller 66 and switch controller 70). An object type becomes a container for the functionality it possesses.

[0092] like Figure 3 As shown, each instance of an object type can include multiple functions, parameters, or properties that can be customized to represent the operation of individual objects within a power system (e.g., power system 30). In other words, power system 74 is abstracted as consisting of the following object types: power source 78, bus 82, switch 86, load 90, transformer 94, and additional controllers (not shown in the diagram). Figure 3 (as shown in the diagram) and the power system 74 itself. According to the embodiments disclosed herein, the power system can be arranged as a collection of object instances; one instance exists for each occurrence of a type object. Each object type is a container of a superset of system control functions associated with that object type. The set of functions contained in an object type is always the same implementation (e.g., software code), regardless of where the object instance is located in the power system. The behavior of individual object instances is modified only by changes in configuration settings, not by new software code (e.g., 'C' code).

[0093] Object instances are typically distributed among controllers around the system based on what they are physically connected to. This allows for functional abstraction from any particular controller implementation or specific installed controller topology. That is, objects and functions are largely decoupled from the controllers on which they will reside / operate. For example, a generator controller (e.g., generator controller 66) can control the functions of associated generator sets (e.g., generator set 42) by controlling fuel supply, aftertreatment, etc., but the generator controller can also control the functions of other objects, and other controllers can influence the operation of the generator controller. Each controller can run multiple instances of different object types. Objects and their functions communicate with each other via a shared global data space. The system-wide global data space can be created using networking technologies and protocols such as DDS over Ethernet. Therefore, the functions within each object instance will work in conjunction with other object types to perform the system control and sequencing required to operate the power system.

[0094] This differs from traditional power system control. Traditional power systems typically rely on a centralized controller that runs the power system control functions; this controller is custom-developed / programmed for a specific customer site installation. Object-based distributed control offers more flexible installation opportunities, provides a robust control environment, and reduces overall system complexity and the required customization.

[0095] Below, about Figure 3 This section discusses object-specific functionality. Functionality associated with a specific object type is exemplary. Other functionality can be associated with that object type, including additional parameters, customizable settings, etc. Furthermore, some functionality can be eliminated from the object type, or it can be included in a context related to the object type. Figure 3 Among the different object types shown.

[0096] Section 1.1 - Power Supply Objects Each power source object 78 within the power system 74 (e.g., utility 34 and generator set 42) defines seven power source functions, including: power status function 98, capacity manager function 102, synchronizer function 106, load sharing function 110, power source selection function 114, power source priority sequencing function 118, and grid parallel control function 122. In some embodiments, each power source object may include more or fewer functions. In some embodiments, unused functions may be built into the control scheme, or custom functions may be added.

[0097] Power status function 98 identifies the current operating state of a power object. A power object needs its current operating state to be known so that power selection and other functions can function. Note that power status function 98 is used by the power system control scheme and is not necessarily indicated by or used by local machine control functions. For example, generator set 42 may operate in a diagnostic state and still be effectively operational, but it cannot provide power to power system 30 as a power source. Power status function 98 would then identify generator set 42 as unavailable, even if it is currently operating. In some embodiments, to fully support the abstraction of power objects within the larger control scheme of power system 30, power status should be generic regardless of the type of power source. For example, a power object may include a superset of power states, and a subset of power states may be selected based on the details of the power object (e.g., a first subset of power states for generator sets and a second subset of power states for utilities). Power sources also have other dynamic information (e.g., current capacity, load, etc.) that they share with power system control functions as part of the power source's "status" information. In some embodiments, the power status function 98 includes information indicating whether the power supply is ready to be invoked when needed, whether the power supply is available based on sensors and has been stable for a period of time, whether the power supply has failed, and / or whether the power supply is disabled (e.g., due to a shutdown failure or not in automatic mode).

[0098] Capacity Manager function 102 provides a dynamic model of the available capacity within power system 30. Continuous management of online capacity is critical. The required power capacity drives the decision of how many power supplies (in priority order) are connected to the load bus object (e.g., load bus 62). There must be sufficient capacity online to not only support the current load but also to accept additional loads (if available) before additional power supplies can come online without overloading power system 30. For critical applications, additional power supplies may also be required online to cover unexpected power losses. Inputs to decisions regarding adding or removing power supplies include: - What is the individual power capacity? Some power objects (such as batteries, solar arrays, or wind power) may be dynamic.

[0099] What is the current total online capacity? What is the current total load? What is the current online standby capacity (total capacity - load)? - What is the expected level of reserve capacity? - Is protection against the accidental loss of either power supply necessary? Are there two power supplies? -If connected to the power grid, what is the power setpoint of the grid? - Is there any notification that a significant load step is about to occur? What is that load? - Is there any notification that a significant loss of power capacity (e.g., power de-rating, reduced solar inflow, decreased wind speed, or battery discharge limitations) is imminent? - Is it necessary to intentionally disconnect the power supply (e.g., for service purposes)? -If this is a black start, how much capacity should be initially provided? All? The selected power supply? Synchronizer function 106 provides parameters and status for the synchronization of power source objects. Traditionally, generator controllers synchronize themselves with the bus to which they are connected, or with another single power source (e.g., a utility). A single generator controller performs all sensing measurements to achieve this. As distributed power system control schemes support various single-line topologies or configurations and power source types, this function becomes a service capable of synchronizing single or multiple generator sets with any sensing point in the power system. Synchronizer function 106 allows the transfer of synchronization parameters between controllers within the power system 30 to enable cohesive synchronization and distributed control. That is, the sensing and initiation of synchronization can occur on other controllers. Furthermore, synchronizer function 106 identifies whether a power source object is capable of synchronization. The system needs to know which power sources can be invoked for synchronization, for the purpose of paralleling that power source with the live bus. Synchronization can include any capability such as matching frequency, matching frequency offset, matching voltage, or matching phase. It may not include all capabilities.

[0100] The load sharing function 110 indicates whether a power source object can maintain its nominal voltage and frequency when sharing loads with other power sources. Typically, the power source object must also be able to act as a grid former for use in load sharing.

[0101] The power selection function 114 combines power priority sorting, power status, and power capacity management information to output a list of power supplies that should be online. If a power supply needs to be changed, the process of putting it online or offline is handled by other downstream functions, such as routing and sorting control associated with the bus object.

[0102] The power priority sequencing function 118 provides a listed priority order for available power supply objects. All power supplies have an active priority number assignment, which is used to determine the order in which power supplies should be invoked based on the status of other power supplies and the amount of load. This priority number can be dynamic or static. The priority assignment stems from the current objective of the power system's operation. For some objectives, the control system can calculate the priority order. For other, more complex objectives / calculations, external optimization algorithms (e.g., cloud or edge computing devices) can set the power supply priority order. Some possible objectives managed locally include: - Run the system to maximize the contribution from renewable power sources.

[0103] - Running this system ensures that not all machines are available simultaneously for service.

[0104] - Running this system ensures that all machines maintain approximately the same amount of wear.

[0105] - Run this system to maximize the lifespan of your assets.

[0106] - Run the system to minimize operating costs.

[0107] - The system runs based on a dynamic priority sorting set by an external optimization algorithm.

[0108] The grid parallel control function 122 identifies which power source types can operate in parallel with other power source object types or subtypes. For a given power system, there are typically limits on which power sources can operate in parallel and for how long. To address the general problems of any power system, an N^2 power source matrix is ​​needed to configure the allowed combinations. For example, the grid parallel function of a power source object can define one or more of the following options: OT = open transition; HCT = hard closed transition (<100ms overlap); SCT = soft closed transition (subject to maximum parallel time limit); All = allow all modes; or EP = extended parallel (no time limit).

[0109] Section 1.2 - Bus Objects Each bus object 82 within the power system 30 (e.g., utility power bus 38, generator power bus 46, and load bus 62) defines five bus functions, including: bus status function 126, routing status function 130, router function 134, non-energized bus access function 138, and system routing table function 142. In some embodiments, each bus object may include more or fewer functions. In some embodiments, unused functions may be built into the control scheme, or custom functions may be added.

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

[0111] The routing state function 130 identifies the routes from which power can flow from the power source through the power system 30 to the load. The routing state function 130 identifies the status or health condition of each available route, allowing routes to be activated or deactivated. Possible states include: unknown, disconnected, cannot be disconnected, connected, and / or unconnectable. The state of each route is determined by a routing state algorithm. The routing state can be used by the load bus router to select feasible routes. If a route is unreachable, the load bus router can select the next highest priority route (if that route is available).

[0112] A core concept of the power system 30 is a sequencing control concept, which identifies routes connecting the load bus and the power source and activates and / or deactivates routes by controlling switches between closed and open states. Switching logic (e.g., stored in switch controller 70) is responsible for (e.g., via synchronizer service requests, synchronization checks, closure of the unenergized bus, etc.) ensuring the safe closing of switches (e.g., utility switch 50 and generator switch 54). Router function 134 determines which routes to activate or deactivate based on the current power source selection. Router function 134 also determines what type of transition is occurring (e.g., disconnect transition, closure transition, etc.) and may involve sequencing of transitions. Router function 134 is shown as being owned by load bus object 82. In some embodiments, router function 134 may operate as a floating body function, which may run in multiple controllers or be associated with multiple different object types for redundancy. Router function 134 acts between the load bus and the power source. In a power system where the load bus has separate load feeders below it, distributed load add / remove functions will be solely responsible for managing the connection and disconnection of load circuits. Furthermore, in some embodiments, the load itself will be connected and disconnected via router functionality.

[0113] In some embodiments, power object 78 or load object 90 may request route hold to keep a specific route connected. If no other higher-priority reason exists to deactivate the route, it will be permitted and remain active until load object 90 or power object 78 indicates that the route is no longer needed. For example, power object 78 may request route hold to ensure a minimum length of time the load is carried to prevent adverse lifespan / maintenance effects. Similarly, load object 90 may request route hold to ensure it remains continuously powered for a minimum amount of time to recharge the UPS battery. Load object 90 may also request route hold if the power system is configured to require manual intervention for retransmission.

[0114] The non-energized bus access function 138 (which may alternatively be referred to as First Start) functions to close a single energized power source object 78 (e.g., generator set 42) to the non-energized bus while preventing all other power source objects 78 (e.g., all other generator sets) from closing to the non-energized bus. Utilizing distributed power system control schemes that support various single-line topologies or configurations and power source types, the non-energized bus access function 138 can be made generic and serves anywhere in the power system 74 where switch / circuit breaker objects 86 need to close between the energized and non-energized sides, or even between two non-energized sides. The non-energized bus access function 138 functions to coordinate and arbitrate the closing of a single energized power source to energize the non-energized bus while preventing all other energized power sources from closing to the bus until operation is complete. Fallback may also be included in fault scenario situations.

[0115] System routing table function 142 defines the available routes presented on a single-line topology. System routing table function 142 lists all possible connection paths between load bus object 82 and the various power objects 78. System routing table function 142 provides a routing table for drawing power from power objects 78 to load bus object 82 and is used by the load bus router. System routing table function 142 can be programmed into all controllers or subsets of controllers on the power system 74 through a tool that includes a user interface. Ideally, this tool would have a graphical interface and a system object library that can be used to draw the single-line topology. The tool can then automatically calculate the routing table.

[0116] Section 1.3 - Switch Objects Each switch object 86 within the power system 74 (e.g., utility switch 50 and generator set switch 54) defines three switching functions: switch status function 146, synchronization check function 150, and switch action processing function 154. In some embodiments, each switch object 86 may include more or fewer functions. In some embodiments, unused functions can be built into the control scheme, or custom functions can be added.

[0117] Switch status function 146 indicates the position of switch object 86, the position of the main contacts of switch object 86, whether switch object 86 is under maintenance, switch malfunction, whether the closing action is pending, and / or whether switch object 86 is prohibited from closing.

[0118] The synchronization check function 150 achieves closure of two energized power source objects 78 by expecting the voltage, frequency, and phase angle to match to a level safe for the device (e.g., mechanical / electrical stress) and without generating unacceptable power disturbances. The synchronization check function 150 is typically performed using measurements of both power source objects 78 at a single controller. This can be a fully local function in an associated controller that has sensor access or visibility on each side of the connected switch object 86.

[0119] Switch action processing function 154 controls the actuation of switch object 86. Based on system routing table function 142, switch action processing function 154 may open, close, or do nothing with switch object 86. Switch action processing function 154 also initiates subsequent actions, such as synchronization check function or non-energized bus access function 138, to close, or wait for ramp unloading to complete to enable opening. Furthermore, switch action processing function 154 monitors bus idle capacity by calculating the available capacity on bus object 82 (e.g., the difference between the power supply capacity rating and the current load on the bus). Bus idle capacity can be used to determine whether a pending closure is allowed. If there is insufficient idle capacity upstream of switch object 86 to support the load downstream, the switch will not close. This is applicable in some scenarios where closing would energize a non-energized load at any switch object 86.

[0120] Section 1.4 - Loading Objects Each load object 90 (e.g., load 58) within the power system 74 defines four load functions, including: load status function 158, load decay function 162, load add / remove function 166, and sensitive load disconnection function 170. In some embodiments, each load object 90 may include more or fewer functions. In some embodiments, unused functions may be built into the control scheme, or custom functions may be added.

[0121] The load status function 158 identifies the status of the load object 90 as energized, power failure, de-energized, or degraded, and identifies all load objects 90 connected to the public or shared bus object 82. Once the load status function 158 determines which load objects 90 are connected, the current status of all connected load objects 90 is determined.

[0122] The load decay function 162 determines when the load object 90 has been de-energized and disconnected from the power supply for a sufficient period of time to allow the load object 90 to be reconnected to a energized power source. For example, it allows a motor load time to stop rotating before being re-energized, in order to avoid unwanted operational / equipment stress.

[0123] The load add / remove function 166 can work in conjunction with the load decay function 162 to determine whether the load demand is high or low compared to the available power supply (i.e., the power supply from the connected power object 78), and accordingly connect or disconnect the current on the common bus object 82. The load add / remove function 166 is used to add (i.e., connect) the load circuit when capacity allows and remove (i.e., disconnect) the load circuit when the system capacity is overloaded. The load add / remove function 166 can be a standalone function or can utilize router functionality 134.

[0124] Sensitive load disconnect function 170 provides control for cases where a sensitive load is directly connected to load bus object 82. In the sensitive load object 90 scenario, sensitive load disconnect function 170 communicates with upstream switch object 86 to control disconnection, closing, and other actions to provide control to sensitive load object 90. In other words, if the load circuit has a sensitive load designation, the circuit will immediately disconnect (i.e., open circuit) upon detecting a power fault, rather than remaining connected to a power source that may only be partially faulty (e.g., brownout or single-phase operation).

[0125] Section 1.5 - Transformer Objects Each transformer object 94 within the power system 74 defines four transformer functions, including: ratio function 174, winding type function 178, X / R ratio function 182, and rating function 186. In some embodiments, each transformer object 94 may include more or fewer functions. In some embodiments, unused functions may be built into the control scheme, or custom functions may be added. The transformer object 94 may be responsible for determining and transmitting its current state. In many embodiments, the transformer object 94 will not have any direct control action. Power system performance will benefit from knowing the location (electrically) of the transformer object 94 and its specifications. For example, synchronization checks may want to know the transformer object's delta / wye 30-degree (deg) offset. The transformer type specification will automatically determine +30 or -30. The transformer ratio function 174 will also be wanted for voltage matching. If different X / R's exist in the power path, power flow management may want to know the transformer object's X / R ratio function 182 to better balance load sharing.

[0126] Section 2 - System Architecture The object-based abstraction discussed above can be applied to any power system architecture. Figure 4 An electric power system 190 is shown, which includes a power system 190 with ... Figure 1 The power system shown in the image contains 30 more components / objects. Figure 5 The diagram shows the object ID, object name, object type, and object subtype for each object in the power system 190. The power system 190 includes four power source objects: utility 194, first generator set 198, second generator set 202, and third generator set 206.

[0127] The power system 190 includes nine switching objects. Five of the switching objects are power switches, including a utility switch 210 connected to utility 194, a first generator set switch 214 connected to a first generator set 198, a second generator set switch 218 connected to a second generator set 202, a third generator set switch 222 connected to a third generator set 206, and a generator set branch switch 226 coupled to each of the first generator set 198, the second generator set 202, and the third generator set 206. Four of the switching objects are load switches, including a first load switch 230, a second load switch 234, a third load switch 238, and a fourth load switch 242.

[0128] Transformer object 246 is connected between third generator set switch 222 and generator set branch switch 226. In some embodiments, power system 190 may include more than one transformer object.

[0129] The power system 190 includes 11 bus objects. Generator branch bus 250 connects the first generator switch 214, the second generator switch 218, the transformer 246, and the generator branch switch 226; transformer bus 254 connects the third generator switch 222 and the transformer 246; load branch bus 258 connects the utility switch 210 and the generator branch switch 226, as well as the first load switch 230, the second load switch 234, the third load switch 238, and the fourth load switch 242; utility bus 262 connects the utility 194 and the utility switch 210; the first generator bus 266 connects the first generator branch switch 226... A generator set 198 is connected to a first generator set switch 214; a second generator set bus 270 is connected between a second generator set 202 and a second generator set switch 218; a third generator set bus 274 is connected between a third generator set 206 and a third generator set switch 222; a first load bus 278 is connected between a first load and a first load switch 230; a second load bus 282 is connected between a second load and a second load switch 234; a third load bus 286 is connected between a third load and a third load switch 238; and a fourth load bus 290 is connected between a fourth load and a fourth load switch 242.

[0130] The power system 190 also includes six controller objects: a first generator set controller 294, a second generator set controller 298, a third generator set controller 302, a utility switch controller 306, a generator set branch switch controller 310, and a load branch controller 314. These controller objects are used to control all objects within the power system 190, and the functions of each object type are assigned to specific controllers, as described in more detail below. The coordination and execution of object functions can be performed via a distributed control scheme utilizing all or some of the controller objects. This distributed control scheme will be discussed in further detail below.

[0131] Each object in the power system 190 can be configured using settings within the controller to represent real-world machine and bus functions. This allows for precise control of the power system 190 using settings and configurations designed around a single-wire topology, without requiring a custom-programmed control system.

[0132] Section 3 - Routing The power system 190 includes multiple interconnected objects and provides paths or routes for power to flow from power source objects to load objects. For example... Figure 6As shown, the system routing table (e.g., created by the system routing table function 142 of the bus object) lists all possible routes between the load bus and the individual power sources for a given power system. The enable attribute is a configuration that allows routes to be disabled. The route ID attribute is a combination of the load bus identifier and the power source identifier. The route priority is a configuration used when there is more than one route from the load bus to the power source. The route priority may have a default value derived from the number of switches on the route, but can be changed by the user. For example, more switches result in lower priority.

[0133] The system routing table provides information to the load bus router, enabling it to know the routes to each power source (and thus which routes to activate to connect the desired power source). The system routing table is also used by switch action processing, allowing the switch to know which routes it "exists" on, enabling it to respond appropriately to the active route list generated by the router functions.

[0134] exist Figure 4 The power system 190 shown in the diagram defines four available routes, and in Figure 6 The routing is described in the diagram. These routes define all available power paths that provide power from the available power object to the load branch bus 258. Figure 6 All routes are shown as enabled (Y), but in some embodiments, routes can be disabled (N) when the power source is offline (e.g., an outage occurs in utility 194). First route 320 is assigned route ID LB1.G1, route priority 1, and defines the route path LB1-SW4-B1-SWG1-G1. The route ID can typically indicate a point-to-point route (e.g., LB1.G1 indicates a route connecting the first generator set 198 and the load branch bus 258), or another naming convention can be used as needed. The route priority is set to 1 because multiple routes between the power source and the load are not feasible in power system 190. The route path of first route 320 defines power flowing from the first generator set 198 through the first generator set switch 214, generator set branch bus 250, generator set branch switch 226, and onto the load branch bus 258.

[0135] The second route 324 is assigned route ID LB1.G2, indicating that power typically flows from the second generator set 202 to the load branch bus 258. This route is enabled and has a priority of 1. The route path is LB1-SW4-B1-SWG2-G2, indicating that power flows from the second generator set 202 through the second generator set switch 218, the generator set branch bus 250, the generator set branch switch 226, and finally to the load branch bus 258.

[0136] The third route 328 is assigned route ID LB1.G3, indicating that power typically flows from the third generator set 206 to the load branch bus 258. This route is enabled and has a priority of 1. The route path is LB1-SW4-B1-SWG3-G3, indicating that power flows from the third generator set 206 through the third generator set switch 222, the generator set branch bus 250, the generator set branch switch 226, and to the load branch bus 258. As shown by the third route path, passive objects such as transformer 246 can be excluded from the route path. In some embodiments, passive objects or all objects may be included in the route path definition.

[0137] The fourth route 332 is assigned route ID LB1.U1, which indicates that power typically flows from utility 194 to load branch bus 258. This route is enabled and has a priority of 1. The route path is LB1-SWU1-U1, which indicates that power flows from utility 194 through utility switch 210 and onto load branch bus 258.

[0138] 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. The control system of power system 190 (including first generator controller 294, second generator controller 298, third generator controller 302, utility switch controller 306, generator branch switch controller 310, and load branch controller 314) utilizes the routing table to efficiently control all objects residing on the respective routes, producing the desired results. For example, if utility 194 is offline, power system 190 can identify the need for more power and activate any of the first route 320, second route 324, and third route 328 to generate power. The activation of route paths provides an automated and coordinated solution for actuating or controlling all objects residing on the activated route paths.

[0139] To further illustrate the concept of routing tables, Complex Power Systems 336... Figure 7The diagram illustrates a single-line topology and includes a first utility 340 and a second utility 344, which may be grid-based power sources or power sources supplied by external sources (e.g., power plants). The power system 336 also includes a first generator set 348, a second generator set 352, and a third generator set 356. In some embodiments, the generator sets are diesel-powered or powered by internal combustion engines that burn another type of fuel. The power system 336 also includes a solar array or solar station 360 and a battery pack 364. Other power sources, such as wind or hydropower, and any other power sources may be connected to the power system envisioned herein. The power system 336 includes seven power sources. In some embodiments, it includes more or fewer than seven power sources.

[0140] The power system 336 also includes seven corresponding power switches, including a first utility switch 368 selectively coupling a first utility 340, a second utility switch 372 selectively coupling a second utility 344, a first generator set switch 376 selectively coupling a first generator set 348, a second generator set switch 380 selectively coupling a second generator set 352, a third generator set switch 384 selectively coupling a third generator set 356, a solar switch 388 selectively coupling a solar station 360, and a battery switch 392 selectively coupling a battery pack 364.

[0141] The generator set branch bus 393 is configured to communicate with the first generator set 348 via the first generator set switch 376, with the second generator set 352 via the second generator set switch 380, and with the third generator set 356 via the third generator set switch 384 and the transformer 394. The generator set switches 376, 380, and 384 provide selective coupling between the generator set power supply objects and the generator set branch bus 393.

[0142] The generator branch bus 393 is configured to selectively communicate with the first load bus 396 via the first generator branch switch 398 and with the second load bus 400 via the second generator branch switch 402. The load bus switch 404 provides selective communication (i.e., connection) between the first load bus 396 and the second load bus 400.

[0143] Four load switches 408, 412, 416, and 420 are connected to the first load bus 396 and selectively supply power to four corresponding loads. Four load switches 424, 428, 432, and 436 are connected to the second load bus 400 and selectively supply power to four corresponding loads. Although four loads coupled to each load bus are shown, more or fewer loads are envisioned. Each load may include a single power consumer or may include a load system (e.g., a microgrid fed by power system 336).

[0144] When an object is added Figure 7 In the single-line topology shown, each object defined on the single-line topology will be assigned the attributes or parameters discussed above, such that the object's functionality is known within the power system 336. An object table will be generated, providing object names (e.g., the first generator set 348 is named S1, etc.) and a list of parameters. Furthermore, the power system 336 includes controllers associated with the various objects to provide actuation and control of the components.

[0145] Power system 336 includes more Figure 4 The power system 190 shown provides more routing dynamics. Power system 336 defines... Figure 8 The twenty-four (24) discrete routes shown. Figure 7 Eleven routes connecting to the first load bus 396 are shown. Routes connecting to the second load bus 400 are not shown. Figure 7 The routing provided offers greater clarity. The routing defined by power system 336 more clearly illustrates the concept of priority. For example, route R1.7 includes route priority 2 because the route includes the first generator branch switch 398, generator branch bus 393, and second generator branch switch 402 to couple the first load bus 396 to the second utility 344. Alternatively, route R1.8 includes route priority 1 because the path between the first load bus 396 and the second utility 344 is more direct.

[0146] exist Figure 7 and Figure 8In the example shown, a load bus router for each route (e.g., load bus router 134 discussed above) is assigned to the associated load bus. That is, all routes ending on the first load bus 396 will be controlled by the load bus router associated with the first load bus 396, and all routes ending on the second load bus 400 will be controlled by the load bus router associated with the second load bus 400. One tenant of the sequencing control concept is a route that connects the load bus and the power supply, and which activates or deactivates switches on the route to close or open. Switching logic is responsible for controlling each individual switch (e.g., closing according to a desired sequence including synchronizer service requests, synchronization checks, non-energized bus closures, etc.). The load bus router determines which routes to activate or deactivate based on the current power object selection. It also determines what type of transition is occurring (open transition, close transition, etc.) and may involve the sequencing of transitions. Load bus router functionality can be owned or assigned to a load bus object and operate as a floating principal function that can run across multiple controllers for redundancy. Note that the load bus router acts between the load bus and the power supply. In applications where the load bus has a separate load feeder underneath, the distributed load add / remove function can be solely responsible for managing the connection / disconnection of the load circuitry. In some embodiments, the load itself will be connected and disconnected via router function 134.

[0147] Individual power or load objects can request route retention to keep a specific route connected. If no higher-priority reason exists to deactivate the route, route retention is granted, and the route remains active until the load or power object indicates that it is no longer needed. For example, a power supply might request route retention to ensure a minimum length of time it is powered to prevent adverse lifespan / maintenance effects. Similarly, a load object might request route retention to ensure it remains continuously powered for a minimum amount of time to recharge the UPS battery. Load objects can also request route retention if the system is configured to require manual intervention for retransmission.

[0148] In some embodiments, the default route priority is simply the sum of the number of switches in the route. If multiple routes to the power source exist, the algorithm for selecting the route to invoke will depend on many things, including route priority. Other factors in routing selection may include the current state of the system and the switches. For example, if there are more disconnected switches on the set of paths with higher priority (i.e., lower priority numbers) than on the set of paths with lower priority (i.e., higher priority numbers), it may make sense to use the lower priority path with the higher priority number (e.g., choosing route R1.7 instead of route R1.8). In some embodiments, the following factors may be included in routing selection: 1) using the fewest disconnected switches to select a route, or 2) using the number of switches in the path, or 3) using a custom priority configuration, etc. Failure modes may also be considered. If a higher priority path with a lower priority number cannot be connected, the power system can revert to the next lower priority path with a higher priority number, assuming other conditions allow that route to be activated (e.g., the connection of that route does not create any power or operating mode conflicts).

[0149] Load bus routers can also resolve potential conflicts. Generally, conflicts are resolved by clearly defining priorities. Power supplies have priorities, loads have priorities, routes can have priorities (e.g., routes can have priority numbers if redundant paths exist), and the reasons for operation have a priority hierarchy. In some embodiments, load bus routers can resolve conflicts. For example, if the system has redundant routes and multiple load buses requesting routes, the load bus router can prevent possible loops (i.e., parallel paths). Some loops may be allowed for fast overlap transitions between routes.

[0150] The use of routing allows for improved control efficiency and enhances the reliability of power system configuration and commissioning.

[0151] Section 4 - Signal Flow According to this disclosure, the operation identification system architecture of the power system comprises discrete objects, and the authority to control the operation of the system can be distributed among the various controllers of the power system. The details of distributed control will be discussed further below. Figure 9A high-level logic scheme 440 is illustrated, which uses routing-level functions to control power delivery from power source objects to load bus objects to control the routing paths discussed above. As used herein, the phrase "routing-level function" refers to a function performed by objects of the power system to implement the cooperative functions of the power system. The routing-level functions of each object are discussed in further detail below. Generally, the task of the power manager is to indicate to the load bus router which power sources should be connected to the load bus. The load bus router activates and deactivates routes to the indicated power sources. Switch action processing functions determine whether each switch is open, closed, or does nothing, depending on the active or inactive route. The following description pertains to functional blocks (e.g., routing-level functions) that interact to implement control of the power system.

[0152] like Figure 9 As shown, the power manager 444 is responsible for monitoring the status of all power supplies, selecting power supplies, and ensuring sufficient capacity. One of the main outputs of the power manager 444 is the load bus power supply list 448, which lists the power supplies that should be connected to the load bus (i.e., the expected power supply connection list). The power supply compatibility matrix 446 defines what types of conversions are allowed between two power supplies, and which power supplies can effectively be connected in parallel. For example, for a system with N power supplies, there is a 1 / 2 power supply compatibility matrix 446. (N^2-N) combinations are used to define compatibility. The power compatibility matrix 446 is used by both the power manager 444 and the load bus router 452. In some embodiments, the power manager 444 uses the power compatibility matrix 446 to avoid selecting disallowed power combinations.

[0153] If the load bus power supply list 448 does not match the currently connected power supplies (or those expected to be connected) with the load bus, then the load bus router 452 diagnoses the discrepancy and determines the next step in the sequence toward matching the currently connected power supplies with the load bus power supply list 448. Several possible scenarios exist where the currently connected power supplies do not match the load bus power supply list 448. For example: 1) the power supply has failed and is being replaced by a different power supply; 2) additional capacity is needed, so a power supply is being added; or 3) a test conversion with load has been initiated. Once the next step is determined, the load bus router 452 updates two main outputs: the active route list 456 and the conversion type 460. The active route list 456 contains only those routes that should be connected (i.e., the expected routes). The conversion type 460 is received by the switch action processing function 464, which then determines any changes needed to the active route list 456 based on the conversion type 460. Values ​​for the conversion type 460 include: none, disconnect conversion, hard close conversion, soft close conversion, or extended parallel connection. In some embodiments, a switch action processing function 464 exists in each switch controller. In some embodiments, multiple instances of the switch action processing function 464 may exist (e.g., one instance per switch object, multiple instances per controller object, etc.), such that a total of one instance of the switch action processing function 464 exists for each switch in the system. Furthermore, in some embodiments, the load bus router 452 uses a power compatibility matrix 446 when requesting a complete power conversion. The load bus router 452 checks the power compatibility matrix 446 for all involved power combinations and selects the lowest common denominator for the conversion type. In some embodiments, the power manager 444 may overwrite the result of the power compatibility matrix 446 and select the smaller conversion type via a cause output signal. Options for setting the power compatibility matrix 446 may include: OT = Disconnect Conversion - Power can not be paralleled; HCT = Hard Close Conversion - Power can only be paralleled <100ms; SCT = Soft Close Conversion - Power can be paralleled to complete a ramp load conversion (applicable to maximum paralleling time); and / or EP = Extended Parallel - Power can be paralleled indefinitely. Other options or details of the settings may vary depending on the system implementation.

[0154] Based on the active route list 456, the switch action processing function 464 determines whether the associated switch should be closed, open, or remain in its current state. The switch action processing function 464 knows which routes the switch "exists" on (i.e., which routes the switch is part of), which is obtained from the system routing table 468.

[0155] When the switch action processing function 464 determines that the switch should be closed, it first determines whether the switch is on an active route and whether it is currently open. If the switch is on an active route and open, then the switch action processing function 464 needs to take appropriate action to safely close the switch. The bus state 472 on each side of the switch determines what is possible. Closure can only occur if the bus state 472 is available-off, available-available, or off-off. Once the conditions of the bus state 472 are met, further conditions are required, such as obtaining exclusive permission to close the off-off bus 476, satisfying the synchronization check condition 480, and checking for sufficient upstream capacity 484 to support the downstream load. Once the conditions are in place, a request is made to close the switch, and mechanism-specific logic in the power switch control 488 (e.g., automatic transfer switch (ATS), circuit breaker, contactor, etc.) activates to close the switch.

[0156] When the switch action processing function 464 determines that the switch should be opened, it first determines whether the switch is closed and not on any active route. If the transfer type 460 is an extended parallel or soft-close transfer, the switch is commanded to open via the power switch control 488 after the load ramp state 492 indicates that the load through the switch has completed ramp off. If the transfer type 460 is a hard-close or open transfer, the switch is commanded to open immediately.

[0157] The switch state 496 is determined by the switch state algorithm. Possible values ​​for switch state 496 include: unknown, open, cannot be opened, closed, and cannot be closed. The switch action processing function 464 uses switch state 496 in conjunction with the active routing list 456 and the system routing table 468 to determine whether to attempt to open the switch, close the switch, or do nothing with the switch.

[0158] The route state 500 for each route is determined using a route state algorithm. Possible route states 500 include: Unknown, Disconnected, Cannot be disconnected, Connected, and Unconnected. The route state 500 is used by the load bus router 452 to select a feasible route. If a route cannot be connected, the load bus router 452 will select the next highest priority route (if that route is available).

[0159] Synchronizer function 504 exists in or is assigned to power sources that have the ability to adjust their voltage, frequency, and phase angle outputs to match the voltage, frequency, and phase angle outputs of another power source (such as a generator set). Switching action processing 464 requests this function when attempting to close between two energized / available power sources.

[0160] Section 5.1 - Controller like Figure 10 As shown, controller 508 represents a controller used by the power system within control scheme 440. Controller 508 may be separate from or included in at least one other controller in the power system. As further discussed below, the control distribution scheme envisioned herein allows computational power, redundancy, and general control calculations to be performed within a single controller circuit, or to be shared by multiple controllers across the power system. The function and structure of controller 508 are described in... Figure 10 It is described in more detail.

[0161] Now for reference Figure 10 A schematic diagram of a controller 508 according to an example embodiment is shown. Figure 10 As shown, controller 508 includes processing circuitry 512 with processor 516 and memory device 520, control system 524 with circuits A 528, B 532 and C 536, and communication interface 540. Typically, controller 508 is configured to control the operation of associated objects and function within a larger power routing control scheme 440.

[0162] In one configuration, circuits A 528, B 532, and C 536 are embodied as a machine- or computer-readable medium executable by a processor such as processor 516. As described herein and among other uses, the machine-readable medium facilitates the execution of certain operations to achieve the reception and transmission of data. For example, the machine-readable medium may provide instructions (e.g., commands, etc.) for acquiring data. In this respect, the machine-readable medium may include programmable logic that defines the frequency of data acquisition (or data transmission). The computer-readable medium may include code written in any programming language, including but not limited to Java and any conventional procedural programming language (e.g., the "C" programming language or similar programming languages). The computer-readable program code may execute on one processor or multiple remote processors. In the latter scenario, the remote processors may be interconnected via any type of network (e.g., a CAN bus, etc.).

[0163] In another configuration, circuits A 528, B 532, and C 536 are embodied as hardware units (e.g., electronic control units). Therefore, circuits A 528, B 532, and C 536 can be embodied as one or more circuit components, including but not limited to processing circuits, network interfaces, peripherals, input devices, output devices, sensors, etc. In some embodiments, circuits A 528, B 532, and C 536 can take the form of one or more analog circuits, electronic circuits (e.g., integrated circuits (ICs), discrete circuits, system-on-a-chip (SoC) circuits, microcontrollers, etc.), telecommunications circuits, hybrid circuits, and any other type of "circuit". In this respect, circuits A 528, B 532, and C 536 can include any type of component for performing or facilitating the implementation of the operations described herein. For example, the circuits described herein may include one or more transistors, logic gates (e.g., NAND, AND, NOR, OR, XOR, NOT, XNOR, etc.), resistors, multiplexers, registers, capacitors, inductors, diodes, wiring, etc. Circuits A 528, B 532, and C 536 may also include programmable hardware devices, such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc. Circuits A 528, B 532, and C 536 may include one or more memory devices for storing instructions executable by the processor of circuits A 528, B 532, and C 536. These memory devices and the processor may have the same definitions provided below regarding memory device 520 and processor 516. In some hardware unit configurations, circuits A 528, B 532, and C 536 may be geographically distributed across various individual locations within the power system. Alternatively, and as shown, circuits A 528, B 532, and C 536 may be embodied in or within a single unit / housing, which is shown as controller 508.

[0164] In the example shown, controller 508 includes processing circuitry 512 having processor 516 and memory device 520. Processing circuitry 512 may be constructed or configured to execute or implement the instructions, commands, and / or control processes described herein with respect to circuits A 528, B 532, and C 536. The depicted configuration represents circuits A 528, B 532, and C 536 as machine- or computer-readable media. However, as noted above, this illustration is not intended to be limiting, as this disclosure contemplates other embodiments in which circuits A 528, B 532, and C 536, or at least one of them, are configured as hardware units. All such combinations and variations are intended to fall within the scope of this disclosure.

[0165] Hardware and data processing components (e.g., processor 516) for implementing the various processes, operations, illustrative logic, logic blocks, modules, and circuits described in conjunction with the embodiments disclosed herein may be implemented or performed using: general-purpose single-chip or multi-chip processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate 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. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. In some embodiments, one or more processors may be shared by multiple circuits (e.g., circuits A 528, B 532, and C 536 may include or otherwise share the same processor, which in some example embodiments may execute instructions stored or otherwise accessed via different regions of memory). Alternatively or additionally, one or more processors may be configured to implement or otherwise perform certain operations independently of one or more coprocessors. In other example embodiments, 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 fall within the scope of this disclosure.

[0166] Memory device 520 (e.g., memory, memory cell, storage device) may include one or more devices (e.g., RAM, ROM, flash memory, hard disk storage) for storing data and / or computer code used to perform or facilitate the various processes, layers, and modules described herein. Memory device 520 may be communicatively connected to processor 516 to provide processor 516 with computer code or instructions for performing at least some of the processes described herein. Furthermore, memory device 520 may be or include tangible, non-transient volatile memory or non-volatile memory. Therefore, memory device 520 may include database components, object code components, scripting components, or any other type of information structure used to support the various activities and information structures described herein.

[0167] Circuit A 528 is responsible for the operation of the associated machine or object 544. For example, circuit A 528 can control the operation of a generator set, aftertreatment system, battery pack, switch, or any other object type. The control actions determined by circuit A 528 are transmitted to object 544 via communication interface 540.

[0168] Circuit B 532 is responsible for determining the objects to be controlled by circuit B 532. In a power system utilizing distributed control, circuit B 532 can communicate with other controllers 548 and / or sensors 552 to determine which objects fall under the guidance and control of controller 508.

[0169] Circuit C 536 is responsible for implementing power routing control 440 and communicating with external systems via communication interface 540 to activate / deactivate routing and complete other actions of power routing control scheme 440.

[0170] Despite Figure 9 and Figure 10 Various circuits with specific functions are illustrated herein, but it should be understood that controller 508 may include any number of circuits for performing the functions described herein. For example, the activities and functions of circuits A 528, B 532, and C 536 may be combined in multiple circuits or combined into a single circuit. Additional circuits with additional functions may also be included. Furthermore, controller 508 may control other activities beyond the scope of this disclosure. In some embodiments, the circuits described herein may include one or more processing circuits including one or more memory devices coupled to one or more processors, the one or more memory devices being configured to store instructions thereon that, when executed by the one or more processors, cause the one or more processors to perform the operations performed herein and described with reference to the circuits.

[0171] As described above, and in one configuration, the "circuit" can be implemented in a machine-readable medium so that it can be processed by various types of processors (e.g., Figure 10 The processor 516 executes the circuit. The identified executable code circuit may, for example, comprise one or more physical or logical blocks of computer instructions, which may be organized, for example, into objects, procedures, or functions. However, the executable file of the identified circuit does not need to be physically located together, but may include different instructions stored in different locations that, when logically connected together, constitute the circuit and achieve the intended purpose of the circuit. In practice, the circuit of computer-readable program code may be a single instruction or many instructions, and may even be distributed across several different code segments, across different programs, and across several memory devices. Similarly, operational data may be identified and illustrated within the circuit herein, and may be represented in any suitable form and organized within any suitable type of data structure. Operational data may be collected as a single dataset, or may be distributed across different locations, including across different storage devices, and may exist at least in part simply as electronic signals within the system or network.

[0172] While the term "processor" has been briefly defined above, the terms "processor" and "processing circuitry" are intended to be interpreted broadly. In this regard, and as stated above, a "processor" can be implemented as one or more general-purpose processors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), or other suitable electronic data processing components configured to execute instructions provided by memory. One or more processors can take the form of a single-core processor, a multi-core processor (e.g., a dual-core processor, a triple-core processor, a quad-core processor, etc.), a microprocessor, etc. In some embodiments, one or more processors can be external to the device, for example, one or more processors can be remote processors (e.g., cloud-based processors). Alternatively or additionally, one or more processors can be internal to the device and / or local to the device. In this regard, a given circuitry or its components can be located locally (e.g., as part of a local server, a local computing system, etc.) or remotely (e.g., as part of a remote server such as a cloud-based server). For this purpose, a "circuitry" as described herein can include components distributed across one or more locations.

[0173] Embodiments within the scope of this disclosure include program products comprising a machine-readable medium for carrying or having machine-executable instructions or data structures stored thereon. Such a machine-readable medium can be any available medium accessible by a general-purpose or special-purpose computer or other machine having a processor. For example, such a machine-readable medium may include RAM, ROM, EPROM, EEPROM, or other optical disc storage, disk storage, or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of machine-executable instructions or data structures and accessible by a general-purpose or special-purpose computer or other machine having a processor. Combinations of the foregoing are also included within the scope of machine-readable media. For example, machine-executable instructions include instructions and data that cause a general-purpose computer, special-purpose computer, or special-purpose processing machine to perform a function or a set of functions.

[0174] Section 5.2 - Controller Assignment Multiple controllers are typically dedicated to a single machine. In some cases, they may support multiple machines. One concept envisioned in this paper is that each instance of a power system object in a power system is "owned" by a controller, typically the one most directly associated with that object (i.e., the one with a specific I / O associated with it). In some cases, the object will have replicas or duplicated controls that operate across multiple controllers and use a floating principal model of distributed control to provide redundancy for functions requiring principal control.

[0175] The object model discussed above enables application flexibility. For some power systems, there will be more than one way to assign controllers to objects. This could be through conscious choices in the power system design or due to the machines involved. In some embodiments, if each load does not require load monitoring, then one controller might handle four switches; otherwise, it might require one controller for each or two switches.

[0176] In a classic ATS+ generator set system, there are two controllers with object assignment, such as... Figure 11As shown. Power system 556 includes a utility 560 connected to a utility power bus 564, providing grid power (e.g., providing alternating current (AC)), and a generator set 568 providing AC power to a generator set bus 572. The utility power bus 564 and generator set bus 572 are connected to an automatic transfer switch (ATS) 576. ATS 576 is also connected to a load bus 580. Automatic transfer switch 576 may be arranged or configured to provide power from either utility bus 564 or generator set bus 572 to load bus 580. Load 584 is connected to load bus 580 and consumes power provided by utility 560 or generator set 568. Power system 556 also includes a generator set controller 588 and a switch controller 592. Generator set controller 588 is primarily associated with generator set 568 and controls the operation of generator set 568. Switch controller 592 is primarily associated with ATS 576.

[0177] like Figure 12 As shown, objects in power system 556 are assigned to generator set controller 588, ATS controller 592, or both. The only overlap in assignments within power system 556 is on generator bus 572 (BG1). This overlap occurs because both generator set controller 588 (C1) and ATS controller 592 (C2) have sensing capabilities for generator bus 572 (BG1). Therefore, the object-based power routing control scheme discussed above will be implemented for generator set 568 and generator bus 572 with respect to generator set controller 588, and the object-based power routing control scheme will be implemented for the remaining objects with respect to ATS controller 592.

[0178] like Figure 13 As shown, the circuit breaker-based single-transfer pair, single-generator power system 596 includes a utility 600 connected to a utility power bus 604, providing grid power (e.g., providing alternating current (AC)), and a generator set 608 providing AC power to a generator set bus 612. The utility power bus 604 is connected to a utility power circuit breaker 616, and the generator set bus 612 is connected to a generator set circuit breaker 620. Circuit breakers are switch-type objects. The utility power circuit breaker 616 and the generator set switch 620 are connected to a load bus 624, and a load 628 is connected to the load bus 624. A single controller 632 (e.g., a generator set controller) manages the entire power system 596 and therefore has all the necessary I / O interfaces to all five power system objects, and will have all the functions associated with these objects, such as... Figure 16 The allocation diagram is shown below.

[0179] like Figure 14 As shown, power system 596' is similar to Figure 13 The power system 596' is labeled with components marked with apostrophes. Power system 596' includes two controllers: generator set controller 636 and utility circuit breaker controller 640. This is possible because utility circuit breaker 616' is located away from generator set 608' and generator set circuit breaker 620'. One advantage of power system 596' is that the status of load bus 624' (LB1) can be known and measured. Figure 16 As shown, generator set 608', generator set circuit breaker 620', load bus 624', generator set bus 612', and load 628' are assigned to generator set controller 636. Utility 600', utility circuit breaker 616', load bus 624', utility bus 604', and load 628' are assigned to utility circuit breaker controller 640.

[0180] like Figure 15 As shown, the power system 596” is similar to Figure 13 The power system 596 is labeled with components marked with double apostrophes. Power system 596” includes three controllers: generator set controller 644, utility circuit breaker controller 648, and generator set circuit breaker controller 652. This arrangement is desirable because utility circuit breaker 616” and generator set circuit breaker 620” are located away from and far from each other, such as… Figure 16 As shown, generator set 608” and generator bus 612” are assigned to generator set controller 644. Utility 600”, utility circuit breaker 616”, load bus 624”, utility bus 604”, and load 628” are assigned to utility circuit breaker controller 648. Generator circuit breaker 620”, load bus 624”, generator bus 612”, and load 628” are assigned to generator circuit breaker controller 652.

[0181] like Figure 17 As shown, similar to the above regarding Figure 4 The power system 190' of the discussed power system 190 is shown, and objects are labeled with a series of apostrophes. In addition to showing the communication paths, Figure 17The assignment of objects to each controller 294', 298', 302', 306', 310', and 314' is also shown. For example, the first generator set controller 294' receives information from the generator set branch bus 250', the first generator set bus 266', and the first generator set switch 214', and also provides information or control signals to the first generator set switch 214'. Communication arrows are not provided for the second generator set controller 298' and the third generator set controller 302' to provide better clarity in the figures. Figure 17 The document also demonstrates how to share load bus router functionality among utility switch controller 306', generator branch switch controller 310', and load bus controller 314'. Similarly, Figure 17 The load sharing function is shown to be distributed among the first generator set controller 294', the second generator set controller 298', and the third generator set controller 302'. Figure 18 The assignment of objects in the power system 190' is shown.

[0182] Section 5.3 - Object and Function Implementation There are different methods that can be used to implement the objects in the controller of the power system discussed above. The power system object in this disclosure is a container for the functions associated with that object that operate at the power system control level.

[0183] One object implementation method includes an embedded software application for a controller that is hard-coded (e.g., compiled) with a fixed (e.g., maximum) number of objects of each type and the complete set of functionality contained in each object. For example, the controller may support up to two power objects, three bus objects, two switch objects, and two load objects. In some embodiments, the controller may support more or fewer objects or be associated with more or fewer objects. The available object options may not be used if needed. For example, some installations may not require the maximum number of available objects. Which instances of available objects in the controller are used is set during debugging or configuration.

[0184] In another approach, the controller has a more complex operating system and can only instantiate objects at runtime as needed.

[0185] Object-based approaches allow for improved activation and configuration via setup tools. All controllers in a power system include identical object / function software code, which is then configured to define which objects / functions are needed, which objects the controller is responsible for (i.e., allocation), where the objects are located in the system's single-line topology (i.e., routing map or table), and further user customization of behavior via various other settings (e.g., power output, time limits, capacity, etc.). Computer-based setup tools can be used to define and configure the power system. These tools can include a palette library of all possible system objects and their variations. Users select objects from the library, drag them to the drawing area, and draw the single-line topology for their power system. Once the power system is drawn and the locations of the controllers are included, each object is assigned an identity and other relevant settings. The setup tool is then able to export the system routing table. Once the system routing table is generated, the setup tool connects to the power system network where the controllers reside and sends configuration data to each controller. Once the configuration data is uploaded to the controllers, the single-line topology and object-based control are initiated.

[0186] In this approach, the tool uses an object-oriented method to draw a single-line topology, set all necessary properties for each object, and then automatically connects to the system and downloads the appropriate settings to all controllers from a single connection point. The tool includes a palette library of all supported power system objects.

[0187] In typical generator set and microgrid control, generator dispatching, power routing, transfer control, and load shedding are usually manually coded into the controller by trained and experienced personnel during design and configuration simulation. Extensive testing is typically required to validate the correct operation of the microgrid and the dispatching for system stability. The designs are often not reusable to other sites or implementations, and any subsequent changes or updates to the microgrid system may require the same level of design and testing, leading to programming and configuration difficulties and a lack of system redundancy.

[0188] This tool suggests properties for each object and allows users / designers to change these properties. It automatically connects to the system and downloads appropriate settings from a single connection point with the microgrid to all controllers, eliminating the need for manual system-to-system controller configuration. The tool supports the commissioning process and the simulation and / or testing of the resulting design.

[0189] Section 6.1 - Centralized Control The power systems discussed above operate within an object-based framework that provides communication and collaboration between objects to enable elegant control schemes that improve ease of commissioning and reliability. This section discusses various control schemes that can be implemented within the framework of the power systems discussed above.

[0190] like Figure 19 As shown, the centralized control scheme 656 includes a controller (traditionally referred to as the master controller 660) that is responsible for telling other controllers 664 what to do. The other controllers 664 are traditionally referred to as slave controllers. The master controller 660 collects all necessary inputs from the other controllers 664 and itself, then runs its algorithm (e.g., a function) and produces outputs that then guide the actions of the other controllers 664. The operation of the power system depends entirely on the master controller 660.

[0191] like Figure 20 As shown, the centralized control scheme 668 with redundant controllers includes a primary controller 672 and adds a backup primary controller 676 to provide redundancy in case the primary controller 672 fails. Typically, the primary controller 672 and the backup primary controller 676 execute the same code in parallel and perform mutual checks. One controller is designated as the primary master 672, and the other is the secondary master 676. If the primary master 672 fails, the secondary master 676 will immediately step in and take over control of the other controllers 680. This method eliminates the single point of failure vulnerability of the centralized control scheme 656.

[0192] exist Figure 19 and Figure 20 In this configuration, the wiring connecting the master and slave controllers indicates that only the master device has any communication with the slave devices. Slave controllers do not communicate with each other. Communication may include transmitting information and / or signals over a hardwired architecture, using a communication link, or another communication system.

[0193] Section 6.2 - Distributed Control Distributed control in this disclosure refers to a control scheme that operates the entire power system without relying on a single controller. In other words, while the absence of a single controller may lead to a degradation in the operation of the power system, it will not render the power system completely inoperable. Figures 21-25 Three distributed control schemes are described, which, together with object-based methods, can build robust and redundant distributed control power systems.

[0194] Section 6.3 - Control of Floating Bodies like Figure 21As shown, the floating subject control scheme 684 includes multiple controllers 688, each capable of performing a specific system function, but this function necessitates execution by only one "brain" or action controller at any given time. That is, there exists a form of control that can be described as centralized control, even if it is actually only used for a single task or function. The action controller currently in the role of performing the function is referred to as the subject controller 692. Other controllers 688 capable of performing the function but not currently the active subject controller 692 are referred to as participant controllers. If the subject controller 692 fails at any time or otherwise becomes unable to perform its duties to the power system, one of the participant controllers seamlessly intervenes and takes over the role of the subject controller 692. This behavior is described as a floating subject because the subject can float to any controller 688 capable of performing the function.

[0195] Each controller 688, currently in the role of a participant in a specific system function, has three options regarding how to handle that function. First, it can refuse to execute the function and only begin running it when controller 688 becomes the principal controller 692. Execution rejection is performed if seamlessness is not required when controller 688 assumes the role of principal controller 692. Second, controller 688 can run the function asynchronously (relative to the current principal controller 692) and compute its output, even if its output is not currently being used. In asynchronous operation, if controller 688 becomes principal controller 692, then controller 688 will typically be within the same execution iteration having the same output as the former principal controller 692. Third, controller 688 can operate the locking step synchronously with principal controller 692, making any takeover completely seamless.

[0196] like Figure 22 As shown, the current master controller 692 collects all inputs from all participant controllers 688 and itself. The master controller 692 then computes outputs / commands to pass to all participant controllers 688 and itself. Except for the algorithmic outputs of the participant controllers 688, which are not used, each participant controller 688 may be doing exactly the same thing as the master controller 692.

[0197] The selection of the principal controller 692 can be automatically determined among controllers in the power system. In some embodiments, each controller 688 includes a unique controller or object ID, and the controller 688 with the lowest object ID number is selected as the principal controller 692.

[0198] Section 6.4 - Fully Distributed Control Some power system functions are inherently suited to fully distributed control models, rather than agent / participant models. For example... Figure 23 As shown, in the fully distributed control scheme 696, all controllers 700 performing a specific system function are equivalent. A characteristic that makes them fully distributed is that each controller 700 determines its own action, rather than determining the actions for other controllers as in the case of the master controller in the floating master control scheme 684. The fully distributed control scheme 696 can also be referred to as a self-determining method.

[0199] like Figure 24 As shown, the general case of the information flow of the fully distributed control scheme 696 gives the example of each controller 700 collecting all the required inputs and only calculating commands / outputs for itself. Figure 24 Only what a single controller 700 is doing is shown, but each controller 700 is performing calculations simultaneously.

[0200] Section 6.5 - Redundancy Control While the floating controller control scheme 684 and the fully distributed control scheme 696 do reduce the impact of single-point controller failures on power system control in many scenarios, the possibility remains that the absence of a single controller could significantly impact the normal operation of the power system. For example... Figure 25 As shown, the redundant floating master scheme 704 includes multiple controllers 708, each of which can act as the master controller 712. Furthermore, a redundant controller 716 is installed at a critical location in the power system topology. A scheme similar to that of the floating master control scheme 684 is then used to determine which controller 708 or redundant controller 716 currently acts as the master controller 712.

[0201] exist Figure 21 , Figure 23 and Figure 25 In this diagram, the lines between controllers are intended to represent communication between each controller and all other controllers. The roughly circular representation simplifies the appearance of the system, but the connections between each controller and every other controller are intentional.

[0202] Section 6.6 - Examples Return to Figure 17The power system 190' includes bus objects that include a load bus router function configured as a floating principal type function. The utility switch controller 306', load bus controller 314', and generator branch switch controller 310' all "own" or are assigned to the load bus 258', and therefore, any one of them can be the principal controller for the load bus router function of the load bus 258'. Using a scheme that selects the controller with the lowest ID as the principal controller, the utility switch controller 306' will be identified as the principal controller.

[0203] In some embodiments, the first generator set controller 294', the second generator set controller 298', or the third generator set controller 302' may also be provided as the main controller for load bus router functions, but the main controller for load bus router functions would advantageously be able to sense the voltage of the load bus 258'. The only controllers capable of sensing the voltage of the load bus 258' are the utility switch controller 306', the load bus controller 314', and the generator set branch switch controller 310'. If any of these controllers fails, then no other controller can perform the work of performing the load bus router function. Therefore, in practice, not all controllers are equivalent, and the functions requiring main control may come from different subsets (depending on the function) of all controllers in the power system.

[0204] Figure 17 The diagram also illustrates a load-sharing function that exists across all power objects and operates in a fully distributed manner. Each of the first generator controller 294', the second generator controller 298', or the third generator controller 302' owns a power object. Each of these three controllers 294', 298', and 302' performs an instance of its load-sharing function by consuming data from the other controllers and itself, and then calculating the results for its own use.

[0205] In a more specific example of a distributed control scheme, the goal of load sharing is to allow each power source to share the load equally. The controller on each power source publishes its current load value data. The first generator controller 294' sums the loads of all generators 198', 202', and 206' and calculates the average load. The first generator controller 294' then compares its current load value to the average load. If its current load is less than the average load, then it is not carrying enough load. The first generator controller 294' will then act to increase the power output of the first generator 198'. The second generator controller 298' is doing the same thing and determining its own necessary corrections, and the third generator controller 302' is doing the same. Therefore, each generator controller only determines its own actions, without determining the actions that the other generator controllers need to take.

[0206] It's possible that a fully distributed algorithm or a floating principal algorithm might have multiple instances within a single controller. Referring to the fully distributed example above, a single controller might have two power objects, and therefore two separate instances of load-sharing functionality. This still means that each instance of that functionality operates in a fully distributed manner, even though it exists within a single controller. The absence of that controller would result in two power object absences.

[0207] With two instances of the floating body function within a controller, two participants will be able to act as the floating body within that controller. If the controller fails, the number of participants in the function's pool will decrease by two.

[0208] As used herein, the terms “approximately,” “about,” “substantially,” and similar terms are intended to have a broad meaning consistent with common and accepted usage by one of ordinary skill in the art to which the subject matter of this disclosure pertains. Those skilled in the art who read this disclosure will understand that these terms are intended to allow for the description of certain features described and claimed, without limiting the scope of these features to the precise numerical ranges provided. Therefore, these terms should be interpreted as indicating that non-substantial or irrelevant modifications or alterations to the described and claimed subject matter are considered within the scope of this disclosure as set forth in the appended claims.

[0209] It should be noted that the terms “exemplary” and variations thereof used herein to describe the various embodiments are intended to indicate that these embodiments are possible examples, representations or illustrations of possible embodiments (and these terms are not intended to imply that these embodiments are necessarily special or the highest level examples).

[0210] As used herein, the term "coupling" and its variations refer to the direct or indirect connection between two components. This connection can be stationary (e.g., permanent or fixed) or movable (e.g., removable or releasable). Such a connection can be achieved by: two components being directly coupled to each other; two components being coupled to each other using one or more separate intermediate components; or two components being coupled to each other using intermediate components that are integrally formed with one of the two components as a single unit. If "coupling" or its variations are modified by an additional term (e.g., direct coupling), the general definition of "coupling" provided above is modified by the common linguistic meaning of the additional term (e.g., "direct coupling" means the connection between the two components does not involve any separate intermediate component), resulting in a narrower definition than the general definition of "coupling" provided above. This coupling can be mechanical, electrical, or fluid. For example, circuit A being communicatively "coupled" to circuit B could mean that circuit A communicates directly with circuit B (i.e., without intermediate components) or indirectly with circuit B (e.g., through one or more intermediate components).

[0211] References to element positions (e.g., "top", "bottom", "above", "below") herein are used only to describe the orientation of the various elements in the accompanying drawings. It should be noted that the orientation of the various elements may differ according to other exemplary embodiments, and such variations are intended to be covered by this disclosure.

[0212] Although the accompanying drawings and descriptions may illustrate a specific order of method steps, the order of these steps may differ from what is depicted and described, unless otherwise stated above. Furthermore, unless otherwise stated above, two or more steps may be performed simultaneously or partially simultaneously. For example, such variations may depend on the chosen software and hardware system and the designer's choices. All such variations are within the scope of this disclosure. Similarly, the software implementation of the described method can be accomplished using standard programming techniques with rule-based logic and other logic to perform the various connection steps, processing steps, comparison steps, and decision steps.

[0213] It is important to note that the construction and arrangement of the power systems, objects, and control schemes shown in the various exemplary embodiments are merely illustrative. Furthermore, any element disclosed in one embodiment may be combined with or used in conjunction with any other embodiment disclosed herein. Additionally, elements from a preceding section (e.g., Section 1.4 - Load Objects) may be combined with or used in conjunction with any other elements described in a separate section (e.g., Section 4 - Signal Flow). For example, regarding... Figure 3 (For example, the object parameters and functions of the exemplary embodiments described in Section 1 - Objects) can be combined with information about Figure 4 , Figure 7 , Figure 9 , Figure 10 , Figure 11 , Figures 13-15 and Figure 17 (For example, Section 5.2 – Controller Assignment) describes exemplary embodiments of power systems and objects. Although the foregoing has described only one example of how elements from one embodiment can be incorporated into or used in another embodiment, it should be understood that other elements of the various embodiments can be combined with or used in conjunction with any other embodiments disclosed herein.

Claims

1. An apparatus for providing coordinated control, comprising: The circuit is constructed as follows: Identify the first power object, the second power object, and the load bus object; Determine the positions of the first power object, the second power object, and the load bus object on the single-line topology; Receive operation parameters from the first power object, the second power object, and the load bus object; A first route is defined using the single-line topology, the first route including objects electrically connected between the first power object and the load bus object; The single-line topology is used to define a second route, which includes all objects electrically connected between the second power object and the load bus object. and Control the operation of the first route and the second route; The circuit is configured to generate an active route list and a transition type, the active route list including desired routes, and a switch action processing function is configured to determine changes to the active route list based on the transition type, and to determine whether the associated switch will be closed, opened, or remain in its current state.

2. The apparatus according to claim 1, wherein, The circuit is also configured to generate a routing table that includes all available routes.

3. The apparatus according to claim 1, wherein, Controlling the first route includes selectively activating the first route by controlling the closing action of a switch object included on the first route, and deactivating the first route by controlling the opening action of at least one switch object on the first route.

4. The apparatus according to claim 3, wherein, Activating the first route includes communicating with all objects on the first route and coordinating the activation action of each object before initiating the closing action of the switch objects included on the first route.

5. The apparatus according to claim 1, wherein, Defining the first route includes communicating with all objects electrically connected between the first power object and the load bus object to define inclusions on the first route within the control circuitry associated with the object.

6. The apparatus according to claim 1, wherein, The circuit is also configured to use the single-line topology to define a third route, which is different from and in parallel with the first route, and the third route includes all objects electrically connected along the third route between the first power object and the load bus object.

7. The apparatus according to claim 6, wherein, The first route defines a first priority value, while the third route defines a second priority value that is higher than the first priority value.

8. The apparatus according to claim 7, wherein, The first priority value is proportional to the number of switch objects included in the first route, while the second priority value is proportional to the number of switch objects included in the third route.

9. The apparatus according to claim 6, wherein, Only one of the first route and the third route is activated simultaneously during continuous use after the transition time.

10. The apparatus according to claim 1, wherein, The circuit is also configured to disable the second route, thereby preventing the second route from being activated.

11. A system for providing coordinated control, comprising: A first generator set controller, which is associated with a first generator set and a first generator set switch; The second generator set controller is associated with the second generator set and the second generator set switch; A generator set branch switch controller, which is associated with a generator set branch switch, the generator set branch switch being coupled to a first generator set switch and a second generator set switch via a generator set branch bus; A utility switch controller, which is associated with a utility switch; and A load bus controller, associated with a load bus coupled to the generator set branch switches and the utility switches. The system is configured to generate a routing table, which is defined as follows: The first route includes the first generator set, the first generator set switch, the generator set branch bus, the generator set branch switch, and the load bus. The second route includes the second generator set, the second generator set switch, the generator set branch bus, the generator set branch switch, and the load bus. The third route includes the utility switch and the load bus. The system also generates an active route list and transition types. The active route list includes desired routes, and the switch action processing function is configured to determine changes to the active route list based on the transition types, and to determine whether the associated switches will be closed, opened, or remain in their current state. The system selectively activates the first route by communicating with the first generator set controller, the generator set branch switch controller, and the load bus controller. The system selectively activates the second route by communicating with the second generator set controller, the generator set branch switch controller, and the load bus controller. The system selectively activates the third route by communicating with the utility switch controller and the load bus controller.

12. The system according to claim 11, wherein, The load bus controller includes a load bus routing function that determines which of the first, second, and third routes should be activated or deactivated, and provides a conversion type function to each controller associated with any switch on any route to enable activation or deactivation.

13. The system according to claim 12, wherein, The switch action processing function is configured to receive the conversion type function from the load bus controller and control the operation of the first generator set and the first generator set switch to activate or deactivate the first route.

14. The system according to claim 13, wherein, The switch action processing function is also configured to request activation of the synchronizer function before the first generator set switch is closed, the synchronizer function adjusting the voltage, frequency and phase angle of the first generator set output.

15. The system according to claim 13, wherein, The switch action processing function is configured to transmit the switch status function to the load bus routing function, and The active route list is generated by the load bus routing function based on the switch status function.

16. A method for providing coordinated control, comprising: A single-line topology of a power system, including power objects, switch objects, bus objects, and controller objects, is generated by a controller that includes circuitry and at least one processor coupled to memory. The controller populates each object with operational parameters; The controller generates a routing table that defines the available routes between power objects and bus objects, with each route including all objects electrically connected between the power object and the bus object on the route; The controller generates an active route list and transition types, the active route list including desired routes, wherein a switch action processing function is configured to determine changes to the active route list based on the transition types, and to determine whether the associated switches will be closed, opened, or remain in their current state; and The controller controls the power system by activating or deactivating routes.

17. The method according to claim 16, wherein, Select the operation parameters for each object from the object configuration library.

18. The method according to claim 16, wherein, The active route list includes a list of routes to be activated or deactivated; and It also includes a list of routes that the controller passes conversion types to switch objects to control the activation or deactivation of routes.

19. The method of claim 16, wherein, The routing table assigns route ID, enable attribute, route priority, and route path to each route.

20. The method of claim 16, wherein, Each controller object is assigned to one or more of the power object, the switch object, and the bus object to implement control of the power system by activating or deactivating routing.

21. A non-transitory computer-readable medium containing computer-executable instructions that, when executed by a circuit of a power system, cause the power system to perform functions to activate or deactivate routing, the functions including: Identify the first power object, the second power object, and the load bus object; Determine the positions of the first power object, the second power object, and the load bus object on the single-line topology; Receive operation parameters from the first power object, the second power object, and the load bus object; A first route is defined using the single-line topology, the first route including objects electrically connected between the first power object and the load bus object; The single-line topology is used to define a second route, which includes all objects electrically connected between the second power object and the load bus object. and Controlling the operation of the first and second routes, The function further includes generating an active route list and a transition type, the active route list including desired routes, and wherein the switch action processing function is configured to determine changes to the active route list based on the transition type, and to determine whether the associated switch will be closed, opened, or remain in its current state.

Images