fanuc fl-net boad operator

7/28/2019 Fanuc FL-Net Boad Operator

1/168

TECHNOLOGY AND MORETECHNOLOGY AND MORETECHNOLOGY AND MORETECHNOLOGY AND MORE

GE Fanuc Automation EuropeGE Fanuc Automation EuropeGE Fanuc Automation EuropeGE Fanuc Automation Europe

FL - Net BoardFL - Net BoardFL - Net BoardFL - Net Board

B-63434EN/02B-63434EN/02B-63434EN/02B-63434EN/02

Computer Numerical ControlsComputer Numerical ControlsComputer Numerical ControlsComputer Numerical Controls

Operators ManualOperators ManualOperators ManualOperators Manual


2/168


3/168

B-63434EN/02 SAFETY PRECAUTIONS

s-1

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

SAFETY PRECAUTIONS


4/168

SAFETY PRECAUTIONS B-63434EN/02

s-2

1 DEFINITION OF WARNING, CAUTION,AND NOTEThis manual includes safety precautions for protecting the user and preventing damage to the machine.

Precautions are classified into Warning and Caution according to their bearing on safety. Also,

supplementary information is described as a Note. Read the Warning, Caution, and Note thoroughly

before attempting to use the machine.

WARNING

Applied when there is a danger of the user being injured or when there is a damage of both the user

being injured and the equipment being damaged if the approved procedure is not observed.

CAUTION

Applied when there is a danger of the equipment being damaged, if the approved

procedure is not observed.

NOTE

The Note is used to indicate supplementary information other than Warning and

Caution.

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


5/168

B-63434EN/02 SAFETY PRECAUTIONS

s-3

2 GENERAL WARNINGS AND NOTESWARNING

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 causingdamage 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.


6/168

SAFETY PRECAUTIONS B-63434EN/02

s-4

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. Whenusing 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.

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. 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 allvital data, and keep the backup copy in a safe place.


7/168

B-63434EN/02 Table of Contents

c-1

Table of Contents

!

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

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

)'-%*)+$#%)

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

!

3

4

,

!

5


8/168

Table of Contents B-63434EN/02

c-2

!

!"#$

!"#$%

$ '

$%

!

(

)

!!

*

*

!

!

+%

+ ,

)

3

5

5!

!

55

54

-i.i.i/ '

%0i/0(1.2

"

! #

"

"

4

)/+ #% 67 4

8 4 $ 44

$

,,

$ ,

9

,


9/168

B-63434EN/02 Table of Contents

c-3

,

,4

7 ,

"

,3 :;

!

"

3#

3#%

3- 2# '

,

- ,

3# ,

4%$

9

7

4


10/168

I. GENERAL


11/168

B-63434EN/02 GENERAL 1.GENERAL

- 3 -

1 GENERALThis manual consists of the following parts:

About this manualSAFETY PRECAUTIONSDescribes the precautions to be observed in reading this manual.

I. GENERAL

Describes the organization of this manual, applicable models,and related manuals.

II. DESCRIPTIONDescribes the general for using the FL-net function.

III. OPERATIONDescribes the setting and operation procedures for using the FL-

net function.

IV. CONNECTION

Describes the method of connecting each device and notes onusing the FL-net function.

V. MAINTENANCEDescribes the drawing number of the FL-net board, the meanings

of LED indications, and so forth.

Applicable modelsThis manual covers the models listed in the table below. In this

manual, the their abbreviations may be used.

Model Abbreviation

Stand-alone type FANUC Series 16i/160i-TA 16i-TA

Stand-alone type FANUC Series 16i/160i-MA 16i-MA

Series 16i-A



Series 18i-A



Series 21i-A

FANUC Power Mate i-MODEL D Power

Mate i-D

FANUC Power Mate i-MODEL H Power

Mate i-H

Power Mate i


12/168

1.GENERAL GENERAL B-63434EN/02

- 4 -

Related manualsThe tables below list the manuals related to each model. When

reading this manual, refer to the related manuals as well.

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

Manual name Specification number

Descriptions B-63002EN

Connection Manual (Hardware) B-63003EN

Connection Manual (Functions) B-63003EN-1

Operators Manual (For Lathes) B-63004EN

Operators Manual (For Machining Centers) B-63014EN

Maintenance Manual B-63005EN

Parameter Manual B-63010EN

Manuals related to Series 21i-TA/MAManual name Specification number




Operators Manual (For Lathes) B-63084EN

Operators Manual (For Machining Centers) B-63094EN



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





Operators Manual B-63174EN




13/168

II. DESCRIPTION


14/168


15/168

B-63434EN/02 DESCRIPTION 1.FL-net SPECIFICATIONS

- 7 -

1 FL-net SPECIFICATIONSThis section describes the specifications of the FL-net.


16/168

1.FL-net SPECIFICATIONS DESCRIPTION B-63434EN/02

- 8 -

1.1 What Is the FL-net?

The FL-net is an open FA network standardized by the FA OpenPromotion 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-netThe 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.

Sensor actuator

Computers

Controllers

Upper LAN Ethernet (TCP/IP, UDP)

FL-net (Ethernet-based control network)

Company A PLC Company B PLC Company C PLCCompany Dpersonal CNC Company E RC

Devices

Field network

Large-scale network

Up to 249 communication devices (nodes) can be connected to

share data among them.

1 2 248 249 250 254

