Skip to content

Feature/dynamic_ac_config: Introduce CP state E#1778

Open
FaHaGit wants to merge 5 commits intoEVerest:mainfrom
chargebyte:feature/dynamic_ac_config/introduce_cp_state_E
Open

Feature/dynamic_ac_config: Introduce CP state E#1778
FaHaGit wants to merge 5 commits intoEVerest:mainfrom
chargebyte:feature/dynamic_ac_config/introduce_cp_state_E

Conversation

@FaHaGit
Copy link
Contributor

@FaHaGit FaHaGit commented Jan 29, 2026

Describe your changes

Under the term “feature/dynamic_ac_config,” we at chargebyte want to integrate the feature for dynamic configuration of an AC session into everest-core in stages.

The first step is to enable the BSP implementation to configure CP state E. This state is used as an alternative to CP state F to initiate a reinitialization of a charging session.

Furthermore, the existing commands were adapted so that the naming matches the new command.

The question remains whether the external API (evse_board_support_API.yaml) should be modified or whether the old naming should be retained. Currently, the external API has also been modified. Feedback would be welcome here.

Summary of changes:

  • Renames EVSE board support commands: pwm_off → cp_state_X1 and pwm_F → cp_state_F across interfaces, implementations, wrappers, simulators, and tests.
  • Updates API documentation and type converters to match the new CP state naming.
  • Introduces supports_cp_state_E in HardwareCapabilities and wires the capability flag through types/adapters.

Tests: Successfully tested with sil-dc and sil-ac

Issue ticket number and link

Zulip chat about the board_support refactoring:
https://lfenergy.zulipchat.com/#narrow/channel/417675-EVerest-General/topic/Configuring.20CP.20State.20E.20via.20the.20evse_baord_support.20interface

Zulip chat dynamic AC configuration feature announcement:
https://lfenergy.zulipchat.com/#narrow/channel/417675-EVerest-General/topic/Refactoring.20EvseManager.20for.20Fake.20DC/with/570586322

Checklist before requesting a review

  • I have performed a self-review of my code
  • I have made corresponding changes to the documentation
  • I read the contribution documentation and made sure that my changes meet its requirements

@FaHaGit FaHaGit force-pushed the feature/dynamic_ac_config/introduce_cp_state_E branch 2 times, most recently from 6d664dd to 41ee43f Compare January 30, 2026 13:19
- introduce cp_state_E command to set Control Pilot line to 0 V
- update YAML and implementation files to handle new command
- log warning for unsupported hardware in various drivers
- add CP state E button in the BUEvseBoardSupport module

Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
…wareCapabilities

- update type converters and API to handle new capability
- modify board support implementations to initialize supports_cp_state_E

Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
- rename all instances of pwm_F to cp_state_F for clarity
- update function names, variables, and documentation accordingly

Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
- Update function names and references from 'pwm_off' to 'cp_state_X1' across multiple files
- Modify test cases and documentation to reflect the changes

Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
@FaHaGit FaHaGit force-pushed the feature/dynamic_ac_config/introduce_cp_state_E branch from 41ee43f to 8f24f6e Compare January 30, 2026 14:33
- show HW caps
- move button, use different color
- fix call

Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants