Search…
Rockwell

Overview

Copia supports the following Rockwell software/versions, and advanced functions:

Rockwell Studio 5000 Logix Designer v28-v34

Configuration

The default file format for Logix Designer is .ACD, which is supported by Copia. Alternatively, the .L5X format can be used, which may decrease file conversion times for display and compare operations.
If a project has source protection, encrypted AOI's, or other protected data, the L5X must be generated and stored, versus the ACD. Options for disabling "Always Encode Source Protected Content on Export" can be found in the Rockwell documentation.
Save your project file (either ACD or L5X) to the repository folder is all you need to do prior to following the Commit and Push operations, to store it on the Copia system.

Things to Consider

If using the Merge operation, Copia will require all necessary AOP and EDS files to be installed on the Copia server. More information is provided in the Advanced Merging section.
In addition, You may want to disable the auto-project backup option, if you are working directly in the repository, as this may create additional BAK files which may not be desired.

Graphical Display and Differences

Copia will display the project graphically, in a similar manner to the Rockwell IDE, for easy navigation and to quickly identify differences. The following types are supported in the graphical output at this time:
  • Ladder (LAD)
  • Function Block Diagram (FBD)
  • Structured Text (ST)
  • Add-On Instructions (AOI)
    • Source-protected and locked Add-On Instruction content require an L5X, as an ACD will require permissions to unlock
  • Datatypes
  • Modules
  • Programs
  • Tag Lists
Function Block Diagram (FBD) is a new feature, currently available for testing and feedback
An example of the output in the desktop app is provided below:

Additional Settings

Additional settings are provided for the visual display and differences.
  • View Options
    • Show Unmodified Items
      • This setting affects the tree view, and if enabled will display the items that are not modified
    • Hide System Data Types
      • This applies only to system data types
  • Ignore tag value changes
    • This lets you disregard all tag value changes
  • Hide unchanged tags
    • This applies to unmodified datatype and tag values
  • Hide unchanged rungs
    • This applies to logic rungs that have not changed
  • View XML diff
    • This displays the difference in a direct XML text-based compare

Rung Commenting

Rung Commenting enhances the Code Review process, once a Pull Request to merge a New Branch into the Main (or default/master) Branch has been generated.
The Rung Commenting process is explained clearly in the video linked below.
NOTE: The product version in the video may be older than the current release, but the process is still applicable

Advanced Merging

Copia provides the standard Git-based approach to merging branches and conflicts for all changes but adds advanced merge capabilities for Logix Designer.
During the Merge operation, the process will require all necessary AOP and EDS files on the Copia server to perform the operation. If missing, a dialog will appear with instructions on how to resolve the issue and provide the required data.
A description of the workflow for Advanced Merging for Logix Designer is in the video below. In addition to the video, it should be noted that the merge tool has the following limitations:
  • Logic merge is at the Routine level, and not Rung level
    • When merging logic changes, you cannot merge 2 different rungs changed within the same routine. Merge is only capable at the routine level.
  • Tag changes are not individually selectable during the merge operation.
    • You can select the changes from one branch only. As a result, if tag changes are present in both branches, we recommend selecting the tags from one branch, and then after merge, re-applying the tag modifications manually in Logix Designer from the other branch.
NOTE: It is NOT recommended to merge projects of differing versions. If necessary, during a merge of two Studio 5000 projects with different version numbers, the resulting project after the two branches have been merged will be the version of the branch that is being merged into.
NOTE: The product version in the video above may be older than the current release, but the process is still applicable
Last modified 1mo ago