Fan Uc Device Net Board 03

GE Fanuc Automation Europe
Computer Numerical Controls
FANUC
DeviceNet™
DeviceNet ™ Board
Operator’s Manual
B-63404EN/03
TECHNOLOGY AND MORE

B-63404EN/03 SAFETY PRECAUTIONS
SAFETY PRECAUTIONS
This section describes the safety precautions related to the use of CNC units, to ensure safe operation
of machines fitted with FANUC CNC units. Read this section carefully before attempting to use any
funcction described in this manaul.
Users ahould also read the relevant descriptions in the Operator’s Manual to become fully familiar
with the functions to be used.
CONTENTS
1. DEFINITION OF WARNING, CAUTION, AND NOTE -----------------------------s-2

2. GENERAL WARNINGS AND NOTES--------------------------------------------------s-3
s-1
SAFETY PRECAUTION B-63404EN/03
1 DEFINITION OF WARNING, CAUTION, AND NOTE
This manual includes safety precautions for protecting the user and
preventing damage to the machine. Precautions are classified into
Warnings and Cautions according to their bearing on safety. Also,
supplementary information is described as Notes. Read the
Warnings, Cautions, and Notes thoroughly before attempting to use
the machine.
WARNING
Applied when there is a danger of the user being
injured or when there is a danger of both the user
being injured and the equipment being damaged if
the approved procedure is not observed.
CAUTION
Applied when there is a danger of the equipment
being damaged, if the approved procedure is not
observed.
NOTE
Notes is used to indicate supplementary information
other than Warnings and Cautions.
• Read this manual carefully, and store it in a safe place.
s-2
2 GENERAL WARNINGS AND CAUTIONS

WARNING
1 Before operating the machine, thoroughly check the
entered data. Operating the machine with incorrectly
specified data may result in the machine behaving
unexpectedly, possibly causing damage to the
workpiece and/or machine itself, or injury to the user.
2 Never attempt to machine a workpiece without first
checking the programmed value, compensation
value, current position, and external signal settings.
Also, never attempt to machine a workpiece without
first checking the operation of the machine. Before
starting a production run, ensure that the machine is
operating correctly by performing a trial run using, for
example, the single block, feedrate override, or
machine lock function, or by operating the machine
with neither a tool nor workpiece mounted. Failure to
confirm the correct operation of the machine may
result in the machine behaving unexpectedly,
possibly causing damage to the workpiece and/or
machine itself, or injury to the user.
3 Ensure that the specified feedrate is appropriate for
the intended operation. Generally, for each machine,
there is a maximum allowable feedrate. The
appropriate feedrate varies with the intended
operation. Refer to the manual provided with the
machine to determine the maximum allowable
feedrate. If a machine is run at other than the correct
speed, it may behave unexpectedly, possibly
causing damage to the workpiece and/or machine
itself, or injury to the user.
4 When using a tool compensation function,
thoroughly check the direction and amount of
compensation.
Operating the machine with incorrectly specified data
may result in the machine behaving unexpectedly,
possibly causing damage to the workpiece and/or
machine itself, or injury to the user.
s-3
SAFETY PRECAUTION B-63404EN/03
WARNING
5 The parameters for the CNC and PMC are factory-
set. Usually, there is no need to change them.
When, however, there is no alternative other than to
change a parameter, ensure that you fully Failure to
set a parameter correctly may result in the machine
behaving unexpectedly, possibly causing damage to
the workpiece and/or machine itself, or injury to the
user.
CAUTION
1 Immediately after switching on the power, do not
touch any of the keys on the MDI panel until the
position display or alarm screen appears on the CNC
unit.
Some of the keys on the MDI panel are dedicated to
maintenance or other special operations. Pressing
any of these keys may place the CNC unit in other
than its normal state. Starting the machine in this
state may cause it to behave unexpectedly.
2 The operator's manual for DeviceNet board
describes all the basic functions of the CNC,
including the optional functions. The selected
optional functions vary with the machine. Some
functions described in this manual may not,
therefore, be supported by your machine. Check the
machine specifications before using DeviceNet
board.
3 Some machine operations and screen functions are
implemented by the machine tool builder. For an
explanation of their usage and related notes, refer to
the manual provided by the machine tool builder.
For example:
• On some machines, executing a tool function
causes the tool change unit to operate. When
executing a tool function on such a machine, stand
well clear of the tool change unit. Otherwise, there
is a danger of injury to the operator.
• Many auxiliary functions trigger physical
operations, such as rotation of the spindle.
Before attempting to use an auxiliary function,
therefore, ensure that you are fully aware of the
operation to be triggered by that function.
s-4
NOTE
• Command programs, parameters, and variables are
stored in nonvolatile memory in the CNC.
Generally, the contents of memory are not lost by a
power on/off operation. However, the contents of
memory may be erased by mistake, or important
data in nonvolatile memory may have to be erased
upon recovering from a failure.
To enable the restoration of data as soon as possible
if such a situation arises, always make a backup of
the data in advance.
s-5
B-63404EN/03 TABLE OF CONTENTS
TABLE OF CONTENTS
SAFETY PRECAUTIONS....................................................................................................................... s-1
I. OUTLINE
1 OUTLINE............................................................................................................................................ 3
II. OPERATION
1 DeviceNet FUNCTIONS..................................................................................................................... 9
1.1 OUTLINE......................................................................................................................................... 10
1.2 SETTING MASTER FUNCTIONS................................................................................................. 11
1.2.1 Setting the Bus Parameters .................................................................................................... 14
1.2.2 Setting Slave Parameters........................................................................................................ 23
1.2.3 Starting Communications ....................................................................................................... 32
1.2.4 Master Function Data Refresh Rate....................................................................................... 37
1.3 SETTING SLAVE FUNCTIONS .................................................................................................... 46
1.3.1 Starting Communications ....................................................................................................... 60
1.3.2 Slave Function Data Refresh Rate ......................................................................................... 61
2 CONFIGURING A SAFE SYSTEM ................................................................................................. 66
2.1 TROUBLESHOOTING COMMUNICATIONS ERRORS ............................................................. 67

2.2 HANDLING MULTIPLE-BYTE DATA ......................................................................................... 68
III. CONNECTION
1 CONNECTING DeviceNet FUNCTIONS ........................................................................................ 71
1.1 CONNECTING DeviceNet.............................................................................................................. 72

1.2 DeviceNet CABLES......................................................................................................................... 74
1.3 CABLE LENGTH AND BAUD RATE............................................................................................ 75
1.4 TERMINATOR ................................................................................................................................ 78
1.5 CONNECTOR.................................................................................................................................. 79
1.6 GROUNDING THE CABLE WIRES.............................................................................................. 82
1.7 CABLE CLAMP ............................................................................................................................... 84
1.8 COMMUNICATIONS POWER SUPPLY....................................................................................... 85
1.8.1 Designing a Power Supply Connection................................................................................... 86
1.8.2 Determining the Power Supply Locations.............................................................................. 86
1.8.3 Verification by Graph-Based Simple Calculation .................................................................. 89
c-1
TABLE OF CONTENTS B-63404EN/03
1.8.4 Verifying by Calculation Expression ...................................................................................... 94

1.8.5 Supplying Multiple Power Supplies on Separated Paths...................................................... 97
1.8.6 Relationship with NC Power Supply ...................................................................................... 98
2 DeviceNet FOR 16i/18i/21i (LCD-MOUNTED TYPE) ..................................................................... 99
2.1 SPECIFICATIONS........................................................................................................................ 100

2.2 INSTALLATION............................................................................................................................ 101
2.2.1 Environmental Conditions .................................................................................................... 101
2.2.2 Leading in Cables .................................................................................................................. 101
2.2.3 Names of Parts on the DeviceNet Board .............................................................................. 102
3 DeviceNet BOARD FOR 16i/18i/21i (STAND-ALONE TYPE), Power Mate i-D/H.......................... 103
3.1 SPECIFICATIONS........................................................................................................................ 104

3.2 INSTALLATION............................................................................................................................ 105
3.3 MOUNTING .................................................................................................................................. 106
3.4 DeviceNet Board B ........................................................................................................................ 107
3.5 DeviceNet Board C ........................................................................................................................ 108
4 DeviceNet BOARD FOR 15i ........................................................................................................... 109
4.1 SPECIFICATIONS........................................................................................................................ 110

4.2 INSTALLATION............................................................................................................................ 111
4.3 INSTALLATION............................................................................................................................ 112
IV. MAINTENANCE.............................................................................................................................. 113
1 16i/18i/21i (LCD-MOUNTED TYPE) DeviceNet............................................................................ 115
1.1 LAYOUT OF PARTS ..................................................................................................................... 116

1.2 DESCRIPTION OF INDICATOR LEDS...................................................................................... 117
1.3 HOW TO ATTACH AND REMOVE THE DeviceNet BOARD ..................................................... 118
2 DeviceNet BOARD FOR 15i, 16i/18i/21i (STAND-ALONE TYPE), Power Mate i-D/H ......................... 119
2.1 DeviceNet BOARD ........................................................................................................................ 120

2.1.1 Layout of Parts....................................................................................................................... 120
2.1.2 Description Of Indicator LEDs ............................................................................................. 121
2.1.3 Short Pin TM1........................................................................................................................ 122
2.1.4 How to Attach and Remove the DeviceNet Board ............................................................... 123
2.2 DeviceNet BOARD B..................................................................................................................... 125
c-2
B-63404EN/03 TABLE OF CONTENTS
2.3 DeviceNet BOARD C..................................................................................................................... 126

2.3.1 Layout of Parts....................................................................................................................... 126
2.3.2 Description Of Indicator LEDs ............................................................................................. 127
APPENDIX
A DEVICE PROFILES AND OBJECT LIBRARIES ...................................................................................... 131
A.1 DeviceNet BOARD C..................................................................................................................... 132
c-3
I. OUTLINE
B-63404EN/03 OUTILINE 1.OUTLINE
1 OUTLINE
This manual comprises the following sections:
Descriptions in This Manual

SAFETY PRECAUTIONS
Describes the precautions you must observe when you read this
manual.
I. OUTLINE
Describes how this manual is organized, applicable models and
related manuals.
II. OPERATION
Describes how to set the various data for performing DeviceNet
communications.
III. CONNECTION
Describes how to connect the various devices for performing
DeviceNet communications and precautions.
IV. MAINTENANCE
Describes the drawing numbers for the DeviceNet board, meanings
of LED indications and error messages.
Trademark
DeviceNet is a trademark of ODVA (Open
DeviceNet Vendor Association).
-3-
1.OUTLINE OUTLINE B-63404EN/03
Applicable Machine Names

This manual covers the following machines.
The following abbreviations are sometimes used in text descriptions.
Machine Name Abbreviation

FANUC Series 15 i-MA 15i-MA
Series 15i-A
FANUC Series 16 i-TA 16i-TA
Series 16i-A
Series 18i-A
Series 21i-A
FANUC Series 16 i-TB 16i-TB
FANUC Series 16 i-MB 16i-MB
Series 16i-B
Series 18i-B
Series 21i-B
FANUC Power Mate i-MODEL D Power Mate i-D
Power Mate i
FANUC Power Mate i-MODEL H Power Mate i-H
-4-
B-63404EN/03 OUTILINE 1.OUTLINE
Related Manuals
The following tables shows the related manuals for each machine
type.
Also refer to these manuals when using this manual.
Series 15i/150i-MA related manuals

Manual Name Specification Number
Descriptions B-63322EN
Connection Manual (Hardware) B-63323EN
Connection Manual (Function) B-63323EN-1
Operator’s Manual (Programming) B-63324EN
Operator’s Manual (Operation) B-63324EN-1
Maintenance Manual B-63325EN
Parameter Manual B-63330EN
Series 16i/18i/160i/180i-TA/MA related manuals

Operator’s Manual (For Lathe) B-63004EN
Operator’s Manual (For Machining Center) B-63014EN
Series 21i/210i-TA/MA related manuals

Series 16i/18i/160i/180i-TB/MB related manuals

-5-
1.OUTLINE OUTLINE B-63404EN/03
Series 21i/210i-TB/MB related manuals

Power Mate i-D/H related manuals

-6-
II. OPERATION
B-63404EN/03 OPERATION 1.DeviceNet FUNCTIONS
1 DeviceNet FUNCTIONS
This chapter describes DeviceNet functions.
-9-
1.DeviceNet FUNCTIONS OPERATION B-63404EN/03
1.1 OUTLINE
Unusable Network Functions

DeviceNet functions cannot be used together with Profibus functions.
Number of networks connectable to NC

• LCD-mounted type Series 16i/18i/21i
One DeviceNet communications board can be mounted.
The connection to the network is made by one function, either
the slave function or master function.
• Stand-Alone type Series 16i/18i/21i Series 15 i -A, and Power

Mate i-D/H series
Two DeviceNet communications boards can be mounted.
Note, however, that when two boards are mounted, one should
be used as the slave function and the other should be used as the
master function.
Outline of DeviceNet function specifications

(1) Master functions
• Poll I/O Connection is supported.
• Max. number of connected slaves: 32

(MAC-ID setup range: 0 to 63)
• Slave assigned addresses

The respective DI/DO signals are assigned continuously
starting from any address in the R area, with single bytes (8
bits) assigned to each address.
• Number of slave DI/DO communication points

: Input signal 0 to 32 bytes
: Output signal 0 to 32 bytes
(2) Slave function

• MAC-ID setup range: 0 to 63
• Assigned addresses
DI/DO signals are assigned continuously starting from any
address in the R area, with single bytes (8 bits) assigned to
each address.
• Number of DI/DO communication points

: Input signal 0 to 64 bytes
: Output signal 0 to 64 bytes
- 10 -
1.2 SETTING MASTER FUNCTIONS
To use the DeviceNet master functions, you must set the bus
parameters and the slave parameters.
"Bus parameters" are for identifying on the network the DeviceNet
interface board that is currently mounted on the control unit (CNC).
"Slave parameters" are for identifying on the network each of the
connected slaves.
The bus parameters are used to specify an MAC-ID, baud rate,
address assignment information, and information about whether to
hold or clear a DI signal related to a communication error(*). Setting
the slave parameters involves setting the MAC-ID, vendor ID, device
type, product code, connection and DI/DO address assignments of the
node to be connected to each slave No.
The following briefly describes each of these items.
The "MAC-ID (Media Access Control ID)" is the ID used for
identifying on the network the DeviceNet communications board that
is currently mounted on the CNC.
This MAC-ID is set to a value within the range 0 to 63, and must not
duplicate the ID of another node on the network.
The "baud rate" is the network's communicating speed, and must be
set to the same value for each node to be connected to the network.
"Address assignment" refers to setting of the DI/DO sizes when I/O of
the DI/DO signals is performed and to setting of the PMC addresses
(addresses of R areas) that are used.
"Vendor ID, device type and product code" are used for specifying the
type of each slave that is connected to the network. If these setting
values do not match the values specific to each of the actually
connected slaves, a connections error will occur.
"Connection" refers to the connection type with each slave. Normally,
set "0". Setting to "0" sets support of Poll I/O Connection.
* See Chapter 2, "Configuring a Safe System" for information

about whether to hold or clear a DI signal related to a
communication error.
- 11 -
Setting Master Functions on the Series 16i/18i/21i-A/B
Procedure (CRT/MDI)
(1) Press function key SYSTEM
and then soft key [PMC] to switch to
the PMC screen.
If you press soft keys [PMCDGN] → ([>])→ [I/OCHK] →

[D_NET] in that order, the DeviceNet Function initial screen
(screen 1.2. (a) below) is displayed.
Screen 1.2 (a)
Table 1.2 shows the display items in the initial screen and a
description of these items.
Table 1.2: Display items in initial screen

Item Description
MODULE ID ID of software running on the DeviceNet interface
board
Example) 0014
MODULE REVISION Version of software running on the DeviceNet
interface board
Example) 0209 → Version 2.9
CONTROL SOFTWARE Series and version number of DeviceNet function
control software on NC
I/F MPU REVISION Version of the MPU on DeviceNet slave board C
Example) H → Version 08
If options are not set for the master function and slave function,
information relating to the corresponding functions and soft keys are
not displayed in the above screen.
In the display example in screen 1.2 (a), both of the options for master
function and slave function are already set.
- 12 -
(2) Next, press soft key [MASTER]. The DEVICENET MASTER

SETTING screen (screen 1.2 (b)) is displayed.
Screen 1.2 (b)
(3) Switch to either of the following parameter setup screens by

pressing soft key [BUS] or [SLAVE], respectively.
(a) Bus parameter setup screen [BUS]
(b) Slave parameter setup screen [SLAVE]
CAUTION
Communications with the slave are not established if
setup of the bus parameters is not completed.
Normally, set up the bus parameters before you set
up the slave parameters.
Descriptions here on regarding parameter setup assume that each of

