Unexpected session stop when processing ISO15118-2 AC charge parameters response

[mbirtwistle]

Your Setup Platform: PEV Firmware Version: i.e. V01_00_07 Host Controller Interface: Ethernet Host: FreeV2G (EV_v1.0.7_0) / Own Implementation

Describe the bug

During an AC ISO15118-2 session, the EV session unexpectedly stops with a debug message 'Battery current out of range!'.
This is because the _handleACChargeParametersChanged method incorrectly calculates the target battery in_current

self.battery.in_current = self.schedule['power'][self.currentSchedule] / self.currentAcMaxCurrent

The nominal voltage from the EVSE response should be used to work out the target current, note that a few lines above, self.battery.in_voltage is assigned the value from the 'nominal_voltage' response parameter

so I believe the self.battery.in_current should be calculated as

self.battery.in_current = self.schedule['power'][self.currentSchedule] / self.battery.in_voltage

To Reproduce

• Set the EV configuration up to negotiate an AC single or 3 phase ISO15118-2 session.
• Ensure the configured battery dc and your evse side ac power, voltage and current parameters are in range for the provided power schedule
• note that FreeV2G seems to hardcode a rapid charging power schedule and you will likely need to turn down the power values on that for a typical AC charging scenario. I used power values of 7500, 5000, 3000 when simulating for a single phase ac 32 amps, 240 volts scenario

Expected behavior The session should continue on to sending the next state machine request rather than aborting the session.

Logs not submitting logs as the code above is clearly not following the I=P/V rule

Additional context

[lho-stx]

Hey @mbirtwistle,

Thanks for contributing and pointing out!

Thank you very much, lho