You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For Autocharge it is possible to extract the PLC unique MAC Address from the EV, which is useful for Autocharge use case
Menno's answer:
Hi @André Duarte as mentioned during the meeting, below is the info I added to our ticket to retrieve the EV PLC node MAC address. I will also add a Wireshark trace.
Quote from ticket:
Even though the EV PLC node MAC address is not present in the high-level communication, there is a method to retrieve it. This is only possible though after SLAC matching has succeeded, because it uses specific messages defined in the HomePlug standard to retrieve the network configuration.
In open-plc-utils (the QCA reference implementation) there are two commands:
which both reveal that 02:26:00:00:00:22 is the EV PLC node MAC address.
The underlying HomePlug message that can be used to retrieve the logical network information is NW_INFO.REQ. If the EVSECC sends that request to the generic HomePlug destination MAC 00:b0:52:00:00:01, the EVSE PLC node will return the network information with connected stations, including the MAC address.
Clearly, this only works after the logical network is formed, so SLAC must complete first.
AB#1525 AB#1526
For Autocharge it is possible to extract the PLC unique MAC Address from the EV, which is useful for Autocharge use case
Menno's answer:
which both reveal that 02:26:00:00:00:22 is the EV PLC node MAC address.
The underlying HomePlug message that can be used to retrieve the logical network information is NW_INFO.REQ. If the EVSECC sends that request to the generic HomePlug destination MAC 00:b0:52:00:00:01, the EVSE PLC node will return the network information with connected stations, including the MAC address.
Clearly, this only works after the logical network is formed, so SLAC must complete first.
Verisco_network_info.pcapng.txt
The text was updated successfully, but these errors were encountered: