Open Volodymyr233 opened 3 weeks ago
Hey @Volodymyr233,
due to the log files not beeing wireshark log files we need some more time for inspecting.
But I can tell you that need to send the "Update DC Charging Parameters" on EVSE side after the schedules are requested by the EV.
Please allow some more time for investigation.
Best regards, lho
Before you post
I can't pair two devices: WhiteBeet EV and WhiteBeet EVSE. The process reaches the "Session Started" messages from both devices. Then the EVSE takes a few more steps:
Message: Payment Selected Message: Autorization Status Requested -> Command: Set Autorization Status Message: Energy Transfer Mode Selected Message: Schedules Requested -> Command: Set Schedules Message: DC Charge Parameters Changed -> Repeatable Command: EVSE Update DC Charging Parameters.
EV waits timeout and then breaks session.
I provide a couple of log files for each side. One file is received via the UART port of the WhiteBeet debug board. The second is an interception of the SPI exchange between the host and the debug board. I cleaned up the duplicate commands. What I noticed: EVSE accepted DC charging parameters from EV. But EV did not. Although Session ID, Device ID were accepted! That is, the physical connection works. I do not quite understand at what point to start repeating "Update DC Charging Parameters" command on the EVSE side. I do this when receiving a message from EV "DC Charge Parameters Changed".
Best regards, Volodymyr.
Log-files for EV side: EV_2024-10-21_18-11-10.log EV_21101810.log Log-files for EVSE side: EVSE_2024-10-21_18-11-02.log EVSE_21101810.log