ECClite Ecotap Controller Configuration Lite Edition
Version 1.4, 15-07-2024
[Internal & External Usage]
1. Version History
| Version | Date | Author |
|---|---|---|
| 1.0 | 21-03-2024 | Product Owner (R&D) |
| 1.1 | 16-04-2024 | Product Owner (R&D) |
| 1.2 | 1-05-2024 | Product Owner (R&D) |
| 1.3 | 23-05-2024 | Product Owner (R&D) |
| 1.4 | 15-7-2024 | Product Owner (R&D) |
| 1.5 | 17-7-2024 | Product Owner (R&D) |
History of changes:
- Version 1.0: Creation. Chapters 5 to 10 are based on content in the original ECC Manager manual, adapted and made relevant to ECClite.
- Version 1.1: Added three table references from Jack de Veer's full EVC4 and EVC5 R&D Manuals to the JSON Parameters.
- Version 1.2: Additional Parameters mentioned in OCPP Dictionary.
- Version 1.3: Small corrections & Added table 7.
- Version 1.4: Added note about OCPPInfo field.
- Version 1.5: Removed content from the Chapter OCPP Connectivity and referred to a separate PDF (OCPP Connection Configuration.PDF) for more elaborate OCPP Connectivity information.
3. Introduction
This document serves as a guide for updating firmware and modifying configuration via ECClite.
The lite version allows configuration of settings regarding Power, Load-management/Grid, and internet connectivity. It also protects against permanent damage to the station by preventing changes to critical configurations. Using the full ECC Manager instead of the lite version is at the user's own risk of voiding warranty.
ECClite is described step-by-step and can be applied to EVC4.x, EVC5.x, and ECC.x controllers running V32Rx software.
Topics covered in this manual:
- Required hardware, software, and related files.
- Updating Firmware via ECClite.
- Sending selected parameters to the controller.
Important!
- A) Standard Factory settings .JSON files with selected parameters must always be supplied by Ecotap!
- B) If ECClite software is used in a way not indicated in the manual, Ecotap cannot guarantee proper controller functionality.
4. Primary Information - Ecotap Controller Configuration – Lite Edition
ECClite is an application for owners, installers, and operators of charging stations. Configuration is primarily done via remote commands from a selected backend, leveraging OCPP compatible backend platforms for convenient remote control and setting power and grid parameters matching the charging infrastructure.
Ecotap stations typically have preset communication data for automatic connection to the backend. ECClite is used to check, correct, or modify backend connectivity, or to configure power and grid settings when backend access is unavailable.
This software toolkit operates on Windows and requires firmware on supported controllers to be version V32RXX or later.
Download the latest version and manual: https://www.ecotap.nl/ecclite/
Generic Information about Updating your Firmware:
To update firmware, a manufacturer-advised ".BIN" file is required. The latest firmware and release notes are available on the web page: https://www.ecotap.nl/ecclite/. Always check release notes for compatibility with your controller module.
Firmware updates are best performed remotely and in batch by the charge point operator via their OCPP-backend access. Manual updates can be done using ECClite.
WARNING: Firmware updates involve flashing the chip memory. Interrupting this process (e.g., by removing power or data cable) can brick the controller, void the warranty, and require module replacement. Consult Ecotap/Legrand before proceeding if unsure.
Unlike OTA updates, firmware updates are user-initiated. It is not advised to update if a stable version is running, unless the update resolves an issue affecting charger operations. Firmware cannot be downgraded. Project-specific firmware on custom products should never be upgraded.
OCPP Connectivity:
Ecotap Charging Stations are pre-configured for OCPP connectivity to the selected backend platform. If connectivity is lost, settings are wiped, or contracts terminate, reconfiguring connectivity is necessary. This requires an "Endpoint" (link to the backend) from the platform provider.
Endpoint URL example: "wss://devices.ecotap.com/registry/ocpp/NL*ECO*1000"
For detailed endpoint configuration, refer to the PDF "OCPP Connection Configuration.PDF", downloadable from: https://www.ecotap.nl/en/ecclite-ecotap-controller-configuration/
5. Required Setup
To use ECClite and its functionalities, ensure the following supplies are present:
5.1. Required Hardware
| Product | Info |
|---|---|
| Computer (incl. 1x USB connection, type A) | To use the ECClite software tool. |
| USB to TTL cable | Cable to connect the controller with the computer (proprietary to Ecotap). Article number: 3510019. Supplied by Ecotap. |
| Ecotap controller (EVC4.x / EVC5.x / ECC.x) | The controller inside the charging station to be programmed / configured. |
| 12V DC power supply | Properly working power supply to power on the controller module inside the charging station. |
5.2. Required Software
| Name | Version | Info |
|---|---|---|
| ECClite | 1.0.0 or later | Software for programming and changing configurations on EVC4.x / EVC5.x / ECC.x controllers with V32 Firmware. Downloadable from the Ecotap Website: https://www.ecotap.nl/ecclite/ |
5.3. Required Files
| Name | Version | Notes |
|---|---|---|
| Factory standard ".Json" file (optional) | Unique per charger model | A file containing all correct standard settings for selected parameters. Used to revert to factory settings. Request from Ecotap. |
| ".bin" file (optional) | V32RXX or later | A file containing the new firmware, required for updating. Request from Ecotap. Latest releases from https://www.ecotap.nl/ecclite/. Older versions/legacy firmwares can be requested from Ecotap technical advisors. |
6. Preparing The Setup
First, unzip the ECClite.EXE to a folder on your PC or a USB Stick. Download the ECClite.zip file and save it to an easily accessible location on your PC.
[Description of Figure 5.1: Image shows a file icon labeled 'ECCMANA GER.zip', representing the compressed software package.]
Right-click the file and select "Extract All". Click "Extract" again in the subsequent screen. A folder named "ECCmanager" will be created in the same location as the .zip file.
[Description of Figure 5.2: Image shows a folder icon labeled 'ECCMANA GER', representing the extracted contents of the zip file.]
Open this folder and double-click ECClite.exe to launch the application.
[Description of Figure 5.3: Image shows an application icon for ECClite, possibly with the ECClite logo or name.]
ECClite starts up ready for use. It is a 'lite' version with no installer needed.
Note: Microsoft Defender might prevent the application from starting. Refer to Chapter 9 for solutions.
Do not power on the module yet during the following steps!
Connect the USB to TTL cable to the controller. Attach the USB end to a computer USB port. Connect the green connector (with black, orange, and yellow wires) to the module's RFID2 reader pins, referencing the I/O layout sticker on the controller.
[Description of Figure 5.4: Image shows the USB to TTL cable connection to an EVC4.x controller, highlighting pin connections.]
[Description of Figure 5.5: Image shows the USB to TTL cable connection to an EVC5.x/ECC.x controller, highlighting pin connections.]
7. Establish Communication with the Module
Before configuration changes, identify the COM port used for serial communication. Ensure the USB is connected to the computer and controller (see Chapter 5).
With the USB to TTL cable connected, press Windows key + X on the keyboard to open a context menu.
[Description of Figure 6.1: Image displays a Windows context menu that appears after pressing Windows key + X, with 'Device Manager' highlighted.]
Click on "Device Manager". Locate and double-click the "Ports (COM & LPT)" heading.
[Note: The visual representation of menus may vary depending on the operating system.]
[Description of Figure 6.2: Image shows the Device Manager window with various hardware categories listed, including 'Ports (COM & LPT)'.]
[Description of Figure 6.3: Image shows the 'Ports (COM & LPT)' section expanded in Device Manager, listing 'USB Serial Port (COM8)' as an example.]
If multiple "USB Serial Port (COMx)" entries appear, disconnect and reconnect the USB to TTL cable. The COM port that disappears and reappears is the correct one.
In the example, only one USB to TTL cable is connected, showing COM8. The COM port may vary.
Open ECClite.
[Description of Figure 6.4: Image displays the ECClite software interface with fields for 'USB Port' and a 'Connect' button.]
Enter the identified COM number (e.g., 10 in the example) into the "USB Port" field.
[Description of Figure 6.5: Image shows the ECClite interface with the 'USB Port' field populated with a COM number (e.g., '10').]
Click the "Connect" button and ensure "Debug" is checked.
[Description of Figure 6.6: Image shows the ECClite interface with the 'Connect' button and the 'Debug' checkbox highlighted.]
Connect the controller's 12V+ pin to the 12V+ DC power supply and the "DC power GND pin" to the power supply's ground. Then, power on the controller.
After a few seconds, logging information (blue text) will appear in the ECClite display.
[Description of Figure 6.7: Image displays a software log window showing lines of blue text, indicating communication with the controller.]
If no blue text appears, remove power, wait 10 seconds, and power on again.
8. Firmware Update
This section details how to update the controller's firmware using ECClite.
Important: During the update process, the USB to TTL cable must remain connected, and the controller must be continuously powered by the 12V DC supply.
Pre-requisites:
- A. Download the ".bin" file and save it to an easily accessible location on the PC.
- B. Ensure communication with the module is established (see Chapter 6 for blue log text).
Proceed only when pre-requisites are met.
- Open ECClite, click the "Update" tab, then "Open Firmware file".
- Locate and open the ".bin" file.
- Verify that the software version name displayed in ECClite matches the ".bin" file name. The example shows an update to V32R16 firmware.
[Description of Figure 7.1: Image shows the ECClite interface with the 'Update' tab selected and the 'Open Firmware file' button.]
[Description of Figure 7.2: Image shows the ECClite interface displaying the path to the selected firmware '.bin' file.]
- Click "Program firmware". Software information (green text) will appear in the logging, and a progress bar will indicate the update status. Wait for it to complete.
[Description of Figure 7.3: Image shows the ECClite interface during firmware update, featuring a progress bar and logging information.]
Upon completion, green text will reappear, followed by red text indicating internal module information like 'copy flash' and 'erase'.
[Description of Figure 7.4: Image shows the ECClite interface indicating that the firmware update is complete.]
- Verify the controller's firmware version in the application's startup information (blue text, after approximately 20 lines).
[Description of Figure 7.5: Image displays a log output from the controller startup, showing firmware version details like 'HW4.XFW32R16' and 'Model Name [EVC4.31]'.]
The V32R16 firmware is shown in the logging upon application boot, indicating successful installation.
Important: During the update process, the USB to TTL cable must remain connected, and the controller must be continuously powered by the 12V DC supply.
9. Load and Send Configuration to the Module
Warning: Incorrect or improperly set configurations can permanently damage the controller. Ecotap is not responsible for such damage. Contact Ecotap for assistance if unsure.
Download the factory standard .json file provided by Ecotap for the specific station model. Save it to an easily accessible PC location. The manual uses "test.json" as an example. Always use the factory standard .json file provided by Ecotap for your station model.
[Description of Figure 8.1: Image shows a file icon labeled 'test.json', representing the configuration file.]
In ECClite, navigate to the "Settings" tab and click the button.
[Description of Figure 8.2: Image shows the ECClite interface with the 'Settings' tab selected and a button to load configuration.]
A file explorer will open. Locate the saved .json file on your PC and click "Open".
[Description of Figure 8.3: Image displays a file explorer window showing the 'test.json' file selected for loading.]
A selection of parameters specified by Ecotap within the Json file will be displayed. Adjust the values for these configuration keys as needed. An example with dummy values is provided.
[Description of Figure 8.4: Image shows the ECClite parameter configuration screen, with fields for values like 'com_Endpoint', 'com_OCPPID', and 'gsm_APN'.]
Adjust parameter values if applicable. When in doubt, contact Ecotap.
Once values are correctly entered, click the "Select All" button to select parameters identified by checkboxes.
Click the "Send selected" button to send these parameters and their values to the module.
[Description of Figure 8.6: Image shows the ECClite interface with parameters selected and the 'Send selected' button.]
Check the logging for the line "SV CFG()". This indicates successful configuration change acceptance.
[Description of Figure 8.7: Image displays log output confirming successful configuration change, showing 'SV CFG()' and a status message.]
To validate the configuration change, reboot the controller. After a few seconds, select all parameters again and click "Receive config". Correct values should be read from the controller module.
Chapter 11 provides a dictionary of parameters for modifying based on installation situations. Other parameters should be changed remotely via the connected OCPP Back-Office platform.
10. Troubleshooting
This section offers solutions for problems encountered while following the manual.
10.1. 'Windows protected your PC' message.
This message may appear when trying to open ECClite software. It's from Microsoft Defender, protecting against unknown applications. The software is not malicious but unrecognized.
Click "More info" to proceed.
[Description of Figure 7.1: Image shows a Microsoft Defender SmartScreen warning about an unrecognized app, with options to 'More info' or 'Don't run'.]
This provides more information about the application. Click "Run anyway" to start the application as expected.
[Description of the second Microsoft Defender window showing 'Run anyway' option.]
11. JSON Configuration Dictionary
ECClite supports JSON Get and Set configuration, including OCPP and Ecotap proprietary parameters, configurable via OCPP (Open Charge Point Protocol).
Note on input values: Commas (,) separate input values. For example, chg_RatedCurrent = [16,16] means the left channel is set to 16 amps and the right channel to 16 amps.
Parameters under "Show Readonly values" in ECClite can only be changed by the CPO via their connected Backend Platform / Central System.
| Configuration Key | R/W | Description |
|---|---|---|
| authorizationKey | WO | Authorization for a secure WebSocket. Writable only, not readable. Requires useTLS to be set. Format: <username>:<password>. Example: ECOTAP-1802500:9N8gGyS8Un7g4lY9dRICK. |
| chg_Debug | RW | Set debug logging options (CSL). See Table 1 for options and levels. Values are bitmasks; multiple levels can be added (e.g., 5 = 1 + 4 for Level 1 + Level 3). Example: 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 |
| chg_KWH1 chg_KWH2 chg_KWH3 | RW | Energy meter configuration for channel 1, channel 2, and utility meter (KWH3). Format: <type>,<address>,<speed>,<parity>,<stop-bits>. Example for utility meter: EASTR_SDM72D,3,9600,N,1 |
| chg_Reader1 chg_Reader2 | RW | Token Reader type (CSL). ECC supports one reader per channel, assignable to channel 1, 2, or any. Format: <type>,<channel>. Example for two readers: chg_Reader1: sl032,CH1. Example for shared reader: chg_Reader1: sl032,any. |
| chg_MinChargingCurrent | RW | Minimal current allowed to charge an EV (CSL). Value is current per phase in amps. Range: 0-63. Example: 6. |
| chg_RatedCurrent | RW | Rated current for a channel (CSL). Current in amps, determined by wiring. Never exceeds this value. Example: 16,16. |
| chg_StationMaxCurrent | RW | Maximum current the charger may consume per phase (CSL). Cannot exceed wiring limits. If utility grid fuse is smaller, use fuse value. Example for 25A fused charger: 25. |
| chg_Ch1Options chg_Ch2Options | RW | Charger options for a channel (CSL). See Table 6. 0 = Disabled, 1 = Enabled. Example: PlugAndCharge=0,OvercurrentSens=0,StopOnChargeComplete=0,OfflineStopOnDisconnect=0,StopOnLowCosphi=0,Rel2OnLowCosphi=0 |
| com_Options | RW | Communication Options (CSL). See Table 7. 0 = Disabled, 1 = Enabled. Example: Events=1,BlockBeforeBoot=1,Wdt=0,updSendInIdle=0,blockLgFull=0,useTLS=0,comMaster=0 |
| com_Endpoint | RW | Endpoint for the central system. Can define variables: #SN# (serial number) and #OSN# (OCPP ID). Example: ws.evc.net:80/#SN# |
| com_OCPPID | RW | OCPP Identification ID (Max 25 characters). Charger restarts after 60 seconds if changed. Example: EcotapTestID |
| com_OCPPInfo | RW | Other info for OCPP Protocol (CSL). See Table 3. Example: modelname=ECC-AC,vendorname=Ecotap,CpSn=G48229*1 |
| com_ProtCh | RW | Communication channel for Central System. Example: GSM or ETH. |
| com_ProtType | RW | Communication protocol for Central System. See Table 2. Example: OCPP1.6J. |
| eth_cfg | RW | Ethernet Interface configuration (CSL). Format: type=<type>,ip=<ip>,netmask=<netmask>,dns=<dns>,gw=<gw>. Example: Type=dhcp,ip=0.0.0.0,netmask=0.0.0.0,dns=0.0.0.0,gw=0.0.0.0 |
| grid_InstallationMaxcurrent | RW | Max current for master/slave grid (per phase) in amps. Range 0-9999. Set on master/supervisor. Example: 250. |
| grid_InstallationSaveCurrent | RW | Max current for master/slave grid when master loses communication (per phase). Range 0-9999. Used on master. Example: 100. |
| grid_Role | RW | Operation mode in a local power grid. See Table 4. Example: Station_ctrl. |
| gsm_APN | RW | GSM APN Information. Format: <APN name>,<APN user>,<APN password>. Name max 39 chars, user/password max 24 chars. Example: m2mservices,,. |
| gsm_Oper | RW | GSM Preferred Operator. Set to 0 for auto-selection, or LLLXX format (country code + provider code). Example for Netherlands: 20408 (KPN NL). |
| gsm_Options | RW | GSM options (CSL). 0 = Disabled, 1 = Enabled. Options: noSmsChk, AutoAPN, 3G4G. Example: noSmsChk=0,AutoAPN=0,3G4G=0. |
| gsm_SigQ | RO | GSM signal quality (0-99). Requires > 8 for valid connection. 99 means strength undetermined. Example: 15. |
[Description of Table 1: Debug options and levels.]
[Description of Table 2: Supported communication protocols.]
[Description of Table 3: Additional OCPP vendor information.]
[Description of Table 4: Grid roles.]
[Description of Table 5: Supported Token Reader types.]
[Description of Table 6: Charger Channel Options.]
[Description of Table 7: Communication options.]
devices.ecotap.com/registry/ocpp/NL*ECO*1000