% & ' ( ) 0 1 ' 2 3 4 5 % 6 7 8 9 @ ( 1 ' ) 3 ' & A % & ' ( ) 0 1 ' 2 3 6 B C 5 %

6 B 7 D E % 2 0 @ F ( 5 ' ( @ ( 9 ' G

FL-net


17/168


- 9 -

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.

Large-capacity common memory

As common memory, 8K bits + 8K words (a total of 17K bytes)

of large-capacity common memory can be shared among all

nodes.

Node=01 common memory Node=02 Node=03 Node=04

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

(Transmission) (Reception) (Reception)

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

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

(Reception)

Fast response

The FL-net provides a fast response of 50 ms/32 nodes (at 2K

bits + 2K words/32 nodes).

NOTEThis value indicates the speed at which a token is

passed through nodes. It does not indicate thetime from when data is set in a node to when itseems to be data in a different node.

H 9 I F 9 5 2 @ ( 3 0 F 3 3 F % ( P 0 ' 3 3 @ Q '

5 2 @ ( 3 0 F 3 3 F % (

H 9 I F 9 5 2 @ ( 3 0 F 3 3 F % (

' 3 3 @ Q '

& @ 5 @

H 9 I F 9 & @ 5 @

R F 5 S @ 5 % T ' (


18/168

1.FL-net SPECIFICATIONS DESCRIPTION B-63434EN/02

- 10 -

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.


19/168


- 11 -

1.2 FANUC FL-net Functions

Cyclic transmissionWith the FANUC FL-net, part of large-capacity common memory can

be allocated in the PMC R area or D area to allow the user program to

read and write data in the FL-net common memory.

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

word) area called area 1 and an 8K-word area called area 2.

Generally, common memory area 1 is used for treating bit data and

common memory area 2 is used for treating numeric data.

For how the PMC memory area corresponds to each common memory

area and how to allocate common memory areas, see Sections 2.1,"Common Memory Area 1 Cyclic Transmission," and 2.2, "Common

Memory Area 2 Cyclic Transmission," in "Description."

Message transmissionThe 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.


20/168


21/168

B-63434EN/02 DESCRIPTION 2.CYCLIC TRANSMISSION

- 13 -

2 CYCLIC TRANSMISSIONThis 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.


22/168

2.CYCLIC TRANSMISSION DESCRIPTION B-63434EN/02

- 14 -

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 address4) Pa31: Area 1 address

5) Pa32: Data size (in words)

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

below, data exchange is performed by making a distinction between a

DI area and a DO area, thus posing no problem. When 0 is set in

Pa32 (data size), the data of common memory area 1 is not

exchanged.

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

+#-$%'##*+)$

)0+)'-

+#-$%'##*+)$

)0+)'-

+#-$%'##)*0

()()'

+#-$%'##*+)$

)0+)'-

+#-$%'##*+)$

)0+)'-

+#-$%'##*+)$

)0+)'-

@ U C

@ U 6 @ 4 6

@ U 4

@ 4 4


23/168


- 15 -

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 forstatically fixing a DI data area independently of nodes.

2.2.1 DO data allocation

Procedure

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:

V C

2222


24/168


- 16 -

4) Until FFh is written to the switch flag, the CNC writes the DO

data in the PMC area specified by Pa40 (allocation address (for

DO)) to common memory area 2, using the same DO offset.

@ 2 ' @

2222


25/168


26/168


- 18 -

@ 2 ' @

2222


27/168


28/168


29/168


- 21 -

@ 2 ' @

2222


30/168


31/168


32/168


33/168


34/168


35/168


36/168


37/168


38/168


- 30 -

2.5 Data Concurrency

With the FANUC FL-net function, when a ladder program handlesinput/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) unitsThe 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-byteunits:

DECB, CODEB, DCNVB, COMPB, DSCHB, XMOVB, ADDB,

SUBB, MULB, DIVB, NUMEB, MOVN, EOR, AND, OR, and

NOT instructions

Data concurrency in word-data (2-byte-data) unitsThe 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

Data concurrency in byte-data (1-byte-data) unitsThere is no constraint.

The data concurrency is always guaranteed in 1-byte-data units.

NOTE

If the above constraints are not satisfied, the

concurrency of word data cannot be guaranteed.

NOTE

If the above constraints are not satisfied, the

concurrency of long data cannot be guaranteed.


39/168


- 31 -

When handling data input from the FL-net, note the following points:

NOTE1 When the PMC R area or D area is used as the input

data area, the synchronous buffer in the PMC is notused. For this reason, input data may change duringladder 1 scan.In other words, the value updated via the FL-net maybe read, depending on the read timing, even when theladder program handles data in the same area.

2 The concurrency of data longer than long data (4-bytedata) is not guaranteed. To establish the

concurrency of such data, see "Measures to guaranteethe concurrency of multiple-byte data" following.


40/168


41/168


- 33 -

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.

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

CAUTIONFor reasons related to the specifications of the FANUCFL-net board, set the size of common memory area 1and area 2 of the local node that are allocated in thePMC area and the size of common memory area 1and area 2 of another node that are allocated in thePMC area so that the total size of them is 1024 wordsor less.


42/168


- 34 -

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


43/168

B-63434EN/02 DESCRIPTION 3.MESSAGE TRANSMISSION

- 35 -

3 MESSAGE TRANSMISSIONThis 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.


44/168


45/168


46/168

3.MESSAGE TRANSMISSION DESCRIPTION B-63434EN/02

- 38 -

The format of each interface area is described below.

Transmit interface for the client and transparent messagesThe interface area specified by Pa50 (interface allocation address) has

the format shown below.

7 0

+0 Transmission

request/response flag

+2 Request status (R_STS)

+3 Response status

(M_RLT)

+4 Cancel flag

+5 Destination nodenumber

+6 (Reserved)

+8 Message section

NOTEThe message section does not include a data bufferarea.

@ B C

@ B 4


47/168


48/168


- 40 -

CAUTIONEnsure that while the transmission request/response

flag is set to 0001h, the user program does not rewritethe data in this interface area. Otherwise, messagetransmission may not be terminated normally.

NOTE1 When a service is terminated normally, 8000h is

returned to this flag. If a value other than 8000h isreturned, check the value, and resolve the problem.See Table 3-3 for the error codes returned from thesystem.

2 After a message transmission request is made, this

interface does not allow the next transmissionrequest to be made until a response message isreceived or an error occurs. So, if a responsemessage cannot be received for a cause on theserver, the next message transmission requestcannot be made until the power is turned off. Insuch a case, the cancel flag allows the system to exitfrom the response message wait state and wait forthe next message transmission request. Thepurpose of this cancellation is just to allow thesystem to accept the next message transmissionrequest. This cancellation is not intended to cancelmessage transmission with the FL-net function.(The FL-net function does not have a function forcanceling message transmission.) This means thatwhen this cancellation function is used, the responsemessage for the previous message request may betreated as a response to the next message requestby mistake.


49/168


- 41 -

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


50/168


51/168


52/168


- 44 -

3.3.2 Procedure for operating the transparent messagetransmission function

2 @ ( 3 ` @ 2 ' ( 5 0 ' 3 3 @ Q ' 5 2 @ ( 3 0 F 3 3 F % ( 3 F & '

3 ' 2 ` 2 % Q 2 @ 0 H 3 5 ' 0

4 G 2 @ ( 3 ` @ 2 ' ( 5 0 ' 3 3 @ Q '

` 2 ' ` @ 2 @ 5 F % (

@ 9 S 3 5 @ 5 ) 3 E I @ Q F 3

9 I ' @ 2 ' & A

6 G 2 @ ( 3 0 F 3 3 F % ( 2 ' d ) ' 3 5

E I @ Q C C C 4 S

U G S ' 9 T F ( Q 5 S @ 5 5 S '

5 2 @ ( 3 0 F 3 3 F % ( 2 ' d ) ' 3 5 E I @ Q

F 3 3 ' 5 5 % C C C 4 S

7 G 2 @ ( 3 ` @ 2 ' ( 5 0 ' 3 3 @ Q '

5 2 @ ( 3 0 F 3 3 F % (

4 6 G S ' 9 T F ( Q 2 ' d ) ' 3 5 3 5 @ 5 ) 3 4 4 G # 2 ' 9 ' ` 5 F % (

4 7 G S ' 9 T F ( Q 5 S @ 5 5 S '

9 % 0 ` I ' 5 F % ( E I @ Q F 3 3 ' 5 5 %

b C C C S

4 U G % 0 ` I ' 5 F % ( E I @ Q b C C C S

4 B G I ' @ 2 F ( Q 5 S ' 9 % 0 ` I ' 5 F % (

E I @ Q 5 % C C C C S

2 @ ( 3 ` @ 2 ' ( 5 0 ' 3 3 @ Q ' 2 ' 9 ' ` 5 F % ( 3 F & '

3 ' 2 ` 2 % Q 2 @ 0 H 3 5 ' 0

B G 2 @ ( 3 ` @ 2 ' ( 5 0 ' 3 3 @ Q '

2 ' 9 ' ` 5 F % (

Y G # 5 2 @ ( 3 0 F 3 3 F % (

b G S ' 9 T F ( Q 5 S @ 5 5 S '

2 ' 9 ' F e ' E I @ Q F 3 3 ' 5 5 %

C C C 4 S

V G ' 9 ' F e ' E I @ Q C C C 4 S

8 G ' 9 ' F e ' 0 ' 3 3 @ Q '

` 2 % 9 ' 3 3 F ( Q

4 C G I ' @ 2 F ( Q 5 S ' 2 ' 9 ' F e ' E I @ Q

5 % C C C C S


53/168


54/168


- 46 -

Table 3-5 Byte Block Read Interface Items

Interface item Description Direction

Transaction code Request message: 65003

Response message: 65203

US

SU

Offset address on

virtual address

space

Request message: Offset address on virtual address

space of byte block data to be read

from the server

Response message: Same as above

US

Data size Request message: Size of byte block data to be read

from the server (in bytes)

Response message: Size of byte block data actually

read from the server (in bytes)

US

SU

Read data buffer

start address

Request message: Start address of an area in the

PMC R area used to store byte

block data read from the server


US

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.

SU

NOTEFor an error code stored when an abnormalresponse is returned, refer to the manual of theequipment of a message transmission destination.


55/168


- 47 -

3.4.2 Byte block write

Request message Response message7 0 7 0

+0 Transmission request

flag

0001h

+0 Response flag

+2 +2 Request status

+3 +3 Response status

+4 Cancel flag +4

+5 Destination node

number

+5

+6 (Reserved) +6 (Reserved)

+8 Transaction code

65004

+8 Transaction code

65204+10 (Reserved) +10 (Reserved)

+12 Offset address on

virtual address space



+16 Data size +16 Data size

+18 Write data buffer start

address


address

Write data (Reserved)

Error code when an

abnormal response isreturned

@ B C

@ B 4


56/168


- 48 -

Table 3-6 Byte Block Write Interface Items




US

SU

Offset address on

virtual address

space


space of byte block data to be

written to the server


US

Data size Request message: Size of byte block data to be written

to the server (in bytes)

Response message: Size of byte block data actually

written to the server (in bytes)

US

SU

Write data buffer

start address


PMC R area storing byte block data

to be written to the server


US

Write data Request message: Byte block data to be written to the

server

Response message: An error code is stored when an

abnormal response is returned.

US

SU



57/168


- 49 -

3.4.3 Word block read



flag

0001h

+0 Response flag



+4 Cancel flag +4

+5 Destination node

number

+5


+8 Transaction code

65005

+8 Transaction code







+18 Read data buffer start

address

+18 Read data buffer start

address

(Reserved) Read data

@ B C

@ B 4


58/168


- 50 -

Table 3-7 Word Block Read Interface Items




US

SU

Offset address on

virtual address

space


space of word block data to be

read from the server


US

Data size Request message: Size of word block data to be read

from the server (in bytes)

Response message: Size of word block data actually

read from the server (in bytes)

US

SU

Read data buffer

start address


PMC R area used to store word

block data read from the server


US

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.

SU



59/168


- 51 -

3.4.4 Word block write



flag

0001h

+0 Response flag



+4 Cancel flag +4

+5 Destination node

number

+5


+8 Transaction code

65006

+8 Transaction code








address


address

Write data (Reserved)

Error code when an

abnormal response isreturned

@ B C

@ B 4


60/168


61/168


- 53 -

3.5 Message Transmission Server Function

3.5.1 Error code list

In response to a request from a client, the message data transmission

server function automatically returns a response message without

involving the user program. If the message transmission client

receives an abnormal response, the FANUC FL-net function returns a

code listed in Table 3-9.

Table 3-9 List of Server Function Error Codes

Error code Description

8001h An attempt was made to access a nonexistent PMC area.

8002h A specified data size exceeded 1024 bytes.

8003h An attempt to allocate a parameter storage area failed.

8004h A request was made to write to a write-prohibited area.


62/168


- 54 -

3.5.2 Virtual address space allocation

Virtual address space used to read/write byte block and read/writeword block is allocated in the PMC area as described below.

Virtual address space for byte block data

Table 3-10 Virtual Address Space for Byte Block Data

Allocation in PMC

Symbol Type of signal Address

(decimal)

Virtual address

space

(hexadecimal)

Remarks

X Signal from machine to

PMC

X0000 or

later

0000h or later Read only

Y Signal from PMC to

machine

Y0000 or

later


F Signal from CNC to PMC F0000 or

later


G Signal from PMC to CNC G0000 or

later

C000h or later Read only

R Internal relay R0000 or

later

10000h or later Read/write

D Data table D0000 or

later


Virtual address space for word block data

Table 3-11 Virtual Address Space for Word Block Data

Allocation in PMC


(decimal)

Virtual address

space

(hexadecimal)

Remarks

X Signal from machine to

PMC

X0000 or

later



machine

Y0000 or

later


F Signal from CNC to PMC F0000 or

later


G Signal from PMC to CNC G0000 or

later



later



later

A000h or later Read/write

NOTEOnly installed address space in the PMC can beaccessed. Check PMC address space before use.


63/168


64/168


65/168


- 57 -

3.6.2 Transparent message reception

Reception notificationmessage

Reception confirmationmessage

7 0 7 0

+0 Receive flag

0001h

+0 Completion flag

+2 Transmission source

node number

+2

+3 (Reserved) +3

+4 Transaction code

50000 to 59999

+4 Transaction code

50000 to 59999


+8 Transparent receivedata

+8 Transmit data bufferstart address

Table 3-13 Transparent Receive Message Interface Items


Receive flag When a transparent message is received, this flag is set to

0001h after the interface items below are set.

SU

Transmission

source node

number

Node number of a transmission source that transmitted a

transparent message

SU

Transaction code !,,,,)!4444 SUData size Size of received transparent data (in words) SU

Transparent

receive data

Transparent data received SU

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 notprocessed 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.

@ B 6

@ B U


66/168


67/168


- 59 -

Table 3-1 Receive Message Interface Items


Receive flag When a message is received, this flag is setto 0001h after the interface items below are

set.

SU

Transmission

source node

number

Number of the node which transmitted a

message

SU

Transaction

code

65003 to 65006 SU

Data size Size of received message data SU

Virtual address

space

Offset address on virtual address space SU

Write data Received write request data 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 Description

02 (buffer full) The previously received message is not processed by

the user program.

03 (not initialized) An interface area for receiving a message is not

allocated.06 (format error) A message actually received is larger than a receive

data area allocated by this interface.

Word block data actually received consists of an odd

number of bytes.


68/168


- 60 -

3.7.2 Response message transmission

2 @ ( 3 0 F 3 3 F % ( 2 ' d ) ' 3 5

0 ' 3 3 @ Q '

2 @ ( 3 0 F 3 3 F % (

9 % 0 ` I ' 5 F % ( 0 ' 3 3 @ Q '

V C V C

5!,)5!,5


69/168


- 61 -

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

Allocation in PMC


(decimal)

Virtual address

space

(hexadecimal)

Remarks

X Signal from machineto PMC

X0000 orhigher

01000000h orhigher

Read only


machine

Y0000 or

higher

01004000h or

higher

Read only

F Signal from NC to

PMC

F0000 or

higher

01008000h or

higher

Read only

G Signal from PMC to

NC

G0000 or

higher

0100C000h or

higher

Read only


higher

01010000h or

higher

Read/write


higher

01014000h or

higher

Read/write

Virtual address space for word block data with confirmation

Table 3-5 Virtual Address Space for Word Block Data with Confirmation

Allocation in PMC


(decimal)

Virtual address

space

(hexadecimal)

Remarks

X Signal from machine

to PMC

X0000 or

higher

01000000h or

higher

Read only


machine

Y0000 or

higher

01002000h or

higher

Read only

F Signal from NC to

PMC

F0000 or

higher

01004000h or

higher

Read only

G Signal from PMC to

NC

G0000 or

higher

01006000h or

higher

Read only


higher

01008000h or

higher

Read/write


higher

0100A000h or

higher

Read/write

NOTE

Only installed address space in the PMC can be

accessed. Check PMC address space before use.


70/168


71/168

III. OPERATION


72/168


73/168


74/168

B-63434EN/02 OPERATION 1.PARAMETER SETTING

- 67 -

(3) Area 1 allocation parametersTable 1-3 Area 1 Allocation Parameters

Parameter name Description Index number

Allocation address

(shared for DI/DO)

Start address of an area in the PMC R area

allocated to area 1

Pa30

Area 1 address

(shared for DI/DO)

Start address of area 1 allocated to an area

in the PMC R area

Pa31

Data size (shared for

DI/DO)

Size of data to be exchanged Pa32

(4) Area 2 allocation parametersTable 1-4 Area 2 Allocation Parameters


Allocation address

(for DO)


or D area that serves as the source of data to

be written to area 2

Pa40

Data size (for DO) Size of data written to area 2 Pa41

Allocation address

(for DI)


or D area that serves as the read destination

of information about other nodes and data

from area 2

Pa42

Area 2 data

exchange condition

allocation address

Address of an area in the PMC D area that is

used to specify conditions on data exchange

with area 2

Pa43

Switch flag

allocation address

Flag for switching between specified

conditions at the area 2 data exchange

condition allocation address above

Pa44

Static area 2 address

(for DI)

Start address of static area 2 to be allocated

in the PMC area

Pa45

Static data size

(for DI)

Size of data statically exchanged Pa46

(5) Message allocation parametersTable 1-5 Message Allocation Parameters


Interface allocation

address

Start address of an area in the PMC R or D

that serves as the start address of an

interface used for message transfer

Pa50

Interface allocation

size

Maximum allowable size of the interface area

used above

Pa51

Transparent receive

message allocation

address


or D area that serves as the start address of

an interface used to store transparent

message receive data

Pa52

Transparent receive

message allocation

size

Maximum allowable size of the interface area

used above

Pa53


75/168

1.PARAMETER SETTING OPERATION B-63434EN/02

- 68 -

For each FL-net function used, the parameters below need to be set.

A. Cyclic transmission of common memory area 1

Basic parameters

Area 1 allocation parameters

B. Cyclic transmission of common memory area 2

Basic parameters


C. Message transmission

Basic parameters

Message allocation parameters

For B (Cyclic transmission of common memory area 2) and C

(message transmission) above, operation based on a user program

needs to be performed as required. For information about requiredoperation, 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.

CAUTIONInput/output data in common memory area 1 andcommon memory area 2 is transferred

asynchronously with ladder program execution. So,the concurrency of input/output data consisting ofmultiple bytes may not be guaranteed. When worddata is input or output, for example depends on thesetting condition, the higher byte may be updatedsome time after the lower byte is updated. Fordetails, see Chapter II DESCRIPTION Section 2.5.


76/168


77/168

1.PARAMETER SETTING OPERATION B-63434EN/02

- 70 -

(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 thescreen 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.

CAUTIONWhen a parameter to be allocated to the PMC area isnot 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 theFL-net board may use an area starting at R0000. Insuch a case, press soft key DISABL so that thesetting becomes "R----."


78/168


- 71 -

Setting item

Each setting item is described below.

Basic parameters

The basic parameters are used to set the FL-net function itself.

Table 1-6 Basic Parameters

Item Description

IP ADDRESS

Pa10

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.

NODE NAME

Pa17

An arbitrary node name not longer than 10 characters can bespecified.

Lowercase letters cannot be displayed and entered.

AREA1 ADDR

(Note 1) Pa11

Start address of common memory area 1 of the local node.

A value from 0 to 511 can be set.

AREA1 SIZE

(Note 1) Pa12

Data size of common memory area 1 of the local node.


AREA2 ADDR

(Note 1) Pa13

Start address of common memory area 2 of the local node.


AREA2 SIZE

(Note 1) Pa14

Data size of common memory area 2 of the local node.


TOKEN WATCH

(Note 2)

Pa15

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)

MIN FRAME

Pa16

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).

NOTE1 For common memory area 1, a value beyond 512

must not be specified. For common memory area2, 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 timespecified in this parameter has elapsed, the nextnode reissues a token. This means that anadequate value needs to be set in connection withthe amount of transmit data of the local node.Usually, set 50 (50 ms).


79/168


80/168


- 73 -


The area 2 allocation parameters are used for allocation-relatedsettings to enable data exchange between common memory area 2 and

the PMC R area.

Table 1-9 Area 2 Allocation Parameters

Item Description

AREA2 DO:

ALLOCATION

Pa40

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.

AREA2 DO:

SIZE(Note 1)

Pa41

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.AREA2 DI:

ALLOCATION

Pa42

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].


AREA2 DI:

ALLOC PTR

(Note 2)

Pa43

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].


AREA2 DI:

CHANGE FLG

(Note 2)

Pa44

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].

AREA2 DI:

AREA2 ADDR

(Note 2)

Pa45

Start address of common memory area 2 to be statically

allocated in the PMC area as DI data

AREA2 DI:

AREA2 SIZE

(Note 1, Note2)Pa46

Size of DI data statically exchanged between common

memory area 2 and the PMC area (Unit: Words)

NOTE1 The unit of size set in this parameter is words. This

means that for an area used in the PMC R area, thenumber of bytes as many as the size set in thisparameter multiplied by 2 is required.

2 Parameters AREA2 ADDR and AREA2 SIZE can beused to set a large area for data exchange betweencommon memory area 2 and PMC area

independently of node numbers.When a value of 0 is set for AREA2 SIZE, no staticallocation is performed and dynamic DI data change


81/168


82/168


83/168


84/168


85/168


86/168


- 79 -

30010 Node name: 1st character

30011 Node name: 2nd character30012 Node name: 3rd character

30013 Node name: 4th character







[Data type] Byte

[Index number] Pa17

Set the equipment name of the local node one character for each

parameter in ASCII code.

30020 Start address of area 1 transmit data

[Data type] Word

[Valid data range] 0 - 511

[Index number] Pa11

30021 Area 1 transmit data size

[Data type] Word


[Index number] Pa12

30022 Start address of area 2 transmit data

[Data type] Word


[Index number] Pa13

30023 Area 2 transmit data size

[Data type] Word[Valid data range] 0 - 8192

[Index number] Pa14

30024 Token monitoring time

[Data type] Byte

[Unit of data] 1 msec


[Index number] Pa15

30025 Minimum allowable frame interval

[Data type] Byte

[Unit of data] 100 sec


87/168


88/168


- 81 -

30036 Area 2 data exchange condition allocation address

[Data type] Word[Valid data range] 0 - (only an even address)

[Index number] Pa43

30037 Switch flag allocation address

[Data type] Word

[Valid data range] 0 - (only an even address)

[Index number] Pa44

30050 Area 2 static DI data exchange address

[Data type] Word


[Index number] Pa45

30051 Area 2 static DI data exchange size

[Data type] Word


[Index number] Pa46

30055 PMC area allocation address (for DO)

[Data type] Word

[Valid data range] 68(D) or 82(R)

[Index number] Pa40

30056 PMC area allocation address (for DI)

[Data type] Word

[Valid data range] 68(D) or 82(R)

[Index number] Pa42

Message allocation parameters

30040 Interface allocation address

[Data type] Word


[Index number] Pa50

30041 Interface allocation size

[Data type] Word

[Index number] Pa51

30042 Receive message allocation address

[Data type] Word


[Index number] Pa52

30043 Receive message allocation data aize

[Data type] Word


89/168


90/168

B-63434EN/02 OPERATION 2.MAINTENANCE SCREEN

- 83 -

2 MAINTENANCE SCREENThis 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.


91/168

2.MAINTENANCE SCREEN OPERATION B-63434EN/02

- 84 -

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] toswitch 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.


92/168


93/168


- 86 -

Table 2-1 explains the items displayed on the screen.

Table 2-1 Participating Node Management Table

Item Description

NODE NO. Node number of the node about which information is

currently displayed

AREA1 ADDR Start address of the node in common memory area 1

AREA1 SIZE Data size of the node in common memory area 1

AREA2 ADDR Start address of the node in common memory area 2

AREA2 SIZE Data size of the node in common memory area 2

TOKEN WATCH Token monitoring time of the node (in ms)

MIN FRAME Allowable minimum frame interval (in 100 s)

ULS State of the upper layer of the node

LKS State of the FA link of the node

NODE NAME Node name of the node.

When the node is not the local node, this item can be

displayed only if the node participates in the network after

the participation of the local node.

Lowercase letters entered are converted to uppercase

letters for display.

VENDOR NAME Vendor code of the node.

When the node is not the local node, this item can be

displayed only if the node participates in the network after




MAKER TYPE Manufacturer Model type of the node.

When the node is not the local node, this item can bedisplayed only if the node participates in the network after




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.


94/168


95/168


96/168


- 89 -

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] toswitch 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 shownbelow appears.

Screen 2-4 FL-net Log Information Management Table Screen

(10.4" LCD)

(4) Pressing soft key [CLEAR] clears log information.


97/168


98/168


99/168


100/168


101/168


- 94 -

Manufacturer type of the local node

8024 STATUS[Data type] Byte

Status of the local node

8025 LKS

[Data type] Byte

State of the FA link of the local node

8026 ULS

[Data type] Word

State of the upper layer of the local node

8027 AREA1 ADDR

[Data type] Word

Start address of common memory area 1 of the local node

8028 AREA1 SIZE

[Data type] Word

Size of common memory area 1 of the local node

8029 AREA2 ADDR

[Data type] Word

Start address of common memory area 2 of the local node

8030 AREA2 SIZE

[Data type] Word

Size of common memory area 2 of the local node

8031 TOKEN WATCH

[Data type] Byte


Token monitoring time of the local node

8032 MIN FRAME[Data type] Byte

[Unit of data] 100 secMinimum allowable frame time interval of the local node

8033 PRTCL VER.

[Data type] Byte

Protocol version

Network management table

8040 TOKEN NODE

[Data type] Byte


102/168


- 95 -

Node number of the node that currently holds the token

8041 MIN FRAME[Data type] Byte

[Unit of data] 100 secMaximum value of the minimum allowable frame time intervals of all

nodes participating in the network

8042 RCT

[Data type] Word


Allowable refresh cycle time of the local node

8043 RCM[Data type] Word


Refresh cycle measurement time of the local node

8044 MAX RCM

[Data type] Word


Maximum refresh cycle measurement time of the local node

8045 MIN RCM

[Data type] Word[Unit of data] 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

8051 SEND ERROR COUNT[Data type] Double word

Number of transmission errors

8052 TOTAL RECEIVE COUNT


Total number of received frames

8053 RECEIVE ERROR COUNT


Number of receive errors

The reception of a packet other than an FL-net packet is also countedas a receive error.


103/168


104/168


- 97 -


Number of disconnections of the local node from the network because

the token is not passed to the local node

8066 OTHER NODE DISCONNECT COUNT


Number of recognitions that other nodes are disconnected from the

network


105/168


106/168

B-63434EN/02 OPERATION 3.EXAMPLE OF CONNECTION

- 99 -

3.1 Example of Configuration

Using the example of configuration shown below, this section

describes the setting of each parameter.

Ethernet

Series 16i -A Series 18i -A Power Mate i -D

Node No.10 Node No.20 Node No.30

Fig. 3-1 Example of FL-net Configuration

The parameter settings and PMC area allocation state when 4-word

DO data in common memory area 1 and 64-word DO data in commonmemory 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

Common memory area

2

0x0000 0x0000 Node No. 10

0x0010 Node No. 100x0014 Node No. 20 0x0040

0x0018 Node No. 30 0x0050 Node No. 200x001c

0x0090

0x00a0 Node No. 30

0x00d0

0x01ff

0x1fff


107/168


108/168


109/168


110/168


111/168


112/168


113/168


114/168


115/168

1.INSTALLATION CONNECTION B-63434EN/02

- 108 -

1.1 Specifications

The specifications of the FL-net board are described below.

For the stand-alone type Series 16i/18i/21i-MODEL A

Name FL-net board

Ordering code A02B-0265-J272

Board drawing

number

A20B-8100-0530

Applicable

model

FANUC 16i/160i-TA (stand-alone type)

FANUC 16i/160i-MA (stand-alone type)

FANUC 18i/180i-TA (stand-alone type)


FANUC 21i/210

i-TA (stand-alone type)


Heat dissipation 7 (W)(Note 1)

For the Power Mate i-MODEL D/H

Name FL-net board

Ordering code A02B-0259-J272

Board drawing

number

A20B-8100-0530

Applicable

model

FANUC Power Mate i-MODEL D/H

Heat dissipation 7 (W)(Note 1)

NOTE1 For the heat dissipation of the main CNC unit and

other optional units, refer to the connection manualof the CNC.

2 When using the FL-net board, observe theinstallation condition (environment condition withinthe cabinet) of the CNC control unit where the FL-netboard is mounted.


116/168


117/168

2.CONNECTION OF THE COMMUNICATION FUNCTION CONNECTION B-63434EN/02

- 110 -

2 CONNECTION OF THECOMMUNICATION FUNCTIONThis chapter provides information required for Ethernet connection of

the FL-net board.

CAUTION1 Before attaching or detaching a cable to the FL-net

board, turn off the power to the CNC, and confirmthat the power is off.

2 For network building and the condition for usingdevices other than the FL-net board (such as mediaconverters, hubs, transceivers, and cables), contactthe supplier of each device. For networkinstallation, care must be taken to protect thenetwork from a noise source. Separate the networkwiring sufficiently away from a noise source such asa power line and motor from an electrical viewpoint,and ground each device as required. If grounding isinsufficient because of high impedance, acommunication error may occur. Before going intoactual operation after equipment installation, checkthe operation by conducting a communication test.FANUC cannot take responsibility for network troublearising from a device other than the FL-net board.


118/168


119/168


120/168


121/168


122/168


123/168


124/168


125/168


126/168

B-63434EN/02 CONNECTION 2.CONNECTION OF THE COMMUNICATION FUNCTION

- 119 -

2.4.4 Hub

Recommended hubManufacturer name Specification Remarks

Contec Co., Ltd. RT-1008H 10BASE-T

Eight ports

This hub is not for FA. Use the hub in a dust-proof cabinet.

Contact points

Manufacturer name Contact point

Contec Co., Ltd.

East Branch Tachibana Annex Building, 2-25-14 Kameido,

Koto Ward, Tokyo, 136-0071

TEL: 03-5628-0211 (pilot number)

FAX: 03-5628-0210Central Branch Orchid Building, 2-38-2 Meieki, Nakamura Ward,

Nagoya City, 450-0002


FAX: 052-564-7826

West Branch 3-9-31 Himesato, Nishiyodogawa Ward, Osaka

City, 555-0025


FAX: 06-6478-1031

Remarks http://www.contec.co.jp/


127/168


- 120 -

2.5 Noise Protection

2.5.1 Signal line separation

The wiring of Ethernet cables belongs to group C. For the method

of separation from group A wiring and group B wiring, refer to

"Connection Manual: Hardware (B-63003EN)" of each CNC.

2.5.2 Cable clamping and shield processing

Clamp those cables that are run into the CNC and require shield

processing, as shown below. Process the shield of a twisted pair

cable for Ethernet in the same way. This clamp processing secures acable, 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

0%('

#1(-0#0

+)='A(#


128/168


129/168


130/168


131/168


- 124 -

NOTE1 Ensure that the ground system of the personal

computer/trunk side is separated from the groundsystem of the machine system. If ground systemseparation is impossible because only onegrounding point is available, run the personalcomputer/trunk side ground wire and the machineside ground wire separately to the grounding point.(See the figure below.) The ground resistance mustbe 100 ohms or less (glass-2 grounding). Theground wire must not be thinner than the AC powerline, and must be at least 5.5 mm

2in diameter.

2 Even when the insulation/separation method based

on 10BASE-T is used as described above, noise canimpede normal communication. When a network isused in such a very poor environment, consider theuse of 10BASE-FLAG (optical fiber media) tocompletely separate the machine side from thepersonal computer side.

73

0%(' +=@(

+)='/%+)*0A+-)#(&)$A=+6+=@-%'

+)='%.A)%

#&0%

+)='/%+)*0$#&0%-%'

When only one grounding point is available


132/168


133/168


134/168


135/168


136/168


137/168


138/168


139/168

B-63434EN/02 INDEX

%

INDEX

(()%))*#(%-)*A#+%&%A#%.)'-