the nodes are connected to the network and the setup required for
communications (e.g. MAC-ID of each slave and baud rate settings)
are completed.
For details on how to set up the slave, refer to the manual for the
device you are using.
- 13 -
1.2.1 Setting the Bus Parameters
Setting Bus Parameters on the Series 16i/18i/21i-A/B
Pressing soft key [BUS] in screen 1.2 (b) displays screen 1.2.1(a).
Screen 1.2.1(a) Bus parameter setup screen (Series 16i/18i/21i-A/B)
In the following description, let's set the node No. of this master node,
baud rate and the area for storing the status information for verifying
the communications status on the PMC.
You can enter setting values in this screen provided that the following
conditions are satisfied:
(a) Setting parameter PWE must be set to "1".
(b) The unit must be in the MDI mode or in an emergency stop
state.
(c) DISABLE must be selected at the "1 DIS/ENB" item.
- 14 -
Setting Bus Parameters on the Series 15i-A
Set each parameter on the bus parameter setup screen.
Screen 1.2.1(b) Bus parameter setup screen (Series 15i-A)
On this screen, specify the node No. of this master node, its baud rate,
and the area for storing the status information for verifying the status
of communication on the PMC.
<1> Bit 0 (PWE) of setting parameter No. 8000 = 1
<2> The unit is in the MDI mode or at an emergency stop.
<3> DISABLE is selected at "DISABLE/ENABLE."
If no option is set for the master or slave function, the above screen
displays neither information nor a soft key related to the
corresponding function.
Screen 1.2.1 (b) is an example of specifying options of both the
master and slave functions.
- 15 -
Display procedures
Procedure 1
repeatedly until the bus parameter
screen, slave parameter screen, or slave function setup screen is
displayed.
(2) If the slave parameter screen or slave function setup screen is
displayed, press soft key [BUS PARAM] in the operation
selection menu.
Procedure 2
or soft key [SYSTEM].
(2) Press soft key [CHAPTER] repeatedly until [DEVICENET] is
displayed.
(3) Press soft key [DEVICENET].
(4) If the slave parameter screen or slave function setup screen is
displayed, press [BUS PARAM] in the operation selection menu.
Cursor/paging
1 Move the cursor using the cursor keys .
- If the cursor is at "DI HOLD/CLEAR," pressing cursor key

moves the cursor to "DISABLE/ENABLE" in the
slave parameter screen for slave No. 001.
- If the cursor is at "DISABLE/ENABLE," pressing cursor
key moves the cursor to "DI SIZE" in the slave
parameter screen for slave No. 032.
If the slave function is enabled, the slave function setup
screen is displayed.
2 Pressing page key PAGE displays the slave parameter screen for
slave No. 001.
PAGE
Pressing page key displays the slave parameter screen for
slave No. 032.
If the slave function is enabled, the slave function setup screen is
displayed.
- 16 -
Diagnosis Information on the Bus Parameters Setting Screen
STATUS and COMMUNUNICATION STATUS are displayed in bus

parameter setting screen as diagnostics information used for verifying
the communications status.
Table 1.2.1 (b) describes this diagnostics information.
Setting the MAC-ID and baud rate

Set the node number "2. MAC-ID" of this master node and the baud
rate "3. BAUD RATE" to appropriate values referring to items 2 and
3 in Table 1.2.1 (a).
Assigning status information

Set to parameters the addresses and sizes of the R areas to which
status information data is to be assigned.
The content up to the STATUS SIZE setting value items (see Table
1.2.1 (c)) is assigned continuously starting from the specified R area
signal.
For example, to assign eight bytes of status information from R1500
onwards, set each of the data items as follows in screen 1-5.
4 STATUS ADDRESS = R1500

5 STATUS SIZE = 8
Status information is assigned to R area signals as follows according

to this setting.
Status Information Assignments

R1500 STATUS information
R1501 Slave communications status 1
R1505 IDLE/ACTIVE information
R1506 CAN BUS STATUS 1 information
On the PMC, start communications with the slaves using this status
information (STATUS information, slave communication status, etc.).
Also use this status information to process on the PMC any
communications errors that may occur.
The error status of this status information is returned to the normal
communications status when the cause of the error is removed. So, if
the error status must be held, perform this operation on the PMC.
CAUTION
When you set the assignment data, carefully set the
data so that areas to be secured as data do not
duplicate areas that are currently used for ladder
programs on the PMC.
- 17 -
Table 1.2.1 (a): Bus parameter setup items

Item Description
1.DIS/ENB Sets whether to disable or enable
(DISABLE/ENABLE) communications.
Move the left and right cursor keys to select this
parameter setting. (For the 15i-A, use soft keys.)
Set ENABLE after setting of the master function
parameters is completed.
Communications is started several seconds after
setting ENABLE.
ENABLE : Enables communications.
DISABLE : Disables communications.
2.MAC-ID Sets the number for identifying on the network the
DeviceNet interface board mounted on the control
unit (CNC).
Set a number that does not duplicate the MAC-ID
of other nodes on the network within the range 0 to
63.
(MAC-ID: Media Access Control ID)
3.BAUD-RATE Sets the baud rate.
The setting range is 0 to 2.
The baud rate for each setting is as follows:
0: 125 kbps
1: 250 kbps
2: 500 kbps
The baud rate is limited by the maximum network
length and other factors. For details, refer to
"Connecting DeviceNet Functions" in the
Connections Manual.
4.STATUS ADDRESS Set the areas to be used as the status information
5.STATUS SIZE data buffer.
Set the leading buffer address and buffer size.
Use the R area as the address to be set.
Size setting range: 0 to 8
6.DI HOLD/CLEAR Specify whether to hold or clear DI data if
Note) See Chapter 2, communication is abnormal.
"Configuring a 0: To hold DI data.
Safe System." 1: To clear DI data.
- 18 -
Table 1.2.1 (b): Diagnostics information

(STATUS/COMMUNICATION STATUS)
Item Description
STATUS: DISABLE : Disables communications.
(normal communications
status)
ERROR : Communications error has
occurred.
Check COMMUNICATION
STATUS and the status of
the master device.
INVALID MAC ID : The MAC-ID is not set
correctly.
DUPLICATE MAC ID : Duplicate MAC-IDs have
been set.
BUS FAULT : Bus error has occurred.
POWER ON ERROR : An error occurred when
the power was turned ON
or when ENABLE was set.
Check the DeviceNet
interface board mounting
state.
COMMUNICATION Indicates the status of the Group 2 Master/Slave
STATUS: Connection Set. "01" indicates an active state.
IDLE/ACTIVE
00: IDLE state
(Group 2 Master/Slave Connection Set is not
established.)
01: ACTIVE state
(Group 2 Master/Slave Connection Set is
established.)
COMMUNICATION Indicates the status information of the CAN
STATUS: (Controller Area Network) bus. Status information
CAN BUS STATUS1 is expressed in hexadecimal with 1 byte
expressing each item of information. Each of the
bits of the status information is significant.
CAN BUS STATUS1 (1byte Data)

#7 #6 #5 #4 #3 #2 #1 #0
[ML] [RO] [TO] [TA] [A] [BO] [BW] [OL]
The meaning of ‘1’ of each bit is as follows.

(Values in parentheses () indicate values in the
normal communications status.)
#01 OL (1) : Online state
#1 BW (0) : Bus warning state
A communications error has
occurred, and the CAN chip
automatically stopped frame transfer.
Probable causes are an incorrect
baud rate setting or noise.
- 19 -
Table 1.2.1 (b) (continued): Diagnostics information

(STATUS/COMMUNICATION STATUS)
Item Description
COMMUNICATION #2 BO (0) : Bus OFF state
STATUS: A communications error has
CAN BUS STATUS1 occurred, and the CAN chip
automatically turned offline. Probable
causes are an incorrect baud rate
setting or a hardware malfunction.
#3 A (1) : Network is active.
Data is being sent and received.
#4 TA (0) : Response error state
There is no response from the
communications destination within 25
to 50 msec. The communications
destination node may not exist on the
network.
#5 TO (0) : Time-out state
High priority data may be being
transferred excessively.
#6 RO (0) : Receive buffer overrun has occurred.
#7 ML (0) : Message lost has occurred.
COMMUNICATION CAN BUS STATUS2 (1byte Data)
STATUS: #7 #6 #5 #4 #3 #2 #1 #0
CAN BUS STATUS2 [SA] [05] [02] [01] [--] [--] [BP] [ER]
The meaning of ‘1’ of each bit is as follows.

#0 ER (0) : A CAN communications error has
occurred.
A probable cause is noise or a
hardware malfunction.
#1 BP (1) : Network power ON state
#2 --
#3 --
#4 01 : Baud rate is 125 kbps.
#7 SA (1) : The network scanner is active.
- 20 -
Table 1.2.1 (c): Relationship between STATUS SIZE setting values

and STATUS information
Setting
Item Description
Value
1 STATUS information This 1-byte data notifies the PMC of the
communications status.
00h : Disables communications.
01h : Enables communications. (normal
communications status)
03h : Communications error has
occurred.
For details, check the
COMMUNICATION STATUS and
status of the master device.
82h : Illegal MAC-ID
84h : Duplicate MAC-ID
8Eh : Bus error has occurred.
8?h : An error other than the above
occurred at start of
communications.
2 Slave communications This 1-byte data indicates the
status 1 communications status with each node
(slave No. 1 to 8) having slave No. 1 to 8 in each of its
respective eight bits.
Bit #7 #6 #5 #4 #3 #2 #1 #0
Node 8 7 6 5 4 3 2 1
Communications status (common to all

bits)
1: Enables communications. (normal
0: Disables communications.
Bit #7 #6 #5 #4 #3 #2 #1 #0
Node 16 15 14 13 12 11 10 9

bits)
- 21 -
Table 1.2.1 (c) (continued): Relationship between setting values of

STATUS SIZE and STATUS information
Setting
Item Description
Value
Bit #7 #6 #5 #4 #3 #2 #1 #0
Node 24 23 22 21 20 19 18 17
Slave communications Communications status (common to all

status 3 bits)
(slave No. 17 to 24) 1: Enables communications. (normal
Bit #7 #6 #5 #4 #3 #2 #1 #0
Node 32 31 30 29 28 27 26 25

bits)
6 COMMUNICATION This 1-byte data notifies the PMC of the
STATUS: state of Group 2 Master/Slave
IDLE/ACTIVE Connection Set of the DeviceNet.
information 00h: IDLE state
01h: ACTIVE state
7 COMMUNICATION This 1-byte data notifies the PMC of
STATUS: CAN BUS CAN BUS STATUS1 information.
STATUS1 information
#7 #6 #5 #4 #3 #2 #1 #0
[ML] [RO] [TO] [TA] [ A ] [BO] [BW] [OL]
For details, refer to the CAN BUS

STATUS1 information described above.
STATUS2 information
#7 #6 #5 #4 #3 #2 #1 #0
[SA] [05] [02] [01] [--] [--] [BP] [ER]

- 22 -
1.2.2 Setting Slave Parameters
Setting Slave Parameters on the Series 16i/18i/21i-A/B
Pressing soft key [SLAVE] in the DEVICENET MASTER SETTING

initial screen (screen 1.2 (a)) displays the slave parameter setup
screens (screens 1.2.2 (a) and 1.2.2 (b)).
Switch between screens

Screen 1.2.2 (a) Bus parameter setup screen (Series 16i/18i/21i-A/B) (1)
using pagekeys ↑ ↓ .
Screen 1.2.2 (b) Bus parameter setup screen (Series 16i/18i/21i-A/B) (2)
- 23 -
Select the slave No. whose parameters are to be set by using soft keys
[PRV.NO] and [NXT.NO].
Table 1.2.2 (a) describes the parameters that are set in these screens.
You can enter setting values in these screens provided that the
following conditions are satisfied:
state.
(c) "DISABLE" must be selected at the "1 DIS/ENB" item.
- 24 -
Setting Slave Parameters on the Series 15i-A

