Filter
Top Products
145
Using FINS Message Communications Section 6-3
Commands Addressed to DeviceNet Units
Command to Send Explicit DeviceNet Messages
6-3 Using FINS Message Communications
There are two instructions that can be executed to send and receive data from
CS/CJ-series CPU Units: SEND(090) and RECV(098). There is another
instruction that can be executed to send any FINS command: CMND(490).
6-3-1 Setting Node Addresses
Set the nodes for FINS message communications to node addresses other
than 0. Node address 0 has a special meaning (local node) in message com-
munications. If 0 is set as a node address for the Unit, message communica-
tions will not be possible.
6-3-2 Creating Routing Tables
The DeviceNet Unit functions as a Communications Unit in the same way as the
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.
Name Command
code
Page
RESET 04 03 241
CONTROLLER DATA READ 05 01 241
CONTROLLER STATUS READ 06 01 242
ECHOBACK TEST 08 01 243
ERROR LOG READ 21 02 244
ERROR LOG CLEAR 03 245
Name Command
code
Page
EXPLICIT MESSAGE SEND 28 01 261
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 is the only
Communications
Unit mounted
Not necessary (See note 1.) Local network table
(See note 2.) and relay
network table are nec-
essary.
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.)