BACKGROUND

[0001] With a rise in the reliance on renewable energy, new challenges arise in supplying power to off-grid facilities. Such challenges include the storage of renewable energy, cost of renewable energy, and reliability of renewable energy. Today, hybrid power systems allow for off-grid facilities to be powered by a variety of power generation sources, including renewable sources. These systems allow off-grid facilities to rely on renewable energy sources when available, but also allow facilities to use power from a grid when renewable energy sources are not available or viable.

[0002] However, these hybrid power systems are often costly to install and require

multiple units in order to utilize power from a variety of sources. Due to this, a large amount of effort is required to integrate and maintain these separate units together. The use of multiple units also requires customers to designate a large amount of space for the units, space an off-site facility may not have. Further, when one unit malfunctions or deactivates, the hybrid power system may not function until that unit is repaired or replaced, causing a loss of time to the off-site facility.

SUMMARY

[0003] Provided herein are system, apparatus, article of manufacture, method and/or computer program product embodiments, and/or combinations and sub-combinations thereof, for a power tracking and control architecture.

[0004] An embodiment includes a power management control system. The power

management control system may include a plurality of power assets arranged in a tiered network that is arranged in a tree architecture. A first tier of this tiered network may comprise a controller configured to output a data telegram communicating a desired output for a power generation source. A second tier of this tiered network may comprise at least one power asset configured to receive, by a first communication path of the tiered network, the data telegram from the first tier, adjust an output of the power generation source according to the data telegram from the first tier, and report, by a second communication path of the tiered network, an update of the power generation source to the first tier. Further, a third tier of this tiered network may comprise at least one power asset configured to receive, by the first communication path of the tiered network, the data telegram from the second tier.

[0005] Another embodiment includes, in a tiered network comprising a controller and a plurality of power assets arranged in a tree architecture, a system. The system includes a memory and at least one processor of a second tier of the tiered network coupled to the memory. The processor may be configured to receive, by a first communication path of the tiered network, a data telegram from a first tier of the tiered network, wherein the data telegram comprises a desired output for a power generation source visualize a plurality of available analytic data in a graphical user interface. Further, the processor may be configured to adjust the output of the power generation source according to the data telegram. Additionally, the processor may be configured to report, by a second communication path of the tiered network, an update of the power generation source to the first tier of the tiered network and send, by the first communication path of the tiered network, the data telegram to a third tier of the tiered network.

[0006] A further embodiment includes, in a tiered network comprising a controller and a plurality of power assets arranged in a tree architecture, a method. The method may comprise compiling a data telegram, wherein the data telegram comprises a plurality of blocks. The method may also comprise sending, by a first communication path of the controller, the data telegram to a second tier of the tiered network, wherein at least one power asset of the second tier of the tiered network is configured to update a power profile according to at least one block of the data telegram. Additionally, the method may comprise receiving, by a second communication path of the tiered network, an update from the at least one power asset of the second tier of the tiered network.

BRIEF DESCRIPTION OF THE DRAWINGS

[0007] FIG. 1 is a diagram illustrating an example of a hybrid power control system 100, according to an embodiment.

[0008] FIG. 2 is a diagram illustrating an example of a hybrid power control unit 200, according to an embodiment. [0009] FIG. 3 is a diagram illustrating an example of hybrid power control module 300, according to an embodiment.

[0010] FIG. 4 is a diagram illustrating system architecture 400 for hybrid power control module 300, according to an embodiment.

[0011] FIG. 5 is a diagram illustrating bi-directional communication between one through

N tiers of system architecture 400, according to an embodiment.

[0012] FIG. 6 is a diagram illustrating data telegram 600, according to an embodiment.

[0013] FIG. 7 is a flowchart illustrating a process for sending a data telegram between tires of system architecture 400, according to an embodiment.

