ECClite Ecotap Controller Configuration Lite Edition User Guide
- September 8, 2024
- ecotap
Table of Contents
ECClite Ecotap Controller Configuration Lite Edition
“`html
Product Information
Specifications
- Product Name: ECClite
- Description: Ecotap Controller Configuration Lite Edition
- Version: 1.4, 15-07-2024 [internal & external usage]
- Platform Compatibility: Windows
- Controller Firmware Requirement: Version V32RXX and up
Product Usage Instructions
Introduction
ECClite is a software application dedicated to owners,
installers, and operators of charging stations. It allows for
remote configuration of Ecotap charging stations through backend
platforms compatible with OCPP.
Setup Requirements
Required Hardware
- Computer with at least 1x USB connection (type A)
- USB to TTL cable
- Ecotap controller (EVC4.x / EVC5.x / ECC.x)
- 12V DC power supply
Required Software
No specific software requirements mentioned in the manual.
Downloading and Installation
To download the latest version of ECClite and the user manual,
visit Ecotap’s official
website.
Updating Firmware
Warning: Firmware updates are critical and
should be done with caution. Always follow the manufacturer’s
instructions to prevent any damage to the controller module.
If you are unsure about updating the firmware, consult
Ecotap/Legrand for guidance.
FAQ
Q: Can ECClite be used on platforms other than Windows?
A: No, ECClite works only on the Windows platform.
Q: Can I downgrade the firmware after updating?
A: No, it is not possible to downgrade the firmware once
updated. Proceed with firmware updates carefully.
“`
ECClite
Ecotap Controller Configuration Lite Edition
Version 1.4, 15-07-2024 [internal & external usage] 1
1. Version History
Version 1.0 1.1 1.2 1.3 1.4 1.5
Date 21-03-2024 16-04-2024 1-05-2024 23-05-2024 15-7-2024 17-7-2024
Author Product Owner (R&D) Product Owner (R&D) Product Owner (R&D) Product Owner (R&D) Product Owner (R&D) Product Owner (R&D)
History of changes:
· Version 1.0: o Creation o Chapters 5 to 10 are based on content in the
original ECC Manager manual, adapted and made relevant to ECClite.
· Version 1.1: o Add three table references, out of Jack de Veer’s full EVC4
and EVC5 R&D Manuals to the JSON Parameters.
· Version 1.2: o Additional Parameters mentioned in OCPP Dictionary.
· Version 1.3: o Small corrections & Added table 7.
· Version 1.4: o Added note about OCPPInfo field.
· Version 1.5: o Removed content from the Chapter OCPP Connectivity and
referred to separate OCPP Connection Configuration.PDF, for more elaborate
OCPP Connectivity information.
2
2. Table of Contents Inhoud
1. Version History …………………………………………………………………………………………………………………………….. 2 2.
Table of Contents………………………………………………………………………………………………………………………….. 3 3.
Introduction…………………………………………………………………………………………………………………………………. 4 4. Primary
information – Ecotap Controller Configuration Lite Edition
………………………………………………….. 5
Generic information about Updating your Firmware:
…………………………………………………………………………… 5 OCPP Connectivity
:………………………………………………………………………………………………………………………….. 6 5. Required Setup
…………………………………………………………………………………………………………………………….. 7 5.1. Required Hardware
……………………………………………………………………………………………………………….. 7 5.2. Required
Software…………………………………………………………………………………………………………………. 7 5.3. Required Files
……………………………………………………………………………………………………………………….. 7 6. Preparing The Setup
……………………………………………………………………………………………………………………… 8 7. Establish Communication
with the Module. …………………………………………………………………………………… 11 8. Firmware
Update………………………………………………………………………………………………………………………… 15 9. Load and Send
Configuration to the Module. …………………………………………………………………………………. 18 10.
Troubleshooting ……………………………………………………………………………………………………………………… 21 10.1.
‘Windows protected your PC’ message. ………………………………………………………………………………….. 21 11.
JSON Configuration Dictionary ………………………………………………………………………………………………….. 22
3
3. Introduction
This document serves as a guide for updating firmware and modifying
configuration via the ECClite. With the lite version you can configure
settings regarding; Power, Loadmanagement/Grid and internet connectivity. The
lite version also protects you from changing any configuration on the station
that could permanently damage it. If you still use the full ECC Manager
instead of the lite version, you will do that at your own risk of voiding
warranty. Using ECClite is described step by step and can be applied to the
EVC4.x, EVC5.x and the ECC.x controller that run the V32Rx software. The
following topics are addressed in this manual:
· Required hardware, software and related files. · Updating Firmware via the
ECClite · Sending selected parameters to the controller.
Important!
A) Standard Factory settings .JSON files with selected parameters should
always be supplied by Ecotap!
B) If the ECClite software is used in a way other than indicated in the
manual, Ecotap cannot guarantee that the controller will work properly.
4
4. Primary information- Ecotap Controller Configuration Lite Edition
ECClite is an application dedicated for owners, installers and operators of
charging stations. Everything that can be done on this software tool, must in
principle be done via remote commands from your selected backend. As the
Ecotap stations are made for convenient remote control, in batch by using OCPP
compatible backend platforms. That is especially the case for all parameters
needed to determine the power and grid settings that match your charging
infrastructure.
In most cases Ecotap manufacturing will have preset all communication data as
such the station will automatically make connection to the backend determined
in the purchasing process. If you need to check, correct or modify the backend
connectivity, or if you can’t access the backend to configure power and grid
settings. You will need to use ECClite.
This software toolkit works only on the windows platform and only if the
firmware on supported controllers is on version V32RXX and up.
To download the latest version & the manual, click here:
https://www.ecotap.nl/ecclite/
Generic information about Updating your Firmware:
To update the firmware, you will need the manufacturer advised .BIN file. You
can find the latest published firmware and their release notes on the web
page: https://www.ecotap.nl/ecclite/ Mind that you should always check the
release notes to evaluate if that firmware file is compatible to your type of
controller module. An update of the firmware of your station is best done
remotely and in batch by the charge point operator via his OCPP-backend
access. In cases you need to do it manually, you can use this software toolkit
`ECClite’.
WARNING: a firmware update is different from commonly known software updates.
If you update the firmware in technical terms, you flash the chip memory. That
means that it completely rewrites itself. If you interrupt this process by
removing power or data cable. Your controller module can brick itself. And
become useless. You lose your warranty and need to swap the controller module.
If you don’t know what you are doing, always first consult the manufacturer
Ecotap/Legrand.
Unlike with OTA (over-the-air) software updates. With firmware, you as owner
of the device decide whether or not you want to update your device to the
manufacturer advised version.
If you have a stable version running on your charger, it is not advised to
update. Only update if you read in the release notes that the update solves a
problem hampers your charger operations. MIND that IT IS NOT possible to
DOWNGRADE the firmware anymore. Project specific firmware on custom product
should thus NEVER be upgraded!
5
OCPP Connectivity :
Because Ecotap Charging Stations are infrastructure objects, the OCPP
connectivity to the selected backend platform is pre-configured in the
factory. If connectivity is lost or connectivity settings are accidentally
wiped and/or contracts with the backend provider are terminated and a switch
to a new party is needed. You will need to reconfigure connectivity yourself.
To connect an OCPP backend platform, you will need receive information from
the platform provider. Namely, the link to the backend. Called an Endpoint. In
most cases it will look like this: Endpoint URL:
“wss://devices.ecotap.com/registry/ocpp/NLECO1000” For detailed information
about how to configure this endpoint on the Ecotap Controller, we refer to a
separate PDF named: OCPP Connection Configuration.PDF. That you can download
from: https://www.ecotap.nl/en/ecclite-ecotap-controller-configuration/ Under
the button:
6
5. Required Setup
In order to use ECClite and its functionalities, there are several supplies
that are required. Make sure these are present before proceeding.
5.1. Required Hardware
Product
Computer (incl. 1x USB connection, type A) USB to TTL cable
Ecotap controller (EVC4.x / EVC5.x / ECC.x) 12V DC power supply
5.2. Required Software
Info
To use the ECClite software tool.
Cable to connect the controller with the computer (cable is proprietary to
Ecotap). Article number: 3510019 Supplied by Ecotap. The controller inside the
charging station to be programmed / configured.
Properly working power supply to power on the controller module inside the
charging station.
Name
ECClite
Version
1.0.0 or later
5.3.
Required Files
Info
Software for programming and changing configurations on the EVC4.x / EVC5.x /
ECC.x controllers that at least have the V32 Firmware.
This can be downloaded from the Ecotap Website: https://www.ecotap.nl/ecclite/
Name
Factory standard “.Json” file. (optional)
Version
Unique per charger model
Notes
A file containing all (correct) standard settings for selected parameters.
To fall back on if you want to go back to factory settings.
This should be requested from Ecotap. Depending on the model of
7
station you are using.
“.bin” file (optional)
V32RXX or later
A file containing the (new) firmware. Required for updating firmware.
This should be requested from Ecotap.
Only the latest releases can be downloaded from the website:
https://www.ecotap.nl/ecclite/
Older version / `Legacy firmwares’, can be requested at your technical
advisors at Ecotap.
6. Preparing The Setup
The first step is to unzip the ECClite.EXE, to a folder on your PC or to a USB
Stick.
Download the ECClite.zip file and save it to your computer. When doing so,
choose a location that is easy to find on your PC.
Figure 5.1 – ECCmanager.zip file.
(The zip-file icon may look different) Right-click on the file and select
Extract All. An additional screen will now open, click extract again. In the
same location as the .zip file, there will now be a folder created with the
same name.
Figure 5.2 – ECCmanager folder after unzipping zip file.
Open this folder and then double-click ECClite.exe to open the application. 8
Figure 5.3 – ECClite application.
ECClite will now start up and is ready to use. As you can notice there is no
installer needed. This software toolkit works as a pocket `lite’ version.
Note: when opening the application, it could occur that Microsoft Defender
prevents the starting of it. If this is the case, see Chapter 9 on how to
solve this easily.
Do not power on the module yet, during the following steps!
Connect the USB to TTL cable with the controller. Attach the USB side of the
cable to one of the computer’s USB ports. At the other end of the cable,
attach the green connector (to which the black, orange and yellow wires are
connected) directly to the module. When doing so, make sure the connector is
attached to the pins of the RFID2 reader, see the sticker with I/O layout on
the controller:
9
For the EVC4.x controller:
Figure 5.4 – Connecting the USB to TTL cable to the controller (EVC 4.x).
For the EVC5.x/ECC.x controller:
Figure 5.5 – Connecting the USB to TTL cable to the controller (EVC 5.x).
10
7. Establish Communication with the Module.
Before changing the configuration, find out which COM port is used for serial
communication. If the USB is not already connected to the computer and/or to
the controller, do so first (see chapter 5). Once the USB to TTL cable is
connected to the computer, use the following key combination on the keyboard:
- X This will reveal the following screen.
Figure 6.1 – Pop-up window after clicking [Windows + X] key combination.
Next, click on Device Manager. Look for the Ports (COM & LPT) heading and ‘double-click’ on it (or once on the arrow to the left of the name).
The visual representation of the menu’s depends on the operating system that is used, and therefore can differ.
11
Figure 6.2 – Device manager overview
Figure 6.3 – Display active ports on the PC.
In case more than one “USB Serial Port (COMx)” are displayed, you can check
which port is used for the controller. Simply disconnect the USB to TTL cable
from your PC, and reconnect it: the COM port that disappears and appears again
is the correct one.
12
In the example above, only one USB to TTL cable has been connected to the
computer. So here, the COM port we are looking for is COM8. Note that the COM
port may vary depending on the following (so always check the COM port first):
· The USB to TTL cable (with controller) is connected to another computer. · A
different USB to TTL cable is used. Open ECClite.
Figure 6.4 – ECClite.
Enter the COM number, which we looked up earlier, in the field next to USB
port. So, in the case of this example, we enter 10 here.
Figure 6.5 – Entering the correct COM port.
13
Now click on the Connect button at the bottom right of the ECC Manager, and
then make sure the checkmark for Debug is checked (at the bottom left of the
ECC Manager).
Figure 6.6 – Connect to the controller & check debug.
Connect the 12V+ pin of the controller, to the 12V+ of the DC power supply.
Connect the “DC power GND pin” on the controller to the ground of the DC power
supply. Next, power on the controller. After a couple of seconds, logging will
appear in the lower display of the ECClite (lines of blue text).
Figure 6.7 Communication with the controller on similar software ECCManager
(heavy version).
If you don’t see blue text, remove power from the module, wait 10 seconds, and
turn the power back on. Now the blue text should still become visible.
14
8. Firmware Update
This section describes how to update the controller’s firmware via ECClite.
It is important that, during the update process, the USB to TTL cable remains
connected to the PC and/or controller and that the controller is continuously
powered-on (provided by the 12V DC supply)!
Pre-requisites: A. Download the “.bin” file and save it to an easily
retrievable place on the PC. B. Make sure there is communication with the
module, see chapter 6 (blue log text).
Only continue when the pre-requisites are met. 1. Open ECClite Click the
“Update” tab and then “Open Firmware file”.
Figure 7.1 – Open firmware file (picture is from the heavy program but looks
the same on the portable version `ECClite’).
2. Look-up the .bin file and open it. 3. Check that the software version name
matches the name of the .bin file, as now
displayed in ECClite (see image below). In this example, the module will be
updated to the V32R16 firmware.
15
Figure 7.2 – Check the name of the opened bin file.
4. Click on “Program firmware”. Now software info (in green) will appear in
the logging. Also, a progress bar at the bottom of ECClite will start running.
This indicates how far the update has progressed. Wait for it to fill up.
Figure 7.3 – Firmware update in progress.
When the progress bar is completed, green text is displayed again followed by
a piece of red text. This is internal info of the module, characterized by
copy flash’ and
erase’ remarks in the logging.
16
Figure 7.4 – Firmware update is complete.
5. Verify the controller’s firmware version. It can be found in the
application’s startup information (blue text), after about 20 lines. See image
below (based on an EVC 4.31 controller).
Figure 7.5 – Check that the controller boots with the correct firmware.
During boot of the application, the V32R16 is shown in the logging; it has
been successfully installed.
It is important that, during the update process, the USB to TTL cable remains
connected to the PC and/or controller and that the controller is continuously
powered-on (provided by the 12V DC supply).
17
9. Load and Send Configuration to the Module.
A configuration that is incorrect or incorrectly set, can permanently damage
the controller and Ecotap cannot be held responsible for this. When in doubt,
always contact Ecotap up front.
Download the factory standard .json file provided by Ecotap, for the exact
station model you have at hand. Save it somewhere on the PC, where the file
can be found easily. As an example in this manual, we will use “test.json”.
Again, only use the factory standard .json file provided by Ecotap
specifically for that station model!
Figure 8.1 – .json file (provided by Ecotap)
(The icon of the .json file may look different) In ECClite, go to the Settings
tab, and then click the button.
Figure 8.2 – Loading the configuration.
Now the explorer will open. On your PC, search for the location where the
.json file was placed earlier. Next, click on the file and click Open.
18
Figure 8.3 – Loading the .json file.
It will show a selection of parameters that Ecotap has specified for you
within the Json file. For these selected configuration keys, you can adjust
the values. Below an example is given with dummy values.
Figure 8.4 – Entering parameter values
Adjust the values of these parameters, if applicable. When in doubt, always
contact Ecotap! When the values are entered correctly, click the Select All
button. This selects the parameters, identified by the checked box to the left
of the parameter names.
19
Then click the Send selected button, which sends these parameters with their
values to the module.
Figure 8.6 – Sending parameters to controller.
Now check the logging again, for the specific code line “SV CFG()”. This
indicates that the configuration change has successfully been accepted.
Figure 8.7 SV CFG(): message to verify the configuration changes.
Next, to validate if the configuration has changed. Reboot the controller.
Wait a couple of seconds, then proceed to Select all, again and Receive
config.
If the parameters are set correctly, the correct values will be read out of
the controller module.
Under chapter 11 you will find a dictionary of parameters available for you to
modify based on your chargers differing installation situations. Any other
parameters that need to be changed should be done remotely from the connected
OCPP Back-Office platform.
20
10. Troubleshooting
Should any problems arise while following the manual, a possible solution to
fix the problem can be found in this section.
10.1. ‘Windows protected your PC’ message.
It is possible that you might end up with this screen when trying to open
ECClite software. This is a message from Microsoft Defender to protect your
computer from malicious software. In this case the software is not malicious
but unknown to Microsoft Defender. To go further with this, click on More
info.
Figure 7.1 – Microsoft Defender window.
This will show you more info about the application that you want to run.
Because we know this software is not malicious you can click on the Run anyway
button. After this, the application will start as expected.
21
11. JSON Configuration Dictionary
ECClite supports JSON Get and Set configuration. The configuration items
consist of OCPP parameters and Ecotap proprietary parameters and can be set
via OCPP (Open Charge Point Protocol). The OCPP parameters can be found in the
appropriate OCPP standard. Below you will find Ecotap’s implementation of
these parameters.
Mind that in the input value of these parameters, if you have a comma ” , “.
That means that after that comma will be the next input value. So, with the
chg_RatedCurrent = [16,16]. That means left channel is on 16 amps and the
right channel is on 16 amps as well. Keep that in mind.
Parameters under
in ECCLite, can and must only be changed by the CPO via
it’s connected Backend Platform / Central System!
Configuration Key authorizationKey
R/W WO
Description Here the authorization for a secure WebSocket must be entered. The key can only be written to and cannot be read out for security reasons. The option `useTLS’ must be set to use the key.
The firmware uses Basic Authentication for HTTPS connections and hence the key must be entered as follows:
Format:
Username as known by the Central System Password as known by the Central System
chg_Debug
Example Authorization Key: ECOTAP-1802500:9N8gGyS8Un7g4lY9dRICK RW Set debug logging options. (CSL) See Table 1: Debug options and levels for the allowed options and their levels.
The value of an option must be entered as a bitmask where each bit represents
a debug level. The following levels are implemented:
0 = Off 1 = Level 1 2 = Level 2 4 = Level 3 8 = Level 4 16 = Level 5
To enable multiple levels add them together e.g.: to enable Level 1 and Level 3 enter the value 5 = 1 +4
chg_KWH1 chg_KWH2 chg_KWH3
Example of a debug configuration:
warn=1,error=1,date=1,syslog=0,gsm=1,events=1,com=0,ocpp=0,eth=0,grid=0,ctrl=3,general=3,
sensors=0,fw=0,modbus=0,canbus=0,sys=0 Energy meter configuration for channel
1, channel 2 and the utility meter (KWH3)
Format:
Energy meter type & brand
(Only the meters compatible to the applied Ecotap Firmware version)
Modbus address in case of a Modbus meter Modbus meter: Baudrate Pulse meter:
Number of pulses per kWh (N)one, (E)ven, (O)dd (Only for Modbus meters) 1 or 2
(Only for Modbus meters)
chg_Reader1 chg_Reader2
Example for utility meter: EASTR_SDM72D,3,9600,N,1 RW Token Reader type (CSL) The ECC supports one reader per channel and each reader can be set to support channel 1, channel 2 or any of those channels. When set to any, the ECC will check which channel gets a valid PP or CP signal and then assigns the token reader to that channel. Hence only one reader is needed..
Format:
22
chg_MinChargingCurrent chg_RatedCurrent chg_StationMaxCurrent chg_Ch1Options
chg_Ch2Options
com_Options com_Endpoint
com_OCPPID com_OCPPInfo com_ProtCh
Reader type See Table 5: Supported Token Reader Channel. Set to either CH1 or CH2 or any
Example for a charger with two readers: chg_Reader1: sl032,CH1 chg_Reader2: sl032,CH2
Example for a charger with a shared reader:
chg_Reader1: sl032,any
chg_Reader2: none,CH2
RW
The minimal current allowed to charge an EV. (CSL)
Value is the current per phase for all phases in amps. Range = 0…63
Example for a standard charger : 6 RW The rated current for a channel (CSL) This is the rated current of the channel in amps as determined by the wiring and other hardware of the charger and will normally be the same as the MCD for this channel. The current delivered to the EV will never be higher than this value.
Example for a standard charger: 16,16 RW The maximum current that a charger may consume in total per phase for all phases in amps. The value of this setting may not exceed the maximum current allowed by the wiring of the charger model. However, when the connection to the utility grid has a fuse with a smaller rating, the value of this rating must be used. This often happens for public chargers which can carry up to 32A but are fused with 25A.
Example for a public charger fused with 25A: 25 RW Charger options for a channel. (CSL) See Table 6: Charger Channel Options for the allowed options.
0 = Option disabled, 1 = Option enabled.
Example: PlugAndCharge=0,OvercurrentSens=0,StopOnChargeComplete=0, OfflineStopOnDisconnect=0, StopOnLowCosphi=0, Rel2OnLowCosphi=0 RW Communication Options (CSL) See Table 7: Communication options for all allowed options. 0 = Option disabled, 1 = Option enabled
Example for a standard charger: Events=1,BlockBeforeBoot=1,Wdt=0,updSendInIdle=0,blockLgFull=0,useTLS=0,comMaster=0 RW Endpoint for the central system
In the definition of the endpoint the user may define two variables:
SN
Replaced by the serial number of the controller module
OSN
Replaced by the OCPP ID of the controller module
Example: ws.evc.net:80/#SN# RW OCPP Identification ID (Maximum length = 25 characters)
When the ID is changed the charger will restart after 60 seconds.
Example: EcotapTestID RW Other info needed for the OCPP Protocol (CSL) See Table 3: Additional OCPP vendor information for the allowed fields.
Example: modelname=ECC-AC,vendorname=Ecotap,CpSn=G48229*1 RW Communication channel for the Central System
Example for a standard charger, connection via the modem: GSM Example for a standard charger where Ethernet interface is used: ETH
23
com_ProtType eth_cfg
grid_InstallationMaxcurrent grid_InstallationSaveCurrent grid_Role gsm_APN
gsm_Oper gsm_Options
RW Communication protocol for the Central System See Table 2: Supported communication
Example for a standard charger: OCPP1.6J
RW Ethernet Interface configuration (CSL)
Format: type=
IP address type Enter static’ or
dhcp’ IPV4 address of the EVC4 IPV4 netmask
IPV4 address of the domain name server IPV4 address of the gateway
Example: Type=dhcp,ip=0.0.0.0,netmask=0.0.0.0,dns=0.0.0.0,gw=0.0.0.0 RW The maximum current allowed for a master/slave grid (per phase for all phases) in amps. Range 0…9999 This option must be set on a master to the value for that master/slave grid. This option must be set on a supervisor to the current available for all grids.
Example: 250 RW The maximum current allowed for a master/slave grid (per phase for all phases) in amps when the master loses communication with the supervisor. Range 0…9999 Must be set on a master and is only used there..
Example: 100 RW Operation mode in a local power grid See Table 4: Grid roles for the allowed roles.
Example for a standard charger: Station_ctrl RW GSM APN Information
Format:
The name is limited to 39 characters while the user and password are limited to 24 characters.
Example for a standard charger: m2mservices,, RW GSM Preferred Operator for the mobile network
Set to 0 (default) if automatic selection is preferred otherwise it should be formatted as LLLXX, where LLL is the country code and XX is the provider code. For the Netherlands possible values are 20404 (Vodafone NL), 20408 (KPN NL), 20416 9T-Mobile NL)
Example for a standard charger: 0 RW GSM options (CSL) 0 = Disabled, 1 = Enabled
The following options are allowed:
Option noSmsChk
AutoAPN 3G4G
Description If enabled allows all originating numbers to send SMS commands If disabled only the number set in parameter `gsm_SMS’ may send SMS commands. Only present to prevent errors with older configurations. Now obsolete. Only present to prevent errors with older configurations. Now obsolete.
gsm_SigQ
Example for standard grid: noSmsChk=0,AutoAPN=0,3G4G=0 RO GSM signal quality(0..99). Must be greater than 8 to have a valid GSM connection. A value of 99 means that no strength could be determined.
24
Example for a standard charger: 15
Chg_Debug Levels :
Option warn error date syslog gsm events com ocpp eth grid ctrl general sensors fw modbus canbus sys
Levels 1 1 1 1 1…3 1…4 1…4 1…3 1…3 1…4 1…3 1…2 1…2 1…2 1…2 1…3 1…3
Com_ProtType :
Description Show warnings. Default set to level 1 Show errors. Default set to
level 1 Show data and time before each line. Log syslog entries Log mobile
communication Log event system info Log communication info Log OCPP info Log
ethernet info Log power grid info Log charger control Log general events Log
sensors Log firmware update info Log Modbus info Log CAN-bus info Log sys info
Table 1: Debug options and levels
Option LMS OCPP1.5J OCPP1.6J Clear
Com_OCPPInfo :
Description Proprietary LMS protocol. (Deprecated. Only still used for
Master/Slave grids) OCPP Versie 1.5 JSON. (Deprecated) OCPP Versie 1.6 JSON.
Clear all events in the event buffer without changing the current protocol.
Used to clear old events before switching to a new protocol to prevent
protocol errors on the Central System. Recommended to use when switching from
LMS to OCPP and vice versa.
Table 2: Supported communication protocols.
Option modelname vendorname CpSn
Grid_Role :
Description Charge point model name Charge point vendor name Charge point
serial number
Table 3: Additional OCPP vendor information
Maximum Length 25 characters 25 characters 25 characters
Option No_ctrl Station_ctrl
Slave
Master
Description
The controller module disables the internal power manager The controller
module uses the internal power manager for the station only. The configuration
key chg_StationMaxCurrent’ will be used to limit the maximum power The controller module will function as a slave that will connect to a master/supervisor. The configuration key
chg_StationMaxCurrent’ will be used
to limit the maximum power The controller module uses the internal power
manager for control of the power on the master and the connected slaves. The
configuration key `grid_InstallationMaxcurrent’ defines the total current for
this master/slave grid
Table 4: Grid roles
25
Chg_Reader :
Option none sl032 Shared
Chg_ChOptions :
Option PlugAndCharge OvercurrentSens StopOnChargeComplete
OffLineStopOnDisconnect StopOnLowCosphi Rel2OnLowCosPhi
Option Events BlockBeforeBoot Wdt
updSendInIdle blockLgFull UseTLS comMaster
Description No reader connected SL032/SL031 reader or twn4 reader emulating a
sl032 reader Shared reader Only used for split systems.
Table 5: Supported Token Reader types.
Description Enable Plug & Charge Enable over-current sensing Stops the
transaction when the EV stops charging If the connection with the central
system is lost, stop the transaction as soon as the cable is disconnected from
the EV Stop charging when the cosine goes low (<0.7) Switch from relay 1 to
relay 2 output when the cosine goes low (<0.7)
Table 6: Charger Channel Options
Description Enable status updates (events) to be send to the Central System
Block the charger until the boot notification message has been sent Enable
Master/Slave communication watchdog. Only supported by Slaves in a
Master/Slave Grid. Should be disabled otherwise. Send meter value updates when
the charger is idle Block the charger when the Transaction Event Log is full
Secured web socket connection with the Central System using TLS Set this
module to be the master and actively put all connected ECCs to slave mode.
This option is obsolete and is only present to prevent errors with older
configurations.
Table 7: Communication options
26
References
Read User Manual Online (PDF format)
Read User Manual Online (PDF format) >>