Filter
Top Products
37
Basic Operating Procedures Section 1-6
Node address (Pins 1 to 6)
Baud rate (Pins 7 and 8)
Etc.
3. Mount the Master and wire the network.
Treat as a CPU Bus Unit.
Can mount to a CPU Rack or Expansion Rack.
With fixed allocations: 3 Units max.
With user-set allocations: 16 Units max.
4. Connect a Programming Device to the PC and turn ON the power supply
to the PC.
5. Generate the I/O tables.
Note 1. A slave may not go online if the communications power supply is turned
ON after the slave is turned ON.
2. The communications power supply and slave power supply, the slave pow-
er supply and PC power supply, or all three of these power supplies may
be turned ON simultaneously.
1-6-3 Creating Routing Tables
The DeviceNet Unit functions as a Communications Unit in the same way as a
SYSMAC LINK Unit, Controller Link Unit, and Ethernet Unit.
It is therefore necessary to create routing tables for the communications func-
tions to be used, as shown in the table below.
Note 1. If a local network table already exists in the CPU unit being used, the De-
viceNet Unit must be registered in that table.
2. The DeviceNet Unit must be registered in the local network table.
Refer to 6-3 Using FINS Message Communications for information on the
routing tables.
The routing tables are created using CX-Net inside the CX-Programmer.
Refer to the CX-Net Operation Manual (
WS02-CXPC1-EV for details.
Note 1. A local network table is sometimes necessary even when the DeviceNet
Unit is not operating across networks.
2. If you prepare a local network table inside the CPU Unit, be sure to register
the DeviceNet Unit.
3. Even if a local network table exists inside the CPU Unit, the 7-segment dis-
play of the DeviceNet Unit may indicate “HC” and FINS message/explicit
Mounted Units Using master or
slave functions only
Using explicit
message
communications
(not supported
across networks)
Using FINS
message
communications
not across networks
Using FINS message
communications across
networks
DeviceNet Unit is the
only Communica-
tions Unit mounted
Not necessary (See note 1.) Local network table (See
note 2.) and relay network
table are necessary.
Multiple DeviceNet
Units mounted as
Communications
Units
Not necessary (See
note 1.)
Local network table necessary (See note 2.)
DeviceNet Unit and
other Communica-
tions Unit mounted
simultaneously
Local network table necessary (See note 2.)