Getting Started

This chapter is intended to help you get started as easily as possible with EV charging together with the Charge SOM Evaluation Kit and the EVerest charging stack. For this purpose, a basic DC charger is set up as an example and explained step by step.

Setting Up the Hardware

Hardware Components

The following hardware components are required to set up the basic DC charger:

  • Charge SOM Evaluation Kit

  • 12 V DC Power Supply

  • Ethernet cable for SSH connection or USB to serial adapter for serial connection

  • DIN70121 or ISO15118-2 EV simulator, for example the Charge Module S Evaluation board

  • Wiring material

Hardware Overview

The following figure shows the basic setup of the DC charger with the Charge SOM Evaluation Kit:

_images/dc_charger_charge_som_setup.svg

Fig. 1: Basic Setup of the DC charger with the Charge SOM

Note

The pin assignment of the Charge SOM Evaluation Kit can be found in the datasheet.

Note

Before you start setting up the hardware, please check whether the HW components used are also listed in Hardware Components section.

First Startup

Boot Process

Here are some key points about the boot process of the Charge controller:

  • The file system basically consists of three ext4 partitions. Two partitions are used as slots for the RAUC update process. The third partition is not touched by the RAUC update process and is usually used for storing update bundles, logs, etc.

  • After connecting the Charge controller to the power supply, the U-Boot bootloader starts the currently active slot managed by RAUC.

  • The LED status indicators on the carrier board provide information about the current status of the boot process.

  • EVerest is automatically started with the default configuration of chargebyte after the boot process is completed. The initial configuration is explained in the Initial Configuration section.

Warning

The journaling file system on the Charge controller does not completely protect against data loss if the power supply is interrupted. So please try to use the Linux commands reboot and halt instead.

Understanding LED Status Indicators

Now you can connect the Charge SOM Evaluation Kit (X24) to the power supply. The LED status indicator on the carrier board provide information about the current status of the boot process. The following table shows the meaning of the LED status indicators:

Table 1: Charge SOM Evaluation Kit LED Status Indicators

State

LED indication

Behavior

Boot process running

LED (red)

periodic blinking for approx. 4 sec.

Operating system running

LED (red)

rhythmic blinking

Connecting via SSH or Serial Interface

For debugging, there are two ways to connect the developer computer to the charge controller: via SSH or via serial interface. The following sections explain how to connect to the charge controller using PuTTY. You can also use other terminal programs (like e.g. MobaXTerm) to connect to the the charge controller.

SSH Connection with PuTTY

Here are the steps to connect to the charge controller via SSH using PuTTY:

  1. Install PuTTY on your computer. You can download PuTTY from the following link: PuTTY Download.

  2. Connect the charge controller over Ethernet to your computer.

  3. Start PuTTY and enter the IPv4 fallback address “169.254.12.53” of the charge controller in the “Host Name (or IP address)” field (See figure PuTTY SSH Configuration).

  4. Click on “Save” to save the configuration and then click on “Open” to start the connection.

  5. A PuTTY Security Alert window will appear. Click on “Accept” to continue.

  6. Enter the username “root” and the password “zebematado” to log in to the charge controller.

Note

The username can also be stored under “Connection -> Data -> Auto-login username” in the PuTTY configuration.

Note

It is also possible to install an SSH key on the charge controller to log in without a password. Please look online for instructions on how to do this on a Linux system.

_images/putty_config_ssh_fallback_ip.png

Fig. 2: PuTTY SSH Configuration

Serial Connection with PuTTY

Here are the steps to connect to the charge controller via serial interface using PuTTY:

  1. Install PuTTY on your computer. You can download PuTTY from the following link: PuTTY Download.

  2. Connect the charge controller to your computer via a USB-to-serial adapter.

  3. Start PuTTY and configure the COM port of the USB-to-serial adapter (e.g. “COM1”) in the “Serial line” field. Note: You can find the COM port of the USB-to-serial adapter in the Windows Device Manager under “Ports (COM & LPT)”.

  4. Switch to Connection -> Serial configuration and set the “Speed” to 115200, “Data bits” to 8, “Stop bits” to 1, “Parity” to “None” and “Flow control” to “None” (See figure PuTTY Serial Configuration).

  5. Switch back to the “Session” and click on “Save” to save the configuration (See figure PuTTY Save Serial Connection).

  6. Click on “Open” to start the connection.

  7. Now a black window will appear. Press enter to get the login prompt.

  8. Enter the username “root” and the password “zebematado” to log in to the charge controller.

_images/putty_config_serial_1.png

Fig. 3: PuTTY Serial Configuration

_images/putty_config_serial_2.png

Fig. 4: PuTTY Save Serial Connection

First Firmware Update

When the charge controller is manufactured, a stable software version is flashed onto it.

However, due to organizational processes and the continuous nature of software development, this version may already be outdated.

We therefore recommend checking first whether a software update for the charge controller is already available for download. If so, it should be installed immediately, as it likely includes bug fixes and possibly new features.

Please look at section Firmware Upgrade for further details, e.g. where to find the firmware update images and how to install them.

Initial Configuration

Now you are connected to the Charge SOM and we can take a deeper look at the initial configuration.

