Can someone help me with a path.

I am programming a MSG instruction in a contrologix to do a SLC Type read to a SLC 5/05. The Contrologic talks to our other processors like this.

Shop_Alarm_P1_C0_S1_ENET, 2, 10.60.17.10, 1, 0

This path will get me to the other Contrologix at the address 10.60.17.10.

The SLC is connected to an ENBT card in slot 2 of this processor.

So the above path is out the shop alarm to 10.60.17.10 - Backplane - slot 0 (Thats whats aboveand that nmuch works.

What I need is as follows shop alarm - 10.60.17.10 - backplane - slot 2 - 2.11.17.20 - backplane - slot 0

The 10.60.17.10 is contrologix ENBT and the 2.11.17.20 is the SLC 5/05.

This is what I have been working with but it doesnt work.

Shop_Alarm_P1_C0_S1_ENET, 2, 10.60.17.20, 2, 2.11.17.20, 1, 0

Sorry for all the trouble.

This is what I got in mine writing from a ControlLogix to a 505.

Ethernet, 2, 192.168.1.144

192.168.1.144 is the 505.

I called A-B about this very problem once and its a bit different than from 5000 to 5000.

Hopefully soneone has a tech note about this too.

You're almost there. The RSLogix 5000 Help for the MSG instruction has a surprisingly good explanation of this.

CIP Paths are sets of two value pairs: Port, Address, Port, Address, Port, Address.....

Port 1 is the backplane. Port 2 is the network port.

Addresses can be Slots, IP Addresses, or ControlNet/DH+ node numbers.


Describe your path in terms of Ports and Addresses.

You want to go on four "hops":

From your controller to the backplane, then to the local -ENBT module slot.

On to Ethernet, then to another -ENBT module on the network.

To a Logix backplane, then to 1756-ENBT in Slot 2.

Onto another Ethernet, to the SLC-5/05.


I think what you want is:

Shop_Alarm_P1_C0_S1_ENET, 2, 10.60.17.20, 1, 2, 2, 2.11.17.20

Logix 5000 tries to simplify things by condensing path elements that are also in your I/O tree to their I/O tree names. If you have a controller in a remote chassis defined, you could type out the path by [Port, Address] and RSLogix 5000 would replace it with the controller's name.

The most common instance of this is when you enter the Path to your local 1756-ENBT or 1756-CNB, and RSLogix 5000 replaces it with the module name.

There's a cheat for this, in which you define a CIP path by browsing the path for an OPC Topic in RSLinx, then copy-and-paste the path from the 'Advanced Communications" tab into Logix 5000 in the MSG Path field. You have to trim off the computer name in that path, but it can be a quick and dirty way to get the path you want without doing dead-reckoning.

Thank you Ken, That is exactly what i needed.


Bob