How ecog-io/iso15118 works
• The EVCC (Electric Vehicle Communication Controller) – implemented under the iso15118/evcc directory.
• The SECC (Supply Equipment Communication Controller) – implemented under the iso15118/secc directory.
There is also a large “shared” library (under iso15118/shared) that includes common functionalities such as messaging (protocol definitions, schemas, state machines), certificate management (PKI files, certificate generation scripts), logging, and utilities. This clearly indicates that the project is structured to handle two interacting controllers that simulate or drive real-world ISO 15118 communications.
Key components
a. EVCC Component:
• Configuration interaction via settings (evcc_settings.py, evcc_config.py) and different state implementations (DINSPEC, ISO15118-2, ISO15118-20, SAP states).
b. SECC Component:
c. Shared Library:
d. External Environment:
• Docker and Deployment: Represent Docker containers (Docker Compose setups like docker-compose.yml, docker-compose-dev.yml, docker-compose-prod.yml, and the host-mode configuration) that orchestrate the running of both EVCC and SECC.
• Environment Variables & Configuration Files: Show the role of several .env files (for Docker and local development) and the Makefile that ties together build, installation, and launch commands.
e. Testing and CI/CD:
Relationships and data flow
• Both controllers to the shared library to denote the usage of common message encoding/decoding, data types, and protocol definitions.
• From an infrastructure perspective, show that both EVCC and SECC are deployed in containerized environments. Optionally indicate that containers can run in “host mode” on Linux to properly handle the IPv6 link-local addresses required by ISO 15118.
• That configuration and certificate management modules affect both controllers (using environment settings and the PKI directory).
Architectural patterns and design principles
• Separation of concerns: Notice the distinct roles of EVCC, SECC, and shared libraries.
• Modularity / extensibility: The use of individual directories for different protocol states and the component separation for message schemas indicate a plug-in style design.
• Communication Over Sockets: TCP/UDP clients and servers are used to emulate or run the ISO 15118 communication flow.
• Container-based deployment: Using Docker-compose for both development and production environments.
• Use of environment variable based configuration which tailors the behavior of the controllers (as seen with the various ENV files).