RSLogix 5000


Copia provides support for Rockwell RSLogix 5000 v16-v20, with advanced feature support for the following:



Copia supports Rockwell files, with .ACD as the standard working file format. You can alternatively use .L5X, which may decrease file conversion times.
To get set up, simply store the file in 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.

Extra Considerations

If you want to use the Advanced Merge for Conflict Resolution, Copia will require all necessary Add-On Profiles and .EDS files to be installed on the Copia server. More information can be found in the Advanced Merging section.
We recommend that you disable the Automatic Project Backup option if you are working directly in the repository, as this may create additional .BAK files.

Graphical Display and Differences


When the exported 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 the Rockwell IDE. This way, you can easily navigate to a project item or identify differences.

Supported Types

The following types are currently supported for graphical output:
  • Ladder (LAD)
  • Function Block Diagram (FBD)
  • Structured Text (ST)
  • Add-On Instructions (AOI)
  • Datatypes
  • Modules
  • Programs
  • Tag Lists
To display the logic and changes to encrypted or encoded data, source protection must be removed, otherwise these items will appear as inaccessible. This does not apply to Safety Locked code, which is accessible for display.

View Options

There are several options you can manage while viewing your Rockwell files in Copia.
  • 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 Source Protected Items
    If source protected items are not exposed, they will be assumed to be different. In those cases, you can toggle them to be ignored, if desired.
  • Ignore tag value changes
    This lets you disregard all tag value changes
  • Show unmodified tags
    This applies to unmodified datatype and tag values
  • Hide unchanged rungs
    This applies to logic rungs that have not changed
  • Show XML
    This displays the difference in a direct XML text-based compare
The View Options dropdown on the left affects items in the project tree, while the one on the right controls more specific viewing settings for items that are in a focus state.

Rung Commenting for Code Review

Copia supports rung commenting for Rockwell files 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.

Advanced Merging for Conflict Resolution

While Copia provides the standard Git-based approach to merging branches and conflict resolution, it offers advanced merging capabilities for Rockwell RSLogix 5000 v20 files.
The Advanced Merge tool will convert programs of any prior version to v20. As such, it is not recommended, nor supported, to perform the merge operation using projects made in versions prior to v20!
Currently, the Advanced Merge tool has the following limitations:
  • All Add-On Profiles and .EDS files are required The Advanced Merging process will require all necessary AOPs 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.
  • Logic merge is at the Routine level, and not Rung level
    When merging logic changes, you cannot merge two different rungs changed within the same routine. Advanced merging 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.
  • Safety Locks must be reapplied The merge process for Rockwell utilizes the L5X project format. As a result, the Safety Lock's which have been applied to a project will no longer exist after merge. Based on this, Copia recommends that you either cancel and manually merge, or continue while making sure to re-enable the Safety Lock upon completion.
You can watch an overview on merging in the video below.
The product version in the video may be older than the current release, but the process is still applicable.