Fanuc FL-Net Boad Operator

GE Fanuc Automation Europe
Computer Numerical Controls
FL - Net Board
Operators Manual
B-63434EN/02
TECHNOLOGY AND MORE
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 Operators 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
WARNING
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.
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
WARNING
GENERAL WARNINGS AND NOTES
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 operators manual and programming manual supplied with a CNC unit provide an overall description of the machines 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. % 0 i/0

i/ (1 .2 '

9
" !# " " 4 )/+# % 67 4
8

4
$
44 $ ,, $ ,

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

9 7 7

,

" ,3
:
; !
"
3 #
3 #
% 3 - 2# -

3 #

4 %$

' , ,

,
4

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

SAFETY PRECAUTIONS Describes the precautions to be observed in reading this I. manual.
GENERAL Describes the organization of this manual, applicable models, and related manuals. DESCRIPTION Describes the general for using the FL-net function.
II.
III. OPERATION Describes the setting and operation procedures for using the FLnet 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 Stand-alone type FANUC Series 16i/160i-TA Stand-alone type FANUC Series 16i/160i-MA Stand-alone type FANUC Series 18i/180i-TA Stand-alone type FANUC Series 18i/180i-MA Stand-alone type FANUC Series 21i/210i-TA Stand-alone type FANUC Series 21i/210i-MA FANUC Power Mate i-MODEL D FANUC Power Mate i-MODEL H Abbreviation 16i-TA Series 16i-A 16i-MA 18i-TA Series 18i-A 18i-MA Series 21i-A 21i-TA 21i-MA Power Mate i Power Mate i-D Power Mate i-H
-3-
1.GENERAL
GENERAL
B-63434EN/02
Related manuals
The tables below list the manuals related to each model. reading this manual, refer to the related manuals as well. Manuals related to Series 16i/18i-TA/MA
Manual name Descriptions Connection Manual (Hardware) Connection Manual (Functions) Operators Manual (For Lathes) Operators Manual (For Machining Centers) Maintenance Manual Parameter Manual Specification number B-63002EN B-63003EN B-63003EN-1 B-63004EN B-63014EN B-63005EN B-63010EN
When
Manuals related to Series 21i-TA/MA

Manual name Descriptions Connection Manual (Hardware) Connection Manual (Functions) Operators Manual (For Lathes) Operators Manual (For Machining Centers) Maintenance Manual Parameter Manual Specification number B-63002EN B-63003EN B-63003EN-1 B-63084EN B-63094EN B-63005EN B-63090EN
Manuals related to FANUC Power Mate i-MODEL D/H

Manual name Descriptions Connection Manual (Hardware) Connection Manual (Functions) Operators Manual Maintenance Manual Parameter Manual Specification number B-63172EN B-63173EN B-63173EN-1 B-63174EN B-63175EN B-63180EN
-4-
II. DESCRIPTION
B-63434EN/02
DESCRIPTION
1.FL-net SPECIFICATIONS
FL-net SPECIFICATIONS
This section describes the specifications of the FL-net.
-7-
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) Controllers
Company A PLC Company B PLC Company C PLC Company D personal CNC Company E RC
Field network Devices Sensor actuator
Large-scale network Up to 249 communication devices (nodes) can be connected to share data among them.
FL-net
248
249
250
254
%&'()01'2345%6789@(1')3'&A
%&' ()01'23 6BC 5% 6B7DE%20@F(5'(@(9'G
-8-
B-63434EN/02
DESCRIPTION
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.
H9IF9&@5@ RF5S@5%T'( H9IF952@(30F33F%(
'33@Q' &@5@
H9IF9 52@(30F33F%( P 0'33@Q' 52@(30F33F%(
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 (Transmission) (Reception) (Reception) (Reception) Node=02 (Reception) (Transmission) (Reception) (Reception) Node=03 (Reception) (Reception) (Reception) (Transmission) Node=04 (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-
DESCRIPTION
B-63434EN/02
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 -
B-63434EN/02
DESCRIPTION
1.2
FANUC FL-net Functions

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.
Cyclic transmission
The FL-net common memory contains two areas: an 8K-bit (= 0.5Kword) 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 -
DESCRIPTION
B-63434EN/02
For details of message transmission, see Chapter 3, "Message Transmission," in "Description."
- 12 -
B-63434EN/02
DESCRIPTION
2.CYCLIC TRANSMISSION
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 -
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.

#+#
%00%(0'0%2H@2'@4

)0+ )'-

+#-$% '## *+)$
@UC
@U4 @44
+#-$% '## *+)$ )0+ )'+#-$% '## )* 0 ()&#( )' +#-$% '## *+)$ )0+ )'-
@46
@U6
+#-$% '## *+)$ )0+ )'+#-$% '## *+)$ )0+ )'-
- 14 -
B-63434EN/02
DESCRIPTION
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
Procedure
DO data allocation
Set the following parameters beforehand: 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:
@7U
V
)' =$1+ )**- :% /)+'-; ## -%> :% /)+'-; )**- :% /)+'-;
2222<, 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)
DESCRIPTION
B-63434EN/02
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.
@2'@ @7U

2222<, 2222< 2222< 2222<5
%&'()01'2 %EE3'5 @5@3FW' %EE3'5 @2'@ RF59SEI@Q X@2'@
@77
2222
%00%(0'0%2H @2'@6

2@(30F5&@5@E2%0 %5S'2(%&'3 2@(30F5&@5@%E 5S'I%9@I(%&'
@7C &@5@
@4U @74
@47
2@(30F5&@5@E2%0 %5S'2(%&'3
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 -
B-63434EN/02
DESCRIPTION
2.2.2
2.2.2.1
DI data allocation 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
Set the following parameters beforehand: 1) Pa42: Allocation address (for DI) 2) Pa43: Area 2 data exchange condition allocation address 3) Pa44: Switch flag allocation address 4) Pa46: Area 2 static allocation data size = 0 Organization of area 2 data exchange condition allocation:
@7U
V
)' =$1+ )**- :% /)+'-; ## -%> :% /)+'-; )**- :% /)+'-;
2222<, 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: 1) The user program specifies the following in the PMC D area specified by Pa43 (area 2 data exchange condition allocation address): Node number DI offset Data size 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. 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 -
DESCRIPTION
B-63434EN/02
@7U
2222<, 2222< 2222< 2222<5
@2'@

%&'()01'2 %EE3'5 @5@3FW' %EE3'5 @2'@ RF59SEI@Q X@2'@
@77
2222
%00%(0'0%2H @2'@6

@76
:%5';
!
&@5@
2@(30F5&@5@E2%0 %5S'2(%&'3 2@(30F5&@5@E2%0 %5S'2(%&'3 2@(30F5&@5@E2%0 %5S'2(%&'3 2@(30F5&@5@E2%0 %5S'2(%&'3
- 18 -
B-63434EN/02
DESCRIPTION
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. - If a negative value is set in Pa43 (area 2 data 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. - If a negative value is set in Pa44 (switch flag 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 -
DESCRIPTION
B-63434EN/02
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
Set the following parameters beforehand: 1) Pa42: Allocation address (for DI) 2) Pa43: Area 2 data exchange condition allocation address 3) Pa44: Switch flag allocation address 4) Pa45: Area 2 static allocation start address 5) Pa46: Area 2 static allocation data size (in words) Organization of area 2 data exchange condition allocation:
@7U
V
)' =$1+ )**- :% /)+'-; ## -%> :% /)+'-; )**- :% /)+'-;
2222<, 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: 1) The user program specifies the following in the PMC D area specified by Pa43 (area 2 data exchange condition allocation address): Node number 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, 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 -
B-63434EN/02
DESCRIPTION
@7U
2222<, 2222< 2222< 2222<5
@2'@

%&'()01'2 %EE3'5 @5@3FW' %EE3'5 @2'@ RF59SEI@Q X@2'@
@77
2222
%00%(0'0%2H @2'@6

@76
!
&@5@
@74
:%5'; @7C
2@(30F5&@5@E2%0 %5S'2(%&'3 2@(30F5&@5@E2%0 %5S'2(%&'3 2@(30F5&@5@%E 5S'I%9@I(%&' 2@(30F5&@5@E2%0 %5S'2(%&'3
@7Y
- 21 -
DESCRIPTION
B-63434EN/02
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. - If a negative value is set in Pa43 (area 2 data exchange condition allocation address), transfer of information on other nodes are not performed. - If a negative value is set in Pa44 (switch flag allocation address), node information cannot dynamically be changed.
2.2.2.3
Nodes information
- 22 -
B-63434EN/02
DESCRIPTION
Information on other nodes and DI data are allocated in the PMC area as follows:
@76
V
<, < < < : -+?'; (%@ (#"+ -# AA+ (#"+ -# '##
FA link layer state:

< 5 ! : -+?'; ,
!"#$# %&&&&")"0" %&&&&#&%& '(#"""#'(#"""#"

Upper layer state:
< < !; 5 5; ! ; ; 4; ; ,; ; ; ; , ; ;
"#$!%
B ,,C ,C 2C
6 ,C C
B B
; :7%.0- 1%; ) ; :)/- 1%;
NOTE For details of each bit, see Subsection 2.3.1, "Allocation of local node state."
- 23 -
DESCRIPTION
B-63434EN/02
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'2`2%Q2@0 4G '53 '@9S `@2@0'5'2 F( 5S' @2'@3`'9FEF'& 1H @7UA 6G '53 S F( 5S' 3RF59S EI@Q3`'9FEF'&1H @77A
H35'0 UG S'9T35S@55S'3RF59SEI@Q F33'55%SA 7G '@&3'@9S`@2@0'5'2E2%0 5S' @2'@ 3`'9FEF'& 1H @7UA BG a9S@(Q'3 &@5@ )(&'2 @ ('R &@5@ 'a9S@(Q' 9%(&F5F%(A YG '53CCSF(5S'3RF59SEI@QA '2E%203 &@5@ 'a9S@(Q' )(&'25S'('R&@5@'a9S@(Q' 9%(&F5F%(E2%05SF3`%F(5@(& )À
VG S'9T3 5S@5 5S' 3RF59S EI@QF33'55%CCSA bG '2E%203&@5@`2%9'33F(QA
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 -
B-63434EN/02
DESCRIPTION
2.3
2.3.1
Node State Monitoring

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:
@6C
V
<, < < < )&#( )' -# (%@ -# 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 -
DESCRIPTION
B-63434EN/02
FA link state:
< 5 ! : -+?'; ,
!"#$# %&&&&")"0" %&&&&#&%& '(#"""#'(#"""#"

Table 2-2 FA Link State
Item Node participation flag
Description 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
6 ,C C
B B
; :7%.0- 1%; ) ; :)/- 1%; : 0%- &)' %- ) =-' /%0 0%'?%&;
- 26 -
B-63434EN/02
DESCRIPTION
Table 2-3 Upper Layer State
Item U_ERR_CODE U_ERR RUN/STOP
Description Currently, not supported. Currently, not supported. The RUN/STOP state of the PMC ladder program is set.
Current RCT value:

< <! 4; ; 5 ,; ; ! ; ; ; ; ; !; ; 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 -
DESCRIPTION
B-63434EN/02
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.
@64
<, <
&! &!
&!' &!(
&! &!)
&!( &!0
&!) &!
&!0 &!
&! "#$!% &!1 &!2
<, &!0( &!0(' &!0( &!0(( &!0() &!0(0 &!0( &!0( < "#$!% &!0( &!0) &!00 &!0 &!0 &!0(1 &!0(2
The bits of node numbers (including the local node) that participate in the network are set to 1.
- 28 -
B-63434EN/02
DESCRIPTION
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
%00%(0'0%2H@2'@4 4B C
<,,,, <,,, 7 !57

#+#
<,, <, <, <,
7 7 7 !57
Common memory area 2 and the PMC area
%00%(0'0%2H@2'@6 4B C
<,,,, <,,, 7 !57

#+#
<,, <, <, <,
7 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 -
DESCRIPTION
B-63434EN/02
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 -
B-63434EN/02
DESCRIPTION
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 -
DESCRIPTION
B-63434EN/02
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 R0100 R0105 R0106 Flag 1 for synchronization Data section 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. 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.
3)
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 -
B-63434EN/02
DESCRIPTION
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 1A1 words Area 2A2 words Node #B: Area 1B1 words Area 2B2 words Node #C: Area 1C1 words Area 2C2 words Node #D: Area 1D1 words Area 2D2 words
- 33 -
DESCRIPTION
B-63434EN/02
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.

@2'@
34
c c" c" c c c c c c c
0(5!6
7085!
340
3085!
c c" c" c c c c c c c

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
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 -
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 -
B-63434EN/02
DESCRIPTION
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 User program Server User program
System -A)- $--#. D=- $--#.
System
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 -
DESCRIPTION
B-63434EN/02
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.
@BC
7 +0 +2 +3 +4 +5 +6 +8 Transmission request/response flag Request status (R_STS) Response status (M_RLT) Cancel flag Destination node number (Reserved) Message section
@B4
NOTE The message section does not include a data buffer area.
- 38 -
B-63434EN/02
DESCRIPTION
Table 3-2 Transmit Interface Items Interface item Description Direction US Flag set by the user program to request message Transmission SU request/response transmission, and set by the CNC to post the reception of a response message or the occurrence of an error. flag(Note 1) 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. SU Request status Status for checking if a request message has been (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 SU Response status Status for checking a response message (M_RLT) 00h: Normal response 01h: Abnormal response 02h: Server service not supported US Cancel flag Set a value other than 0 for service cancellation before a (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 US number US Message section Area for setting a message transaction code, parameters, SU and so forth. The information set in this area depends on 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 (US) or is posted from the system to the user program (SU).
- 39 -
DESCRIPTION
B-63434EN/02
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 -
B-63434EN/02
DESCRIPTION
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 -
DESCRIPTION
B-63434EN/02
Receive interface for transparent messages

The interface area specified by Pa52 (transparent receive message allocation address) has the format shown below.
@B6
7 +0 +2 +3 +4 +6 +8 Receive flag
Transmission source node number (Reserved) Transaction code Size Data
@BU
Table 3-4 Transparent Message Receive Interface Items Interface item Description Receive flag Flag used by the system to post the reception of a transparent message to the user program. 0001h: The system posts the reception of a transparent message. 0000h: The user program posts the completion of message receive processing. Transparent message transmission source node number Transmission source node number Transaction code Transaction code of a received transparent message Size Number of words of data contained in a received transparent message Data Data contained in a received transparent message
Direction SU US
SU
SU SU SU
- 42 -
B-63434EN/02
DESCRIPTION
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

4G '33@Q' `2'`@2@5F%( @9S 35@5)3 EI@Q F3 9I'@2'&A 6G 2@(30F33F%( 2'd)'35 EI@QCCC4S bG S'9TF(Q2'd)'3535@5)3 4BG S'9TF(Q 5S@5 5S' 2'3`%(3' EI@Q F3 3'5 5% bCCCSA 4YG S'9TF(Q 2'3`%(3' 35@5)3 4VG '3`%(3' 0'33@Q' `2%9'33F(Q 4bG I'@2F(Q 5S' 2'3`%(3' EI@Q5%CCCCS
-+ A+).+#$ -+ A+).+#$
(% "-$
UG S'9TF(Q 5S@5 5S' 52@(30F33F%( 2'd)'35 EI@Q F33'55%CCC4S 7G 'd)'35 0'33@Q' 52@(30F33F%( VG #2'9'`5F%( 44G '3`%(3' 0'33@Q' 2'9'`5F%( 46G '3`%(3'EI@QbCCCS 4UG #2'9'`5F%(
+?+
$ ' ) 0
!"# %&#""# (! "# %& !"#
"-$

- 43 -
DESCRIPTION
B-63434EN/02
3.3.2
Procedure for operating the transparent message transmission function

2@(3`@2'(50'33@Q'52@(30F33F%(3F&' 3'2`2%Q2@0 H35'0 2@(3`@2'(5 0'33@Q' `2'`@2@5F%( @9S 35@5)3 EI@Q F3 9I'@2'&A 2@(30F33F%( 2'd)'35 UG S'9TF(Q 5S@5 5S' 52@(30F33F%( 2'd)'35 EI@Q EI@QCCC4S F33'55%CCC4S 7G 2@(3`@2'(5 0'33@Q' 52@(30F33F%( S'9TF(Q2'd)'3535@5)3 44G #2'9'`5F%( S'9TF(Q 5S@5 5S' 4UG %0Ì'5F%(EI@QbCCCS 9%0Ì'5F%(EI@QF33'55% bCCCS I'@2F(Q 5S' 9%0Ì'5F%( EI@Q5%CCCCS
4G 6G 46G 47G 4BG
2@(3`@2'(50'33@Q'2'9'`5F%(3F&' 3'2`2%Q2@0 H35'0 BG 2@(3`@2'(5 0'33@Q' 2'9'`5F%( YG #52@(30F33F%( bG S'9TF(Q 5S@5 5S' VG '9'Fe'EI@QCCC4S 2'9'Fe' EI@Q F3 3'5 5% CCC4S 8G '9'Fe' 0'33@Q' `2%9'33F(Q 4CG I'@2F(Q5S'2'9'Fe'EI@Q 5%CCCCS
- 44 -
B-63434EN/02
DESCRIPTION
3.4
3.4.1
Message Transmission Client Function

This section describes the detailed interface of each service of the message transmission client function.
Byte block read

Request message Response message 0 Transmission request flag 0001h +0 7 Response flag 0
@BC +0
+2 +3 +4 +5 +6 +8 +10 +12 +16 +18
Cancel flag Destination node number (Reserved) Transaction code 65003 (Reserved) Offset address on virtual address space Data size Read data buffer start address (Reserved)
+2 +3 +4 +5 +6 +8 +10 +12 +16 +18
Request status Response status
(Reserved) Transaction code 65203 (Reserved) Offset address on virtual address space Data size Read data buffer start address Read data
@B4
- 45 -
DESCRIPTION
B-63434EN/02
Byte Block Read Interface Items Description Direction Request message: 65003 US Response message: 65203 SU US Offset address on virtual address Offset address on Request message: space of byte block data to be read virtual address from the server space Response message: Same as above US Data size Request message: Size of byte block data to be read SU from the server (in bytes) Response message: Size of byte block data actually read from the server (in bytes) US Read data buffer Request message: Start address of an area in the start address PMC R area used to store byte block data read from the server Response message: Same as above SU Read data Request message: Reserved Response message: Byte block data actually read from the server. When an abnormal response is returned, an error code is stored. Interface item Transaction code
Table 3-5
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 -
B-63434EN/02
DESCRIPTION
3.4.2
Byte block write

@BC +0
+2 +3 +4 +5 +6 +8 +10 +12 +16 +18
Cancel flag Destination node number (Reserved) Transaction code 65004 (Reserved) Offset address on virtual address space Data size Write data buffer start address Write data
+2 +3 +4 +5 +6 +8 +10 +12 +16 +18
(Reserved) Transaction code 65204 (Reserved) Offset address on virtual address space Data size Write data buffer start address (Reserved) Error code when an abnormal response is returned
@B4
- 47 -
DESCRIPTION
B-63434EN/02
Byte Block Write Interface Items Description Direction Request message: 65004 US Response message: 65204 SU US Offset address on virtual address Offset address on Request message: space of byte block data to be virtual address written to the server space Response message: Same as above US Data size Request message: Size of byte block data to be written SU to the server (in bytes) Response message: Size of byte block data actually written to the server (in bytes) US Write data buffer Request message: Start address of an area in the start address PMC R area storing byte block data to be written to the server Response message: Same as above US Write data Request message: Byte block data to be written to the SU server Response message: An error code is stored when an abnormal response is returned. Interface item Transaction code
Table 3-6
- 48 -
B-63434EN/02
DESCRIPTION
3.4.3
Word block read

@BC +0
+2 +3 +4 +5 +6 +8 +10 +12 +16 +18
Cancel flag Destination node number (Reserved) Transaction code 65005 (Reserved) Offset address on virtual address space Data size Read data buffer start address (Reserved)
+2 +3 +4 +5 +6 +8 +10 +12 +16 +18
(Reserved) Transaction code 65205 (Reserved) Offset address on virtual address space Data size Read data buffer start address Read data
@B4
- 49 -
DESCRIPTION
B-63434EN/02
Word Block Read Interface Items Description Direction Request message: 65005 US Response message: 65205 SU US Offset address on virtual address Offset address on Request message: space of word block data to be virtual address read from the server space Response message: Same as above US Data size Request message: Size of word block data to be read SU from the server (in bytes) Response message: Size of word block data actually read from the server (in bytes) US Read data buffer Request message: Start address of an area in the start address PMC R area used to store word block data read from the server Response message: Same as above SU Read data Request message: Reserved Response message: Word block data actually read from the server. When an abnormal response is returned, an error code is stored. Interface item Transaction code
Table 3-7
- 50 -
B-63434EN/02
DESCRIPTION
3.4.4
Word block write

@BC +0
+2 +3 +4 +5 +6 +8 +10 +12 +16 +18
Cancel flag Destination node number (Reserved) Transaction code 65006 (Reserved) Offset address on virtual address space Data size Write data buffer start address Write data
+2 +3 +4 +5 +6 +8 +10 +12 +16 +18
(Reserved) Transaction code 65206 (Reserved) Offset address on virtual address space Data size Write data buffer start address (Reserved) Error code when an abnormal response is returned
@B4
- 51 -
DESCRIPTION
B-63434EN/02
Word Block Write Interface Items Description Direction Request message: 65006 US Response message: 65206 SU US Offset address on virtual address Offset address on Request message: space of word block data to be virtual address written to the server space Response message: Same as above US Data size Request message: Size of word block data to be SU written to the server (in bytes) Response message: Size of word block data actually written to the server (in bytes) US Write data buffer Request message: Start address of an area in the start address PMC R area storing word block data to be written to the server Response message: Same as above US Write data Request message: Word block data to be written to the SU server Response message: An error code is stored when an abnormal response is returned. Interface item Transaction code
Table 3-8
- 52 -
B-63434EN/02
DESCRIPTION
3.5
3.5.1
Message Transmission Server Function

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 Error code 8001h 8002h 8003h 8004h List of Server Function Error Codes Description An attempt was made to access a nonexistent PMC area. A specified data size exceeded 1024 bytes. An attempt to allocate a parameter storage area failed. A request was made to write to a write-prohibited area.
- 53 -
DESCRIPTION
B-63434EN/02
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 Virtual address Allocation in PMC space Symbol Type of signal Address (hexadecimal) (decimal) X Signal from machine to X0000 or 0000h or later PMC later Y Signal from PMC to Y0000 or 4000h or later machine later F Signal from CNC to PMC F0000 or 8000h or later later G Signal from PMC to CNC G0000 or C000h or later later R Internal relay R0000 or 10000h or later later D Data table D0000 or 14000h or later later Remarks
Read only Read only Read only Read only Read/write Read/write
Virtual address space for word block data

Table 3-11 Virtual Address Space for Word Block Data Remarks Allocation in PMC Virtual address space Symbol Type of signal Address (hexadecimal) (decimal) 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 -
B-63434EN/02
DESCRIPTION
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 message Transmission completion message 7 Transmission request flag 0001h (Reserved) Cancel flag Destination node number (Reserved) Transaction code 50000 to 59999 (Reserved) Data size Transmit data buffer start address Transparent transmit data +0 Completion flag
@BC +0
+2 +3 +4 +5 +6 +8 +10 +16 +18
+2 +3 +4 +5 +6 +8 +10 +16 +18
Request status
(Reserved) Transaction code 50000 to 59999 (Reserved) Data size Transmit data buffer start address (Reserved)
@B4
NOTE Note that when the destination node number is set to 255, the message is transmitted to all nodes.
- 55 -
DESCRIPTION
B-63434EN/02
Table 3-12 Transparent Transmit Message Interface Items Interface item Description Transaction code !,,,, ) !4444 Data size Size of transparent data to be transmitted (in words) Start address of an area in the PMC R area storing Transmit data transparent data to be transmitted buffer start address Transparent Transparent data to be transmitted transmit data
Direction US US US
US
- 56 -
B-63434EN/02
DESCRIPTION
3.6.2
Transparent message reception

Reception notification message Reception confirmation message
@B6 +0
+2 +3 +4 +6 +8
7 Receive flag 0001h Transmission source node number (Reserved) Transaction code 50000 to 59999 Data size Transparent receive data
0 +0 +2 +3 +4 +6 +8
7 Completion flag
Transaction code 50000 to 59999 Data size Transmit data buffer start address
@BU
Table 3-13 Transparent Receive Message Interface Items Interface item Description Direction Receive flag When a transparent message is received, this flag is set to SU 0001h after the interface items below are set. Node number of a transmission source that transmitted a SU Transmission transparent message source node number Transaction code !,,,, ) !4444 SU Data size Size of received transparent data (in words) SU Transparent Transparent data received SU 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 -
DESCRIPTION
B-63434EN/02
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

'9'`5F%((%5FEF9@5F%( 0'33@Q' V C
&%? *(#.
@B6 <,
< < < <5 < <
<, < < < <5 < <
'9'`5F%( 9%(EF20@5F%(0'33@Q' V C
)$A(%) *(#. ,,,,0
2@(30F33F%(3%)29' (%&'()01'2
: -+?'; +#-#&%) &)' 5!,, ) 5!,,5 ## -%>
,,,0
+#-#&%) &)' 5!,, ) 5!,,5 ## -%>
@BU
EE3'5@&&2'33%( eF25)@I@&&2'333`@9'
EE3'5@&&2'33%( eF25)@I@&&2'333`@9'
- 58 -
B-63434EN/02
DESCRIPTION
Table 3-1 Receive Message Interface Items Interface item Receive flag Description When a message is received, this flag is set to 0001h after the interface items below are set. Number of the node which transmitted a message 65003 to 65006 Size of received message data Offset address on virtual address space Received write request data Direction SU
Transmission source node number Transaction code Data size Virtual address space Write data
SU
SU SU SU SU
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 02 (buffer full) 03 (not initialized) 06 (format error) Description The previously received message is not processed by the user program. An interface area for receiving a message is not allocated. 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 -
DESCRIPTION
B-63434EN/02
3.7.2
Response message transmission

2@(30F33F%(2'd)'35 0'33@Q' V C
1#""#23
,,,0
@BC <,
< < < <! <5 < <, < <5 <
<, < < < <! <5 < <, < <5 <
2@(30F33F%( 9%0Ì'5F%(0'33@Q' V C
)$A(%) *(#. D=- -#=-
#&( *(#.
4"#"###5
: -+?'; +#-#&%) &)' 5!, ) 5!,5 : -+?';
: -+?'; +#-#&%) &)' 5!, ) 5!,5 : -+?';
@B4
EE3'5@&&2'33%( eF25)@I@&&2'333`@9'
## -%>
EE3'5@&&2'33%( eF25)@I@&&2'333`@9'
## -%>
Table 3-3 Response Message Interface Items Interface item Transaction code Virtual address space Data size Transmit data buffer start address Read data Description 65203 to 65206 Offset address on virtual address space Size of data to be transmitted Start address of an area in the PMC R area containing data to be transmitted Read request data for response Direction US US US US
US
NOTE The procedure for transmission of a message with confirmation is the same as for the transparent message transmission function.
- 60 -
B-63434EN/02
DESCRIPTION
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 Symbol X Y F G R D Allocation in PMC Type of signal Signal from machine to PMC Signal from PMC to machine Signal from NC to PMC Signal from PMC to NC Internal relay Data table Address (decimal) X0000 or higher Y0000 or higher F0000 or higher G0000 or higher R0000 or higher D0000 or higher Virtual address space (hexadecimal) 01000000h or higher 01004000h or higher 01008000h or higher 0100C000h or higher 01010000h or higher 01014000h or higher Remarks
Virtual address space for word block data with confirmation

Table 3-5 Virtual Address Space for Word Block Data with Confirmation Symbol X Y F G R D Allocation in PMC Type of signal Signal from machine to PMC Signal from PMC to machine Signal from NC to PMC Signal from PMC to NC Internal relay Data table Address (decimal) X0000 or higher Y0000 or higher F0000 or higher G0000 or higher R0000 or higher D0000 or higher Virtual address space (hexadecimal) 01000000h or higher 01002000h or higher 01004000h or higher 01006000h or higher 01008000h or higher 0100A000h or higher Remarks
NOTE Only installed address space in the PMC can be accessed. Check PMC address space before use.
- 61 -
DESCRIPTION
B-63434EN/02
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()&@ '##
C
<,, <, <, <,

#+#
<,, <, <, <,
7 7 !57 7
7 7 !57 7
Word block data and the PMC area

)+' 1()&@ '##
4B

#+#
<,,,, <,,,
7 !57
<,, <, <, <,
7 7 7 !57
Transparent data and the PMC area

+#-A#+ '##
4B

#+#
<,,,, <,,,
7 !57
<,, <, <, <,
7 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
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 (4) Area 2 allocation parameters (5) Message allocation parameters Each parameter is detailed below. (1) Basic parameters
Parameter name IP address Basic Parameters Description Index number Pa10 IP address of the local node (The host address section of this IP address is the node number of the local node.) Start address of an area 1 area allocated as Pa11 DO of the local node Data size of an area 1 area allocated as DO Pa12 of the local node Start address of an area 2 area allocated as Pa13 DO of the local node Data size of an area 2 area allocated as DO Pa14 of the local node Token hold time of the local node Pa15 Pa16 Pa17 Table 1-1
Start address of area 1 transmit data Area 1 transmit data size Start address of area 2 transmit data Area 2 transmit data size Token monitoring time Allowable minimum Inter-frame time interval requested to frame interval another node Node name Equipment name of the local node
(2) State monitoring parameters

Table 1-2 Parameter name Local node information address Participating node information address State Monitoring Parameters Description Start address of an area in the PMC R area used as the output destination of status information about the local node Start address of an area in the PMC R area used as the output destination of a list of all nodes participating in the network Index number Pa20
Pa21
- 66 -
B-63434EN/02
OPERATION
1.PARAMETER SETTING
(3) Area 1 allocation parameters

Table 1-3 Area 1 Allocation Parameters Parameter name Description Allocation address Start address of an area in the PMC R area (shared for DI/DO) allocated to area 1 Area 1 address Start address of area 1 allocated to an area (shared for DI/DO) in the PMC R area Data size (shared for Size of data to be exchanged DI/DO) Index number Pa30 Pa31 Pa32
(4) Area 2 allocation parameters

Area 2 Allocation Parameters Parameter name Description Index number Pa40 Allocation address Start address of an area in the PMC R area (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 Pa42 Allocation address Start address of an area in the PMC R area (for DI) or D area that serves as the read destination of information about other nodes and data from area 2 Pa43 Address of an area in the PMC D area that is Area 2 data exchange condition used to specify conditions on data exchange with area 2 allocation address Pa44 Switch flag Flag for switching between specified 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) Table 1-4
(5) Message allocation parameters

Table 1-5 Message Allocation Parameters Parameter name Description Index number Pa50 Interface allocation Start address of an area in the PMC R or D 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 Pa52 Transparent receive Start address of an area in the PMC R area message allocation or D area that serves as the start address of an interface used to store transparent address message receive data Pa53 Transparent receive Maximum allowable size of the interface area message allocation used above size
- 67 -
1.PARAMETER SETTING
OPERATION
B-63434EN/02
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 Cyclic transmission of common memory area 2 Basic parameters Area 2 allocation parameters Message transmission Basic parameters Message allocation parameters
B.
C.
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 -
B-63434EN/02
OPERATION
1.PARAMETER SETTING
1.2
1.2.1
Procedure
Setting of Parameters
Before the FL-net function can be used, the parameters described below must be set.
Series 16i/18i/21i-A
(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 FLnet 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 -
1.PARAMETER SETTING
OPERATION
B-63434EN/02
(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 -
B-63434EN/02
OPERATION
1.PARAMETER SETTING
Setting item
Each setting item is described below.
Basic parameters
The basic parameters are used to set the FL-net function itself.
Basic Parameters Description 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. Only an IP address in class C can be specified. An arbitrary node name not longer than 10 characters can be specified. Lowercase letters cannot be displayed and entered. Start address of common memory area 1 of the local node. A value from 0 to 511 can be set. Data size of common memory area 1 of the local node. A value from 0 to 512 can be set. Start address of common memory area 2 of the local node. A value from 0 to 8191 can be set. Data size of common memory area 2 of the local node. A value from 0 to 8192 can be set. Token monitoring time. Maximum duration of time for which the local node can hold the token. A value from 1 to 255 can be set. (Unit: ms) 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 receive data frames in succession. Usually, set 10 (1 ms). Table 1-6
Item IP ADDRESS
Pa10 NODE NAME Pa17 AREA1 ADDR (Note 1) Pa11 AREA1 SIZE (Note 1) Pa12 AREA2 ADDR (Note 1) Pa13 AREA2 SIZE (Note 1) Pa14 TOKEN WATCH (Note 2) Pa15 MIN FRAME
Pa16
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 -
1.PARAMETER SETTING
OPERATION
B-63434EN/02
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 Item OWN STATUS State Monitoring Parameters Description 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
Area 1 allocation parameters

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.
Table 1-8 Item AREA1 DO/DI: ALLOCATION Pa30 AREA1 DO/DI: ADDRESS Pa31 AREA1 DI/DO: SIZE(Note 1) Area 1 Allocation Parameters Description Start address of an area in the PMC R area used for data exchange with common memory area 1. This parameter allows only an even address to be set. Start address of an area in common memory area 1 used for data exchange with the PMC R area.
Size of data exchanged between common memory area 1 and 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 -
B-63434EN/02
OPERATION
1.PARAMETER SETTING

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.
Table 1-9 Item AREA2 DO: ALLOCATION Pa40 AREA2 DO: SIZE(Note 1) Pa41 AREA2 DI: ALLOCATION Area 2 Allocation Parameters Description Start address of an area in the PMC R area or D area used for DO data exchange with common memory area 2. This parameter allows only an even address to be set. Size of DO data exchanged between common memory area 2 and the PMC R area or D area (Unit: Words). When DO data exchange between common memory area 2 and the PMC is not performed, set 0 in this parameter. Start address of an area in the PMC R area or D area used for 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]. This parameter allows only an even address to be set. Set an area in the PMC R area used to specify a node from which data is to be read as DI data. 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]. This parameter allows only an even address to be set. The user can dynamically switch between nodes from which data is to be read as DI data. Specify an area in the PMC R area used to specify switch timing. When dynamic switching is not performed for reading DI data, set -1 in this parameter, or press soft key [DISABL]. Start address of common memory area 2 to be statically allocated in the PMC area as DI data
Pa42 AREA2 DI: ALLOC PTR (Note 2)
Pa43 AREA2 DI: CHANGE FLG (Note 2)
Pa44 AREA2 DI: AREA2 ADDR (Note 2) Pa45 Size of DI data statically exchanged between common AREA2 DI: memory area 2 and the PMC area (Unit: Words) AREA2 SIZE (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 -
1.PARAMETER SETTING
OPERATION
B-63434EN/02
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 -
B-63434EN/02
OPERATION
1.PARAMETER SETTING
Message allocation parameters

The message allocation parameters are used to allocate a message transmit interface area in the PMC R area.
Table 1-10 Item MESSAGE: ADDRESS Pa50 MESSAGE: SIZE Pa51 MESSAGE: RECV MSG Pa52 MESSAGE: SIZE Pa53 Message Allocation Parameters Description Start address of an interface area in the PMC R area or D area used when the message transmission client function is used. This parameter allows only an even address to be set. Size of the interface area above (Unit: Bytes). When the message transmission client function is not used, set 0 in this parameter. Start address of an interface area in the PMC R area or D area used for transparent message receive data. This parameter allows only an even address to be set. Size of the interface area above (Unit: Bytes). When transparent message receive data is not accepted, set 0 in this parameter.
- 75 -
1.PARAMETER SETTING Basic method of parameter input
OPERATION
B-63434EN/02
The basic method of parameter input is described below.
Procedure
(1) (2) (3) (4) (5) Set the CNC mode to the MDI mode. Display the parameter setting screen of screen 1-2. With the cursor keys, move the cursor to a desired item. Enter a desired parameter value with the MDI keys. 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-63434EN/02
OPERATION
1.PARAMETER SETTING
(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.PARAMETER SETTING
OPERATION
B-63434EN/02
1.2.2
Procedure
Power Mate i-MODEL D/H

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 Operators Manual."
Basic parameters
30000 IP address (1)
[Data type] [Valid data range] [Index number]
Byte 1 - 254 Pa10 Set bits 0 to 7 of the IP address of the local node.
IP address (2)
30001
IP address (3)
30002
IP address (4)
30003
- 78 -
B-63434EN/02
OPERATION
1.PARAMETER SETTING
30010 30011 30012 30013 30014 30015 30016 30017 30018 30019
Node name: Node name: Node name: Node name: Node name: Node name: Node name: Node name: Node name: Node name:
1st character 2nd character 3rd character 4th character 5th character 6th character 7th character 8th character 9th character 10th character
[Data type] [Index number]
Byte Pa17 Set the equipment name of the local node one character for each parameter in ASCII code.
Start address of area 1 transmit data
30020
Word 0 - 511 Pa11
30021
Area 1 transmit data size
Word 0 - 512 Pa12
30022
Start address of area 2 transmit data
Word 0 - 8191 Pa13
30023
Area 2 transmit data size
Word 0 - 8192 Pa14
30024
Token monitoring time
[Data type] [Unit of data] [Valid data range] [Index number]

30025
Byte 1 msec 1 - 255 Pa15

Minimum allowable frame interval
[Data type] [Unit of data]
Byte 100 sec

- 79 -
1.PARAMETER SETTING
[Valid data range] [Index number] 0 - 50 Pa16
OPERATION
B-63434EN/02
State monitoring parameters

30026 Local node informatino address
Word 0 - (only an even address) Pa20
30027
Participating node information address
Byte 0 - (only an even address) Pa21

30030 Allocation address (shared for DI/DO)

30031

Area 1 address (shared for DI/DO)

30032
Word 0 - 511 Pa31

Data size (shared for DI/DO)
Word 0 - 512 Pa32

30033 Allocation address (for DO)

30034

Data size (for DO)

30035
Word 0 - 8192 Pa41

Allocation address (for DI)

- 80 -
B-63434EN/02
OPERATION
1.PARAMETER SETTING
30036
Area 2 data exchange condition allocation address

30037

Switch flag allocation address

30050

Area 2 static DI data exchange address

30051
Word 0 - 8191 Pa45

Area 2 static DI data exchange size

30055
Word 0 - 8192 Pa46

PMC area allocation address (for DO)

30056
Word 68(D) or 82(R) Pa40

PMC area allocation address (for DI)
Message allocation parameters

30040 Interface allocation address

30041

Interface allocation size
[Data type] [Index number]

30042
Word Pa51
Receive message allocation address

30043

Receive message allocation data aize
[Data type]
Word
- 81 -
1.PARAMETER SETTING
[Index number]
30060
OPERATION
B-63434EN/02
Pa53
Interface PMC area allocation address

30061

Receive message PMC area allocation address
Node selection parameter

30045 Node number (maintenance information display node setting)
[Data type] [Valid data range]
Byte 1 - 254 Set the number of a node on which maintenance information is to be displayed.
- 82 -
B-63434EN/02
OPERATION
2.MAINTENANCE SCREEN
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 -
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. (2) Press soft keys [PMCDGN], [I/OCHK], and [FL-NET] in this 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 -
B-63434EN/02
OPERATION
[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.
3)
Screen 2-2
FL-net Participating Node Monitor Screen (9.5" LCD)
- 85 -
OPERATION
B-63434EN/02
Table 2-1 explains the items displayed on the screen.

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. 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. MAKER TYPE Manufacturer Model type 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. 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. Table 2-1
- 86 -
B-63434EN/02
OPERATION
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
(1) Press function key SYSTEM , 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 appears. (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 -
OPERATION
B-63434EN/02

Table 2-2 Item TOKEN NODE MIN FRAME RCT RCM MAX RCM MIN RCM Network Management Table Description Node number of the node that currently holds the token Maximum value of the allowable minimum frame intervals of all nodes participating in the network (in 100 s) Allowable refresh cycle time of the local node (in ms) Refresh cycle measurement time of the local node (in ms) Maximum refresh cycle measurement time of the local node (in ms) Minimum refresh cycle measurement time of the local node (in ms)
- 88 -
B-63434EN/02
OPERATION
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
(1) Press function key SYSTEM , 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 appears. (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 -
OPERATION
B-63434EN/02

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 timeout 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 -
B-63434EN/02
OPERATION
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 -
OPERATION
B-63434EN/02
2.4
Procedure
Power Mate i-MODEL D/H

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 Operators 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

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

AREA2 ADDR
8002
[Data type]
Word Start address of common memory area 2 of the node

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

LKS
8004
[Data type]
Byte State of the FA link of the node

ULS
8005
[Data type]
Word State of the upper layer of the node

TOKEN WATCH
8006
Byte 1 msec Token monitoring time of the node
- 92 -
B-63434EN/02
OPERATION
MIN FRAME
8007
Byte 100 sec Minimum allowable frame time interval of the node
RCT
8008
Word 1 msec Allowable refresh cycle time of the node

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

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

MAKER TYPE
8011
[Data type]
Byte (10-byte data) 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

NODE NAME
8021
[Data type]
Byte (10-byte data) Node name of the local node

VENDOR NAME
8022
[Data type]
Byte (10-byte data) Vendor name of the local node

MAKER TYPE
8023
[Data type]
Byte (10-byte data)

- 93 -
OPERATION
B-63434EN/02
Manufacturer type of the local node

8024 STATUS
[Data type]
Byte Status of the local node

LKS
8025
[Data type]
Byte State of the FA link of the local node

ULS
8026
[Data type]
Word State of the upper layer of the local node

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

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

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

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

TOKEN WATCH
8031
Byte 1 msec Token monitoring time of the local node

MIN FRAME
8032
Byte 100 sec Minimum allowable frame time interval of the local node
PRTCL VER.
8033
[Data type]
Byte Protocol version
Network management table

8040 TOKEN NODE
[Data type]
Byte
- 94 -
B-63434EN/02
OPERATION
Node number of the node that currently holds the token

8041 MIN FRAME
Byte 100 sec Maximum value of the minimum allowable frame time intervals of all nodes participating in the network
RCT
8042
Word 1 msec Allowable refresh cycle time of the local node

RCM
8043
Word 1 msec Refresh cycle measurement time of the local node

MAX RCM
8044
Word 1 msec Maximum refresh cycle measurement time of the local node
MIN RCM
8045
Word 1 msec Minimum refresh cycle measurement time of the local node
Log data
8050 TOTAL SEND COUNT
[Data type]
Double word Total number of transmitted frames

SEND ERROR COUNT
8051
[Data type]
Double word Number of transmission errors

TOTAL RECEIVE COUNT
8052
[Data type]
Double word Total number of received frames

RECEIVE ERROR COUNT
8053
[Data type]
Double word Number of receive errors The reception of a packet other than an FL-net packet is also counted as a receive error.
- 95 -
8054
OPERATION
B-63434EN/02
CYCLIC DATA ERROR COUNT
[Data type]
Double word Number of errors in cyclic transmission

MESSAGE RETRY COUNT
8055
[Data type]
Double word Number of retrials for message transmission

MESSAGE RETRY OVER COUNT
8056
[Data type]
Double word Number of operations where retrials for message transmission exceeded the maximum number
MESSAGE RECEIVE ERROR COUNT
8057
[Data type]
Double word Number of receive message errors

ACK ERROR COUNT
8058
[Data type]
Double word Number of ACK data errors

DUPLICATED TOKEN COUNT
8059
[Data type]
Double word Number of duplicate tokens detected

DESTROYED TOKEN COUNT
8060
[Data type]
Double word Number of token discard operations

TOKEN COUNT
8061
[Data type]
Double word Number of token reissue operations

FRAME WAIT COUNT
8062
[Data type]
Double word Number of frame wait states entered because there are no other nodes in the network
ENTRY COUNT
8063
[Data type]
Double word Number of network participation operations performed by the local node
OWN DISCONNECT COUNT
8064
[Data type]
Double word Number of disconnections of the local node from the network due to a token hold time-out
SKIP DISCONNECT COUNT
8065
- 96 -
B-63434EN/02
OPERATION
[Data type]
Double word Number of disconnections of the local node from the network because the token is not passed to the local node
OTHER NODE DISCONNECT COUNT
8066
[Data type]
Double word Number of recognitions that other nodes are disconnected from the network
- 97 -
3.EXAMPLE OF CONNECTION
OPERATION
B-63434EN/02
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.1
Example of Configuration
Using the example of configuration shown below, this section describes the setting of each parameter.
Ethernet
Series 16i -A Node No.10
Series 18i -A Node No.20
Power Mate i -D 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 1
0x0000 0x0010 0x0014 0x0018 0x001c 0x0090 0x00a0 0x00d0 0x01ff 0x0000
Common memory area 2 Node No. 10
Node No. 10 Node No. 20 Node No. 30
0x0040 0x0050
Node No. 20
Node No. 30
0x1fff
- 99 -
OPERATION
B-63434EN/02
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 R0108 R0116 R0124 R0128 R0160
Common memory area 1 data Local node information Participating node list
Node No. 10 Node No. 20 Node No. 30
Common memory area 2 DO data

R0288 R0299 R0300 R0304 R0432 R0450 R0470
Switch flag Common memory area 2 DI data Information other nodes Real data on
Message client
transmission
Interface Read/write buffer
R1494
- 100 -
B-63434EN/02
OPERATION
Item IP ADDRESS NODE NAME AREA1 ADDR AREA1 SIZE AREA2 ADDR AREA2 SIZE TOKEN WATCH MIN FRAME OWN STATUS ENTRY NODE AREA1 DO/DI: ALLOCATION ADDRESS SIZE AREA2 DO: ALLOCATION SIZE
Table 3-1 Parameters of Node No. 10 Setting Item Setting 192.168.250.10 AREA2 DI: NODE#10 ALLOCATION R0300 16 ALLOC PTR D0000 4 CHANGE FLG R0299 0 AREA2 ADDR 0 64 AREA2 SIZE 0 50 MESSAGE: 10 ADDRESS R0450 R0124 SIZE 20 R0128 RECV MSG R0000 SIZE 0 R0100 16 12 D0000 of PMC 20 D0002 of PMC 0 R0160 D0004 of PMC 64 64 D0006 of PMC 0 Table 3-2 Parameters of Node No. 20 Setting Item Setting 192.168.250.20 AREA2 DI: NODE#20 ALLOCATION R0300 20 ALLOC PTR D0000 4 CHANGE FLG R0299 80 AREA2 ADDR 0 64 AREA2 SIZE 0 50 MESSAGE: 10 ADDRESS R0450 R0124 SIZE 20 R0128 RECV MSG R0000 SIZE 0 R0100 16 12 D0000 of PMC 30 D0002 of PMC 0 R0160 D0004 of PMC 64 64 D0006 of PMC 0
Item IP ADDRESS NODE NAME AREA1 ADDR AREA1 SIZE AREA2 ADDR AREA2 SIZE TOKEN WATCH MIN FRAME OWN STATUS ENTRY NODE AREA1 DO/DI: ALLOCATION ADDRESS SIZE AREA2 DO: ALLOCATION SIZE
- 101 -
OPERATION
B-63434EN/02
Table 3-3 Parameters of Node No. 30 (CRT/MDI) Item Setting Item Setting IP ADDRESS 192.168.250.30 AREA2 DI: NODE NAME NODE#30 ALLOCATION R0300 AREA1 ADDR 24 ALLOC PTR D0000 AREA1 SIZE 4 CHANGE FLG R0299 AREA2 ADDR 160 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 10 AREA2 DO: D0002 of PMC 0 ALLOCATION R0160 D0004 of PMC 64 SIZE 64 D0006 of PMC 0 Table 3-4 Item No.30000 No.30001 No.30002 No.30003 No.30010 No.30011 No.30012 No.30013 No.30014 No.30015 No.30016 No.30017 No.30018 No.30019 No.30020 No.30021 No.30022 No.30023 No.30024 No.30025 No.30026 No.30027 30 250 168 192 78 79 68 69 35 51 48 0 0 0 24 4 160 64 50 10 124 128 Parameters of Node No. 30 (DPL/MDI) Setting Item Setting No.30030 100 No.30031 16 No.30032 12 No.30033 160 No.30034 64 No.30035 300 No.30036 0 No.30037 299 No.30040 450 No.30041 20 No.30042 0 No.30043 0 No.30050 0 No.30051 0 No.30055 82 No.30056 82 No.30060 82 No.30061 82 D0000 of PMC 10 D0002 of PMC 0 D0004 of PMC 64 D0006 of PMC 0
- 102 -
B-63434EN/02
OPERATION
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 R0000 R0000 Node No. 20 R0000 Node No. 30
R0100 R0108 R0116
#10 Area 1 #20 #30
R0100 R0108 R0116
#10 Area 1 #20 #30
R0100 R0108 R0116
#10 Area 1 #20 #30
R0160
Area 2 DO
R0160
Area 2 DO
R0160
Area 2 DO
R0304
Area 2 DI
R0304
Area 2 DI
R0304
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
INSTALLATION
This chapter provides information required for installation of the FLnet 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 Ordering code Board drawing number Applicable model FL-net board A02B-0265-J272 A20B-8100-0530
FANUC 16i/160i-TA (stand-alone type) 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 Ordering code Board drawing number Applicable model Heat dissipation FL-net board A02B-0259-J272 A20B-8100-0530 FANUC Power Mate i-MODEL D/H 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
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.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 FL-net board
Transceiver
Max. 100m
10BASE5 trunk cable
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 -
CONNECTION
B-63434EN/02
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 -
B-63434EN/02
CONNECTION
2.3
Pin Allocation of the 10BASE-T Connector (CD38N)

CD38N
Pin No. 1 2 3 4 5 6 7 8 Signal TX+ TXRX+ Meaning Transmission + Transmission Reception + Not used Not used Reception Not used Not used
RX-
- 113 -
CONNECTION
B-63434EN/02
2.4
2.4.1
Twisted Pair Cable Specifications

Cable connection
Referring to the operators 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 CD38N Media converter or hub RJ-45 modular connector
1 2 3 4 5 6 7 8
TX+ TXRX+
RXMAX.100m
1 2 3 4 5 6 7 8
TX+ TXRX+
RX-
TX+ TXRX+ RX-
(1) (2) (3) (6)
(1) (2) (3) (6)
TX+ TXRX+ RX-
Shield
The cable must not be longer than 100 m. cable unnecessarily.
Do not extend the
- 114 -
B-63434EN/02
CONNECTION
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 CD38N Media converter or hub RJ-45 modular connector
1 2 3 4 5 6 7 8
TX+ TXRX+
RXMAX.100m
1 2 3 4 5 6 7 8
TX+ TXRX+
RX-
TX+ TXRX+ RX-
(1) (2) (3) (6)
(3) (6) (1) (2)
TX+ TXRX+ RX-
Shield
The cable must not be longer than 100 m. cable unnecessarily.
Do not extend the
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 -
CONNECTION
B-63434EN/02
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 The Furukawa Electric Co., Ltd. Nissei Electric Co., Ltd. Specification DTS5087C-4P F-4PFWMF Remarks Twisted wire Solid wire
Contact point
Manufacturer name Contact point 2-6-1 Marunouchi Chiyoda Ward, Tokyo, 100-8233 Sales Division, the TEL: 03-3286-3126 FAX: 03-3286-3979 Furukawa Electric Co., Ltd. Remarks Tamachi Office, Nissei Electric Co., Ltd. Contact point for overseas sales MU Building 3F, 1-9-1 Minaminaruse, Machida City, Tokyo 194-0045 TEL: 0427-29-2531 FAX: 0427-29-3375 IWATANI International Corporation Tokyo Head Office 21-8 NISHI-SHINBASHI 3-CHOME, MINATO-KU, TOKYO, 105-8458, JAPAN TEL03-5405-5810 FAX03-5405-5666 Telex2524256 IWATYO J A processed cable with the both terminal connector is provided.
Remarks
NOTE The recommended standard cables cannot be used with movable parts.
Recommended cable (For movable parts)
Manufacturer name Oki Electric Cable Co., Ltd. Specification AWG26 4P TPMC-C5-F(SB) Remarks FANUC-specific cable
#1( -A&%*%&#%)- :
-A&%*%& &#1( ) &)&)+; +#/%. =$1+C 55,,,, ! #=*#&=++C @% (&+%&
#1(
) ' Nagano Sales Office TEL: ,55!4 A&%*%&#%) (&+%& &0#+#&+%-%&-C
)*)+$ ) 6 !5 &#.)+%- #' ! )+ +#-)- +(#' ) #=#%) A+*)+$#& 0 '%-#& ) 0 0=1 $=- 1 !, $ )+ -0)++ +=&=+C
)$$) -0%(' &#1( :1+#%'' -0%('; +#% /%+ A+)?%''
- 116 -
B-63434EN/02
CONNECTION
0 &)'=&)+ %- 5 ##(' &)AA+ -+#'' /%+ 0 -0#0 0%&@-- %- , $$ 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 -
CONNECTION
B-63434EN/02
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 5-569530-3 MS8-RSZT-EMC 5-569552-3 TM11AP-88P Manufacturer AMP Japan, Ltd. SK KOHKI Co., Ltd. AMP Japan, Ltd. Hirose Electric Co., Ltd. Remarks Special tool required Special tool required
For solid wire For solid wire For twisted wire For twisted wire
For movable parts For cable AWG26 4P TPMC-C5-F(SB)
Specification
:,;
Manufacturer Hirose Electric Co., Ltd.
Remarks (Note)
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 -
B-63434EN/02
CONNECTION
2.4.4
Hub
Recommended hub
Manufacturer name Contec Co., Ltd. Specification RT-1008H Remarks 10BASE-T Eight ports
This hub is not for FA. Contact points

Manufacturer name Contec Co., Ltd. East Branch
Use the hub in a dust-proof cabinet.
Contact point Tachibana Annex Building, 2-25-14 Kameido, Koto Ward, Tokyo, 136-0071 TEL: 03-5628-0211 (pilot number) FAX: 03-5628-0210 Orchid Building, 2-38-2 Meieki, Nakamura Ward, Nagoya City, 450-0002 TEL: 052-564-7821 (pilot number) FAX: 052-564-7826 3-9-31 Himesato, Nishiyodogawa Ward, Osaka City, 555-0025 TEL: 06-6472-0265 (pilot number) FAX: 06-6478-1031 http://www.contec.co.jp/
Central Branch
West Branch
Remarks
- 119 -
CONNECTION
B-63434EN/02
2.5
2.5.1
Noise Protection
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 -
B-63434EN/02
CONNECTION
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 -
CONNECTION
B-63434EN/02
!! $$ $#2
$$
5$$
$$
Outline Drawing of the Clamp Ordering code of the clamp: A02B-0124-K001 (8 clamps)
- 122 -
B-63434EN/02
CONNECTION
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(
:) ; +-)#( &)$A=+6 +=@ -%' &#1( 73
%R'2 3)`ÌHE%2 S)1

&#1(
I'952F9@I3'`@2@5F%( 1H4C"f 9%(('95F%( @9SF('3H35'03F&'
#&0% :) ;
#&0%
#&0%
:) ;
:) ;
Large network
+-)#( &)$A=+
:) ; +-)#( &)$A=+6 +=@ -%'
73
%R'2 3)`ÌHE%2 S)1
I'952F9@I3'`@2@5F%( 1H4C"f 9%(('95F%( @9SF('3H35'03F&'
&#1(
#&0% :) ;
Small network
- 123 -
CONNECTION
B-63434EN/02
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 +)=' /%+ )* 0 A+-)#( &)$A=+6+=@ -%'
#&0% +)=' /%+ )* 0 $#&0% -%' +)='%. A)%
When only one grounding point is available
- 124 -
V. MAINTENANCE
B-63434EN/02
MAINTENANCE
1.HARDWARE
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 LSI
Custom LSI
MPU TM1
CD38N
Name FL-net board
PCB drawing number A20B-8100-0530
Remarks
- 128 -
B-63434EN/02
MAINTENANCE
1.HARDWARE
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 : Blinking : : Turned off Dont care
CD38N
(COL)(RED) (LIL)(GREEN)
5(COM)(GREEN)
B(HER)(RED)
4(POK)(GREEN)
3(LNK)(GREEN)
1(ROS)(GREEN)
2(RES)(GREEN)
Note)
The face plate is represented by dotted lines.
LED indication transition at power-on (ROS, RES, LNK, POK)

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

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

No. LED indication 1 COM 2 LIL 3 COL Communication status Turned on when data is transmitted or received Turned on when the connection with the hub is normal 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 -
B-63434EN/02
MAINTENANCE
1.HARDWARE
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 LONG SHORT 43 21 43 21
No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Board state Reset exception General machine check exception Data Storage Instruction Storage Alignment Program Floating Point Unavailable Decrementer Trace Floating Point Assist Implementation Dependent Software Emulation Implementation Dependent Instruction TLB Miss Implementation Dependent Data TLB Miss Implementation Dependent Instruction TLB Error Implementation Dependent Data TLB Error Implementation Dependent Data Breakpoint Implementation Dependent Instruction Breakpoint Implementation Dependent Peripheral Breakpoint Implementation Dependent Non Maskable Development DRAM Parity Alarm Other NMI Invalid interrupt
Note) If any of these errors occurs, contact FANUC.
LED indication when an error occurs (HER)

No. LED indication 1 HER Board state A parity error occurred in the main memory.
- 131 -
1.HARDWARE
MAINTENANCE
B-63434EN/02
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=1 4
#1( &(#$A%. #' -0%(' A+)&--%. 4

#1( &)&%)
#1( /%+ 4,
)$$) $)+"
)$$) $)+"

)&%) ) 0+ ! +#
"&(%& +#-$%--%) +#
"&(%& +#-$%--%) 7

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

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

! 4
--#. +#-$%--%)
(% =&%) 4 --#. +#-$%--%) +?+ =&%)

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

)*%.=+#%) 8

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

+#
+?+ =&%) )* +#-$%%. # --#. /%0

)*%+$#%) %. )* #+#$+- %. % ,5

?+?%/ ,

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

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

9%+=#( #''+-- -A#& #(()&#%) !

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

0# - 0 )+' 1()&@ +#' )+' 1()&@ /+% !

+%- 5i6i6i
%
EUROPEAN HEADQUARTERS GRAND-DUCH DE LUXEMBOURG GE Fanuc Automation Europe S.A. Zone Industrielle L-6468 Echternach (+352) 727979 - 1 (+352) 727979 214
www.gefanuceur.com
CZECH REPUBLIC GE Fanuc Automation CR s.r.o. U studanky 3 CZ-170 00 Praha 7 (+420) 2 333 72 502 (CNC) (+420) 2 333 72 503 (PLC) (+420) 2 333 70 821
BELGIUM / NETHERLANDS GE Fanuc Automation Europe S.A. - Netherlands Branch Postbus 7230 - NL-4800 GE Breda Minervum 1603A - NL-4817 ZL Breda (+31) 76-5783 201 (CNC) (+31) 76-5783 212 (PLC) (+31) 76-5870 181
www.gefanuc.nl
FRANCE GE Fanuc Automation France S.A. 39, rue du Saule Trapu, BP 219 F-91882 Massy Cedex (+33) 1 69 75 86 39 (CNC) (+33) 1 69 75 86 20 (PLC) (+33) 1 69 75 86 49
www.gefanuc.cz
GERMANY GE Fanuc Automation GmbH Bernhuser Strae 22 D-73765 Neuhausen a.d.F (+49) 7158 187 400 (+49) 7158 187 455 (CNC) (+49) 7158 187 466 (PLC)
www.gefanuc.fr
GERMANY GE Fanuc Eberle Automation GmbH Ernst-Weyden-Str. 7 D-51105 Kln (Cologne) (+49) 221-83904-53 (+49) 221-83904-55
www.gefanuc.de
GERMANY GE Fanuc Automation GmbH Obere Hauptstr. 72 D-09244 Lichtenau (+49) 37208 695 20(CNC) (+49) 37208 695 30 (PLC) (+49) 37208 695 55
www.gefanuc.de
GERMANY GE Fanuc Automation GmbH Elberfelderstr. 45 D-40724 Hilden (+49) 2103 247410 (Laser/CNC) (+49) 2103 247420 (Laser/CNC)
www.gefanuc.de
GERMANY GE Fanuc Automation Deutschland GmbH Bensheimer Str. 61 D-65428 Rsselsheim (+49) 6142 357600 (+49) 6142 357611
www.gefanuc.de
GERMANY GE Fanuc Eberle Automation GmbH Sdwestpark 48 D-90449 Nrnberg (+49) 911 9672 100 (PLC) (+49) 911 9672 200 (PLC)
www.gefanuc.de
GERMANY GE Fanuc Eberle Automation GmbH Reichenbergerstr. 6 D-33605 Bielefeld (+49) 521 92445 0 (PLC) (+49) 521 92445 30 (PLC)
www.gefanuc.de
SWEDEN GE Fanuc Automation Nordic AB Hammarbacken 4 S-19149 Sollentuna (+46) 8 444 5520 (+46) 8 444 5521
www.gefanuc.de
ITALY GE Fanuc Automation Italia S.r.l. Piazza Tirana 24/4B I-20147 Milano (+39) 02 413 81 41 (CNC) (+39) 02 419 669 (CNC)
www.gefanuc.se
ITALY GE Power Controls Italia S.p.a Via Tortona 27 I-20144 Milano (+39) 02 4242 280 (PLC) (+39) 02 4242 511 (PLC)
www.gefanuc.it
SPAIN GE Fanuc Automation Espaa S.A. Polgono Industrial Olaso Calle Olaso, 57 - Locales 10 y 11 E-20870 Elgoibar (+34) 943 74 82 90 (CNC) (+34) 943 74 44 21 (CNC)
www.gefanuc.it
SPAIN GE Power Controls Ibrica S.L. Calle Marqus de Comillas, 1 E-08225 Terrassa (Barcelona) (+34) 93 736 58 28 (PLC) (+34) 93 788 24 03 (PLC)
www.gefanuc.es
UNITED KINGDOM GE Fanuc Automation (UK) Ltd. Unit 1 - Mill Square Featherstone Road Wolverton Mill South Milton Keynes MK12 5BZ (+44) 1908 84 4000 (+44) 1908 84 4001
www.gefanuc.es
SWITZERLAND GE Fanuc Automation Filiale Suisse/Niederlassung Schweiz Erlenstrasse 35a CH-2555 Brgg b. Biel (+41) 32 366 63 63 (CNC) (+41) 32 366 63 33 (PLC) (+41) 32 366 63 64 (CNC) (+41) 32 366 63 34 (PLC)
www.gefanuceur.co.uk
02/01
www.gefanuc.ch
Printed at GE Fanuc Automation S.A. , Luxembourg
Modification of FANUC FL-net Board
OPERATORS MANUAL
1.Type of applied technical documents Name Spec.No./Ed. FANUC FL-net Board OPERATORS MANUAL B-63434EN/02
2.Summary of Change Group Name/Outline New Add Correct Delete Add Applicable Date Immediately
Basic Function Optional Function
The following parameter and screen are added. - Byte-swap parameter - Error message screen
Unit Maintenance Parts
Notice Modification of Page 3,4,19,23,26,29,40,62,66,67,69,70,75,87 and 91. Correction (Explanations for the additional function are included in the above.)
Another
TITLE Modification of FANUC FL-net Board OPERATORS MANUAL
01
EDIT
02.05.20
DATE
Mutai DESIGN
First
issue
DRAW.NO.
B-63434EN/02-1
SHEET
DESCRIPTION
FANUC LTD.
1/17
The additional information of FANUC FL-net Board OPERATORS MANUAL
Addition of Stand-alone type FANUC Series 16i/18i/21i-TB/MB to the table of Page 3
Applicable models
Model Stand-alone type FANUC Series 16i/160i -TA Stand-alone type FANUC Series 16i/160i -MA Stand-alone type FANUC Series 16i/160i -TB Stand-alone type FANUC Series 16i/160i -MB Stand-alone type FANUC Series 18i/180i -TA Stand-alone type FANUC Series 18i/180i -MA Stand-alone type FANUC Series 18i/180i -TB Stand-alone type FANUC Series 18i/180i -MB Stand-alone type FANUC Series 21i/210i -TA Stand-alone type FANUC Series 21i/210i -MA Stand-alone type FANUC Series 21i/210i -TB Stand-alone type FANUC Series 21i/210i -MB FANUC Power Mate i-MODEL D FANUC Power Mate i-MODEL H Abbreviation 16i-TA Series 16i-A 16i-MA 16i-TB Series 16i-B 16i-MB 18i-TA Series 18i-A 18i-MA 18i-TB Series 18i-B 18i-MB 21i-TA Series 21i-A 21i-MA 21i-TB Series 21i-B 21i-MB Power Mate i-D Power Mate i Power Mate i-H
16i
18i
21i
PMi
Addition of the following table to Page 4
Related manuals
Manual related to FANUC Series 16i/18i-TB/MB Manual name Descriptions Connection Manual(Hardware) Connection Manual(Functions) Operators Manual(For Lathes) Operators Manual(For Milling Centers) Maintenance Manual Parameter Manual Specification number B-63522EN B-63523EN B-63523EN-1 B-63524EN B-63534EN B-63525EN B-63530EN
01
EDIT
02.05.20
DATE
Mutai DESIGN
First
issue
DRAW.NO.
B-63434EN/02-1
SHEET
DESCRIPTION
FANUC LTD.
2/17
Manuals related to FANUC Series 21i-TB/MB Manual name Descriptions Connection Manual(Hardware) Connection Manual(Functions) Operators Manual(For Lathes) Operators Manual(For Milling Centers) Maintenance Manual Parameter Manual Specification number B-63522EN B-63523EN B-63523EN-1 B-63604EN B-63614EN B-63525EN B-63610EN
Addition of the following Item 5 to NOTE of Page 19.

NOTE 5 When changing the node number to a new one with using the method of 2.2.2.1.Dynamic DI data allocation of common memory area 2, the status of its node is indicated at the place corresponding to its node number. But, if the new node is not participating in FL-net network, the DI data of the old node remain because the DI data from the new node can not be received. When the new node participates in the network, the new DI data are copied to the corresponding DI area.
Addition of Unavailable communication detection flag to FA link layer state of Page 23

FA link layer state: 7 +1 6 5 4 3 2 1 0
(Reserved)
Node participation flag (1: Participate) Unavailable communication detection flag (1: Detection) Upper layer operation signal error flag (1: Error) Common memory data valid flag (1: Valid) Common memory setting complete flag (1: Complete) Duplicate address detection flag (1: Duplicate address detected)
01
EDIT
02.05.20
DATE
Mutai DESIGN
First
issue
DRAW.NO.
B-63434EN/02-1
SHEET
DESCRIPTION
FANUC LTD.
3/17
Addition of Unavailable communication detection flag to FA link state of Page 26

FA link state: 7 +1 6 5 4 3 2 1 0
(Reserved)
Node participation flag (1: Participate) Unavailable communication detection flag (1: Detection) Upper layer operation signal error flag (1: Error) Common memory data valid flag (1: Valid) Common memory setting complete flag (1: Complete) Duplicate address detection flag (1: Duplicate address detected) Table 2-2 FA Link State Item Node participation flag Description Indicates whether the node participates in the network (1) or is disconnected from the network (0). Unavailable communication detection flag (NOTE) Upper layer operation signal error flag Common memory data valid flag Common memory setting complete flag Set when cyclic data is valid, in other words, when PMC area allocation is normal. Set when node common memory setting is complete, in other words, when the parameters related to the common memory setting (Pa11, Pa12, Pa13 and Pa14) are valid. Duplicate address detection flag Set when a common memory setting for 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) Set when detecting the node of a different token mode and when communication is unavailable. Currently, not supported.
NOTE This flag is available for the edition 4 or later of FL-net control software (656C series)
01
EDIT
02.05.20
DATE
Mutai DESIGN
First
issue
DRAW.NO.
B-63434EN/02-1
SHEET
DESCRIPTION
FANUC LTD.
4/17
Replacement of 2.4. Byte List of Cyclic Data of Page 29
2.4
Byte List of Cyclic Data

The interrelation among the byte lists in a common memory, the PMC area, and FL-net network is described as follows.
FL-net network / Common memory / PMC area

On FL-net network
7 0
Common memory
15 0
PMC area
7 0
+00 +01 +02 +03
12H 34H 56H 78H
+00 +01
3412H 7856H
+00 +01 +02 +03
34H 12H 78H 56H
By setting the bit 0 of the FL-net parameter OPTION1 to 1, a byte list is swapped as follows. On FL-net network
7 0
Common memory
15 0
PMC area
7 0
+00 +01 +02 +03
12H 34H 56H 78H
+00 +01
3412H 7856H
+00 +01 +02 +03
12H 34H 56H 78H
NOTE 3 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. 4 The OPTION1 parameter is available when Communication setting software (654I series) is edition 04 or later and when FL-net control software (6564 series / 656C series ) is edition 07 / 01 or later.
01
EDIT
02.05.20
DATE
Mutai DESIGN
First
issue
DRAW.NO.
B-63434EN/02-1
SHEET
DESCRIPTION
FANUC LTD.
5/17
Addition of the following item 3 to NOTE of Page 40

NOTE 3 When receiving the response message before receiving the ACK frame as the acknowledgement of a request message, Request status(R_STS) may not become 01h.
Replacement of 3.8. Byte List of Message Data of Page 62
3.8
Byte List of Message Data

The interrelation among the byte lists in a virtual address space, the PMC area, and FL-net network is described as follows
Byte block data

On FL-net network
7 0
Virtual address
7 0
PMC area
7 0
+00 +01 +02 +03
12H 34H 56H 78H
+00 +01 +02 +03
12H 34H 56H 78H
+00 +01 +02 +03
12H 34H 56H 78H
7 0
Virtual address s
7 0
PMC area
7 0
+00 +01 +02 +03
12H 34H 56H 78H
+00 +01 +02 +03
12H 34H 56H 78H
+00 +01 +02 +03
34H 12H 78H 56H
NOTE The OPTION1 parameter is available when Communication setting software (654I series) is edition 04 or later and when FL-net control software (6564 series / 656C series ) is edition 07 / 01 or later
01
EDIT
02.05.20
DATE
Mutai DESIGN
First
issue
DRAW.NO.
B-63434EN/02-1
SHEET
DESCRIPTION
FANUC LTD.
6/17
Word block data Transparent data

On FL-net network
7 0
Virtual address
15 0
PMC area
7 0
+00 +01 +02 +03
12H 34H 56H 78H
+00 +01
3412H 7856H
+00 +01 +02 +03
34H 12H 78H 56H
7 0
Virtual address
15 0
PMC area
7 0
+00 +01 +02 +03
12H 34H 56H 78H
+00 +01
3412H 7856H
+00 +01 +02 +03
12H 34H 56H 78H
NOTE 1 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. 2 The OPTION1 parameter is available when Communication setting software (654I series) is edition 04 or later and when FL-net control software (6564 series / 656C series ) is edition 07 / 01 or later.
01
EDIT
02.05.20
DATE
Mutai DESIGN
First
issue
DRAW.NO.
B-63434EN/02-1
SHEET
DESCRIPTION
FANUC LTD.
7/17
Addition of (6) Option parameter to Page 66 as follows
1.1
Overview
The parameters for FL-net function are divided into five major groups: (1) Basic parameters (2) State monitoring parameters (3) Area 1 allocation parameters (4) Area 2 allocation parameters (5) Message allocation parameters (6) Option parameters

(6) Option parameters Table 1-6 Option parameters Parameter name Option 1 Option 2 Description FL-net option parameter (Reserved) Index number Pa60 Pa61
NOTE The OPTION 1 parameter is available when Communication setting software (654I series) is edition 04 or later and when FL-net control software (6564 series / 656C series ) is edition 07 / 01 or later.
01
EDIT
02.05.20
DATE
Mutai DESIGN
First
issue
DRAW.NO.
B-63434EN/02-1
SHEET
DESCRIPTION
FANUC LTD.
8/17
Addition of the explanation about [ERRMSG] to Page 69

(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 LED) 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] 2) [NODE] 3) [NETWRK] 4) [LOG] 5) [ERRMSG] : Parameter setting screen for using the FL-net function : Monitor screen of Participating Node Management Table : Monitor screen of the FL-net network parameters : Monitor screen of the log of the local node : Error message screen for FL-net
01
EDIT
02.05.20
DATE
Mutai DESIGN
First
issue
DRAW.NO.
B-63434EN/02-1
SHEET
DESCRIPTION
FANUC LTD.
9/17
Replacement of Screen 1-2 of Page 70
Screen 1-2 FL-net Parameter Setting Screen (for the 10.4 LCD)
01
EDIT
02.05.20
DATE
Mutai DESIGN
First
issue
DRAW.NO.
B-63434EN/02-1
SHEET
DESCRIPTION
FANUC LTD.
10/17
Option parameters
Table 1-12 Option parameters Item OPTION1 Bit parameters Bit 0 : When setting 1, Cyclic data is byte-swapped. Bit 1 : When setting 1, Word block data and Transparent data of the message are byte-swapped. Bit 2 : When setting 1, Byte block data of the message is byte-swapped. Other bits are not used. Please set 0. Pa60 OPTION2 Pa61 OPTION 2 is not used at present. Please set 0. Description
NOTE The OPTION 1 parameter is available when Communication setting software (654I series) is edition 04 or later and when FL-net control software (6564 series / 656C series ) is edition 07 / 01 or later.
01
EDIT
02.05.20
DATE
Mutai DESIGN
First
issue
DRAW.NO.
B-63434EN/02-1
SHEET
DESCRIPTION
FANUC LTD.
11/17
Modification of Screen 2-3 of Page 87 as follows
Screen 2-3 FL-net Network Management Table Screen (10.4 LCD) (4) The above information can be cleared by pressing the [CLEAR] soft key.
01
EDIT
02.05.20
DATE
Mutai DESIGN
First
issue
DRAW.NO.
B-63434EN/02-1
SHEET
DESCRIPTION
FANUC LTD.
12/17
Insertion of the following new chapter after Chapter 2.3
2.4
Procedure
Error message
When a error occurs at the local node, the error of its error is displayed at the Error message screen. (1) Press function key
, then press soft key [PMC] to switch to the PMC screen.
SYSTEM
(2) Press soft keys [PMCDGN], [I/OCHK], and [FL-NET] in this order. Then screen 1-1 appears. (3) Press soft key [ ERRMSG ] of screen 1-1, and the screen 2-6 shown below appears.
Screen 2-6 FL-net Error Message Screen (for the 10.4 LCD) An error message and the date/time at which its error occurred is displayed. The format of date and time is Year/Month/Date Hour:Minute:Second. As for the explanation of error messages, please refer to 2.4.1 Error Message . NOTE This error message screen is available when Communication setting software (654I series) is edition 04 or later and when FL-net control software (6564 series / 656C series ) is edition 07 / 01 or later.
01
EDIT
02.05.20
DATE
Mutai DESIGN
First
issue
DRAW.NO.
B-63434EN/02-1
SHEET
DESCRIPTION
FANUC LTD.
13/17
2.4.1
Contents of Error messages
Error messages which are displayed when the communication is not available
When the communication is not available at all, the following error messages are displayed. Please correct the problem parameter, and then power off and on CNC.
NODE(???) CONFLICT
The local node number is being duplicated with the other one. Please check the Pa10 parameter to avoid the duplication of a node number.
OWN NODE(???) IS INVALID

The node number (???) of the local node is not within the range of 1-254. Please check the Pa10 parameter.
IP ADDRESS(????????H) IS INVALID
The specified IP address (????????H) is not within the range of Class C of IP address type. Please check the Pa10 parameter.
TOKEN WATCH(???) IS INVALID

Token monitoring time (???) is out of range. Please check the Pa15 parameter.
MINIMUM FRAME(??) IS INVALID

Allowable minimum frame interval (??) is out of range. Please check the Pa16 parameter.
AREA1 ADDRESS(???H) IS INVALID

Start address of area1 is not within the range of 0-511. Please check the Pa11 parameter.
AREA1(???H, ???H) IS INVALID

The specified common memory area1 is out of range. The sum of (Start address of area1 + Size of area1) should be within 0-512 words. Please check the Pa11 and Pa12 parameters.
AREA2 ADDRESS(????H) IS INVALID

Start address of area2 is not within the range of 0-8191. Please check the Pa13 parameter.
AREA2(????H, ????H) IS INVALID

The specified common memory area2 is out of range. The sum of (Start address of area2 + Size of area2) should be within 0-8192 words. Please check the Pa13 and Pa14 parameters.
NODE(???) TOKEN MODE IS NOT SAME

The node number (???) is behaving as Version 1.00 of FL-net specifications and this local node can not communicate with the problem node(???). Please change the problem node from Version 1.00 into Version 2.00.
01
EDIT
02.05.20
DATE
Mutai DESIGN
First
issue
DRAW.NO.
B-63434EN/02-1
SHEET
DESCRIPTION
FANUC LTD.
14/17
Error messages which are displayed when data exchange fails

When the cyclic data can not be exchanged or the message data can not be transferred, the following error messages are displayed. In that case, please check the parameters written in each explanation.
ADDRESS(????, ????) OVERLAPPING

The local common area (area1 and area2) overlaps with the other node. In that case, DO data of the local node is not sent. Please check the Pa11, Pa12, Pa13, and Pa14 parameters.
OWN NODE STATUS IS OUT OF RANGE

Local node information address is invalid. In that case, the information is not copied into the specified PMC address. Please check the Pa20 parameter. An even address should be configured. The specified address should be within PMC R address.
ENTRY NODE STATUS IS OUT OF RANGE

Participating node information address is invalid. In that case, the information is not copied into the specified PMC address. Please check the Pa21 parameter. An even address should be configured. The specified address should be within PMC R address.
INVALID DYNAMIC CHANGE FLAG

Switch flag allocation address is invalid. In that case, the dynamic switch of the area2 can not be performed. Please check the Pa44 parameter.
INVALID PARAMETER (COMMON MEMORY AREA1)

The allocation address of common memory area1 is invalid. In that case, the cyclic data of area1 is not copied into the specified PMC address. Please check the Pa30 parameter. An even address should be configured to Pa30. The specified address should be within PMC R address. The sum of Pa31 and Pa32 should be within the range 0-512 of area1.
NODE NUMBER(???) IS INVALID

The node number of Information on other nodes of area2 is not within the range of 1-254. In that case, the Information on other nodes is not copied into the prescribed PMC address. Please confirm that a ladder program writes a node number of 1-254 to PMC R address specified by Pa43.
INVALID DI PARAMETER (COMMON MEMORY AREA2)

The Allocation address of area2 DI data is invalid. In that case, the area2 data is not copied into the specified PMC address. Please check the Pa43 parameter.
01
EDIT
02.05.20
DATE
Mutai DESIGN
First
issue
DRAW.NO.
B-63434EN/02-1
SHEET
DESCRIPTION
FANUC LTD.
15/17
AREA2 DI SIZE IS OUT OF RANGE

DI area of area2 is out of the range of PMC address. In that case, DI data is not copied into the specified PMC address. When intending to configure with Static DI data allocation of area2, the sum of (Pa42+(Pa44 * 2 )+4) should be within the range of PMC address. When intending to configure with Dynamic DI allocation of area2, the sum of (Pa42+(Data size of Pa43 * 2)+ 4) should be within the range of PMC address.
INVALID DO PARAMETER (COMMON MEMORY AREA2)

The Allocation address of area2 DO data is invalid. In that case, the DO data of the specified PMC address is not copied into common memory area2. Please check the Pa40 and Pa41 parameters. An even address should be configured to Pa40. The specified address should be within PMC R address. The sum of (Pa40+(Pa41 * 2 )) should be within the range of PMC address.
INVALID DO OFFSET
The specified DO offset is out of the range of area2 for the local node. In that case, the DO data of the specified PMC address is not copied into common memory area2. Please confirm that the sum of Pa14. (Pa41+ DO offset of Pa43) is smaller than the size of
INVALID MESSAGE INTERFACE(SEND MSG)

The interface allocation address or size is invalid. In that case, a message can not be sent. Please check the Pa50 and Pa51 parameters. An even address should be configured to Pa50. The size of Pa51 should be 20 bytes or larger. The sum of (Pa50+Pa51) should be within the range of PMC address.
INVALID MESSAGE INTERFACE(RECV MSG)

The allocation address or size for receiving Transparent message is invalid. In that case, a message can not be received. Please check the Pa52 and Pa53 parameters. An even address should be configured to Pa52. The size of Pa53 should be 8 bytes or larger. The sum of (Pa52+Pa53) should be within the range of PMC address.
01
EDIT
02.05.20
DATE
Mutai DESIGN
First
issue
DRAW.NO.
B-63434EN/02-1
SHEET
DESCRIPTION
FANUC LTD.
16/17
Other error message NODE(???) OUT-RING

The node number (???) is dropped from the network.
DROPPED PACKET(???->???)
Because the reception buffer is full, the data of the node number(???->???) can not be received. Please set the larger value into Pa16.
TOKEN IS DUPLICATED(???)
Because the node number (???) sent the token though this local node possesses the token, this local node dropped its own token. Please set the larger value into Pa15 of the node number (???).
TOKEN HOLDING TIME IS UP

Because token monitoring time expired, this local node dropped its possessing token. Please set the larger value into Pa15 of this local node.
IP CHECK-SUM ERROR
The checksum of IP layer of the received data is not correct. FL-net data may be sometimes destroyed by the reason that noise or something influences the FL-net network. Please check the ground of the devices etc.
SEND BUFFER IS FULL

Because the transmission buffer is full, data can not be sent. The transmission error may be often occurring by the reason of noise or something. Please check the ground of the devices etc.
SEND ERROR(????H)
The error (????H) occurred when data is just sent. The transmission error may be often occurring by the reason of noise or something. Please check the electric ground of the devices etc.
RECEIVE ERROR(????H)
The error (????H) occurred when data is just received. The transmission error may be often occurring by the reason of noise or something. Please check the electric ground of the devices etc.
Addition of the following note into Page 97
NOTE The error message can not be displayed in the DPL screen.
01
EDIT
02.05.20
DATE
Mutai DESIGN
First
issue
DRAW.NO.
B-63434EN/02-1
SHEET
DESCRIPTION
FANUC LTD.
17/17
FANUC FL-net Board OPERATORS MANUAL

1.Type of applied technical documents
Name

B-63434EN/02
Spec.No./Ed.
2.Summary of Change New, Add, Correct, Delete Correct
Group
Name/Outline Addition of the setting method of address mapping for PMC-SD7
Applicable Date Immediately
Basic Optional Function Unit Maintenance Parts Notice Correction Another
Title
Draw
No.
Ed. Date Date Design Description Apprv.
B-63434EN/02-3
Sheet 1/9
Dec.15.2004 Desig. Y.Honda
Add the following explanation as Chapter 4 into the OPERATION part.
SETTING METHOD FOR PMC-SD7

This chapter describes the setting method when PMC-SD7 is used. NOTE 1 When PMC-SD7 is used, Communication setting software 654I series must be Edition 08 or later. 2 When using PMC-SD7, the setting method of PMC address is different from other PMC. About other settings, refer to Section 1.2 Setting of Parameters.
Title
Draw
No.
B-63434EN/02-3
Sheet 2/9
4.1
PMC ADDRESS SETTING FOR PMC-SD7

The method of PMC address setting is described below when using PMC-SD7.
Screen 4-1 FL-net Parameter Setting Screen (for the 10.4 LCD)
When using PMC-SD7, the following parameters are different from them of other PMC.
Table 4-1 PMC address related to PMC-SD7
Item OWN STATUS Description The available PMC address is %M. The available range is from 1 to 63985. But the following condition has to be satisfied. Condition) (16*n)+1 [n=from 0 to 3999] Examples) M1, M17, M63985 ENTRY NODE The available PMC address is %M. The available range is from 1 to 63985. But the following condition has to be satisfied. Condition) (16*n)+1 [n=from 0 to 3999] Examples) M1, M17, M63985 AREA1 DO/DI : ALLOCATION The available PMC address is %M. The available range is from 1 to 63985. But the following condition has to be satisfied. Condition) (16*n)+1 [n=from 0 to 3999] Examples) M1, M17, M63985
Title
Draw
No.
B-63434EN/02-3
Sheet 3/9
AREA2 DO : ALLOCATION
The available PMC address is %M and %R. In case of %M, the available range is from 1 to 63985. But the following condition has to be satisfied. Condition) (16*n)+1 [n=from 0 to 3999] In case of %R, the available range is from 1 to 5000. Examples) M1, M17, M63985, R1, R2, R5000
AREA2 DI : ALLOCATION
AREA2 DI : ALLOC PTR
The available PMC address is %R. The available range is from 1 to 5000. Examples) R1, R2, R5000
AREA2 DI : CHANGE FLG
The available PMC address is %M. The available range is from 1 to 63993. But the following condition has to be satisfied. Condition) (8*n)+1 [n=from 0 to 7999] Examples) M1, M9, M63993
MESSAGE : ADDRESS
MESSAGE : RECV MSG
NOTE 1 When inputting the PMC address, it is not necessary to input %. 2 When PMC address setting is invalid, an error message INPUT INVALID is displayed.
Title
Draw
No.
B-63434EN/02-3
Sheet 4/9
4.2
4.2.1
Example of Setting
Example of Configuration
Using the example of configuration shown below, this section describes the setting of each parameter.
FL-net
Series 18i -B Node No.10
Fig. 4-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 1 0x0000 0x0010 0x0014 0x0018 0x001c 0x0090 0x00a0 0x00d0 0x01ff Node No.30 Node No.10 Node No.20 Node No.30 0x0040 0x0050 Node No.20 0x0000 Common memory area 2 Node No.10
0x1fff
Title
Draw
No.
B-63434EN/02-3
Sheet 5/9
4.2.2
Example of Parameter Settings

Assume that the address map of the PMC %M area of each node is as shown below. Then, the parameters of each node are set as indicated in Table 4-2 through Table 4-4.
PMC %M area %M00001 %M00801 %M00865 %M00929 %M00993 %M01025 %M01281 Common memory area 2 DO data %M02305 %M02393 %M02401 %M02433 %M03457 %M03601 %M03760 Common memory area 2 data Switch flag Information on other node Real data Local node information Participating node list Common memory area 1 data
Node No.10 Node No.20 Node No.30
Message transmission client
Interface Read/write buffer
%M11953
Title
Draw
No.
B-63434EN/02-3
Sheet 6/9
Table 4-2 Parameters of Node No.10

Item IP ADDRESS NODE NAME AREA1 ADDR AREA1 SIZE AREA2 ADDR AREA2 SIZE TOKEN WATCH MIN FRAME OWN STATUS ENTRY NODE AREA1 DO/DI: ALLOCATION ADDRESS SIZE AREA2 DO: ALLOCATION SIZE Setting 192.168.250.10 NODE#10 16 4 0 64 50 10 %M00993 %M01025 %M00801 16 12 %M01281 64 %R0001 of PMC %R0002 of PMC %R0003 of PMC %R0004 of PMC 20 0 64 0 Item AREA2 DI: ALLOCATION ALLOC PTR CHANGE FLG AREA2 ADDR AREA2 SIZE MESSAGE: ADDRESS SIZE RECV MSG SIZE %M02401 %R00001 %M02393 0 0 %M03601 20 %M00001 0 Setting

Title
Draw
No.
B-63434EN/02-3
Sheet 7/9

Title
Draw
No.
B-63434EN/02-3
Sheet 8/9
4.2.3
Image of Data Exchange

When data exchange is performed with the examples of configuration and parameter settings described before, the illustration below shows how the data of each node is viewed in the PMC %M area of each node.
Node No.10 %M00001 %M00801 %M00865 %M00929 %M01281 Area1 %M00001 %M00801 %M00865 %M00929 %M01281 Area1 Node No.20 %M00001 %M00801 %M00865 %M00929 %M01281 Area1 Node No.30
#10 #20 #30
#10 #20 #30
#10 #20 #30
Area2 DO
Area2 DO
Area2 DO
%M02433
Area2 DI
%M02433
Area2 DI
%M02433
Area2 DI
Moreover, a message can be transmitted using a PMC area starting at %M03601.
Title
Draw
No.
B-63434EN/02-3
Sheet 9/9

Fanuc FL-Net Boad Operator

Uploaded by

Document Information

Original Description:

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 Boad Operator

Uploaded by

Copyright:

Available Formats

GE Fanuc Automation Europe

Computer Numerical Controls

TECHNOLOGY AND MORE

GENERAL WARNINGS AND NOTES--------------------------------------------------s-3

DEFINITION OF WARNING, CAUTION, AND NOTE

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

GENERAL WARNINGS AND NOTES

              %    

               

    !

     !!

  !

3  5    5!

   54

 ,  ,4

    

  ,

About this manual

Manuals related to Series 21i-TA/MA

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

What Is the FL-net?

Features of the FL-net

Field network Devices Sensor actuator

%&' ()01'23 6BC 5% 6B7DE%20@F(5'(@(9'G

H9IF9&@5@ RF5S@5%T'( H9IF952@(30F33F%(

H9IF9 52@(30F33F%( P 0'33@Q' 52@(30F33F%(

FANUC FL-net Functions

For details of message transmission, see Chapter 3, "Message Transmission," in "Description."

Common Memory Area 1 Cyclic Transmission

+#-$% '## *+)$ )0+ )'+#-$% '## *+)$ )0+ )'-

Common Memory Area 2 Cyclic Transmission

2222<, 2222< 2222< 2222<5

%&'()01'2 %EE3'5 @5@3FW' %EE3'5 @2'@ RF59SEI@Q X@2'@

2@(30F5&@5@E2%0 %5S'2(%&'3 2@(30F5&@5@%E 5S'I%9@I(%&'

DI data allocation Dynamic DI data allocation of common memory area 2

2222<, 2222< 2222< 2222<5

%&'()01'2 %EE3'5 @5@3FW' %EE3'5 @2'@ RF59SEI@Q X@2'@

2@(30F5&@5@E2%0 %5S'2(%&'3 2@(30F5&@5@E2%0 %5S'2(%&'3 2@(30F5&@5@E2%0 %5S'2(%&'3 2@(30F5&@5@E2%0 %5S'2(%&'3

Static DI data allocation of common memory area 2

2222<, 2222< 2222< 2222<5

%&'()01'2 %EE3'5 @5@3FW' %EE3'5 @2'@ RF59SEI@Q X@2'@

2@(30F5&@5@E2%0 %5S'2(%&'3 2@(30F5&@5@E2%0 %5S'2(%&'3 2@(30F5&@5@%E 5S'I%9@I(%&' 2@(30F5&@5@E2%0 %5S'2(%&'3

FA link layer state:

!"#$#  %&&&&")"0" %&&&&#&%& '(#"""#'(#"""#"

VG S'9T3 5S@5 5S' 3RF59S EI@QF33'55%CCSA bG '2E%203&@5@`2%9'33F(QA

Node State Monitoring

Local node state:

Table 2-1 Local Node State

!"#$#  %&&&&")"0" %&&&&#&%& '(#"""#'(#"""#"

Item Node participation flag

Table 2-3 Upper Layer State

Item U_ERR_CODE U_ERR RUN/STOP

Current RCT value:

Allocation of a list of participating nodes

&! "#$!% &!1 &!2

Byte List of Cyclic Data

Common memory area 1 and the PMC area

<,, <, <, <,

 7 7 7 !57

Common memory area 2 and the PMC area

<,, <, <, <,

 7 7 7 !57

Data concurrency in long-data (4-byte-data) units

%

!

!!

!

3 5 5!

54

, ,4

,

+#-$% '## +)$ )0+ )'+#-$% '## +)$ )0+ )'-

2222<, 2222< 2222< 2222<5

%&'()01'2 %EE3'5 @5@3FW' %EE3'5 @2'@ RF59SEI@Q X@2'@

2222<, 2222< 2222< 2222<5

%&'()01'2 %EE3'5 @5@3FW' %EE3'5 @2'@ RF59SEI@Q X@2'@

2222<, 2222< 2222< 2222<5

%&'()01'2 %EE3'5 @5@3FW' %EE3'5 @2'@ RF59SEI@Q X@2'@

!"#$# %&&&&")"0" %&&&&#&%& '(#"""#'(#"""#"

!"#$# %&&&&")"0" %&&&&#&%& '(#"""#'(#"""#"

&! "#$!% &!1 &!2

<,, <, <, <,

7 7 7 !57

<,, <, <, <,

7 7 7 !57

System -A)- $--#. D=- $--#.

System --#. --#.

!"# %&#""# (! "# %& !"#

<, < < < <5 < <

)$A(%) *(#. ,,,,0

+#-#&%) &)' 5!,, ) 5!,,5 ## -%>

)$A(%) *(#. D=- -#=-

: -+?'; +#-#&%) &)' 5!, ) 5!,5 : -+?';

<,, <, <, <,

7 7 !57 7

7 7 !57 7

<,, <, <, <,

7 7 7 !57

<,, <, <, <,

7 7 7 !57