Charging session not working when PEV is requesting secured connection, but WHITE Beet EVSE does not offer it.

[Ivangel1972]

Platform: EVSE
Firmware Version: i.e. V02_01_00
Host Controller Interface: SPI
Host: Own Implementation

Describe the bug
As in the title: Ford E-mach, does not start communication after V2G2 Start listen command. I tried a solution with the addition of the Set SDP Config command, but this also does not bring a positive resulatu.
When the car is plugged in and next to the charging socket, the charging initiation indicator lights flash white, then, after calling the V2G2 Start listen command on the car, these lights turn red and the car does not respond in any way. I tried changing the protocols to DIN alone or ISO alone - no change. I tried setting only one energy trasnfer mode (Extended) but even that does not help.
I can provide the configuration for all the commands BEFORE the V2G2 Start listen command, but I based it on your FreeV2G program and basically we only differ in the other IDs (ISO and DIN EVSE ID)

To Reproduce

Expected behavior
In the older FW, i.e. 01_01_07 the same car starts charging correctly, it looks like the problem lies in the FW of the WhiteBeet module - please verify this and solve the problem.

Logs
Of course, I can post the SPI log between the CPU and the WhiteBeet module, but I think it's pointless - all the other cars we've tested so far, as well as those tested on stations of our production, charge without problems.
Unfortunately I have NO way to download the log from the port mirror - only from the SPI.

Regards
Marcin Matusiak

[lho-stx]

Hey @Ivangel1972,

creating the log files is not pointless, else I do not have any clue what is going on. I may not see the V2G traffic but the framing messages are a first indication what is wrong.

Please create the UART and SPI logfiles accordingly to the wiki. If you do not have have a Logic2 or KingstVIS based logic analyzer I can tell you in which format you can print out the SPI traffic from your CPU, so I am able to extract the framing messages from it.

Best regards,
lho

[Ivangel1972]

Hej @lho-stx
This will not be a simple and quick action, I have to organize a customer who has and will be willing to provide such a car for further tests.
I remind you additionally that this is another time when you expect from me SPI log in which you find nothing wrong - but ok.
UART log also involves the presence of a car - I will attach as soon as I can.
Regards
Marcin

[lho-stx]

Hey @Ivangel1972,

I am sorry for this situation, but ISO15118 is a complicated protocol. All I can do without any log files is another code review. We can go this route, but please share your configuration used. I'll try to reproduce the problem.

Best regards,
lho

[Ivangel1972]

Hey @lho-stx
He is just working to get everything together logistically. I'll try to do it as soon as possible.
Greetings
Marcin

[fjdicker]

I have exactly the same problem.
When I connect a TESLA Model 3 everything works fine.

[lho-stx]

@fjdicker,
do you have the possibility to create logs of the whitebeet port mirror? This would really help alot!

[fjdicker]

Since I use the SPI Interface that is all what I have.

20240313_MME_SPI_Log.txt
20240313_MME_UART_Log.txt

[fjdicker]

I will try to use a different IPv6 address.
Doing this I found this TYPO.

[fjdicker]

The command 0x43 (Get IPv6 Configuration) works only with Index = 0, otherwise I get 0xFF Module Internal error.
I think there is only one entry in the IPv6 address, the example should be adopted.