[0014] The drawing are representative of embodiments of the invention. In the drawings, like reference numbers generally indicate identical or similar elements. Additionally, generally, the left-most digit(s) of a reference number identifies the drawing in which the reference number first appears.

DETAILED DESCRIPTION

[0015] Provided herein are system, method and/or computer program product embodiments, and/or combinations and sub-combinations thereof, for exporting analytic data.

[0016] FIG. 1 is a diagram illustrating an example of a hybrid power control system 100, according to an embodiment. The hybrid power control system 100 may comprise power controller 102, plurality of power generation sources 104 (comprising power sources 104a, 104b, 104c, and 104d), plurality of loads 106 (comprising loads 106a, 106b, 106c, 106d, 106e, and 106f), and plurality of power storages 108 (comprising power storage 108a, 108b, 108c, 108d, 108e, and 108f). According to an embodiment, power

generations sources 104 may comprise a plurality of power generation source types such as photovoltaic solar panels, wind turbines, diesel generators, electrical grids,

hydroelectric sources, or any combination thereof— to name a few.

[0017] According to an embodiment, power characteristics of the power generated by power generation sources 104 may be dependent on environmental conditions. The power characteristics may comprise the frequency, voltage, current, amplitude, or any combination thereof, of the power generated. The environmental conditions may comprise solar irradiance, temperature of the environment, temperature of the power generation source, mass of the air, or any combination thereof— to name a few. For example, power generation sources 104 may comprise a photovoltaic solar panel which outputs power at a voltage that is dependent upon solar irradiance (i.e. the voltage of the power generated by the solar panel changes as the solar irradiance changes).

[0018] According to an embodiment, power generation sources 104 may be connected to power controller 102. Power controller 102 may comprise a microcontroller unit (MCU), maximum power point tracker (MPPT), grid rectifier, distributed generation (DG) rectifier, inverters, or any combination thereof— to name a few. In an embodiment, power controller 102 may control characteristics of the power generated by power generation sources 104. Power controller 102 may control these power characteristics through adjusting loads attached to a power generation sources, pulse width modulation (PWM), maximum power point tracking, automatic gain control (AGC), or any combination thereof— to name a few examples.

[0019] In another embodiment, power controller 102 may maintain desired characteristics of power generated by power sources 104 wherein the power generated is dependent on environmental conditions. Power controller 102 may maintain desired characteristics of the power generated through the use of PWM or maximum power point tracking, to name a couple of examples. For example, the voltage of power generated by a photovoltaic solar panel may change based on the solar irradiance. Power controller 102 may be configured to maintain a desired voltage for the power generated by the photovoltaic solar panel through the use of PWM or maximum power point tracking.

[0020] In an embodiment, power controller may control the activation and deactivation of power generation sources 104. Power controller 104 may control the

activation/deactivation of power generation sources 104 through the sending of activate/deactivate commands, electronic switching, mechanical switching, or any combination thereof— to name some examples.

[0021] In an embodiment, power generated by powers generation sources 104 is fed to loads 106 and power storage 108. Loads 106 may comprise a plurality of load types found at different locations such load types found at oil pipelines, telecommunication stations, residential homes, oil rigs, cities, offices, factories, military facilities, or any combination thereof. Each of the load types may have different power requirements for the loads to operate. Such power requirements may comprise desired frequencies, voltages, currents, amplitudes, or any combination thereof. According to an embodiment, the power flow from power generation sources 104 to loads 106 is regulated by power controller 102 based on these power requirements, as discussed further in the discussion of FIG. 2.

[0022] In an embodiment, power storages 108 may comprise a plurality of power storage types such as batteries, flywheels, capacitors, deep-cycle batteries, or any combination thereof— to name a few. Each of the power storage types may have different power requirements to allow the power storage types to store energy. Such power requirements may comprise desired frequencies, voltages, currents, amplitudes, or any combination thereof. For example, power storage 108 may comprise a plurality of batteries that require a desired voltage in order to charge. According to an embodiment, the power flow from power generation sources 104 to power storage 108 is regulated by power controller 102 based on these power requirements, as discussed further in the discussion of FIG. 2.

[0023] FIG. 2 is a diagram illustrating an example of a hybrid power control unit 200, according to an embodiment. The hybrid power control unit 200 may comprise power controller 202, plurality of charge controllers 212, a plurality of charge controllers 214, a plurality of inverter modules 216, or any combination thereof. In an embodiment, the hybrid power control system may control the distribution of power from a plurality of power sources (204, 206, 208, and 210 respectively) to plurality of loads 220 and plurality of power storages 218. The plurality of power sources may comprise

photovoltaic solar panels 204, wind turbines 206, diesel generators 208, an electrical grid 210, or any combination thereof— to name a few examples. Power controller 202 may control the flow of the power outputs from the power sources to charge controllers 212, charge controllers 214, power storages 218, inverter modules 216, or any combination thereof. Power controller 202 may comprise a MCU, a computer, a mobile device, or any combination thereof— to name a few.

[0024] According to an embodiment, power controller 202 may control the flow of the power outputs through multiplexers 222 and 224. Multiplexers 222 and 224 may comprise a plurality of electrical switches, a plurality of logic gates, digital multiplexors, or any combination thereof— to name a few examples.

[0025] The power outputs of each of the power sources may be fed into multiplexer 222.

Multiplexer 222 may receive a command from power controller 202 that determines how the outputs from the power sources are forwarded to charge controllers 212, charge controllers 214, power storages 218, multiplexer 224, or any combination thereof. The power outputs of multiplexer 222, charge controllers 212 and charge controllers 214 may be fed into multiplexer 224. Multiplexer 224 may receive a command from power controller 202 that determines how the outputs from multiplexer 222, charge controllers 212 and charge controllers 214 are forwarded to power storages 218 and invertors 216.

[0026] For example, the power sources may comprise photovoltaic solar panels 204, wind turbines 206, diesel generators 208, and an electrical grid 210. The outputs of these power sources may be fed into multiplexer 222. Muliplexer 222 may receive a command from controller 202 that comprises data instructing multiplexer 222 to forward the power output from photovoltaic solar panels 204 to charge controllers 212, the power output from wind turbines 206 to multiplexer 224, and the power output from diesel generator 208 to charge controllers 214.

[0027] Building on this example, multiplexer 224 may receive a command from power controller 202 that comprises data instructing multiplexer 224 to forward the power output from charge controllers 212 to inverter modules 216, the power output from wind turbines 206 to power storages 218, and the output from charge controllers 214 to power storages 218.

[0028] Charge controllers 212 and 214 may comprise MPPTs, grid rectifiers, DG

rectifiers, PWN controllers, or any combination thereof. In an embodiment, charge controllers 212 and 214 may receive commands from power controller 202 comprising a power profile. The power profile may comprise data to control the power characteristics of the power generated by the plurality of power sources and output a power with desired characteristics to meet the power requirements of power storages 218 and loads 220.

[0029] For example, power storages 218 may comprise a plurality of batteries requiring direct current (DC) to charge. By way of multiplexer 222, the power output from diesel generator 208 (in alternating current (AC)) may be fed to charge controllers 214 which comprise DG rectifiers. Charge controllers 214 may receive a power profile from power controller 202 comprising data for charge controllers 214 to rectify the power output from the diesel generator from AC to DC .

[0030] As another example, loads 220 may comprise a type of load that requires a desired voltage to operate. By way of multiplexer 222, the power output from photovoltaic solar panels 204 may be fed to charge controllers 212 which comprise MPPTs. Charge controllers 212 may receive a power profile from power controller 202 to control the voltage of the power output of the photovoltaic solar panels to meet the desired voltage required for the loads to operate.

[0031] According to an embodiment, loads 220 may comprise types of loads that require

