LogoLogo
  • Overview
    • Introduction
      • Git-Based Source Control
      • DeviceLink
    • System Requirements
    • Supported Vendors and Device Types
    • Glossary
  • Git-Based Source Control
    • Getting Started
      • Planning
      • Initial Setup
        • Migrations
    • Basic Tasks
      • Navigation
        • Home page
        • Exploring the Web App
        • Exploring the Desktop App
      • Configuration
        • Creating Repositories
        • Creating Templates
        • Cloning Repositories
      • Operations
        • Pulling
        • Committing
        • Pushing
        • Managing History
        • Binary & Large Files
    • Advanced Tasks
      • Branching
        • Branch Protections
      • Pull Requests & Code Review
        • Contributors
        • Reviewers
      • Merging
    • Additional Features
      • Topics
      • Issues
        • Milestones
        • Labels
        • References and Links
      • Wiki
      • Tags & Releases
      • Webhooks
      • Activity
    • Administration
      • Org Settings
      • User Management
        • External Identity Management (SSO + SCIM)
      • Teams & Permissions
        • Permissions by Account Type
      • Registration & Billing
      • Repo Settings
      • Desktop App Options
      • Profile and Settings
        • Notifications
        • Two-Factor Authentication (2FA)
    • Supported Vendors
      • ABB
      • Beckhoff
      • B&R Automation
      • CODESYS
      • Inductive
      • Lenze
      • Rockwell
        • RSLogix 500
        • RSLogix 5000
        • Studio 5000 Logix Designer
      • Schneider
        • Control Expert
        • Machine Expert
      • Siemens
        • Siemens Step7 TIA Portal
        • Siemens Step7 5.x
      • WAGO
    • Integrations
      • Discord
      • Jira
      • Microsoft Teams Connectors
      • Slack
      • Zapier
      • Microsoft Teams Workflows
  • DeviceLink
    • Getting Started
      • Architecture
      • Planning & Installation
    • Sites and Agents
      • Sites
        • Site Settings
        • File Lists
        • Graphs and Metrics
      • Agents
        • Creating a Site-Based Agent
        • Creating a Multi-Site Agent
    • Projects and Devices
    • Vendor Configuration
      • Beckhoff TwinCAT 3
      • CODESYS v3
      • Copia FTP
      • Copia sFTP/SCP
      • Copia Scripting
      • FANUC Robots
      • Rockwell RSLogix 500
        • Smart Filter
      • Rockwell Studio/RSLogix 5000
        • Smart Filter
      • Rockwell PanelView ME HMI
      • Schneider Control Expert
      • Siemens Step7 TIA Portal
      • Siemens Step7 5.x
    • Jobs
      • Job Navigation
      • Creating Jobs
      • Managing Jobs and History
      • Manual Backups
      • Pull Requests
    • Additional Features
      • Webhooks
      • Copia Import Tool
        • Getting Started
        • Preparing your data
        • Importing your data
        • Rolling back a prior import
    • Administration
      • Teams
      • Permissions
      • Notifications
  • Copilot
    • Copia Copilot
    • Getting Started
    • Using Copia Copilot
  • Copilot FAQ
  • Support
    • Best Practices
    • FAQs
      • Git-Based Source Control
        • Troubleshooting
      • DeviceLink
        • Troubleshooting
Powered by GitBook
On this page
  • Agent Requirements
  • Linking to a Project
  • Setting up the TwinCAT Route to the Device
  • New Project Configuration
  • Define the Project
  • Define the Device(s)
  • Define the Job(s)
  • Submit the Configuration

Was this helpful?

  1. DeviceLink
  2. Vendor Configuration

Beckhoff TwinCAT 3

PreviousVendor ConfigurationNextCODESYS v3

Last updated 2 years ago

Was this helpful?

Agent Requirements

Below are the Agent system requirements to configure a Copia Agent for the backup of Beckhoff Twincat3 projects:

  • Installation of Beckhoff TwinCAT 3 (at least Build 3.1.4024.29) with the standalone TcXAEShell option (i.e. not the Visual Studio add-on).

  • Any additional vendor software required for project backup from the devices must be licensed and installed on PC running the Copia Agent. (i.e. Add-on's etc.)

  • The Agent should be tested using the installed Beckhoff software, and proven able to backup the project without error.

Setting up the TwinCAT Route to the Device

To back up a Beckhoff device, Beckhoff TwinCAT requires a preconfigured route from the agent machine to the device. This is a bit like Bluetooth pairing -- the devices may be on the same physical network before this step, but without setting this up they can't do anything that requires TwinCAT communications, like a backup. Here are the necessary steps:

  • Click the Beckhoff tray icon. It looks like this:

  • Click Router > Edit Routes:

  • Click Add > Broadcast Search:

  • Click on the device you want to add, then click Add Route:

  • At this point you'll need the login information of the device you're setting up. Once you enter the username and password, click Add Route. You should see a little icon like this under Connected in the Routes dialog if everything works:

Linking to a Project

Now that you've created your Device, it's time to link it to your Project. Click the caret in the device card and choose Edit Device.

Setting up the TwinCAT Route to the Device

To back up a Beckhoff device, Beckhoff TwinCAT requires a preconfigured route from the agent machine to the device. The devices may be on the same physical network before this step, but without setting this up they can't do anything that requires TwinCAT communications, like a backup. Here are the necessary steps:

  • Click the Beckhoff tray icon

  • Click Router > Edit Routes

  • Click Add > Broadcast Search

  • Click on the device you want to add, then click Add Route

  • At this point you'll need the login information of the device you're setting up. Once you enter the username and password, click Add Route.

New Project Configuration

To configure a new project for Beckhoff TwinCAT 3, you will need a target repository for the project folder. You may either:

  • or, you may create an empty project folder in the repository during the process below, and "upload" the project into the folder from the device

In the both cases, you will need to know the communication parameters for the device, which are stored in the project, to fill out all of the required fields.

Click either of the Add a Project buttons in the Projects tab.

The Add a new project configuration dialog will appear which allows you to fully configure the project, devices and job for the project.

Any items highlighted with an asterisk are required.

This is a multi-step process with each section explained in detail. At any time, you can edit the prior section of this workflow.

The project can be edited after creation. Devices and Jobs can also be edited or created directly, using the Devices or Jobs tab. The steps for creation are similar to the steps provided below for those sections.

Define the Project

When complete, press Save and Continue.

You will now select the Project Path, which is the location (Repo/Branch) that the project is, or will be stored.

You can edit the previous steps at any time.

For Beckhoff TwinCAT3, you can either select an existing project folder, or create a new empty project folder (so that you can upload a copy from the device) for an initial revision. You can make this choice after you have selected the repository and branch for the project folder.

If you choose to select an existing folder, you should select the folder which contains the .tsproj file as the TwinCAT3 project folder.

In this example, we will create a new empty project folder.

Once complete, press Save and Continue to proceed.

The project details allows you to update the Project name, and description if desired. In addition, you will need to select the filelist for a Beckhoff TwinCAT 3 backup. This tells Copia what to copy when making a backup. Copia has provided a recommended default filelist that you can select, or you can choose to create your own.

Once complete, press Save and Continue to proceed.

Define the Device(s)

The Device Setup section is for defining the device information (PLC, communication path, etc) that is in your project. If you have pre-created devices, you can add existing devices, otherwise you can Add a Device as seen.

For Beckhoff TwinCAT3, the Communication Path will be the AMS Net ID of the project.

The AMS NET ID can be found on the Copia Agent, according to the routes that have been configured and tested during initial setup.

Press Save Device when complete.

Though more devices can be added, Copia only supports a single device per project at this time.

Once complete, you can proceed to Add a Job.

Define the Job(s)

Submit the Configuration

Once complete, press Submit Project Setup to create the Project, Device(s) and Job(s).

Already have a Beckhoff TwinCAT 3 project folder created in this repository (see the section of Git-based Source Control)

To get started, we will first select the Project Type from the list provided, and then select an Agent. If you have not already created an Agent, you can create and assign an Agent at a later time. See more about this in the section of the documentation.

Creating Jobs is similar for all vendor types, and is described in the section. It is recommended to review that section while completing a job configuration, and press Save to save the job. You can create more than one job for a device if desired.

Don't forget to enable/disable the button, based on your preferences for project .

Agents
Creating Jobs
Notifications
Beckhoff Configuration
Watch
If the icon is not visible, ensure you have installed TwinCAT 3. If you have TwinCAT 3 and still cannot see the icon, it may be nested inside the icon tray's caret -- ^
In some cases, this icon will be an x instead of the plug. This is not an issue and backups will work just the same.