Home › Technical articles

Đọc bằng tiếng Việt

Logix program version control and backup: ACD, L5X, Compare and Merge Tool, Git, AssetCentre

TDL Industrial Automation · Last updated:

From the Logix Designer 37.00 help, LDCT-UM001H, LOGIX-AT003B, LDSDK-GR001D, the AssetCentre 16.00.00 help and the FactoryTalk Vault help: ACD, L5K and L5X files, the Compare Tool and Merge Tool, Git through the VCS Custom Tools and Logix Designer SDK, FactoryTalk Vault, AssetCentre Backup and Compare, and what to keep with each version.

A Studio 5000 Logix Designer project is saved as a binary .ACD file, and Logix Designer can also write the same project as text: an .L5K file (ASCII) or an .L5X file (XML). Rockwell Automation's tools for version control work on those files: the Logix Designer Compare Tool and Merge Tool, Backup and Compare in FactoryTalk AssetCentre, Git through the Logix Designer SDK, and FactoryTalk Vault in the cloud. AssetCentre set-up and ports are covered in FactoryTalk AssetCentre: automatic backup.

The version loop of a Logix projectFour steps joined in a clockwise loop. One, upload or export: upload into the ACD file that matches the controller, Save As an L5X or L5K file, or l5xgit commit to take the ACD to L5X and into Git. Two, compare: the Compare Tool compares ACD, L5K and L5X files from version 17, AssetCentre runs Backup and Compare against the master, or an online compare with certain controllers on firmware 34 or later. Three, store: a new version in the AssetCentre Archive, a commit and tag in Git, or the FactoryTalk Vault History. Four, restore: open the stored ACD, l5xgit restoreacd with Logix Designer closed, then download with the same major revision as the firmware. Then back to step one. Based on the Logix Designer 37.00 help, LDCT-UM001H, LOGIX-AT003B, the AssetCentre 16.00.00 help, the FactoryTalk Vault help and 1756-UM543.The version loop of a Logix projectupload into the ACD that matchesthe controllerSave As an .L5X or .L5K filel5xgit commit: ACD to L5X, theninto GitCompare Tool: ACD, L5K, L5Xfrom version 17AssetCentre: Backup and Compareagainst the masteronline: certain controllers onfirmware 34 or later1 · Upload or exportget the program out2 · Comparefind what changedAssetCentre: new version inthe ArchiveGit: commit, tag for a releaseFactoryTalk Vault: History and notesopen the stored ACDl5xgit restoreacd, Logix Designerclosed firstdownload: same major revision asthe firmware3 · Storekeep every version4 · Restorebring a stored version backBased on Rockwell Automation: Logix Designer 37.00 help, LDCT-UM001H, LOGIX-AT003B,AssetCentre 16.00.00 help, FactoryTalk Vault help, 1756-UM543 (read 15 November 2026).Figure: drawn by TDL.
Figure 1: The version loop of a Logix project. On a phone, swipe sideways to see the whole figure.

1. The project file and its two text formats

The Save As dialog in Logix Designer (help version 37.00) offers three file types:

File type What the help says
.ACD – Logix Designer Project File The normal project file
.L5K – Import-Export File An ASCII representation of the entire project; importing it creates a new project or overwrites an existing one; the extension must stay .L5K
.L5X – Import-Export File XML, readable in a text editor; holds a whole project or selected components

Selected components can go out as L5X on their own: rungs, routines, programs and equipment phases, user-defined data types, Add-On Instructions, trends, tag-based alarms and modules. The export brings along the referenced components that an import will need.

Three details matter for backups:

  • Online export. Logix Designer asks whether to upload tag values, so current values go into the file only by choice. Force masks are exported; the Forces Enabled state is not.
  • Protected content. With Encode Protected Content selected, source-protected content is exported encrypted; cleared, as clear text.
  • Comments live on disk. The help topic About Upload says rung comments and descriptions are not stored in the controller. They stay in the offline project file and are merged in during an upload, and the help says to upload only into a matching project file: one downloaded to or uploaded from that controller, or a copy of it. An upload is no substitute for the stored ACD.

2. Comparing and merging: the Compare Tool and the Merge Tool

The Logix Designer Compare Tool User Manual, LDCT-UM001H (September 2024, Compare Tool version 11.00.00), describes a standalone program that also starts from Logix Designer's Compare Tool command or from the command prompt as RSLCompare. Rockwell's Product Compatibility and Download Center lists the product as the Logix Designer Compare and Merge Tool.

What it compares (p. 9, 23):

  • ACD, L5K and L5X project files of version 17 or later, in any mix;
  • partial L5X files that hold components of one type;
  • a project file against a running controller: certain ControlLogix 5580, GuardLogix 5580, CompactLogix 5380 and 5480 and Compact GuardLogix 5380 models with firmware 34 or later, which needs Logix Designer 34.00.00 or later and FactoryTalk Linx 6.30.00 or later.

The Compare Summary lists only the items that differ (p. 37): red for an item that exists in one file only, blue for a common item that differs, black for a common parent, gray for no difference. A report can be printed, sent to PDF through Microsoft Print to PDF, or saved as XML (p. 9, 20), and a result can be stored as a .compare file (p. 25–26). Encrypted Add-On Instructions and routines are compared only by their hash (p. 38). Command-line use needs the Compare: Execute permission (p. 24–25).

The Logix Designer Merge Tool, in the same manual, starts from File > New > Project Merge or from the Compare Tool (p. 73). It merges two or three project files:

Merge Files What the manual says
Two-way Left (base) and right The right is merged into the left; the tool cannot tell added from removed content and treats it as added (p. 73, 88)
Three-way Left (base), center (original), right An Original Content file is added in the center (p. 73)

Conflicts show as unresolved items in blue and must be resolved by hand before saving (p. 74, 91). The result is saved as ACD, L5K or L5X. All files must be version 17 or later, and the left file's version must be equal to or higher than the others (p. 74). Pending and test edits are removed from the result, signed or protected Add-On Instructions merge only as a whole, and Instanced Library Objects cannot be merged (p. 73, 92).

3. Git with the Logix Designer SDK

Rockwell's application technique LOGIX-AT003B (October 2026), Distributed Version Control for Studio 5000 Logix Designer Control Systems using Git Integration, starts from the point that ACD files are binary: for Git, the project has to be in L5X form (p. 22). Its route is the Studio 5000 Logix Designer VCS Custom Tools on Rockwell's public GitHub, a set of .NET 8.0 command-line utilities (p. 25):

  • l5xplode breaks an L5X into a folder of XML and text files and rebuilds it;
  • l5xgit adds the ACD steps: commit exports the ACD to a temporary L5X, explodes it into the local repository and deletes the temporary file; restoreacd rebuilds the L5X and imports it into the ACD, and it fails if the project is open in Logix Designer; difftool shows the latest commit against the previous one in WinMerge (p. 26).

The document treats the main branch as the source of truth (p. 14) and, in its CI/CD section, tags releases with semantic version numbers for traceability and rollback (p. 33). Rockwell's Logix Designer product page adds that Git workflows are supported through examples and community collaboration only.

Underneath is the Logix Designer SDK. Its Getting Results Guide, LDSDK-GR001D (March 2026), gives C# from SDK 2.00 and Python from 2.01 (p. 8); projects of Logix Designer version 31 and later, with older projects only convertible; a 64-bit OS; FactoryTalk Linx, not RSLinx (p. 7). A program can open a project and save or export it as ACD, L5K or L5X, also as a partial L5X (p. 28); one example commits a project file to version control for automated testing (p. 17).

4. FactoryTalk Vault

The FactoryTalk Vault help calls Vault the secure storage provided with FactoryTalk Hub, for collaboration, backup and recovery and version control of automation projects. It accepts Logix Designer projects as .ACD, .L5X and .L5K and needs a verified MyRockwell account. Each upload can carry a note; the History tab of a project shows its file history, and a project can be reverted to a previous version. Its release notes add a tool that compares code with previous revisions (August 2023) and Logix Designer v38 support in release 6.3.00 (October 2025). Vault can upgrade a project to a later Logix version but never downgrade it. The help warns that outside North and South America uploads and downloads can be slower, because not all FactoryTalk Hub services are deployed in every region.