(()%))*()()'-#!

3"1()&@+#'4

3"1()&@/+%

3"%-)*"&(%#4

3"%-)*--#.##5

#1(&(#$A%.#'-0%('A+)&--%.4

#1(&)&%)

#1(/%+4,

)$$)$)+"+#"&(%&+#-$%--%)

)$$)$)+"+#"&(%&+#-$%--%)

7

)&%))0+!

)&)+A&%*%%)-4

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

'###(()%)

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

5

++)+&)'(%-

2#$A()*)*%.=+#%)

8

2#$A()*#+#$+%.-

=&%)-,

5

7,

7=14

$#.)*##2&0#.

-#((#%)

#")=)*)$A)-,

'%%)-#'#%.-,

%-)*--#.+#-$%--%)+?%&-,

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

!4

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

--#.+#-$%--%)+?+=&%)

/)+@%-#((#%)4

/)+@##.$#1(5

)'#)%)+%.!

)'-%*)+$#%)

)%-+)&%)4


140/168


141/168


142/168


143/168


144/168

TITLE

Modification of FANUC FL-net BoardOPERATORS MANUAL

The additional information of FANUC FL-net BoardOPERATORS MANUAL

Addition of Stand-alone type FANUC Series 16i/18i/21i-TB/MB to the table of Page 3

