From 98c569597be5e998e394d1657e5c40b600455174 Mon Sep 17 00:00:00 2001 From: uhi22 Date: Wed, 19 Oct 2022 19:31:21 +0200 Subject: [PATCH] added status --- readme.md | 71 ++++++++++++++++++++++++++++++++++++------------------- 1 file changed, 47 insertions(+), 24 deletions(-) diff --git a/readme.md b/readme.md index 9e9020d..9c96c6e 100644 --- a/readme.md +++ b/readme.md @@ -3,6 +3,11 @@ ## Goal This project tries to use cheap powerline network adaptors for communication with electric cars charging system. +There are three different use cases, where this project can be helpful: +1. Sniffing the traffic between an CCS charger and a car. For instance to measure which side is the limiting element for reduced charging power. +2. Building a charger for CCS or for AC with digital communication. +3. Building a charging unit for a car which does not support powerline communication. + ## References [i] https://www.goingelectric.de/wiki/CCS-Technische-Details/ [ii] https://openinverter.org/forum/viewtopic.php?p=37085#p37085 @@ -32,29 +37,29 @@ It is worth to read its documentation, starting in docbook/index.html, this cont (Tested on Linux/Raspbian on a raspberryPi 3) Find the PLC adaptor -pi@RPi3D:~ $ int6klist -ieth0 -v + pi@RPi3D:~ $ int6klist -ieth0 -v This shows the software version and the mac address. Read the configuration from the PLC adaptor and write it to a file -pi@RPi3D:~ $ plctool -ieth0 -p original.pib 98:48:27:5A:3C:E6 -eth0 98:48:27:5A:3C:E6 Read Module from Memory + pi@RPi3D:~ $ plctool -ieth0 -p original.pib 98:48:27:5A:3C:E6 + eth0 98:48:27:5A:3C:E6 Read Module from Memory Patch the configuration file (aee /docbook/ch05s15.html). For each side (pev (vehicle) and evse (charger)) there is a special configuration. Example pev side: -pi@RPi3D:~ $ cp original.pib pev.pib -pi@RPi3D:~ $ setpib pev.pib 74 hfid "PEV" -pi@RPi3D:~ $ setpib pev.pib F4 byte 1 -pi@RPi3D:~ $ setpib pev.pib 1653 byte 1 -pi@RPi3D:~ $ setpib pev.pib 1C98 long 10240 long 102400 + pi@RPi3D:~ $ cp original.pib pev.pib + pi@RPi3D:~ $ setpib pev.pib 74 hfid "PEV" + pi@RPi3D:~ $ setpib pev.pib F4 byte 1 + pi@RPi3D:~ $ setpib pev.pib 1653 byte 1 + pi@RPi3D:~ $ setpib pev.pib 1C98 long 10240 long 102400 Write the configuration file to the PLC adaptor -pi@RPi3D:~ $ plctool -ieth0 -P pev.pib 98:48:27:5A:3C:E6 -eth0 98:48:27:5A:3C:E6 Start Module Write Session -eth0 98:48:27:5A:3C:E6 Flash pev.pib -... -eth0 98:48:27:5A:3C:E6 Close Session -eth0 98:48:27:5A:3C:E6 Reset Device -eth0 98:48:27:5A:3C:E6 Resetting ... + pi@RPi3D:~ $ plctool -ieth0 -P pev.pib 98:48:27:5A:3C:E6 + eth0 98:48:27:5A:3C:E6 Start Module Write Session + eth0 98:48:27:5A:3C:E6 Flash pev.pib + ... + eth0 98:48:27:5A:3C:E6 Close Session + eth0 98:48:27:5A:3C:E6 Reset Device + eth0 98:48:27:5A:3C:E6 Resetting ... The open-plc-utils contain the programs evse and pev, which can be used for try-out of the functionality, using two PLC adaptors. @@ -70,21 +75,39 @@ Attention: There are (at least) three different python-libs available for pcap: - Pypcap (recommented on https://stackoverflow.com/questions/63941109/pcap-open-live-issue) - Pcap-ct (https://pypi.org/project/pcap-ct/) We use the last one. -python -m pip install --upgrade pcap-ct + python -m pip install --upgrade pcap-ct This is fighting against the Libpcap-installation, so we need to deinstall the second: -python -m pip uninstall libpcap + python -m pip uninstall libpcap Then again install pcap-ct, and finally add in the libpcap\_platform\__init__py the missing is_osx = False. (Is in the meanwhile fixed in the github repository.) +Finally, we need to patch the Pcap-ct, because the python script needs a non-blocking version. This is discussed in https://github.com/karpierz/pcap-ct/issues/9 + Now, in the IDLE shall 3.10.6, the import works: -import pcap -sniffer = pcap.pcap(name=None, promisc=True, immediate=True, timeout_ms=50) -addr = lambda pkt, offset: '.'.join(str(pkt[i]) for i in range(offset, offset + 4)) -for ts, pkt in sniffer: - print('%d\tSRC %-16s\tDST %-16s' % (ts, addr(pkt, sniffer.dloff + 12), addr(pkt, sniffer.dloff + 16))) + import pcap + sniffer = pcap.pcap(name=None, promisc=True, immediate=True, timeout_ms=50) + addr = lambda pkt, offset: '.'.join(str(pkt[i]) for i in range(offset, offset + 4)) + for ts, pkt in sniffer: + print('%d\tSRC %-16s\tDST %-16s' % (ts, addr(pkt, sniffer.dloff + 12), addr(pkt, sniffer.dloff + 16))) ### Usage on Raspberry Pcap-ct does not work with Python 3.4. After update to Python 3.8, it works. -## Further steps -(to be continued) +## Change history / functional status +### 2022-10-19 Communication with Ioniq car established +* Using a TPlink TL-PA4010P with firmware MAC-QCA7420-1.4.0.20-00-20171027-CS and the PIB configuration file patched for evse according to the open-plc-utils docu. +* Python software running on Win10, Python 3.10.8 +* On control pilot, sending 5% PWM to initiate digital communication with the car +* Since the TPlink is configured as coordinator, it sends "alive" messages, and the IONIQ starts sending the SLAC_PARAM.REQ. +* Per keystroke, we trigger a SET_KEY before the car is connected. The TPlink responds with "rejected", but this is normal, the LEDs are turning off and on, key is accepted. +* Python script interprets the relevant incoming messages (SLAC_PARAM.REQ, MNBC_SOUND.IND, SLAC_MATCH.REQ) and reacts accordingly. +* After successfull SLAC sequence, all three LEDs on the TPlink are ON, means: Network is established. +* In wireshark, we see that the car is sending UDP multicast messages to destination port 15118. This looks like a good sign, that it wants a ISO15118 compatible communication. +### 2022-10-19 Sniffing mode not yet working with the TPlink adaptors +* with a Devolo dLAN 200 AVplus, software INT6000-MAC-4-4-4405-00-4497-20101201-FINAL-B in original parametrization, it is possible +to see the complete SLAC traffic (both directions) which sniffing the communication between a real charger and a real car. This does +NOT work with the TPlink adaptors. They route only "their own" direction of the traffic to the ethernet. Means: The pev-configured device +does not see the real car, and the evse-configured device does not see the real charger. This is bad for sniffing. + + +(further steps ongoing)