Using a Route Path To Locate a Remote CPU

A route path allows you to indicate the location of a particular CPU on a ControlLogix network in relation to the Ethernet module you’re using as your initial point of communication. It maps out a communication channel across a network of PLCs by defining a series of ports and addresses that eventually lead to the destination CPU.

This information is configured in the [ABCLX] section of the Citect.ini file, using the following syntax:

IOServer name.Port name.RoutePath=/P:m/A:n,...,/P:m/A:n

where:

Example

Starting from the initial Ethernet module, each point in the communication path is defined with a Port value and Address in the following format:

/P:m/A:n,

Include an appropriate numeric value for "m" to indicate if the next communication point is on the same backplane, or connected via a particular port. The value for "n" will then become a backplane slot number, or a module’s unique address.

If you are attempting to route from one Ethernet module to another, you’ll have to use "2" (Port A) for "m", and the destination IP address for "n". For example:

/P:2/A:123.234.0.124,

Simply recreate this syntax for each point in the communication path, separated by commas, to complete the Route Path parameter.

Consider the following diagram, showing a Plant SCADA I/O server, and a network of three ControlLogix PLC backplanes. There are two example route paths represented, one distinguished by a dotted line.

The syntax for the first example (solid line) would be:

IOServerName.PortName.RoutePath=/P:1/A:3,/P:2/A:23,/P:1/A:9,/P:2/A:123.234.0.124,/P:1/A:6

The syntax for the second example would be:

IOServerName.PortName.RoutePath=/P:1/A:3,/P:2/A:23,/P:1/A:7,/P:2/A:17,/P:1/A:6