Skip to content

Conversation

@FaHaGit
Copy link
Contributor

@FaHaGit FaHaGit commented Dec 2, 2025

Describe your changes

Currently, as soon as V2G communication is unexpectedly terminated by a failed response code and the EV does not send a SessionStopReq, the dlink action parameter is incorrectly left at the initial value "dlink_error". This means that a connected EvseManager is not notified when V2G communication is terminated in this error case. However, the enum value dlink_error does not make sense within the EvseV2G module, as a data-link error cannot be detected by this module.

Issue ticket number and link

Checklist before requesting a review

  • I have performed a self-review of my code
  • I have made corresponding changes to the documentation
  • I read the contribution documentation and made sure that my changes meet its requirements

Copy link
Contributor

@corneliusclaussen corneliusclaussen left a comment

Choose a reason for hiding this comment

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

LGTM

Additionally, improved the naming of the elements and
class member.

Signed-off-by: Fabian Hartung <[email protected]>

EvseV2G: Set default d_link_action to D_LINK_ACTION_TERMINATE

Removed the unused D_LINK_ACTION_ERROR and made D_LINK_ACTION_TERMINATE
the new default value after initilization of the "conn" structure.

This commit solves the issue that d_link_action is not correctly configured to
D_LINK_ACTION_TERMINATE when a session ends unexpectedly without SessionStop
(before lingered on D_LINK_ACTION_ERROR).

Signed-off-by: Fabian Hartung <[email protected]>
@FaHaGit FaHaGit force-pushed the fix/unexpected_dlink_action branch from 5c6aa40 to ae84401 Compare December 5, 2025 14:46
@FaHaGit
Copy link
Contributor Author

FaHaGit commented Dec 5, 2025

I squashed the commits

@FaHaGit
Copy link
Contributor Author

FaHaGit commented Dec 10, 2025

@SebaLukas What I forgot to ask in the working group. Can we merge this pull request or do you want to review it first.

@SebaLukas SebaLukas added this pull request to the merge queue Dec 10, 2025
@SebaLukas
Copy link
Member

Sry I had a look into your PR last week but did not click on approved 🙈 I added it to the merge queue

Merged via the queue into EVerest:main with commit 1769a97 Dec 10, 2025
12 checks passed
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