Plug&Charge with EVerest Software in the Loop

EVerest provides support for Plug&Charge within ISO15118-2 and OCPP1.6 and OCPP2.0.1. This tutorial explains how you can set up and configure EVerest for Plug&Charge with the software in the loop.

Prerequisites

If you’re new to EVerest, start with our Quick Start Guide to get a simulation in EVerest running for the first time. If you have done that successfully, you can move on with this tutorial.

If you are interested in more in-depth information about how Plug&Charge is implemented in EVerest, please refer to the Plug&Charge explanations and the Plug&Charge Configuration Howto

Certificates for ISO 15118 communication

The EVerest install ships a test PKI under etc/everest/certs of the install prefix (sources in config/certs): CA certificates in certs/ca and client certificates, private keys and password files in certs/client. The EV simulation (Ev15118) and the charger (EvseV2G, Evse15118D20) use it, so no extra setup is needed for Plug&Charge in the software in the loop.

CMake generates this PKI at configure time when all of these hold:

  • ISO15118_2_GENERATE_AND_INSTALL_CERTIFICATES is ON, the default;

  • edm is enabled; packaging builds with DISABLE_EDM=ON, such as Yocto, get no development keys;

  • at least one of Ev15118, EvseV2G and Evse15118D20 is built.

Configure fails if the generation fails, and says why when it skips it.

To check that an install holds every file the TLS and Plug&Charge configurations load, run tests/dev_pki/test_installed_dev_pki.sh <prefix> after cmake --install. It is a manual check and not part of any test suite.

Attention

This PKI can only be used for testing and simulation. It will not work and is not recommended for production.

The Plug&Charge process

The process we are going to simulate covers a complete AC Plug&Charge process including a CertificateInstallation request to install a virtual contract in the simulated EV.

The components included in this setup are the following:

  1. Charging Station (SECC): The EVerest stack provides the software running on the charger. It provides the ISO 15118 and OCPP implementations.

  2. Electric Vehicle (EVCC): The EV is simulated using the software in the loop (SIL). The SIL runs as part of EVerest using separate modules that are started alongside with the EVerest application.

  3. Charging Station Management System (CSMS): The CSMS used in this setup is an external service. It’s a very simple implementation of an OCPP central system based on the Python ocpp package from TheMobilityHouse (https://github.com/mobilityhouse/ocpp).

Let’s get started step by step

  1. Prerequisites must be fullfilled: EVerest must be installed on your system. A default build includes a complete and automatic installation of a test PKI, under the conditions listed in Certificates for ISO 15118 communication. The certificates and keys are located under dist/etc/everest/certs.

  2. Let’s prepare the central system that we are going to use. Follow the instructions described here to set it up: https://github.com/EVerest/ocpp-csms

  3. Run EVerest with either OCPP1.6, OCPP2.x using the prepared run-scripts. Make sure the the endpoint localhost:9000/<id> is specified in the respective ocpp configuration file (OCPP2.x config defaults to this address, while for OCPP1.6 the default is different). The recommended OCPPmulti module covers OCPP 1.6 and OCPP 2.x; see the combined module tutorial for setup and enabling Plug&Charge.

./run-scripts/run-sil-ocpp201-pnc.sh

or

./run-scripts/run-sil-ocpp-pnc.sh

Make sure Node-RED is running and access the UI on localhost:1880/ui.

In Node-RED select AC ISO 15118-2 from the Car Simulation dropdown and click “Car Plugin”. This will initiate the EV plugin and start the Plug&Charge process.

Check the EVerest console and OCPP logs. By default OCPP logs are located in /tmp/everest_ocpp_logs .

Troubleshooting

If you observe logging messages indicating a timeout of the SDP request like

[WARN] iso15118_car    EV Controller: SDP discovery / connect did not complete in time

you may need to adjust your firewall settings to allow communication between the EVCC and SECC modules.

sudo ip6tables -I INPUT  -i <your_network_interface_name> -p udp --dport 15118 -j ACCEPT

Authors: Piet Gömpel