Beckhoff
Overview
Copia provides support for Beckhoff TwinCAT 3, with advanced feature support for the following:
Configuration
Copia supports Beckhoff TwinCAT 3 project files and .library
library files.
To get set up, simply store the Beckhoff TwinCAT 3 project files in a project folder within a Copia repository. Once you perform the appropriate commit and push operations, you'll be able to see your project file and all of its data from both the Web App and Desktop App.
Putting the Beckhoff TwinCAT 3 project in a sub-folder (and not the root) of the Copia repository allows you to more easily integrate DeviceLink operations at a later time.
Graphical Display and Differences
General
Copia provides both a graphical rendering of Ladder Logic and clear rendering of Structured Text programs for Beckhoff TwinCAT 3. For other project files with tree-based navigation, Copia provides text and/or tabular data to show changes within the project.
Supported Types
The following types are supported in graphical or enhanced output:
Ladder (LAD)
Structured Text (ST)
Copia also includes support for the following types, which may include hierarchical navigation, text, or tabular details:
.tsProj (TwinCAT project file)
.plcProj (TwinCAT PLC project file)
.tspProj (standalone TwinCAT PLC project file)
.tcTTO (PLC task object)
.tcDUT (PLC data type)
.tcIO (PLC object)
.tcPOU (PLC program organizational unit)
.tcGVL (PLC global variable list)
.splcProj (TwinCAT safety project file)
.library (library file)
In some cases, if the content of the file is modified, Copia will render the entire file, and highlight the differences.
Rung Commenting for Code Review
Copia supports rung commenting for Beckhoff TwinCAT 3 for both Ladder and Structured Text.
Rung Commenting enhances the Code Review process once someone generates a Pull Request to merge a Branch. During the review process, users can add comments directly to the supported parts of the code.
You can watch an overview of rung commenting in the video below.
The product version in the video may be older than the current release, but the process is still applicable.
Last updated