In the slave parameter screen, specify slave parameters and address
assignment.
Screen 1.2.2 (c) Bus parameter setup screen (Series 15i-A)
Table 1.2.2(a) lists the parameters to be set up in this screen.
Display procedures
Procedure 1
displayed.
(2) If the bus parameter screen or slave function setup screen is
displayed, enter the desired slave number, and press soft key
[SLAVE PARAM].
Procedure 2
displayed.
(4) If the bus parameter screen or slave function setup screen is
displayed, enter the desired slave number, and press soft key
[SLAVE PARAM].
- 25 -
Cursor/paging
- If the cursor is on a "DO SIZE" line, pressing cursor key
moves the cursor to "DISABLE/ENABLE" for the
next slave number.
If the cursor is on the last "DO SIZE" line for slave No. 032,
pressing the cursor key moves the cursor to
"DISABLE/ENABLE" in the bus parameter screen.
- If the cursor is at "DISABLE/ENABLE," pressing cursor
key moves the cursor to "DO SIZE" for the previous
slave number.
If the cursor is at "DISABLE/ENABLE" for slave No. 001,
pressing the cursor key moves the cursor to "DI
HOLD/CLEAR" in the bus parameter screen.
PAGE
2 Pressing page keys PAGE displays the slave parameter
screen for the previous or next slave number, respectively.
- In the slave parameter screen for slave No. 001, pressing page
PAGE
key displays the slave parameter screen for slave No. 002.
PAGE
key displays the bus parameter screen.
If the slave function is enabled, the slave function setup screen is
displayed.
key PAGE displays the bus parameter screen.
The following procedures can display the slave parameter screen
for the specified slave number.
Procedure 1
(1) Press soft key [SLAVE PARAM].
(2) Key in the desired slave number.
(3) Press soft key [EXEC].
Procedure 2
(1) Key in the desired slave number.
(2) Press soft key [SLAVE PARAM].
- 26 -
(1) To proceed to "3 VENDOR ID", "4 DEVICE TYPE" and "5
PRODUCT CODE", set the respective vendor ID, device type
and product code. These setting values are referenced to as
values specific to the connected slave. If the setting values do
not match the values specific to the connected slave, an error(s)
occurs. Note, however, that setting of these items is arbitrary.
(Communications will not be influenced if these setting values
are left at their "0000" settings. If these setting values are set to
"0000," the slaves will not be referenced.)
In a normal communications state with the connected slaves,
these values can be read and the respective items automatically
set by operating soft key [INIT].
(Refer to "1.2.3 Starting communications, Automatic setting of
slave parameters.")
(2) To proceed to "6 CONNECTION" set "0". The connection type

with the slave is Poll I/O Connection. Also set the connection
type on the slave device to Poll I/O Connection.
STATUS and CONDITION are displayed in this screen as diagnostics

information used for verifying the communications status.
Table 1.2.2 (b) describes this diagnostics information.
- 27 -
Table 1.2.2 (a): Slave parameter setup items

Item Description
1 DIS/ENB Sets whether to disable or enable communications
(DISABLE/ENABLE) with the node having the selected slave No.
parameter setting. (Soft keys are used in the 15i-
A.)
Communications is started several seconds after
setting ENABLE.
2 MAC-ID Sets the number for identifying on the network the
slave to be connected.
63.
3 VENDOR ID Set the vendor ID/device type/product code of the
4 DEVICE TYPE slave to be connected.
5 PRODUCT CODE Set in hexadecimal within the range 0000 to FFFF.
(default: 0000)
These setting values are used for specifying the
type of connected type. If the setting value does
not match the value specific to the connected
slave, an error (INVALID VENDOR ID/INVALID
DEVICE TYPE/INVALID PRODUCT CODE)
occurs. Note, however, that this error is not
detected when the setting value is set to "0000".
Also, as nodes on the network are identified by a
MAC-ID, communications is performed normally
even if the setting value of these items is set to
"0000".
In a normal communications state, the values of
these items can be read from the connected slave
and the read values automatically set to the
respective items by operating soft key [INIT].
6 CONNECTION Sets the connection type with the slave.
"0" must be set.
Setting to "0" sets the connection type with the
slave to Poll I/O Connection.
7 DI ADDRESS Set the areas to be used as the DI/DO data buffer.
8 DI SIZE Set the leading buffer address and buffer size.
9 DO ADDRESS Use the R area as the address to be set.
10 DO SIZE Size setting range: 0 to 32
- 28 -
Table 1.2.2 (b): Diagnostics information (STATUS/CONDITION)

Item Description
STATUS Displays the communications status.
occurred.
For details, check CONDITION,
status of COMMUNICATION
STATUS in the bus parameter
screen, and the status of the
master function.
INVALID MAC ID : The MAC-ID is not set correctly.
DUPLICATE MAC ID : Duplicate MAC-IDs have been set.
DUPLICATE DEVICE : A MAC-ID duplicating the bus
parameter has been set.
INVALID CONNECTION : Connection by the correct I/O
Connection is not made.
The connection by these
DeviceNet master functions is Poll
I/O Connection.
POWER ON ERROR : An error occurred when the power
was turned ON or when ENABLE
was set.
Check the network cable
connections or DeviceNet interface
board mounting state.
CONDITION Displays the states of the connected slaves.
(00) DISABLE : Disables communications.
(01) IDLE : Network scan standby state
(02) DEVICE BEING SCANED : Normal communications
status
Scanning of connected
slaves is being performed
correctly.
(03) TIMED-OUT : Time-out state
There is no response from
the slaves.
(04) CONNECTION ERROR : The UCMM (Unconnected
Message Manager)
connection cannot be
performed correctly.
(05) CONNECTION BUSY : Master/Slave connection is
busy.
(06) CONNECTION ERROR : Master/Slave connection
cannot be established.
(07) INVALID VENDOR ID : The vendor ID of the
currently connected slave
differs from the parameter
setting value.
(08) VENDOR ID ERROR : The vendor ID of the
cannot be read.
- 29 -
Table 1.2.2 (b) (continued): Diagnostics information

(STATUS/CONDITION)
Item Description
CONDITION (09) INVALID DEVICE TYPE : The device type of the
(continued) currently connected slave
setting value.
(0A) DEVICE TYPE ERROR : The device type of the
cannot be read.
(0B) INVALID PRODUCT CODE: The product code of the
setting value.
(0C) PRODUCT CODE ERROR : The product code of the
cannot be read.
(0D) INVALID INPUT SIZE : The DI size of the currently
connected slave differs
from the DI SIZE
parameter setting value.
(0E) INPUT SIZE ERROR : The DI size of the currently
connected slave cannot be
read.
(0F) INVALID OUTPUT : The DO size of the
differs from the DO SIZE
(10) OUTPUT SIZE ERROR : The DO size of the
cannot be read.
(17) SYNC FAULT : Failed to synchronize
Master/Slave connection.
(??) ERROR : Other error state
Assigning DI/DO addresses

DI/DO areas are to be assigned. For example, to assign six bytes of DI
data (data input to the CNC from the slave) to R1000 onwards and
assign two bytes of DO data (data output from the CNC to the slave)
to R1100 onwards, set each of the data items as follows in screen
1.2.2 (b).
4 DI ADDRESS = R1000
5 DI SIZE = 6
6 DO ADDRESS = R1100
7 DO SIZE = 2
DI/DO is assigned to R area signals as follows according to this

setting.
- 30 -
DI Assignments
R1000 1st DI data from slave
R1001 2nd DI data from slave
R1002 3rd DI data from slave
R1003 4th DI data from slave
DO Assignments
R1100 1st DO data to slave
R1101 2nd DO data to slave
When a DI only slave or a DO only slave is connected, set the value

of the parameter that specifies the size of the unused DO or DI to "0".
CAUTION
data so that areas to be secured as each assigned
data item are not duplicated. Also, thoroughly check
before setting to prevent areas that are currently
used for other slave assignment addresses and PMC
ladder programs from being duplicated.
- 31 -
1.2.3 Starting Communications

After you have finished setting up the bus parameters and slave
parameters, start communications by selecting ENABLE at the "1
DIS/ENB" item. Move the cursor from DISABLE to ENABLE. After
a few seconds, communications is started, and the STATUS display
changes to ERROR and the CONDITION display changes to (01)
IDLE as shown in screens 1.2.3 (a) and (b) below.
Case of the Series 16i/18i/21i-A/B
Screen 1.2.3 (a) Case of Series 16i/18i/21i-A/B
Case of the Series 15i-A
Screen 1.2.3 (b) Case of Series 15i-A
- 32 -
When communications with the currently connected slave is

performed normally, the STATUS display changes to ENABLE and
the CONDITION display changes to (02) DEVICE BEING
SCANNED. (See screens 1.2.3 (c) and (d) below.)
Screen 1.2.3 (c) Case of Series 16i/18i/21i-A/B

To continue setting other slave parameters, press soft key [PRV.NO]
or [NXT.NO] to change the slave No. Up to 32 slaves can be set.
Screen 1.2.3 (d) Case of Series 15i-A
- 33 -
PAGE
To set up another slave parameter, press page keys PAGE to
switch to that slave number.
Cursor operations and switching of screens are not possible for

several seconds until the connection for communications is
established.
- 34 -
Automatic setting of slave parameters

You can automatically set "3 VENDOR ID", "4 DEVICE TYPE" and
"5 PRODUCT CODE" by pressing soft key [INIT] in screen 1.2.3 (b)
in a normal communications state (STATUS display: ENABLE,
CONDITION display: (02) DEVICE BEING SCANNED).
When you press soft key [INIT], soft keys [YES] and [NO] are
displayed. (See screens 1.2.3 (e) and (f) below.)
Screen 1.2.3 (e) Case of Series 16i/18i/21i-A/B
Next, press soft key [YES] to automatically set these items.
- 35 -
Pressing soft keys [INIT] → [EXEC] enables "VENDOR ID,"

"DEVICE TYPE," and "PRODUCT CODE" to be set up
automatically.
Screen 1.2.3 (f) Case of Series 15i-A
CAUTION
Automatic setting of parameters is not performed
when communications is not being performed
normally.
- 36 -
1.2.4 Master Function Data Refresh Rate
The "data refresh rate" is the time required for the control unit (CNC)
to update all I/O signals assigned to the R areas.
CAUTION
The data refresh rate does not indicate the I/O
response time on the network. The I/O response
time is dependent on the condition of the network.
Refreshing of I/O signals in the master function is performed every 8

msec at a maximum of 32 bytes for both DI and DO. In other words,
the data refresh rate changes as shown in the following table
according to the number of communications points on each slave.
Table 1.2.4 (a)

Total Number of Slave Communications Points Data Refresh Rate
1 to 32byte 8ms
33 to 64byte 16ms
65 to 96byte 24ms
In the same way from here on, the data refresh rate is extended by 8 ms at a
time as the total number of slave communications points increases by 32
bytes.
For example, the total DI size becomes 68 bytes when the sizes of the
DI/DO signals on each slave are set as follows. (See table below.)
Table 1.2.4 (b)

Slave No. DI Size DO Size
1 16 0
2 16 16
3 0 8
4 8 8
5 24 0
6 4 0
Total DI/DO size 68 32
At this time, as the data refresh rate of the DI signal is 24 msec and
the total DO size is 32 bytes according to Table 1.2.4 (a), the data
refresh rate of DO signals becomes 8 msecs. In this instance, the time
until all DI/DO signals are updated becomes the slower time of 24
msec.
- 37 -
Setting Master Functions on Power Mate i-D/H
On the Power Mate i-D/H, master functions can be set using the
regular parameters, and you can confirm "STATUS" and
"CONDITION" in the regular diagnostics screen.
NOTE
1 When the DeviceNet parameters have been set, the
power must be turned OFF temporarily.
2 In the case of Power Mate i-D two-path control,
setting and diagnostics can be performed only from
the 1st path.
Procedure when using CRT/MDI

The setup procedure is exactly the same as the Procedure (CRT/MDI)
in "Setting Master Functions on the Series 16i/18i/21i-A/B" described
earlier. For details, see this item.
Procedure when using DPL/MDI

DGNOS
(1) Press the PARAM key to switch to the parameter screen.
(2) Set the parameters described later in the same way as regular
parameters.
DGNOS
(3) Press the PARAM key to switch to the diagnostics screen.
(4) Check the diagnostics numbers described later.
Procedure when using the DPL/MDI operation package (PC)

F4
(1) Press the DGN
PRM
key to switch to the parameter screen.
parameters.
F4
(3) Press the DGN
PRM
key to switch to the diagnostics screen.
(4) Check the diagnostics numbers described later.
- 38 -
Parameters
28100 Enable/disable communications
DI16
[Data type] Byte

[Data range] 0, 1
Sets whether to disable or enable communications. Communications
is started when this parameter is set to "1" and the power is turned ON
again.
This parameter is equivalent to the "1 DIS/ENB" setting in screen
1.2.1(a) or 1.2.1(b).
Setting Value Meaning
0 Disables communications.
1 Enables communications.
28101 MAC-ID
DI16
[Data type] Byte

[Data range] 0 to 63
Sets the number for identifying on the network the DeviceNet
interface board mounted on the control unit (CNC).
Set a number that does not duplicate the MAC-ID of other nodes on
the network within the range 0 to 63.
This parameter is equivalent to the "2 MAC-ID" setting in screen
1.2.1(a) or 1.2.1(b).
28102 Baud rate

DI16
[Data type] Byte

[Data range] 0 to 2
Sets the baud rate. The baud rate is limited by the maximum network
length and other factors. For details, see the "Connecting the
DeviceNet Functions" item in the Connections section.
This parameter is equivalent to the "3 BAUD-RATE" setting in screen
1.2.1(a) or 1.2.1(b).
Setting Value Baud rate
0 125Kbps
1 250Kbps
2 500Kbps
28116 Status information data buffer area
[Data type] Byte

[Data range] 0
Sets the area to be used as the status information data buffer. Use the
R area as the address to be set.
This parameter is equivalent to the buffer area setting in "4 STATUS
ADDRESS" in screen 1.2.1(a) or 1.2.1(b).
Setting Value Buffer Area
0 R area
- 39 -
28117 Status information data buffer address
[Data type] Word

[Data range] 0 to (value obtained by subtracting the setting value of No.28118 from
the maximum value of the R area)
Sets the leading address of the status information data buffer.
This parameter is equivalent to the buffer address setting in "4
STATUS ADDRESS" in screen 1.2.1(a) or 1.2.1(b).
28118 Status information data buffer size
[Data type] Byte

[Data range] 0 to 4
Sets the size of the status information data buffer.
This parameter is equivalent to the "5 STATUS SIZE" setting in
screen 1.2.1(a) or 1.2.1(b).
28119 Holding/Clearing the DI data
[Data type] Byte

[Data range] 0, 1
Sets the state of the DI data when communication is not normal.
This parameter is equivalent to the "6 HOLD/CLEAR" setting in
screen 1.2.1(a) or 1.2.1(b).
0 Holding the DI data
1 Clearing the DI data
28200 Disable/enable communications with slave No.1.
[Data type] Byte

[Data range] 0, 1
Sets whether to disable or enable communications with the slave No.1
node. Communications is started when this parameter is set to "1" and
the power is turned ON again.
1.2.2(a) or 1.2.1(c).
28201 MAC-ID of slave No.1
[Data type] Byte

Sets the number for identifying the slave to be connected.
1.2.2(a) or 1.2.1(c).
- 40 -
28203 Vendor ID of slave No.1
28204 Device type of slave No.1
28205 Product code of slave No.1
[Data type] Word

Sets the vendor code/device type/product code of the slave to be
connected. Set this parameter in decimal (default=0). This setting is
used to specify the type of connected slave. If the setting value does
not match the value specific to the connected slave, an error
(INVALID VENDOR ID/INVALID DEVICE TYPE/INVALID
PRODUCT CODE) occurs. Note, however, that this error is not
detected when the setting value is set to "0". Also, as nodes on the
network are identified by a MAC-ID, communications is performed
normally even if the setting value of this parameter is set to "0".
This parameter is equivalent to the "3 VENDOR ID" / "4 DEVICE
TYPE" / "5 PRODUCT CODE" settings in screen 1.2.2(a) or 1.2.1(c).
28206 Connection type of slave No.1
[Data type] Byte

[Data range] 0
Sets the connection type with the slave. "0" must be set. Setting to "0"
sets the connection type with the slave to Poll I/O Connection.
This parameter is equivalent to the "6 CONNECTION" setting in
screen 1.2.2(a) or 1.2.1(c).
Setting Value Connection Type
0 Poll I/O Connection
28210 DI data buffer area of slave No.1
[Data type] Byte

[Data range] 0
Sets the area to be used as the DI data buffer. Use the R area as the
address to be set. This parameter is equivalent to the buffer area
setting in "7 DI ADDRESS" in screen 1.2.2(b) or 1.2.1(c).
0 R area
28211 DI data buffer address of slave No.1
[Data type] Word

Sets the area to be used as the DI data buffer. Set the leading address
of the buffer.
This parameter is equivalent to the buffer address setting in "7 DI
ADDRESS" in screen 1.2.2(b) or 1.2.1(c).
- 41 -
28212 DI data buffer size of slave No.1
[Data type] Byte

Sets the area to be used as the DI data buffer. Set the size of the buffer
within the range 0 to 32.
This parameter is equivalent to the "8 DI SIZE" setting in screen
1.2.2(b) or 1.2.1(c).
28213 DO data buffer area of slave No.1
[Data type] Byte

[Data range] 0
Sets the area to be used as the DO data buffer. Set the leading address
of the buffer.
This parameter is equivalent to the buffer area setting in "9 DO
0 R area
28214 DO data buffer address of slave No.1
[Data type] Word

of the buffer.
This parameter is equivalent to the buffer address setting in "9 DO
28215 DO data buffer size of slave No.1
[Data type] Byte

Sets the area to be used as the DO data buffer. Set the size of the
buffer within the range 0 to 32.
This parameter is equivalent to the "10 DO SIZE" setting in screen
1.2.2(b) or 1.2.1(c).
From here on, parameter numbers for slave number n (where, n=1 to
32) are numbers obtained by adding (n-1) x 20 to the parameter
number of slave No.1.
- 42 -
28200
Enable/disable communications with slave No. n
+(n-1)×20
28201
MAC-ID of slave No. n
+(n-1)×20
28203
Vendor ID of slave No. n
+(n-1)×20
28204
Device type of slave No. n
+(n-1)×20
28205
Product code of slave No. n
+(n-1)×20
28206
Connection type of slave No. n
+(n-1)×20
28210
DI data buffer area of slave No. n
+(n-1)×20
28011
DI data buffer address at slave No. n
+(n-1)×20
28012
DI data buffer size at slave No. n
+(n-1)×20
28013
DO data buffer area at slave No. n
+(n-1)×20
28014
DO data buffer address at slave No. n
+(n-1)×20
28015
DO data buffer size at slave No. n
+(n-1)×20
- 43 -
Diagnostics
900 Communications status of slave No.1
Indicates the communications status of slave No.1.

This diagnostic is equivalent to the "STATUS" setting in screens
1.2.2 (a), 1.2.2 (b) and 1.2.2(c).
Display on Screens
Value Meaning
1.2.2 (a), 1.2.2 (b) and 1.2.2(c)
0 DISABLE Disables communications.
1 ENABLE Enables communications.
2 Reserved
3 ERROR Communications error has occurred.
For details, check CONDITION, status of STATUS information (R area)
and the error status of the slave device.
129 Reserved
130 INVALID MAC ID The MAC-ID is not set correctly.
131 Reserved
132 DUPLICATE MAC ID Duplicate MAC-IDs have been set.
133 DUPLICATE DEVICE A MAC-ID duplicating the bus parameter has been set.
134 Reserved
135
136
137
138
139
140
141
142
143 INVALID CONNECTION Connection by the correct I/O Connection is not made.
The connection by these DeviceNet master functions is Poll I/O
Connection.
144 Reserved
145
146
POWER ON ERROR An error occurred when the power was turned ON or when ENABLE was
set.
Check the network cable connections or DeviceNet interface board
mounting state.
- 44 -
901 Status of slave No.1
Indicates the status of slave No.1.

This diagnostic is equivalent to the "CONDITION" setting in screens
1.2.2 (a), 1.2.2 (b) and 1.2.2(c).
Display on Screens
Value Meaning
1.2.2 (a), 1.2.2 (b) and 1.2.2(c)
0 DISABLE Disables communications.
1 IDLE Network scan standby state
2 DEVICE BEING SCANNED Normal communications status
Scanning of connected slaves is being performed correctly.
3 TIMED-OUT Time-out state
There is no response from the slaves.
4 CONNECTION ERROR The UCMM (Unconnected Message Manager) connection cannot be
performed correctly.
5 CONNECTION BUSY Master/Slave connection is busy.
6 CONNECTION ERROR Master/Slave connection cannot be established.
7 INVALID VENDOR ID The vendor ID of the currently connected slave differs from the parameter
setting value.
8 VENDOR ID ERROR The vendor ID of the currently connected slave cannot be read.
9 INVALID DEVICE TYPE The device type of the currently connected slave differs from the
10 DEVICE TYPE ERROR The device type of the currently connected slave cannot be read.
11 INVALID PRODUCT CODE The product code of the currently connected slave differs from the
12 PRODUCT CODE ERROR The product code of the currently connected slave cannot be read.
13 INVALID INPUT SIZE The DI size of the currently connected slave differs from the DI SIZE
14 INPUT SIZE ERROR The DI size of the currently connected slave cannot be read.
15 INVALID OUTPUT SIZE The DO size of the currently connected slave differs from the DO SIZE
16 OUTPUT SIZE ERROR The DO size of the currently connected slave cannot be read.
23 SYNC FAULT Failed to synchronize Master/Slave connection.
?? ERROR Other error state
From here on, diagnostics numbers for slave number n (where, n=1 to
32) are numbers obtained by adding (n-1) x 2 to the diagnostics
number of slave No.1.
900
Communications status of slave No. n
+(n-1)×2
901
Status of slave No. n
+(n-1)×2
- 45 -
1.3 SETTING SLAVE FUNCTIONS
To use the DeviceNet slave functions, you must set the MAC-ID,
baud rate and address assignments.
The "MAC-ID (Media Access Control ID)" is the ID used for
identifying on the network the DeviceNet communications board that
is currently mounted on the CNC.
This MAC-ID is set to a value within the range 0 to 63, and must not
duplicate the ID of another node on the network. The "baud rate" is
the network's communicating speed. Set the same value as the baud
rate currently set for communications on the network. (Refer to the
baud rate setting of the master device currently used on the network.)
"Address assignment" refers to setting of the DI/DO sizes when I/O of
the DI/DO signals is performed and to setting of the PMC addresses
(addresses of R areas) that are used.
Setting Slave Functions on Series 16i/18i/21i-A/B
Procedure (CRT/MDI)
and then soft key [PMC] to switch to
the PMC screen.
(2) If you press soft keys [PMCDGN] → ([>])→ [I/OCHK] →

[D_NET] in that order, the DeviceNet Function initial screen
(screen 1.2 (a) below) is displayed.
If you press [SLAVE] in this screen, the slave function setup
screen (screen 1.3(a) or 1.3(c)) is displayed.
state.
(c) "DISABLE" must be selected at the "1 DIS/ENB" item.
Table 1.3(a) shows the setting items in this screen.

STATUS and COMMUNUNICATION STATUS are displayed in this
screen as diagnostics information used for verifying the
Table 1.3(b) describes this diagnostics information.
- 46 -
Switch between screens

Screen 1.3 (a) Slave functions setting screen (Series 16i/18i/21i-A) (1)
using page keys ↑ ↓ .
Screen 1.3 (b) Slave functions setting screen (Series 16i/18i/21i-A) (2)
- 47 -
Setting Slave Functions on Series 15i-A
Screen 1.3 (c) Slave functions setting screen (Series 15i-A)
Table 1.3(a) lists the items to be set up in this screen.

Table 1.3(c) lists the diagnostics information for verifying
communication statuses.
- 48 -
Display procedures
Procedure 1
displayed.
(2) If the bus parameter screen or slave parameter screen is
displayed, press soft key [SLAVE SETTING] in the operation
selection menu.
Procedure 2
displayed.
(4) If the bus parameter screen or slave parameter screen is
displayed, press [SLAVE SETTING] in the operation selection
menu.
Cursor/paging
If the master function is enabled:

- If the cursor is at "DI HOLD/CLEAR," pressing cursor key
moves the cursor to "DISABLE/ENABLE" in the bus
parameter screen.
- If the cursor is at "DISABLE/ENABLE", pressing cursor
key moves the cursor to "DI SIZE" in the slave
parameter screen for slave No. 032.
PAGE
- Pressing page key displays the bus parameter screen.
PAGE
- Pressing page key displays the slave parameter
screen for slave No. 032.
- 49 -
Table 1.3 (a): Setting items in slave function screen

Item Description
1.DIS/ENB Sets whether to disable or enable
(DISABLE/ENABLE) communications.
parameter setting. (For the 15i-A, use soft keys.)
Communications is started a few seconds after
setting ENABLE.
2.MAC-ID Sets the number for identifying on the network the
DeviceNet interface board mounted on the control
unit (CNC).
63.
3.BAUD-RATE Sets the baud rate.
The setting range is 0 to 2.
The baud rate for each setting is as follows:
0: 125 kbps
1: 250 kbps
2: 500 kbps
The baud rate is limited by the maximum network
length and other factors. For details, refer to
"Connecting DeviceNet Functions" in the
Connections section.
4 DI ADDRESS Set the areas to be used as the DI/DO data
5 DI SIZE buffers.
6 DO ADDRESS Set the leading buffer address and buffer size.
7 DO SIZE Use the R area as the address to be set.
8.STATUS ADDRESS Set the areas to be used as the status information
9.STATUS SIZE data buffer.
Set the leading buffer address and buffer size.
Use the R area as the address to be set.
10. DI HOLD/CLEAR Specify whether to hold or clear DI data if
communication is abnormal.
Note) See Chapter 2,
0: To hold DI data.
"Configuring a
Safe System." 1: To clear DI data.
- 50 -
When the Devicenet Slave Board (A20B-8100-0490) or Slave Board A(A20B-8100-0491)is used
Table 1.3 (b): Diagnostics information

