Skip to content

CCY: update parameter block and safety protocol/DBC description - #117

Merged
mhei merged 4 commits into
everest/charge_control_yfrom
everest/charge_control_y_safety
Nov 17, 2026
Merged

mhei merged 4 commits into
everest/charge_control_yfrom
everest/charge_control_y_safety

Conversation

@mhei

@mhei mhei commented Nov 6, 2026

Copy link
Copy Markdown
Member

No description provided.

mhei added 3 commits November 6, 2026 12:03
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>
@mhei
mhei requested review from FaHaGit and martinlukas84 November 6, 2026 11:08
- 0x0 = FALSE
- 0x1 = TRUE
- 0x3 = NotConfigured

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see any documentation here yet for some signals such as SafeStateReason. Is that intentional?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, at least in this PR - yes. I think we have to check whether such a signal description needs to go into the DBC. Here, only the DBC is used as source...

Co-authored-by: barsnick <barsnick@users.noreply.github.com>
@mhei
mhei merged commit 2fcd6ea into everest/charge_control_y Nov 17, 2026
1 check passed
@mhei
mhei deleted the everest/charge_control_y_safety branch November 17, 2026 07:10
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