Applicable models

Model Abbreviation

Stand-alone type FANUC Series 16i/160i -TA 16i-TA

Stand-alone type FANUC Series 16i/160i -MA 16i-MASeries 16i-A

Stand-alone type FANUC Series 16i/160i -TB 16i-TB

Stand-alone type FANUC Series 16i/160i -MB 16i-MBSeries 16i-B

16i





18i





21i

FANUC Power Mate i-MODEL D Power Mate i-D

FANUC Power Mate i-MODEL H Power Mate i-HPower Mate i PMi

Addition of the following table to Page 4

Related manuals

Manual related to FANUC Series 16i/18i-TB/MB



Connection Manual(Hardware) B-63523EN

Connection Manual(Functions) B-63523EN-1

Operators Manual(For Lathes) B-63524EN

Operators Manual(For Milling Centers) B-63534EN



SHEET 2/17DESCRIPTIONDESIGNDATEEDIT

01 Mutai First issue B-63434EN/02-1

FANUC LTD.

02.05.20 DRAW.NO.


145/168


146/168


147/168


148/168


149/168


150/168


151/168


152/168


153/168


154/168


155/168


156/168


157/168

TITLE

Modification of FANUC FL-net BoardOPERATORS MANUAL

Error messages which are displayed when data exchange failsWhen 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(????, ????) OVERLAPPINGThe 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 RANGEParticipating node information address is invalid.