(STATUS/COMMUNICATIONS STATUS)
Item Description
STATUS: DISABLE : Disables communications.
status)
occurred.
Check COMMUNICATION
STATUS and the status of
the master device.
INVALID MAC ID : The MAC-ID is not set
correctly.
DUPLICATE MAC ID : Duplicate MAC-IDs have
been set.
BUS FAULT : Bus error has occurred.
POWER ON ERROR : An error occurred when
the power was turned ON
or when ENABLE was set.
Check the DeviceNet
interface board mounting
state.
IDLE/ACTIVE Indicates the status of the Group 2 Master/Slave
Connection Set. "01" indicates an active state.
00: IDLE state

(Group 2 Master/Slave Connection Set is not
established.)
01: ACTIVE state
(Group 2 Master/Slave Connection Set is
established.)
CAN BUS STATUS1 Indicates the status information of the CAN
(Controller Area Network) bus. Status information
is expressed in hexadecimal with 1 byte
expressing each item of information. Each of the
bits of the status information is significant.
CAN BUS STATUS1 (1byte Data)

#7 #6 #5 #4 #3 #2 #1 #0
The meaning of bits is as follows.

#01 OL (1) : Online state
#1 BW (0) : Bus warning state
automatically stopped frame transfer.
Probable causes are an incorrect
baud rate setting or noise.
- 51 -
Table 1-3 (b) (continued): Diagnostics information

Item Description
CAN BUS STATUS1 #2 BO (0) : Bus OFF state
automatically turned offline. Probable
causes are an incorrect baud rate
setting or a hardware malfunction.
#3 A (1) : Network is active.
Data is being sent and received.
#4 TA (0) : Response error state
There is no response from the
communications destination within 25
to 50 msec. The communications
destination node may not exist on the
network.
#5 TO (0) : Time-out state
High priority data may be being
transferred excessively.
#6 RO (0) : Receive buffer overrun has occurred.
#7 ML (0) : Message lost has occurred.
CAN BUS STATUS2 CAN BUS STATUS2 (1byte Data)
#7 #6 #5 #4 #3 #2 #1 #0
[SA] [05] [02] [01] [--] [--] [BP] [ER]
The meaning of each bit is as follows.

#0 ER (0) : A CAN communications error has
occurred.
A probable cause is noise or a
hardware malfunction.
#1 BP (1) : Network power ON state
#2 --
#3 --
#7 SA (1) : The network scanner is active.
- 52 -
When the DeviceNet Slave Board B(A20B-8100-0650) is used
Table 1.3 (c): Diagnostics information

Item Description
STATUS 00 DISABLE Disables communications.
01 ENABLE Enables communications.
status)
03 ERROR Communications error has
occurred.
Check the status and error.
IDLE/ The display is in hexadecimal notation and consists of one byte.
ACTIVE The individual bits of the status information have their respective
meanings.
When the bits are 1, they mean:
#7 #6 #5 #4 #3 #2 #1 #0
[VR] [IC]
(A value enclosed in parentheses corresponds to a normal
communication status.)
#0 IC (1) : Initialization completed
#1 VR (1) : Valid-data-being-received flag
CONDITION 00 OFFLINE DISABLE has been selected.
STATUS
01 INITIAL COMPLETE The DeviceNet interface has
been initialized.
02 CHECK BAUDRATE A baud rate check is in
progress.
- If the specified baud rate is
incorrect, the operation is
halted in this status.
03 CHECK NODE DUPLICATION A check for a duplicate MAC-
ID specification is in
progress.
04 WAIT CONNECTION ONLINE The DeviceNet is waiting for
communication with the
master to begin.
The operation is halted in this
status if:
- A cable is broken or not
connected normally.
- The specified MAC-ID is
invalid in the master side.
- The DI/DO SIZE setting
does not match that in the
master side.
05 ONLINE Communication is effective
(normal communication
status).
06 WAIT CONNECTION TIMEOUT Communication is
interrupted.
- 53 -
Table 1.3 (c): Diagnostics information

Item Description
STATUS 80 HARDWARE ABNORMAL ERROR Check the error.
81 SETTING ERROR
82 NODE DUPLICATION ERROR
83 BUS OFF ERROR
(Undefined) WATCH DOG ERROR A failure has occurred on the
DeviceNet interface board.
ERROR 00 No alarm condition has
STATUS occurred. (Normal
communication status)
01 ROM ERROR A failure has occurred on the
02 RAM ERROR DeviceNet interface board.
03 DP-RAM ERROR
04 CAN ERROR
09 PARAMETER ERROR The setting is incorrect.
0B NODE DUPLICATION ERROR There is a duplicate MAC-ID

specification on the network.
0C BUS OFF ERROR This failure occurs if:
- The line is disturbed by
noise or any other
abnormal condition.
- A baud rate does not
match between nodes.
0D NETWORK POWER ERROR A failure has occurred in the
power supply for DeviceNet
communication.
(Undefined) WATCH DOG ERROR Another failure has occurred
on the DeviceNet interface
board.
Note) For the models other than Series 15i, only numbers are
displayed.
Setting the MAC-ID and baud rate

Set the node No. "2. MAC-ID" of this slave node and the baud rate "3.
BAUD RATE" to appropriate values referring to items 2 and 3 in
Table 1.3 (a).
- 54 -
Assigning DI/DO addresses

DI/DO areas are to be assigned. For example, to assign six bytes of DI
data (data input to the CNC from the master) to R1000 onwards and
assign two bytes of DO data (data output from the CNC to the master)
to R1100 onwards, set each of the data items as follows in screen
1.3(a) or 1.3(c).
4 DI ADDRESS = R1000
5 DI SIZE = 6
6 DO ADDRESS = R1100
7 DO SIZE = 2
DI/DO is assigned to R area signals as follows according to this

setting.
DI Assignments
R1000 1st DI data from master
R1001 2nd DI data from master
R1002 3rd DI data from master
R1003 4th DI data from master
DO Assignments
R1100 1st DO data to master
R1101 2nd DO data to master
When a DI only slave or a DO only slave is connected, set the value

of the parameter that specifies the size of the unused DO or DI to "0".
Assign DI/DO in the same way on the master device, too. For details
on how to set parameters on the master device, refer to the
Specifications Manual for the master device to be used.
NOTE
data so that area to be secured as each assigned
data item are not duplicated. Also, thoroughly check
before setting to prevent areas that are currently
used for other slave assignment addresses and PMC
ladder programs from being duplicated.
- 55 -
Assigning status information

Assign the status information. This information is used for verifying
the communications status on the PMC.
Set to parameters the address and size of the R area in which the
status information data is to be assigned.
When the Devicenet Slave Board (A20B-8100-0490) or Slave Board A(A20B-8100-0491)is used
Table 1.3(d) shows the relationship between the STATUS SIZE

setting values and the status information data to be assigned.
Table 1.3 (d): Relationship between STATUS SIZE setting values and
STATUS information
Setting
Item Description
Value
1 STATUS information This 1-byte data notifies the PMC of the
00h : Disables communications.
01h : Enables communications. (normal
03h : Communications error has
occurred.
For details, check the
COMMUNICATION STATUS and
status of the master device.
82h : Illegal MAC-ID
84h : Duplicate MAC-ID
8Eh : Bus error has occurred.
8?h : An error other than the above
occurred at start of
communications.
2 COMMUNICATION This 1-byte data notifies the PMC of the
STATUS: state of Group 2 Master/Slave
IDLE/ACTIVE Connection Set of the DeviceNet.
information 00h: IDLE state
01h: ACTIVE state
STATUS1 information
#7 #6 #5 #4 #3 #2 #1 #0

STATUS2 information
#7 #6 #5 #4 #3 #2 #1 #0
[SA] [05] [02] [01] [--] [--] [BP] [ER]

- 56 -
Setting the status information storage area

The content up to the STATUS SIZE setting value items (see Table
1.3(d)) is assigned continuously starting from the specified R area
signal.
For example, to assign four bytes of status information from R1500

5 STATUS SIZE = 4

to this setting.

R1500 STATUS information
R1501 IDLE/ACTIVE information
- 57 -
When the Devicenet Slave Board C (A20B-8100-0650) is used
Table 1.3(e) lists the relationships between the STATUS SIZE

settings and the status information assigned according to the settings.
Table 1.3(e) Meanings of status information

Item Value Description
STATUS (This 00h Communication is disabled.
1-byte data 01h Communication is enabled.
notifies the
PMC of the (Normal communication status)
communication 03h A communication error has occurred.
status.) Check the status and error.
IDLE/ACTIVE The individual bits have their respective meanings.
(This 1-byte When the bits are 1, they mean:
data notifies the (Values enclosed in parentheses corresponds to the normal
PMC of the communication status.)
communication #0 (1) Initialization completed. (Normal
status.) communication status)
#1 (1) Effective-data-being-received flag (normal
communication status)
CONDITION 00h DISABLE is selected.
STATUS (This 01h Initialization is completed.
1-byte data 02h A check on the baud rate is in progress.
notifies the 03h A check for a duplicate MAC-ID
PMC of the specification is in progress.
communication 04h The DeviceNet is waiting for
status.) communication to begin.
05h Communication is enabled.
(Normal communication status)
06h Communication is interrupted.
80h to 83h Communication is disabled.
For details, check the error.
Other values in a A failure has occurred on the DeviceNet
range between interface board.
00h and FFh
ERROR 00h No alarm condition has occurred.
STATUS (This (Normal communication status)
1-byte data 01h to 04h A failure has occurred on the DeviceNet
notifies the interface board.
PMC of the 09h The setting is incorrect.
communication 0Bh There is a duplicate MAC-ID specification
status.) on the network.
0Ch This failure occurs if:
- The line is disturbed by noise or any
other abnormal condition.
- A baud rate does not match between
nodes.
0Dh A failure has occurred in the power supply
for DeviceNet communication.
Other values in a A failure has occurred on the DeviceNet
range between interface board.
00h and FFh
- 58 -
Setting the status information storage area

Status information is assigned sequentially starting at the signal in the
specified R area.
For example, to assign four bytes of status information from R1500

5 STATUS SIZE = 4

to this setting.

R1500 STATUS
R1501 IDLE/ACTIVE
R1502 Status
R1503 Error
On the PMC, start communications using this status information. Also

use this status information to process on the PMC any
communications errors that may occur.
The error status of this status information is returned to the normal
communications status when the cause of the error is removed. So, if
the error status must be held, perform this operation on the PMC.
CAUTION
data so that areas to be secured as data do not
duplicate areas that are currently used for ladder
programs on the PMC.
- 59 -
1.3.1 Starting Communications
After you have finished setting up the parameters, start

communications by selecting ENABLE at the "1 DIS/ENB" item.
Move the cursor from DISABLE to ENABLE. After several seconds,
communications is started, and the STATUS display changes to
ENABLE as shown in screen 1.3.1 below.
Screen 1.3.1
Case of the Series 16i/18i/21i-A
After parameter setting is completed, setting DISABLE/ENABLE to

ENABLE triggers communication and changes the status indication to
ENABLE.
Cursor operations and switching of screens are not possible for a few
seconds until the connection for communications is established.
- 60 -
1.3.2 Slave Function Data Refresh Rate
The "data refresh rate" is the time required for the control unit (CNC)
to update all I/O signals assigned to the R areas.
NOTE
The data refresh rate does not indicate the I/O
response time on the network. The I/O response
time is dependent on the condition of the network.
Table 1.3.2(a) shows the relationship between the total number of

DI/DO communications points and the data refresh rate in the slave
function.
Table 1.3.2 (a)

Total Number of Slave Communications Points Data Refresh Rate
1 to 64byte 8ms
The relationship changes as follows when master functions are used

together with slave functions.
Table 1.3.2 (b)

Number of DI/DO Communications Points (byte) Data Refresh Rate
1 to 32 8ms
33 to 64 16ms
* A maximum of 32 bytes of DI/DO is updated every 8 msec.
CAUTION
This data refresh rate sometimes changes according
to the configured options taking the overall
performance of the CNC into consideration.
- 61 -
Setting Slave Functions on Power Mate i-D/H
On the Power Mate i-D/H, slave functions can be set using the regular
parameters.
NOTE
1 When the DeviceNet parameters have been set, the
power must be turned OFF temporarily.
2 In the case of Power Mate i-D two-path control,
setting can be performed only from the 1st path.
Procedure when using CRT/MDI

The setup procedure is exactly the same as the Procedure (CRT/MDI)
in "Setting Slave Functions on the Series 16i/18i/21i-A/B" described
earlier. For details, see this item.
Procedure when using DPL/MDI

DGNOS
(1) Press the PARAM key to switch to the parameter screen.
parameters.
Procedure when using the DPL/MDI operation package (PC)

F4
(1) Press the DGN
PRM
key to switch to the parameter screen.
parameters.
- 62 -
Parameters
28000 Enable/disable communications
[Data type] Byte

[Data range] 0, 1
Sets whether to disable or enable communications. Communications
is started when this parameter is set to "1" and the power is turned ON
again.
1.3(a) or 1.3(c).
28001 MAC-ID
[Data type] Byte

Sets the number for identifying on the master device the DeviceNet
interface board mounted on the control unit (CNC).
1.3(a) or 1.3(c).
28002 Baud rate
[Data type] Byte

[Data range] 0 to 2
Sets the baud rate. Set the same value as the baud rate of the master
device as the setting value.
This parameter is equivalent to the "3 BAUD-RATE" setting in screen
1.3(a) or 1.3(c).
Setting Value Baud rate
0 125Kbps
1 250Kbps
2 500Kbps
28010 DI data buffer area
[Data type] Byte

[Data range] 0
Sets the area to be used as the DI data buffer. Use the R area as the
address to be set.
This parameter is equivalent to the buffer area setting in "4 DI
ADDRESS" in screen 1.3(a) or 1.3(c).
0 R area
- 63 -
28011 DI data buffer address
[Data type] Word

