Integrate Reduxi with the ABB Terra Wall-Box charger via Wi-Fi, utilizing the Modbus TCP/RTU or OCPP protocol. Reduxi's flexibility allows cost reductions of up to 30%.

1. Install the TerraConfig application

1.1 TerraConfig Platform:

https://abb.installer.chargedot.com/#/login

1.2 The application is available on the Google Store:

https://play.google.com/store/apps/details?id=com.abbemobility.terraconfig

1.3 The application is available on the Apple App Store:

https://apps.apple.com/us/app/terraconfig/id6443887124

 

2. Connect to the TerraConfig application

2.1 Login/Registration to the TerraConfig app

Open the application and either log in or register a new account by clicking the 'SIGN-UP' button, then log in.

2.1.1 TerraConfig charger settings

Once logged-in configuration for TerraConfig app needs to be performed.

• Dashboard (click on Configure a charger):

• Connect to charger (available device):

• Fill in the basic settings:

 

2.1.2  TerraConfig charger OCPP server parameters

• Enable the External Server.
• The OCPP url server is obtained from the Reduxi controller.

• Fill in the Energy Management parameters (Enable the Modbus): 

 

2.1.4 TerraConfig charger Modbus settings

• Choose Local Controller

• Modbus settings (RTU):

The same settings must be applied on the Reduxi controller for RS485 port1 or port2.

• Set parameter for Modbus TCP/IP, for communication purposes to Reduxi contoller.

 

2.1.4 Connect to Wifi

 

3. OCPP communication between the ABB Terra AC Wall-box charger and the Reduxi controller

3.1  Add device

First login to the local Reduxi configurator and add a new device by clicking on the 'Add device' button.

 

3.2 Select the device that would you like to add

Within the first step select basic settings:

• Select Device type: EV charger,
• Select Type: OCPP 1.6 - JSON,
• And define the name.

4.3 Device Configuration for OCPP

The second step is used for the Communication channel, for OCPP communication to work properly. First, fill in the Device identifier obtained from the TerraConfig app.

When OCPP JSON 1.6 protocol is utilized, server OCPP URL is needed, generated by Reduxi controller. URL can be obtained directly from the Communication channel. 

Device ID (Unique OCPP ID) is obtained from charger (on right side of charger starts with TACW11-4-......) and needs to be set in communication channel.

Example URL: ws://192.168.1.200/ocpp/1.6/json/

 

4.4 Configure OCPP settings in the TerraConfig

Link to: 2.1.2 ABB Terra Wall-box charger OCPP server parameters      

 

4.5 Test communication

To ensure that OCPP communication is established, a communication test can be performed via the 'Test communication button' located bottom right after all Communication channel fields.

There are three different cases of communication response.

Case 1: Communication is working properly.

Case 2: Unable to communicate with device 1, the ID of the device is not set or is different.

Case 3: No device with OCPP 1.6 communication is found.

 

4. Modbus TCP/IP communication between the ABB Terra AC Wall-box charger and the Reduxi controller

Link to ABB liberally for Modbus communication of ABB Terra AC Wall-box: 

https://library.e.abb.com/public/4124e0d39f614ba7b0a7a6f7a2ce1f99/ABB_Terra_AC_Charger_ModbusCommunication_v1.7.pdf

4.1  Add device (ABB Terra AC Wall-box charger)

First login to the local Reduxi configurator and add a new device by clicking on the 'Add device' button.

 

4.2 Select the device that would you like to add

Within the first step select basic settings:

• Select Device type: EV charger,
• Select Type: ABB Terra AC Wall-box,
• and define the name.

 

4.3 Device Configuration for Modbus TCP/IP

The second step is used for the Communication channel, for Modbus TCP/IP communication to work properly. First, fill in the obtained IP from ABB Terra AC wall-box and define Modbus ID, which by default is set to 1.

 

4.4 Test communication

To ensure that Modbus TCP/IP communication is established, a communication test can be performed via the 'Test communication button' located bottom right after all Communication channel fields.

Example IP: 192.168.2.201

There are three different cases of communication response.

Case 1: Communication is working properly reading:

Case 2: Unable to communicate with the device on IP = 192.168.2.201, IP of the device is different:

 

Case 3: The port chosen is not correct, check the port for Modbus TCP/IP:

4.5 Default parameters

Fill in the advanced settings and choose the parameters shown in the image below. Settings can vary depending on location needs. Once you are done, click the 'Done' button on your screen.

 

5.1 Readings from Device for OCPP or Modbus TCP/IP

The purpose of this point is to show how to check readings from the device. This is done under 'Device/Last measurement'.

Once the device is successfully added through the configurator, it can be monitored via the cloud application Reduxi.