Skip to content

Conversation

@mhei
Copy link
Member

@mhei mhei commented Oct 30, 2025

No description provided.

mhei added 2 commits October 30, 2025 10:20
Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>

Since the open/close timings make no sense in case of `disabled` or `without-feedback`, it is possible to use these
tokens directly as array item (actually, it is also possible to use the `with-feedback...` ones, but then the timings
are considered zero).
Copy link
Member

Choose a reason for hiding this comment

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

Sorry, I'm not sure about the intention of this paragraph. Do you just want to say that close-time & open-time are optional and preinitialized with 0? In case of "with-feedback" it wont work because of the physics of a contactor, right?

Copy link
Collaborator

Choose a reason for hiding this comment

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

If you dont use feedback, the open/close times can be any value.
If you use feedback and leave the open/close time empty ... they will be 0 which will not work.

Maybe you can write:
Since the open/close timings make no sense in case of disabled or without-feedback, it is possible to use these
tokens directly as array item (actually, it is also possible to use the with-feedback... ones, but then the timings
are considered zero which will result in an error due to the latency in the contactor).


- 0x0 = NormalState
- 0x1 = SafeState
- 0x3 = SNA
Copy link
Member

Choose a reason for hiding this comment

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

What does it mean?

Copy link
Member Author

Choose a reason for hiding this comment

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

SignalNotAvailable

mhei added 2 commits November 3, 2025 16:59
Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
@mhei mhei merged commit c63b5bb into everest/charge_som Nov 4, 2025
1 check failed
@mhei mhei deleted the everest/charge_som-new-safety-fw branch November 4, 2025 14:33
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.

4 participants