232
Conditions Requiring Routing Tables Section 6-7
Required Routing Tables
Specify the addresses as shown in the following example.
Serial-to-Serial Conversion
Routing tables to enable the serial communications path to be treated as a
network are optional.
Without Routing Tables
Specify the addresses as shown in the following example.
Address Specification
Routing tables for treating serial communications path as a networ
Unit number
80 hex (128 decimal)
Calculated from unit number: 0, port 1
A
(1) Network address:
To serial communications path network address A
Target: PLC
(2) Node address: Unit numbers for Host Link (0 to 31) + 1
(3) Unit address: E.g., 00 hex for CPU Unit
CPU Unit
CPU Unit
Serial Communications Unit/Board
E.g., Unit number 0, port 1
PLC
FINS network
Address
Contents Example
Remote network address
Remote node address
Remote unit address
A
s+1
CPU Unit: 00 hex
FINS
command
sent
(1) Serial communications path
network address
(2) Unit No. for Host Link
incremented by 1.
(3) Actual remote unit address for
FINS command
FINS Commu-
nications Unit
Network
address
Serial communications
path (Host Link FINS)
Address Specification
Address
Contents Example
Remote node address
Remote unit address
s+1
CPU Unit: 00 hex
Serial Communications Unit/Board
E.g., Unit number 0, port 1
No routing tables required to treat serial communications
path as a network
(1) Network address:
To serial communications path unit address (e.g., 80 hex)
Target: PLC
(2) Node address: Unit numbers for Host Link (0 to 31) + 1
(3) Unit address: E.g., 00 hex for CPU Unit
CPU Unit
CPU Unit
FINS
command
sent
Serial communications
path (Host Link FINS)
Remote network
address
(1) Serial communica-
tions path unit address
(2) Unit No. for Host Link
incremented by 1.
(3) Actual remote unit ad-
dress for FINS command
80 hex (128 decimal)
Calculated from Unit No. 0,
port 1
Serial communications
path (Host Link FINS)
To Next Page
Loading...
Need help?
General
