Skip to main content
How Can We Help?

Search for answers or browse our knowledge base.

Allen Bradley Device Communication

Created On
byAndrew Binning
You are here:
< Back

Initial Setup

https://thetaone.atlassian.net/wiki/spaces/XS/pages/62652423/Allen-Bradley+Device+Communication

In order to implement the Allen-Bradley Device Communication on a new XSPOC System.

  1. Obtain a single license for the INGEAR NET.LOGIX 6.0 package and/or the INGEAR NET.ABLINK 6.0 package.
  2. Install the INGEAR NET.LOGIX 6.0  and/or the INGEAR NET.ABLINK 6.0 package onto the XSPOC Server computer. 
  3. Install the INGEAR License Manager onto the XSPOC Server computer, and activate the license.
  4. Run a sample program to test the installation. Each one, if both are installed. This is required because the initial run of the driver has a splash screen which may conflict with the server service.
    1. Run the Browse from Start->INGEAR.NET  Use the IP Address for the device. Hit Connect. It will take a minute to load. Take note of the Global Tags.
  5. Enable the POCType 111 in the tblPOCTypes of the XSPOC database.
  6. Only test with a single tag. It will fail if you have bad tags.

 https://ingeardrivers.com/net-logix-free-trial-2/

https://ingeardrivers.com/net-ablink-free-trial/

INGEAR NET.LOGIX 6.0 Driver

This driver supports the following Allen-Bradley devices:

Controller
Model Number

ControlLogix (all firmware revisions)

1756-L55M12, 1756-L55M22, 1756-L625

1756-L55M13, 1756-L55M24, 1756-L63 / L63S

1756-L55M14, 1756-L61 / L61S, 1756-L64

1756-L55M15, 1756-L615, 1756-LM60M03SEv

1756-L55M16, 1756-L62 / L62S, 1756-L72

1756-L73, 1756-L74, 1756-L75

1756-L71, 1756-L83E, 1756-L85E

CompactLogix (all firmware revisions)

1769-L16E, 1769-L18E, 1769-L24E

1769-L27E, 1769-30E, 1769-L32E

1769-L33E, 1769-35E, 1769-L36E

1768-L42E, 1768-L43E, 1768-L45E

5370-L1, 5370-L2, 5370-L3

5380 (5069-L306ER, 5069-L310ER, 5069-L330ER, 5069-L340ER, 5069-L310ER-NSE, 5069-L306ERM, 5069-L310ERM, 5069-L330ERM, 5069-L340ERM )

Micro850 (all firmware revisions)

2080-LC50-24AWB, 2080-LC50-24QBB, 2080-LC50-24QVB

2080-LC50-24QWB, 2080-LC50-48AWB, 2080-LC50-48QBB

2080-LC50-48QVB, 2080-LC50-48QWB

Micro820 (all firmware revisions)

2080-LC20-20QWB, 2080-LC20-20QBB, 2080-LC20-20AWB

SoftLogix 5800 (all firmware revisions)

1789-L10, 1789-L30, 1789-L60

INGEAR NET.ABLINK 6.0 Driver

This driver supports the following Allen-Bradley devices:

Controller
Model
Communication

MicroLogix 1100
MicroLogix 1400

1763-L16 (all series)

1766-L32 (all series)
  • Direct Ethernet Connection
  • Direct Serial (DF1 Ch0)
  • Serial DF1 via Serial to Ethernet convertor
  • Serial DF1 via 1761 NET ENI
  • Serial DF1 via Digi One IAP

MicroLogix 1000

MicroLogix 1200

MicroLogix 1500

1761-L10, 1761-L16, 1761-L32 (all series)

1762-L24, 1762-L40 (all series)

1764-24, 1764-L28 (all series)
  • Serial DF1 via 1761 NET ENI
  • Serial DF1 via Digi One IAP
SLC-5/05 1747-L551, 1747-L552, 1747-L5532
  • Serial DF1 to Ch0
  • Ethernet to Serial
  • Serial DF1 via 1761 NET ENI
  • Serial DF1 via Digi One IAP
  • Direct Ethernet Connection
SLC-5/04 1747-L541, 1747-L542, 1747-L543
  • Serial DF1 to Ch0
  • Ethernet to Serial DF1 Ch0
  • DH+ via Allen-Bradley 1784-U2DHP
  • DH+ via ControlLogix Gateway
  • DH+ via DL3000-ENI
  • DH+ via DL3500 DH+/IAP
  • Serial DF1 via 1761 NET ENI
  • Serial DF1 via Digi One IAP
SLC-5/03 1747-L531, 1747-L532, 1747-L
  • Serial DF1 to Ch0
  • Ethernet to Serial DF1 Ch0
  • DH-485 via Allen-Bradley 1747-UIC
  • DH-485 via DL3500 DH+/IAP
  • Serial DF1 via 1761 NET ENI
  • Serial DF1 via Digi One IAP
PLC-5/11 1785-L11B
  • Serial DF1 to Ch0
  • Ethernet to Serial DF1 Ch0
  • DH+ via Allen-Bradley 1784-U2DHP
  • Ethernet via 1785-ENET
  • DH+ via ControlLogix Gateway
  • DH+ via DL3000-ENI
  • DH+ via DL3500 DH+/IAP
  • Serial DF1 via 1761 NET ENI
  • Serial DF1 via Digi One IAP
PLC-5/20, PLC-5/20E , PLC-5/20C 1785-L20B, 1785-L20E, 1785-L20C15
  • Serial DF1 to Ch0
  • Ethernet to Serial DF1 Ch0
  • DH+ via Allen-Bradley 1784-U2DHP
  • Direct Ethernet
  • Ethernet via 1785-ENET
  • ControlNet via ControlLogix Gateway
  • DH+ via ControlLogix Gateway
  • DH+ via DL3000-ENI
  • DH+ via DL3500 DH+/IAP
  • Serial DF1 via 1761 NET ENI
  • Serial DF1 via Digi One IAP
PLC-5/26 1785-L26B
  • Serial DF1 to Ch0
  • Ethernet to Serial DF1 Ch0
  • DH+ via Allen-Bradley 1784-U2DHP
  • Ethernet via 1785-ENET
  • DH+ via ControlLogix Gateway
  • DH+ via DL3000-ENI
  • DH+ via DL3500 DH+/IAP
  • Serial DF1 via 1761 NET ENI
  • Serial DF1 via Digi One IAP
PLC-5/30 1785-L30B
  • Serial DF1 to Ch0
  • Ethernet to Serial DF1 Ch0
  • DH+ via Allen-Bradley 1784-U2DHP
  • Ethernet via 1785-ENET
  • DH+ via ControlLogix Gateway
  • DH+ via DL3000-ENI
  • DH+ via DL3500 DH+/IAP
  • Serial DF1 via 1761 NET ENI
  • Serial DF1 via Digi One IAP
PLC-5/40, PLC-5/40E, PLC-5/40L, PLC-5/40C 1785-L40B, 1785-L40E, 1785-L40L, 1785-L40C15
  • Serial DF1 to Ch0
  • Ethernet to Serial DF1 Ch0
  • DH+ via Allen-Bradley 1784-U2DHP
  • Direct Ethernet
  • Ethernet via 1785-ENET
  • ControlNet via ControlLogix Gateway
  • DH+ via ControlLogix Gateway
  • DH+ via DL3000-ENI
  • DH+ via DL3500 DH+/IAP
  • Serial DF1 via 1761 NET ENI
  • Serial DF1 via Digi One IAP
PLC-5/46C 1785-L46C15
  • Serial DF1 to Ch0
  • Ethernet to Serial DF1 Ch0
  • DH+ via Allen-Bradley 1784-U2DHP
  • Ethernet via 1785-ENET
  • ControlNet via ControlLogix Gateway
  • Serial DF1 via 1761 NET ENI
  • Serial DF1 via Digi One IAP
PLC 5/60, PLC 5/60E, PLC 5/60L, PLC-5/60C 1785-L60B, 1785-L60E, 1785-L60L, 1785-L60C15
  • Serial DF1 to Ch0
  • Ethernet to Serial DF1 Ch0
  • DH+ via Allen-Bradley 1784-U2DHP
  • Direct Ethernet
  • Ethernet via 1785-ENET
  • ControlNet via ControlLogix Gateway
  • DH+ via ControlLogix Gateway
  • DH+ via DL3000-ENI
  • DH+ via Dl3500 DH+/IAP
  • Serial DF1 via 1761 NET ENI
  • Serial DF1 via Digi One IAP
PLC 5/80, PLC 5/80E, PLC 5/80L, PLC-5/80C 1785-L80B, 1785-L80E, 1785-L80L, 1785-L80C15
  • Serial DF1 to Ch0
  • Ethernet to Serial DF1 Ch0
  • DH+ via Allen-Bradley 1784-U2DHP
  • Direct Ethernet
  • Ethernet via 1785-ENET
  • ControlNet via ControlLogix Gateway
  • DH+ via ControlLogix Gateway
  • DH+ via DL3000-ENI
  • DH+ via Dl3500 DH+/IAP
  • Serial DF1 via 1761 NET ENI
  • Serial DF1 via Digi One IAP