In that case, the information is not copied into the specified PMC address.


- An even address should be configured.


INVALID DYNAMIC CHANGE FLAG

Switch flag allocation address is invalid.

In that case, the dynamic switch of the area2 can not be performed.


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.


- An even address should be configured to Pa30.


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


SHEET 15/17DESCRIPTIONDESIGNDATEEDIT

01 Mutai First issue B-63434EN/02-1

FANUC LTD.

02.05.20 DRAW.NO.


158/168


159/168


160/168


161/168

Sheet

Title

DrawNo.

Ed. Date Design DescriptionDate Dec.15.2004 Desig. Y.Honda Apprv. 2/9

FANUC FL-net Board

OPERATORS MANUAL

B-63434EN/02-3

Add the following explanation as Chapter 4 into the OPERATION part.

4SETTING METHOD FOR PMC-SD7

This chapter describes the setting method when PMC-SD7 is used.

NOTE1 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 Section1.2 Setting of Parameters.


162/168

Sheet

Title

DrawNo.


FANUC FL-net Board

OPERATORS MANUAL

B-63434EN/02-3

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

OWN STATUS

Examples) M1, M17, M63985





ENTRY NODE






AREA1 DO/DI :

ALLOCATION



163/168


164/168

Sheet

Title

DrawNo.


