,First time posting here, so we’re not sure if this is under the right topic. We are two electrical engineering students and we’re trying to get an electric car to communicate with/via a charging station in accordance with ISO 15118 as part of an experimental project.
At the moment, however, we are facing a software problem that we have not been able to solve. The problem is that the electric car is sending IPv6 requests that we cannot answer.
The current setup looks like this:
Electric Car <- type 2 adapter -> Charging Controller with Devolo/Codico (QCA7000+LPC1758) module <- Ethernet cable -> <-Ethernet to USB Adapter-> Debian PC <- Ethernet cable -> Router
The Electric Car, Charging Controller and the Debian PC constitute a separate network from the router and Debian PC network
The situation right now:
• Charging control with Devolo/Codico (QCA7000+LPC1758) module, charging via PWM works.
• PLC connection passes everything through, also works with extra DevKit
• PC with USB Ethernet is connected to the charge controller and the ISO15118 Switch-EV implementation is running there (NETWORK_INTERFACE=xxx make run-secc simulation run with make run-evcc working
• PWM is set to 5%
• The car (e-Corsa) now sends Neighbor and Router Solicitation Requests via IPv6
• We can answer the Router Solicitation Requests using the radvd daemon on the PC, but not the Neighbor Solicitation Requests.
• Apart from the neighbor and router solicitation requests, there is currently no other data traffic via PLC.
We are now wondering whether the radvd solution conforms to the standard at all and how we can solve the problem with the neighbor solicitation requests.
