Skip to content

Conversation

hikinggrass
Copy link
Member

This is very likely a safer default behavior since it keeps control of the V2G connection at the EVSE

Describe your changes

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

This is very likely a safer default behavior since it keeps control of the V2G connection at the EVSE

Signed-off-by: Kai-Uwe Hermann <[email protected]>
@SebaLukas
Copy link
Member

The problem here is that some EVs dont like the immediately tcp/tls server shutdown and the cars wont charge about 5-30mins after this. Because the ECU crashed.
So the default should be false and not true

@hikinggrass hikinggrass marked this pull request as draft October 6, 2025 15:14
@kwoyhope
Copy link

The problem here is that some EVs dont like the immediately tcp/tls server shutdown and the cars wont charge about 5-30mins after this. Because the ECU crashed. So the default should be false and not true

How about setting SO_RCVTIMEO to short(ex, 1.5s) value on V2G_Resp_FAILED situation?
ie, not terminate socket connection immediately by EVSE on error but by socket recv timeout only when EV doesn't handle error immediately/correctly(ex, send SessionStopReq, or disconnect tcp/tls from EV(client) side first).
IMHO, this could help for both normal and abnormal(including PLC link fail) case of EV behavior.

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