---
title: "Evlink Pro AC, Lektri.co or Terra AC charger and KNX: read the feedback"
description: "Vehicle state, current, energy and error codes of an Evlink Pro AC, Lektri.co or Terra AC charger on KNX: DPTs, status values and troubleshooting in Link’nX."
canonical: https://wiki.can-nx.com/en/guides/link-charger-feedback/
language: en
product: Link’nX
audience:
  - utilisateur
  - administrateur
  - installateur
context: "Link’nX web: KNX gateway table of a declared EV charger, feedback tab"
---

# Evlink Pro AC, Lektri.co or Terra AC charger and KNX: read the feedback

Context: Link’nX web: KNX gateway table of a declared EV charger, feedback tab

The second tab of the Link’nX gateway table maps KNX group addresses to the feedback of an Evlink Pro AC, Lektri.co or Terra AC EV charger: vehicle and charging status, current, voltage, power, energy, cable locking and error codes. The tables below give the DPT of each feedback and the meaning of the status values, followed by the checks to run when charging does not go as expected.

Intended for installers and administrators who configure feedback, and for authorized users who interpret the displayed information. Always check which charger, which function and which observation time are concerned.

## Before you start

- The charger is [declared in the right gateway](https://wiki.can-nx.com/en/guides/link-charger-devices/).
- The read group addresses and their DPTs are planned in the KNX project.
- Charging commands are configured separately, in [the charger’s KNX commands](https://wiki.can-nx.com/en/guides/link-charger-knx/) or [a charger action](https://wiki.can-nx.com/en/guides/link-charger-actions/).

## Map a feedback to a group address

1. In the right project and gateway, open **Devices → Climate & Energy**, then **Evlink Pro**, **Lektri.co** or **Terra AC**.
2. On the charger’s row, click the **two opposing arrows**, **Gateway mode configuration**.
3. Open the **second tab**, marked with a message bubble. Check the function name and its **DPT** in the tables below.
4. Fill in its KNX group **Address** and tick **Active** if this feedback must be used.
5. Save with the floppy disk and wait for **Données sauvegardées avec succès !** (Data saved successfully!). Then reopen the table to check the values, as described in [the gateway table guide](https://wiki.can-nx.com/en/guides/link-gateway-table/).

## Evlink Pro AC feedback

| Displayed feedback | DPT |
| --- | --- |
| **Vehicle state**, **Last stop cause** | **5.010** |
| **EV presence** | **1.002** |
| **Current L1**, **Current L2**, **Current L3** | **14.019** |
| **Voltage L1**, **Voltage L2**, **Voltage L3** | **14.027** |
| **Total active power**, **Total apparent power** | **14.056**, **14.080**, respectively |
| **Power factor**, **Frequency** | **14.057**, **14.033**, respectively |
| **Total active energy**, **Session energy** | **13.010** |
| **Total reactive energy** | **13.012** |
| **Contactor charging time**, **Session charging time** | **12.100** |

**Vehicle state** is a numeric status, not a battery percentage. The documented values notably distinguish **2** available not ready, **3** vehicle connected not ready, **6** available ready, **7** vehicle connected ready, **8** charging and **9** charging with ventilation required. **4** and **5** correspond to a stop request in the charging states concerned. **0**, **1**, **10** and **11** describe other states of the control pilot signal: do not draw a hardware diagnosis from them without confirmation, and send the value and its context to support if the status is unexpected or unknown.

**Last stop cause** concerns the last session or the rejection of its start, not necessarily an error that is still active: 0 no cause given, 1 emergency stop, 2 vehicle disconnected, 3 hardware reset, 4 local command, 5 other, 6 power loss, 7 reboot, 8 remote command, 9 software reset, 10 unlock command, 11 not authorized. Report an unexpected value to support without inferring the current cause from it.

Before programming a condition on **EV presence**, have support confirm the **0/1** mapping for your installation: the polarity cannot be inferred from the label alone.

For **Total active power** and **Total apparent power**, have the unit and scale expected by your display confirmed before any calculation or comparison. Do not assume an automatic conversion between W and kW, or between VA and kVA, based on the row name.

## Lektri.co feedback

| Displayed feedback | DPT or useful unit |
| --- | --- |
| **Charger state**, **Extended charger state**, **Firmware version** | **16.001**, text |
| **Session charged energy**, **Energy index**, **Total charged energy** | **13.010**; the session is expressed in Wh |
| **Session charging time** | **12.100**, seconds |
| **Session ID**, **Heap free space** | **12.001**; these are not power measurements |
| **Instant power** | **14.056**, W |
| **Current**, **Current phase 1**, **Current phase 2**, **Current phase 3**, **Install current**, **Dynamic current**, **Load balancing current limit**, **PWM current value** | **14.019**, A |
| **Voltage**, **Voltage phase 1**, **Voltage phase 2**, **Voltage phase 3** | **14.027**, V |
| **Temperature** | **9.001** |
| **Current limit reason**, **LED brightness** | **5.010** |
| **Headless flag**, **Active errors flag**, **Charger paused flag** | **1.001** |

**Charger state** returns a letter, from A to F according to the IEC 61851 standard, as stated in the row’s help. **Extended charger state** notably distinguishes **A** (vehicle disconnected), **B** (connected), **B_AUTH** (waiting for authentication), **C** (charging), **D** (charging with ventilation required), **E** (error), **OTA** (update), **LOCKED** (charger locked), **B_PAUSE** (pause) and **B_SCHEDULER** (pause due to the schedule). These texts are specific to Lektri.co: do not convert them into a Terra AC or Evlink status number.

**Current limit reason** distinguishes: 0 hardware capabilities, 1 installation limit, 2 user limit, 3 dynamic current, 4 schedule, 5 offline energy management, 6 energy management, 7 OCPP current. Read this feedback before changing a setpoint. It indicates the reason reported by the charger, without a procedure for changing these settings.

**Current** is not the sum of the three phases: use the phase feedback to distinguish them. Likewise, distinguish **Dynamic current**, **Install current** and **Load balancing current limit**. The availability of measurements depends on the information provided by the charger; a missing measurement is not a zero value.

## Terra AC feedback

| Displayed feedback | DPT |
| --- | --- |
| **Charging state**, **Socket lock state** | **5.010** |
| **Charging current limit (A)**, **Current L1 (A)**, **Current L2 (A)**, **Current L3 (A)**, **User settable max current** | **14.019** |
| **Active power (W)** | **14.056** |
| **Voltage L1 (V)**, **Voltage L2 (V)**, **Voltage L3 (V)** | **14.027** |
| **Energy delivered (Wh)** | **13.010**, session energy |
| **Error code** | **7.001**; do not reduce it to a byte |

**Charging state**: 10 idle, 20 vehicle plugged in waiting for authorization, 21 ready to charge, 30 vehicle ready without PWM, 40 charging at nominal current, 41 charging below the commanded value, 50 other state and 99 unknown. This feedback does not indicate the vehicle’s battery percentage. **41** signals limited charging, not necessarily a fault.

**Socket lock state**: 0 no cable; 1 cable on the charger side, unlocked; 2 cable on the charger side, locked; 3 cable connected to the charger and the vehicle, unlocked on the charger side; 4 connected to both and locked on the charger side; 99 unknown. To know whether a charge is in progress, read **Charging state**: the cable status alone is not enough.

For **Error code**, use the manual for the model or send the exact code to support. The number alone gives neither a component diagnosis nor a repair procedure. According to the row’s help, **User settable max current** is set with the Terra Config app, whose steps and setting limits are not described here; have them confirmed if needed.

## Check the result

Check the feedback obtained on your installation’s viewing device. The gateway table configures the associations; its rows do not show the charger’s measurements live. Only a value read on this device shows that a measurement is received; a missing value is not a zero value.

## Troubleshooting

- No feedback: check the gateway, the charger’s declaration, the feedback tab, the address, the DPT, the **Active** box and the save. Then check that the viewing device actually requests the associated feedback. Do not present missing data as 0 or as a stopped charge.
- Vehicle connected but not charging: compare the charging status, the pause or the schedule and, if available, the limitation reason. A start request, a locked socket or a saved current limit must always be checked by observing the result. For an Evlink Pro AC or Lektri.co scenario command, have the path confirmed by support.
- Charging lower than expected: distinguish the setpoint, the current actually measured and the various limits displayed. Do not raise a limit just to make the symptom disappear.
- Status or error code not understood: note the exact value, the function and the observation time, then contact support.

## Contact support

If the checks have already been done, write to support@can-nx.com with the family and model if known, the gateway, the function and its DPT, the exact value or message, the observation time, the expected result and the checks already carried out. Add a screenshot without sensitive data if it helps; never send a password, key or private log.

French labels: **État du véhicule**, **Présence du véhicule** and **Cause de l'arrêt de la dernière session** (Evlink), **État du chargeur**, **État du chargeur étendu** and **Raison de la limite de courant** (Lektri.co), **État de charge**, **État du verrouillage de la prise** and **Code erreur** (Terra AC).