---
title: "Atmoce and KNX: control the battery and read PV measurements"
description: "Connect an Atmoce gateway to the KNX bus with Link’nX: remote mode, power setpoints, dispatch, battery SoC, power readings and energy meters, each with its DPT."
canonical: https://wiki.can-nx.com/en/guides/link-atmoce-knx/
language: en
product: Link’nX
audience:
  - administrateur
  - installateur
context: "Link’nX web: KNX gateway table of a declared Atmoce PV and storage gateway"
---

# Atmoce and KNX: control the battery and read PV measurements

Context: Link’nX web: KNX gateway table of a declared Atmoce PV and storage gateway

The Atmoce gateway table in Link’nX maps the group addresses of your KNX project to the control of an Atmoce PV and storage system (remote mode, power setpoints, dispatch, restart) and to its measurements: statuses, powers, voltages, currents, state of charge and energy meters. A KNX visualization or logic can then read the battery status and send it setpoints.

Intended for installers and administrators authorized to configure PV and storage control. **Force charge** and **Force discharge** are not in this table: they are prepared with [the Atmoce scenario actions](https://wiki.can-nx.com/en/guides/link-atmoce-actions/).

## Before you start

- The Atmoce gateway is [declared in Link’nX](https://wiki.can-nx.com/en/guides/link-dga-devices/).
- The group addresses, powers and limits of the installation are confirmed.

## Open the Atmoce gateway table

1. Check the Link’nX project and gateway.
2. In **Devices → Climate & Energy → Atmoce**, find the physical gateway concerned.
3. Click its two opposing arrows, before the pencil. **Gateway mode configuration** opens.

The table applies to this gateway only. The address format, the filters and tab changes are described in [the gateway table guide](https://wiki.can-nx.com/en/guides/link-gateway-table/).

## Map the KNX commands

1. In **Actions**, fill in the **Address** of each function you want and tick **Active**. The name and the DPT are set by the table.
2. Save the tab with the floppy disk at the bottom right and wait for **Succès** (Success) and **Données sauvegardées avec succès !** (Data saved successfully!).

| Function | DPT | Value and scope |
| --- | --- | --- |
| **Remote control mode** | 1.001 | ON: remote control; OFF: gives control back to the local self-consumption or time-of-use (TOU) mode |
| **Active power setpoint (W)** | 14.056 | Fixed positive or zero power, in watts, within the installation’s limits |
| **Active power setpoint (%)** | 5.001 | From 0 to 100% |
| **Dispatch power (W, signed)** | 14.056 | Negative: charge; positive: discharge; 0: dispatch stop |
| **System reset** | 1.001 | Restart of the whole system, with the prerequisites below |

Power setpoints require remote control, and stopping them does not give control back to the local mode. To resume local operation, send OFF on **Remote control mode**, then check **Operating mode**. The switchover delay and the effect on the installation show in the feedback, not at sending.

To deactivate an association, untick **Active** and save. This is neither a command to stop the battery nor a return to local mode.

## Prepare System reset

**System reset** restarts the entire plant: PV, battery and gateway. It requires:

- a gateway running Modbus protocol V1.2 or later; the presence of the row in the table does not confirm your hardware’s protocol version;
- two activation telegrams within three seconds; a single telegram or an OFF does not trigger the restart.

Feedback can disappear during the restart. Have the need and the prerequisites confirmed by the installer or support before configuring this restart. Do not use it as a repeated test to bring back missing feedback.

## Map the status feedback and measurements

1. Open the **second tab**, marked with a speech bubble.
2. Fill in the **Address** of the feedback you want, tick **Active** and save this tab too.

| Feedback | DPT | Meaning |
| --- | --- | --- |
| **Plant fault** | 1.005 | 0 normal, 1 fault; this is not a component diagnosis |
| **Storage status** | 5.010 | 1 charging, 2 discharging, 99 neither; 99 is not a battery percentage |
| **Operating mode** | 5.010 | 1 self-consumption, 2 time-of-use (TOU), 10 remote control |
| **Battery SoC** | 5.001 | Percentage from 0 to 100 |
| **PV power**, **Battery power**, **Grid power** | 14.056 | Power in watts |
| **Voltage L1**, **Voltage L2**, **Voltage L3** | 14.027 | Voltage in volts |
| **Current L1**, **Current L2**, **Current L3** | 14.019 | Current in amperes |
| **Max charging power limit**, **Max discharging power limit** | 14.056 | Limits in watts; these are not setting commands |

To interpret the sign of **Battery power** and **Grid power** on your installation, ask the installer or support for confirmation before inferring a flow direction. This caveat concerns only these measurements: the dispatch command follows the sign convention of the commands table.

Energies use DPT 13.013 and are expressed in Wh. Each cumulative meter has a daily meter:

| Cumulative meter | Daily meter |
| --- | --- |
| **PV energy** | **PV energy (today)** |
| **Battery energy charged** | **Battery energy charged (today)** |
| **Battery energy discharged** | **Battery energy discharged (today)** |
| **Grid energy exported** | **Grid energy exported (today)** |
| **Grid energy imported** | **Grid energy imported (today)** |

Choose the meter that matches the period you want, and do not confuse a cumulative energy with an instantaneous power. For a very large meter or a capped value, have the usable value confirmed before calculating a balance.

## Check the result

1. Go back to the list, reopen the gateway and review the addresses and **Active** checkboxes of each tab.
2. Then check the exchange on the bus, for example with the ETS group monitor, and the effect of a setpoint on the **Operating mode** and **Storage status** feedback. Saving the table validates the configuration; only the feedback and the installation show that a command was applied to the battery.

## Troubleshooting

- **Storage status** is 99: this feedback means neither charging nor discharging, not a full battery. The percentage is read with **Battery SoC**.
- **Operating mode** stays at 10 after stopping dispatch or forcing: these stops do not request the return to local mode. Check the **Remote control mode** association, the sending of OFF, then the **Operating mode** feedback.
- A feedback is missing: check the project, the gateway, the feedback name, the address, the DPT, the **Active** checkbox and the save by reopening the table. Clear the filters if the row is hidden. A missing value is not equivalent to zero.
- A measurement per microinverter or per charger cannot be found: the feedback in this table describes the system attached to the gateway, not each individual device.

For a fault, an inconsistent value or a command without effect after these checks, contact support@can-nx.com with the project and gateway, the model, the function, the address, the DPT, the observed value and the tests already done.

French labels: **Mode contrôle à distance**, **Puissance de dispatch (W, signée)**, **Reset système**, **État du stockage**, **Mode de fonctionnement**, **État de charge batterie**, **Énergie PV (aujourd'hui)**.