5. Scheduled backup on the plant network: AssetCentre

In FactoryTalk AssetCentre (help 16.00.00), a Logix 5000 controller is a Configuration Data asset: its master files sit in the Archive under version control, and each schedule names the version used as master. A Backup schedule uploads and stores the result as a new version. A Backup and Compare schedule compares the upload with the master, and what is saved next depends on the result and on the Promote New Upload to Master setting. LDCT-UM001H says AssetCentre performs these comparisons with the Logix Designer Compare Tool (p. 9). Asset tree, agents and ports: AssetCentre article.

6. What to keep with each version

The ControlLogix 5580 user manual, 1756-UM543 (online edition, superseding 1756-UM543S-EN-P), requires controller firmware and Logix Designer of the same major revision: firmware 38.xxx goes with Logix Designer version 38. Logix Designer's Change Revision dialog offers only installed major revisions higher than the current one, and it keeps the original project with the old version in the file name, for example test_project.acd_v10. Each stored version therefore needs, next to the ACD, the Logix Designer version it was saved with and the controller firmware revision. Which software opens which controller: RSLogix 5000 and Studio 5000 versions; changing the firmware itself: Logix firmware update.

What we check first

This is TDL's practice, not a Rockwell requirement.

  • Before any change we upload from the running controller into a copy of the plant's latest file and compare the two, so we know which program is real.
  • We keep the ACD as the master, because comments and descriptions live there, and an L5X next to it for reading differences.
  • We record catalog number, firmware revision and Logix Designer version with every stored version.
  • We ask who holds the source keys: protected and encrypted content is compared only by hash.
  • In AssetCentre we agree with the plant which version is the master and whether a new upload is promoted to master.
  • We test a restore: open the stored version in the matching Logix Designer version and check that it verifies.
  • Git with the VCS Custom Tools stays on the engineering side; the plant's backup does not depend on it, since Rockwell supports it through examples and the community.

Backup and version control at TDL

TDL Industrial Automation is a System Integrator in the Rockwell Automation PartnerNetwork. At P&G Vietnam's Dong An plant we set up FactoryTalk AssetCentre in two stages, first for LFE making and then for the packing lines: scheduled automatic backups of PLC and HMI programs with version history, an audit trail of program changes, user access control and a recovery procedure from the archived versions. Without AssetCentre, our scheduled, versioned backup package compares each upload with the last archived copy. More: PLC and HMI backup and version control, Rockwell PLC security.

Frequently asked questions

What is the difference between ACD, L5K and L5X files?

ACD is the normal Logix Designer project file and is binary. L5K is an ASCII representation of a whole project, and L5X is XML that can hold a whole project or selected components such as routines, programs, data types and Add-On Instructions.

Can Logix Designer projects be stored in Git?

Yes, as L5X. Rockwell's LOGIX-AT003B describes the VCS Custom Tools, which export the ACD to L5X, split it into text files for Git and rebuild the ACD on restore. Rockwell's product page says these Git workflows are supported through examples and community collaboration only.

How do I compare two versions of a ControlLogix program?

With the Logix Designer Compare Tool, which compares ACD, L5K and L5X files of version 17 or later and lists only what differs. Certain ControlLogix 5580 and CompactLogix 5380 controllers with firmware 34 or later can also be compared online against a project file.

Can I merge two Logix Designer projects?

Yes, with the Logix Designer Merge Tool: two-way, or three-way with an original file in the center. Conflicts must be resolved by hand, and the left file's version must be equal to or higher than the others.

Why does an uploaded program have no rung comments?

Rung comments and descriptions are stored in the offline project file, not in the controller. Upload merges them from a matching project file, so the stored ACD is needed.

Sources

Read 15 November 2026. This article paraphrases the sources and does not quote them; read the original documents before designing or working on a system.

Related services:
Rockwell Automation (Allen-Bradley) PLC backup and version control