Adapt interpretation of minimum SOC for EVCS

[sebastian-peter]

Currently, we're forcing EVs to charge until they reached some minimum SOC, and above that level EMs are free to do whatever they want, which leads to large differences in charged energy compared to non-em-controlled behavior.

What we want instead is something like this:
EVCS is free to do what it wants with EVs (charge, discharge if v2g is enabled, do nothing). At some point in time though, we force charging before the EV leaves (we know the departure time). This point in time is exactly the last moment where charging with full power leads to an EV with minimum SOC.

To have a somewhat energy-equivalent behavior when not em-controlling the EVCS, maybe the regular (non-em-controlled) behavior would be to charge until minimum SOC as well, and then stop charging.

Discovered by @danielfeismann.

[danielfeismann]

I couldn't have described it better. Thank you for creating this issue @sebastian-peter. In order to be flexible for further developments, maybe we should give a target SoC that the car could give optionally, otherwise the target SoC would be 100% I guess, right?

[sebastian-peter]

@danielfeismann Yes, sounds right.

And just to spell it out: For discharging with v2g, the target SOC should not be relevant, right? So there should not be a necessity to discharge an EV with 100% SOC because the target is 80%?

[danielfeismann]

No, I don't think so. But we may should think about some minimum level that never should be touched in case v2g takes place?

But we should be careful not over engineering this...

[sebastian-peter]

In that case we'd have the minSOC as it is now, and additionally a targetSOC. Makes logical sense, I'll think about if this would be too cumbersome to implement

[danielfeismann]

I would like to adapt this as well so we have the possibility either to provide a global upper and lower limit as well as get individual ones for each vehicle. So it would be possible that the MobilitySim provide e.g. the distance of the next trip which would allow to estimate a minimum SoC. But imho this is not a must feature...