Everest Charge Control C 1.6.0#96
Open
FaHaGit wants to merge 5 commits intoeverest/charge_control_cfrom
Open
Conversation
Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
- update initialization instructions of git sub modules Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
lategoodbye
reviewed
Apr 24, 2026
| - `-` | ||
|
|
||
| In order to use High-Level Communication, the EVerest modules *EvseV2G* and *EvseSlac* must be considered. | ||
| In order to use High-Level Communication, the EVerest modules *EvseV2G*, *Evse15118D20* and *EvseSlac* must be considered. |
Member
There was a problem hiding this comment.
Do we need to mention IsoMux here?
| - `standardized/SecurityCtrlr.json: SecurityCtrlrIdentity`: In "attributes" adapt the "value" key to configure the SecurityCtrlrIdentity. It is the Charging Station identity. | ||
|
|
||
| For further information about the device model initialization, please refer to the | ||
| `libocpp documentation <https://github.com/EVerest/libocpp/blob/main/doc/v2/ocpp_201_device_model_initialization.md>`_. |
Member
There was a problem hiding this comment.
Not sure, if this complete section still applies
Contributor
There was a problem hiding this comment.
It does not, it has moved into the main EVerest mono-repository.
Member
There was a problem hiding this comment.
Okay, how should we handle this? Drop the "important points" completely ?
| prepared for the basic AC PWM charger setup. | ||
|
|
||
| Just type "less /etc/everest/bsp-only.conf" to see the content of the configuration file: | ||
| Just type "less /etc/everest/bsp-only.yaml" to see the content of the configuration file: |
lategoodbye
reviewed
Apr 24, 2026
| Please note, however, that the range of functions described in the linked `libiso15118` library documentation may not | ||
| correspond to those already integrated in EVerest, as the library has not yet been fully integrated. | ||
| Implementation gaps may exist, particularly in the case of BPT (bidirectional power transfer) functionality. | ||
| For Plug & Charge related setup details, please also refer to the |
Member
There was a problem hiding this comment.
Maybe we should add a note, that for a real PnC use case the customer should contact us (regarding HSM/TPM).
barsnick
approved these changes
Apr 27, 2026
barsnick
requested changes
Apr 27, 2026
Contributor
barsnick
left a comment
barsnick
left a comment
There was a problem hiding this comment.
There are still three links to the obsolete libocpp repository in docs/source/troubleshooting.rst. The content can remain, but the links need to be updated to the new location in the mono-repo.
| ------------- | ||
|
|
||
| The internal eMMC storage of a chargebyte device is divided into several partitions. The main aim is to have two independent systems available, i.e. system A and system B. This allows to running firmware updates in background while performing normal charging operation, and then switching to the updated system with a fast restart of the device. This also allows to supporting a rollback mechanism in case of failures during firmware updates. In other words, during a firmware update, the active root file system switches from A to B or vice versa, leaving the other as rollback. | ||
| The internal eMMC storage of a chargebyte device is divided into several partitions. The main aim is to have two independent systems available, i.e. system A and system B. This allows firmware updates to run in the background while normal charging operation continues, and then switches to the updated system with a fast restart of the device. This also supports a rollback mechanism in case of failures during firmware updates. In other words, during a firmware update, the active root file system switches from A to B or vice versa, leaving the other as the rollback system. |
Contributor
There was a problem hiding this comment.
Can we break this line (in the RST source)?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refresh shared EVerest Charge Control C documentation for release 1.6.0