> For the complete documentation index, see [llms.txt](https://docs.copia.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.copia.io/docs/devicelink/basic/abb/abb-drives-neta-21.md).

# ABB Drives (NETA-21)

## Overview

ABB drives cannot send parameter backups over the network on their own. To back them up with DeviceLink, pair an ABB **NETA-21 Remote Monitoring Tool** with the [Copia FTP](https://docs.copia.io/docs/devicelink/basic/copia-ftp.md) integration:

1. The NETA-21 connects to one or more ABB drives and logs parameter values on a schedule. It writes them as CSV report files to its SD/SDHC card.
2. A Copia FTP project connects to the NETA-21's built-in FTP server and retrieves the report files on a scheduled Job. No custom scripting is required.

```
ABB Drive(s)  →  NETA-21 Module  →  Copia Agent (FTP)  →  Copia Repository
```

## Requirements

* A **NETA-21** module, purchased by the customer. A single NETA-21 can connect up to 32 drives on the same network.
* Drives connected to the NETA-21 over panel bus, DDCS fiber, or Modbus/RTU.
* A Copia Agent with network access to the NETA-21.
* The **NETA-21 Remote Monitoring Tool User's Manual**, particularly the *Reporting* chapter, which covers CSV-formatted reports and report triggers.

## Create a Repository

Create a repository to store the NETA-21 backups, for example `NETA21_Backups`. A single repository can hold backups from many NETA-21 units if each unit's reports are stored in its own folder (for example `DriveArea1`, `DriveArea2`).

## Configure the NETA-21 Module

1. Connect the NETA-21 to the target ABB drive(s) using panel bus, DDCS fiber, or Modbus/RTU.
2. Connect the NETA-21 to the customer network.
3. Go to **Reports > History logger** and set:
   * **Logging interval**: for example, 60 minutes, or whatever matches your drive-change tolerance.
   * **Parameters/Groups**: the parameter groups to log (for example Group 99, Group 30).
4. Go to **Reports > Settings > FTP/FTPS Access** and:
   * Confirm FTP is enabled for the SD/SDHC card.
   * Set and record the FTP username and password.
   * Record the report file directory path. You will use it as the start directory in Copia.

## Project Configuration

#### Define the Project

Add a Project from the **Projects** tab in your Copia Site:

| Field        | Value                                                                                                                                                                                                            |
| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Project Type | FTP                                                                                                                                                                                                              |
| Agent        | `{copia_agent_name}`                                                                                                                                                                                             |
| Project Path | Select the repository and branch (typically `main`) created for NETA-21 backups. Check **Create and select a new directory…** and name it `{unique_project_name}` (for example, the drive or NETA-21 unit name). |
| Project Name | `{unique_project_name}`                                                                                                                                                                                          |
| Description  | Optional                                                                                                                                                                                                         |
| File List    | Select an existing file list, or [create one](https://docs.copia.io/docs/devicelink/sitesandagents/sites/file-lists.md) with **Name** `NETA21_Reports`, **Project Type** FTP, and **Include in Backup** `*.csv`  |

#### Define the Device(s)

| Field               | Value                                                                                  |
| ------------------- | -------------------------------------------------------------------------------------- |
| Host / IP Address   | NETA-21 IP address                                                                     |
| Port                | `21`                                                                                   |
| Username / Password | NETA-21 FTP account credentials                                                        |
| Start Directory     | The report/history-log folder on the NETA-21 SD card, as set in **Reports > Settings** |

#### Define the Job(s)

Press **Add a Job** and choose your Job settings. Skip this step if you plan to use a sitewide job.

{% hint style="info" %}
Schedule the Job to run shortly after the NETA-21 logging interval so a fresh report is always available.&#x20;
{% endhint %}

#### Submit the Configuration

Press **Submit Project Setup**.

## Limitations

The NETA-21 report comes from the parameter history logger. It captures parameter **values**, not a full restore image.&#x20;

For disaster-recovery restore, pair this with a periodic Drive Composer backup (`.dcparamsbak`) committed to the same repository. Because the history logger CSV is plain text, it will produce a clean, human-readable diff in Copia Source Control; the `.dcparamsbak` file will version as a restorable, but binary file with no diff.&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.copia.io/docs/devicelink/basic/abb/abb-drives-neta-21.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
