FactoryTalk Linx Considerations

Requirements for use of FactoryTalk Linx with DeviceLink

The Copia Agent can perform backups with FactoryTalk Linx as the selected Communication Software on the agent. However, "under the hood" the Agent still depends on RSLinx Classic for some aspects of the backup. As such, this configuration requires additional configuration:

• RSLinx Classic must be installed on the agent in addition to FactoryTalk Linx.

• A driver must be configured in RSLinx Classic with the same name as the one in the device's Communication Path.

  • For example, if the device's Communication Path is stored in the project file as AB_ETHIP-1\10.10.10.10\Backplane\0 and an Ethernet/IP driver named AB_ETHIP-1 is configured in FactoryTalk Linx, you must ensure that an Ethernet/IP driver named AB_ETHIP-1is also configured in RSLinx Classic.

Configuring Devices with FactoryTalk Linx

Before configuring a device for use with FactoryTalk Linx, you must ensure your agent meets all of the Requirements for use of FactoryTalk Linx with DeviceLink .

Once you meet these requirements, you must use the FactoryTalk Linx network browser to browse down to the specific slot associated with the device you wish to back up.

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

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

If using FactoryTalk Linx, you must configure the Communication Path in the project file in Copia Source Control (at the bottom of the RSWho dialog in Logix Designer, see below). If you do not have a path set in the project file, you can do so by navigating to the controller, using the button to Set Project Path, and committing this change back to the branch and repository associated with the DeviceLink Project.

The "Who Active" Dialog, with the "Set Project Path" button and Comm Path highlighted.