Add extracted tools: CitrineOS, OpenOCPP, ShapeShifter
- CitrineOS core extracted (CSMS OCPP 2.0.1) - OpenOCPP extracted (firmware OCPP 1.6J/2.0.1) - ShapeShifter library installed (pip install -e) - ShapeShifter specification extracted - EVerest extracted TODO updated with progress
This commit is contained in:
Eric F
130
tools/EVerest-main/docs/source/tutorials/plug-and-charge.rst
Normal file
130
tools/EVerest-main/docs/source/tutorials/plug-and-charge.rst
Normal file
@@ -0,0 +1,130 @@
|
||||
.. _tutorial_plug_and_charge:
|
||||
|
||||
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:
|
||||
|
||||
Prerequisites
|
||||
-------------
|
||||
|
||||
If you're new to EVerest, start with our
|
||||
`Quick Start Guide <02_quick_start_guide.html>`_ 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
|
||||
:doc:`Plug&Charge explanations </explanation/pnc-process>`
|
||||
and the :doc:`Plug&Charge Configuration Howto </how-to-guides/configure-pnc>`
|
||||
|
||||
Packages for ISO 15118 communication
|
||||
------------------------------------
|
||||
|
||||
To be able to build EVerest with ISO 15118 capability, you will have to
|
||||
install the requirements for Josev:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
cd {EVerest Workspace Directory}/Josev
|
||||
python3 -m pip install -r requirements.txt
|
||||
|
||||
For ISO 15118 communication including Plug&Charge, install Josev and some CA
|
||||
certificates:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
cd {EVerest Workspace Directory}/Josev/iso15118/shared/pki
|
||||
./create_certs.sh -v iso-2 -i {EVerest Workspace Directory}/EVerest
|
||||
|
||||
This will enable ISO 15118 communication including Plug&Charge and install the
|
||||
required CA certificates inside ``config/certs/ca`` and the client certificates,
|
||||
private keys and password files inside ``config/certs/client``.
|
||||
|
||||
.. attention::
|
||||
|
||||
This will generate an example PKI setup that can only be used for testing
|
||||
and simulation. It will not work and is not recommended for production.
|
||||
|
||||
As the shell script uses the Java ``keytool``, it is required for this
|
||||
procedure to have Java installed.
|
||||
|
||||
The script for setting up PKI can also be used with the EvseV2G module.
|
||||
|
||||
.. _plug_and_charge_process:
|
||||
|
||||
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.
|
||||
By default, this includes a complete and automatic installation of a test PKI.
|
||||
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).
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
./run-scripts/run-sil-ocpp201-pnc.sh
|
||||
|
||||
or
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
./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
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
2025-10-17 17:21:47.039511 [WARN] iso15118_car pybind11_init_everestpy(pybind11::module_&)::<lambda(const std::string&)> :: A TimeoutError occurred. Waited for Timeouts.SDP_REQ s after sending an SDPRequest
|
||||
|
||||
you may need to adjust your firewall settings to allow communication between
|
||||
the EVCC and SECC modules.
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
sudo ip6tables -I INPUT -i <your_network_interface_name> -p udp --dport 15118 -j ACCEPT
|
||||
|
||||
|
||||
----
|
||||
|
||||
**Authors**: Piet Gömpel
|
||||
Reference in New Issue
Block a user