ISO 15118

ISO 15118 communication requires the network interface to have an IPv6 link-local address assigned.

• Docker Default: Uses an internal ipv6_net network. This works for isolated testing of EVCC and SECC containers but prevents the host machine from reaching the link-local addresses.
• Host Mode: To allow the host to interact with the link-local addresses (e.g., via HomePlug Green PHY), you must use network_mode: host. This is currently only fully supported on Linux. To use this, copy the contents of docker-compose-host-mode.yml into your main docker-compose.yml file.

To run the project locally, follow these steps:

1. Generate Certificates: Use the create_certs.sh script located in iso15118/shared/pki/ to generate certificates for ISO 15118-2 and 15118-20.
2. Install JRE: If using the Java-based EXI codec (EXIficient), install a JRE (e.g., openjdk-17-jre).
3. Configure Environment: Copy .env.dev.local to .env. Ensure the NETWORK_INTERFACE key matches your actual network interface (default is eth0).
4. Install Dependencies: Use Poetry to manage dependencies.
5. Run Controllers: Use the provided Makefile to start the SECC or EVCC.

$ make install-local
$ make run-secc

Using Docker is the recommended way to start the project as it automatically handles certificate generation, tests, linting, and spawns both the SECC and EVCC containers. When using Docker, make dev automatically uses the .env.dev.docker file, so you do not need to manually create a .env file.

$ make build
$ make dev

A Java Runtime Environment (JRE) is required if using the Java-based EXI codec (EXIficient). On Ubuntu, you can install it via apt. If the default version is outdated, install openjdk-17-jre and use update-alternatives to set it as the default.

# Install default JRE
sudo apt update && sudo apt install -y default-jre

# Install specific version
sudo apt install openjdk-17-jre

# Query installed versions
update-alternatives --query java

# Configure default version
update-alternatives --config java

The ISO15118 deployment consists of the following services:

• secc: The SECC (Supply Equipment Communication Controller) service. It depends on redis and connects to the ipv6_net network.
• evcc: The EVCC (Electric Vehicle Communication Controller) service. It depends on both redis and secc and connects to the ipv6_net network.
• redis: A Redis instance (version 6.2.6-alpine) used for data persistence or messaging. It exposes port 6379 to the host.

The project uses .env files for configuration. For local development, copy .env.dev.local to .env.

Important: You must set the NETWORK_INTERFACE variable in your .env file to match your system's network interface (e.g., eth0, wlan0). The values in .env directly configure secc_settings.py and evcc_settings.py.

The project can be deployed using Docker Compose, which orchestrates three main services: secc, evcc, and redis. The setup uses a custom IPv6 bridge network (ipv6_net) to facilitate communication between services.

To run the stack, ensure you have Docker and Docker Compose installed, then use the standard compose command from the root of the repository.

docker compose up

You can start the SECC using the Makefile or by calling the start script directly via Poetry. The Makefile approach is recommended for convenience.

# Using Makefile
$ make install-local
$ make run-secc

# Using Poetry directly
$ poetry install
$ poetry run python iso15118/secc/start_secc.py

The create_certs.sh script in iso15118/shared/pki/ is used to generate certificates for the different protocol versions. Use the -v flag to specify the version.

$ cd iso15118/shared/pki/
$ ./create_certs.sh -v iso-2
$ ./create_certs.sh -v iso-20

The EVCC can be started via the Makefile. You can pass specific configuration files (found in iso15118/shared/examples/evcc/) as a command-line argument to test different modes like AC, DC, or TLS settings.

# Standard run
$ make install-local
$ make run-evcc

# Run with a specific configuration file
$ make run-evcc config=path_of_config_file