MSG between CLX and SLC via Backplane of second CLX

DaveW

Member
Join Date
Apr 2005
Location
SoCal
Posts
389
Anyone know if I can msg between a ControlLogix L71 (A) and an SLC5/05 (C) via backplane of second ControlLogix L71 (B)? ControlLogix (A) and SLC (C) are on different networks and the the second ControlLogix (B) has two ENBT's that links the 2 networks. See picture attached. I can write logic in ControlLogix (B) to exchange data between (A) and (C) but preferred to go direct.

PLCS.png
 
Yes, you can.

The CIP Path is the key. You can read up on it in the user manuals, the Knowledgebase, or this site, but the basic idea is that the CIP Path consists of pairs of values: "Port, Address", separated by commas.

In this case, the CIP Path will be:

1, 2, 2, 192.168.1.2, 1, 3, 2, 192.168.10.3



Code:
1,2               Backplane, Slot 02 of Chassis A
2,192.168.1,2     Ethernet port, IP address of 1756-ENBT in Chassis B
1,3               Backplane, Slot 03 of Chassis B
2,192.168.10.3    Ethernet port, IP address of SLC-5/03
 
Yes, you can.

The CIP Path is the key

I cannot understand why this very simple addressing concept is so misunderstood. Yet it causes so much problems.

Put simply, a "Path" is specified as ....

Port, Destination, [Port, Destination] ....


... repeat until you land at the target.

A "path" will always need at least two, and an even number, of parameters, otherwise the "port, destination" specification falls short.

However, when specifying paths the programming software will always replace path specifications it "knows about", if that path (or part of) is included in the I/O configuration of the project.

This will occur if you have had to add remote controllers to the I/O configuration for produced/consumed tag exchange.

It doesn't stop you entering the path explicitly, but what you will see (after entering the path) will be different.
 
I cannot understand why this very simple addressing concept is so misunderstood. Yet it causes so much problems. ...




Port,Destination[,Port,Destination]? Yeah, it seems simple, but when I look at the #2 here, I see


Code:
Backplane,Slot,Port,IP,Backplane,Slot,Port,IP
While I agree it is simple, it is only so "once you know the secret" - actually many many many secrets e.g. how does someone know that Ethernet is Port 2? Or how slots are numbered? Or when the Port is actually a Backplane? Or how do I learn that Backplane is 1?


So yeah, to the cognoscenti it is simple, but they have the decoder ring.
 

Similar Topics

I'm using a SLC typed write from the ControlLogix5572 to the MicroLogix 1400, with path: 2, (MicroLogix IP). The ControlLogix equipment has a...
Replies
0
Views
86
Hi all I'm trying to setup a MSG connection (which I'm not familiar to) between a CompactLogix CPU (L310ER) and a Micrologix 1400 CPU. At the...
Replies
1
Views
807
Hi, Is it possible to write tag using MSG in two diffirent controllers in separated networks using Dual-IP? I need to do something like that: 1...
Replies
2
Views
1,588
Hey everyone, I feel like this is an easy question, but I can't seem to find an answer for it. Currently have a PLC-5 that we're swapping out...
Replies
3
Views
1,809
Hello, I am trying to msg between a 1756-ENBT and a 1756-ENBT. One PLC is on a 192.168.34.xx subnet with a 1756-ENBT in slot 2 with a...
Replies
11
Views
2,647
Back
Top Bottom