Rockwell Studio/RSLogix 5000

Agent Requirements

Below are the Agent system requirements to configure a Copia Agent for the backup of Rockwell Logix Designer projects:

• You will need a licensed copy of Rockwell Studio 5000 Logix Designer or RSLogix 5000 (see supported versions) that is capable of backing up the entire Project from a Device, which typically equates to Service Edition, Standard Edition, or higher. Refer to the Rockwell documentation to ensure that the version installed is adequate for this purpose, based on your local usage requirements.

  • If there are many versions of a Project that will be managed by the Agent, each version should be installed.

  • NOTE: A Professional Edition license is required if using FactoryTalk Linx. See FactoryTalk Linx Configuration for more information. (including the .NET 8 (x86) runtime, which is normally installed alongside Studio 5000, but this should be confirmed)

• In addition, any additional vendor software must be licensed and installed on PC running the Copia Agent. (i.e. EDS files, Add-on's etc.)

• Copia recommends starting RSLinx as a service from the RSLinx Classic Launch Control Panel:

• The Agent should be tested to confirm that it can backup the PLC using the vendor software.

  • Please refer to the Rockwell documentation regarding port requirements for communication requirements for RSLinx Classic.

• Studio 5000 must be configured to use the appropriate communication software for the devices the Agent will back up. You can set this by opening Studio 5000 Logix Designer or RSLogix 5000 on the Agent machine, and (without any project open) choose the correct version, based on the menu options shown.

Screenshot showing how to select the communication software in Studio 5000

New Project Configuration

To configure a project for Rockwell Logix Designer, you will need to already have a repository created with the Rockwell .acd file.

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

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 Agents section of the documentation.

When complete, press Save and Continue.

You will now select the Project Path, which is the location (Repository/Branch) where the project file is stored.

You can edit the previous steps at any time.

You will only be allowed to select the appropriate filetype or folder that is allowed for the Project Type. In some cases, a project is required to perform a backup, in other cases, the backup can create the initial backup into an empty project folder.

Once selected, press Save and Continue to proceed.

The Project Details section allows you to set the Project name and add a description if desired.

Define the Device(s)

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

We support systems configured with RSLinx Classic and FactoryTalk Linx. It is recommended that you configure the device in Copia setup to match the communication software setup in Studio 5000 Logix Designer IDE.

Fill in all required fields and any additional fields that are applicable. For the "Device Name" field, it is suggested to use the same name as the Project.

DeviceLink requires configuration of the Communication Path in both the agent and the web application.

This on-agent configuration has to be performed for every device you wish to back up. You will need to use the Linx software to browse down to each device.

RSLinx Classic Configuration

First, you must use the RSLinx Classic utility on the agent to browse down to the slot associated with each device you wish to back up.

This can be done via the "Who Active" dialog inside Studio 5000 (pictured below) or the RSLinx Classic application.

The "Who Active" dialog box can be found under the "Communications" menu.

Once you browse down to the device in the Linx browser, you should be able to view the full device Communication Path.

In this example, the full communication path would be {Redacted_Driver_Name}/10.23.37.6/PointBus/0

This path must be entered in the Communication Path field in the web application. You must use the fully qualified communication path including the communication bus (e.g. Backplane, PointBus, CompactBus, etc.). This is typically in the form of: drivername\ipaddress\commbus\slotno. Note that the name of the communication bus is case-sensitive. For example:

• AB-ETHIP-1\192.168.1.21\Backplane\0

• AB-ETHIP-1\192.168.1.21\CompactBus\0

• AB-ETHIP-1\192.168.1.21\PointBus\0

RSLinx Classic cannot back up devices when the communication path routes through a parent device Unsupported example: PLC_1\192.168.1.1\Backplane\2\A\192.168.1.3\CompactBus\0

If your device is networked in this type of configuration, you have two options:

1. Adjust the network layout and communication path so that the RSLinx Classic path does not route through a parent device, or

2. Switch the device configuration to FactoryTalk Linx, which can support routed communication paths and is not subject to this RSLinx limitation.

After successfully backing up all of the devices linked to a given agent, Copia recommends copying your RSLinx configuration. This way, if RSLinx gets corrupted, you can restore the configuration without manually re-browsing to each device. Your RSLinx configuration is created via the "RSLinx Classic Backup and Restore Utility" installed along with RSLinx. You can manually upload this configuration file to your Copia repository to keep it in the Cloud.

Ensuring Correct Communication Software

Note: In the latest Agent versions this setting is applied automatically. The Agent updates the configuration file based on the communication software selected in the web UI. However it’s still a good idea to double check the setting in Studio 5000 especially when troubleshooting or verifying backup connectivity.

Studio 5000 must be configured to use RSLinx as the communication software for the devices the Agent will back up. You can set this by opening Studio 5000 Logix Designer on the Agent machine (without any project open).

To confirm the correct communication software:

• Open Studio 5000

• Navigate to Communications → Select Communication Software → RSLinx

This ensures the Agent can detect the PLC communication path and perform backups successfully.

Example shown below:

Web UI

If you have configured your agent to use RSLinx Classic, you will enter the full communication path here. Select "RSLinx Classic" communication software radio button and finally press Save Device when complete.

Define the Job(s)

Creating Jobs is similar for all vendor types, and is described in the Creating Jobs 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.

Submit the Configuration

Once complete, press "Submit Project Setup" at the bottom of the form to create the Project, Device(s) and Job(s).

FactoryTalk Linx Configuration

Important: The Logix Designer SDK is not installed automatically with Studio 5000. To enable FactoryTalk Linx backup support, you must install Studio 5000 using the Customize option and explicitly select the Logix Designer SDK component.

Device Agent supports backing up PLC projects configured to use FactoryTalk Linx as the communication software. The Agent utilizes Rockwell’s Logix Designer SDK; therefore, Studio 5000 Logix Designer v31 or newer with a valid Professional Edition License is required for FactoryTalk Linx–based backups. If the SDK is not installed, FactoryTalk Linx backups will fail.

Installing the Logix Designer SDK

If the SDK is missing, or if you need to add it to an existing Studio 5000 installation follow these steps:

1. Launch the installer: Run setup.exe from your Studio 5000 installation media or downloaded installer.

2. Choose “Customize”: When the installer opens, select Customize instead of Install Now.

3. Navigate components: Proceed through the initial screens (user information, license agreement, etc.).

4. Select Optional Tools / Features: Continue until you reach the page allowing selection of optional features.

5. Enable the SDK: Check the box for Logix Designer SDK (or similar wording).

6. Complete the installation: Click Next and finish the setup. A reboot may be required.

Verify That the SDK Is Installed

On the Agent system:

1. Open Services.msc

2. Locate the service LDSDKService

3. Confirm that the service is present and its status is Running

If the service is missing, the SDK was not installed and you must re-run the installer using the steps above.

Also, please ensure that the .NET 8 (x86) runtime, which is normally installed alongside Studio 5000, was installed, as well. If not, see this link to add it.

Browsing the Device in FactoryTalk Linx Network Browser

After verifying SDK installation, open the FactoryTalk Linx Network Browser on the Agent system and browse to the device you want to back up, as shown in the example below:

This path must be entered in the Communication Path field in the web application. Some examples can be found below:

• AB_ETH-1\10.41.2.208

• AB_ETH-1\10.41.2.208\A2\10.41.4.209

• AB_ETH-1\10.41.2.208\A2\10.41.4.209\PointBus\0

Ensuring Correct Communication Software

Note: This setting is applied automatically in the latest Agent versions. The Agent updates the configuration file based on the communication software selected in the Copia Web App. However, we still recommend double checking the setting in Studio 5000, especially when troubleshooting or verifying backup connectivity.

Studio 5000 must be configured to use FactoryTalk Linx as the communication software for the devices the Agent will back up. You can set this by opening Studio 5000 Logix Designer on the Agent machine (without any project open).

To confirm the correct communication software:

• Open Studio 5000

• Navigate to Communications → Select Communication Software → FactoryTalk Linx

This ensures the Agent can detect the PLC communication path and perform backups successfully.

Example shown below:

Web UI

Configure the project as given in the project setup above. When configuring the Device, enter the appropriate Communication Path and select FactoryTalk Linx from the radio button as seen in the image below:

Proceed with the Job Setup as see below:

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

Troubleshooting FactoryTalk Linx Backup Errors

Resolving FactoryTalk Linx “No Valid License” Backup Error

When performing backups using FactoryTalk Linx, Studio 5000 Logix Designer requires a Professional Edition license to successfully execute the Logix Designer SDK. In most cases, Rockwell automatically provides a 7-day trial license, but this temporary license does not appear in FactoryTalk Activation Manager, which can lead to confusion when diagnosing backup failures.

However, you may still encounter the following error even with an active Professional license: no valid license

Rockwell has identified this as a licensing entitlement issue within the Logix Designer SDK. According to the official Rockwell knowledge base article (ID: BF29224) Resolution:

• Ensure the license is activated using entitlement version 35.00.01, which is required for the Logix Designer SDK to function.

• If the license is already activated under a different entitlement version, re-host the license and reactivate it, selecting entitlement 35.00.01 during activation.

• A valid Professional Edition license is required.

Missing .NET Backup Error

FactoryTalk Linx backups require the .NET 8 (x86) runtime, which is normally installed alongside Studio 5000. However, we have observed cases where this dependency was not installed, resulting in backup failures.

A missing .NET runtime produces error output similar to:

You must install .NET to run this application. Architecture: x86

Resolution:

If you encounter this message:

• Install the required .NET 8 x86 Runtime as administrator using the link provided in the error output: https://aka.ms/dotnet-core-applaunch?missing_runtime=true&arch=x86&rid=win-x86&os=win10&apphost_version=8.0.6

• After installation, retry the backup .

This dependency is essential for the FTLinxCLI used by the Device Agent during FactoryTalk Linx SDK backups.