Scandinavian
Well-Known Member
- First Name
- Peter
- Joined
- Nov 3, 2019
- Threads
- 47
- Messages
- 3,087
- Reaction score
- 2,690
- Location
- France
- Vehicles
- Taycan T, Tesla M3P, Aston Martin DB9, Porsche 996 C4 Cab
I am in Europe so I guess I will not have that J1772 protocol. ISO yes!J1772 defines a rudimentary communication protocol. The EVSE communicates the charging current it is able to supply by modifying the pulse width on a 1 KHz pilot signal. The vehicle communicates back one of 5 states by changing the resistance on this pilot signal. The EVSE can sense that resistance by measuring the voltage drop. Those states include connected/idle (waiting), charging, charging complete, and error.
J1772 does not provide any way for the vehicle to communicate a VIN or even a manufacturer to the EVSE. So anyone who has seen the PMCC report their VIN has some other communication going on.
ISO15118 defines data exchange that rides on top of some of these signals (I don't know the technical details how but it might work very similar to PLC). Theoretically any data could be exchanged. Maybe ISO15118 is just the protocol but PLC is the physical connection...? There is plenty of data to suggest the car supports ISO15118.
IIRC, the PMCC allows you to use PLC between the PMCC and a home PLC network (that would include the PEM but doesn't have to), and use the PMCC as a WiFi hotspot. Maybe the car would recognize the PMCC's WiFi hotspot - but I've never tried this. You can't enable the PMCC's WiFi hotspot while using WiFi to connect the PMC to your home network.
My query is more based on two new pages for the charger after the update. There it seems it can identify VIN and other details in future? See photos. I have not seen these pages in the web interface earlier?