The configuration files of the EVerest charging stack are stored in the directory “/etc/everest”. EVerest uses the YAML format for the configuration files. EVerest runs as a systemd service that by default uses “/etc/everest/config.yaml” as a configuration setup. If you take a look at the content of the configuration file, you will see that it is only a reference to the “bsp-only-dc.yaml” file.

Note

If you create an own configuration file, you can also store it in the “/etc/everest” directory and create a symbolic link to it like “ln -sf /etc/everest/my-config.yaml /etc/everest/config.yaml”. The file where the “config.yaml” symbolic link points to is preserved during the update process.

root@chargesom:/etc/everest# ls -l /etc/everest/
total 28
-rw-r--r-- 1 root root 1134 Jun 20 07:45 bsp-only-dc.yaml
lrwxrwxrwx 1 root root   14 Jun 25 19:26 config.yaml ->  my-config.yaml

Let’s take a look at the content of the bsp-only-dc.yaml configuration file. This file is already prepared for the basic DC charger setup.

Just type “less /etc/everest/bsp-only-dc.yaml” to see the content of the configuration file:

  1#
  2# This is an example configuration for free DC charging
  3#
  4active_modules:
  5  api:
  6    module: API
  7    connections:
  8      evse_manager:
  9        - module_id: connector
 10          implementation_id: evse
 11      error_history:
 12        - module_id: error_history
 13          implementation_id: error_history
 14      evse_energy_sink:
 15        - module_id: grid_connection_point
 16          implementation_id: external_limits
 17  rpc_api:
 18    module: RpcApi
 19    connections:
 20      evse_manager:
 21        - module_id: connector
 22          implementation_id: evse
 23      evse_energy_sink:
 24        - module_id: grid_connection_point
 25          implementation_id: external_limits
 26      charger_information:
 27        - module_id: charger_info
 28          implementation_id: main
 29  charger_info:
 30    module: ChargerInfo
 31    config_module:
 32      firmware_version_file: /usr/share/secc/VERSION
 33    connections:
 34      kvs:
 35        - module_id: kvs
 36          implementation_id: main
 37  kvs:
 38    module: YamlStore
 39    config_module:
 40      file: /etc/everest/charger_info.yaml
 41  bsp:
 42    module: CbChargeSOMDriver
 43  connector:
 44    module: EvseManager
 45    mapping:
 46      module:
 47        evse: 1
 48    config_module:
 49      connector_id: 1
 50      charge_mode: DC
 51      evse_id: DE*CHB*E123456*1
 52      evse_id_din: 49A80737A45678
 53      session_logging: true
 54      session_logging_path: /tmp/everest-logs
 55      session_logging_xml: false
 56    connections:
 57      bsp:
 58        - module_id: bsp
 59          implementation_id: evse_board_support
 60      slac:
 61        - module_id: slac
 62          implementation_id: main
 63      powersupply_DC:
 64        - module_id: powersupply_dc
 65          implementation_id: main
 66      powermeter_car_side:
 67        - module_id: powersupply_dc
 68          implementation_id: powermeter
 69      imd:
 70        - module_id: imd
 71          implementation_id: main
 72      hlc:
 73        - module_id: iso15118_charger
 74          implementation_id: charger
 75  energy_manager:
 76    module: EnergyManager
 77    connections:
 78      energy_trunk:
 79        - module_id: grid_connection_point
 80          implementation_id: energy_grid
 81  grid_connection_point:
 82    module: EnergyNode
 83    mapping:
 84      module:
 85        evse: 1
 86    config_module:
 87      fuse_limit_A: 16
 88      phase_count: 3
 89    connections:
 90      energy_consumer:
 91        - module_id: connector
 92          implementation_id: energy_grid
 93  error_history:
 94    module: ErrorHistory
 95    config_implementation:
 96      error_history:
 97        database_path: /tmp/error_history.db
 98  iso15118_charger:
 99    module: EvseV2G
100    config_module:
101      device: eth1
102    connections:
103      security:
104        - module_id: evse_security
105          implementation_id: main
106  evse_security:
107    module: EvseSecurity
108    config_module:
109      private_key_password: "123456"
110  slac:
111    module: EvseSlac
112    config_implementation:
113      main:
114        device: eth1
115  auth:
116    module: Auth
117    config_module:
118      connection_timeout: 10
119      prioritize_authorization_over_stopping_transaction: true
120      selection_algorithm: PlugEvents
121    connections:
122      token_provider:
123        - module_id: token_provider
124          implementation_id: main
125      token_validator:
126        - module_id: token_validator
127          implementation_id: main
128      evse_manager:
129        - module_id: connector
130          implementation_id: evse
131      kvs:
132        - module_id: persistent_store
133          implementation_id: main
134  persistent_store:
135    module: PersistentStore
136    config_module:
137      sqlite_db_file_path: /var/lib/everest/everest_persistent_store.db
138  powersupply_dc:
139    module: DCSupplySimulator
140  imd:
141    module: IMDSimulator
142  token_provider:
143    module: DummyTokenProvider
144    config_implementation:
145      main:
146        timeout: 10
147        token: DEADBEEF
148        type: RFID
149    connections:
150      evse:
151        - module_id: connector
152          implementation_id: evse
153  token_validator:
154    module: DummyTokenValidator
155    config_implementation:
156      main:
157        sleep: 0.25
158        validation_reason: Token seems valid
159        validation_result: Accepted

In general, the EVerest charging stack consists of different modules, each of which fulfills a specific task. An EVerest module provides and requests interfaces. The configuration file shows which EVerest modules are activated, how they are configured and how they are connected to each other over the interfaces. The following figure illustrates how the EVerest modules are connected to each other:

_images/admin_panel_bsp_only.png

Fig. 5: EVerest admin panel view of the bsp-only-dc.yaml configuration

However, not all configuration parameters of the modules are shown here. Only the configuration parameters that do not match the default configuration of the respective module need to be specified here. Depending on the installed hardware components, the configuration file may need to be adapted. The hardware related tasks are mainly handled by the CbChargeSOMDriver module. The configuration of the CbChargeSOMDriver module can be found in “/usr/libexec/everest/modules/CbChargeSOMDriver” directory.

Each module has a description of all configuration parameter including their defaults. This file is called “manifest.yaml” and is stored in the main directory of the module. In order to see the content of the configuration file you can take a look using “less /usr/libexec/everest/modules/CbChargeSOMDriver/manifest.yaml” to see the content of the manifest file and check whether the configuration fits to your hardware setup.

If you want to change a configuration parameter of a module, which is not part of your EVerest YAML configuration file, just copy the specific configuration key from the “manifest.yaml” file of the module to the module specific “config_module” space in your EVerest configuration and adjust the value. Please note if you change it directly in the “manifest.yaml” file of a module, the changes will be get lost after a software update.

Here is an excerpt of an EVerest configuration to change the parameter “evse_id” to “MY*CUS*T654321*1” of the CbChargeSOMDriver module.

bsp:
  module: CbChargeSOMDriver
connector:
  module: EvseManager
  config_module:
    connector_id: 1
    charge_mode: DC
    evse_id: MY*CUS*T654321*1

After adjusting the configuration file, you have to restart the EVerest charging stack to apply the changes. Just type “systemctl restart everest” to restart the EVerest charging stack.

Note

You can also use the EVerest admin panel to adjust the EVerest configuration in a GUI. This tool must currently be installed manually on your developer computer, because the resources on the board are limited.

Note

If you have made a mistake in the configuration file, the EVerest charging stack will not start. Therefore, it is recommended to back up the original configuration file before making changes.

Starting and Monitoring the Charging Process

Before we start the first charging session, we shall open the EVerest log to monitor the charging process. The EVerest log is stored in the systemd journal and can be accessed via the journalctl command. The journalctl command provides a lot of options to filter the log messages. Now just type “journalctl -f -u everest -n 50” to see the last 50 log messages of the EVerest charging stack and to follow the charging process in real time. For more information about the EVerest log, see the Logging and Debugging chapter.

The EVerest log should look like this:

root@chargesom:~# journalctl -f -u everest -n 100
2026-04-29T14:40:21.595882+0200 csom-carespot2 systemd[1]: Starting EVerest...
2026-04-29T14:40:21.600254+0200 csom-carespot2 sh[140227]: Starting to migrate EVerest configurations
2026-04-29T14:40:21.633827+0200 csom-carespot2 sh[140227]: EVerest configurations migrated successfully
2026-04-29T14:40:21.659046+0200 csom-carespot2 systemd[1]: Started EVerest.
2026-04-29T14:40:21.680731+0200 csom-carespot2 manager[140234]: [INFO] manager          ::   ________      __                _
2026-04-29T14:40:21.680731+0200 csom-carespot2 manager[140234]: [INFO] manager          ::  |  ____\ \    / /               | |
2026-04-29T14:40:21.681770+0200 csom-carespot2 manager[140234]: [INFO] manager          ::  | |__   \ \  / /__ _ __ ___  ___| |_
2026-04-29T14:40:21.681770+0200 csom-carespot2 manager[140234]: [INFO] manager          ::  |  __|   \ \/ / _ \ '__/ _ \/ __| __|
2026-04-29T14:40:21.681770+0200 csom-carespot2 manager[140234]: [INFO] manager          ::  | |____   \  /  __/ | |  __/\__ \ |_
2026-04-29T14:40:21.681770+0200 csom-carespot2 manager[140234]: [INFO] manager          ::  |______|   \/ \___|_|  \___||___/\__|
2026-04-29T14:40:21.681770+0200 csom-carespot2 manager[140234]: [INFO] manager          ::
2026-04-29T14:40:21.681770+0200 csom-carespot2 manager[140234]: [INFO] manager          :: everest-framework 0.25.0 2026.02.0-54-g1b2d3e15-dirty
2026-04-29T14:40:21.681770+0200 csom-carespot2 manager[140234]: [INFO] manager          :: everest-core 2026.02.0 2026.02.0-54-g1b2d3e15-dirty
2026-04-29T14:40:21.681770+0200 csom-carespot2 manager[140234]: [INFO] manager          ::
2026-04-29T14:40:21.681770+0200 csom-carespot2 manager[140234]: [INFO] manager          :: Using MQTT broker localhost:1883
2026-04-29T14:40:21.707310+0200 csom-carespot2 manager[140234]: [INFO] manager          :: Boot mode is set to YamlFile, loading module configs from YAML file
2026-04-29T14:40:21.707616+0200 csom-carespot2 manager[140234]: [INFO] manager          :: Loading config file at: /etc/everest/bsp-only-dc.yaml
2026-04-29T14:40:21.858941+0200 csom-carespot2 manager[140234]: [INFO] manager          :: Config loading completed in 177ms
2026-04-29T14:40:21.862484+0200 csom-carespot2 manager[140234]: [INFO] manager          :: Starting 18 modules
2026-04-29T14:40:23.936040+0200 csom-carespot2 manager[140252]: [INFO] energy_manager:  :: Module energy_manager initialized [1993ms]
2026-04-29T14:40:23.974989+0200 csom-carespot2 manager[140241]: [INFO] api:API          :: Module api initialized [2075ms]
2026-04-29T14:40:24.010143+0200 csom-carespot2 manager[140242]: [INFO] auth:Auth        :: Module auth initialized [2056ms]
2026-04-29T14:40:24.065946+0200 csom-carespot2 manager[140244]: [INFO] charger_info:Ch  :: Module charger_info initialized [2140ms]
2026-04-29T14:40:24.067589+0200 csom-carespot2 manager[140243]: [INFO] bsp:CbChargeSOM  :: chargebyte's Charge SOM EVerest module (version: 0.30.0)
2026-04-29T14:40:24.070179+0200 csom-carespot2 manager[140266]: [INFO] evse_security:E  :: Module evse_security initialized [2078ms]
2026-04-29T14:40:24.137649+0200 csom-carespot2 manager[140329]: [INFO] token_provider:  :: Module token_provider initialized [2002ms]
2026-04-29T14:40:24.153326+0200 csom-carespot2 manager[140246]: [INFO] connector:EvseM  :: Module connector initialized [2151ms]
2026-04-29T14:40:24.166004+0200 csom-carespot2 manager[140281]: [INFO] iso15118_charge  :: Module iso15118_charger initialized [2100ms]
2026-04-29T14:40:24.177408+0200 csom-carespot2 manager[140311]: [INFO] persistent_stor  :: Module persistent_store initialized [2040ms]
2026-04-29T14:40:24.187280+0200 csom-carespot2 manager[140299]: [INFO] kvs:YamlStore    :: Module kvs initialized [2123ms]
2026-04-29T14:40:24.198918+0200 csom-carespot2 manager[140253]: [INFO] error_history:E  :: Resetting database
2026-04-29T14:40:24.200011+0200 csom-carespot2 manager[140279]: [INFO] imd:IMDSimulato  :: Module imd initialized [2194ms]
2026-04-29T14:40:24.209623+0200 csom-carespot2 manager[140314]: [INFO] powersupply_dc:  :: Module powersupply_dc initialized [2115ms]
2026-04-29T14:40:24.225936+0200 csom-carespot2 manager[140253]: [INFO] error_history:E  :: Module error_history initialized [2194ms]
2026-04-29T14:40:24.225936+0200 csom-carespot2 manager[140315]: [INFO] rpc_api:RpcApi   :: libwebsockets version (compiled/runtime): 4.5.2-v4.5.2 / 4.5.2-v4.5.2
2026-04-29T14:40:24.227262+0200 csom-carespot2 manager[140315]: [INFO] rpc_api:RpcApi   :: Module rpc_api initialized [2116ms]
2026-04-29T14:40:24.231938+0200 csom-carespot2 manager[140267]: [INFO] grid_connection  :: Module grid_connection_point initialized [2214ms]
2026-04-29T14:40:24.233024+0200 csom-carespot2 manager[140330]: [INFO] token_validator  :: Module token_validator initialized [2065ms]
2026-04-29T14:40:24.242542+0200 csom-carespot2 manager[140316]: [INFO] slac:EvseSlac    :: Module slac initialized [2086ms]
2026-04-29T14:40:24.407225+0200 csom-carespot2 manager[140243]: [INFO] bsp:CbChargeSOM  :: Safety Controller Firmware: 0.3.0 (g5566522abd7e4adf, Charge SOM, firmware, Parameter Version: 1)
2026-04-29T14:40:24.407635+0200 csom-carespot2 manager[140243]: [INFO] bsp:CbChargeSOM  :: Module bsp initialized [2449ms]
2026-04-29T14:40:24.408544+0200 csom-carespot2 manager[140234]: [INFO] manager          :: Clearing retained topics published by manager during startup
2026-04-29T14:40:24.410540+0200 csom-carespot2 manager[140234]: [INFO] manager          :: 🚙🚙🚙 All modules are initialized. EVerest up and running [2730ms] 🚙🚙🚙
2026-04-29T14:40:24.417279+0200 csom-carespot2 manager[140281]: [INFO] iso15118_charge  :: TCP server on eth1 is listening on port [fe80::201:87ff:fe00:304b%3]:61341
2026-04-29T14:40:24.417585+0200 csom-carespot2 manager[140281]: [INFO] iso15118_charge  :: TLS server on eth1 is listening on port [fe80::201:87ff:fe00:304b%3]:64109
2026-04-29T14:40:24.436633+0200 csom-carespot2 manager[140266]: [INFO] evse_security:E  :: Requesting leaf certificate info: V2G
2026-04-29T14:40:24.439351+0200 csom-carespot2 manager[140316]: [INFO] slac:EvseSlac    :: Starting the SLAC state machine
2026-04-29T14:40:24.458558+0200 csom-carespot2 manager[140266]: [INFO] evse_security:E  :: Found valid leaf: ["/etc/everest/certs/client/cso/CPO_CERT_CHAIN.pem"]
2026-04-29T14:40:24.464410+0200 csom-carespot2 manager[140266]: [INFO] evse_security:E  :: Found valid leaf: ["/etc/everest/certs/client/cso/SECC_LEAF.pem"]
2026-04-29T14:40:24.572833+0200 csom-carespot2 manager[140281]: [INFO] iso15118_charge  :: Ignoring bidirectional SupportedEnergyTransferMode
2026-04-29T14:40:24.641151+0200 csom-carespot2 manager[140316]: [INFO] slac:EvseSlac    :: Entered Reset state
2026-04-29T14:40:24.646217+0200 csom-carespot2 manager[140316]: [INFO] slac:EvseSlac    :: New NMK key: 50:51:49:39:4E:39:32:57:38:58:49:4D:56:51:45:41
2026-04-29T14:40:24.648196+0200 csom-carespot2 manager[140316]: [INFO] slac:EvseSlac    :: Received CM_SET_KEY_CNF
2026-04-29T14:40:24.649441+0200 csom-carespot2 manager[140316]: [INFO] slac:EvseSlac    :: Entered Idle state
2026-04-29T14:40:24.843605+0200 csom-carespot2 manager[140242]: [WARN] auth:Auth        :: Can not load reservations: reservations is not a json array.
2026-04-29T14:40:24.951866+0200 csom-carespot2 manager[140281]: [INFO] iso15118_charge  :: Ignoring bidirectional SupportedEnergyTransferMode
2026-04-29T14:40:24.969158+0200 csom-carespot2 manager[140281]: [WARN] iso15118_charge  :: <n> certificates != <n> OCSP responses
2026-04-29T14:40:24.985033+0200 csom-carespot2 manager[140281]: [INFO] iso15118_charge  :: SDP socket setup succeeded
2026-04-29T14:40:25.311890+0200 csom-carespot2 manager[140315]: [INFO] rpc_api:RpcApi   :: WebSocket Server running on port 8080 (interface "lo" only) without TLS
2026-04-29T14:40:25.579445+0200 csom-carespot2 manager[140246]: [INFO] connector:EvseM  :: Cleaning up any other transaction on start up
2026-04-29T14:40:25.757033+0200 csom-carespot2 manager[140246]: [INFO] connector:EvseM  :: 🌀🌀🌀 Ready to start charging 🌀🌀🌀
2026-04-29T14:40:26.103228+0200 csom-carespot2 manager[140243]: [INFO] bsp:CbChargeSOM  :: handle_enable: Applying cached duty cycle of 100.0%
2026-04-29T14:40:26.226792+0200 csom-carespot2 manager[140243]: [INFO] bsp:CbChargeSOM  :: CP state change from PowerOn to A, PWM: 100.0%
2026-04-29T14:40:26.395336+0200 csom-carespot2 manager[140243]: [INFO] bsp:CbChargeSOM  :: handle_cp_state_X1: Setting new duty cycle of 100.0%
2026-04-29T14:40:26.494984+0200 csom-carespot2 manager[140243]: [INFO] bsp:CbChargeSOM  :: handle_allow_power_on: request to OPEN the contactor (PowerOff)
2026-04-29T14:40:26.539714+0200 csom-carespot2 manager[140243]: [INFO] bsp:CbChargeSOM  :: handle_cp_state_X1: Setting new duty cycle of 100.0%
2026-04-29T14:40:26.547757+0200 csom-carespot2 manager[140246]: [INFO] connector:EvseM  :: All errors cleared
2026-04-29T14:40:26.548075+0200 csom-carespot2 manager[140246]: [INFO] connector:EvseM  :: All errors cleared
2026-04-29T14:40:26.807717+0200 csom-carespot2 manager[140315]: [INFO] rpc_api:RpcApi   :: Client ac8bb36f-5db9-4387-8c40-36d381c9ea68 connected from 127.0.0.1
2026-04-29T14:40:26.808622+0200 csom-carespot2 manager[140315]: [INFO] rpc_api:RpcApi   :: API.Hello request received from client ac8bb36f-5db9-4387-8c40-36d381c9ea68

Before connecting the CP line between Charge SOM Evaluation Kit and the EV simulator, please make sure that the following things are fulfilled:

  • GND from X18 is connected to the EV simulator

  • PP from X18 is not connected to the EV simulator

  • EV simulator is powered up

  • EV simulator must configured to DIN 70121 or ISO 15118-2 DC EIM (No TLS)

After connecting the CP line, a CP state change from “A” to “B” should be visible in the EVerest log. The duty cycle should directly switch from 100% to 5%. The duty cycle change indicates the EVSE is now ready for high level communication.

The EVerest log messages should look like this:

2026-04-29T14:40:30.676991+0200 chargesomCARE03 manager[2710]: [INFO] bsp:CbChargeSOM  :: CP state change from A to B, PWM: 100.0%
2026-04-29T14:40:30.721100+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Entered Matching state, waiting for CM_SLAC_PARM_REQ
2026-04-29T14:40:30.810194+0200 chargesomCARE03 manager[2710]: [INFO] bsp:CbChargeSOM  :: Current (unchanged) state: OPEN
2026-04-29T14:40:30.941735+0200 chargesomCARE03 manager[2712]: [INFO] connector:EvseM  :: SYS  Session logging started.
2026-04-29T14:40:30.942724+0200 chargesomCARE03 manager[2712]: [INFO] connector:EvseM  :: EVSE IEC Session Started: EVConnected
2026-04-29T14:40:30.947959+0200 chargesomCARE03 manager[2709]: [INFO] auth:Auth        :: Plug In event for evse#1, starting auth
2026-04-29T14:40:30.949107+0200 chargesomCARE03 manager[2783]: [INFO] token_provider:  :: Publishing new dummy token: {
2026-04-29T14:40:30.949107+0200 chargesomCARE03 manager[2783]:     "authorization_type": "RFID",
2026-04-29T14:40:30.949107+0200 chargesomCARE03 manager[2783]:     "id_token": {
2026-04-29T14:40:30.949107+0200 chargesomCARE03 manager[2783]:         "type": "ISO14443",
2026-04-29T14:40:30.949107+0200 chargesomCARE03 manager[2783]:         "value": "[redacted] hash: 29F2679CA504908"
2026-04-29T14:40:30.949107+0200 chargesomCARE03 manager[2783]:     },
2026-04-29T14:40:30.949107+0200 chargesomCARE03 manager[2783]:     "parent_id_token": {
2026-04-29T14:40:30.949107+0200 chargesomCARE03 manager[2783]:         "type": "ISO14443",
2026-04-29T14:40:30.949107+0200 chargesomCARE03 manager[2783]:         "value": "[redacted] hash: 29F2679CA504908"
2026-04-29T14:40:30.949107+0200 chargesomCARE03 manager[2783]:     }
2026-04-29T14:40:30.949107+0200 chargesomCARE03 manager[2783]: }
2026-04-29T14:40:30.953621+0200 chargesomCARE03 manager[2709]: [INFO] auth:Auth        :: Received new token: {
2026-04-29T14:40:30.953621+0200 chargesomCARE03 manager[2709]:     "authorization_type": "RFID",
2026-04-29T14:40:30.953621+0200 chargesomCARE03 manager[2709]:     "id_token": {
2026-04-29T14:40:30.953621+0200 chargesomCARE03 manager[2709]:         "type": "ISO14443",
2026-04-29T14:40:30.953621+0200 chargesomCARE03 manager[2709]:         "value": "[redacted] hash: 29F2679CA504908"
2026-04-29T14:40:30.953621+0200 chargesomCARE03 manager[2709]:     },
2026-04-29T14:40:30.953621+0200 chargesomCARE03 manager[2709]:     "parent_id_token": {
2026-04-29T14:40:30.953621+0200 chargesomCARE03 manager[2709]:         "type": "ISO14443",
2026-04-29T14:40:30.953621+0200 chargesomCARE03 manager[2709]:         "value": "[redacted] hash: 29F2679CA504908"
2026-04-29T14:40:30.953621+0200 chargesomCARE03 manager[2709]:     }
2026-04-29T14:40:30.953621+0200 chargesomCARE03 manager[2709]: }
2026-04-29T14:40:30.959095+0200 chargesomCARE03 manager[2796]: [INFO] token_validator  :: Got validation request for token: [redacted] hash: 29F2679CA504908
2026-04-29T14:40:31.209485+0200 chargesomCARE03 manager[2796]: [INFO] token_validator  :: Returning validation status: Accepted
2026-04-29T14:40:31.213119+0200 chargesomCARE03 manager[2709]: [INFO] auth:Auth        :: Providing authorization to evse#1
2026-04-29T14:40:31.442613+0200 chargesomCARE03 manager[2712]: [INFO] connector:EvseM  :: EVSE IEC Set PWM On (5.0%) took 0 ms
2026-04-29T14:40:31.444344+0200 chargesomCARE03 manager[2710]: [INFO] bsp:CbChargeSOM  :: handle_pwm_on: Setting new duty cycle of 5.0%
2026-04-29T14:40:31.596684+0200 chargesomCARE03 manager[2709]: [INFO] auth:Auth        :: Result for token: [redacted] hash: 29F2679CA504908: ACCEPTED
2026-04-29T14:40:31.648990+0200 chargesomCARE03 manager[2712]: [INFO] connector:EvseM  :: EVSE IEC EIM Authorization received
2026-04-29T14:40:31.711864+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): initialized, waiting for CM_START_ATTEN_CHAR_IND
2026-04-29T14:40:31.737341+0200 chargesomCARE03 manager[2712]: [INFO] connector:EvseM  :: EVSE IEC Transaction Started (0 kWh)
2026-04-29T14:40:31.737972+0200 chargesomCARE03 manager[2712]: [INFO] connector:EvseM  :: EVSE IEC DC mode. We are in 5percent mode so we can continue without further action.
2026-04-29T14:40:31.738394+0200 chargesomCARE03 manager[2712]: [INFO] connector:EvseM  :: EVSE IEC Charger state: Wait for Auth->PrepareCharging

After that, the EV simulator should establish a powerline connection to the Charge SOM via SLAC.

2026-04-29T14:40:31.951845+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): received CM_START_ATTEN_CHAR_IND, going to substate SOUNDING
2026-04-29T14:40:31.971833+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): needs to be in state WAIT_FOR_START_ATTEN_CHAR for CM_START_ATTEN_CHAR_IND
2026-04-29T14:40:31.991809+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): needs to be in state WAIT_FOR_START_ATTEN_CHAR for CM_START_ATTEN_CHAR_IND
2026-04-29T14:40:32.014530+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): received CM_MNBC_SOUND_IND
2026-04-29T14:40:32.022430+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): received CM_ATTEN_PROFILE_IND
2026-04-29T14:40:32.031792+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): received CM_MNBC_SOUND_IND
2026-04-29T14:40:32.040271+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): received CM_ATTEN_PROFILE_IND
2026-04-29T14:40:32.051785+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): received CM_MNBC_SOUND_IND
2026-04-29T14:40:32.059660+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): received CM_ATTEN_PROFILE_IND
2026-04-29T14:40:32.071801+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): received CM_MNBC_SOUND_IND
2026-04-29T14:40:32.080279+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): received CM_ATTEN_PROFILE_IND
2026-04-29T14:40:32.091866+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): received CM_MNBC_SOUND_IND
2026-04-29T14:40:32.099780+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): received CM_ATTEN_PROFILE_IND
2026-04-29T14:40:32.111745+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): received CM_MNBC_SOUND_IND
2026-04-29T14:40:32.119798+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): received CM_ATTEN_PROFILE_IND
2026-04-29T14:40:32.131953+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): received CM_MNBC_SOUND_IND
2026-04-29T14:40:32.139962+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): received CM_ATTEN_PROFILE_IND
2026-04-29T14:40:32.152298+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): received CM_MNBC_SOUND_IND
2026-04-29T14:40:32.160310+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): received CM_ATTEN_PROFILE_IND
2026-04-29T14:40:32.174327+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): received CM_MNBC_SOUND_IND
2026-04-29T14:40:32.181827+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): received CM_ATTEN_PROFILE_IND
2026-04-29T14:40:32.192459+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): received CM_MNBC_SOUND_IND
2026-04-29T14:40:32.199916+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): received CM_ATTEN_PROFILE_IND
2026-04-29T14:40:32.200284+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): received all sounds, going to substate FINALIZE_SOUNDING
2026-04-29T14:40:32.244308+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): Finalize sounding, sending CM_ATTEN_CHAR_IND
2026-04-29T14:40:32.273559+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): received CM_ATTEN_CHAR_RSP, going to substate WAIT_FOR_SLAC_MATCH
2026-04-29T14:40:33.171940+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Session (run_id=662841C53AD4145D, ev_mac=00:01:87:0F:97:8B): Received CM_SLAC_MATCH_REQ, sending CM_SLAC_MATCH_CNF -> session complete
2026-04-29T14:40:33.173389+0200 chargesomCARE03 manager[2732]: [INFO] evse_slac:EvseS  :: Entered Matched state
2026-04-29T14:40:33.176961+0200 chargesomCARE03 manager[2712]: [INFO] connector:EvseM  :: EVSE ISO SLAC MATCHED
2026-04-29T14:40:33.216906+0200 chargesomCARE03 manager[2712]: [INFO] connector:EvseM  :: EVSE ISO D-LINK_READY (true)

Now the EV simulator discovers the V2G service of the Charge SOM and establishes a TCP connection. Both hosts negotiate the protocol ISO 15118-2 and start a charging session. Since the setup lacks some components of a real DC charger (e.g. HV contactors, power modules) only the state ChargeParameterDiscovery will be reached.

2026-04-29T14:40:35.662140+0200 chargesomCARE03 manager[2750]: [INFO] iso15118_charge  :: Received packet from [fe80::201:87ff:fe0f:978b]:58650 with security 0x10 and protocol 0x00
2026-04-29T14:40:35.662140+0200 chargesomCARE03 manager[2750]: [INFO] iso15118_charge  :: SDP requested NO-TLS, announcing NO-TLS
2026-04-29T14:40:35.662140+0200 chargesomCARE03 manager[2750]: [INFO] iso15118_charge  :: sendto([fe80::201:87ff:fe0f:978b]:58650) succeeded
2026-04-29T14:40:35.678618+0200 chargesomCARE03 manager[2750]: [INFO] iso15118_charge  :: Incoming connection on eth1 from [a00:c000:0:0:fe80::]:49152
2026-04-29T14:40:35.679087+0200 chargesomCARE03 manager[2750]: [INFO] iso15118_charge  :: Started new TCP connection thread
2026-04-29T14:40:35.679390+0200 chargesomCARE03 manager[2750]: [INFO] iso15118_charge  :: Handling SupportedAppProtocolReq
2026-04-29T14:40:35.679839+0200 chargesomCARE03 manager[2750]: [INFO] iso15118_charge  :: Protocol negotiation was successful. Selected protocol is ISO15118
2026-04-29T14:40:35.682040+0200 chargesomCARE03 manager[2712]: [INFO] connector:EvseM  ::                                     CAR ISO V2G SupportedAppProtocolReq
2026-04-29T14:40:35.720169+0200 chargesomCARE03 manager[2750]: [INFO] iso15118_charge  :: SessionSetupReq.EVCCID: 00:01:87:0F:97:8B
2026-04-29T14:40:35.720169+0200 chargesomCARE03 manager[2750]: [INFO] iso15118_charge  :: No session_id found or not equal to the id from the preceding v2g session. Generating random session id.
2026-04-29T14:40:35.720169+0200 chargesomCARE03 manager[2750]: [INFO] iso15118_charge  :: Created new session with id 0x9079111121431940848
2026-04-29T14:40:35.725579+0200 chargesomCARE03 manager[2712]: [INFO] connector:EvseM  :: EVSE ISO V2G SupportedAppProtocolRes
2026-04-29T14:40:35.770725+0200 chargesomCARE03 manager[2712]: [INFO] connector:EvseM  ::                                     CAR ISO V2G SessionSetupReq
2026-04-29T14:40:35.856733+0200 chargesomCARE03 manager[2712]: [INFO] connector:EvseM  :: EVSE ISO V2G SessionSetupRes
2026-04-29T14:40:35.915128+0200 chargesomCARE03 manager[2750]: [WARN] iso15118_charge  :: PnC is not allowed without TLS-communication. Correcting value to '1' (ExternalPayment)
2026-04-29T14:40:35.917660+0200 chargesomCARE03 manager[2712]: [INFO] connector:EvseM  ::                                     CAR ISO V2G ServiceDiscoveryReq
2026-04-29T14:40:36.052925+0200 chargesomCARE03 manager[2712]: [INFO] connector:EvseM  :: EVSE ISO V2G ServiceDiscoveryRes
2026-04-29T14:40:36.121459+0200 chargesomCARE03 manager[2750]: [INFO] iso15118_charge  :: SelectedPaymentOption: ExternalPayment
2026-04-29T14:40:36.145121+0200 chargesomCARE03 manager[2712]: [INFO] connector:EvseM  ::                                     CAR ISO V2G PaymentServiceSelectionReq
2026-04-29T14:40:36.220660+0200 chargesomCARE03 manager[2712]: [INFO] connector:EvseM  :: EVSE ISO V2G PaymentServiceSelectionRes
2026-04-29T14:40:36.373414+0200 chargesomCARE03 manager[2712]: [INFO] connector:EvseM  ::                                     CAR ISO V2G AuthorizationReq
2026-04-29T14:40:36.425496+0200 chargesomCARE03 manager[2712]: [INFO] connector:EvseM  :: EVSE ISO V2G AuthorizationRes
2026-04-29T14:40:36.533923+0200 chargesomCARE03 manager[2712]: [INFO] connector:EvseM  ::                                     CAR ISO V2G AuthorizationReq
2026-04-29T14:40:36.633361+0200 chargesomCARE03 manager[2712]: [INFO] connector:EvseM  :: EVSE ISO V2G AuthorizationRes
2026-04-29T14:40:36.737969+0200 chargesomCARE03 manager[2750]: [INFO] iso15118_charge  :: Parameter-phase started
2026-04-29T14:40:36.737969+0200 chargesomCARE03 manager[2750]: [INFO] iso15118_charge  :: Selected energy transfer mode: DC_extended
2026-04-29T14:40:36.765666+0200 chargesomCARE03 manager[2712]: [INFO] connector:EvseM  :: Received EV maximum limits: {
2026-04-29T14:40:36.765666+0200 chargesomCARE03 manager[2712]:     "dc_ev_maximum_current_limit": 5.0,
2026-04-29T14:40:36.765666+0200 chargesomCARE03 manager[2712]:     "dc_ev_maximum_power_limit": 1100.0,
2026-04-29T14:40:36.765666+0200 chargesomCARE03 manager[2712]:     "dc_ev_maximum_voltage_limit": 228.0
2026-04-29T14:40:36.765666+0200 chargesomCARE03 manager[2712]: }
2026-04-29T14:40:36.765666+0200 chargesomCARE03 manager[2712]: [INFO] connector:EvseM  ::                                     CAR ISO V2G ChargeParameterDiscoveryReq
2026-04-29T14:40:36.835806+0200 chargesomCARE03 manager[2712]: [INFO] connector:EvseM  :: EVSE ISO V2G ChargeParameterDiscoveryRes

Congratulations! You have successfully established a charging session with the EVerest charging stack and the Charge SOM. Now you are prepared to start your own charging project and adjust your setup to your needs. The following chapters will help you understand the EVerest charging stack and Charge SOM in more detail and gain deeper insight into the configuration.