AC to operate. Inverter modules 216 may convert power received from the power generation sources and charge controllers from DC to AC, if necessary. For example, a power output from wind turbines 206 may output in DC and be fed to inverter modules 216. Inverter modules 216 may convert the power from wind turbines 206 from DC to AC to meet the requirements of the types of loads of loads 220.

[0032] FIG. 3 is a diagram illustrating an example of hybrid power control module 300, according to an embodiment. In an embodiment, hybrid power control module may comprise a power distribution unit (PDU) 304, MCU 306, a plurality of charge controllers 308 comprising charge controller modules 308a-d, a plurality of rectifiers 310 comprising rectifier modules 3 lOa-d, and a plurality of inverters 312 comprising inverter modules 312a and 312b. According to an example embodiment, hybrid power control module 300 may be located in a single housing 302.

[0033] PDU 304 may comprise a plurality of electrical input connections and a plurality of electrical output connections. The electrical input and output connections may be rated for a variety of voltages, currents, frequencies, or any combination thereof— to name a few.

[0034] In an embodiment, the electrical input connections of PDU 304 may be connected to a plurality of power generation sources. Power generated from the plurality of generation sources may flow from the power generation sources to charge controllers 308, rectifiers 310, and invertors 312 of hybrid power control module 300 via the electrical input connections of PDU 304, with the flow of power being controlled by MCU 306 as described in the discussion of FIG. 2.

[0035] According to an embodiment, power outputs from the power generation sources as well as charge controllers 308, rectifiers 310, and invertors 312 of hybrid power control module 300, may flow to the electrical output connections of PDU 304. The electrical output connections of PDU 304 may be connected to power storages 218 and loads 220. The flow of power from the power generation sources and charge controllers 308, rectifiers 310, and invertors 312 to power storages 218 and loads 220,connected via the electrical output connects of PDU 304, may be controlled by MCU 306 as described in the discussion of FIG. 2.

[0036] In an embodiment, charge controllers MCU 306, 308, rectifiers 310, and invertors

312 of hybrid power control module 300 may be hot swappable. When MCU 306, a charge controller, rectifier, or inverter of hybrid power control module 300 is removed and replaced with another power asset of the same type, the newly installed power asset will continue to operate as the power asset that it replaced. For example, a charge controller in hybrid power control module 300 may be programmed to receive a power output from photovoltaic solar panels 204, control the voltage of the power output from photovoltaic solar panels 204 to a desired voltage, and output the controlled power output to power storages 218. When this charge controller is removed from hybrid power control module 300 and replaced with a new charge controller, the new charge controller will continue to operate as the replaced charge controller.

[0037] According to an embodiment, hybrid power control module 300 may include a memory. The memory may comprise ROM, PROM, EEPROM, or any combination thereof— to name a few examples. The memory of hybrid power control module 300 may be connected to MCU 306, charge controllers 308, rectifiers 310, and invertors 312 and may store power profiles received by MCU 306, charge controllers 308, rectifiers 310, and invertors 312. For example, a charge controller of hybrid power control module 300 may receive a power profile from MCU 306 instructing the charge controller to control the voltage of the power output from photovoltaic solar panels 204 to a desired voltage for power storages 218. The memory of hybrid power control module 300 may store this command and apply it to any charge controller that replaces the original.

[0038] In another embodiment, a power asset that replaces an original asset may

communicate with other power assets in the system through the bi-directional

communication of the system architecture further discussed in FIG. 5. By communicating with the other power assets in the system, a newly installed power asset may ascertain its placement and role within the system and operate as the power asset that was replaced.

[0039] For example, a charge controller of hybrid power control module 300 may be programmed to receive a power output from photovoltaic solar panels 204, control the voltage of the power output from photovoltaic solar panels 204 to a desired voltage, and output the controlled power output to power storages 218. When this charge controller is removed and replaced with a new charge controller, the new charge controller may communicate with the other power assets in the system to ascertain its placement and role in the system and will operate as the charge controller that was replaced.

[0040] In an embodiment, MCU 306 may receive signals from remote location 314.

Remote location may comprise a computer, a mobile device, a mobile phone, a MCU, or any combination thereof— to name a few examples. MCU 306 may receive signals from remote location 314 via radio, intranet, internet, WIFI, a cellular network, or any combination thereof.

[0041] According to an embodiment, when MCU 306 receives a signal from remote location 314, MCU 306 may compile a data telegram, as depicted in the discussion of FIG. 6. The data telegram may comprise commands for the power flow and power profiles for charge controllers 308, rectifiers 310, and invertors 312 of hybrid power control module 300 as described in the discussion of FIG. 2

[0042] FIG. 4 is a diagram illustrating system architecture 400 for hybrid power control module 300, according to an embodiment. In an embodiment, system architecture 400 may comprise a plurality of tiers in a tree architecture with each tier comprising a plurality of power assets. Power assets may comprise MCU 306, charge controllers 308, rectifiers 310, invertors 312 of hybrid power control module 300, or any combination thereof.

[0043] In an embodiment, a first tier of the system architecture 400 comprises power asset 402 which may comprise a MCU, a computer, a mobile device, or any combination thereof. Power asset 402 may be configured to receive signals from remote location 314. When power asset 402 receives a signal from remote location 314, power asset 402 may compile a data telegram, as described further in the discussion of FIG. 6. The data telegram may comprise commands for the power flow and power profiles for charge controllers 308, rectifiers 310, and invertors 312 of hybrid power control module 300 as described in the discussion of FIG. 2

[0044] According to an embodiment, power asset 402 may send the data telegram to a second tier of the system architecture 400. The second tier of the system architecture 400 may comprise a plurality of power assets, such as power assets 404, 406, or any combination thereof. Power assets of the second tier of the system architecture 400 may comprise MCUs, charge controllers 308, rectifiers 310, invertors 312 of hybrid power control module 300, or any combination thereof. In an example embodiment, the second tier of system architecture 400 may comprise up to up to 16 power assets.

[0045] In an embodiment, each power asset of the second tier may process the data

telegram received as discussed in the method of FIG. 7. Once the data telegram has been processed, each power asset of the second tier may send the data telegram to a third tier of the system architecture 400. The third tier of the system architecture 400 may comprise a plurality of power assets, such as power assets 408, 410, 412, 414, or any combination thereof. Power assets of the second tier of the system architecture 400 may comprise MCUs, charge controllers 308, rectifiers 310, invertors 312 of hybrid power control module 300, or any combination thereof.

[0046] According to an embodiment, each power asset of the second tier is connected to a group of assets of the third tier. For example, power asset 404 may by connected to power assets 408 and 410 of the third tier and power asset 406 may be connected to power assets 412 and 414 of the third tier. In an example embodiment, each power asset of the second tier is connected to a group of up to 16 power assets of the third tier.

[0047] In an embodiment, after the power assets of the second tier have processed the data telegram as discussed in the method of FIG. 7, each power asset of the second tier may send the datagram to the group of power assets of the third tier for which it is connected. For example, power asset 404 may send the data telegram to power assets 408 and 410 and power asset 406 may send the data telegram to power assets 412 and 414.

[0048] In an embodiment, each power asset of the third tier may process the data

telegram received from the second tier as discussed in the method of FIG. 7. Once the data telegram has been processed, each power asset of the third tier may send the data telegram to a fourth tier of the system architecture 400. The fourth tier of the system architecture 400 may comprise a plurality of power assets, such as power assets 416, 418, 420, 422, 424, 426, 428, and 430 or any combination thereof.

