The connection between Reduxi and GL charge LiteBox can execute the DLMS to protect installation.
1. Logo
2. Connect the GL Charge LiteBox to the PC
2.1 Connection between PC and charger
Both devices must be on the same network to configure the GL Charge Litebox. Once this criterion is met user can connect to the browser interface of the charger on the preferred browser.
Procedure:
- Paste/write IP and add port 8080 of the charger to your browser (example: 10.150.1.104:8080)
- Login it with, Username: admin, Password:glc999
2.2.1 Browser Interface (Charger Configuration)
Steps for correct settings:
- Charger mode, set to 1 = APP.
- Set the charger ID to the preferred value (example:1234).
- Write/Paste the Server URL of the Reduxi controller (see 3.3 Device Configuration for OCPP).
- Delete Authentication Key.
3. OCPP communication between the GL charge LiteBox and the Reduxi controller
3.1 Add device
First login to the local Reduxi configurator and add a new device by clicking the 'Add device' button.
3.2 Select the device that you would like to add
Within the first step select basic settings:
- Select Device type: EV charger,
- Select Type: OCPP 1.6 - JSON,
- Name the device.
3.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 (Set charger ID 2.2.1) obtained from the browser, which needs to be pasted into the communication channel first field.
When the OCPP JSON 1.6 protocol is utilized, the server OCPP URL is needed and generated by the Reduxi controller. URL can be obtained directly from the Communication channel.
Example URL: ws://10.150.120/ocpp/1.6/json/
3.4 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. Readings from Device
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.