Sets the area to be used as the DI data buffer. Set the leading address
of the buffer.
This parameter is equivalent to the buffer address setting in "4 DI
28012 DI data buffer size
[Data type] Byte

Sets the area to be used as the DI data buffer. Set the size of the buffer
within the range 0 to 64.
This parameter is equivalent to the "5 DI SIZE" setting in screen
1.3(a) or 1.3(c).
28013 DO data buffer area
[Data type] Byte

[Data range] 0
Sets the area to be used as the DO data buffer. Use the R area as the
address to be set.
This parameter is equivalent to the buffer area setting in "6 DO
0 R area
28014 DO data buffer address
[Data type] Word

of the buffer.
This parameter is equivalent to the buffer address setting in "6 DO
28015 DO data buffer size
[Data type] Byte

Sets the area to be used as the DO data buffer. Set the size of the
This parameter is equivalent to the "7 DO SIZE" setting in screen
1.3(a) or 1.3(c).
- 64 -
28016 Status information data buffer area
[Data type] Byte

[Data range] 0
Sets the area to be used as the status information data buffer. Use the
R area as the address to be set.
This parameter is equivalent to the buffer area setting in "8 STATUS
0 R area
28017 Status information data buffer address
[Data type] Word

Sets the leading address of the status information data buffer. Set the
leading address of the buffer.
This parameter is equivalent to the buffer address setting in "8
STATUS ADDRESS" in screen 1.3(a) or 1.3(c).
28018 Status information data buffer size
[Data type] Byte

[Data range] 0 to 4
Sets the size of the status information data buffer. Set the size of the
This parameter is equivalent to the "9 STATUS SIZE" setting in
screen 1.3(a) or 1.3(c).
28019 Holding/Clearing the DI data
[Data type] Byte

[Data range] 0, 1
Sets the state of the DI data when communication is not normal.
This parameter is equivalent to the "10 HOLD/CLEAR" setting in
screen 1.3(a) or 1.3(c).
0 Holding the DI data
1 Clearing the DI data
- 65 -
2.CONFIGURING A SAFE SYSTEM OPERATION B-63404EN/03
2 CONFIGURING A SAFE SYSTEM

This chapter describes how to configure a safe system when creating a
system using DeviceNet functions.
- 66 -
B-63404EN/03 OPERATION 2.CONFIGURING A SAFE SYSTEM
2.1 TROUBLESHOOTING COMMUNICATIONS ERRORS
Using the Series 16i/18i/21i-A/B (DeviceNet function software series 6576/edition 02

or earlier)
With this DeviceNet function, assignment data is not updated when a

communications error occurs. For this reason, DI data is held at the
state that was active when the alarm was detected.
Using the Series 16i/18i/21i-A/B (DeviceNet function software series 6576/edition 03

or later) or Series 15i-A
In this DeviceNet function, whether to hold or clear the DI data when

a communication error has occurred can be selected by setting the DI
HOLD/CLEAR parameter as follows:
DI HOLD/CLEAR
0: The DI data is held in the state where it was when an alarm
condition was detected.
1: The DI data is cleared.
When designing the system, design the system so that the status of the
status information is monitored at all times and the system operates
stably. You can also prepare signals in DI/DO data, by which data is
exchanged, for indicating whether or not communications is being
performed instead of using the status information, and you can also
judge whether or not communications is being performed normally by
monitoring whether or not chose signals are being read. On the slave
system side, start and continue operations after receiving permission
from the master device.
- 67 -
2.CONFIGURING A SAFE SYSTEM OPERATION B-63404EN/03
2.2 HANDLING MULTIPLE-BYTE DATA
With this DeviceNet function, data communications on the network

and updating of data assigned to PMC R area are performed
asynchronously. For this reason, handling of data of two bytes or
longer must be synchronized on the PMC (in the ladder program).
For example, when multiple-byte DI data is read from the master
device on a slave, signals for acquiring synchronization must be
provided before and after the data, DI data must be read when the
synchronizing signals set by the master device is correctly read by the
slave, and the slave must reset the synchronizing signals when it has
finished reading the DI data and then notify the master device that it
has finished reading the DI data.
- 68 -
III. CONNECTION
B-63404EN/03 CONNECTION 1.CONNECTING DeviceNet FUNCTIONS
1 CONNECTING DeviceNet FUNCTIONS

This chapter describes information relating to connecting DeviceNet
functions.
Refer to issued DeviceNet specifications from ODVA about the
standard of DeviceNet.
NOTE
The following DeviceNet connecting fixtures are
made available but not supplied by FANUC. Buy
connecting fixtures that comply with the DeviceNet
standard from a third party.
• Communications cables
• Communications power supply
• Terminator
• T-branch tap
• Power supply tap
• Crimped terminals
Trademark
DeviceNet is a trademark of ODVA (Open
DeviceNet Vendor Association.)
- 71 -
1.CONNECTING DeviceNet FUNCTIONS CONNECTION B-63404EN/03
1.1 CONNECTING DeviceNet
With FANUC DeviceNet, one DeviceNet board is needed for each

network. The number of networks that can be connected and available
functions is limited to the machine type.
Machine Type Number of Networks Function

FS16i/18i/21i
1 Master or slave
(LCD-mounted type)
FS16i/18i/21i
Master 1 control, Slave
(Stand-alone type) 2
1 control
and Power Mate i
1) Master function
The "master function" refers to controlling I/O of other slave
units to be connected on the network with the CNC as the master
unit as shown in the figure below.
Master
(CNC)
#3 #4 #5 #6 #N
• • •
-Slaves
Up to 32 slaves can be connected to a single master.
2) Slave function
Master Master
(group 1) #1 (group 2) #2
slave slave slave slave slave slave slave

(CNC) (CNC)
#11 #12 #21 #13 #22 #23 #24
DeviceNet-Slaves
Master/Slave Combinations
Group Master Slave
1 #1 #11,#12,#13
2 #2 #21,#22,#23,#24
Up to 64 devices, including masters and slaves, can connected on a

single network.
- 72 -
1.2 DeviceNet CABLES
There are two types of DeviceNet cable: thick cable and thin cable.
Normally, thick cable is used as the trunk line when a long-distance
network is required. Normally, thin cable is used as branch cable as it
is thinner and more flexible than thick cable. Thin cable can also used
as the trunk in short-distance networks.
Use cables that comply with the DeviceNet standard.
- 73 -
1.3 CABLE LENGTH AND BAUD RATE
There are some restrictions in configuring a network: maximum

network length, branch length and total branch length. These factors
are also restricted by the baud rate.
Maximum network length

The "maximum network length" refers to whichever is longer, the
distance between furthermost nodes or the distance between
terminators.
Whichever of these is longer is the maximum

network length.
Terminator Terminator
T-branch tap Node T-branch tap

Branch
Node length
Node
Branch length Node
Communications
power supply
The following table shows the maximum network length according to

cable type.
Cable Type Maximum Network Length

Thick cable (5-wire) 500m
Thin cable (5-wire) 100m
NOTE
Thin cable can also be used as the trunk if the
maximum network length is within 100 m. In this
case, also pay attention to the maximum current
capacity of the cable so that this limit value is not
exceeded.
The maximum network length is also limited by the baud rate.
Maximum Network Length Maximum Network Length

Baud Rate When Only Thick Cable Is When Only Thin Cable Is
Used Used
500 K bit/sec 100m
250 K bit/sec 250m 100m
125 K bit/sec 500m
- 74 -
NOTE
When Thick Cable Is Used Together With Thin
Cable
A mixture of thick cable and thin cable can be used
for the cable connecting furthermost nodes. Note,
however, that in this case, the line lengths of each
type of cable must satisfy the expression in the
following table. So, the total network length becomes
shorter than when the network is configured by
connecting only thick cable.
Prevent the maximum current consumption of the cables from being

exceeded.
Baud Rate Maximum Network Length

500 K bit/sec Lthick + Lthin < 100m
250 K bit/sec Lthick + 2.5 × Lthin < 250m
125 K bit/sec Lthick + 5 × Lthin < 500m
Lthick: Length of thick cable, Lthin: Length of thin cable
Example
Maximum network length
1m 100m 25m 40m 1m

T-branch tap Node T-branch tap
3m
Node
5m
2m Node
Branch length Node
Communications
power supply
Baud Rate Maximum Network Length Acceptability

500 K bit/sec Lthick + Lthin=175 < 100m NG
250 K bit/sec Lthick + 2.5 × Lthin = 125 + 2.5 × 50=250 < 250m OK
125 K bit/sec Lthick + 5 × Lthin = 125 + 5 × 50 = 375 < 500m OK
According to the above calculation, communications at 250 kbit/sec

and 125 kbit/sec is possible in this case. Note, however, that a
network cannot be configured if the maximum allowable current
consumption of the cables is exceeded even if the above conditions
are satisfied.
- 75 -
Branch length
The "branch length" refers to the longest value from where the trunk
is divided into a branch up to the first node connected to the branch.
The maximum branch length is 6 m.
Branches can be sub-divided into further branches.
Calculation example
Trunk line Trunk line
T-branch tap A to node A: 6 m
T-branch tap T-branch tap A T-branch tap A to node B: 5 m
T-branch tap A to node C: 6 m
Branch length (max. 6 m) 4m
All branches are within 6 m.
T-branch tap B
2m 1m
Node
Node B
Node A
1m
Node C
Branch length
Total branch length

The "total branch length" refers to the length obtained by totaling the
length of all branches. The total branch length is sometimes exceeds
this restriction even if all of the branches is within 6 m. Also, the total
branch length restriction also varies according to the baud rate.
Baud Rate Maximum Total Branch Length

500 K bit/sec 39m
250 K bit/sec 78m
125 K bit/sec 156m
Calculation example
T-branch T-branch tap C
tap A
4m 6m T-branch tap A to T-branch tap B: 4 m
T-branch tap B to Node A: 2 m
T-branch tap B
T-branch tap B to Node B: 1 m
2m 1m Node B to Node C: 1 m
Node D
Node B T-branch tap C to Node D: 6 m
Node A 1m
Node C The total branch length is 12 m.
- 76 -
1.4 TERMINATOR
To reduce the influence of signal reflection and ensure more stable

communications, terminators must be attached to both ends of the
trunk. Terminators need not be attached to the ends of branches. Do
not attach terminators to the ends of branches; attach them only to the
ends of the trunk.
The following shows the specifications and how to connect a
terminator.
CAN L(2)
R = 121O, 1/4w
Allowable resistance error: 1%
Metal sheath
CAN H(4)
NOTE
Numbers in parentheses () indicate the connector
pin No.
Install the terminator within 1 m of the end (node or
T-branch tap) of the branch line.
1m
Terminator
T-branch tap
Node
- 77 -
1.5 CONNECTOR
Connector
DeviceNet interface connector
Terminal No. Signal Name Color Code Signal Type

1 V- Black Signal cable - side
2 CAN L Blue Communications data Low side
3 SHIELD Bare Shield
4 CAN H White Communications data High side
5 v+ Red Signal cable + side
Cable connector:
Manufactured by Phoenix Contacts Inc.
MSTB2.5/5-ST-5.08AU (provided with the product)
Applicable cable conductor AWG24-12
Connecting the communications cable

Connect the communications cable to the DeviceNet interface
connector according to the following procedure.
(1) Strip about 30 mm of the cable sheath and remove unwanted

sheath.
(2) Peel off the aluminum tape covers the signal leads and the power
leads, and strip the sheath of the signal leads and power leads
matched to the length of the crimped terminals.
(3) Twist the stripped signal leads and power leads and attach the
crimped terminals.
We recommend the following crimped terminal:
• Phoenix Contacts Inc. AI series (special tool ZA3)
(4) Loosen the cable fastening screws on the connector so that the
line materials can be easily inserted.
(5) Insert each of the signal leads into the holes on the connector
terminal plate so that the sheath colors of the shielded lead,
signal leads and power leads match the colors indicated on the
connector.
(6) Tighten the power leads in place with the cable fastening screws
on the connector.
Two thin cables can be connected to this connector in a multi-drop

configuration. In this case, insert two leads into a single hole on the
terminal plate. Thick cable cannot be used in a multi-drop
configuration. In a multi-drop configuration, use T-branch taps.
- 78 -
- Connector (DeviceNet boards B and C)

Cable-end connector for DeviceNet boards B and C:
Manufactured by Hirose Electric Co., Ltd.
HR31-5.08p-5SC (plug) and
HR31-SC-121 × 5 pieces (crimp terminals)
Applicable cable conductor 0.25 to 1.65 mm2
The plug is shipped along with DeviceNet boards B and C. The plug
has a label indicating a color code. No crimp terminal is shipped
unless separately ordered. (A02B-0259-K211).
NOTE
No crimp terminal is shipped along with DeviceNet
board B or C.
- Connecting the communication cable (DeviceNet boards B and C)

To attach a communication cable to the DeviceNet interface
connector, follow this procedure.
(1) Remove the sheath of the cable to a length of about 30 mm, and
cut off the excess shielding.
(2) Remove the aluminum tape from around the signal and power
supply wires. Also remove the insulator from each wire to a
length of about 5 mm.
(3) Twine the stripped signal wire strands. Also twine the stripped
power supply wire strands. Attach a crimp terminal to each
bundle of wire strands.
To crimp the terminal, use a crimp tool complying with JIS
C9711 by setting its indication to 1.25.
Recommended crimp tool:
HR31-TC-01 manufactured by Hirose Electric Co., Ltd.
(4) Insert the shielding wire, signal wire, and power supply wire into
the plug by matching their insulator colors to the color codes
indicated on the connector.
When attaching each crimp terminal to the plug, keep them in
the orientation shown below.
Crimp terminal Wire
(5) Insert the plug into the DeviceNet board, and fasten it with its
bolts using a No. 0 cross-head bit.
These crimp terminals are of a multidrop type. Each terminal can be

used to crimp two thin cable wires together. They are not for thick
cables.
- 79 -
- Pulling out crimp terminals (DeviceNet boards B and C)

If you made a misconnection, correct it by pulling out the crimp
terminal according to this procedure.
A rod 1 mm in diameter can be used to pull out a crimp terminals.
Recommended tool: HR31-SC-TP manufactured by Hirose Electric
Co., Ltd.
(1) Push a pull-out tool against the molded lance. (See Fig. 1.)
(2) While pushing the molded lance, tilt the pull-out tool to release
the crimp terminal lock. (See Fig. 2.)
(3) Pull out the pull-out tool.
(4) Pull the wire to take out the crimp terminal.
Molded lance Molded lance
Wire Wire
Pull-out tool Pull-out tool

Fig. 1 Fig. 2
- Extending the line (DeviceNet boards B and C)

Adding a CNC to the existing line requires another crimp terminal
A02B-0259-K211.
(1) Pull out the crimp terminal from the plug of the CNC at the last
stage of the line.
(2) Detach the existing communication cable from the crimp
terminal.
(3) Attach the detached communication cable and an additional
communication cable to a new crimp terminal, and insert it to the
plug.
For details, see "Connecting the communication cable (DeviceNet
boards B and C)."
- 80 -
1.6 GROUNDING THE CABLE WIRES
Wire the cable referring to the figure below when connecting the
cable to the connector.
DeviceNet
Communications
Board
power supply
V- V+ FG
Connector 100 ? min.
1 2 3 4 5
Drain wire/shield
Signal line (CAN_L)
Signal line (CAN_H)
Power line (V-)
Power line (V+)
Grounding the network

In the DeviceNet specification, it is recommended that only one place
on the network be grounded and a place as near as possible to the
center of the network be grounded to prevent a ground loop.
As shown in the figure above, connect the shielded lead of the cable
to frame ground (FG) for the communications power supply and
ground FG to a maximum resistance of 100.
When multiple power supplies are used, connect and ground the
shielded lead only at the power supply near the center of the network.
Do not connect the shielded lead to the frame ground of other power
supplies, and ground these FGs to a maximum of 100. When you use
multiple power supplies, user a special power supply tap made by
other manufacturers.
Only one communications power supply:
T-branch tap or power supply tap
Power
Master supply Slave
Two or more communications power supplies:
Ground at only one location near the center

Power supply
tap
Power Power Power

Master supply Slave supply Slave supply
- 81 -
Obtaining a ground lead

There are three ways of obtaining a ground lead:
• By drawing out from the connector to which the communications

cable is connected
Insert the ground lead into the same hole as the shielded lead
of the communications cable and fix in place.
• By drawing out from the T-branch tap
Connect only the ground lead to one of the connectors on the
T-branch tap.
• By using the cable clamp
Ground the communications cable shield by the cable clamp,
and connect the communications power supply ground to the
clamp base.
NOTE
Be sure to ground the shield lead of each
communications cable. If there is even one place
that is not grounded, the shielding effect of the entire
network is impaired.
- 82 -
1.7 CABLE CLAMP
The cable clamp has two functions: to support the cable and to shield
the cable. As shown in the figures below, peel off part of the cable
sheath to expose the outer shield cover, and press this part against the
earth plate with the earth plate.
Earth plate
Cable
Cable clamp
Earth plate
Shield
Cable sheath
- 83 -
1.8 COMMUNICATIONS POWER SUPPLY
With DeviceNet, power must be supplied for communications. Use a

power supply that satisfies the specifications shown in the table below
and that has insulated AC input and DC output as the communications
power supply. Also, select a communications power supply having
margin in its current capacity greater than the total current
consumption of all nodes to which power is to be supplied.
Communications Power Supply Specifications

Item Specifications
Output voltage 24VDC ± 1%
Output current 16 A max.
Input fluctuation Max. 0.3%
Load fluctuation Max. 0.3%
Influence of ambient temperature Max. 0.03%/°C
Output ripple 250mVp-p
Output side capacity Max. 7000 µF
Ambient temperature During operation : 0 to 50°C
During storage : -40 to +85°C
Inrush Current Limit Less than 65 A (peak)
Protection against overvoltage Provided
Protection against overcurrent Provided (max. current 125%)
Startup time 250 ms up to 5% value of final output
voltage
Overshoot at startup Max. 0.2%
Insulation Across output and AC power supply,
and output and housing
Compliant standards Necessary : UL
Recommended : FCC Class, B, CSA
TUV, VDE
Ambient humidity 30 to 90% (no condensation allowed)
Surge current Max. 10%
Be sure to supply power from the trunk down to the branches. The
maximum current capacity of the communications cable is 8A on
thick cables and 3A on thin cables.
The communications power supply is connected in various forms
depending on the user's power supply requirements.
The current capacity of the branch varies according to the branch

length. The longer the branch, the smaller the branch's maximum
current capacity becomes. The same applies if the cable used as the
branch is thick cable or thin cable. Calculate the possible current
capacity (I) on a single branch (the total current that is consumed on
each branch) according to the following expression:
I = 4.57/L I: Allowable current (A)

L: Branch length (m)
- 84 -
1.8.1 Designing a Power Supply Connection
Design the power supply connection in the following order:
(1) Provisional determine the position of the power supply.

(2) Calculate the current consumption of all nodes to be located on
the network.
(3) Calculate the length at the provisional position, and calculate a
rough value for the current that can be supplied to the cable
according to the graph.
(4) Verify whether or not the supplied current satisfies the current
consumption.
(5) Change the position of the power supply and verify again.
(6) If the conditions are not satisfied by the simple calculation
according to the graph in step (3), calculate the supplied current
according to the calculation expression and verify again.
(7) If the conditions in the calculation expression are not satisfied in
step (6), provide two or more power supplies, separate the power
supply paths, and verify whether or not the supply current
satisfies the conditions for each of the power supplies.
1.8.2 Determining the Power Supply Locations
Power supplies can be located in the four configurations shown

below.
In principle, select configurations (1) and (2).
If the power supply conditions are not satisfied in configurations (1)
and (2), study the use of configuration (3). To provide two or more
power supplies for the simultaneous supply of power, configuration
(4) is also possible.
(1) When nodes are located both sides of the power supply:
Power supply tap

Terminator or T-branch tap Terminator
Node Node Node Node Node
Communications
power supply
(2) When the nodes are located to one side of the power supply:
NOTE
We recommend the configuration in (1) when
supplying power to many nodes from a single power
supply.
- 85 -
(3) When the power supply path is separated between two or more
power supplies:
Path 1 path 2
Power supply tap Power supply tap Terminator
Terminator
Communications Communications
power supply power supply
Remove the fuse and separate V+. Fuse

V+ Set V- common to
V- paths 1 and 2.
24V 0V
(4) When two or more power supplies are provided to

simultaneously cover all of the nodes in between:
Power supply tap Power supply tap
Communications Communications
power supply power supply
NOTE
If the current capacity flowing to the thick cable
exceeds 8A even if the position of the
communications power supply is changed, the power
supply conditions cannot be satisfied by one power
supply. So, use two or more power supplies.
When thick cable is used in the configuration in (1),
there will be no problems if the current capacities on
both sides of the trunk from the communications
power supply are both 8A or less. For this reason, a
configuration up to a maximum current capacity of
16A is possible.
If the current capacity flowing to the thin cable
exceeds 3A when thin cable is used for the trunk,
verify whether or not the conditions are satisfied by
changing to thick cable.
- 86 -
Factors for determining the power supply locations

Two factors for determining whether or not current can be supplied
normally are the current capacity required by each node and voltage
drop on the cable. Calculate the following two values beforehand:
• Current capacity required at each node
• Distance from the power supply(ies)
How to calculate the power supply

There are two ways of calculating the power supply for the trunk:
1) Simple calculation according to the graph
2) Calculation by calculation expression (Voltage drop is calculated
from the resistance of the communications cable and the current
consumption.)
NOTE
Calculate the power supply so that the conditional
expression for the current consumption on branches
according to the branch length is satisfied for each
branch.
Distance to furthest node on trunk Regarded as no

or to branch tap from power supply distance
Terminator Power supply tap Node Node Node Node Terminator
Communications
power supply
• The conditions are sometimes satisfied by calculating using the

calculation expression even if the power supply conditions are
not satisfied by calculating simply according to the graph. In this
case, locating the power supply at a hypothetical position poses
no problem.
NOTE
When using a common power supply for
communications and the NC, the power supply
cannot be calculated by graph-based simple
calculation in the following item. Calculate the power
supply according to the calculation expression.
- 87 -
1.8.3 Verification by Graph-Based Simple Calculation
Voltage drop occurs when current flows to the communications cable.

The longer the communications cable, the larger the current value
becomes and the larger the voltage drop occurs.
The voltage of the communications power supply at each node must
be 11 VDC or more.
The following tables and graphs show the maximum current for each
cable thickness by which a sufficient voltage can be supplied to the
communications power even if a voltage drop occurs.
• Thick cable
Thick cable (m) 0 25 50 100 150 200 250 300 350 400 450 500
Max. current (A) 8.00 8.00 5.42 2.93 2.01 1.53 1.23 1.03 0.89 0.78 0.69 0.63
6
Max. current (A)
0
0 50 100 150 200 250 300 350 400 450 500
Thin cable (m)
• Thin cable
Thick cable (m) 0 10 20 30 40 50 60 70 80 90 100
Max. current (A) 3.00 3.00 3.00 2.06 1.57 1.26 1.06 0.91 0.80 0.71 0.64
3
Max. current (A)
0
0 10 20 30 40 50 60 70 80 90 100
Thin cable (m)
- 88 -
Graph-based simple calculation

The items must be checked in order (1) to (3) for each of the nodes
located in the same direction viewed from the power supply.
If nodes are located on both sides of the power supply, items (1) to (3)
must be checked in each direction.
(1) Calculate total current consumption (A) for all nodes located on
the network in each direction.
(2) Calculate from the graph maximum current (B) that can flow to
the cable based upon the cable type (thick or thin) and the
distance to the furthermost end on the trunk from the power
supply.
(3) If total current consumption (A) calculated in (1) is less than or
equal to maximum current (B) calculated in (2), this means that
the power supply conditions are satisfied for all nodes.
NOTE
The graph to refer to varies according to the cable
type (thick or thin) used for the trunk.
Remedies
If total current consumption (A) calculated in (1) is greater than
maximum current (B) calculated in (2), study the following:
• Move the power supply towards the center to configure the
network so that nodes are located on both sides of the power
supply.
• If nodes are already located on both sides of the power supply,
move the power supply towards the direction on which the larger
current consumption is required.
• Swap with thick cable if thin cable is used.
If A is grater than B in any of the above measures, study the positions

of the nodes according to the calculation expression taking into the
actual positions of the nodes.
When the power supply unit is located at the one of the network (example 1):
The following shows an example where thick cable having a total
length of 200 m is used for the power supply, and the communications
power supply is located at the end of the network.
In this example, the current consumptions of each node are assumed
to be as shown in the following figure.
200m
Terminator Power supply

tap Node Node Node Node Terminator
0.1A 0.25A 0.05A 0.25A
Trunk line (5-lead cable)
Communications
power supply
Total length of power supply line = 200 m

- 89 -
Total current consumption = 0.1A + 0.15A + 0.05A + 0.25A = 0.65A

Maximum possible current calculated from the table for thick cable =
1.53A
The relationship becomes "total current consumption is less than the
maximum current," so you can verify that power can be supplied to all
nodes.
When the power supply unit is located at the center (example 2):
power supply is located at the center of the network.
As the communications power supply is located in the center of the
network, the maximum current flows to both the left and right of the
power supply. For this reason, a current twice the maximum current
can be supplied compared with when the communications power
supply is located at the end of the network.
Power supply tap

120m 120m
Terminator Within Terminator

Node Node Node Node
3m
0.1A 0.45A 0.25A 0.3A
Communications
power supply
Total length of power supply line (left side) = Total length of power
supply line (right side) = 120 m
Total current consumption (left side) = 0.1 A + 0.45 A = 0.55 A
Total current consumption (right side) = 0.25 A + 0.3A = 0.55 A
Maximum current (left side) calculated from the table for thick cable
= Approx. 2.5 A
Maximum current (right side) calculated from the table for thick cable
= Approx. 2.5 A
(The above values are calculated by linear approximation between
100 and 150 m.)
The relationship becomes "total current consumption (left side) is less

than the maximum current (left side)" and the "total current
consumption (right side) is greater than the maximum current (right
side)," so you can verify that power can be supplied to all nodes.
- 90 -
When current consumption is uneven on either side of the power supply unit (example 3)
power supply is located by moving it slightly away from the center of
the network.
If the total current consumption is uneven on either side of the power
supply unit and is insufficient even if the communications power
supply is located in the center of the network, the current
consumption conditions are sometimes satisfied by moving the power
supply unit slightly.
When the power supply unit is located in the center:
Power supply tap

120m 120m
Terminator Within Terminator

Node Node Node Node Node Node
3m
1.1A 1.25A 0.5A 0.25A 0.25A 0.85A
Communications
power supply
Total length of power supply line (left side) = Total length of power
supply line (right side) = 120 m
Total current consumption (left side) = 1.1A + 1.25A + 0.5A = 2.85A
Total current consumption (right side) = 0.25A+0.25A+0.85A=1.35A
= Approx. 2.5 A
= Approx. 2.5 A
100 and 150 m.)
The relationship becomes "total current consumption (left side) is

greater than the maximum current (left side)," so it can be seen that
the current consumption is insufficient on the left side.
To remedy this, move the position of the power supply unit to the left
as shown in the figure below.
Power supply tap

100m 120m
Terminator Node Terminator

Node Within Node Node Node Node
3m
1.1A 1.25A 0.5A 0.25A 0.25A 0.85A
Communications
power supply
Total length of power supply line (left side) = 100 m
Total length of power supply line (right side) = 140 m
- 91 -
Total current consumption (left side) = 1.1A + 1.25A = 2.35A

Total current consumption (right side) = 0.5A+0.25A+0.25A+0.85A=
1.85A
= 2.93A
= Approx. 2.1 A
100 and 150 m on the right.)
As a result, the relationship becomes "total current consumption is

greater than the maximum current" for both the left and right sides, so
you can verify that power can be supplied to all nodes.
- 92 -
1.8.4 Verifying by Calculation Expression
If the conditions cannot be satisfied by simply calculating from the

graph, verify the conditions according to the actual positions of each
node and the communications power supply.
With DeviceNet, the maximum voltage drop allowed in a system is
stipulated as 5V for each of the power supply lines (V+, V-) based
upon the voltage specifications (24 VDC) of the communications
power supply and the input voltage specifications (11 to 25 VDC) of
the communications power supply for each device.
This 5 V voltage drop comprises an allowable voltage drop of 4.65A
on the trunk and an allowable voltage drop of 0.35V on the branches.
The approach for considering voltage drop in the cable is as follows.
In the DeviceNet standard, the voltage drop in the communications
cable is stipulated to within 5 V or less including margin taking into
consideration the voltage specifications (24 VDC) and the input
voltage specifications (11 to 25 VDC) of the communications power
supply of each device.
Voltage drop at V+ (VA)
V1 V2
Voltage drop at V- (VB)
Supply voltage to each node
Supply voltage of communications power supply
V1: Supply voltage of communications power supply. Set V1 to 23 V

taking into consideration the fluctuation range of the power
supply voltage.
V2: Supply voltage to each node. Set V2 to > 13 V taking the margin
into consideration.
VA: Voltage drop at power cable V+
VB: Voltage drop at power cable V-
On DeviceNet, set VA to less than or equal to 5V and VB to less
than or equal to 5V.
The voltage drop on the communications cables is stipulated at 5V or

less on each of the power lines (V+, V-).
This 5 V voltage drop comprises an allowable voltage drop of 4.65A
on the trunk and an allowable voltage drop of 0.35V on the branches.
Calculation expression
Fist, investigate the distance between the power supply and each of
the nodes, and the current consumption of the communications unit on
each device.
Then check whether or not the following conditional expression is
satisfied. If the conditional expression is satisfied, the conditions for
power supply to each node are satisfied. However, prevent the
maximum current capacity (thick cable: 8A, thin cable: 3A) of the
cables from being exceeded.
- 93 -
These conditions cannot be used if one power supply is shared as the

communications power supply and the NC power supply. This must
be studied separately.
• Conditional expression (totalizing expression of voltage drop on

trunk)
Σ (Ln × Rc+Nt × 0.005) × ln < 5V
Ln: Distance between power supply and node (excluding

branch length)
Rc: Maximum cable resistance (thick cable: 0.015Ω/m, thin
cable: 0.069Ω/m)
Nt: Number of taps between each node and power supply
In: Current consumption required for communications units on
each node
0.005Ω = Contact resistance of tap
- 94 -
When nodes are located to one side of the power supply (configuration example 1)
50m
30m
Power 1m
supply tap
Trunk line: thick cable
50mA 30mA 50mA

Node Node Node
Communications 40mA 30mA 50mA

power supply
Node Node Node
Branch: thin cable 8 units 10 units
5 units
40mA 30mA 50mA
Node Node Node
Communications <Group 1> <Group 2> <Group 3>
power supplies 50mA+40mA×5=250mA 30mA×8=240mA 50mA×10=500mA
The voltage drop is calculated for each group.

Group 1 : (1×0.015+1×0.005) × 0.25=0.005V
Group 2 : (30×0.015+2×0.005) × 0.24=0.1104V
Group 3 : (50×0.015+3×0.005) × 0.50=0.3825V
Total voltage drop = 0.005 + 0.1104 + 0.3825 = 0.4979V ≥ 4.65V
So, in this configuration example, the conditional expression is not
satisfied.
When nodes are located both sides of the power supply (configuration example 2)
Path 1 Path 2
30m
20m 10m
Trunk line: thick cable
Terminator Power supply tap Terminator
50mA 30mA 50mA

Node Node Node
40mA Communications 30mA 50mA

Branch: thin cable Node power supply
Node Node
8 units 10 units
5 units
40mA 30mA 50mA
Node Node Node
Communications <Group 1> <Group 2> <Group 3>
power supplies 50mA+40mA×5=250mA 30mA×8=240mA 50mA×10=500mA
The voltage drop of each group is calculated for each path.

Group 1 of path 1 : (20 × 0.015+1 × 0.005) × 0.25=0.07625V
Group 2 of path 2 : (10 × 0.015+1 × 0.005) × 0.24=0.0372V
Group 3 of path 2 : (30 × 0.015+2 × 0.005) × 0.50=0.23V
Voltage drop on path 1 =0.07625V<4.65V
- 95 -
Total voltage drop on path 2 =0.0372V+0.23=0.2672V<4.65V

So, in this configuration example, the conditional expression is
satisfied on both paths.
1.8.5 Supplying Multiple Power Supplies on Separated Paths
When the conditions cannot be satisfied even by calculating with the

calculation expression, use two or more communications power
supplies and separate the power supply paths.
How to separate power supply paths

As two or more power supplies are used, use power supply taps for
each of the power supplies. Power supply taps are not provided by
FANUC. Power supply tapes that comply with the DeviceNet
standard must be purchased separately from another manufacturer.
The figure below shows the internal circuit of the power supply tap.
Power supply tap

Fuse A Fuse B
V+ V+
5-lead cable CAN H CAN H 5-lead cable
A side shield shield B side
CAN L CAN L
V- V-
Shot key
diode
GND V- V+
terminal
Power supply unit
When the power supply path is separated at the cable A side, remove
fuse A, and when it is separated at the cable B side, remove fuse B
before use.
- 96 -
1.8.6 Relationship with NC Power Supply
In principle, the communications power supply cannot be shared as

the NC power supply. Prepare separate power supplies for the
communications power supply and for the NC power supply.
However, note the following points when a power supply must
unavoidable be shared due to the difficulty of providing separate
power supplies because of space and cost considerations.
The minimum stipulated input voltage of the NC power supply (24

VDC input type) is 21.6 V and is higher than that of the
communications power supply. Satisfy this stipulation taking into
consideration loss caused by voltage drop on the cables. Also, the NC
control unit turns OFF when the communications cable breaks or is
disconnected or when there is a short-circuit caused by shared use.
Turn the communications power supply and NC power supply ON

and OFF in the following sequence when separate power supplies are
provided:
• Turn ON the communications power supply at the same time or
before turning ON the NC power supply.
• Turn OFF the communications power supply at the same time or
after turning OFF the NC power supply on the master node.
If only the communications power supply is turned OFF during
network operations, an abnormality may occur on other nodes that are
currently communicating.
- 97 -
2.DeviceNet FOR 16i/18i/21i (LCD-MOUNTED TYPE) CONNECTION B-63404EN/03
2 DeviceNet FOR 16i/18i/21i (LCD-

MOUNTED TYPE)
This chapter describes hardware specifications and connection
information relating to the DeviceNet board 16i/18i/21i (LCD-
mounted Type).
- 98 -
B-63404EN/03 CONNECTION 2.DeviceNet FOR 16i/18i/21i (LCD-MOUNTED TYPE)
2.1 SPECIFICATIONS
Item Specifications
DeviceNet interface board for LCD-mounted Type i
Name
series
A02B-0236-J301 16i/18i/21i-A
Specification Dwg. No.
A02B-0281-J301 16i/18i/21i-B
Hardware Dwg. No. A20B-8001-0880
Communications power 11 to 24 VDC (supplied from communications
supply voltage connector)
Communications power supply: Max. 50 mA
Current consumption Internal power supply circuit: 5 VDC, max. 850 mA
(supplied from NC unit)
Weight 200g
- 99 -
2.DeviceNet FOR 16i/18i/21i (LCD-MOUNTED TYPE) CONNECTION B-63404EN/03
2.2 INSTALLATION
2.2.1 Environmental Conditions
When using the DeviceNet board, strictly observe the installation

conditions (cabinet internal environment conditions) of the CNC
control unit in which it is mounted.
2.2.2 Leading in Cables
The cables are lead in only from the bottom in the same way as other
regular option PCBs.
The figure below shows the location of the connector on the
DeviceNet board.
View from rear of unit
DeviceNet interface
View from bottom of unit
Note, however, that the board mounting position in the above figure
and connector locations of boards other than the DeviceNet board
vary from the actual positions. For details of the actual connector
locations of boards other than the DeviceNet board, refer to the
respective Connections Manual.
NOTE
Fit or remove the DeviceNet board into the option
slot with the DeviceNet interface connector removed.
The DeviceNet board cannot be mounted on slot 2
when another optional PCB is mounted at slot 3 on a
3-slot type unit.
- 100 -
B-63404EN/03 CONNECTION 2.DeviceNet FOR 16i/18i/21i (LCD-MOUNTED TYPE)
2.2.3 Names of Parts on the DeviceNet Board
LEDA
LED3
LED2
LED1
LED0
DeviceNet interface connector
Communications board status indicators
Slot status and alarm
indicator LED
- 101 -
3.DeviceNet BOARD FOR 16i/18i/21i (STAND-ALONE TYPE), Power Mate i-D/H CONNECTION B-63404EN/03
3 DeviceNet BOARD FOR 16i/18i/21i

(STAND-ALONE TYPE), Power Mate i-D/H
information relating to the DeviceNet slave board for the Series
16i/18i/21i (Stand-Alone Type) and the Power Mate i-D/H, and the
DeviceNet master board.
- 102 -
B-63404EN/03 CONNECTION 3.DeviceNet BOARD FOR 16i/18i/21i (STAND-ALONE TYPE), Power Mate i-D/H
3.1 SPECIFICATIONS
Item Specifications
Name DeviceNet slave board
FS 16i/18i/21i (Stand-Alone
A02B-0265-J300
Specification Dwg. No. Type)
A02B-0259-J240 Power Mate i -D/H
Functions DeviceNet slave function 1 channel
PCB Dwg. No. A20B-8100-0490
Weight 200g
Item Specifications
Name DeviceNet master board
A02B-0265-J301
A02B-0259-J241 Power Mate i -D/H
Functions DeviceNet master function, 1 channel
PCB Dwg. No. A20B-8100-0490
Weight 200g
NOTE
1 There are two DeviceNet boards, the DeviceNet
slave board and DeviceNet master board. The PCB
specifications are the same, the only difference
being is the shorted position of setting pin TM1 on
the board. (The position of setting pin changes the
unit specifications.) Usually, TM1 is factory-set by
FANUC.
2 If a DeviceNet board (A02B-0265-K412) is supplied
together with the CNC, TM1 on the DeviceNet board
is factory-set to the MASTER position. To use the
DeviceNet board as a slave, set TM1 to the SLAVE
position by referring to Subsection 2.1.3 of Part IV,
"Maintenance."
3 The sequence in which this DeviceNet board is
attached and removed is fixed. See sections 2 and 3
of the Maintenance section.
4 When the axis control card (A17B-3700-050*) is
mounted on the opposite PCB, the connector causes
interference. Use DeviceNet board B or C.
- 103 -
3.2 INSTALLATION
When using the DeviceNet board, the ambient temperature range

during operation of the control unit is 0°C to 50°C. For details of
other installation environment conditions, refer to the installation
environment conditions of each CNC control unit.
- 104 -
3.3 MOUNTING
On the FS16i/18i/21i (Stand-Alone Type), the DeviceNet board can

be mounted in the 1-slot or in all mini slots of the 3-slot basic unit. On
the Power Mate i-D/H, the DeviceNet board can be mounted on either
of the two mini slots.
- 105 -
3.4 DeviceNet Board B
DeviceNet board B is characterized by a crimp type connector

(manufactured by Hirose Electric Co., Ltd.) used in the
communication connector section. See Section 1.5, "Connector," of
Part III, "Connection," for explanations about how to crimp connector
terminals.
The descriptions in Sections 3.1 to 3.3 except for specification
drawing numbers and PCB drawing numbers apply also to DeviceNet
board B.
Item Specifications
Name DeviceNet slave board
A02B-0265-J302
A02B-0259-J242 Power Mate i –D/H
PCB Dwg. No. A20B-8100-0491
Item Specifications
Name DeviceNet master board B
A02B-0265-J303
A02B-0259-J243 Power Mate i –D/H
PCB Dwg. No. A20B-8100-0491
- 106 -
3.5 DeviceNet Board C
DeviceNet board C is characterized by a crimp type connector

communication connector section. See Section 1.5, "Connector," of
Part III, "Connection," for explanations about how to crimp connector
terminals.
The descriptions in Sections 3.1 to 3.3 except for specification
drawing numbers and PCB drawing numbers apply also to DeviceNet
board C.
Item Specifications
Name DeviceNet slave board C
Specification Dwg. No. A02B-0265-J304
Type)
PCB Dwg. No. A20B-8100-0650
Weight 110g
NOTE
1 No fixed procedure applies to the mounting or
dismounting of DeviceNet board C, unlike other
types of DeviceNet boards.
2 DeviceNet board C has no setting pin.
- 107 -
4.DeviceNet BOARD FOR 15i CONNECTION B-63404EN/03
4 DeviceNet BOARD FOR 15i

information relating to the DeviceNet slave board for the Series 15i/,
and the DeviceNet master board.
- 108 -
B-63404EN/03 CONNECTION 4.DeviceNet BOARD FOR 15i
4.1 SPECIFICATIONS
Item Specifications
Name DeviceNet slave board C
Weight 110g
Item Specifications
Name DeviceNet master board
Weight 200g
NOTE
1 Setting pin TM1 on DeviceNet board B is factory-set
by FANUC. See Section 2.4 of Part IV,
"Maintenance."
2 A fixed procedure applies to the mounting and
dismounting of DeviceNet board B. See Section 2.3
of Part IV, "Maintenance." No fixed procedure
applies to the mounting or dismounting of DeviceNet
board C, however.
- 109 -
4.DeviceNet BOARD FOR 15i CONNECTION B-63404EN/03
4.2 INSTALLATION
When using the DeviceNet board, the ambient temperature (in the
cabinet) range during operation of the control unit is 0°C to 50°C. For
details of other installation environment conditions, refer to the
Connection Manual (Hardware) (B-63323EN)
- 110 -
B-63404EN/03 CONNECTION 4.DeviceNet BOARD FOR 15i
4.3 INSTALLATION
On the FS15i, the DeviceNet board can be mounted in the 2-slot or in all mini slots of
the 4-slot basic unit.
- 111 -
IV. MAINTENANCE
B-63404EN/03 MAINTENANCE 1.16i/18i/21i (LCD-MOUNTED TYPE) DeviceNet
1 16i/18i/21i (LCD-MOUNTED TYPE)

DeviceNet
This chapter describes maintenance related to the DeviceNet board
for the Series 16i/18i/21i (LCD-mounted Type).
- 115 -
1.16i/18i/21i (LCD-MOUNTED TYPE) DeviceNet MAINTENANCE B-63404EN/03
1.1 LAYOUT OF PARTS
LEDA
LED3
LED2
LED1
LED0
DeviceNet interface connector HEALTH NS Slot status and alarm
indicator LED
- 116 -
B-63404EN/03 MAINTENANCE 1.16i/18i/21i (LCD-MOUNTED TYPE) DeviceNet
1.2 DESCRIPTION OF INDICATOR LEDS
This board has five status indicator LEDs (4 green, 1 red), and two
LEDs that light in both the red and green colors on the internal
daughter board. The table below describes the functions of these
LEDs.
Name Color Meaning

LED0 ~ 3 Green No particular meaning
LEDA Red This LED lights when an error occurs on the
internal daughter board, and goes out when the
power is turned ON.
When this LED lights, replace the DeviceNet
board.
NS Red/Green The LED indicates the DeviceNet
module/network status. This LED indicates
whether or not the DeviceNet board power is
turned ON, and whether DeviceNet
communications is being performed normally.
For details of the meaning of the lit states of this
LED, refer to the Specifications Manual issued by
ODVA.
HEALTH Red/Green This LED indicates the status of the daughter
board.
It lights red after the power is turned ON. When
the firmware is loaded to the internal daughter
board, it lights green.
It lights red if a failure occurs on the daughter
board.
If the LED lights red, replace the DeviceNet
board.
- 117 -
1.16i/18i/21i (LCD-MOUNTED TYPE) DeviceNet MAINTENANCE B-63404EN/03
1.3 HOW TO ATTACH AND REMOVE THE DeviceNet BOARD
Outline
To remove and remove the DeviceNet board from the control unit, the
DeviceNet connector terminal plate must first be removed.
Removing the DeviceNet connector terminal plate

The terminal plate can be removed from the DeviceNet board
interface connector with the cable still connected. Remove the
terminal plate by pulling it towards you.
NOTE
The DeviceNet board cannot be removed unless the
connector's terminal plate has been removed first.
Removing and attaching the DeviceNet board

For details on how to remove and attach the DeviceNet board, refer to
"How to Remove and Attach Optional Boards" in the Maintenance
Manual in the respective Maintenance Manual.
CAUTION
The DeviceNet board cannot be mounted on slot 2
when another optional PCB is mounted at slot 3 on a
3-slot type unit.
- 118 -
B-63404EN/03 MAINTENANCE2.DeviceNet BOARD FOR 15i, 16i/18i/21i (STAND-ALONE TYPE), Power Mate i-D/H
2 DeviceNet BOARD FOR 15i, 16i/18i/21i

(STAND-ALONE TYPE), Power Mate i-D/H
This chapter describes the maintenance information relating to the
DeviceNet slave board for the Series 15i, Series 16i/18i/21i (Stand-
Alone Type) and Power Mate i-D/H, and the DeviceNet master board.
- 119 -
2.DeviceNet BOARD FOR 15i, 16i/18i/21i (STAND-ALONE TYPE), Power Mate i-D/H MAINTENANCE B-63404EN/03
2.1 DeviceNet BOARD
2.1.1 Layout of Parts

Setting
pin TM1
PWB
MASTER SLAVE
version
No.
PCB Dwg.
No.
LED indicators
MNS (Left),
HEALTH (right)
LED indicators
A321 External line
connector TBL
LED LED
MNS HEALTH
- 120 -
2.1.2 Description Of Indicator LEDs
This board has four status indicator LEDs (3 green, 1 red), and two
LEDs that light in both the red and green colors on the internal
daughter board. The table below describes the functions of these
LEDs.
Name Color Meaning

LED1 ~ 3 Green These LEDs indicate whether the DeviceNet
board is a master board or a slave board. These
LEDs go out when the power is turned ON.
LED1 LED2 LED3

Master board Lit Out Out
Slave board Lit Lit Out
LEDA Red This LED lights when an error occurs on the

internal daughter board, and goes out when the
power is turned ON.
When this LED lights, replace the DeviceNet
board.
MNS Red/Green The LED indicates the DeviceNet
module/network status. This LED indicates
whether or not the DeviceNet board power is
turned ON, and whether DeviceNet
communications is being performed normally.
For details of the meaning of the lit states of this
LED, refer to the Specifications Manual issued by
ODVA.
HEALTH Red/Green This LED indicates the status of the daughter
board.
It lights red after the power is turned ON. When
the firmware is loaded to the internal daughter
board, it lights green.
It lights red if a failure occurs on the daughter
board.
If the LED lights red, replace the DeviceNet
board.
- 121 -
2.1.3 Short Pin TM1

This board has a 3-pin short pin TM1. TM1 indicates whether that
board is used for DeviceNet slave functions or DeviceNet master
functions.
Short pin
MASTER SLAVE
When the short pin is set to SLAVE, that board is used for DeviceNet
slave functions. When it is set to MASTER, that board is used for
DeviceNet master functions.
The short pin is already set before the board is shipped from the
factory according to your particular specifications. Do not change the
setting.
NOTE
For some models, machine tool builders are
requested to set TM1.
In this case, first find the location of short pin TM1 by
referencing the parts layout drawing shown in
Subsection 2.1.1. To use the board as a master,
set TM1 to the MASTER position. To use the board
as a slave, set it to the SLAVE position.
- 122 -
2.1.4 How to Attach and Remove the DeviceNet Board
Outline
The sequence in which this DeviceNet board is attached and removed
from the control unit is fixed.
CAUTION
To prevent the inadvertent loss of data in SRAM
during this operation, back up the data in the CNC's
SRAM to built-in FROM (Power Mate i only) or to
memory card before you attach and remove the
DeviceNet board.
Removing the DeviceNet Board

1) Removing the DeviceNet connector terminal plate
The terminal plate can be removed from the DeviceNet board
interface connector with the cable still connected. Loosen the
two screws shown in the figure below, and then remove the
terminal plate by pulling it towards you.
Screw
Base PCB
Device net board
NOTE
The base PCB cannot be removed unless the
2) Removing the base PCB

Remove the base PCB before you remove the DeviceNet board.
For details on how to remove the base PCB, refer to the
respective Maintenance Manual.
CAUTION
The DeviceNet board cannot be removed unless the
base PCB has been removed first. If the DeviceNet
board is removed without removing the base PCB,
the DeviceNet board may interfere and break the
base PCB.
- 123 -
3) Removing the DeviceNet board

Remove the DeviceNet board without the base PCB attached.
For details on how to remove the DeviceNet board, refer to
"How to Remove and Attach Optional Boards" in the respective
Maintenance Manual.
Attaching the DeviceNet board

1) Removing the base PCB
Remove the base PCB before you remove the DeviceNet board.
For details on how to remove the base PCB, refer to the
CAUTION
The DeviceNet board cannot be attached unless the
base PCB has been removed first. If you attempt to
attach the DeviceNet board without removing the
base PCB, the DeviceNet board may interfere and
break the base PCB.
2) Removing the DeviceNet connector terminal plate

Remove the interface connector terminal plate from the
DeviceNet board. Loosen the two screws shown in the figure
below to remove.
Screws
3) Attaching the DeviceNet board

Attach the DeviceNet board without the base PCB attached.
For details on how to attach the DeviceNet board, refer to "How
to Remove and Attach Optional Boards" in the respective
Maintenance Manual.
4) Attaching the base PCB

After you have attached the DeviceNet board, attach the base
PCB. For details on how to attach the base PCB, refer to the
5) Attaching the DeviceNet connector terminal plate

Attach the interface connector terminal plate to the DeviceNet
board. After attaching the terminal plate, firmly tighten the two
screws on the terminal plate.
NOTE
The base PCB cannot be attached unless the
- 124 -
2.2 DeviceNet BOARD B
DeviceNet board B is characterized by a crimp type connector

communication connector section. The parts layout, indicator LEDs,
and short pin of this board are the same as for DeviceNet board A.
See Subsection 2.1.4 also for explanations about how to mount and
dismount this board.
- 125 -
2.3 DeviceNet BOARD C
2.3.1 Layout of Parts
Custom
LSI
MPU
TBL
Name PCB DRW number Remarks