[0049] According to an embodiment, as with the second tier, each power asset of the third tier is connected to a group of assets of the fourth tier. For example, power asset 408 may be connected to power assets 416 and 418 of the fourth tier, power asset 410 may be connected to power assets 420 and 422 of the fourth tier, power asset 412 may be connected to power assets 424 and 426 of the fourth tier, and power asset 414 may be connected to power assets 428 and 430 of the fourth tier. In an example embodiment, each power asset of the third tier is connected to a group of up to 16 power assets of the fourth tier.

[0050] In an embodiment, after the power assets of the third tier have processed the data telegram as discussed in the method of FIG. 7, each power asset of the third tier may send the datagram to the group power assets of the fourth tier for which it is connected. For example, power asset 408 may send the data telegram to power assets 416 and 418, power asset 410 may send the data telegram to power assets 420 and 422, power asset 412 may send the data telegram to power assets 424 and 426, and power asset 414 may send the data telegram to power assets 428 and 430.

[0051] In an embodiment, each power asset of the fourth tier may process the data

telegram received from the third tier as discussed in the method of FIG. 7. Once the data telegram has been processed, each power asset of the third tier may send the data telegram to a fifth tier of the system architecture 400. The fifth tier of the system architecture 400 may comprise a plurality of power assets, such as power assets 432, 434, 436, 438, 440, and 442 or any combination thereof.

[0052] According to an embodiment, the fourth tier and the fifth tier are likewise

connected as the second tier to the third tier, or the third tier to the fourth tier, as demonstrated in FIG. 4. In an example embodiment, each power asset of the fourth tier may be connected to up to 16 power assets of the fifth tier.

[0053] In another embodiment, system architecture 400 may comprise a number of tiers likewise connected together as depicted in FIG. 4.

[0054] FIG. 5 is a diagram illustrating bi-directional communication between one

through N tiers of system architecture 400, according to an embodiment. In an

embodiment, each power asset allows for bi-directional communication. Each power asset within a tier of system architecture 400 comprises two signal lines. Signal lines may comprise receiver (RX) lines, transmitter (TX) lines, serial lines, buses, or any

combination thereof— to name a few examples.

[0055] According to an embodiment, the tiers of system architecture 400, may transfer data over two data pathways in parallel, i.e. two streams of data may be transferred between the tiers simultaneously. A first data pathway may comprise data paths comprising connections between the first signal lines of each power asset between tiers within system architecture 400, and a second data pathway may comprise data paths comprising connections between the second signal lines of each power asset between tiers within system architecture 400.

[0056] For example a first data pathway between tier 1 502, tier 2 504, tier 3 506, and tier

N 508 of system architecture 400 may comprise data paths 510, 514, and 518. Wherein data path 510 comprises the connections between the first signal lines of the power assets of tier 1 502 and tier 2 504, data path 514 comprises the connections between the first signal lines of the power assets of tier 2 504 and tier 3 506, and data path 518 comprises the connections between the first signal lines of the power assets of tier 3 506 and tier N 508.

[0057] As another example, a second data pathway between tier 1 502, tier 2 504, tier 3

506, and tier N 508 of system architecture 400 may comprise data paths 512, 516, and 520. Wherein data path 512 comprises the connections between the second signal lines of the power assets of tier 1 502 and tier 2 504, data path 516 comprises the connections between the second signal lines of the power assets of tier 2 504 and tier 3 506, and data path 520 comprises the connections between the second signal lines of the power assets of tier 3 506 and tier N 508.

[0058] According to an embodiment, a data telegram from MCU 306 may be sent to each tier using the first pathway of system architecture 400. While the data telegram is being sent between the tiers, the second signal pathway of system architecture 400 may be used by the power assets to send responses to MCU 306 as detailed in the method of FIG. 7.

[0059] In an embodiment, the bi-directional communication may be used by a power asset to communicate with other power assets in the system to determine its position in system architecture 400 and its role in hybrid power control module 300. The position may comprise the power asset's location in the tiered structure of system architecture 400 and the role may comprise power profiles sent from MCU 306. For example, a replacement power asset may request information from power assets to which it is connected. The requested information may comprise the position information of the power assets to which the replacement power asset is connected, the latest data telegram received, identification information of the power assets to which it is connected, or any combination thereof— to name a few examples.

[0060] According to another embodiment, the bi-directional communication may be used to create redundancy within system architecture 400. When a power asset with system architecture 400 deactivates or malfunctions, the bi-directional communication can be used to alert other power assets within system architecture 400 that such a deactivation or malfunction has occurred. For example, a power asset may detect that a malfunctioned power asset is no longer connected. The power asset may then alert, via the bi-directional communication, other power assets within the system architecture 400 that the

malfunction has occurred, allowing the other power assets to compensate for the malfunction.

[0061] As an example, a power output from photovoltaic solar panels 204 may be fed to five MPPTs (power assets) within tier 3 of system architecture 400 that have received power profiles from MCU 306 to regulate the current to 50A, for example, in order to charge batteries within power storages 218. To provide 50A to the batteries, each of the 5 MPPTs may output 10A to the batteries, for example. If one of the five MPPTs malfunction, other power assets within the system may alert, via the bi-directional communication of system architecture 400, the other four MPPTs that the malfunction has occurred. In response to the alert, the other four MPPTs may alter their power profiles to output 12.5A each in order to provide 50A to the batteries, for example.

[0062] FIG. 6 is a diagram illustrating data telegram 600, according to an embodiment. In an embodiment, data telegram 600 may comprise blocks 602, 604, 606, and 608. Block 602 may comprise synchronization bits, or a synchword. Synchronization bits may comprise data indicating the end of header information and the beginning the data, or frame, of the data telegram 600.

[0063] According to an embodiment, block 604 may comprise object type bytes. Object type bytes may comprise data indicating the type of power assets for which the data telegram is intended. For example, MCU 306 may send data telegram 600 instructing MPPTs of the second tier to change their power profile to control the current of photovoltaic solar panels 204 and output 10A. In this case, block 604 of data telegram 600 may comprise object type bytes comprising data indicating the data telegram is meant for MPPTs of the second tier.

[0064] In an embodiment, block 606 may comprise data bytes. Data bytes may comprise data indicating commands to power assets. These commands may comprise changes to power profiles, request for responses, activation/deactivation requests, or any

combination thereof— to name a few. For example, MCU 306 may send data telegram 600 instructing MPPTs of the second tier to change their power profile to control the current of photovoltaic solar panels 204 and output 10A. In this case, block 606 of data telegram 600 may comprise data bytes comprising data indicating to change power profiles to control the current of photovoltaic solar panels 204 and output 10A.

[0065] According to an embodiment, block 608 may comprise a number of objects for which an answer is requested. The answer requested may be status information, power profile information, connection information, or any combination thereof— to name a few. For example, MCU 306 may send a data telegram 600 instructing MPPTs of the second tier to change their power profile to control the current of photovoltaic solar panels 204 and output 10A and requesting that five MPPTs of the second tier answer with status information. In this case, block 608 may comprise information indicating that five MPPTs are to respond with an answer with status information.

[0066] FIG. 7 is a flowchart illustrating a process for sending a data telegram in system architecture 400, according to an embodiment.

[0067] At block 702, an exemplary data telegram is constructed by MCU 306. For

example, MCU 306 may construct a data telegram instructing MPPTs of the second tier to change their power profile to control the current of photovoltaic solar panels 204 and output 10A and that five answer with status information. In this case, a data telegram would be constructed comprising block 604 that comprises data indicating the data telegram is meant for MPPTs of the second tier, block 606 that comprises data indicating to change power profiles to control the current of photovoltaic solar panels 204, and block 608 that comprises information indicating that five MPPTs are to respond with an answer with status information.

[0068] At block 704, the data telegram is sent to the next tier of data architecture 400 via the first communication path. For example, MCU 306 may send the data telegram to power assets of the second tier via the first communication path.

[0069] At block 706, the power assets that received the data telegram via the first

communication path determine whether the object type data of the data telegram matches the type of the power asset that received the data telegram. For example, the power assets of the second tier may receive a data telegram comprising instructions that MPPTs of the second tier change their power profile to control the current of photovoltaic solar panels 204 and output 10A and that five MPPTs of the second tier answer with status information. Each power asset of the second tier will then determine whether they match the object type of the data telegram. In this case, only assets that are MPPTs would determine that they match the object type.

[0070] If a power asset determines that it does not match the object type of the data

telegram, the system will then repeat block 704 and send the data telegram to a next tier via the first communication path. If a power asset does determine that it does match the object type of the data telegram, the system will then move on to block 708.

[0071] At block 708, the power assets that matched the object type determine whether the number of assets indicated by the data telegram has been met. For example, the power assets of the second tier may receive a data telegram comprising instructions MPPTs of the second tier to change their power profile to control the current of photovoltaic solar panels 204 and output 10A and that five MPPTs of the second tier answer with status information. Each power asset of the second tier that matched the object type will then determine whether five MPPTs have already responded to the data telegram. A power asset may determine this based on its position in the system architecture 400.

[0072] If a power asset determines that the number of assets has been met, the system will then repeat block 704 and send the data telegram to the next tier via the first communication path. If a power asset determines that the number of assets has not been met, the system will then move on to block 710.

[0073] At block 710, the power assets that matched the object type and determined the number of objects had not been met perform operations based on the data telegram. For example, the power assets of the second tier may receive a data telegram comprising instructions MPPTs of the second tier to change their power profile to control the current of photovoltaic solar panels 204 and output 10A and that five MPPTs of the second tier answer with status information. In this case, power assets that matched the object type and determined the number of objects had not been met will change their power profile to control the current of photovoltaic solar panels 204 and output 10V.

[0074] At block 712, power assets that performed the operations based on block 606 of the data telegram, send a response, via the second communication path, to MCU 308. For example, the power assets of the second tier may receive a data telegram comprising instructions MPPTs of the second tier to change their power profile to control the current of photovoltaic solar panels 204 and output 10A and that five MPPTs of the second tier answer with status information. In this case, power assets that performed the operations based on block 606 of the data telegram, send a response, via the second communication path, to MCU 308 comprising status information. The system will then repeat block 704 and send the data telegram to the next tier via the first communication path.

[0075] It is to be appreciated that the Detailed Description section, and not the Summary and Abstract sections (if any), is intended to be used to interpret the claims. The

Summary and Abstract sections (if any) may set forth one or more but not all exemplary embodiments of the invention as contemplated by the inventor(s), and thus, are not intended to limit the invention or the appended claims in any way.

[0076] While the invention has been described herein with reference to exemplary

embodiments for exemplary fields and applications, it should be understood that the invention is not limited thereto. Other embodiments and modifications thereto are possible, and are within the scope and spirit of the invention. For example, and without limiting the generality of this paragraph, embodiments are not limited to the software, hardware, firmware, and/or entities illustrated in the figures and/or described herein. Further, embodiments (whether or not explicitly described herein) have significant utility to fields and applications beyond the examples described herein.

[0077] Embodiments have been described herein with the aid of functional building

blocks illustrating the implementation of specified functions and relationships thereof. The boundaries of these functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternate boundaries can be defined as long as the specified functions and relationships (or equivalents thereof) are appropriately performed. Also, alternative embodiments may perform functional blocks, blocks, operations, methods, etc. using orderings different than those described herein.

[0078] References herein to "one embodiment," "an embodiment," "an example

embodiment," or similar phrases, indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it would be within the knowledge of persons skilled in the relevant art(s) to incorporate such feature, structure, or characteristic into other embodiments whether or not explicitly mentioned or described herein.

The breadth and scope of the invention should not be limited by any of the above- described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.