FANUC FL-net Board

OPERATORS MANUAL

B-63434EN/02-3

4.2 Example of Setting

4.2.1 Example of Configuration

Using the example of configuration shown below, this section describes

the setting of each parameter.

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 Common memory area 2

0x0000 0x0000Node No.10

0x0010Node No.10

0x0014Node No.20

0x0040

0x0018Node No.30

0x0050Node No.20

0x001c

0x0090

0x00a0Node No.30

0x00d0

0x01ff

0x1fff

FL-net

Series 18i -B Series 18i -B Series 18i -B

Node No.10 Node No.20 Node No.30


165/168


166/168

Sheet

Title

DrawNo.


FANUC FL-net Board

OPERATORS MANUAL

B-63434EN/02-3

Table 4-2 Parameters of Node No.10

Item Setting Item Setting

IP ADDRESS 192.168.250.10 AREA2 DI: NODE NAME NODE#10 ALLOCATION %M02401

AREA1 ADDR 16 ALLOC PTR %R00001

AREA1 SIZE 4 CHANGE FLG %M02393

AREA2 ADDR 0 AREA2 ADDR 0AREA2 SIZE 64 AREA2 SIZE 0

TOKEN WATCH 50 MESSAGE: MIN FRAME 10 ADDRESS %M03601

OWN STATUS %M00993 SIZE 20

ENTRY NODE %M01025 RECV MSG %M00001

AREA1 DO/DI: SIZE 0ALLOCATION %M00801

ADDRESS 16

SIZE 12 %R0001 of PMC 20

AREA2 DO: %R0002 of PMC 0ALLOCATION %M01281 %R0003 of PMC 64


Table 4-3 Parameters of Node No.20

Item Setting Item Setting

IP ADDRESS 192.168.250.20 AREA2 DI: NODE NAME NODE#20 ALLOCATION %M02401

AREA1 ADDR 20 ALLOC PTR %R00001

AREA1 SIZE 4 CHANGE FLG %M02393

AREA2 ADDR 80 AREA2 ADDR 0

AREA2 SIZE 64 AREA2 SIZE 0

TOKEN WATCH 50 MESSAGE: MIN FRAME 10 ADDRESS %M03601

OWN STATUS %M00993 SIZE 20

ENTRY NODE %M01025 RECV MSG %M00001

AREA1 DO/DI: SIZE 0ALLOCATION %M00801

ADDRESS 16


AREA2 DO: %R0002 of PMC 0ALLOCATION %M01281 %R0003 of PMC 64



167/168


168/168

fanuc fl-net boad operator

Documents