ControlLogix, CompactLogix, SoftLogix

All series, all firmware (using PLC / SLC memory mapped tags)

 
  • Direct Ethernet
  • Serial DF1 to Ch0
  • Ethernet to Serial DF1 Ch0

None of the Serial communications options are currently implemented.

 

Device Setup

  1. Create a new Asset with the XSPOC Client.

  1. Give it a Name (NodeID) that is unique to the XSPOC system and identifies the AB Device.
  2. Make it a “Facility AB Logix/Micro” device (POCType 111)
  3. Enter the “Node” Address in the Following Format:
Controller Address
innn.nnn.nnn.nnn|pppp|taaaa
Where: i is "i"
nnn.nnn.nnn.nnn is the tcp/ip address of the controller
pppp is the tcp/ip port of the controller
t is The Allen-Bradley PLC CPU Type/DriverType Letter from the table below
aaaa is the dot-delimited string representing the CIP path

Allen-Bradley PLC CPU Type / DriverType

Letter
Allen-Bradley PLC
CPUType
DriverType
L ControlLogix, CompactLogix, SoftLogix CPU.LOGIX NET.LOGIX
M Micro820, Micro850 CPU.Micro NET.LOGIX
E

PLC-5E Series (Direct Ethernet)

 CPU.PLC NET.ABLINK Driver.ENET
S

PLC-5 w/ 1785 Side Car

 CPU.PLC NET.ABLINK Driver.ENETIP
B

PLC-5 (CH 0) via 1761-NET ENI (Series B or later)

 CPU.PLC NET.ABLINK Driver.ENETIP
A

PLC-5 (CH 0) via 1761-NET ENI (Series A or later)

 CPU.PLC NET.ABLINK Driver.NETENI
C

SLC 5/05 (Direct Ethernet)

 CPU.SLC NET.ABLINK Driver.ENET
D

SLC 5/0x (CH 0) via 1761 NET ENI (Series B)

 CPU.SLC NET.ABLINK Driver.ENETIP
F

SLC 5/0x (CH 0) via 1761 NET ENI (Series A)

 CPU.SLC NET.ABLINK Driver.NETENI
G

MicroLogix 1100 FRN 4.0 or Later (Direct Ethernet)

 CPU.MLC NET.ABLINK Driver.ENETIP
H

MicroLogix 1100 FRN 3.0 or Earlier (Direct Ethernet) and ControlLogix/CompactLogix memory mapped tags

 CPU.MLC1100 NET.ABLINK Driver.ENETIP
I

MicoLogix 1000, 1100, 1200, 1400, 1500 (CH 0) via 1761 NET ENI (Series B or later)

 CPU.MLC NET.ABLINK Driver.ENETIP
J

MicoLogix 1000, 1100, 1200, 1400, 1500 (CH 0) via 1761 NET ENI (Series A or later)

 CPU.MLC NET.ABLINK Driver.NETENI

 

Note: When the CommDF1 is implemented, it will override the DriverType

 

Path for ControlLogix/CompactLogix Local Processors

A Local processor resides in the same chassis or back place as the Ethernet Module. For a ControlLogix processor set the Path property to SLOT NUMBER where the CPU resides in the I/O chassis. For a CompactLogix processor set the Path property to “0”.

Path for ControlLogix Remote Processors

Processors residing in remote chassis’ are connected to the local chassis by one or bridge modules. You can address remote processors by supplying one or more segments (network hops) in the Path property.

Syntax: <segment 1>.<segment 2>.<segment n>.1.<slot>

Segment Syntax: 1.<slot>.<channel>.<node>

1. – indicates chassis back plane

<slot> – indicates chassis slot number of bridge module

<channel> – indicates output channel (usually A or B ) of the bridge module to send the message

<node> – node address of destination bridge module to receive the message.

  • Example: Remote Path 1.2.A.6.1.0

    “1.” Chassis Back plane
    2. Slot number of bridge module
    A. Send message out Channel ‘A’ on bridge module
    6. Destination node 6 on remote chassis
    “1.” Chassis back plane on remote
    0 Slot ‘0’ on remote chassis is location of ControlLogix CPU

  • Example: Remote Path 1.11.(192.168.1.135).1.0

    “1.” Local chassis Backplane
    11. Slot number of ENTB/A module on local chassis
    (192.168.1.135). Destination IP Address ( ENBT/A module on remote chassis)
    1.  Backplane on remote chassis
    0   ControlLogix CPU slot on remote chassis

Path For ABLINK DF1 Communications

If Controller.Transport is set to an instance of a CommDF1 class, the Path property represents the destination station id for the target PLC.

  • DH+ controllers (0-63) decimal
  • DH-485 controllers (0-31) decimal
  • For direct serial communications to Channel 0 the .Path property has no significance.

Path for ABLINK ControlLogix Gateway Ethernet/IP and Ethernet Communications

When addressing a PLC/SLC node through a ControlLogix Gateway, you need to specify a routing path (Hop)

  • Always start with “1”
  • I/O Slot of the 1756-DH+/RIO Module
  • The 1756-DH+/RIO Channel to Use (A or B)
  • The Data Highway Plus Node Address of the target (Decimal Address)

Example Hop: 1.2.A.10

  • 1 = Back Plane
  • 2 = I/O chassis slot of 1756-DH+/RIO Module
  • A = Channel A of the 1756 DH+/RIO Module.
  • 10 = PLC Node (decimal address)

Path for non-ControlLogix Gateway:

  • Specify “0” in the Path property.

 

Select a Type 1 or Type 5 Port (Until we have more experience with this driver it might be good to not mix other devices on the same port unless it is necessary.)

Check the “Enable” checkbox if you are ready to communicate with the device.

Save the new Controller

Tag Setup

Select the NodeID that you want to setup Facility Tags for.

Select the “Facilities” tab and then the “Facility Tags Configuration” button

  1. Select the “+New” button
  2. Type “ABReg:” and the Allen-Bradley Device Tag for the datapoint you want to collect.
  3. Type a “Description” for the tag you want to collect.
  4. Set the “DataType” Usually “Float(IEEE)” sometimes “Discrete”, “Byte”, “Integer”, “Long”, or “String”
  5. Select the Tag Configuration “Display Decimals” for “Float(REAL)” datapoints.
  6. Select the Tag Configuration “Enabled” Checkbox
  7. Press the “Save” button.
  8. Press the “Scan” button to see the Data Source “Current Value” and “Last Scan” values update.

 

Tag Name for ABLINK SLC / MicroLogix Processors

Data Table
Syntax
Example
DataType / NetType
INPUT (WORD) I:[MODULE].[ELEMENT] I:0.0 ATOMIC.INTEGER (System.Int16)
INPUT (BIT)

I:[MODULE].[ELEMENT].<0~15>

I:0.0.0 or I:0.0/0

ATOMIC.BOOLEAN (System.Boolean)
OUTPUT (WORD)

O:[MODULE].[ELEMENT]

O:0.0

 ATOMIC.INTEGER (System.Int16)
OUTPUT (BIT)

O:[MODULE].[ELEMENT].<0~15>

O:0.0.0 or 0:0.0/0

ATOMIC.BOOLEAN (System. Int16)

STATUS (WORD)

S:[WORD]

S:0

ATOMIC.INTEGER (System.Int16)

STATUS (BIT)

S:[WORD].<0~15>

S:0.0 or S:0/0

ATOMIC.BOOLEAN (System.Boolean)

BINARY (WORD)

B[FILENUM]:[ELEMENT]

B3:0

ATOMIC.INTEGER (System.Int16)

BINARY (BIT)

B[FILENUM]:[ELEMENT].<0~15>

B3:0.0 or B3:0/0

ATOMIC.BOOLEAN (System.Boolean)

TIMER (STRUCTURE) READONLY

T[FILENUM]:[ELEMENT]

T4:0

ATOMIC.TMR

TIMER (MEMBER)

T[FILENUM]:[ELEMENT].<mnemonic>

T4:0.PRE, T4:0.DN

COUNTER (STUCTURE) READONLY

C[FILENUM]:[ELEMENT]

C5:0

ATOMIC.CTR

COUNTER (MEMBER)

C[FILENUM]:[ELEMENT].<mnemonic>

C5:0.PRE, C5:0.DN

CONTROL (STRUCTURE) READONLY

R[FILENUM]:[ELEMENT]

R6:0

ATOMIC.CTL

CONTROL (MEMBER)

R[FILENUM]:[ELEMENT].<mnemonic>

R6:0.LEN, R6:0.ER

INTEGER (WORD)

N[FILENUM]:[ELEMENT]

N7:0

ATOMIC.INTEGER (System.Int16)

INTEGER (BIT)

N[FILENUM]:[ELEMENT].<0~15>

N7:0.0 or N7:0/0

ATOMIC.BOOLEAN (System.Boolean)

FLOAT (FLOAT)

F[FILENUM]:[ELEMENT]

F8:0

ATOMIC.FLOAT (System.Single)

STRING (STRING)

ST:[FILENUM]:[ELEMENT]

ST9:0

ATOMIC.STRING (System.String)

ASCII (char array)

A[FILENUM]:[ELEMENT]

A10:0

ATOMIC.ASCII (System.Char Array)

LONG (LONG) MicroLogix Only

L[FILENUM]:[ELEMENT]

L10:0

ATOMIC.LONG (System.Int32)

QUEUE (Data Log) MicroLogix 1100/1500 Only

Q:[QUEUE NUMBER]

Q:0

ATOMIC.STRING (READ ONLY)

Tag Name for ABLINK PLC-5 Processors

 

Data Table
Syntax
Example
DataType / NetType
INPUT (WORD) I:[MODULE] I:0 ~ I:77 (octal) ATOMIC.INTEGER (System.Int16)
INPUT (BIT)

I:[MODULE].<0~17>

I:0.0 or I:0/0 (octal)

ATOMIC.BOOLEAN (System.Boolean)

OUTPUT (WORD)

O:[MODULE]

O:0 ~ 0:77 (octal)

ATOMIC.INTEGER (System.Int16)

OUTPUT (BIT)

O:[MODULE].<0~17>

O:0.0 or O:0/0 (octal)

ATOMIC.BOOLEAN (System. Int16)

STATUS (WORD)

S:[WORD]

S:0

ATOMIC.INTEGER (System.Int16)

STATUS (BIT)

S:[WORD].<0~15>

S:0.0 or S:0/0

ATOMIC.BOOLEAN (System.Boolean)

BINARY (WORD)

B[FILENUM]:[ELEMENT]

B3:0

ATOMIC.INTEGER(System.Int16)

BINARY (BIT)

B[FILENUM]:[ELEMENT].<0~15>

B3:0.0 or B3:0/0

ATOMIC.BOOLEAN(System.Boolean)

TIMER (STRUCTURE) READONLY

T[FILENUM]:[ELEMENT]

T4:0

ATOMIC.TMR

TIMER (MEMBER)

T[FILENUM]:[ELEMENT].<mnemonic>

T4:0.PRE, T4:0.DN

COUNTER (STUCTURE) READONLY

C[FILENUM]:[ELEMENT]

C5:0

ATOMIC.CTR

COUNTER (MEMBER)

C[FILENUM]:[ELEMENT].<mnemonic>

C5:0.PRE, C5:0.DN

CONTROL (STRUCTURE) READONLY

R[FILENUM]:[ELEMENT]

R6:0

ATOMIC.CTL

CONTROL (MEMBER)

R[FILENUM]:[ELEMENT].<mnemonic>

R6:0.LEN, R6:0.ER

 

INTEGER (WORD)

N[FILENUM]:[ELEMENT]

N7:0

ATOMIC.INTEGER (System.Int16)

INTEGER (BIT)

N[FILENUM]:[ELEMENT].<0~15>

N7:0.0 or N7:0/0

ATOMIC.BOOLEAN (System.Boolean)

FLOAT (FLOAT)

F[FILENUM]:[ELEMENT]

F8:0

ATOMIC.FLOAT (System.Single)

STRING (STRING)

ST:[FILENUM]:[ELEMENT]

ST9:0

ATOMIC.STRING (System.String)

BLK XFR (STRUCTURE) READONLY

BT[FILENUM]:[ELEMENT]

BT10:0

ATOMIC.BT

BLK XFR (MEMBER)

BT[FILENUM]:[ELEMENT].<mnemonic>

BT10:0.DLEN, BT10.0.DN

MESSAGE (STRUCTURE) READONLY

MG[FILENUM]:[ELEMENT]

MG11:0

ATOMIC.MG

MESSAGE (MEMBER)

MG[FILENUM]:[ELEMENT].<mnemonic>

MG11:0.DLEN, MG11:0.DN

PD BLK (STRUCTURE) READONLY

PD[FILENUM]:[ELEMENT]

PD12:0

ATOMIC.PD
PD BLK (MEMBER)

PD[FILENUM]:[ELEMENT].<mnemonic>

PD12:0.Ki, PD12:0.Kp

SFC (STRUCTURE) READLONLY

SC[FILENUM]:[ELEMENT]

SC13:0

ATOMIC.SC

SFC (MEMBER)

SC[FILENUM]:[ELEMENT].<mnemonic>

SC13:0.PRE, SC13:0.DN

ASCII (char array)

A[FILENUM]:[ELEMENT]

A10:0

ATOMIC.ASCII

BCD (WORD)

D[FILENUM]:[ELEMENT]

D11:0

ATOMIC.BCD