FANUC FL-Net Board Operators Manual GFZ-63434EN02 CNC Manual

GE Fanuc Automation
Computer Numerical Control Products
FL–Net Board
Operator's Manual
GFZ-63434EN/02 November 2000

GFL-001
Warnings, Cautions, and Notes
as Used in this Publication
Warning
Warning notices are used in this publication to emphasize that hazardous voltages, currents,
temperatures, or other conditions that could cause personal injury exist in this equipment or may
be associated with its use.
In situations where inattention could cause either personal injury or damage to equipment, a
Warning notice is used.
Caution
Caution notices are used where equipment might be damaged if care is not taken.
Note
Notes merely call attention to information that is especially significant to understanding and
operating the equipment.
This document is based on information available at the time of its publication. While efforts
have been made to be accurate, the information contained herein does not purport to cover all
details or variations in hardware or software, nor to provide for every possible contingency in
connection with installation, operation, or maintenance. Features may be described herein which
are not present in all hardware and software systems. GE Fanuc Automation assumes no
obligation of notice to holders of this document with respect to changes subsequently made.
GE Fanuc Automation makes no representation or warranty, expressed, implied, or statutory

with respect to, and assumes no responsibility for the accuracy, completeness, sufficiency, or
usefulness of the information contained herein. No warranties of merchantability or fitness for
purpose shall apply.
©Copyright 2000 GE Fanuc Automation North America, Inc.

All Rights Reserved.
B-63434EN/02 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 PRECAUTIONS B-63434EN/02
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 Warning and Caution according to their bearing on safety. Also,
supplementary information is described as a Note. Read the Warning, Caution, and Note thoroughly
before attempting to use the machine.
WARNING
Applied when there is a danger of the user being injured or when there is a damage 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
The Note is used to indicate supplementary information other than Warning and
Caution.
- Read this manual carefully, and store it in a safe place.
s-2
B-63434EN/02 SAFETY PRECAUTIONS
2 GENERAL WARNINGS AND NOTES
WARNING
1. Before operating the machine, thoroughly check the entered data.

Operating the machine with incorrect 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 perform a production run, such as actually machining a workpiece, without first
checking the operation of the machine. Before starting the machine for a production run, ensure
that the program command values, offsets, current position, external signals, and other settings are
suitable for the operation to be performed. Also check that the machine operates 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.
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.
5. The parameters for the CNC and PMC are factory-set. Usually, there is not need to change them.
When, however, there is not alternative other than to change a parameter, ensure that you fully
understand the function of the parameter before making any change.
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.
6. 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.
s-3
SAFETY PRECAUTIONS B-63434EN/02
WARNING
7. The operator’s manual and programming manual supplied with a CNC unit provide an overall
description of the machine’s functions, including any optional functions. Note that the optional
functions will vary from one machine model to another. Therefore, some functions described in
the manuals may not actually be available for a particular model. Check the specification of the
machine if in doubt.
8. Some functions may have been implemented at the request of the machine-tool builder. When
using such functions, refer to the manual supplied by the machine-tool builder for details of their
use and any related cautions. Refer to the following two examples.
<1> Some machines have a tool replacement device that operates when a tool feature is
executed. When the user is working near the device, he or she may touch it. Execute tool
features in a place sufficiently away from the tool replacement device.
<2> Many auxiliary features cause machine operation such as rotation of the spindle.
Understand the operations of auxiliary features before using them.
NOTE
Command programs, parameters, and variables are stored in nonvolatile memory in the CNC unit.
Usually, they are retained even if the power is turned off. Such data may be delated inadvertently,
however, or it may prove necessary to delete all data from nonvolatile memory as part of error
recovery.
To guard against the occurrence of the above, and assure quick restoration of deleted data, backup all
vital data, and keep the backup copy in a safe place.
s-4
B-63434EN/02 Table of Contents
Table of Contents

!

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

!

3

4

,

!

5

c-1
Table of Contents B-63434EN/02

!
!" #
$
!" #
$%
&#
$ '
&#
$%

!
(

)

!!
*
*

!
+ %
+ ,
)

3
5

5!

55

54
- i.i.i/ '
%0 i/0(1.2

4
)/+#% 67 4
8

4

44

,,
,
9

,
c-2
B-63434EN/02 Table of Contents

,

,4

7

,

,3
:
;

3#

3#
%
3 -
2# '

,
-

,
3#

,
4 %$

9
7

4

c-3
I. GENERAL
B-63434EN/02 GENERAL 1.GENERAL
1 GENERAL
This manual consists of the following parts:
About this manual

SAFETY PRECAUTIONS
Describes the precautions to be observed in reading this manual.
I. GENERAL
Describes the organization of this manual, applicable models,
and related manuals.
II. DESCRIPTION
Describes the general for using the FL-net function.
III. OPERATION
Describes the setting and operation procedures for using the FL-
net function.
IV. CONNECTION
Describes the method of connecting each device and notes on
using the FL-net function.
V. MAINTENANCE
Describes the drawing number of the FL-net board, the meanings
of LED indications, and so forth.
Applicable models
This manual covers the models listed in the table below. In this
manual, the their abbreviations may be used.
Model Abbreviation
Stand-alone type FANUC Series 16i/160i-TA 16i-TA Series 16i-A
Stand-alone type FANUC Series 16i/160i-MA 16i-MA
FANUC Power Mate i-MODEL D Power Power Mate i
Mate i-D
FANUC Power Mate i-MODEL H Power
Mate i-H
-3-
1.GENERAL GENERAL B-63434EN/02
Related manuals
The tables below list the manuals related to each model. When
reading this manual, refer to the related manuals as well.
Manuals related to Series 16i/18i-TA/MA

Manual name Specification number
Descriptions B-63002EN
Connection Manual (Hardware) B-63003EN
Connection Manual (Functions) B-63003EN-1
Operator’s Manual (For Lathes) B-63004EN
Operator’s Manual (For Machining Centers) B-63014EN
Maintenance Manual B-63005EN
Parameter Manual B-63010EN
Manuals related to Series 21i-TA/MA

Operator’s Manual (For Lathes) B-63084EN
Operator’s Manual (For Machining Centers) B-63094EN
Manuals related to FANUC Power Mate i-MODEL D/H

Operator’s Manual B-63174EN
-4-
II. DESCRIPTION
B-63434EN/02 DESCRIPTION 1.FL-net SPECIFICATIONS
1 FL-net SPECIFICATIONS
This section describes the specifications of the FL-net.
-7-
1.FL-net SPECIFICATIONS DESCRIPTION B-63434EN/02
1.1 What Is the FL-net?

The FL-net is an open FA network standardized by the FA Open
Promotion Council (JOP) in the Manufacture, Science, and
Technology Center (MSTC) Incorporated Foundation, which is an
extra-governmental organization of the Ministry of International
Trade and Industry.
The FL-net can interconnect various types of FA controllers such as
programmable controllers (PLCs) and computer numerical controllers
(CNCs), and personal computers that are manufactured by many
different manufacturers to control and monitor them.
Features of the FL-net

The FL-net has the following features:
Multi-vendor environment using an open network

The FL-net conforms not to the FANUC-specific communication
standard, but to the open FA network standard so that
communication devices manufactured by different vendors
(manufacturers) can communicate with each other.
Computers
Upper LAN Ethernet (TCP/IP, UDP)

FL-net (Ethernet-based control network)
Company D
Company A PLC Company B PLC Company C PLC personal CNC Company E RC
Controllers
Field network
Devices Sensor actuator
Large-scale network
Up to 249 communication devices (nodes) can be connected to
share data among them.
FL-net
1 2 248 249 250 254
!"#$%&'(!) ! $*+ #

$*%,- (.#('/
-8-
Two communication functions available according to the application

The FL-net supports both the common memory function and
message communication function. The common memory
function uses cyclic data transmission to allow the nodes to
always share the same data. The message communication
function allows the nodes to exchange only required information
as required.
0'1.'(#( !!(3
4.#5(#6 (#(
0'1.'# (!.!!. 0'1.' # (!.!!. 2 !!(3

# (!.!!.
Large-capacity common memory
As common memory, 8K bits + 8K words (a total of 17K bytes)
of large-capacity common memory can be shared among all
nodes.
Node=01 common memory Node=02 Node=03 Node=04
(Transmission) (Reception) (Reception) (Reception)
(Reception) (Transmission) (Reception) (Reception)

・・・・
・・・・
(Reception) (Reception) (Reception) (Transmission)

・・・・
・・・・
(Reception) (Reception) (Transmission) (Reception)
Fast response
The FL-net provides a fast response of 50 ms/32 nodes (at 2K
bits + 2K words/32 nodes).
NOTE
This value indicates the speed at which a token is
passed through nodes. It does not indicate the
time from when data is set in a node to when it
seems to be data in a different node.
-9-
High reliability
Each node can participate in or be disconnected from the FL-net
at any time. So, the power to each node can be turned on or off
without restraint to provide high maintainability.
The masterless token method allows communication to be
continued without stopping the network by the token
management if a failure occurs in a communication device.

Low cost
The use of cables for Ethernet, which is now widespread in the
OA field, can reduce the cost of communication devices such as
transceivers and hubs.
High maintainability
Various types of management tables are available. The
management tables can be referenced to identify a faulty node
quickly.
- 10 -
1.2 FANUC FL-net Functions
Cyclic transmission
With the FANUC FL-net, part of large-capacity common memory can
be allocated in the PMC R area or D area to allow the user program to
read and write data in the FL-net common memory.

The FL-net common memory contains two areas: an 8K-bit (= 0.5K-

word) area called area 1 and an 8K-word area called area 2.
Generally, common memory area 1 is used for treating bit data and
common memory area 2 is used for treating numeric data.
For how the PMC memory area corresponds to each common memory
area and how to allocate common memory areas, see Sections 2.1,
"Common Memory Area 1 Cyclic Transmission," and 2.2, "Common
Memory Area 2 Cyclic Transmission," in "Description."
Message transmission
The message transmission function is the other FL-net function.
With this function, the user program also executes message
transmission services via PMC memory areas.
To perform message transmission, the user program writes the
transmission request code of message transmission in the PMC
memory area that has been set as an message transmission interface in
advance. The user program also reads received message data via a
PMC memory area. Part of message transmission server (request
receiver) processing may be performed in the FL-net board without
user-program intervention.
- 11 -

For details of message transmission, see Chapter 3, "Message

Transmission," in "Description."
- 12 -
B-63434EN/02 DESCRIPTION 2.CYCLIC TRANSMISSION
2 CYCLIC TRANSMISSION
This chapter details how to use the cyclic data transmission function
of the FL-net function with the Series 16i/18i/21i-A and with the
Power Mate i.
- 13 -
2.CYCLIC TRANSMISSION DESCRIPTION B-63434EN/02
2.1 Common Memory Area 1 Cyclic Transmission
Those areas of common memory area 1 that are to be used for data
exchange can be allocated in the PMC R area in direct image.
An area to be allocated needs to be set beforehand. If the setting of
an allocation area is changed, the power needs to be turned off then
back on.
Procedure
Set the following parameters beforehand:

1) Pa11: Area 1 transmit data start address
2) Pa12: Area 1 transmit data size (in words)
3) Pa30: Allocation address
4) Pa31: Area 1 address
5) Pa32: Data size (in words)
If an allocated area includes a mixture of DI and DO areas as shown

below, data exchange is performed by making a distinction between a
DI area and a DO area, thus posing no problem. When 0 is set in
Pa32 (data size), the data of common memory area 1 is not
exchanged.

#+# 0( ("

+#-$%'##*+)$
)0+)'-
(7+
(7" +#-$%'##*+)$
("" )0+)'-
+#-$%'##)*0
("$ (7$
()&#()'
+#-$%'##*+)$
)0+)'-
+#-$%'##*+)$
)0+)'-
+#-$%'##*+)$
)0+)'-
- 14 -
2.2 Common Memory Area 2 Cyclic Transmission
When the data of common memory area 2 is exchanged, DI areas

need to be set separately from DO areas.
In any case, a DI/DO area needs to be allocated in the PMC area
beforehand. If the setting of a DI/DO allocation area is changed, the
power needs to be turned off then back on. On the other hand, a part
of common memory area 2 can be dynamically changed by the user
program.
There are two allocation methods for DI areas: ① method for
dynamically changing DI data areas in node units and ② method for
statically fixing a DI data area independently of nodes.
2.2.1 DO data allocation
Procedure

1) Pa13: Area 2 transmit data start address
2) Pa14: Area 2 transmit data size (in words)
3) Pa40: Allocation address (for DO)
4) Pa41: Data size (for DO) (in words)
5) Pa43: Area 2 data exchange condition allocation address
6) Pa44: Switch flag allocation address
Organization of area 2 data exchange condition allocation:
(%7 8 +
2222<, )'=$1+
2222< )**-:%/)+'-;
2222< ##-%>:%/)+'-;
2222<5 )**-:%/)+'-;
Note) This function does not use the hatched portions.
Procedure of dynamic change of common memory area 2 allocation
by the user program:
1) The user program specifies the following in the PMC D area
specified by Pa43 (area 2 data exchange condition allocation
address):
- DO offset
2) Then, the user program writes FFh to the area (switch flag) in
the PMC R area specified by Pa44 (switch flag allocation
address).
3) The CNC monitors the switch flag at all times. When FFh is
written, the node number, DI offset, data size, and DO offset set
in the PMC D area are taken in as internal information, and the
switch flag is set to 00h.
- 15 -
4) Until FFh is written to the switch flag, the CNC writes the DO
data in the PMC area specified by Pa40 (allocation address (for
DO)) to common memory area 2, using the same DO offset.
( (
(%7

2222<,
2222<
--!#
2222< (#(!.9
2222<5 --!#
( ( 0
(%% 2222 4.#'5-1(3 ( ($

:( ( (!.#(#(-
#5 !
("7 (!.#(#(-
(%+
#51'(1
(#( ("%
(%"
(!.#(#(-
#5 !
NOTE
1 When the offset is dynamically changed for DO data
allocation of common memory area 2, the node
number, DI offset, and data size are also changed.
To change only the DO data offset, carefully change
the setting not to change other values.
2 There are the following restrictions on DO data
exchange:
- When 0 is set in Pa41 (data size), DO data exchange
is not performed.
- If a negative value is set in Pa43 (area 2 data
exchange condition allocation address), operation
assumes that the DO offset is 0.
- If a negative value is set in Pa44 (switch flag
allocation address), the DO offset cannot be
dynamically changed.
- When (DO offset + Pa41) > Pa14, DO data exchange
is not performed.
- 16 -
2.2.2 DI data allocation
2.2.2.1 Dynamic DI data allocation of common memory area 2

The user program switches to the DI data area for a target node and
reads the DI data for the node. By specifying a node number, the DI
data from the node and status information of the node can be read.
Procedure

1) Pa42: Allocation address (for DI)
4) Pa46: Area 2 static allocation data size = 0
(%7 8 +
2222<, )'=$1+
2222< )**-:%/)+'-;
2222< ##-%>:%/)+'-;
2222<5 )**-:%/)+'-;
Note) This function does not use the hatched portion.
Procedure of dynamic change of common memory area 2 allocation
by the user program:
address):
- Node number
- DI offset
- Data size
address).
written, the node number, DI offset, data size, and DO offset set
in the PMC D area are taken in as internal information, and the
switch flag is set to 00h. At this time, the CNC once reads DI
data according to the new settings before the switch flag is set to
00h. So, the user program can read DI data immediately after
checking that the switch flag is set to 00h.
4) Until FFh is written to the switch flag, the user program can read
the node information of a specified node number and area 2 DI
data from the R area or the D area.
5) Until FFh is written to the switch flag, the CNC writes the node
information of a specified node number and area 2 DI data to the
specified area in the PMC R area or D area.
- 17 -
( (
(%7

2222<,
2222<
--!#
2222< (#(!.9
2222<5 --!#
( ( 0
(%% 2222 4.#'5-1(3 ( ($

:( ( (!.#(#(-
#5 !
(!.#(#(-
(%$ #5 !
:#;
(#( (!.#(#(-
#5 !
(!.#(#(-
#5 !
- 18 -
NOTE
1 When node information or DI data is dynamically
changed for dynamic DI data allocation of common
memory area 2, the DO offset is also changed. To
change only the DI data, carefully change the setting
not to change another value.
2 Information on other nodes is 4 bytes in size.
So, for an area in the R area to be allocated for DI,
allocate an area 4 bytes larger than the value set in
Dxxxx+4 (data size (in words).
When the user program handles DI data in area 2, the
data at the address 4 bytes shifted from the address
set in Pa42 (allocation address (for DI)) is handled.
3 There are the following restrictions on dynamic DI
data exchange:
- Set a value of 0 in Pa46 (area 2 static allocation data
size).
- If a negative value is set in Pa42 (allocation address
(for DI)), transfer of information on other nodes and
DI data exchange are not performed.
exchange condition allocation address), transfer of
information on other nodes and DI data exchange
are not performed.
- If 0 is specified in Dxxxx+4 (data size) specified by
Pa43 (area 2 data exchange condition allocation
address), transfer of information on other nodes is
performed, but DI data exchange is not performed.
allocation address), the DI data source cannot be
dynamically changed.
- For reasons related to the specifications of the
FANUC FL-net board, set Pa32 (data size), Pa41
(data size), and Dxxxx+4 (data size) so that the total
size of them is 1024 words or less.
4 When DI data exchange is performed with a size
specification with which the local node transmit data
area is contained, data transfer from the common
memory area to the PMC area may overwrite the
PMC area data with the common memory data.
Carefully specify the data size so that the local node
transmit data area is not contained.
- 19 -
2.2.2.2 Static DI data allocation of common memory area 2

This allocation method fixes the DI data area. With this method, an
area larger than that allocated with the dynamic allocation method can
be allocated in the PMC area.
Only node status information can be read by dynamic change.
Procedure

1) Pa42: Allocation address (for DI)
4) Pa45: Area 2 static allocation start address
5) Pa46: Area 2 static allocation data size (in words)
(%7 8 +
2222<, )'=$1+
2222< )**-:%/)+'-;
2222< ##-%>:%/)+'-;
2222<5 )**-:%/)+'-;
Note) This function does not use the hatched portions.
Procedure of node information change by the user program:
The node information on the specified node can dynamically be
checked using the following procedure:
address):
- Node number
address).
written, the node number, and DO offset set in the PMC D area
are taken in as internal information, and the switch flag is set to
00h. At this time, the CNC once updates the specified node
status information according to the new settings before the
switch flag is set to 00h. So, the user program can read the
status information immediately after checking that the switch
flag is set to 00h.
4) Until FFh is written to the switch flag, the user program can read
the node information of a specified node number from the R area
or the D area.
5) Until FFh is written to the switch flag, the CNC writes the node
information of a specified node number to the specified area in
the PMC R area or D area. The DI data can be read regardless
of whether the switch flag is set to 00h.
- 20 -
( (
(%7

2222<,
2222<
--!#
2222< (#(!.9
2222<5 --!#
( ( 0
(%% 2222 4.#'5-1(3 ( ($

:( ( (!.#(#(-
#5 !
(!.#(#(-
(%$ #5 ! (%;

(#( (%" (!.#(#(-
#51'(1
(!.#(#(-
:#;
#5 !
(%+
- 21 -
NOTE
1 As shown in the above example, the area specified by
Pa46 (area 2 static allocation data size (in words))
can contain the local node transmit data area. In
this case, the corresponding PMC area can be
specified for Pa40 (allocation address (for DO)) to
allocate no wasted PMC area.
To make such a setting, however, carefully set Pa40
(allocation address (for DO)) not to duplicate PMC
area setting.
2 Node information can also be changed dynamically
with static DI data allocation of common memory
area 2. When node information is changed,
however, the DO offset is also changed. To change
only the node information, carefully change the
setting not to change the DO offset.
3 Information on other nodes is 4 bytes in size.
So, for an area in the R area to be allocated for DI,
allocate an area 4 bytes larger than the value set in
Pa46 (area 2 static allocation data size (in words)).
When the user program handles DI data in area 2,
the data at the address 4 bytes shifted from the
address set in Pa42 (allocation address (for DI)) is
handled.
4 There are the following restrictions on static DI data
exchange:
- When a value of 0 is specified for Pa46 (area 2 static
allocation data size (in words)), DI data exchange
with dynamic allocation is performed.
- If a negative value is set in Pa42 (allocation address
(for DI)), transfer of information on other nodes and
DI data exchange are not performed.
exchange condition allocation address), transfer of
information on other nodes are not performed.
allocation address), node information cannot
dynamically be changed.
2.2.2.3 Nodes information
- 22 -
Information on other nodes and DI data are allocated in the PMC area
as follows:
(%$ 8 +
<, : -+?';
< (%@(#"+-#
< AA+(#"+-#
< '##
FA link layer state:

5 ! ,
< : -+?';

Upper layer state:

5 ! ,
< !; 5; ; ; 4; ,; ; ;
< ; ; ; ;
B
,,C
,C
2C
6
,C B B

C ;:7%.0-1%;);:)/-1%;
NOTE
For details of each bit, see Subsection 2.3.1,
"Allocation of local node state."
- 23 -
2.2.2.4 Timing of switching between conditions on data exchange

with common memory area 2
In data exchange between common memory area 2 and the PMC area,
the user can switch between data (nodes information) exchange
conditions.
The timing of data switching specified by the user program is
described below.
! < 3 ( 0!#

"/ #! ('5 <( (# .
#5 ( (!<'.-.
0(%7)
$/ #! 5 . #5 !4.#'5 7/ 5'6!#5(##5!4.#'5-1(3
-1(3!<'.-.0(%%) .!!##5)
%/ (!('5<( (# -
#5 ( ( !<'.-.
0(%7)
*/ ='5(3! (#( (
4 (#( ='5(3
'.#.)
8/ 5'6! #5(# #5 !4.#'5 ;/ #!++5.#5!4.#'5-1(3)
-1(3.!!##++5)
>/ - !(#(< '!!.3)
- ! (#( ='5(3
#54(#(='5(3
'.#.- #5.!<.#(
<)
CAUTION
1 If the setting of a parameter in the PMC D area
specified by Pa43 (area 2 data exchange condition
allocation address) is incorrect (for example, if a
specified DI offset exceeds the common memory
area of a specified node number), data exchange is
not performed.
So, be careful when making a data exchange
condition modification.
2 Do not access the DI data of common memory area
2 until the switch flag is set to 00h after the switch
flag is set to FFh by the user program. Otherwise,
invalid data may be read.
NOTE
Immediately after the power is turned on, data
exchange is performed according to each parameter
set in the PMC D area specified by Pa43 (area 2
data exchange condition allocation address) even if
no instruction is provided by the user program.
- 24 -
2.3 Node State Monitoring
2.3.1 Allocation of local node state
The state of the local node can be monitored by allocating the 6-byte
state code of the local node in the PMC R area.
If a negative value is set in Pa20 (local node information address),
local node information is not posted.
Procedure
Set the following parameter beforehand:

1) Pa20: Local node information address
Local node information is allocated in the PMC R area as follows:
($+ 8 +
<, )&#()'-#
< (%@-#
< AA+(#"+-#
<
=++
?#(=
Local node state:

5 ! ,
<, : -+?';

Table 2-1 Local Node State

Item Description
Token monitoring time Set when transmission does not
error flag terminate within the token monitoring
time (Pa15) set for the local node.
Initialization error flag Set when an initialization parameter or
a parameter set again is invalid.
Reception wait state Set when the node enters the frame
flag reception wait state without receiving
any frame during network initialization.
Duplicate node number Set when a node having the same node
flag number as for the local node is detected
in the network.
- 25 -
FA link state:
5 ! ,
< : -+?';

Table 2-2 FA Link State

Item Description
Node participation flag Indicates whether the node participates
in the network (1) or is disconnected
from the network (0).
Upper layer operation Currently, not supported.
signal error flag
Common memory data Set when cyclic data is valid, in other
valid flag words, when PMC area allocation is
normal.
Common memory Set when node common memory
setting complete flag setting is complete, in other words,
when the parameters related to the
common memory setting (Pa11, Pa12,
Pa13, and Pa14) are valid.
Duplicate address Set when a common memory setting for
detection flag a node connected to the network is
duplicate, in other words, when the
value specified for a parameter (Pa11,
Pa12, Pa13, or Pa14) for another device
is specified for a parameter related to
the common memory setting (Pa11,
Pa12, Pa13, or Pa14).
Upper layer state:

5 ! ,
< !; 5; ; ; 4; ,; ; ;
< ; ; ; ;
B
,,C
,C
2C B B

6 ;:7%.0-1%;);:)/-1%;
,C :0%-&)'%-)=-'/%00%-
C '?%&;
- 26 -
Table 2-3 Upper Layer State

Item Description
U_ERR_CODE Currently, not supported.
U_ERR Currently, not supported.
RUN/STOP The RUN/STOP state of the PMC
ladder program is set.
Current RCT value:

5 ! ,
< 4; ,; ; ; ; ; !; 5;
<! ; ; ; ; !; 5; ; ;
Current RCT value:

1) (Highest bit) to 16) (Lowest bit)
RCT (Refresh Cycle Time):
120% of the real time required for a token to pass through
all nodes (Unit: ms)
- 27 -
2.3.2 Allocation of a list of participating nodes
A list of the numbers of the nodes participating in the network can be

allocated in the PMC R area to monitor the participation state.
When a negative number is set in Pa21 (participating node
information address), participating node list information is not posted.
Procedure
Set the following parameter beforehand:

1) Pa21: Participating node information address
Participating node information as indicated below is allocated in the

PMC R area.
($" 5 ! ,
<,

<
：
<,

<
The bits of node numbers (including the local node) that participate in
the network are set to 1.
- 28 -
2.4 Byte List of Cyclic Data
A byte list in a common memory area is related with a byte list in the
PMC area as described below.
Common memory area 1 and the PMC area
0( ("

#+#
"* + 8 +
<,,,, 7 <,, 7
<,,, !57 <, 7
<, 7
<, !57
Common memory area 2 and the PMC area
0( ($

#+#
"* + 8 +
<,,,, 7 <,, 7
<,,, !57 <, 7
<, 7
<, !57
NOTE
The data width of each address in a common
memory area of the FL-net is 16 bits.
On the other hand, the data width of each address in
the PMC area is 8 bits. So, data is exchanged
between the common memory areas and the PMC
area according to the relationships shown above.
- 29 -
2.5 Data Concurrency

With the FANUC FL-net function, when a ladder program handles
input/output signals, the data concurrency is guaranteed in long-data
(4-byte-data) units and in word-data (2-byte-data) units under the
following constraints.
Data concurrency in long-data (4-byte-data) units

① The allocation start addresses in common memory and in the PMC
area are on 4-byte boundaries.
② The PMC ladder program uses the following instructions in 4-byte
units:
DECB, CODEB, DCNVB, COMPB, DSCHB, XMOVB, ADDB,
SUBB, MULB, DIVB, NUMEB, MOVN, EOR, AND, OR, and
NOT instructions
NOTE
If the above constraints are not satisfied, the
concurrency of long data cannot be guaranteed.
Data concurrency in word-data (2-byte-data) units

① The allocation start addresses in common memory and in the PMC
area are on 2-byte boundaries.
② The PMC ladder program uses the following instructions in 2-byte
units:
DECB, CODEB, DCNVB, COMPB, DSCHB, XMOVB, ADDB,
SUBB, MULB, DIVB, NUMEB, MOVW, MOVN, EOR, AND,
OR, and NOT instructions
NOTE
If the above constraints are not satisfied, the
concurrency of word data cannot be guaranteed.
Data concurrency in byte-data (1-byte-data) units

There is no constraint.
The data concurrency is always guaranteed in 1-byte-data units.
- 30 -
When handling data input from the FL-net, note the following points:
NOTE
1 When the PMC R area or D area is used as the input
data area, the synchronous buffer in the PMC is not
used. For this reason, input data may change during
ladder 1 scan.
In other words, the value updated via the FL-net may
be read, depending on the read timing, even when the
ladder program handles data in the same area.
2 The concurrency of data longer than long data (4-byte
data) is not guaranteed. To establish the
concurrency of such data, see "Measures to guarantee
the concurrency of multiple-byte data" following.
- 31 -
Measures to guarantee the concurrency of multiple-byte data
An example of handling input data of multiple-byte on the second

ladder level to guarantee its concurrency is given below. To
establish the concurrency of data tens to hundreds of bytes long, it is
simple to perform data transmission with transmission of a message
with confirmation. For details of transmission of a message with
confirmation, see Section 3.7, "Server Function of Transmitting a
Message with Confirmation."
Example of measures: Control using a flag for synchronization
This control method provides a flag for synchronization before and

after multiple-byte data to synchronize the data. An example of
guaranteeing the concurrency of 6-byte data is described below.
1) Data structure
A flag for synchronization is provided in the byte preceding the
2-byte data and in the byte following the 2-byte data, thus
extending the 2-byte data to 8-byte data.
R0099 Flag 1 for
synchronization
R0100 Data section
R0105
R0106 Flag 2 for
synchronization
2) Processing by the data writing side

The data is updated according to the procedure below.
(1) Flag 1 for synchronization is incremented.
(2) The data section is updated.
(3) The same value as flag 1 for synchronization is set in flag 2
for synchronization.
3) Processing by the data reading side

The data is processed according to the procedure below.
(1) The eight bytes starting with R0099 are copied to the area
for synchronization (R0199) at the start of the second level.
(2) A check is made to see if R0199 = R0206.
(3) If R0199 = R0202, R0200 is processed as 6-byte data.
CAUTION
If the size of data to be synchronized is increased by
combining many bytes of data at a time, the data
may not be synchronized easily.
In such a case, divide the data at each variable, for
example, and provides flags for synchronization.
- 32 -
2.6 Notes on Allocation in the PMC Area
When allocating common memory area 1 and area 2 in the PMC area,
observe the following caution.
CAUTION
For reasons related to the specifications of the FANUC
FL-net board, set the size of common memory area 1
and area 2 of the local node that are allocated in the
PMC area and the size of common memory area 1
and area 2 of another node that are allocated in the
PMC area so that the total size of them is 1024 words
or less.
Example of setting
When the common memory areas of the following sizes are allocated
for nodes #A, #B (local node), #C, and #D:
Node #A: Area 1→A1 words Area 2→A2 words
Node #B: Area 1→B1 words Area 2→B2 words
Node #C: Area 1→C1 words Area 2→C2 words
Node #D: Area 1→D1 words Area 2→D2 words
- 33 -
Example: Allocating DO data of local node B and DI data of node C in the PMC area
Assume that the size of allocation of area 1 in the PMC area is 512
words (all of common memory area 1). Also assume that the size of
DO data in area 2 of the local node that is allocated in the PMC area
is B2" words. In this case, allocation of DI data in area 2 of node #C
in the PMC area is performed as follows:
When B1 + C1 + B2" + C2 <= 1024, all of C2 words can be allocated.
When B1 + C1 + B2" + C2 > 1024, up to 1024 - B1 - C1 - B2" (=
C2") words can be allocated.
( ( ! "

?
?
?
?
?
?
?
?
?
?
#$
! "
%&#
?
?

!&# ?
?
?

?
?
?
?
?
NOTE
When all of common memory area 1 is allocated in the
PMC area, the value to be noted is also the sum of the
sizes of allocation of the local node area and another
node area in the PMC area.
In other words, when DI data of node #D is read under
the same conditions as for the above example, DI
data in common memory area 2 that satisfies (1024 -
B1 - D1 - B2”) can be read at a time.
- 34 -
B-63434EN/02 DESCRIPTION 3.MESSAGE TRANSMISSION
3 MESSAGE TRANSMISSION
This chapter details how to use the message transmission function of
the FL-net function with the Series 16i/18i/21i-A with the Power
Mate i.
- 35 -
3.MESSAGE TRANSMISSION DESCRIPTION B-63434EN/02
3.1 List of Message Transmission Services
The message transmission function of the FANUC FL-net function

supports the services listed in Table 3-1.
Table 3-1 List of Services Supported

Message service item Client function Server function
Byte block read
Byte block write
Word block read
Word block write
Network parameter read -
Network parameter write -
Stop command - -
Start command - -
Profile read -
Log data read -
Log data clear -
Transparent message (Note) (Note)
Echo back message (for test) -
NOTE
Among the transaction codes assigned to transparent
messages, 50000 to 59999 are used for this
transparent message.
- 36 -
3.2 Procedure of the Message Transmission Function
The function for transmitting messages other than transparent

messages involves a client function and server function. For a
message transmitted from the client, the server returns a response
message. In short, the client is a service requester, and the server is
a service receiver.
With the server function for each type of message transmission of the
FANUC FL-net function, a response message is automatically
returned to the client without involving the user program in response
to a received message. With the client function, the user program
transmits a message by using the interface area set by Pa50 (interface
allocation address).
Client Server
User program User program
System System
-A)-$--#.
D=-$--#. FL-net
A transparent message can be handled freely by the user program

without making a client/server distinction. So, two interface areas
are required: one for transmission and the other for reception. As
the transmit interface area, the interface area set by Pa50 (interface
allocation address) used with a client message is used. As the
receive interface area, the interface area set by Pa52 (transparent
receive message allocation address) is used.
User program User program
System System
--#.
--#. FL-net
- 37 -
The format of each interface area is described below.
Transmit interface for the client and transparent messages
The interface area specified by Pa50 (interface allocation address) has

the format shown below.
7 0
(*+ +0 Transmission
request/response flag
+2 Request status (R_STS)
+3 Response status
(M_RLT)
+4 Cancel flag
+5 Destination node (*"
number
+6 (Reserved)
+8 Message section
NOTE
The message section does not include a data buffer
area.
- 38 -
Table 3-2 Transmit Interface Items

Interface item Description Direction
Transmission Flag set by the user program to request message U→S
request/response transmission, and set by the CNC to post the reception of S→U
flag(Note 1) a response message or the occurrence of an error.
0001h: The user program requests message
transmission.
8000h: The system posts the reception of a
normal response message.
The system posts the transmission of a
normal transparent message.
8100h and up: The system posts a request message
format error.
8200h and up: The system posts a request message
transmission error.
8300h and up: The system posts the reception of an
abnormal response message.
8800h: The system posts the acceptance of
cancellation from the user program.
Request status Status for checking if a request message has been S→U
(R_STS) delivered.
01h: A request message has been delivered to the
server normally.
02h: Server buffer file
03h: The server is not initialized yet.
05h: Serial number/version number error
06h: Format error
Response status Status for checking a response message S→U
(M_RLT) 00h: Normal response
01h: Abnormal response
02h: Server service not supported
Cancel flag Set a value other than 0 for service cancellation before a U→S
(Note 2) message responding to a transmission request is
returned. The purpose of this cancellation is just to allow
the system to accept the next transmission request. This
cancellation is not intended to cancel message
transmission with the FL-net function.
Destination node Message transmission destination node number U→S
number
Message section Area for setting a message transaction code, parameters, U→S
and so forth. The information set in this area depends on S→U
the type of message transmission service.
The column of direction in the table above indicates whether each

item is posted from the user program to the system (U→S) or is
posted from the system to the user program (S→U).
- 39 -
CAUTION
Ensure that while the transmission request/response
flag is set to 0001h, the user program does not rewrite
the data in this interface area. Otherwise, message
transmission may not be terminated normally.
NOTE
1 When a service is terminated normally, 8000h is
returned to this flag. If a value other than 8000h is
returned, check the value, and resolve the problem.
See Table 3-3 for the error codes returned from the
system.
2 After a message transmission request is made, this
interface does not allow the next transmission
request to be made until a response message is
received or an error occurs. So, if a response
message cannot be received for a cause on the
server, the next message transmission request
cannot be made until the power is turned off. In
such a case, the cancel flag allows the system to exit
from the response message wait state and wait for
the next message transmission request. The
purpose of this cancellation is just to allow the
system to accept the next message transmission
request. This cancellation is not intended to cancel
message transmission with the FL-net function.
(The FL-net function does not have a function for
canceling message transmission.) This means that
when this cancellation function is used, the response
message for the previous message request may be
treated as a response to the next message request
by mistake.
- 40 -
Table 3-3 Error Codes of the Transmit Interface

Error code Description
8101h A specified node number is incorrect.
8102h A specified transaction code is incorrect.
8103h An area specified as a transmit/receive buffer in the PMC R
area exceeds the allowable range.
8104h In word block data, an odd address is specified as a
transmit/receive buffer area in the PMC R area.
8105h Excessive data size
8202h Server buffer file
8203h The server is not initialized yet.
8205h Server serial number/version number error
8206h Server format error
8210h Retry failure (no response from the server)
8301h Abnormal response reception
8302h Server service not supported
- 41 -
Receive interface for transparent messages
The interface area specified by Pa52 (transparent receive message

allocation address) has the format shown below.
7 0
(*$ +0 Receive flag
+2 Transmission source node

number
+3 (Reserved)
+4 Transaction code
(*7
+6 Size
+8 Data
Table 3-4 Transparent Message Receive Interface Items

Receive flag Flag used by the system to post the reception of a S→U
transparent message to the user program. U→S
0001h: The system posts the reception of a transparent
message.
0000h: The user program posts the completion of
message receive processing.
Transmission Transparent message transmission source node number S→U
source node
number
Transaction code Transaction code of a received transparent message S→U
Size Number of words of data contained in a received S→U
transparent message
Data Data contained in a received transparent message S→U
- 42 -
3.3 Procedure for Message Transmission Operation
This section describes the procedure of operations between the user

program and system required to perform the message data
transmission client function and transparent message function.
3.3.1 Procedure for operating the message transmission client

function

(%
-+A+).+#$ "-$
"/ !!(3 < <( (#.
('5 !#(#! -1(3 .!
'1( )
$/ (!.!!. @!# 7/ 5'6.3 #5(# #5
-1(3←+++"5 # (!.!!. @!# -1(3
.!!##+++"5
%/ @!# !!(3
# (!.!!.
>/ 5'6.3 @!#!#(#! 8/ '<#.
""/ !<! !!(3
'<#.
"*/ 5'6.3 #5(# #5 "$/ !<!-1(3←>+++5
!<! -1(3 .! !# #
>+++5)
";/ 5'6.3 !<! "7/ '<#.
!#(#!
"8/ !<! !!(3
< '!!.3
">/ 1( .3 #5 !<!
-1(3#++++5
+?+
-+A+).+#$ "-$

- 43 -
3.3.2 Procedure for operating the transparent message

transmission function
(!<( #!!(3# (!.!!.!.
! < 3 ( 0!#
"/ (!<( # !!(3
< <( (#.
('5 !#(#! -1(3 .!
'1( )
$/ (!.!!. @!# 7/ 5'6.3 #5(# #5
-1(3←+++"5 # (!.!!. @!# -1(3
.!!##+++"5
%/ (!<( # !!(3
# (!.!!.
"$/ 5'6.3 @!#!#(#! ""/ '<#.
"%/ 5'6.3 #5(# #5 "7/ <1#.-1(3←>+++5
'<1#.-1(3.!!##
>+++5
"*/ 1( .3 #5 '<1#.
-1(3#++++5
(!<( #!!(3 '<#.!.

! < 3 ( 0!#
*/ (!<( # !!(3
'<#.
;/ # (!.!!.
>/ 5'6.3 #5(# #5 8/ '.A-1(3←+++"5
'.A -1(3 .! !# #
+++"5
&/ '.A !!(3
< '!!.3
"+/ 1( .3#5 '.A-1(3
#++++5
- 44 -
3.4 Message Transmission Client Function
This section describes the detailed interface of each service of the

message transmission client function.
3.4.1 Byte block read

Request message Response message
(*++0
7 0 7 0
Transmission request +0 Response flag
flag
0001h
+2 +2 Request status
+3 +3 Response status
+4 Cancel flag +4
+5 Destination node +5
number
+6 (Reserved) +6 (Reserved)
+8 Transaction code +8 Transaction code (*"
65003 65203
+12 Offset address on +12 Offset address on

virtual address space virtual address space
+16 Data size +16 Data size
+18 Read data buffer start +18 Read data buffer start
address address
(Reserved) Read data
- 45 -
Table 3-5 Byte Block Read Interface Items

Transaction code Request message: 65003 U→S
Response message: 65203 S→U
Offset address on Request message: Offset address on virtual address U→S
virtual address space of byte block data to be read
space from the server
Response message: Same as above
Data size Request message: Size of byte block data to be read U→S
from the server (in bytes) S→U
Response message: Size of byte block data actually
read from the server (in bytes)
Read data buffer Request message: Start address of an area in the U→S
start address PMC R area used to store byte
block data read from the server
Read data Request message: Reserved S→U
Response message: Byte block data actually read from
the server. When an abnormal
response is returned, an error code
is stored.
NOTE
For an error code stored when an abnormal
response is returned, refer to the manual of the
equipment of a message transmission destination.
- 46 -
3.4.2 Byte block write

(*++0
7 0 7 0
flag
0001h
+4 Cancel flag +4
number
65004 65204

+18 Write data buffer start +18 Write data buffer start
address address
Write data (Reserved)

Error code when an
abnormal response is
returned
- 47 -
Table 3-6 Byte Block Write Interface Items

virtual address space of byte block data to be
space written to the server
Data size Request message: Size of byte block data to be written U→S
to the server (in bytes) S→U
Response message: Size of byte block data actually
written to the server (in bytes)
Write data buffer Request message: Start address of an area in the U→S
start address PMC R area storing byte block data
to be written to the server
Write data Request message: Byte block data to be written to the U→S
server S→U
Response message: An error code is stored when an
abnormal response is returned.
NOTE
- 48 -
3.4.3 Word block read

(*++0
7 0 7 0
flag
0001h
+4 Cancel flag +4
number
65005 65205

+18 Read data buffer start +18 Read data buffer start
address address
(Reserved) Read data
- 49 -
Table 3-7 Word Block Read Interface Items

virtual address space of word block data to be
space read from the server
Data size Request message: Size of word block data to be read U→S
from the server (in bytes) S→U
Response message: Size of word block data actually
read from the server (in bytes)
Read data buffer Request message: Start address of an area in the U→S
start address PMC R area used to store word
block data read from the server
Read data Request message: Reserved S→U
Response message: Word block data actually read from
the server. When an abnormal
response is returned, an error code
is stored.
NOTE
- 50 -
3.4.4 Word block write

(*++0
7 0 7 0
flag
0001h
+4 Cancel flag +4
number
65006 65206

+18 Write data buffer start +18 Write data buffer start
address address
Write data (Reserved)

Error code when an
abnormal response is
returned
- 51 -
Table 3-8 Word Block Write Interface Items

virtual address space of word block data to be
space written to the server
Data size Request message: Size of word block data to be U→S
written to the server (in bytes) S→U
Response message: Size of word block data actually
written to the server (in bytes)
Write data buffer Request message: Start address of an area in the U→S
start address PMC R area storing word block
data to be written to the server
Write data Request message: Word block data to be written to the U→S
server S→U
Response message: An error code is stored when an
abnormal response is returned.
NOTE
- 52 -
3.5 Message Transmission Server Function
3.5.1 Error code list
In response to a request from a client, the message data transmission

server function automatically returns a response message without
involving the user program. If the message transmission client
receives an abnormal response, the FANUC FL-net function returns a
code listed in Table 3-9.
Table 3-9 List of Server Function Error Codes

Error code Description
8001h An attempt was made to access a nonexistent PMC area.
8002h A specified data size exceeded 1024 bytes.
8003h An attempt to allocate a parameter storage area failed.
8004h A request was made to write to a write-prohibited area.
- 53 -
3.5.2 Virtual address space allocation
Virtual address space used to read/write byte block and read/write

word block is allocated in the PMC area as described below.
Virtual address space for byte block data

Table 3-10 Virtual Address Space for Byte Block Data
Allocation in PMC Virtual address Remarks
Symbol Type of signal Address space
(decimal) (hexadecimal)
X Signal from machine to X0000 or 0000h or later Read only
PMC later
Y Signal from PMC to Y0000 or 4000h or later Read only
machine later
F Signal from CNC to PMC F0000 or 8000h or later Read only
later
G Signal from PMC to CNC G0000 or C000h or later Read only
later
R Internal relay R0000 or 10000h or later Read/write
later
D Data table D0000 or 14000h or later Read/write
later
Virtual address space for word block data

Table 3-11 Virtual Address Space for Word Block Data
X Signal from machine to X0000 or 0000h or later Read only
PMC later
Y Signal from PMC to Y0000 or 2000h or later Read only
machine later
F Signal from CNC to PMC F0000 or 4000h or later Read only
later
G Signal from PMC to CNC G0000 or 6000h or later Read only
later
R Internal relay R0000 or 8000h or later Read/write
later
D Data table D0000 or A000h or later Read/write
later
NOTE
Only installed address space in the PMC can be
accessed. Check PMC address space before use.
- 54 -
3.6 Transparent Message Transmission Function
With the FANUC FL-net function, a transparent message of a

transaction code (50000 to 59999) can be used as a transparent
message for data transmission/reception by the user program. This
section details the interface used for transmission and reception using
the transparent message transmission function.
3.6.1 Transparent message transmission

Transmission request Transmission
message completion message
(*++0
7 7
Transmission request +0 Completion flag
flag
0001h
+3 (Reserved) +3
+4 Cancel flag +4
number
+6 (Reserved) +6 (Reserved) (*"
+8 Transaction code +8 Transaction code
50000 to 59999 50000 to 59999
+18 Transmit data buffer +18 Transmit data buffer

start address start address
Transparent transmit (Reserved)

data
NOTE
Note that when the destination node number is set to
255, the message is transmitted to all nodes.
- 55 -
Table 3-12 Transparent Transmit Message Interface Items

Transaction code !,,,,)!4444 U→S
Data size Size of transparent data to be transmitted (in words) U→S
Transmit data Start address of an area in the PMC R area storing U→S
buffer start transparent data to be transmitted
address
Transparent Transparent data to be transmitted U→S
transmit data
- 56 -
3.6.2 Transparent message reception

Reception notification Reception confirmation
message message
7 0 7 0
(*$+0 Receive flag +0 Completion flag
0001h
+2 Transmission source +2
node number
+3 (Reserved) +3
+4 Transaction code +4 Transaction code
50000 to 59999 50000 to 59999 (*7
+8 Transparent receive +8 Transmit data buffer

data start address
Table 3-13 Transparent Receive Message Interface Items

Receive flag When a transparent message is received, this flag is set to S→U
0001h after the interface items below are set.
Transmission Node number of a transmission source that transmitted a S→U
source node transparent message
number
Transaction code !,,,,)!4444 S→U
Data size Size of received transparent data (in words) S→U
Transparent Transparent data received S→U
receive data
When a transparent message is received, a R_STS code with a

meaning indicated below may be returned to the transparent message
transmission client.
Table 3-14 Meanings of R_STS Codes Returned to the Transparent

Message Transmission Side
R_STS value Description
02 (buffer full) The previously received transparent message is not
processed by the user program.
03 (not initialized) An interface area for receiving a transparent message
is not allocated.
06 (format error) A transparent message actually received is larger than
a receive data area allocated by this interface.
Transparent data actually received consists of an odd
number of bytes.
- 57 -
3.7 Server Function of Transmitting a Message with

Confirmation
When an ordinary byte block read/write or word block read/write

service of the message transmission server function is executed, data
is exchanged with the client without user-program intervention.
Data can also be exchanged with user-program intervention using a
specific virtual address space specification.
This specification can be used to establish the concurrency of data
tens to hundreds of bytes long easily. In this case, the user program
must transmit a response message, however.
This section details the interfaces used for transmission and reception
using the function of transmitting a message with confirmation.
These interfaces use the transmission and reception areas for
transparent message transmission.
To perform transmission of a message with confirmation, specify an
address with an offset of 1000000h in the ordinary virtual address
space.
3.7.1 Reception of a message with confirmation
'<#.#.-.'(#. '<#.
!!(3 '-. (#.!!(3
8 + 8 +
(*$
<, <,
&%?*(#.
)$A(%)*(#.
,,,0 ,,,,0
< (!.!!.! ' <

< : -+?'; <
< < (*7
+#-#&%)&)' +#-#&%)&)'
5!,,)5!,,5 5!,,)5!,,5
<5 ##-%> <5 ##-%>
< --!#( !! < --!#( !!

A. #(1( !!!<(' A. #(1( !!!<('
< <
- 58 -
Table 3-1 Receive Message Interface Items

Receive flag When a message is received, this flag is set S→U
to 0001h after the interface items below are
set.
Transmission Number of the node which transmitted a S→U
source node message
number
Transaction 65003 to 65006 S→U
code
Data size Size of received message data S→U
Virtual address Offset address on virtual address space S→U
space
Write data Received write request data S→U
When a message with confirmation is received, an R_STS code with a

meaning indicated below may be returned to the message transmission
client.
Table 3-2 Meanings of R_STS Codes Returned to the Transmission Side of

Transmission of a Message with Confirmation
R_STS value Description
02 (buffer full) The previously received message is not processed by
the user program.
03 (not initialized) An interface area for receiving a message is not
allocated.
06 (format error) A message actually received is larger than a receive
data area allocated by this interface.
Word block data actually received consists of an odd
number of bytes.
- 59 -
3.7.2 Response message transmission
(!.!!. @!# (!.!!.

!!(3 '<1#.!!(3
(*+ 8 + 8 +
<, <,
!
)$A(%)*(#.
,,,0
< < D=--#=-
< <
<
#&(*(#. <
<! <!
" #
<5 : -+?'; <5 : -+?';
< +#-#&%)&)' < +#-#&%)&)' (*"
5!,)5!,5 5!,)5!,5
<, : -+?'; <, : -+?';
< --!#( !! < --!#( !!

A. #(1( !!!<(' A. #(1( !!!<('
<5 ##-%> <5 ##-%>
< <
Table 3-3 Response Message Interface Items

Transaction 65203 to 65206 U→S
code
Virtual address Offset address on virtual address space U→S
space
Data size Size of data to be transmitted U→S
Transmit data Start address of an area in the PMC R area U→S
buffer start containing data to be transmitted
address
Read data Read request data for response U→S
NOTE
The procedure for transmission of a message with
confirmation is the same as for the transparent
message transmission function.
- 60 -
3.7.3 Virtual address space allocation
Virtual address space used for byte block read/write and word block
read/write with confirmation is allocated in the PMC area as
described below.
Virtual address space for byte block data with confirmation
Table 3-4 Virtual Address Space for Byte Block Data with Confirmation
X Signal from machine X0000 or 01000000h or Read only
to PMC higher higher
Y Signal from PMC to Y0000 or 01004000h or Read only
machine higher higher
F Signal from NC to F0000 or 01008000h or Read only
PMC higher higher
G Signal from PMC to G0000 or 0100C000h or Read only
NC higher higher
R Internal relay R0000 or 01010000h or Read/write
higher higher
D Data table D0000 or 01014000h or Read/write
higher higher
Virtual address space for word block data with confirmation
Table 3-5 Virtual Address Space for Word Block Data with Confirmation
X Signal from machine X0000 or 01000000h or Read only
to PMC higher higher
Y Signal from PMC to Y0000 or 01002000h or Read only
machine higher higher
F Signal from NC to F0000 or 01004000h or Read only
PMC higher higher
G Signal from PMC to G0000 or 01006000h or Read only
NC higher higher
R Internal relay R0000 or 01008000h or Read/write
higher higher
D Data table D0000 or 0100A000h or Read/write
higher higher
NOTE
Only installed address space in the PMC can be
accessed. Check PMC address space before use.
- 61 -
3.8 Byte List of Message Data
The order of data transmission on the network in message

transmission is related with the byte list in the PMC area as shown
below.
Byte block data and the PMC area
3"1()&@'##
#+#
8 + 8 +
<,, 7 <,, 7
<, 7 <, 7
<, !57 <, !57
<, 7 <, 7
Word block data and the PMC area
)+'1()&@'##
#+#
"* + 8 +
<,,,, 7 <,, 7
<,,, !57 <, 7
<, 7
<, !57
Transparent data and the PMC area
+#-A#+'##
#+#
"* + 8 +
<,,,, 7 <,, 7
<,,, !57 <, 7
<, 7
<, !57
NOTE
FL-net word block data and transparent message
data are 16 bits wide. On the other hand, the data
width of each address in the PMC area is 8 bits.
So, the relationships indicated above apply when
data is exchanged between FL-net messages and
the PMC area.
- 62 -
III. OPERATION
B-63434EN/02 OPERATION 1.PARAMETER SETTING
1 PARAMETER SETTING
This chapter describes the parameters required to operate the FL-net
function with the Series 16i/18i/21i-A,and with the Power Mate i and
the method of setting the parameters.
- 65 -
1.PARAMETER SETTING OPERATION B-63434EN/02
1.1 Overview
The parameters for the FL-net function are divided into five major
groups:
(1) Basic parameters
(2) State monitoring parameters
(3) Area 1 allocation parameters
(5) Message allocation parameters
Each parameter is detailed below.
(1) Basic parameters

Table 1-1 Basic Parameters
Parameter name Description Index number
IP address IP address of the local node Pa10
(The host address section of this IP address
is the node number of the local node.)
Start address of area Start address of an area 1 area allocated as Pa11
1 transmit data DO of the local node
Area 1 transmit data Data size of an area 1 area allocated as DO Pa12
size of the local node
Start address of area Start address of an area 2 area allocated as Pa13
2 transmit data DO of the local node
Area 2 transmit data Data size of an area 2 area allocated as DO Pa14
size of the local node
Token monitoring Token hold time of the local node Pa15
time
Allowable minimum Inter-frame time interval requested to Pa16
frame interval another node
Node name Equipment name of the local node Pa17
(2) State monitoring parameters

Table 1-2 State Monitoring Parameters
Local node Start address of an area in the PMC R area Pa20
information address used as the output destination of status
information about the local node
Participating node Start address of an area in the PMC R area Pa21
information address used as the output destination of a list of all
nodes participating in the network
- 66 -

Table 1-3 Area 1 Allocation Parameters
Allocation address Start address of an area in the PMC R area Pa30
(shared for DI/DO) allocated to area 1
Area 1 address Start address of area 1 allocated to an area Pa31
(shared for DI/DO) in the PMC R area
Data size (shared for Size of data to be exchanged Pa32
DI/DO)

(for DO) or D area that serves as the source of data to
be written to area 2
Data size (for DO) Size of data written to area 2 Pa41
(for DI) or D area that serves as the read destination
of information about other nodes and data
from area 2
Area 2 data Address of an area in the PMC D area that is Pa43
exchange condition used to specify conditions on data exchange
allocation address with area 2
Switch flag Flag for switching between specified Pa44
allocation address conditions at the area 2 data exchange
condition allocation address above
Static area 2 address Start address of static area 2 to be allocated Pa45
(for DI) in the PMC area
Static data size Size of data statically exchanged Pa46
(for DI)
(5) Message allocation parameters

Table 1-5 Message Allocation Parameters
Interface allocation Start address of an area in the PMC R or D Pa50
address that serves as the start address of an
interface used for message transfer
Interface allocation Maximum allowable size of the interface area Pa51
size used above
Transparent receive Start address of an area in the PMC R area Pa52
message allocation or D area that serves as the start address of
address an interface used to store transparent
message receive data
Transparent receive Maximum allowable size of the interface area Pa53
message allocation used above
size
- 67 -
For each FL-net function used, the parameters below need to be set.
A. Cyclic transmission of common memory area 1

Basic parameters
Area 1 allocation parameters
B. Cyclic transmission of common memory area 2
Basic parameters
C. Message transmission
Basic parameters
Message allocation parameters
For B (Cyclic transmission of common memory area 2) and C

(message transmission) above, operation based on a user program
needs to be performed as required. For information about required
operation, see Chapter II DESCRIPTION Section 2.2 and Chapter 3,
respectively.
When the state monitoring parameters are set, the user program can
monitor the state of the local node and the network participation state
of other nodes. Perform node state monitoring as required.
CAUTION
Input/output data in common memory area 1 and
common memory area 2 is transferred
asynchronously with ladder program execution. So,
the concurrency of input/output data consisting of
multiple bytes may not be guaranteed. When word
data is input or output, for example depends on the
setting condition, the higher byte may be updated
some time after the lower byte is updated. For
details, see Chapter II DESCRIPTION Section 2.5.
- 68 -
1.2 Setting of Parameters
Before the FL-net function can be used, the parameters described

below must be set.
1.2.1 Series 16i/18i/21i-A
Procedure
(1) Press the SYSTEM key, then press soft key [PMC] to switch to
the PMC screen.

(2) Press soft keys [PMCDGN], [I/OCHK], and [FL-NET] in this
order. Then, screen 1-1 shown below appears.
Screen 1-1 FL-net Main Menu Screen (for the 10.4" LCD)
This screen also displays the MAC address (Ethernet address) of

the FL-net board.
When a soft key on this screen is pressed, the corresponding
screen is displayed as follows:
1) [PRMTR]: Parameter setting screen for using the FL-
net function
2) [NODE]: Monitor screen of the Participating Node
Management Table
3) [NETWRK]: Monitor screen of the FL-net network
parameters
4) [LOG]: Monitor screen of the log of the local
node
- 69 -
(3) Pressing soft key [PRMTR] displays screen 1-2.

If data is already registered, the data is displayed.
(4) With the MDI keys and soft keys, enter/update data.
Screen 1-2 FL-net Parameter Setting Screen (for the 10.4" LCD)
(5) Only when a parameter for which "----" is displayed on the

screen above is set, soft key [DISABL] is displayed. When
such a parameter is not to be used, press soft key [DISABL].
Then, "----" is displayed for the parameter to disable its use.
When such a parameter is to be used, enter a desired value as
with other parameters.
CAUTION
When a parameter to be allocated to the PMC area is
not to be used, be sure to "disable" the parameter.
For example, when 0 is set in OWN STATUS, R0000
in the PMC area is assumed to be allocated, and the
FL-net board may use an area starting at R0000. In
such a case, press soft key DISABL so that the
setting becomes "R----."
- 70 -
Setting item
Each setting item is described below.
Basic parameters
The basic parameters are used to set the FL-net function itself.
Table 1-6 Basic Parameters

Item Description
IP ADDRESS IP address of the local node.
The host address section (last numeric value) of this IP
address is the node number of the local node.
Pa10 Only an IP address in class C can be specified.
NODE NAME An arbitrary node name not longer than 10 characters can be
specified.
Pa17 Lowercase letters cannot be displayed and entered.
AREA1 ADDR Start address of common memory area 1 of the local node.
(Note 1) Pa11 A value from 0 to 511 can be set.
AREA1 SIZE Data size of common memory area 1 of the local node.
AREA2 ADDR Start address of common memory area 2 of the local node.
AREA2 SIZE Data size of common memory area 2 of the local node.
TOKEN WATCH Token monitoring time.
(Note 2) Maximum duration of time for which the local node can hold
the token.
Pa15 A value from 1 to 255 can be set. (Unit: ms)
MIN FRAME Minimum allowable frame time interval.
A value from 0 to 50 can be specified. (Unit: 100 µs)
Set an inter-frame time interval so that the local node can
Pa16 receive data frames in succession. Usually, set 10 (1 ms).
NOTE
1 For common memory area 1, a value beyond 512
must not be specified. For common memory area
2, a value beyond 8192 must not be specified.
Otherwise, the FL-net function cannot participate in
the network.
2 A token monitoring time is set to reissue a token. If
the local node does not issue a token when the time
specified in this parameter has elapsed, the next
node reissues a token. This means that an
adequate value needs to be set in connection with
the amount of transmit data of the local node.
Usually, set 50 (50 ms).
- 71 -
State monitoring parameters
The state monitoring parameters are used to allocate areas in the PMC
area to which the states of the local node and other nodes are posted.
Table 1-7 State Monitoring Parameters

Item Description
OWN STATUS Specify the start address of an area in the PMC R area to
which the communication state of the local node is posted.
When this area is not used, set -1, or press soft key [DISABL].
This parameter allows only an even address to be set.
Pa20
ENTRY NODE Specify the start address of an area in the PMC R area to
which the network participation state of other nodes is posted.
When this area is not used, set -1, or press soft key [DISABL].
This parameter allows only an even address to be set.
Pa21
The area 1 allocation parameters are used for allocation-related

settings to enable data exchange between common memory area 1 and
the PMC R area.

Item Description
AREA1 DO/DI: Start address of an area in the PMC R area used for data
ALLOCATION exchange with common memory area 1.
Pa30 This parameter allows only an even address to be set.
AREA1 DO/DI: Start address of an area in common memory area 1 used for
ADDRESS data exchange with the PMC R area.
Pa31
AREA1 DI/DO: Size of data exchanged between common memory area 1 and
SIZE(Note 1) the PMC R area (Unit: Words).
When data exchange between common memory area 1 and
Pa32 the PMC is not performed, set 0 in this parameter.
NOTE
1 The unit of size set in this parameter is words. This
means that for an area used in the PMC R area, the
number of bytes as many as the size set in this
parameter multiplied by 2 is required.
- 72 -
The area 2 allocation parameters are used for allocation-related

settings to enable data exchange between common memory area 2 and
the PMC R area.

Item Description
AREA2 DO: Start address of an area in the PMC R area or D area used for
ALLOCATION DO data exchange with common memory area 2.
AREA2 DO: Size of DO data exchanged between common memory area 2
SIZE(Note 1) and the PMC R area or D area (Unit: Words).
When DO data exchange between common memory area 2
Pa41 and the PMC is not performed, set 0 in this parameter.
AREA2 DI: Start address of an area in the PMC R area or D area used for
ALLOCATION DI data exchange with common memory area 2.
When DI data exchange between common memory area 2
and the PMC is not performed, set -1 in this parameter, or
press soft key [DISABL].
AREA2 DI: Set an area in the PMC R area used to specify a node from
ALLOC PTR which data is to be read as DI data.
(Note 2) When DI data exchange between common memory area 2
and the PMC is not performed, set -1 in this parameter, or
press soft key [DISABL].
AREA2 DI: The user can dynamically switch between nodes from which
CHANGE FLG data is to be read as DI data.
(Note 2) Specify an area in the PMC R area used to specify switch
timing.
When dynamic switching is not performed for reading DI data,
Pa44 set -1 in this parameter, or press soft key [DISABL].
AREA2 DI: Start address of common memory area 2 to be statically
AREA2 ADDR allocated in the PMC area as DI data
(Note 2)
Pa45
AREA2 DI: Size of DI data statically exchanged between common
AREA2 SIZE memory area 2 and the PMC area (Unit: Words)
(Note 1, Note2)
Pa46
NOTE
1 The unit of size set in this parameter is words. This
means that for an area used in the PMC R area, the
number of bytes as many as the size set in this
parameter multiplied by 2 is required.
2 Parameters AREA2 ADDR and AREA2 SIZE can be
used to set a large area for data exchange between
common memory area 2 and PMC area
independently of node numbers.
When a value of 0 is set for AREA2 SIZE, no static
allocation is performed and dynamic DI data change
- 73 -
is performed for each node.

On the other hand, when a value other than 0 is set
for AREA2 SIZE, data starting at AREA2 ADDR in
common memory area 2 is expanded to an area in
the PMC area that is specified by ALLOCATION+4,
and dynamic DI data change cannot be performed.
In this case, ALLOC PTR and CHANGE FLG are
used only for node status information switching.
3 For reasons related to the specifications of the
FANUC FL-net board, set the sizes of common
memory area 1 and area 2 of the local node that are
allocated in the PMC area and the sizes of common
memory area 1 and area 2 of another node that are
allocated in the PMC area so that the total size of
them is 1024 words or less.
For example, when 1024 words of common memory
area 1 and area 2 of the local node are allocated in
the PMC area, DI data of another node cannot be
allocated in the PMC area to read it. Conversely,
when 1024-word DI data of another node is
allocated in the PMC area to read it, DO data of the
local node cannot be allocated in the PMC area. In
such a case, take a means such as dynamic change
of the allocated area so that the total size becomes
1024 words or less. For details, see Chapter II
DESCRIPTION Section 2.6, "Notes on Allocation in
the PMC Area."
4 Data in the PMC D area is also retained after the
power is turned off, then on again. For this reason,
be careful to use the PMC D area. Clear the PMC
D area to 0 using the user program immediately after
power-on as required.
- 74 -
The message allocation parameters are used to allocate a message

transmit interface area in the PMC R area.
Table 1-10 Message Allocation Parameters

Item Description
MESSAGE: Start address of an interface area in the PMC R area or D area
ADDRESS used when the message transmission client function is used.
MESSAGE: Size of the interface area above (Unit: Bytes).
SIZE When the message transmission client function is not used,
Pa51 set 0 in this parameter.
MESSAGE: Start address of an interface area in the PMC R area or D area
RECV MSG used for transparent message receive data.
MESSAGE: Size of the interface area above (Unit: Bytes).
SIZE When transparent message receive data is not accepted, set
Pa53 0 in this parameter.
- 75 -
Basic method of parameter input
The basic method of parameter input is described below.
Procedure
(1) Set the CNC mode to the MDI mode.

(2) Display the parameter setting screen of screen 1-2.
(3) With the cursor keys, move the cursor to a desired item.
(4) Enter a desired parameter value with the MDI keys.
(5) Execute the input of the parameter by pressing soft key [INPUT]
or function key INPUT .
Example of input
Setting 192.168.250.10 in IP ADDRESS

For the sample screen below, the 9.5" LCD is used.
(A) Move the cursor to IP ADDRESS.
- 76 -
(B) Enter the parameter 192.168.250.10 through the MDI keys.
(C) Execute the input of the parameter by pressing soft key [INPUT]
or function key INPUT .

This operation saves the parameter in nonvolatile memory of the
CNC.
- 77 -
1.2.2 Power Mate i-MODEL D/H
Procedure
When the CRT/MDI or FANUC touch panel is used as the LCD, set
parameters in the same way as for the Series 16i/18i/21i-A.
When the DPL/MDI Operation Package is used as the LCD, set
values for parameters Nos. 30000 and after.
For how to set parameters using the DPL/MDI Operation Package,
refer to "Power Mate i Operator’s Manual."
Basic parameters
30000 IP address (1)

[Data type] Byte
[Valid data range] 1 - 254
[Index number] Pa10
Set bits 0 to 7 of the IP address of the local node.

[Data type] Byte
[Index number] Pa10

[Data type] Byte
[Index number] Pa10

[Data type] Byte
[Index number] Pa10
- 78 -
30010 Node name: 1st character

30011 Node name: 2nd character
30012 Node name: 3rd character
30013 Node name: 4th character
[Data type] Byte
[Index number] Pa17
Set the equipment name of the local node one character for each
parameter in ASCII code.
30020 Start address of area 1 transmit data

[Data type] Word
[Index number] Pa11
30021 Area 1 transmit data size

[Data type] Word
[Index number] Pa12
30022 Start address of area 2 transmit data

[Data type] Word
[Index number] Pa13
30023 Area 2 transmit data size

[Data type] Word
[Index number] Pa14
30024 Token monitoring time

[Data type] Byte
[Unit of data] 1 msec
[Index number] Pa15
30025 Minimum allowable frame interval

[Data type] Byte
[Unit of data] 100 μsec
- 79 -

[Index number] Pa16
State monitoring parameters
30026 Local node informatino address

[Data type] Word
[Valid data range] 0 - (only an even address)
[Index number] Pa20
30027 Participating node information address

[Data type] Byte
[Index number] Pa21
30030 Allocation address (shared for DI/DO)

[Data type] Word
[Index number] Pa30
30031 Area 1 address (shared for DI/DO)

[Data type] Word
[Index number] Pa31
30032 Data size (shared for DI/DO)

[Data type] Word
[Index number] Pa32
30033 Allocation address (for DO)

[Data type] Word
[Index number] Pa40
30034 Data size (for DO)

[Data type] Word
[Index number] Pa41
30035 Allocation address (for DI)

[Data type] Word
[Index number] Pa42
- 80 -
30036 Area 2 data exchange condition allocation address

[Data type] Word
[Index number] Pa43
30037 Switch flag allocation address

[Data type] Word
[Index number] Pa44
30050 Area 2 static DI data exchange address

[Data type] Word
[Index number] Pa45
30051 Area 2 static DI data exchange size

[Data type] Word
[Index number] Pa46
30055 PMC area allocation address (for DO)

[Data type] Word
[Valid data range] 68(D) or 82(R)
[Index number] Pa40
30056 PMC area allocation address (for DI)

[Data type] Word
[Index number] Pa42
30040 Interface allocation address

[Data type] Word
[Index number] Pa50
30041 Interface allocation size

[Data type] Word
[Index number] Pa51
30042 Receive message allocation address

[Data type] Word
[Index number] Pa52
30043 Receive message allocation data aize

[Data type] Word
- 81 -
[Index number] Pa53
30060 Interface PMC area allocation address

[Data type] Word
[Index number] Pa50
30061 Receive message PMC area allocation address

[Data type] Word
[Index number] Pa52
Node selection parameter
30045 Node number (maintenance information display node setting)

[Data type] Byte
Set the number of a node on which maintenance information is to be
displayed.
- 82 -
B-63434EN/02 OPERATION 2.MAINTENANCE SCREEN
2 MAINTENANCE SCREEN
This chapter describes the screens used for maintenance of the FL-net
function with the Series 16i/18i/21i-A and with the Power Mate i.
- 83 -
2.MAINTENANCE SCREEN OPERATION B-63434EN/02
2.1 Participating Node Management Table
The FL-net participating node monitor screen allows the user to

reference the parameters of each node participating in the FL-net
network.
Procedure
(1) Press function key SYSTEM , then press soft key [PMC] to
switch to the PMC screen.

order. Then, screen 1-1 appears.
(3) On screen 1-1, press soft key [NODE]. Then, screen 2-1 shown
below appears.
Screen 2-1 FL-net Participating Node Monitor Screen (10.4" LCD)
(4) In the upper part of the screen, a list of nodes participating in the
network can be monitored. A node participating in the network
has its node number marked with O. (An asterisk (*) is
indicated for the local node.) On the screen above, nodes 10
and nodes 85 are participating in the network, and the local node
is node 10.
(5) When a soft key displayed on the screen is pressed, the
corresponding operation is performed as follows:
1) [NODE]: Displays the parameters of a specified node.
2) [P.NODE]: Displays the parameters of the node
immediately before the currently displayed
node.
- 84 -
3) [N.NODE]: Displays the parameters of the node

immediately after the currently displayed
node.
(6) When this screen is displayed, the information about the local
node is first displayed.
(7) When the 9.5" LCD is used, all information cannot be displayed
on one screen. So, two screens are used as shown below. One
screen is used to monitor participating nodes, and the other is
used to monitor the parameters of each node.
Screen 2-2 FL-net Participating Node Monitor Screen (9.5" LCD)
- 85 -
Table 2-1 explains the items displayed on the screen.
Table 2-1
Participating Node Management Table
Item Description
NODE NO. Node number of the node about which information is
currently displayed
AREA1 ADDR Start address of the node in common memory area 1
AREA1 SIZE Data size of the node in common memory area 1
AREA2 ADDR Start address of the node in common memory area 2
AREA2 SIZE Data size of the node in common memory area 2
TOKEN WATCH Token monitoring time of the node (in ms)
MIN FRAME Allowable minimum frame interval (in 100 µs)
ULS State of the upper layer of the node
LKS State of the FA link of the node
NODE NAME Node name of the node.
When the node is not the local node, this item can be
displayed only if the node participates in the network after
the participation of the local node.
Lowercase letters entered are converted to uppercase
letters for display.
VENDOR NAME Vendor code of the node.
MAKER TYPE Manufacturer Model type of the node.
RCT Allowable refresh cycle time of the node (in ms)
STATUS Local node status.
This item is displayed only when the node is the local
node.
PRTCL VER. Protocol version.
This item is displayed only when the node is the local
node. At present, however, this item is fixed at 80H.
- 86 -
2.2 Network Management Table
The FL-net network management table screen allows the user to

reference the parameters of each node in the FL-net network
management table.
Procedure

(3) On screen 1-1, press soft key [NETWRK]. Then, screen 2-3
shown below appears.
Screen 2-3 FL-net Network Management Table Screen (10.4" LCD)
- 87 -
Table 2-2 Network Management Table

Item Description
TOKEN NODE Node number of the node that currently holds the token
MIN FRAME Maximum value of the allowable minimum frame intervals
of all nodes participating in the network (in 100 µs)
RCT Allowable refresh cycle time of the local node (in ms)
RCM Refresh cycle measurement time of the local node
(in ms)
MAX RCM Maximum refresh cycle measurement time of the local
node (in ms)
MIN RCM Minimum refresh cycle measurement time of the local
node (in ms)
- 88 -
2.3 Log Information Management Table
The FL-net log information management table screen allows the user
to reference the network log information of the local node.
Procedure

(3) On screen 1-1, press soft key [LOG]. Then, screen 2-4 shown
below appears.
Screen 2-4 FL-net Log Information Management Table Screen

(10.4" LCD)
(4) Pressing soft key [CLEAR] clears log information.
- 89 -
Table 2-3 Log Information Management Table

Item Description
TOTAL SEND COUNT SEND Number of transmitted frames
SEND ERROR COUNT SERR Number of transmission errors
TOTAL RECEIVE COUNT RECV Number of received frames
RECEIVE ERROR COUNT RERR Number of receive errors.
The reception of a packet other than
FL-net packets is also counted as a
receive error.
CYCLIC DATA ERROR RCYC Number of errors in cyclic
COUNT transmission
MESSAGE RETRY COUNT RMSG Number of retrials for message
transmission
MESSAGE RETRY OVER MOVR Number of operations where retrials
COUNT for message transmission
exceeded an allowable number of
retrials
MESSAGE RECEIVE MRCV Number of receive message errors
ERROR COUNT
ACK ERROR COUNT ACKE Number of ACK errors
DUPLICATED TOKEN TDUP Number of duplicate tokens
COUNT detected
DESTROYED TOKEN TDES Number of token discard operations
COUNT
TOKEN COUNT TKNC Number of token reissue operations
FRAME WAIT COUNT FRMW Number of frame wait states
entered because there are no other
nodes in the network
ENTRY COUNT ENTR Number of network participation
operations performed by the local
node
OWN DISCONNECT DISC Number of disconnections of the
COUNT local node due to token hold time-
out
SKIP DISCONNECT SKIP Number of disconnections of the
COUNT local node because the token is not
passed to the local node
OTHER NODE OTHE Number of recognitions that other
DISCONNECT COUNT nodes are disconnected
- 90 -
When the 9.5" LCD is used, the name of each item is limited to four
characters as shown below.
Screen 2-5 FL-net Log Information Management Table Screen

(9.5" LCD)
- 91 -
2.4 Power Mate i-MODEL D/H
Procedure
When the CRT/MDI or FANUC touch panel is used as the LCD,
reference maintenance information in the same way as for the Series
16i/18i/21i-A.
When the DPL/MDI Operation Package is used as the LCD,
maintenance information can be referenced with diagnosis numbers
8000 and after.
For how to display diagnostic data using the DPL/MDI Operation
Package, refer to "Power Mate i Operator’s Manual."
The diagnosis numbers and corresponding reference items are listed
below.
Participating node management table

The number of the node on which maintenance information is
displayed is set using parameter No. 30045.
8000 AREA1 ADDR

[Data type] Word
Start address of common memory area 1 of the node
8001 AREA1 SIZE

[Data type] Word
Size of common memory area 1 of the node
8002 AREA2 ADDR

[Data type] Word
Start address of common memory area 2 of the node
8003 AREA2 SIZE

[Data type] Word
Size of common memory area 2 of the node
8004 LKS
[Data type] Byte
State of the FA link of the node
8005 ULS
[Data type] Word
State of the upper layer of the node
8006 TOKEN WATCH

[Data type] Byte
Token monitoring time of the node
- 92 -
8007 MIN FRAME

[Data type] Byte
Minimum allowable frame time interval of the node
8008 RCT
[Data type] Word
Allowable refresh cycle time of the node
8009 NODE NAME

[Data type] Byte (10-byte data)
Node name of the node (Note 2)
8010 VENDOR NAME

Vendor name of the node (Note 2)
8011 MAKER TYPE

Manufacturer type of the node (Note 2)
NOTE
1 If the local node number is set for parameter No.
30045, the above information is not displayed
correctly. For information on the local node,
reference diagnosis numbers 8020 to 8033 shown
below.
2 The information can be displayed only when the target
node participates in the network following the local
Local node management table
8020 NODE NO.

[Data type] Byte
Node number of the local node
8021 NODE NAME

Node name of the local node
8022 VENDOR NAME

Vendor name of the local node
8023 MAKER TYPE

- 93 -
Manufacturer type of the local node
8024 STATUS
[Data type] Byte
Status of the local node
8025 LKS
[Data type] Byte
State of the FA link of the local node
8026 ULS
[Data type] Word
State of the upper layer of the local node
8027 AREA1 ADDR

[Data type] Word
Start address of common memory area 1 of the local node
8028 AREA1 SIZE

[Data type] Word
Size of common memory area 1 of the local node
8029 AREA2 ADDR

[Data type] Word
Start address of common memory area 2 of the local node
8030 AREA2 SIZE

[Data type] Word
Size of common memory area 2 of the local node
8031 TOKEN WATCH

[Data type] Byte
Token monitoring time of the local node
8032 MIN FRAME

[Data type] Byte
Minimum allowable frame time interval of the local node
8033 PRTCL VER.

[Data type] Byte
Protocol version
Network management table
8040 TOKEN NODE

[Data type] Byte
- 94 -
Node number of the node that currently holds the token
8041 MIN FRAME

[Data type] Byte
Maximum value of the minimum allowable frame time intervals of all
nodes participating in the network
8042 RCT
[Data type] Word
Allowable refresh cycle time of the local node
8043 RCM
[Data type] Word
Refresh cycle measurement time of the local node
8044 MAX RCM

[Data type] Word
Maximum refresh cycle measurement time of the local node
8045 MIN RCM

[Data type] Word
Minimum refresh cycle measurement time of the local node
Log data
8050 TOTAL SEND COUNT

[Data type] Double word
Total number of transmitted frames
8051 SEND ERROR COUNT

Number of transmission errors
8052 TOTAL RECEIVE COUNT

Total number of received frames
8053 RECEIVE ERROR COUNT

Number of receive errors
The reception of a packet other than an FL-net packet is also counted
as a receive error.
- 95 -
8054 CYCLIC DATA ERROR COUNT

Number of errors in cyclic transmission
8055 MESSAGE RETRY COUNT

Number of retrials for message transmission
8056 MESSAGE RETRY OVER COUNT

Number of operations where retrials for message transmission
exceeded the maximum number
8057 MESSAGE RECEIVE ERROR COUNT

Number of receive message errors
8058 ACK ERROR COUNT

Number of ACK data errors
8059 DUPLICATED TOKEN COUNT

Number of duplicate tokens detected
8060 DESTROYED TOKEN COUNT

Number of token discard operations
8061 TOKEN COUNT

Number of token reissue operations
8062 FRAME WAIT COUNT

Number of frame wait states entered because there are no other nodes
in the network
8063 ENTRY COUNT

Number of network participation operations performed by the local
node
8064 OWN DISCONNECT COUNT

Number of disconnections of the local node from the network due to a
token hold time-out
8065 SKIP DISCONNECT COUNT
- 96 -

Number of disconnections of the local node from the network because
the token is not passed to the local node
8066 OTHER NODE DISCONNECT COUNT

Number of recognitions that other nodes are disconnected from the
network
- 97 -
3.EXAMPLE OF CONNECTION OPERATION B-63434EN/02
3 EXAMPLE OF CONNECTION
This chapter describes an example of connection using the FL-net
function with the Series 16i/18i/21i-A with the Power Mate i.
- 98 -
B-63434EN/02 OPERATION 3.EXAMPLE OF CONNECTION
3.1 Example of Configuration
Using the example of configuration shown below, this section

describes the setting of each parameter.
Ethernet
Series 16i -A Series 18i -A Power Mate i -D

Node No.10 Node No.20 Node No.30
Fig. 3-1 Example of FL-net Configuration
The parameter settings and PMC area allocation state when 4-word
DO data in common memory area 1 and 64-word DO data in common
memory area 2 are exchanged at all of the three nodes are described
below.
The common memory of each node is allocated as shown below.
Common memory area Common memory area

1 2
0x0000 0x0000 Node No. 10
0x0010 Node No. 10
0x0014 Node No. 20 0x0040
0x0018 Node No. 30 0x0050 Node No. 20
0x001c
0x0090
0x00a0 Node No. 30
0x00d0
0x01ff
0x1fff
- 99 -
3.2 Example of Parameter Settings
Assume that the address map of the PMC R area of each node is as
shown below. Then, the parameters of each node are set as indicated
in Table 3-1 through Table 3-4.
PMC R area
R0000
R0100 Node No. 10

R0108 Common memory area 1
Node No. 20
R0116
data
Node No. 30
R0124 Local node information
R0128 Participating node list
R0160
Common memory area 2 DO data
R0288
R0299 Switch flag
R0300 Information on
Common memory area 2 other nodes
R0304 DI data Real data
R0432
R0450 Message transmission Interface

client
R0470 Read/write buffer
R1494
- 100 -
Table 3-1 Parameters of Node No. 10

Item Setting Item Setting
IP ADDRESS 192.168.250.10 AREA2 DI: -
NODE NAME NODE#10 ALLOCATION R0300
AREA1 ADDR 16 ALLOC PTR D0000
AREA1 SIZE 4 CHANGE FLG R0299
AREA2 ADDR 0 AREA2 ADDR 0
AREA2 SIZE 64 AREA2 SIZE 0
TOKEN WATCH 50 MESSAGE: -
MIN FRAME 10 ADDRESS R0450
OWN STATUS R0124 SIZE 20
ENTRY NODE R0128 RECV MSG R0000
AREA1 DO/DI: - SIZE 0
ALLOCATION R0100
ADDRESS 16
SIZE 12 D0000 of PMC 20
AREA2 DO: - D0002 of PMC 0
ALLOCATION R0160 D0004 of PMC 64
Table 3-2 Parameters of Node No. 20

ALLOCATION R0100
ADDRESS 16
- 101 -
Table 3-3 Parameters of Node No. 30 (CRT/MDI)

ALLOCATION R0100
ADDRESS 16
Table 3-4 Parameters of Node No. 30 (DPL/MDI)

No.30000 30 No.30030 100
No.30001 250 No.30031 16
No.30002 168 No.30032 12
No.30003 192 No.30033 160
No.30010 78 No.30034 64
No.30011 79 No.30035 300
No.30012 68 No.30036 0
No.30013 69 No.30037 299
No.30014 35 No.30040 450
No.30015 51 No.30041 20
No.30016 48 No.30042 0
No.30017 0 No.30043 0
No.30018 0 No.30050 0
No.30019 0 No.30051 0
No.30020 24 No.30055 82
No.30021 4 No.30056 82
No.30022 160 No.30060 82
No.30023 64 No.30061 82
No.30024 50 D0000 of PMC 10
No.30025 10 D0002 of PMC 0
No.30026 124 D0004 of PMC 64
No.30027 128 D0006 of PMC 0
- 102 -
3.3 Image of Data Exchange
When data exchange is performed with the examples of configuration

and parameter settings described earlier, the illustration below shows
how the data of each node is viewed in the PMC R area of each node.
Node No. 10 Node No. 20 Node No. 30

R0000 R0000 R0000
R0100 R0100 R0100

#10 #10 #10
R0108 R0108 R0108
Area 1 #20 Area 1 #20 Area 1 #20
R0116 R0116 R0116
#30 #30 #30
R0160 R0160 R0160

Area 2 DO Area 2 DO Area 2 DO
R0304 R0304 R0304

Area 2 DI Area 2 DI Area 2 DI
Moreover, a message can be transmitted using a PMC area starting at

R0450.
- 103 -
IV. CONNECTION
B-63434EN/02 CONNECTION 1.INSTALLATION
1 INSTALLATION
This chapter provides information required for installation of the FL-
net board.
- 107 -
1.INSTALLATION CONNECTION B-63434EN/02
1.1 Specifications
The specifications of the FL-net board are described below.
For the stand-alone type Series 16i/18i/21i-MODEL A

Name FL-net board
Ordering code A02B-0265-J272
Board drawing A20B-8100-0530
number
Applicable FANUC 16i/160i-TA (stand-alone type)
model FANUC 16i/160i-MA (stand-alone type)
FANUC 18i/180i-TA (stand-alone type)
FANUC 18i/180i-MA (stand-alone type)
FANUC 21i/210i-TA (stand-alone type)
FANUC 21i/210i-MA (stand-alone type)
Heat dissipation 7 (W)(Note 1)
For the Power Mate i-MODEL D/H

Name FL-net board
Ordering code A02B-0259-J272
Board drawing A20B-8100-0530
number
Applicable FANUC Power Mate i-MODEL D/H
model
Heat dissipation 7 (W)(Note 1)
NOTE
1 For the heat dissipation of the main CNC unit and
other optional units, refer to the connection manual
of the CNC.
2 When using the FL-net board, observe the
installation condition (environment condition within
the cabinet) of the CNC control unit where the FL-net
board is mounted.
- 108 -
B-63434EN/02 CONNECTION 1.INSTALLATION
1.2 Installation
This section describes information about the installation of the FL-net

board.
The FL-net board can be installed in any mini-slot of a one-slot or

three-slot basic unit.
CD38N
- 109 -
2.CONNECTION OF THE COMMUNICATION FUNCTION CONNECTION B-63434EN/02
2 CONNECTION OF THE
COMMUNICATION FUNCTION
This chapter provides information required for Ethernet connection of
the FL-net board.
CAUTION
1 Before attaching or detaching a cable to the FL-net
board, turn off the power to the CNC, and confirm
that the power is off.
2 For network building and the condition for using
devices other than the FL-net board (such as media
converters, hubs, transceivers, and cables), contact
the supplier of each device. For network
installation, care must be taken to protect the
network from a noise source. Separate the network
wiring sufficiently away from a noise source such as
a power line and motor from an electrical viewpoint,
and ground each device as required. If grounding is
insufficient because of high impedance, a
communication error may occur. Before going into
actual operation after equipment installation, check
the operation by conducting a communication test.
FANUC cannot take responsibility for network trouble
arising from a device other than the FL-net board.
- 110 -
B-63434EN/02 CONNECTION 2.CONNECTION OF THE COMMUNICATION FUNCTION
2.1 Connection to Ethernet
The FL-net board has a 10BASE-T interface. For connection to a

10BASE5 system, a media converter or hub (concentrator) is used.
A typical example of connection is shown below.
Transceiver cable
Hub
(concentrator)
・
・
・
Twisted pair cable
CNC
Transceiver
FL-net board
10BASE5
trunk cable
Max. 100m
Some devices (such as hubs and transceivers) used to build a network

do not have a dust-proof structure. Using such devices in an
atmosphere containing dust or oil mist can cause a communication
error or failure. Be sure to house such devices in a dust-proof
cabinet.
- 111 -
2.2 Routing of the Ethernet Cable
The Ethernet cable can be routed only from the front of the control
unit. For connector location information, see the outside drawing of
each board.
Radius of 70 mm or more
10BASE-T
Ethernet cable
Clamp
Ground plate
The Ethernet cable needs to be secured with a clamp so that no

tension is applied to the connector (RJ-45) installed at the end of the
cable even if the cable is pulled. This clamping also serves as the
grounding of the cable shield.
- 112 -
2.3 Pin Allocation of the 10BASE-T Connector (CD38N)
CD38N
Pin No. Signal Meaning
1 TX+ Transmission +
2 TX- Transmission -
3 RX+ Reception +
4 Not used
5 Not used
6 RX- Reception -
7 Not used
8 Not used
- 113 -
2.4 Twisted Pair Cable Specifications
2.4.1 Cable connection
Referring to the operator’s manual of a device used, select an

appropriate cable. An example of straight cable connection between
the FL-net board 10BASE-T interface CD38N and a hub (or media
converter) is given below.
FL-net board Media converter

CD38N or hub
1 TX+ RJ-45 1 TX+

2 TX- modular connector 2 TX-
3 RX+ 3 RX+
4 4
5 5
6 RX- 6 RX-
7 7
8 MAX.100m
8
TX+ (1) (1) TX+

TX- (2) (2) TX-
RX+ (3) (3) RX+
RX- (6) (6) RX-
Shield
- The cable must not be longer than 100 m. Do not extend the
cable unnecessarily.
- 114 -
An example of cross cable connection between the FL-net board

10BASE-T interface CD38N and a mediate converter (or hub) is
given below.
FL-net board Media converter

CD38N or hub
1 TX+ RJ-45 1 TX+

2 TX- modular connector 2 TX-
3 RX+ 3 RX+
4 4
5 5
6 RX- 6 RX-
7 7
8 MAX.100m
8
TX+ (1) (3) TX+

TX- (2) (6) TX-
RX+ (3) (1) RX+
RX- (6) (2) RX-
Shield
- The cable must not be longer than 100 m. Do not extend the
cable unnecessarily.
NOTE
A straight cable is usually used for connection
between a communication device and hub. The
cable required for connection may differ depending
on the manufacturer of the hub or media converter,
however. Check whether a straight or cross cable
is required, then prepare a correct cable.
When connection is correct, the LED marked with
"LIL" on the FL-net board lights up.
- 115 -
2.4.2 Cable wire
As twisted pair cables for 10BASE-T, unshielded cables (UTP cables)

are available on the market. For improved protection against noise
in an FA environment, however, use a common shielded category-5
twisted pair cable (STP cable).
Recommended cables (For standard)

Manufacturer name Specification Remarks
The Furukawa Electric Co., Ltd. DTS5087C-4P Twisted wire
Nissei Electric Co., Ltd. F-4PFWMF Solid wire
Contact point
Manufacturer name Contact point
Sales Division, the 2-6-1 Marunouchi Chiyoda Ward, Tokyo, 100-8233
Furukawa Electric TEL: 03-3286-3126 FAX: 03-3286-3979
Co., Ltd.
Remarks
Tamachi Office, MU Building 3F, 1-9-1 Minaminaruse, Machida City,
Nissei Electric Co., Tokyo 194-0045
Ltd. TEL: 0427-29-2531 FAX: 0427-29-3375
Contact point IWATANI International Corporation
for overseas Tokyo Head Office
sales 21-8 NISHI-SHINBASHI 3-CHOME, MINATO-KU,
TOKYO, 105-8458, JAPAN
TEL：03-5405-5810 FAX：03-5405-5666
Telex：2524256 IWATYO J
Remarks A processed cable with the both terminal connector
is provided.
NOTE
The recommended standard cables cannot be used
with movable parts.
Recommended cable (For movable parts)

Oki Electric Cable Co., AWG26 4P TPMC-C5-F(SB) FANUC-specific
Ltd. cable

#1(-A&%*%&#%)-:
-A&%*%&&#1( )&)&)+;
+#/%.=$1+C 55,,,, !
#=*#&=++C @%(&+%&
#1(
)'
Nagano Sales Office TEL: ,55!4
A&%*%&#%)-
・(&+%&&0#+#&+%-%&-C
)*)+$)6!5
&#.)+%-#'!
)++#-)-+(#')#=#%)A+*)+$#&0
'%-#&)00=1$=-1!,$)+-0)++
・+=&=+C
)$$)-0%('&#1(:1+#%''-0%('; +#%
/%+A+)?%''
- 116 -
0&)'=&)+%-5##('&)AA+-+#''/%+
0-0#00%&@--%-,$$ 0)=-%''%#$+%-
5±,$$
・(#$+-%-#&C ! 9
・ %(+-%-#&C 3#-')0
-#'#+'
:D=%?#( ) 0 &)?%)#( )%(+-%-# (&+%&
&#1(-;
・(2%.+-%-#&C $%((%)%$-)+$)+/%0!,$$)*
#1'+#'%=-:-0#A*(2%.-;
・-"()C ,5 :,℃6,969;
); (/#"- =- &)&)+

:,;
$#=*#&=+'1"7%+)-(&+%&*)+0%-&#1(

#1(#--$1("
@% (&+%&
#1(
) ' #(-) -=AA(%- &#1(
#--$1(%- =-%. &)&)+
:,;
$#=*#&=+' 1" 7%+)- (&+%& #@ #++#.$-
'%+&(" /%0 0 $#=*#&=++ *)+ 0 -A&%*%&#%)-
:(.0 )=.)%. %-A&%) A#&@%. #' )0+-; #'
A=+&0#-&#1(#--$1(%-

)#&A)%C @%(&+%&
#1(
)'
#(- &)#& A)%; #.#) #(- **%&
TEL: ,55!4
- 117 -
2.4.3 Connector Specifications
As a connector used with a twisted pair cable for Ethernet, an 8-bit

modular connector called RJ-45 is used. Use the following
connector or equivalent:
Specification Manufacturer Remarks

For solid wire 5-569530-3 AMP Japan, Ltd.
For solid wire MS8-RSZT-EMC SK KOHKI Co., Special tool
Ltd. required
For twisted wire 5-569552-3 AMP Japan, Ltd.
For twisted wire TM11AP-88P Hirose Electric Co., Special tool
Ltd. required
For movable parts Specification Manufacturer Remarks

For cable AWG26
:,; Hirose Electric (Note)
4P TPMC-C5-F(SB) Co., Ltd.
NOTE

:,;

)&)+:$#=*#&=++-#'#+'A#+;
+#/%.=$1+C 5,,,,E
#=*#&=++C 7%+)-(&+%&
)'
#=*#&=++&##().=$1+C
:,;

)*)+$-)6!5&#.)+%-#'!
)+ 0)/ ) #--$1( 0 &)&)+ #' &#1( &)#&
7%+)-(&+%&
:7%+)- (&+%& &0%&#( ')&=$ F
:,;

)&%) +)&'=+ A&%*%&#%)-F :&0%&#(
-A&%*%&#%))．5;%-#?#%(#1(;
- 118 -
2.4.4 Hub
Recommended hub
Contec Co., Ltd. RT-1008H 10BASE-T
Eight ports
This hub is not for FA. Use the hub in a dust-proof cabinet.
Contact points
Manufacturer name Contact point
Contec Co., Ltd.
East Branch Tachibana Annex Building, 2-25-14 Kameido,
Koto Ward, Tokyo, 136-0071
TEL: 03-5628-0211 (pilot number)
FAX: 03-5628-0210
Central Branch Orchid Building, 2-38-2 Meieki, Nakamura Ward,
Nagoya City, 450-0002
FAX: 052-564-7826
West Branch 3-9-31 Himesato, Nishiyodogawa Ward, Osaka
City, 555-0025
FAX: 06-6478-1031
Remarks http://www.contec.co.jp/
- 119 -
2.5 Noise Protection
2.5.1 Signal line separation
The wiring of Ethernet cables belongs to group C. For the method

of separation from group A wiring and group B wiring, refer to
"Connection Manual: Hardware (B-63003EN)" of each CNC.
2.5.2 Cable clamping and shield processing
Clamp those cables that are run into the CNC and require shield
processing, as shown below. Process the shield of a twisted pair
cable for Ethernet in the same way. This clamp processing secures a
cable, and also processes the shield of the cable. Be sure to perform
this clamp processing because it is key to stable operation of the
system.
As shown below, peel off a part of the outer sheath to expose the
shield, then press the exposed portion of the shield against the ground
plate with a clamp. The machine tool builder is to prepare a ground
plate and install it as shown below.
+)='A(#

#1(

#1(&(#$A
+)='A(#
0%('

#1(-0#0
- 120 -
Prepare the following ground plate:
)=%.-&+/0)(
+)='+$%#(
:*)+.+)='%.;

(#$A$)=%.0)(
As a ground plate, use an iron plate as thick as 2 mm or more, and

plate it with nickel.
$$ +)='A(#
$$
,$$
- 121 -
!!$$$#2
$$
5$$
$$
Outline Drawing of the Clamp
Ordering code of the clamp: A02B-0124-K001 (8 clamps)
- 122 -
2.5.3 Network installation
Even when the grounding condition on the machine side is satisfied,

noise generated by a machine may induce a communication error on
the communication line, depending on the installation condition and
environment of the machine. To prevent such trouble, the
machine(s) should be separated and insulated from the Ethernet trunk
cable and personal computer. Examples of connections are given
below.
+-)#(&)$A=+
:); ,3!
+=@&#1(
:); 4
!<<10-
+-)#(&)$A=+6 73 5
+=@-%'
1'# .'(1!<( (#.
0"+B &#1( &#1(
''#.
('5.!0!#!. #&0% #&0%

#&0%
:); :); :);
Large network
+-)#(&)$A=+
4
!<<10-
73 5
:);
+-)#(&)$A=+6
+=@-%'
1'# .'(1!<( (#. &#1(
0"+B
''#.
('5.!0!#!.

#&0%
:);
Small network
- 123 -
NOTE
1 Ensure that the ground system of the personal
computer/trunk side is separated from the ground
system of the machine system. If ground system
separation is impossible because only one
grounding point is available, run the personal
computer/trunk side ground wire and the machine
side ground wire separately to the grounding point.
(See the figure below.) The ground resistance must
be 100 ohms or less (glass-2 grounding). The
ground wire must not be thinner than the AC power
2
line, and must be at least 5.5 mm in diameter.
2 Even when the insulation/separation method based
on 10BASE-T is used as described above, noise can
impede normal communication. When a network is
used in such a very poor environment, consider the
use of 10BASE-FLAG (optical fiber media) to
completely separate the machine side from the
personal computer side.

0%(' +=@&#1(
73
+)='/%+)*0A+-)#(
&)$A=+6+=@-%'
#&0%
+)='/%+)*0$#&0%-%'
+)='%.A)%
When only one grounding point is available
- 124 -
V. MAINTENANCE
B-63434EN/02 MAINTENANCE 1.HARDWARE
1 HARDWARE
This chapter provides hardware information required for the
maintenance of the FL-net board.
- 127 -
1.HARDWARE MAINTENANCE B-63434EN/02
1.1 Layout of Components
Custom Custom
LSI LSI
MPU
TM1
CD38N
Name PCB drawing number Remarks

FL-net board A20B-8100-0530
- 128 -
1.2 LED Indications and Meanings
The FL-net board has four green LEDs (ROS, RES, LNK, and POK)
and one red LED (HER) for state indication, and two green LEDs
(COM and LIL) and one LED (COL) for communication status
indication. The locations and meanings of the LEDs are described
below. In the description below, the following marks are used to
represent the display states of each LED:
: Turned on : Turned off

✩: Blinking : Don’t care
CD38N
5(COM)(GREEN)
B(HER)(RED)
4(POK)(GREEN)
3(LNK)(GREEN)
1(ROS)(GREEN)
2(RES)(GREEN)
(COL)(RED)
(LIL)(GREEN)
Note) The face plate is represented by dotted lines.
LED indication transition at power-on (ROS, RES, LNK, POK)
No. LED indication Ethernet board state

4 3 2 1
POK LNK RES ROS
1 Power off
2 Initial state immediately after power-on
3 Completion of MPU initialization
4 Completion of downloading of firmware
5 Transfer of control to the OS
6 OS PHASE1
7 OS PHASE2
8 OS PHASE3
9 OS PHASE4
10 ✩ Completion of activation
When the board is activated normally, the state of No. 10 is set.
This state continues until an error occurs.
- 129 -
LED indication during normal operation

No. LED indication Communication status
1 ROS ☆ Blinks at 1-second intervals when the
communication software on the FL-net board
operates normally.
2 RES □ Normally, off
3 LNK ■ Turned on when the node participates in the FL-
net network
4 POK ■ Turned on when all FL-net parameters are valid.
LED indication for communication status
No. LED indication Communication status

1 COM Turned on when data is transmitted or received
2 LIL Turned on when the connection with the hub is
normal
3 COL Turned on when a data collision occurs
NOTE
COL: The FL-net manages the token-based
transmission right so that no collision occurs. If
this LED is turned on frequently, a
communication error has occurred due to noise,
or an Ethernet compliant product other than the
FL-net is connected.
- 130 -
LED indication when an error occurs (ROS, RES, LNK, POK)
The LEDs repeat the indications of the LONG pattern and SHORT
pattern. In this case, the LONG pattern is turned on for a longer
time, and the SHORT pattern is turned on for a shorter time.
LED indication
No. LONG SHORT Board state
43 21 43 21
1 Reset exception
2 General machine check exception
3 Data Storage
4 Instruction Storage
5 Alignment
6 Program
7 Floating Point Unavailable
8 Decrementer
9 Trace
10 Floating Point Assist
11 Implementation Dependent Software Emulation
12 Implementation Dependent Instruction TLB Miss
13 Implementation Dependent Data TLB Miss
14 Implementation Dependent Instruction TLB Error
15 Implementation Dependent Data TLB Error
16 Implementation Dependent Data Breakpoint
17 Implementation Dependent Instruction Breakpoint
18 Implementation Dependent Peripheral Breakpoint
19 Implementation Dependent Non Maskable Development
20 DRAM Parity Alarm
21 Other NMI
22 Invalid interrupt
Note) If any of these errors occurs, contact FANUC.
LED indication when an error occurs (HER)
No. LED indication Board state

1 HER A parity error occurred in the main memory.
- 131 -
1.3 Setting Pin
The FL-net board has a setting pin (TM1) installed. The B side is
connected with a jumper plug (factory setting). If the plug is
removed, or the setting is changed, the FL-net board does not operate
normally.
- 132 -
B-63434EN/02 INDEX
INDEX

(()&#%))*#(%-)*A#+%&%A#%.)'-
=&%)-,
(()&#%))*()&#()'-#!

5

3"1()&@+#'4
3"1()&@/+%

3"%-)*
"&(%&##4
3"%-)*--#.##5 7 ,
7=14

#1(&(#$A%.#'-0%('A+)&--%.4
#1(&)&%) $#.)*##2&0#.
#1(/%+4, -#((#%)
)$$)$)+"+#
"&(%&+#-$%--%)
)$$)$)+"+#
"&(%&+#-$%--%)

7

#")=)*
)$A)-,
)&%))0+! '%&#%)-#'#%.-,
)&)+A&%*%&#%)-4 %-)*--#.+#-$%--%)+?%&-,

).*)+$#%)##.$#1(5

##
)&=++&",

!
'###(()&#%)5 4
'###(()&#%) --#.+#-$%--%)
(%=&%)4
"#$%&'###(()&#%))*&)$$)$$)+"#+# --#.+#-$%--%)+?+=&%)
5

/)+@%-#((#%)4
++)+&)'(%- /)+@##.$#1(5
2#$A()*
)*%.=+#%) )'#)%)+%.!
8

)'-%*)+$#%)
2#$A()*#+#$+%.- )%-+)&%)4
%
INDEX B-63434EN/02
)-)(()&#%)%0
+# +?+=&%))*+#-$%%.#--#./%0

)*%+$#%)

%.)*#+#$+-
?+?%/ , %.%,5
%.#((%-A#+#%)4

A&%*%&#%)-
4 #%&'###(()&#%))*&)$$)$$)+"#+#
#+%&%A#%.)'##.$#1(! 4
%(()&#%))*0,3
)&)+:
;

)/+#i 67! %$%.)*-/%&0%.1/&)'%%)-)'##
)/+#i 6755 2&0#./%0&)$$)$$)+"#+#
+)&'=+*)+--#.+#-$%--%) A+#%) +#-A#+$--#.+&A%)
+)&'=+*)+)A+#%.0$--#.+#-$%--%) +#-A#+$--#.+#-$%--%)4
&(%*=&%) +#-A#+--#.+#-$%--%)=&%)4
+)&'=+*)+)A+#%.0+#-A#+$--#. /%-'#%+
#1(A&%*%&#%)-
+#-$%--%)*=&%)

+)&'=+)*0--#.+#-$%--%)=&%)
9%+=#(#''+---A#&#(()&#%)!

&A%))*#$--#./%0&)*%+$#%)
-A)-$--#.+#-$%--%) 0#-0
)=%.)*00+
#1(5 )+'1()&@+#'
)+'1()&@/+%!

+%-5i6i6i
%
· No part of this manual may be
reproduced in any form.
· All specifications and designs

are subject to change without
notice.

FANUC FL-Net Board Operators Manual GFZ-63434EN02 CNC Manual

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

FANUC FL-Net Board Operators Manual GFZ-63434EN02 CNC Manual

Uploaded by

Copyright:

Available Formats

GE Fanuc Automation

Computer Numerical Control Products

GFZ-63434EN/02 November 2000

GE Fanuc Automation makes no representation or warranty, expressed, implied, or statutory

©Copyright 2000 GE Fanuc Automation North America, Inc.

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

2. GENERAL WARNINGS AND NOTES--------------------------------------------------s-3

1 DEFINITION OF WARNING, CAUTION,

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

2 GENERAL WARNINGS AND NOTES

1. Before operating the machine, thoroughly check the entered data.

       

      

  

#%& '###(()&#%))*&)$$)$$)+"#+#,

 )'-%*)+$#%) 

     !

  

      5!

   

   ,

 7   

  

About this manual

Manuals related to Series 16i/18i-TA/MA

Manuals related to Series 21i-TA/MA

Manuals related to FANUC Power Mate i-MODEL D/H

1.1 What Is the FL-net?

Features of the FL-net

Multi-vendor environment using an open network

Upper LAN Ethernet (TCP/IP, UDP)

Devices Sensor actuator

1 2 248 249 250 254

 !"#$%&'(!)   ! $*+ #

Two communication functions available according to the application

0'1.'# (!.!!. 0'1.' # (!.!!. 2 !!(3

(Transmission) (Reception) (Reception) (Reception)

(Reception) (Transmission) (Reception) (Reception)

(Reception) (Reception) (Reception) (Transmission)

(Reception) (Reception) (Transmission) (Reception)

  

  

   

1.2 FANUC FL-net Functions

The FL-net common memory contains two areas: an 8K-bit (= 0.5K-

For details of message transmission, see Chapter 3, "Message

2.1 Common Memory Area 1 Cyclic Transmission

Set the following parameters beforehand:

If an allocated area includes a mixture of DI and DO areas as shown

2.2 Common Memory Area 2 Cyclic Transmission

When the data of common memory area 2 is exchanged, DI areas

2.2.1 DO data allocation

Set the following parameters beforehand:

Organization of area 2 data exchange condition allocation:

2.2.2 DI data allocation

2.2.2.1 Dynamic DI data allocation of common memory area 2

Set the following parameters beforehand:

Organization of area 2 data exchange condition allocation:

2.2.2.2 Static DI data allocation of common memory area 2

Set the following parameters beforehand:

Organization of area 2 data exchange condition allocation:

2.2.2.3 Nodes information

FA link layer state:

Upper layer state:

#%&'###(()&#%))*&)$$)$$)+"#+#,

)'-%*)+$#%)

!

5!

,

7

!"#$%&'(!) ! $*+ #

0'1.'# (!.!!. 0'1.' # (!.!!. 2 !!(3

! < 3 ( 0!#

0( ("

0( ($

(!<( #!!(3 '<#.!.