Release v0.20.0 and safety firmware v0.4.0 by mhei · Pull Request #10 · chargebyte/ra-utils

mhei · 2026-09-07T11:54:38Z

This PR adds support for upcoming configuration features of the safety firmware and the new safety firmware itself.

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>

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>

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>

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>

lategoodbye · 2026-09-11T12:50:46Z

+    INLET_STATE_OPENING = 0x2,
+    INLET_STATE_CLOSED = 0x3,
+    INLET_STATE_CLOSING = 0x4,
+    INLET_STATE_ERROR = 0x5,


The gap at 0x6 is intended?

lategoodbye · 2026-09-11T12:54:38Z

@@ -982,24 +982,29 @@ void cb_proto_dump(struct safety_controller *ctx)
    unsigned int i;

    if (!ctx->mcs) {


Not related to this change, but I would prefer to swap cases here for better readability

lategoodbye · 2026-09-11T13:05:42Z

+        case 5:
+        case 6:
+        case 7:
+            return errmsg_append_u32(buffer, size, &first, "FSP error code", additional_data_1);


lategoodbye · 2026-09-11T13:09:51Z

+- Scalar form: `disabled`, `disable`, `none`, or `off`
+- Mapping form:
+  - `abort-temperature`: temperature in `°C`
+  - `resistance-offset`: resistance offset in `Ω` or `Ω`


Both symbols look identical, is this intended?

lategoodbye · 2026-09-11T13:16:20Z

+        !(strcmp(endptr, "%") == 0 || strcmp(endptr, " %") == 0))
+        return -1;
+
+    if (val < 0 || val > 100)


Controversial: yes 0 and 100 are valid values, but shouldn't give some kind of warning?

lategoodbye · 2026-09-11T13:18:29Z

 install(
    FILES
-        chargesom_fw_v_00_03_01.bin
+        chargesom_fw_v_00_04_00.bin


Could you please specify the RX timeout in the commit message?

lategoodbye · 2026-09-11T13:24:23Z

+        param_block->crc = crc;

    if (fwrite(param_block, sizeof(*param_block), 1, f) != 1)
        return -1;


Not directly related to this change: Is there at least a chance to factor out this fwrite part?

mhei added 24 commits July 15, 2026 14:16

cb_protocol: add support to trigger inlet lock closing and opening

9a35f86

Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>

ra-raw: add Inlet State to output

975c346

While at, move Proximity Pilot to previous line to save one line. Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>

cb_protocol: add inlet related error codes

086021e

Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>

lib: bump SOVERSION to 6

c2044a2

Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>

Bump version to 0.20.0

a6b5144

Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>

ra-pb-dump: ensure an empty line between rcm and inlet config

ad27487

Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>

ra-pb-create: fix YAML parsing when inlet is specified after RCM

8f4d92b

Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>

Don't use hardcoded install path for systemd units

9dc70dd

Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>

cb_protocol: add missing/new inlet related error string

a1795ff

Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>

Update error code tables after safety firmware side cleanup

ace1a21

Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>

Dump also the numeric module identification and reason for error frames

e7d4afc

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>

firmware: add example YAML files with all possible keys for all versions

d9f36d2

Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>

README.md: add documentation for YAML files

18bd8d4

Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>

Add ra-candump command line helper

c391ff1

This tool is intended to support manual debugging of safety controller communication issues. Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>

Install ra-candump in sbin instead of bin

25a990b

Usually root permissions are needed for capturing. Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>

Add human-readable dump for ADC test errors

0c63aea

Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>

README.md: add hold-duty-cycle example

77cafb9

Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>

mhei requested review from lategoodbye and martinlukas84 September 7, 2026 11:54

ra-pb-create: introduce cmdline parameter -W or --wrong-crc

2bedf53

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>

lategoodbye requested changes Sep 11, 2026

View reviewed changes

Navigation Menu

Uh oh!

Release v0.20.0 and safety firmware v0.4.0 - #10

Release v0.20.0 and safety firmware v0.4.0#10
mhei wants to merge 25 commits into
mainfrom
feature/for-release-0.20.0

mhei commented Sep 7, 2026

Uh oh!

lategoodbye Sep 11, 2026

Uh oh!

lategoodbye Sep 11, 2026

Uh oh!

lategoodbye Sep 11, 2026

Uh oh!

lategoodbye Sep 11, 2026

Uh oh!

lategoodbye Sep 11, 2026

Uh oh!

lategoodbye Sep 11, 2026

Uh oh!

lategoodbye Sep 11, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

		@@ -982,24 +982,29 @@ void cb_proto_dump(struct safety_controller *ctx)
		unsigned int i;

		if (!ctx->mcs) {

Uh oh!

Conversation

mhei commented Sep 7, 2026

Uh oh!

lategoodbye Sep 11, 2026

Choose a reason for hiding this comment

Uh oh!

lategoodbye Sep 11, 2026

Choose a reason for hiding this comment

Uh oh!

lategoodbye Sep 11, 2026

Choose a reason for hiding this comment

Uh oh!

lategoodbye Sep 11, 2026

Choose a reason for hiding this comment

Uh oh!

lategoodbye Sep 11, 2026

Choose a reason for hiding this comment

Uh oh!

lategoodbye Sep 11, 2026

Choose a reason for hiding this comment

Uh oh!

lategoodbye Sep 11, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants