---
title: "Atmoce actions: force charge, dispatch and return to local mode"
description: "Prepare an Atmoce action in Link’nX: forced battery charge or discharge, dispatch setpoint and return to local mode after remote control of the gateway."
canonical: https://wiki.can-nx.com/en/guides/link-atmoce-actions/
language: en
product: Link’nX
audience:
  - administrateur
  - installateur
context: "Link’nX web: Actions form, Atmoce type, for a declared PV and storage gateway"
---

# Atmoce actions: force charge, dispatch and return to local mode

Context: Link’nX web: Actions form, Atmoce type, for a declared PV and storage gateway

In Link’nX, an Atmoce action prepares a command for an Atmoce PV and storage gateway: forced charge or discharge of the battery, dispatch setpoint, or switching between remote control and local mode. Forcing exists only in this form; the KNX table does not offer it.

Intended for administrators and installers who prepare the control of a PV and storage installation. To map KNX group addresses to the gateway’s setpoints and measurements, follow [the Atmoce KNX gateway guide](https://wiki.can-nx.com/en/guides/link-atmoce-knx/) instead.

## Before you start

- The Atmoce gateway is [declared in Link’nX](https://wiki.can-nx.com/en/guides/link-dga-devices/).
- The installer has confirmed the powers, the battery limits and the authorized use on the installation.
- Support has confirmed the path for saving and running Atmoce actions for your version. This guide describes the visible commands and parameters so that you can prepare this request: until this path is confirmed, treat a filled-in action as neither saved nor run.

## Create the action and choose the command

1. Check the Link’nX project and gateway.
2. Open **Actions → Add**, then choose **Atmoce** in **Select an action type**.
3. Fill in **Name**: required, 64 characters maximum, not only spaces.
4. In **Atmoce gateway(s) to control**, select the gateways concerned. After **Select all**, review all the targets.
5. In **Command**, choose the operation using the table below.

| Command | Parameters | Requested effect |
| --- | --- | --- |
| **Force charge** | Positive power and stop condition | Charges the battery; can draw from the grid even if grid charging is disabled |
| **Force discharge** | Positive power and stop condition | Discharges the battery; can export to the grid |
| **Exit forced mode** | No power or duration field | Stops forcing, without giving control back to the local mode |
| **Set dispatch power** | **Dispatch power (W)**, signed | Negative to charge, positive to discharge, 0 to request that dispatch stop |
| **Set remote mode** | **Remote mode ON** box | Ticked: remote control; unticked: return to the local self-consumption or time-of-use (TOU) mode |

## Set a forced charge or discharge

1. Fill in **Forced power (W)** with a strictly positive value confirmed for the installation. The chosen command sets the direction; the sign of the power does not change it.
2. In **Stop condition**, choose **Target SOC (%)** or **Duration (minutes)**.
3. For a target, fill in **Target SOC (%)** between 0 and 100. For a duration, fill in **Duration (min)** between 0 and 1440. These ranges are those of the form: choose values suited to your battery with the installer.

Only one condition is used: the target SOC or the duration. Forcing therefore does not stop “at whichever threshold is reached first”. Fictitious examples: 1000 W up to a target of 80%, or 1000 W for 30 min.

## Stop forcing or return to local mode

Stopping a setpoint and giving control back to the local mode are two separate requests.

| Goal | Command to use | Requested result |
| --- | --- | --- |
| Stop a forced charge or discharge | **Exit forced mode** | Forcing stops; the gateway stays in remote control |
| Stop dispatch | **Set dispatch power** at 0 | Dispatch stops; the local mode is not restored |
| Return to the local self-consumption or time-of-use (TOU) mode | **Set remote mode** with **Remote mode ON** unticked | Return to local operation |

The return to local mode is requested with this command, in the path confirmed for your version, or with the **Remote control mode** KNX association set to OFF, described in the KNX gateway guide.

## Check the result

Check the effect of a command on the gateway itself, for example with the **Operating mode** KNX feedback: 1 self-consumption, 2 time-of-use (TOU), 10 remote control. After a request to return to local mode, give the gateway time to change mode before drawing conclusions.

## Troubleshooting

- The floppy disk produces no result: check the name, the targets, the command and its parameters, then have support confirm the path suited to your version. If these fields have already been checked, tell support directly rather than re-entering them.
- **Force charge** is missing from the KNX table: this is expected, because forcing combines several parameters and is prepared only in this form. Do not replace it with a series of KNX associations assumed to be equivalent.
- **Operating mode** stays at 10 after exiting forcing: the value 10 corresponds to remote control, and exiting forcing does not restore the local mode. Send the request to return to local mode, then read the feedback again.
- You are considering **System reset** to unblock charging: this is not an ordinary troubleshooting step, because it restarts the whole PV, battery and gateway system. See its scope and prerequisites in [the Atmoce KNX gateway guide](https://wiki.can-nx.com/en/guides/link-atmoce-knx/) and have support establish the need.

If the problem persists, contact support@can-nx.com with Link’nX, the project and gateway, the gateway model, the command, the power, the chosen stop condition, the observed result and the tests already carried out. Do not send any password or key.

French labels: **Passerelle(s) Atmoce à piloter**, **Charge forcée**, **Décharge forcée**, **Puissance du forçage (W)**, **Condition d'arrêt**, **Cible SOC (%)**, **Durée (min)**, **Sortir du mode forcé**, **Consigne de dispatch**, **Mode distant**, **Mode distant ON**.