> 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/git-based-source-control/supported-vendors/wago.md).

# WAGO e!COCKPIT

### Overview

Copia provides support for **e!COCKPIT v1.10**, with advanced feature support for the following\*\*:\*\*

* [Graphical Display and Differences](#graphical-display-and-differences)

{% hint style="info" %}
WAGO is migrating their ecosystem to CODESYS 3.5 instead of e!COCKPIT. For CODESYS, Copia has both [Advanced Git](/docs/git-based-source-control/supported-vendors/codesys.md) and [DeviceLink](/docs/devicelink/basic/codesys-v3.md) support.
{% endhint %}

### Configuration

Copia supports\* WAGO e!COCKPIT project files in native `.ecp` format. You can just drop your `.ecp` files into your repository, and the Copia desktop client will display the project data logic and differences.

{% hint style="warning" %}
*The `.ecp` display/difference is generated using a Codesys-based conversion to .project format. As such, some items may not be supported for rendering, such as Wago internal libraries, configurators or targets/runtimes.*
{% endhint %}

In addition, Copia supports the CODESYS 3 Export format (i.e. `.export` files). To export from e!COCKPIT, click the *Export* button under the *Program* menu option.

![](https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2FCvjrDjbvZlDLi8Ei9Z1B%2FWAGO_ExportOption.png?alt=media\&token=21ea8b7e-599f-48e5-a461-3d67a187e02f)

You should now see the export dialog. Check all items by choosing the *Select all* option and then click the *Export* button:

![](https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2Fs2X4NXxNgEaOzxGUb4hp%2FWAGO_SelectAll.png?alt=media\&token=328a70b0-b448-442c-9ba3-ab3c67f748e6)

Export your exported project file as a `.export` and save it to the repository folder. Once you perform the appropriate [commit and push](/docs/git-based-source-control/basic/making-changes/saving-changes.md#commit--push-a-change) operations, you'll be able to see your project file and all of its data from both the Web App and Desktop App.

### Graphical Display and Differences

#### General

When the project file is selected in the Web App or Desktop App, Copia displays the project tree structure in a way that's familiar to users of e!COCKPIT software. This way, you can easily navigate to a project item or identify differences.

![](https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2FGphtYmWgWCz53sS7IvTM%2FWAGO_GraphicalDisplay.png?alt=media\&token=7a38c7a7-2457-4b71-a7e6-066a0b8f76d6)

#### Supported Types

The following CODESYS types are supported in graphical or enhanced output:

* Ladder (LAD)
* Structured Text (ST)
* Tasks
* UDT
* Global Variable List

Copia also supports the following types:

* PLC Device
* Alarm Configuration
* Application
* Communication Manager
* Data Sources Manager
* DUT
* Global Variable List (tasklocal)
* Interface
* Network Variable List (Receiver)
* Network Variable List (Sender)
* Persistent Variables
* POU's to include:
  * Action
  * Method
  * Property
  * Transition
* Recipe Manager
* Task Configuration
  * Task
* Trace
* Trend Recording Manager


---

# 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/git-based-source-control/supported-vendors/wago.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.