Page History

ControlLogix 5000

, FlexLogic and CompactLogix

On This Page:

Configuration Workflow

This document has only the specific information about the protocol connection settings and its address syntax.
→ Go To Data Connection models, for information on the configuration options. 

• UNS LocalTags + Devices

1. Create  local tags
2. On Devices, create the Channel, Node, and map the Tag to a an address
3. Alternatively with the Import Wizard for automated creation. 

• UNS LocalTags + Devices

1. Create  local tags
2. On Devices, create the Channel, Node, and map the Tag to a an address
3. Alternatively with the Import Wizard for automated creation

1. .

This document has only information about the specific information about the device connection settings and its address syntax.

Refer to the User Guide for more information on the Device Module or on UNS TagProvider Connections.

For further Information, see:

• • Devices Module (Concept)
  • Devices Module (Reference)

Channels Configuration

Protocol Options

Model:  Set the PLC model. It can be:

• Others: For all models except 1756-L8X and Micro850.
• 1756-L8X: For Allen-Bradley model: 1756-L8X, 5069-L330ERS, CompactLogix 5380 and 5069-L310ERS2 5380 GuardLogix.
• Micro850: For the Micro850 series.
  

MaxStringItemsPerBlock:  Define the maximum string item count to each block.

For example, if there are 12 string items configured and the MaxStringItemsPerBlock is 3, the result will be 4 blocks to read string data.

WaitingBetweenMsgs: Sets the delay time between consecutive messages sent to the device, helping manage communication load.

StringLegacy: Configures compatibility with legacy string formats used in older systems.

Nodes Configuration

Primary Station 

Stations syntax:  <IP > ; <Port > ; <Slot>

Where :

 <IP> = IP address of the slave device in the network 

< Port > = TCP port where the slave device is listening (default is 44818) 

<Slot> = Slot is the Slot number where the CPU is connected.

Example: 192.168.1.101; 44818; 0

Points Configuration

The syntax for the ControlLogix communication points is: <Type> : <DeviceTagName>

• Type: Type is data type of the Tag in the PLC.
• DeviceTagName: name of the Tag in the PLC.

The valid type values are:

The following Table has possible formats for the DeviceTagName

Accessing Bit from SINT or INT or DINT ControlLogix datatype

Method 1: Using the Modifiers column. 

Use the Modifiers column in Device -> Points to specify the Bit to access.

Example of Device Point Configuration to access Bit 3 from INT

Method 2: Using the Tag property. 

In the Device the whole word into a tag and use the Tag property to access the specify Bit.

Example of Device Point Configuration to access whole word

Syntax to access Tag Bit property in any place of project 

Tag.<TagName>.Bit<Bit Number>

E.g.: Tag.Interger.Bit3

 Examples

Performance Optimization

Overview

When you communicate with a ControlLogix PLC, the protocol is not as efficient as the older PLC 5 style N7:0 addressing. This is the price you pay for the convenience of using tag names in a PLC.

With the ControlLogix PLC, you actually have to give it the complete tag name of each tag that you want. The PLC has to find that tag in its database and return the data to you.

When ControlLogix first came out, you could only get one item in each packet, which meant performance was quite slow. Years later, Rockwell added what they call the CIP (Controller Interface Protocol) Multi-Item Request Packet.

ControlLogix Multi-Item Request Packet sizes are about 500 bytes and can contain the names of multiple PLC tag names that you would like to read. Every character in a tag name takes up about 1 byte.

Some of the 500 bytes are needed for the PLC command and general communication overhead. The point remains the same though: there are less than 500 bytes available to fill tag names into a request packet.

Maximizing System Throughput

As with any programmable controller, there are a variety of ways to enhance the performance and system communications.

In this document, we will discuss the following items:

• Set the PLC CPU time slice to 40%-50%
• Use Array Tags
• Use Global Tags only
• Simultaneous Connections

Set the PLC CPU time slice to 40%-50%

One of the first things you should check in your system is the CPU time slice setting in your ControlLogix PLC. This is set using your RS Logix 5000 programming software. This value represents the percentage of available CPU time that is dedicated to communication activities by the PLC CPU.

It should be noted that the time slice settings for the CPU communications default is 10%. For every 10 ms program scan that occurs, the controller spends 1 ms processing driver requests.

If the communication tasks are high priority, the time slice should be set at or above 30%. Set the slice from 10% to 40% to achieve the best balance of communication, performance, and CPU usage. Values greater than 50% start to reach diminishing returns.

Use Array Tags

The best way to communicate with ControlLogix is through the use of Arrays and short PLC tag addresses. Arrays may have a long tag address name in the PLC. If there are numerous tags in the array, great gains in performance can be achieved due to the ability of a single request for all the tags within the 500-byte packet size.

One hundred tags can be read or written to in a single command. For example: If the Array size is 100 (e.g.: MyTag is an array MyTag[0] to MyTag[99]), under 200ms would be reasonable yet still dependent on the number of other requests required to be met by the system and demands on ControlLogix.

Boolean arrays are treated differently: in protocol, a Boolean array is a 32-bit array. Thus, requesting element 0 is requesting bits 0 through 31.

Use Global Tags Only

In PLCs, the use of short tag names for tags other than arrays is also of great benefit. This is because the TOP Server packs the PLC tag addresses into the Multi-Item Request packet sent to ControlLogix. The 500-byte limit is what makes the shortness of the tag addresses so critical.

Creating all required PC communication tags under the Global file is one way of shortening the names because Global tags require the least amount of space in the Multi-Item Request Packet.

Local (e.g.: Program) tags may sound nice, but in the ControlLogix to get at a program tag (vs. a Global) we also have to put the text: Program:ProgramName in the packet.Plus, we have to add the tag name. You can see how 500 bytes can go fast.

Since we can import L5K file tag descriptions, it is not hard to then change the Server tag names to something more descriptive which would make HMI project creation easier. The key is that the ControlLogix PLC tag name be as short as possible, not the tag name used in the SCADA database.

Simultaneous Connections

In general, the limit on the number of Ethernet connections that can be made to a ControlLogix PLC is high. The default ControlLogix driver opens one TCP socket or connection to the PLC’s Ethernet module for each channel that is defined in the SCADA. However, in the ControlLogix Channel → Settings Column, you can change the number of the NodeConnections and Simultaneous Connections (default 1 and 1 respectively).

For example: If a user created a ControlLogix Channel with 15 node connections and 15 simultaneous connections, 15 TCP socket connections would be made. It means that you have 15 messages going to the PLC at the same time. It is 15 time faster than only one connection. In theory, if the PLC’s Ethernet module had a limit of 64 simultaneous TCP sockets, users could connect 64 simultaneous connection at the same time to the PLC.

As more connections are made to a controller, communication performance will begin to degrade based on the amount of data being acquired and the rate of acquisition. To refine the ratio of CPU time spent on processing and communications, refer to the PLC’s System Overhead Time Slice (SOTS) parameter description.

In summary, this can greatly increase the performance of your communication, but you need to balance it with the PLC’s Time Slice.

Troubleshoot

The status of the driver execution can be observed through the platform built-in diagnostic tools. Refer to the Using Diagnostic Tools topic in Devices Communication page.

Connection Error Codes

CIP Error Codes

Troubleshooting tips

In this driver, it is very important to enable the TraceWindow messages, as invalid addresses can cause all the communication block with the PLC to fail, the TraceWindow tool will display the first invalid address found on the block when Device is enabled on the settings.

In order to have a quick view on the many communication blocks, open the ModuleInformation, navigate on the tree to find ControlLogix and then select Read Groups. Looking at the number and success and fail communication counters, you can easily identify if there is a block with error and then use the TraceWindow to locate the wrong address.

Driver Revision History

In this section: