Rockwell Studio/RSLogix 5000
Agent Requirements
Below are the Agent system requirements to configure a Copia Agent for the backup of Rockwell Logix Designer or RSLogix projects:
If you choose to run the Copia Device Agent as a Service, it must be run by a user account, and not the Local System account. FactoryTalk activation needs a Windows user accounts, not machine accounts such as Local System.
See how to configure this in the "FactoryTalk Services Platform connection Error" of the troubleshooting section below
Make sure to perform a manual backup(s) of the device(s) using Studio 5000 Logix Designer / RSLogix 5000 directly on the Agent machine to confirm connectivity and the ability to process uploaded files.
Important: If using FactoryTalk Linx, Studio 5000 Logix Designer can use a different license for uploading PLC files than the Copia Agent will use - see "Communication Software and Licensing" below.
Rockwell Requirements
Logix Software and Licensing
You will need a licensed copy of Rockwell Studio 5000 Logix Designer or RSLogix 5000 (see supported versions)
Note: If the Agent will be managing multiple versions of a project, each corresponding version of Studio 5000 or RSLogix must be installed on the machine.
Communication Software and Licensing
Rockwell FactoryTalk Linx is supported for v31 and later. This requires Service Edition or Professional Edition, and must be installed with the Rockwell Logix SDK v2.02 option enabled.
The Logix SDK v2.02 also requires Microsoft .NET 10 (x86) runtime
NOTE: PLC's connected though another PLC require FactoryTalk Linx.
Rockwell RSLinx Classic is supported for version up to v37, and requires a version capable of backing up the project, such as Service Edition, Standard Edition, or higher.
RSLinx must be run as a service from the RSLinx Classic Launch Control Panel:
Please refer to the Rockwell documentation for FactoryTalk Linx or RSLinx Classic communication port requirements
Important: Certain individual models are not supported by RSLinx Classic. Currently Copia is aware of the following incompatibilities:
5069-L320ERMS2 (Compact GuardLogix SIL2 2.0/1.0M Motion)
5069-L320ERS2 (Compact GuardLogix SI2 2.0/1.0M)
5069-L330ERMS2 (Compact GuardLogix SIL2 3.0/1.0M Motion)
5069-L330ERS2 (Compact GuardLogix SI2 3.0/1.0M)
1756‑L902TS (ControlLogix 5590 with Safety, 2 MB Memory)
1756-L905TS (ControlLogix 5590 with Safety, 5MB user memory)
1756-L908TS (ControlLogix 5590 with Safety, 8MB user memory)
1756-L83EP (ControlLogix, 5580 10MB user memory)
Additionally, any PLC which is connected through another PLC is not supported by DeviceLink's usage of RSLinx Classic.
For these circumstances, FactoryTalk Linx must be used. See details in Device Configuration below.
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 an ACD or L5X file during this step. 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.
Device Configuration
Define the Device(s)
The Device Setup section is for defining the device information (PLC, communication path, and communication software) that is in your Project. If you have pre-created devices you can add them; otherwise you can Add a Device as shown.
If a Communication Path is not configured in the Device, DeviceLink will attempt to use the Communication Path saved in the PLC Project file. In either case, it must contain a Driver configured in RSLinx or FactoryTalk Linx on the Agent machine.
For the "Device Name" field, it is suggested to use the same name as the Project.
RSLinx Classic - Communication Path
First, you must use the RSLinx Classic utility on the Agent machine 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.
Once you browse down to the device in the Linx browser, you should be able to view the full device Communication Path.
{Redacted_Driver_Name}/10.23.37.6/PointBus/0This 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\0AB-ETHIP-1\192.168.1.21\CompactBus\0AB-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:
Adjust the network layout and communication path so that the RSLinx Classic path does not route through a parent device, or
Switch the device configuration to FactoryTalk Linx, which can support routed communication paths and is not subject to this RSLinx limitation.
Once you have entered the correct Communication Path, make sure you have selected "RSLinx Classic" communication software radio button and then press Save Device when complete.
Please remember to configure RSLinx Classic to run as a Service, as mentioned in the Rockwell Requirements above!
FactoryTalk Linx - Communication Path
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.
The Copia Device Agent supports backing up PLC projects configured to use FactoryTalk Linx as the communication software. The Logix Designer SDK entitlement must be visible in FactoryTalk Activation Manager. If the SDK is not installed or the SDK entitlement is not present, FactoryTalk Linx–based backups will fail.
Installing the Logix Designer SDK
Users should install the latest version of the Logix Designer SDK, which can be found as a standalone download from the Rockwell Compatibility & Downloads Center.
If using the latest verion of Studio 5000, the SDK may be installed using the Studio 5000 (Service or Professional Edition) Install, as a custom option. See below:
If the SDK is missing, or if you need to add it to an existing Studio 5000 installation follow these steps:
Launch the installer: Run
setup.exefrom your Studio 5000 installation media or downloaded installer.Choose “Customize”: When the installer opens, select Customize instead of Install Now.
Navigate components: Proceed through the initial screens (user information, license agreement, etc.).
Select Optional Tools / Features: Continue until you reach the page allowing selection of optional features.
Enable the SDK: Check the box for Logix Designer SDK (or similar wording).
Complete the installation: Click Next and finish the setup. A reboot may be required.
Verify That the SDK Is Installed
On the Agent system:
Open Services.msc
Locate the service LDSDKService
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 10 runtime is installed. 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.208AB_ETH-1\10.41.2.208\A2\10.41.4.209AB_ETH-1\10.41.2.208\A2\10.41.4.209\PointBus\0
Enter the appropriate Communication Path and select FactoryTalk Linx from the radio button as seen in the image below:
Job Configuration
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).
Don't forget to enable/disable the Watch button based on your preferences for project Notifications.
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.
Troubleshooting FactoryTalk Linx Backup Errors
FactoryTalk Linx “No Valid License” Backup Error
When performing backups using FactoryTalk Linx, Studio 5000 Logix Designer must be licensed for use with the Logix Designer SDK. See more in the Rockwell Requirements section.
Rockwell automatically provides a temporary 7-day trial license. This trial license does not appear in FactoryTalk Activation Manager, which can make diagnosing backup failures confusing. Resolution:
Ensure the Logix SDK is installed, not a trial, and the entitlement is present, visible and active in FactoryTalk Activation Manager. (as seen here)
Ensure the Service Edition or Professional license is under current Rockwell Support
Ensure the Service Edition or Professional license is activated using CodeMeter, and not as Flexnet
If using a License Server, ensure the license entitlement provided for the Agent is always a Service Edition or Professional version (it is recommended to dedicate a license if there is a possibility it is given an unsupported version from the license server)
FactoryTalk Services Platform connection Error
If you are running the Copia Agent as a Service, and it fails to run due to a FactoryTalk connection error such as:
An unknown error has occurred. at RockwellAutomation.LogixDesigner.FTSP.FactoryTalkServicesPlatformLogin
It is likely due to the the Agent being run by the Local System account, and not a Windows User account. FactoryTalk permissions are assigned to Windows-linked user accounts, not machine accounts, so the FactoryTalk CLI cannot proceed. This can be changed, as seen below:
Open Services
Right-click CopiaAgentService
Open Properties > Log On
Click browse
Enter a Windows user account that has FactoryTalk permissions
Click Check Names
Click OK
Enter account password and apply these changes.
Right click the CopiaAgentService and click Restart
Follow the same steps above but for Logix Designer SDK Service, as well.
Update it to log on as the same account as the CopiaAgentService.
Ensure to restart the Logix Designer SDK Service afterwards.
Be sure to enter a Windows user account that has the required FactoryTalk perms. This may be an Administrator account in some environments, but the key requirement is that FactoryTalk recognizes the account and it is included in a FactoryTalk permissions group. The Local System / machine account is not listed, which is why it does not have the required FactoryTalk permissions.
Finally, verify the Windows user has FactoryTalk permissions. They should be included in the Groups listed below:
Open FactoryTalk Administration Console
Select Network from the popup
Open User Groups, then check Authenticated Users or Windows Administrators.
Missing .NET Backup Error
FactoryTalk Linx backups require the .NET 10 runtime when using the SDK v2.02 (.NET 8 Runtime, when using SDK v2.01), 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 Runtime as administrator using the link provided in the error output:
After installation, retry the backup .
This dependency is essential for the Copia Agent during FactoryTalk Linx SDK backups.
Last updated
Was this helpful?