Rockwell Logix Designer
Last updated
Last updated
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 (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.
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 and FactoryTalk Linx.
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 on the Agent, and (without any project open) choose the correct version, based on the menu options shown.
Copia strongly recommends the use of RSLinx Classic on the agent (instead of FactoryTalk Linx). Please consult the FactoryTalk Linx Considerationsbefore moving forward with the use of FactoryTalk Linx.
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.
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 (Repo/Branch) that the project is, or will be 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 allows you to update the Project name, and description if desired.
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 seen.
Fill in all required field, and any fields that are applicable. The Name would often be that same name as the Project for Rockwell, to maintain the 1-to-1 relationship.
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 is the recommended Communication Software for use with the Copia Agent.
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.
Once you browse down to the device in the Linx browser, you should be able to view the full device Communication Path.
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
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.
If you have configured your agent to use RSLinx Classic as recommended, you will enter the full communication path here. If you are using FactoryTalk Linx, you can leave the Communication Path field here empty. Press Save Device when complete.
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.
Once complete, press Submit Project Setup 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.
Copia recommends the use of RSLinx Classic on the agent over FactoryTalk Linx. However, it is still possible to use FactoryTalk Linx, albeit with some additional requirements. Instructions on configuring devices for FactoryTalk can be found in .
{Redacted_Driver_Name}/10.23.37.6/PointBus/0
