Applies To:
  • CitectSCADA 5.xx, 6.xx, 7.0, 7.10 
Summary:
There is a confusing array of Citect drivers for Allen Bradley equipment. In many situations there are a number of drivers that could be used. The following list hopes to clarify the best drivers to use for the most common applications.

Solution:

Name

Description

Version (released)

Devices

Notes

Ref

KE

DH485 via KF3 module, PCCC Messages

2.01.01.001

PLC5, SLC500 (typically via 1747-AIC)

Also supports DF1 Serial (Half Duplex).

2

ABRSLINX

RSLinx API, PCCC Messages

1.02.14.001

PLC5, SLC500

(Requires RSLinx)

The most common application of this protocol is connecting to PLC5 or SLC500’s on DH+ which are routed via a ControlLogix gateway to Ethernet.

1,2

ABCLX

Direct connection via Ethernet to ControlLogix, Ethernet/IP Native (using optimised packets)

3.02.37.001

ControlLogix, CompactLogix, FlexLogix

Also supports routed connections where the first hop is Ethernet.

5,6

OPC

OPC DA 1.0a / 2.0 Client

1.15.18.001

Any

(Requires RSLinx)

Was commonly used for ControlLogix connections however it is now preferable to use ABCLX. Can be used for uncommon configurations where there is no native driver or as an alternative to ABRSLINX in some cases.

1

ABTCP

CSP/PCCC (via Ethernet with TCPIP Board driver or via DH+ with CIKT or SSTAB Board drivers

2.06.01.000

SLC500, PLC5

 

SLC5/04 has DH+ connection on the CPU, SLC5/05 has Ethernet connection on the CPU.

 

Most PLC5’s have DH+ connection on the CPU, PLC5E’s have Ethernet connections (via AUI) on the CPU.

 

Cannot be used for ControlLogix.

 

ABMLXEIP

Ethernet/IP, PCCC Messaging

1.01.03.000

Micrologix 1100 (Direct), Other Micrologix via 1761-NET-ENI,

May work with:

SLC5/05 and PLC5E's with newer firmware, older firmwares support ABTCP driver only

Not supporting CIP routing yet ie must be ethernet from end to end.

There may be issues communicating with SLC500 / PLC5. This driver is only designed and tested with MicroLogix (Oct 2009).

2

ABDF1FD

DF1 serial, PCCC Messaging

1.01.02.000

Micrologix,

May work with: SLC500, PLC5

 There may be issues communicating with SLC500 / PLC5. This driver is only designed and tested with MicroLogix (Oct 2009).

2

Superseded

-

-

-

-

 

ABKT

Interchange API (for DH+)

2.01.00.242

SLC500, PLC5

(Requires Interchange or RSLinx)

Superseded by ABRSLinx.

1,2,3

ABEI

Interchange API (for Ethernet)

 

SLC500, PLC5

(Requires Interchange or RSLinx)

Superseded by ABRSLinx.

1,2,3

ABLOGIX

Direct connection via Ethernet to ControlLogix, Ethenet/IP Native (non optimised)

2.00.11.003

ControlLogix, CompactLogix, FlexLogix

Superseded by ABCLX. ABCLX driver version 3.2.0.0 and above support Program Tags.

6

Board drivers

-

-

-

-

 

CIKT

KT, KTX, PKTX card board driver for DH+

2.02.05.000

-

For use with ABTCP protocol driver.

4

SSTAB

3rd party alternative DH+ board (SS_Technologies)

2.05.04.001

-

For use with ABTCP protocol driver.

4

 

  1. RSLinx is Rockwell’s communications gateway software. It will communicate via any of their data networks. It is used to program their PLC’s and also for real-time data access. Interfaces to RSLinx (for real-time data) are via its proprietary API (or legacy Interchange API) or via its OPC Server.
  2. PCCC messaging is the application layer protocol used with register type addressing such as N7:4 or B3:0/7, Some drivers based on this type of addressing can be used with the ControlLogix PLC where the ControlLogix is setup to use PLC5 mapped tags (depending on how the PCCC commands are encapsulated). There are significant limitations when doing this.
  3. Interchange is the old DOS equivalent to RSLinx. These drivers can still be used via RSLinx as RSLinx still supports the Interchange API via ‘INTERCHANGE port mapping’
  4. These board drivers are not supported in Windows Vista and setup can have difficulties in certain hardware (regardless of OS). An alternative is to use these boards with RSLinx and the ABRSLINX driver.
  5. Optimised packets are a Rockwell specific extention to the Ethernet/IP (CIP) protocol. This is the same approach that RSLinx uses to communicate with the ControlLogix.
  6. Native refers to named variables (tag based addressing) as opposed to register addressing.

Some KB articles that are key to understanding this array of drivers are;

Q3424 - Allen Bradley Ethernet/IP and CIP Protocols

Q3721 - Problems with PLC5 Mapped Tags in the ControlLogix

Q3858 - AB Micrologix via an ENI Module

Q3874 - Shortcut Drivers in RSLinx (to Replace Complicated Routes)

Q3938 - ABCLX Driver: Alternative Applications

Refer also to Rockwell KB article Q9356 - RSLinx Version/Features Matrix (also available here: http://forums.mrplc.com/index.php?act=Attach&type=post&id=5058)

In short:

  • If your RSLinx says "Lite" anywhere in the title bar, it will not support _any_ data clients (ie it can browse and program PLC's but nothing else).
  • "Single node" edition will support a local OPC client to one only PLC.
  • Editions higher that will support multiple OPC clients or multiple API clients.
  • To support remote OPC clients (DCOM) you will need the "Gateway" version.
 
Keywords:
 

Attachments