What's needed?
In microgrids, we implement a crucial safety measure called "Precharging" when connecting batteries to inverters. Precharging involves gradually ramping up the DC voltage to prevent any potential damage to sensitive electrical components like capacitors. To achieve this, a precharge circuit operates in parallel to the DC bus.
The process begins by activating the precharge circuit, allowing the voltage to rise gradually. Once the voltage stabilizes at an acceptable level, the main connection is closed, and the precharge circuit is subsequently opened.
While many inverters and batteries come equipped with in-built precharging mechanisms, some may lack this feature. In such cases, we need to ensure full support for external precharge modules within our APIs. This support enables seamless integration and control of external precharge modules, safeguarding electrical components and contributing to the overall reliability and efficiency of the microgrid system.
Please look here for the corresponding issue in the common proto specs: frequenz-floss/frequenz-api-common#44
Proposed solution
The Microgrid API should facilitate streaming data from Precharge components. Therefore, it needs data definitions. For an example of such data definitions, please refer to the for inverters here.
The data definition should support the following states: PRECHARGING, PRECHARGED, and INACTIVE.
Additionally, the Microgrid API should also support the start and stop methods for Precharge components.
Invoking the start method should cause a state transition from INACTIVE to PRECHARGING to PRECHARGED. The stop command should cause a state transition from PRECHARGED to INACTIVE.
Use cases
No response
Alternatives and workarounds
No response
Additional context
No response
What's needed?
In microgrids, we implement a crucial safety measure called "Precharging" when connecting batteries to inverters. Precharging involves gradually ramping up the DC voltage to prevent any potential damage to sensitive electrical components like capacitors. To achieve this, a precharge circuit operates in parallel to the DC bus.
The process begins by activating the precharge circuit, allowing the voltage to rise gradually. Once the voltage stabilizes at an acceptable level, the main connection is closed, and the precharge circuit is subsequently opened.
While many inverters and batteries come equipped with in-built precharging mechanisms, some may lack this feature. In such cases, we need to ensure full support for external precharge modules within our APIs. This support enables seamless integration and control of external precharge modules, safeguarding electrical components and contributing to the overall reliability and efficiency of the microgrid system.
Please look here for the corresponding issue in the common proto specs: frequenz-floss/frequenz-api-common#44
Proposed solution
The Microgrid API should facilitate streaming data from Precharge components. Therefore, it needs data definitions. For an example of such data definitions, please refer to the for inverters here.
The data definition should support the following states:
PRECHARGING,PRECHARGED, andINACTIVE.Additionally, the Microgrid API should also support the start and stop methods for Precharge components.
Invoking the start method should cause a state transition from
INACTIVEtoPRECHARGINGtoPRECHARGED. The stop command should cause a state transition fromPRECHARGEDtoINACTIVE.Use cases
No response
Alternatives and workarounds
No response
Additional context
No response