DeviceNet slave board C A20B-8100-0650
- 126 -
2.3.2 Description Of Indicator LEDs
This board has five status indicator LEDs (2 green(MS, NS), 3

red(ALM, MS, NS).
TBL
A(ALM)(RED)
4(MS)(GREEN)
3(MS)(RED)
2(NS)(GREEN)
1(NS)(RED)
NOTE
The face plate is indicated using dotted lines.
- 127 -
Status LED indicators

The locations of the indicator LEDs and their definitions are
explained below.
A : Off B : On C : Blinking D : Don't care
ALM
LED indicator
No. Board status
ALM (RED)
The board is reset, or an error has been detected
1 B
on the board.
MS (This is a modular status LED of the DeviceNet. Refer to the

specification document issued by ODVA.)
LED indicator
No. Board status
MS(GREEN),(RED)
1 BA The board is running normally.
A setting has not been completed. The
2 CA insufficient or inaccurate setting requires
adjustment.
3 AC A recoverable error has occurred.
4 AB An irrecoverable error has occurred.
5 CC Self-diagnosis is in progress.
NS (This is a network status LED of the DeviceNet. Refer to the

specification document issued by ODVA.)
LED indicator
No. Board status
NS(GREEN),(RED)
1 AA The communication link is not on-line.
The communication link is on-line, but no
2 CA
connection has been established.
The communication link is on-line, and a
3 BA
connection has been established.
4 AC The connection is in the time-out state.
A network error was detected which disabled
5 AB
communication.
The board has detected a network access error, is
in the Communication Faulted state, and has
6 CC
received an Identify Communication Faulted
request.
- 128 -
APPENDIX
B-63404EN/03 APPENDIX A.DEVICE PROFILES AND OBJECT LIBRARIES
A DEVICE PROFILES AND OBJECT LIBRARIES

This appendix presents information about the communication data
and IDs defined for the DeviceNet.
- 131 -
A.DEVICE PROFILES AND OBJECT LIBRARIES APPENDIX B-63404EN/03
A.1 DeviceNet BOARD C
Device profile
General data Applicable DeviceNet specification Volume 1 Release2.0
Volume 2 Release2.0
Vendor ID 591
Device type 0CH
Product code 1
Physical conformance data Network current drain 50 mA on 24 VDC
Connector type Open plug
Whether there is a physical layer Yes
insulation.
Supported LED Module
Network
MAC ID setting Parameter
Default MAC ID 0
Transmission baud rate setting Parameter
Supported transmission baud rate 125Kbps,250Kbps,500Kbps
Communication data Predefined master/slave connection set Group 2-only server
Dynamic connection support No
(UCMM)
Explicit message fragmentation Yes
Object installation
1. Identity object (01H)
Object class Attribute Unsupported
Service Unsupported
Object instance Attribute ID Description GET SET Value

1 Vendor O X 591
2 Device type O X 12
3 Product code O X 1
4 Revision O X 1.0
5 Status (bits supported) O X bit0
bit10
6 Serial number O X (*1)
7 Product name O X (*2)
8 State X X
9 Configuration Consistency Value X X
10 Heartbeat Interval X X
Service DeviceNet service Parameter option
05H Reset No
0EH Get_attribute_Signle No
*1 Value set up for an individual board

*2 A20B-8100-0650
- 132 -
2. Message router object (02H)

Service Unsupported
Object instance Attribute Unsupported
Service Unsupported
Additional vendor-specific specification No
3. DeviceNet object (03H)

Object class Attribute ID Description GET SET Value
1 revision O X 02H
Object instance Attribute ID Description GET SET Value

1 MAC ID O X
2 Baud rate O X
3 BOI O X 00H
4 Bus-off counter O X
5 Allocation information O X
6 MAC ID switch changed X X
7 Baud rate switch changed X X
8 MAC ID switch value X X
9 Baud rate switch value X X
4BH Allocate Master/Slave_Connection Set No
4CH Release Master/Slave_Connection Set No
4. Assembly object (04H)

Service Unsupported
Object instance Section Information Maximum number of

1 instances
Instance type Static I/O 1
Attribute ID Description GET SET Value
1 Number of Members in List X X
2 Member List X X
3 Data O O
10H Set_attribute_Signle No
- 133 -
5. Connection object (05H)

Service Unsupported
Maximum available number of 1
active connections
Object Section Information Maximum number of

instance 1 instances
Instance type Explicit Message 1
Production Cyclic
trigger
Transport type Server
Transport class 3
1 State O X
2 Instance type O X 00H
3 Transport class trigger O X 83H
4 Produced connection ID O X
5 Consumed connection ID O X
6 Initial comm. Characteristics O X 21H
7 Produced connection size O X FE00H
8 Consumed connection size O X FE00H
9 Expected packed rate O O
12 Watchdog time-out action O O One of 01,03
13 Produced connection path length O X 0000
14 Produced connection path O X
15 Consumed connection path length O X 0000
16 Consumed connection path O X
17 Production inhibit time O X
05H Reset No
- 134 -
Object Section Information Maximum number of instances

instance 2 Instance type Polled I/O 1
Production trigger Cyclic
Transport class 2
1 State O X
6 Initial comm. characteristics O X 01H
7 Produced connection size O X (*1)
8 Consumed connection size O X (*2)
12 Watchdog time-out action O O 00
13 Produced connection path length O X 0000 (IN:No)
0600 (IN:Yes)
14 Produced connection path O X No data (IN:No)
20_04_24_01_30_03 IN:Yes)
15 Consumed connection path O X 0000 (OUT:No)
length 0600 (OUT:Yes)
16 Consumed connection path O X No data (OUT:No)
20_04_24_01_30_03 (OUT:Yes)
17 Production inhibit time O X 00
05H Reset No
*1 Number of IN bytes used, in which the upper byte has been

replaced with the lower byte (Example: 4000H when 64 bytes
are used)
*2 Number of OUT bytes used, in which the upper byte has been
replaced with the lower byte (Example: 4000H when 64 bytes
are used)
- 135 -
Object Section Information Maximum number of instances

instance 3 Instance type Bit Strobed I/O 1
Production trigger Cyclic
Transport class 2
1 State O X
6 Initial comm. Characteristics O X 02H
7 Produced connection size O X (*)
8 Consumed connection size O X 0800H
12 Watchdog time-out action O O 00
13 Produced connection path length O X 0600
14 Produced connection path O X 20_04_24_01_30_03
15 Consumed connection path length O X 0000
16 Consumed connection path O X No data
17 Production inhibit time O X 00
05H Reset No
* Number of IN bytes used, in which the upper byte has been

replaced with the lower byte (example: 0800H when 8 bytes
are used)
For the bit strobe, up to 8 bytes are usable.
- 136 -
B-63404EN/03 INDEX
INDEX
DeviceNet FOR 16i/18i/21i (LCD-MOUNTED
1
TYPE)............................................................. 98
16i/18i/21i (LCD-MOUNTED TYPE) DeviceNet
DeviceNet FUNCTIONS .................................... 9
...................................................................... 115
E
A
Environmental Conditions ............. 100, 104, 110
Applicable Machine Names................................ 4
G
C
GENERAL WARNINGS AND CAUTIONS ...... 3
CABLE CLAMP ................................................ 83
GROUNDING THE CABLE WIRES ............... 81
CABLE LENGTH AND BAUD RATE............. 74
H
COMMUNICATIONS POWER SUPPLY........ 84
CONFIGURING A SAFE SYSTEM................. 66 HANDLING MULTIPLE-BYTE DATA........... 68
CONNECTING DeviceNet............................... 72 How to Attach and Remove the DeviceNet
CONNECTING DeviceNet FUNCTIONS ....... 71 Board............................................................ 123
CONNECTOR ................................................... 78 HOW TO ATTACH AND REMOVE THE
DeviceNet BOARD....................................... 118
D
I
DEFINITION OF WARNING¥, CAUTION¥,
AND NOTE .................................................... 2 INSTALLATION ............................. 100, 104, 111
Description Of Indicator LEDs .............. 121, 127 L
DESCRIPTION OF INDICATOR LEDS ....... 117
Layout of Parts........................................ 120, 126
Descriptions in This Manual.............................. 3
LAYOUT OF PARTS ...................................... 116
Designing a Power Supply Connection ........... 85
Leading in Cables ........................................... 100
Determining the Power Supply Locations ...... 85
DEVICE PROFILES AND OBJECT LIBRARIES......... 131 M
DeviceNet BOARD.......................................... 120 Master Function Data Refresh Rate................ 37
DeviceNet Board B ......................................... 106 MOUNTING.................................................... 105
DeviceNet BOARD B ...................................... 125
N
DeviceNet Board C .................................. 107, 132
DeviceNet BOARD C ...................................... 126 Names of Parts on the DeviceNet Board ....... 101
DeviceNet BOARD FOR 15i............................108 NSTALLATION .............................................. 110
DeviceNet BOARD FOR 15i/16i/18i/21i (STAND-
P
ALONE TYPE)¥, Power Mate i-D/H ..............119
PECIFICATIONS............................................ 109
DeviceNet BOARD FOR 16i/18i/21i (STAND-
ALONE TYPE)¥, Power Mate i-D/H........... 102 R
DeviceNet CABLES .......................................... 73 Related Manuals ................................................. 5
i-1
INDEX B-63404EN/03
Relationship with NC Power Supply ............... 97 Separated Paths ............................................ 96
S T
SETTING MASTER FUNCTIONS.................. 11 TERMINATOR.................................................. 77

SETTING SLAVE FUNCTIONS ..................... 46 TROUBLESHOOTING COMMUNICATIONS
Setting Slave Parameters................................. 23 ERRORS ........................................................ 67
Setting the Bus Parameters............................. 14
V
Short Pin TM1................................................. 122
Verification by Graph-Based Simple Calculation
Slave Function Data Refresh Rate .................. 61
........................................................................ 88
SPECIFICATIONS ................................... 99, 103
Verifying by Calculation Expression ............... 93
Starting Communications .......................... 32, 60
Supplying Multiple Power Supplies on
i-2

!"!#
( ')'*)&'
" $%&""'
(
( '+
"& $%&""" (
( , -- . /0 0

10 02
"' -$%'333

EUROPEAN HEADQUARTERS
GRAND-DUCHE DE LUXEMBOURG
GE Fanuc Automation Europe S.A.
Zone Industrielle
L-6468 Echternach
(+352) 727979 - 1
(+352) 727979 – 214
www.gefanuc-europe.com
BELGIUM / NETHERLANDS CZECH REPUBLIC FRANCE
GE Fanuc Automation Europe S.A. GE Fanuc GE Fanuc Automation France S.A.
- Netherlands Branch - Automation CR s.r.o. 39, rue du Saule Trapu, BP 219
Postbus 7230 - NL-4800 GE Breda U studanky 3 F-91882 Massy Cedex
Minervum 1603A - NL-4817 ZL Breda CZ-170 00 Praha 7 (+33) 1 69 75 86 39 (CNC)
(+31) 76-5783 201 (CNC) (+420) 2 333 72 502 (CNC) (+33) 1 69 75 86 20 (PLC)
(+31) 76-5783 212 (PLC) (+420) 2 333 72 503 (PLC) (+33) 1 69 75 86 49
(+31) 76-5870 181 (+420) 2 333 70 821 www.gefanuc.fr
www.gefanuc.nl www.gefanuc.cz
GERMANY GERMANY GERMANY
GE Fanuc Automation GmbH GE Fanuc Eberle Automation GmbH GE Fanuc Automation GmbH
Bernhäuser Straße 22 Südwestpark 48 Elberfelderstr. 45
D-73765 Neuhausen a.d.F D-90449 Nürnberg D-40724 Hilden
(+49) 7158 187 400 (+49) 911 9672 100 (PLC) (+49) 2103 247410 (Laser/CNC)
(+49) 7158 187 455 (CNC) (+49) 911 9672 200 (PLC) (+49) 2103 247420 (Laser/CNC)
(+49) 7158 187 466 (PLC) www.gefanuc.de www.gefanuc.de
www.gefanuc.de
GERMANY GERMANY ITALY
GE Fanuc Automation Deutschland GE Fanuc Automation GmbH GE Fanuc Automation Italia S.r.l.
GmbH Obere Hauptstr. 72 Largo Brugnatelli 15 – Via Volta 4
Bensheimer Str. 61 D-09244 Lichtenau I-20090 Buccinasco (MI)
D-65428 Rüsselsheim (+49) 37208 695 20(CNC) (+39) 02 45795 1 (CNC)
(+49) 6142 357600 (+49) 37208 695 30 (PLC) (+39) 02 45795 250 (CNC)
(+49) 6142 357611 (+49) 37208 695 55 www.gefanuc.it
www.gefanuc.de www.gefanuc.de
ITALY POLAND SPAIN
GE Power Controls GE Fanuc Automation Polska Sp. z o.o. GE Fanuc Automation España S.A.
Italia S.p.a ul. Czerwinskiego 6 Polígono Industrial Olaso
Via Tortona 27 40-123 Katowice - Poland Calle Olaso, 57 - Locales 10 y 11
I-20144 Milano (+48) 32 258 5077 E-20870 Elgoibar
(+39) 02 4242 280 (PLC) (+48) 32 258 5077 (+34) 943 74 82 90 (CNC)
(+39) 02 4242 511 (PLC) (+34) 943 74 44 21 (CNC)
www.gefanuc.it www.gefanuc.es
SPAIN SWEDEN SWITZERLAND
GE Power Controls GE Fanuc Automation Nordic AB GE Fanuc Automation Europe S.A.
Ibérica S.L. Hammarbacken 4B Zweigniederlassung Brügg –
Calle Marqués de Comillas, 1 S-19149 Sollentuna Swiss Branch
E-08225 Terrassa (Barcelona) (+46) 8 444 5520 Erlenstrasse 35a
(+34) 93 736 58 28 (PLC) (+46) 8 444 5521 P.O. Box CH-2555 Brügg BE
(+34) 93 788 24 03 (PLC) www.gefanuc.se (+41) 32 366 63 63 (CNC)
www.gefanuc.es (+41) 32 366 63 33 (PLC)
(+41) 32 366 63 64 (CNC)
(+41) 32 366 63 34 (PLC)
www.gefanuc.ch
UNITED KINGDOM
GE Fanuc
Automation (UK) Ltd.
Unit 1 - Mill Square
Featherstone Road
Wolverton Mill South
Milton Keynes MK12 5BZ
(+44) 1908 84 4000
(+44) 1908 84 4001
www.gefanuceur.co.uk
10/01
Printed at GE Fanuc Automation S.A. , Luxembourg March 2001

Fan Uc Device Net Board 03

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Fan Uc Device Net Board 03

Uploaded by

Copyright:

Available Formats

GE Fanuc Automation Europe

Computer Numerical Controls

TECHNOLOGY AND MORE

1. DEFINITION OF WARNING, CAUTION, AND NOTE -----------------------------s-2

1 DEFINITION OF WARNING, CAUTION, AND NOTE

• Read this manual carefully, and store it in a safe place.

2 GENERAL WARNINGS AND CAUTIONS

SAFETY PRECAUTIONS....................................................................................................................... s-1

2 CONFIGURING A SAFE SYSTEM ................................................................................................. 66

2.1 TROUBLESHOOTING COMMUNICATIONS ERRORS ............................................................. 67

1 CONNECTING DeviceNet FUNCTIONS ........................................................................................ 71

1.1 CONNECTING DeviceNet.............................................................................................................. 72

1.8.4 Verifying by Calculation Expression ...................................................................................... 94

2 DeviceNet FOR 16i/18i/21i (LCD-MOUNTED TYPE) ..................................................................... 99

2.1 SPECIFICATIONS........................................................................................................................ 100

3.1 SPECIFICATIONS........................................................................................................................ 104

4 DeviceNet BOARD FOR 15i ........................................................................................................... 109

4.1 SPECIFICATIONS........................................................................................................................ 110

IV. MAINTENANCE.............................................................................................................................. 113

1 16i/18i/21i (LCD-MOUNTED TYPE) DeviceNet............................................................................ 115

1.1 LAYOUT OF PARTS ..................................................................................................................... 116

2.1 DeviceNet BOARD ........................................................................................................................ 120

2.3 DeviceNet BOARD C..................................................................................................................... 126

A DEVICE PROFILES AND OBJECT LIBRARIES ...................................................................................... 131

A.1 DeviceNet BOARD C..................................................................................................................... 132

Descriptions in This Manual

Applicable Machine Names

Machine Name Abbreviation

Series 15i/150i-MA related manuals

Series 16i/18i/160i/180i-TA/MA related manuals

Series 21i/210i-TA/MA related manuals

Series 16i/18i/160i/180i-TB/MB related manuals

Series 21i/210i-TB/MB related manuals

Power Mate i-D/H related manuals

Unusable Network Functions

Number of networks connectable to NC

• Stand-Alone type Series 16i/18i/21i Series 15 i -A, and Power

Outline of DeviceNet function specifications

• Max. number of connected slaves: 32

• Slave assigned addresses

• Number of slave DI/DO communication points

(2) Slave function

• Number of DI/DO communication points

1.2 SETTING MASTER FUNCTIONS

* See Chapter 2, "Configuring a Safe System" for information

Setting Master Functions on the Series 16i/18i/21i-A/B

If you press soft keys [PMCDGN] → ([>])→ [I/OCHK] →

Screen 1.2 (a)

Table 1.2: Display items in initial screen

(2) Next, press soft key [MASTER]. The DEVICENET MASTER

Screen 1.2 (b)

(3) Switch to either of the following parameter setup screens by

Descriptions here on regarding parameter setup assume that each of

1.2.1 Setting the Bus Parameters

Setting Bus Parameters on the Series 16i/18i/21i-A/B

Screen 1.2.1(a) Bus parameter setup screen (Series 16i/18i/21i-A/B)

Setting Bus Parameters on the Series 15i-A

Set each parameter on the bus parameter setup screen.

Screen 1.2.1(b) Bus parameter setup screen (Series 15i-A)

- If the cursor is at "DI HOLD/CLEAR," pressing cursor key

Diagnosis Information on the Bus Parameters Setting Screen

STATUS and COMMUNUNICATION STATUS are displayed in bus

Setting the MAC-ID and baud rate

Assigning status information