|
|
ControlLogix Gateway Support
|
|
|
|
|
The concept behind routing is to provide a means of communicating with a remote device over various networks. Routing can be thought of as a bridge between your local device and a remote device even if they are on two different field bus networks. Access to a remote (destination) back plane allows for direct communication with the following modules located on this back plane:
|
|
|
|
|
|
Remote Modules Accessible via Routing:
- ControlLogix 5500 CPUs for ControlLogix Applications
- SoftLogix 5800 CPUs for SoftLogix Applications
- Interface Modules for DH+ Gateway Applications
- Interface Modules for ControlNet Gateway Applications
Communications Networks Supported:
- Ethernet (Ethernet/IP)
- Data Highway Plus
- ControlNet
- Serial Gateway
New! Ethernet/IP Gateway Support
EtherNet/IP Gateway provides a means of communicating with MicroLogix, SLC 500, and PLC-5 series PLC on EtherNet/IP with the Allen-Bradley ControlLogix Ethernet Driver.
New! Serial Gateway Support
Serial Gateway provides a means of communicating with ControlLogix, CompactLogix, FlexLogix, and SoftLogix PLCs on a serial network with the Allen-Bradley ControlLogix Ethernet Driver.
Routing Path Examples
The ControlLogix Gateway capabilities of this TOP Server driver are extremely powerful and flexible. To fully understand the capabilities and limitations of gateway routing please review the driver help file.
|
|
|
|
|
Routing Path Examples:
Due to the complex nature of this feature, examples can typically provide the best tutorial. The examples below will include the entire the Device ID minus the IP of the local 1756-ENET.
 For further details on building a connection/routing path, see the driver help file under the topic “Communications Routing”.
Node Addressing Note: The TOP Server ControlLogix Ethernet Driver specifies all Node IDs in Decimal format. Rockwell software (RSLogix, etc.) specifies all Node IDs in Octal format, so please be aware that this conversion may be necessary.
Diagram Key:
- Green = Ethernet
- Blue = DH+
- Orange = ControlNet
|
|
|
|
|
|
|
|
|
|
Example 1: Logix 5500 to PLC-5 via DH+ Gateway
|
|
Destination Node
|
Model
|
Routing
|
Device ID (Less IP Address)
|
|
PLC-5/20 (D)
|
DH+ Gateway
|
No
|
1,1.B.9
|
|
|
|
|
|
|
Example 2: Logix 5500 to PLC-5C via ControlNet Gateway
|
|
Destination Node
|
Model
|
Routing
|
Device ID (Less IP Address)
|
|
PLC-5/40C (B)
|
ControlNet Gateway
|
No
|
1,2.A.1
|
|
|
|
|
|
|
Example 3: Logix 5500 to Logix 5500 via Routing over DH+
|
|
Destination Node
|
Model
|
Routing
|
Device ID (Less IP Address)
|
|
Logix5550 (C)
|
ControlLogix 5550
|
Yes
|
1,[1,2,8,1],0
|
|
Routing Path Breakdown
|
|
Hop #
|
Segment
|
Description
|
|
1
|
1,2,8,1
|
Slot 1 (DHRIO) -> Port 2 (DH+ Ch. A) -> DH+ Node 8 -> Logix C Backplane
|
|
|
|
|
|
|
Example 4: Logix 5500 to PLC-5C via ControlNet Gateway / Routing over DH+
|
|
Destination Node
|
Model
|
Routing
|
Device ID (Less IP Address)
|
|
PLC-5/80C (E)
|
ControlNet Gateway
|
Yes
|
1,[1,2,8,1],2.A.3
|
|
Routing Path Breakdown
|
|
Hop #
|
Segment
|
Description
|
|
1
|
1,2,8,1
|
Slot 1 (DHRIO) -> Port 2 (DH+ Ch. A) -> DH+ Node 8 -> Backplane Logix5550 (C) -> Slot 2 (CNB) -> Port A (CN) -> PLC-5/80C (E) CN Node 3
|
|
|
|
|
|
|
Example 5: Logix 5500 to Logix 5500 via Routing over DH+ / ControlNet
|
|
Destination Node
|
Model
|
Routing
|
Device ID (Less IP Address)
|
|
Logix5550 (C)
|
ControlLogix 5550
|
Yes
|
1,[1,2,8,1,2,2,15,1],0
|
|
Routing Path Breakdown
|
|
Hop #
|
Segment
|
Description
|
|
1
|
1,2,8,1
|
Slot 1 (DHRIO) -> Port 2 (DH+ Ch. A) -> DH+ Node 8 -> Logix C Backplane
|
|
2
|
2 2,2,15,1
|
Slot 2 (CNB) -> Port 2 (CN Ch A) -> CN Node 15 -> Logix F Backplane
|
|
|
|
|
|
|
Example 6: Logix 5500 to SLC 5/04 via Routing over DH+ / ControlNet
|
|
Destination Node
|
Model
|
Routing
|
Device ID (Less IP Address)
|
|
SLC 5/04 (G)
|
DH+ Gateway
|
Yes
|
1,[1,2,8,1,2,2,15,1],1.A.2
|
|
Routing Path Breakdown
|
|
Hop #
|
Segment
|
Description
|
|
1
|
1,2,8,1
|
Slot 1 (DHRIO) -> Port 2 (DH+ Ch A) -> DH+ Node 8 -> Logix C Backplane
|
|
2
|
2,2,15,1
|
Slot 2 (CNB) -> Port 2 (CN Ch A) -> CN Node 15 -> Logix F Backplane
|
|
3
|
1.A.2
|
Slot 1 (DHRIO) -> Port A (DH+) -> SLC 5/04 (G) DH+ Node 2
|
|
|
|
|
|
|
Example 7: Logix 5500 to Logix5500 via Routing over DH+ / ControlNet / Ethernet
|
|
Destination Node
|
Model
|
Routing
|
Device ID (Less IP Address)
|
|
Logix5550 (H)
|
ControlLogix 5550
|
Yes
|
1,[1,2,8,1,2,2,15,1,3,2,192.192.180.101,1],0
|
|
Routing Path Breakdown
|
|
Hop #
|
Segment
|
Description
|
|
1
|
1,2,8,1
|
Slot 1 (DHRIO) -> Port 2 (DH+ Ch A) -> DH+ Node 8 -> Logix C Backplane
|
|
2
|
2,2,15,1
|
Slot 2 (CNB) -> Port 2 (CN Ch A) -> CN Node 15 -> Logix F Backplane
|
|
3
|
3,2,192.192.180.101,1
|
Slot 3 (ENET) -> Port 2 -> Remote1756-ENET IP -> Logix H Backplane
|
|
|
|
|
|
