Release v0.20.0 and safety firmware v0.4.0 - #10
Open
mhei wants to merge 25 commits into
Open
Conversation
The inlet configuration allows to specify whether a lock is used or not. This is intended to cover AC use-cases. The driving time for both opening and closing the lock can be configured. The lock may or may not have a feedback contact which is evaluated with an ADC channel. When a feedback is used, the it is required to specify voltage ranges for "locked" and "unlocked" cases. Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
While at, move Proximity Pilot to previous line to save one line. Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
It was decided that the parameter block version v2 only include the RCM related configuration. For the upcoming inlet support (plug lock), the parameter block version 3 will be used. So, split the implementation accordingly. Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
Switch to the term "pluglock" instead of "inlet" in YAML and various visible error messages. Users are more familiar with it on EVSE side compared to "inlet" which is more often used on EV side. Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
This change is coming with a big difference in the binary representation: the former individual arrays are not reworked into a struct per contactor. And then there is an array with three contactor configurations elements. Since there is no official firmware release with parameter block v3 yet, we don't need any backwards compatible code and/or migrations. This 'economizer' feature is only available with Charge SOM hardware revision V1R2a or later and with matching safety controller firmware. Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
The safety controller can monitor the feedback pin of the eg. DRV8876. It is only reported once for every pluglock move request with an error message frame, but has no further impact. Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
This is important e.g. when safety firmware and this library are out-of-sync, e.g. when dealing with older or development firmware versions. Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
For the error frames which make use of additional data fields, add helper functionality to generate and better human-readable error message where the extra data is interpreted. Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
This tool is intended to support manual debugging of safety controller communication issues. Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
Usually root permissions are needed for capturing. Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
Changelog for Charge SOM platform (since 0.3.1): - requires parameter block version v2 - enter safe state on UART RX timeout - support for RCMs Changelog for Charge Control Y (parsley) (since 0.3.1): - requires parameter block version v2 - enter safe state on UART RX timeout Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
This allows to create parameter block binary files with a fixed and thus wrong CRC. Only for testing purpose! Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
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
2 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.
This PR adds support for upcoming configuration features of the safety firmware and the new safety firmware itself.