Construct a communications path to the controller

For ControlNet and
DH+
, construct a communications path starting from the communications card in the workstation to which the
RSLinx Classic
 driver is connected. For Ethernet and DF1, construct the path starting from the communications module in the local chassis. Separate the number or address entered in each step with a comma.
TIP:
The path should be empty if talking to a controller directly via DF1.
All numbers are in decimal by default, but enter any number other than an Ethernet IP address in another base by using an IEC-61131 prefix ("8#" for octal, "16#" for hexadecimal); Ethernet IP addresses are always dot-separated decimal numbers.
To construct a communications path to the controller
  1. If communicating over ControlNet, enter a
    2
    for the ControlNet port of the KTC card in the workstation, and then enter the network address (node number) of a CNB module in the local chassis. Skip to step 3.
  2. If communicating over
    DH+
    , enter a
    0
    for the
    DH+
     port of the KT card, then enter the network address (node number) of a DH/RIO module in the local chassis.
  3. Choose the port from which to communicate and enter that number (normally the backplane, so enter a
    1
    ).
  4. Enter the slot number of the module in the local chassis through which to pass.
  5. If that module is the desired controller, skip the remaining steps. However, if bridging across a network through another communications module, enter the number of the port out of which to communicate.
  6. Enter the network address of the destination communications module in the remote chassis.
  7. Return to Step 3 and proceed to select the desired controller with which to communicate.
Examples to construct a single link path
Example 1:
Using
DH+
 to the local chassis to program the controller in slot 9.
0, 8#37, 1, 9
  • 0 =
    DH+
     port of the KT communications card in the workstation
  • 8#37 = octal
    DH+
     node of the DH/RIO module in the local chassis
  • 1 = backplane port of the
    DH+
     module in the local chassis
  • 9 = slot number of the controller in the local chassis
Example 2:
Using ControlNet to the local chassis to program the controller in slot 9.
2, 49, 1, 9
  • 2 = ControlNet port of the KTC communications card in the workstation
  • 49 = ControlNet node of the CNB module in the local chassis
  • 1 = backplane port of the CNB module in the local chassis
  • 9 = slot number of the controller in the local chassis
Example 3:
Using Ethernet to the local chassis to program the controller in slot 9.
1, 9
  • 1 = backplane port of the ENet in the local chassis
  • 9 = slot number of the controller in the local chassis
Examples to construct a bridged path
Example 1:
Using
DH+
 to the local chassis to program the controller in slot 9 of the remote chassis, bridging to the remote chassis via ControlNet.
0, 8#37, 1, 0, 2, 42, 1, 9
  • 0 =
    DH+
     port of the KT communications card in the workstation
  • 8#37 = octal
    DH+
     node of the DH/RIO module in the local chassis
  • 1 = backplane port of the
    DH+
     module in the local chassis
  • 0 = slot number of the CNB in the local chassis
  • 2 = ControlNet port of the CNB in slot 0 of the local chassis
  • 42 = ControlNet node of the CNB in the remote chassis
  • 1 = backplane port of the CNB in the remote chassis
  • 9 = slot number of the controller in the remote chassis
Example 2:
Using ControlNet to the local chassis to program the controller in slot 9 of the remote chassis, bridging to the remote chassis via ControlNet.
2, 49, 1, 0, 2, 42, 1, 9
  • 2 = ControlNet port of the KTC communications card in the workstation
  • 49 = ControlNet node of a CNB module in the local chassis
  • 1 = backplane port of the CNB module in the local chassis
  • 0 = slot number of another CNB in the local chassis
  • 2 = ControlNet port of the CNB in slot 0 of the local chassis
  • 42 = ControlNet node of the CNB in the remote chassis
  • 1 = backplane port of the CNB in the remote chassis
  • 9 = slot number of the controller in the remote chassis
Example 3:
Using
DH+
 to the local chassis to program the controller in slot 9 of the remote chassis, bridging to the remote chassis via
DH+
.
0, 8#37, 1, 2, 3, 8#24, 1, 9
  • 0 =
    DH+
     port of the KT communications card in the workstation
  • 8#37 = octal
    DH+
     node of the DH/RIO module in the local chassis
  • 1 = backplane port of the
    DH+
     module in the local chassis
  • 2 = slot number of the other DH/RIO module in the local chassis
  • 3 = Channel B of the DH/RIO in slot 2 of the local chassis, configured as
    DH+
  • 8#24 = octal
    DH+
     node of the DH/RIO module in the remote chassis
  • 1 = backplane port of the DH/RIO in the remote chassis
  • 9 = slot number of the controller in the remote chassis
Example 4:
Using Ethernet to the local chassis to program the controller in slot 9 of the remote chassis, bridging to the remote chassis via Ethernet.
1, 5, 2, 127.127.127.12, 1, 9
  • 1 = backplane port of an ENet module in the local chassis
  • 5 = slot number of the another ENet module in the local chassis
  • 2 = Ethernet port of the ENet module in slot 5 of the local chassis
  • 127.127.127.12 = IP address of the ENet module in the remote chassis
  • 1 = backplane port of the ENet module in the remote chassis
  • 9 = slot number of the controller in the remote chassis
This table shows target device path specifications.
Via
From
To (first element)
To (second element)
ControlNet
Anything
2
node 1. . . 99
Backplane
Anything
1
slot #
DH+
KT
0
node 8#0 . . . 8#77
DH+
DHRIO Channel A
2
node 8#0 . . . 8#77
DH+
DHRIO Channel B
3
node 8#0 . . . 8#77
Ethernet
Ethernet
2
IP address
TIP:
The first step for TCP and DF1 protocols is the backplane; for the KT or KTC, it is
DH+
 or ControlNet.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.