computer numerical controls -...

TECHNOLOGY AND MORETECHNOLOGY AND MORETECHNOLOGY AND MORETECHNOLOGY AND MORE

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

FANUCFANUCFANUCFANUCDeviceNetDeviceNetDeviceNetDeviceNet™™™™ Board Board Board Board

B-63404EN/03B-63404EN/03B-63404EN/03B-63404EN/03

Computer Numerical ControlsComputer Numerical ControlsComputer Numerical ControlsComputer Numerical Controls

Operator’s ManualOperator’s ManualOperator’s ManualOperator’s Manual

B-63404EN/03 SAFETY PRECAUTIONS

s-1

This section describes the safety precautions related to the use of CNC units, to ensure safe operationof machines fitted with FANUC CNC units. Read this section carefully before attempting to use anyfuncction described in this manaul.Users ahould also read the relevant descriptions in the Operator’s Manual to become fully familiarwith the functions to be used.

CONTENTS

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

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

SAFETY PRECAUTIONS

SAFETY PRECAUTION B-63404EN/03

s-2

1 DEFINITION OF WARNING, CAUTION, AND NOTE

This manual includes safety precautions for protecting the user andpreventing damage to the machine. Precautions are classified intoWarnings and Cautions according to their bearing on safety. Also,supplementary information is described as Notes. Read theWarnings, Cautions, and Notes thoroughly before attempting to usethe machine.

WARNINGApplied when there is a danger of the user beinginjured or when there is a danger of both the userbeing injured and the equipment being damaged ifthe approved procedure is not observed.

CAUTIONApplied when there is a danger of the equipmentbeing damaged, if the approved procedure is notobserved.

NOTENotes is used to indicate supplementary informationother than Warnings and Cautions.

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


s-3

2 GENERAL WARNINGS AND CAUTIONS

WARNING1 Before operating the machine, thoroughly check the

entered data. Operating the machine with incorrectlyspecified data may result in the machine behavingunexpectedly, possibly causing damage to theworkpiece and/or machine itself, or injury to the user.

2 Never attempt to machine a workpiece without firstchecking the programmed value, compensationvalue, current position, and external signal settings.Also, never attempt to machine a workpiece withoutfirst checking the operation of the machine. Beforestarting a production run, ensure that the machine isoperating correctly by performing a trial run using, forexample, the single block, feedrate override, ormachine lock function, or by operating the machinewith neither a tool nor workpiece mounted. Failure toconfirm the correct operation of the machine mayresult in the machine behaving unexpectedly,possibly causing damage to the workpiece and/ormachine itself, or injury to the user.

3 Ensure that the specified feedrate is appropriate forthe intended operation. Generally, for each machine,there is a maximum allowable feedrate. Theappropriate feedrate varies with the intendedoperation. Refer to the manual provided with themachine to determine the maximum allowablefeedrate. If a machine is run at other than the correctspeed, it may behave unexpectedly, possiblycausing damage to the workpiece and/or machineitself, or injury to the user.

4 When using a tool compensation function,thoroughly check the direction and amount ofcompensation.Operating the machine with incorrectly specified datamay result in the machine behaving unexpectedly,possibly causing damage to the workpiece and/ormachine itself, or injury to the user.

SAFETY PRECAUTION B-63404EN/03

s-4

WARNING5 The parameters for the CNC and PMC are factory-

set. Usually, there is no need to change them.When, however, there is no alternative other than tochange a parameter, ensure that you fully Failure toset a parameter correctly may result in the machinebehaving unexpectedly, possibly causing damage tothe workpiece and/or machine itself, or injury to theuser.

CAUTION1 Immediately after switching on the power, do not

touch any of the keys on the MDI panel until theposition display or alarm screen appears on the CNCunit.Some of the keys on the MDI panel are dedicated tomaintenance or other special operations. Pressingany of these keys may place the CNC unit in otherthan its normal state. Starting the machine in thisstate may cause it to behave unexpectedly.

2 The operator's manual for DeviceNet boarddescribes all the basic functions of the CNC,including the optional functions. The selectedoptional functions vary with the machine. Somefunctions described in this manual may not,therefore, be supported by your machine. Check themachine specifications before using DeviceNetboard.

3 Some machine operations and screen functions areimplemented by the machine tool builder. For anexplanation of their usage and related notes, refer tothe manual provided by the machine tool builder.For example:• On some machines, executing a tool function

causes the tool change unit to operate. Whenexecuting a tool function on such a machine, standwell clear of the tool change unit. Otherwise, thereis a danger of injury to the operator.

• Many auxiliary functions trigger physicaloperations, such as rotation of the spindle.Before attempting to use an auxiliary function,therefore, ensure that you are fully aware of theoperation to be triggered by that function.


s-5

NOTE• Command programs, parameters, and variables are

stored in nonvolatile memory in the CNC.Generally, the contents of memory are not lost by apower on/off operation. However, the contents ofmemory may be erased by mistake, or importantdata in nonvolatile memory may have to be erasedupon recovering from a failure.To enable the restoration of data as soon as possibleif such a situation arises, always make a backup ofthe data in advance.

B-63404EN/03 TABLE OF CONTENTS

c-1

TABLE OF CONTENTS

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

I. OUTLINE

1 OUTLINE............................................................................................................................................ 3

II. OPERATION

1 DeviceNet FUNCTIONS..................................................................................................................... 9

1.1 OUTLINE......................................................................................................................................... 10

1.2 SETTING MASTER FUNCTIONS................................................................................................. 11

1.2.1 Setting the Bus Parameters .................................................................................................... 14

1.2.2 Setting Slave Parameters........................................................................................................ 23

1.2.3 Starting Communications ....................................................................................................... 32

1.2.4 Master Function Data Refresh Rate....................................................................................... 37

1.3 SETTING SLAVE FUNCTIONS.................................................................................................... 46

1.3.1 Starting Communications ....................................................................................................... 60

1.3.2 Slave Function Data Refresh Rate ......................................................................................... 61

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

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

2.2 HANDLING MULTIPLE-BYTE DATA ......................................................................................... 68

III. CONNECTION

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

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

1.2 DeviceNet CABLES......................................................................................................................... 74

1.3 CABLE LENGTH AND BAUD RATE............................................................................................ 75

1.4 TERMINATOR ................................................................................................................................ 78

1.5 CONNECTOR.................................................................................................................................. 79

1.6 GROUNDING THE CABLE WIRES.............................................................................................. 82

1.7 CABLE CLAMP ............................................................................................................................... 84

1.8 COMMUNICATIONS POWER SUPPLY....................................................................................... 85

1.8.1 Designing a Power Supply Connection................................................................................... 86

1.8.2 Determining the Power Supply Locations.............................................................................. 86

1.8.3 Verification by Graph-Based Simple Calculation .................................................................. 89

TABLE OF CONTENTS B-63404EN/03

c-2

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

1.8.5 Supplying Multiple Power Supplies on Separated Paths...................................................... 97

1.8.6 Relationship with NC Power Supply ...................................................................................... 98

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

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

2.2 INSTALLATION............................................................................................................................ 101

2.2.1 Environmental Conditions .................................................................................................... 101

2.2.2 Leading in Cables .................................................................................................................. 101

2.2.3 Names of Parts on the DeviceNet Board .............................................................................. 102

3 DeviceNet BOARD FOR 16i/18i/21i (STAND-ALONE TYPE), Power Mate i-D/H.......................... 103

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

3.2 INSTALLATION............................................................................................................................ 105


3.3 MOUNTING .................................................................................................................................. 106

3.4 DeviceNet Board B ........................................................................................................................ 107

3.5 DeviceNet Board C ........................................................................................................................ 108

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

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

4.2 INSTALLATION............................................................................................................................ 111


4.3 INSTALLATION............................................................................................................................ 112

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

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

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

1.2 DESCRIPTION OF INDICATOR LEDS...................................................................................... 117

1.3 HOW TO ATTACH AND REMOVE THE DeviceNet BOARD ..................................................... 118

2 DeviceNet BOARD FOR 15i, 16i/18i/21i (STAND-ALONE TYPE), Power Mate i-D/H ......................... 119

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

2.1.1 Layout of Parts....................................................................................................................... 120

2.1.2 Description Of Indicator LEDs ............................................................................................. 121

2.1.3 Short Pin TM1........................................................................................................................ 122

2.1.4 How to Attach and Remove the DeviceNet Board ............................................................... 123

2.2 DeviceNet BOARD B..................................................................................................................... 125

B-63404EN/03 TABLE OF CONTENTS

c-3

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

2.3.1 Layout of Parts....................................................................................................................... 126

2.3.2 Description Of Indicator LEDs ............................................................................................. 127

APPENDIX

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

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

I. OUTLINE

B-63404EN/03 OUTILINE 1.OUTLINE

- 3 -

1 OUTLINE

This manual comprises the following sections:

Descriptions in This ManualSAFETY PRECAUTIONSDescribes the precautions you must observe when you read thismanual.I. OUTLINE

Describes how this manual is organized, applicable models andrelated manuals.

II. OPERATIONDescribes how to set the various data for performing DeviceNetcommunications.

III. CONNECTIONDescribes how to connect the various devices for performingDeviceNet communications and precautions.

IV. MAINTENANCEDescribes the drawing numbers for the DeviceNet board, meaningsof LED indications and error messages.

TrademarkDeviceNet is a trademark of ODVA (OpenDeviceNet Vendor Association).

1.OUTLINE OUTLINE B-63404EN/03

- 4 -

Applicable Machine NamesThis manual covers the following machines.The following abbreviations are sometimes used in text descriptions.

Machine Name AbbreviationFANUC Series 15 i-MA 15i-MAFANUC Series 150 i-MA 150i-MA

Series 15i-A

FANUC Series 16 i-TA 16i-TAFANUC Series 16 i-MA 16i-MAFANUC Series 160 i-TA 160i-TAFANUC Series 160 i-MA 160i-MA

Series 16i-A


Series 18i-A


Series 21i-A

FANUC Series 16 i-TB 16i-TBFANUC Series 16 i-MB 16i-MBFANUC Series 160 i-TB 160i-TBFANUC Series 160 i-MB 160i-MB

Series 16i-B


Series 18i-B


Series 21i-B

FANUC Power Mate i-MODEL D Power Mate i-DFANUC Power Mate i-MODEL H Power Mate i-H

Power Mate i

B-63404EN/03 OUTILINE 1.OUTLINE

- 5 -

Related ManualsThe following tables shows the related manuals for each machinetype.Also refer to these manuals when using this manual.

Series 15i/150i-MA related manualsManual Name Specification Number

Descriptions B-63322ENConnection Manual (Hardware) B-63323ENConnection Manual (Function) B-63323EN-1Operator’s Manual (Programming) B-63324ENOperator’s Manual (Operation) B-63324EN-1Maintenance Manual B-63325ENParameter Manual B-63330EN

Series 16i/18i/160i/180i-TA/MA related manualsManual Name Specification Number

Descriptions B-63002ENConnection Manual (Hardware) B-63003ENConnection Manual (Function) B-63003EN-1Operator’s Manual (For Lathe) B-63004ENOperator’s Manual (For Machining Center) B-63014ENMaintenance Manual B-63005ENParameter Manual B-63010EN

Series 21i/210i-TA/MA related manualsManual Name Specification Number


Series 16i/18i/160i/180i-TB/MB related manualsManual Name Specification Number


1.OUTLINE OUTLINE B-63404EN/03

- 6 -

Series 21i/210i-TB/MB related manualsManual Name Specification Number


Power Mate i-D/H related manualsManual Name Specification Number

Descriptions B-63172ENConnection Manual (Hardware) B-63173ENConnection Manual (Function) B-63173EN-1Operator’s Manual (For Lathe) B-63174ENMaintenance Manual B-63175ENParameter Manual B-63180EN

II. OPERATION

B-63404EN/03 OPERATION 1.DeviceNet FUNCTIONS

- 9 -

1 DeviceNet FUNCTIONS

This chapter describes DeviceNet functions.

1.DeviceNet FUNCTIONS OPERATION B-63404EN/03

- 10 -

1.1 OUTLINE

Unusable Network FunctionsDeviceNet functions cannot be used together with Profibus functions.

Number of networks connectable to NC• LCD-mounted type Series 16i/18i/21i

One DeviceNet communications board can be mounted.The connection to the network is made by one function, eitherthe slave function or master function.

• Stand-Alone type Series 16i/18i/21i Series 15 i -A, and PowerMate i-D/H seriesTwo DeviceNet communications boards can be mounted.Note, however, that when two boards are mounted, one shouldbe used as the slave function and the other should be used as themaster function.

Outline of DeviceNet function specifications(1) Master functions

• Poll I/O Connection is supported.

• Max. number of connected slaves: 32(MAC-ID setup range: 0 to 63)

• Slave assigned addressesThe respective DI/DO signals are assigned continuouslystarting from any address in the R area, with single bytes (8bits) assigned to each address.

• Number of slave DI/DO communication points: Input signal 0 to 32 bytes: Output signal 0 to 32 bytes

(2) Slave function• MAC-ID setup range: 0 to 63

• Assigned addressesDI/DO signals are assigned continuously starting from anyaddress in the R area, with single bytes (8 bits) assigned toeach address.

• Number of DI/DO communication points: Input signal 0 to 64 bytes: Output signal 0 to 64 bytes


- 11 -

1.2 SETTING MASTER FUNCTIONS

To use the DeviceNet master functions, you must set the busparameters and the slave parameters."Bus parameters" are for identifying on the network the DeviceNetinterface board that is currently mounted on the control unit (CNC)."Slave parameters" are for identifying on the network each of theconnected slaves.The bus parameters are used to specify an MAC-ID, baud rate,address assignment information, and information about whether tohold or clear a DI signal related to a communication error(*). Settingthe slave parameters involves setting the MAC-ID, vendor ID, devicetype, product code, connection and DI/DO address assignments of thenode to be connected to each slave No.The following briefly describes each of these items.The "MAC-ID (Media Access Control ID)" is the ID used foridentifying on the network the DeviceNet communications board thatis currently mounted on the CNC.This MAC-ID is set to a value within the range 0 to 63, and must notduplicate the ID of another node on the network.The "baud rate" is the network's communicating speed, and must beset to the same value for each node to be connected to the network."Address assignment" refers to setting of the DI/DO sizes when I/O ofthe DI/DO signals is performed and to setting of the PMC addresses(addresses of R areas) that are used."Vendor ID, device type and product code" are used for specifying thetype of each slave that is connected to the network. If these settingvalues do not match the values specific to each of the actuallyconnected slaves, a connections error will occur."Connection" refers to the connection type with each slave. Normally,set "0". Setting to "0" sets support of Poll I/O Connection.

* See Chapter 2, "Configuring a Safe System" for informationabout whether to hold or clear a DI signal related to acommunication error.


- 12 -

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

Procedure (CRT/MDI)(1) Press function key SYSTEM and then soft key [PMC] to switch to

the PMC screen.

If you press soft keys [PMCDGN] → ([>])→ [I/OCHK] →[D_NET] in that order, the DeviceNet Function initial screen(screen 1.2. (a) below) is displayed.

Screen 1.2 (a)

Table 1.2 shows the display items in the initial screen and adescription of these items.

Table 1.2: Display items in initial screenItem Description

MODULE ID ID of software running on the DeviceNet interfaceboard Example) 0014

MODULE REVISION Version of software running on the DeviceNetinterface board Example) 0209 → Version 2.9

CONTROL SOFTWARE Series and version number of DeviceNet functioncontrol software on NC

I/F MPU REVISION Version of the MPU on DeviceNet slave board C Example) H → Version 08

If options are not set for the master function and slave function,information relating to the corresponding functions and soft keys arenot displayed in the above screen.

In the display example in screen 1.2 (a), both of the options for masterfunction and slave function are already set.


- 13 -

(2) Next, press soft key [MASTER]. The DEVICENET MASTERSETTING screen (screen 1.2 (b)) is displayed.

Screen 1.2 (b)

(3) Switch to either of the following parameter setup screens bypressing soft key [BUS] or [SLAVE], respectively.(a) Bus parameter setup screen [BUS](b) Slave parameter setup screen [SLAVE]

CAUTIONCommunications with the slave are not established ifsetup of the bus parameters is not completed.Normally, set up the bus parameters before you setup the slave parameters.

Descriptions here on regarding parameter setup assume that each ofthe nodes are connected to the network and the setup required forcommunications (e.g. MAC-ID of each slave and baud rate settings)are completed.For details on how to set up the slave, refer to the manual for thedevice you are using.


- 14 -

1.2.1 Setting the Bus Parameters

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

Pressing soft key [BUS] in screen 1.2 (b) displays screen 1.2.1(a).

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

In the following description, let's set the node No. of this master node,baud rate and the area for storing the status information for verifyingthe communications status on the PMC.

You can enter setting values in this screen provided that the followingconditions are satisfied:

(a) Setting parameter PWE must be set to "1".(b) The unit must be in the MDI mode or in an emergency stop

state.(c) DISABLE must be selected at the "1 DIS/ENB" item.


- 15 -

Setting Bus Parameters on the Series 15i-A

Set each parameter on the bus parameter setup screen.

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

On this screen, specify the node No. of this master node, its baud rate,and the area for storing the status information for verifying the statusof communication on the PMC.


<1> Bit 0 (PWE) of setting parameter No. 8000 = 1<2> The unit is in the MDI mode or at an emergency stop.<3> DISABLE is selected at "DISABLE/ENABLE."

If no option is set for the master or slave function, the above screendisplays neither information nor a soft key related to thecorresponding function.Screen 1.2.1 (b) is an example of specifying options of both themaster and slave functions.


- 16 -

Display proceduresProcedure 1

(1) Press function key SYSTEM repeatedly until the bus parameter

screen, slave parameter screen, or slave function setup screen isdisplayed.

(2) If the slave parameter screen or slave function setup screen isdisplayed, press soft key [BUS PARAM] in the operationselection menu.

Procedure 2

(1) Press function key SYSTEM or soft key [SYSTEM].

(2) Press soft key [CHAPTER] repeatedly until [DEVICENET] isdisplayed.

(3) Press soft key [DEVICENET].(4) If the slave parameter screen or slave function setup screen is

displayed, press [BUS PARAM] in the operation selection menu.

Cursor/paging1 Move the cursor using the cursor keys .

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

moves the cursor to "DISABLE/ENABLE" in the

slave parameter screen for slave No. 001.- If the cursor is at "DISABLE/ENABLE," pressing cursor

key moves the cursor to "DI SIZE" in the slave

parameter screen for slave No. 032.If the slave function is enabled, the slave function setupscreen is displayed.

2 Pressing page key PAGE displays the slave parameter screen for

slave No. 001.

Pressing page key PAGE displays the slave parameter screen for

slave No. 032.If the slave function is enabled, the slave function setup screen isdisplayed.


- 17 -

Diagnosis Information on the Bus Parameters Setting Screen

STATUS and COMMUNUNICATION STATUS are displayed in busparameter setting screen as diagnostics information used for verifyingthe communications status.Table 1.2.1 (b) describes this diagnostics information.

Setting the MAC-ID and baud rateSet the node number "2. MAC-ID" of this master node and the baudrate "3. BAUD RATE" to appropriate values referring to items 2 and3 in Table 1.2.1 (a).

Assigning status informationSet to parameters the addresses and sizes of the R areas to whichstatus information data is to be assigned.The content up to the STATUS SIZE setting value items (see Table1.2.1 (c)) is assigned continuously starting from the specified R areasignal.For example, to assign eight bytes of status information from R1500onwards, set each of the data items as follows in screen 1-5.

4 STATUS ADDRESS = R15005 STATUS SIZE = 8

Status information is assigned to R area signals as follows accordingto this setting.

Status Information AssignmentsR1500 STATUS informationR1501 Slave communications status 1R1502 Slave communications status 2R1503 Slave communications status 3R1504 Slave communications status 4R1505 IDLE/ACTIVE informationR1506 CAN BUS STATUS 1 informationR1507 CAN BUS STATUS 2 information

On the PMC, start communications with the slaves using this statusinformation (STATUS information, slave communication status, etc.).Also use this status information to process on the PMC anycommunications errors that may occur.The error status of this status information is returned to the normalcommunications status when the cause of the error is removed. So, ifthe error status must be held, perform this operation on the PMC.

CAUTIONWhen you set the assignment data, carefully set thedata so that areas to be secured as data do notduplicate areas that are currently used for ladderprograms on the PMC.


- 18 -

Table 1.2.1 (a): Bus parameter setup itemsItem Description

1.DIS/ENB(DISABLE/ENABLE)

Sets whether to disable or enablecommunications.Move the left and right cursor keys to select thisparameter setting. (For the 15i-A, use soft keys.)Set ENABLE after setting of the master functionparameters is completed.Communications is started several seconds aftersetting ENABLE. ENABLE : Enables communications. DISABLE : Disables communications.

2.MAC-ID Sets the number for identifying on the network theDeviceNet interface board mounted on the controlunit (CNC).Set a number that does not duplicate the MAC-IDof other nodes on the network within the range 0 to63.(MAC-ID: Media Access Control ID)

3.BAUD-RATE Sets the baud rate.The setting range is 0 to 2.The baud rate for each setting is as follows: 0: 125 kbps 1: 250 kbps 2: 500 kbpsThe baud rate is limited by the maximum networklength and other factors. For details, refer to"Connecting DeviceNet Functions" in theConnections Manual.

4.STATUS ADDRESS5.STATUS SIZE

Set the areas to be used as the status informationdata buffer.Set the leading buffer address and buffer size.Use the R area as the address to be set.Size setting range: 0 to 8

6.DI HOLD/CLEARNote) See Chapter 2,

"Configuring aSafe System."

Specify whether to hold or clear DI data ifcommunication is abnormal.0: To hold DI data.1: To clear DI data.


- 19 -

Table 1.2.1 (b): Diagnostics information(STATUS/COMMUNICATION STATUS)

Item DescriptionSTATUS: DISABLE : Disables communications.

ENABLE : Enables communications.(normal communicationsstatus)

ERROR : Communications error hasoccurred.Check COMMUNICATIONSTATUS and the status ofthe master device.

INVALID MAC ID : The MAC-ID is not setcorrectly.

DUPLICATE MAC ID : Duplicate MAC-IDs havebeen set.

BUS FAULT : Bus error has occurred.POWER ON ERROR : An error occurred when

the power was turned ONor when ENABLE was set.Check the DeviceNetinterface board mountingstate.

COMMUNICATIONSTATUS:IDLE/ACTIVE

Indicates the status of the Group 2 Master/SlaveConnection Set. "01" indicates an active state.

00: IDLE state(Group 2 Master/Slave Connection Set is notestablished.)

01: ACTIVE state(Group 2 Master/Slave Connection Set isestablished.)

COMMUNICATIONSTATUS:CAN BUS STATUS1

Indicates the status information of the CAN(Controller Area Network) bus. Status informationis expressed in hexadecimal with 1 byteexpressing each item of information. Each of thebits of the status information is significant.

CAN BUS STATUS1 (1byte Data)

#7 #6 #5 #4 #3 #2 #1 #0[ML] [RO] [TO] [TA] [A] [BO] [BW] [OL]

The meaning of ‘1’ of each bit is as follows.(Values in parentheses () indicate values in thenormal communications status.)#01 OL (1) : Online state#1 BW (0) : Bus warning state

A communications error hasoccurred, and the CAN chipautomatically stopped frame transfer.Probable causes are an incorrectbaud rate setting or noise.


- 20 -

Table 1.2.1 (b) (continued): Diagnostics information(STATUS/COMMUNICATION STATUS)

Item DescriptionCOMMUNICATIONSTATUS:CAN BUS STATUS1

#2 BO (0) : Bus OFF stateA communications error hasoccurred, and the CAN chipautomatically turned offline. Probablecauses are an incorrect baud ratesetting or a hardware malfunction.

#3 A (1) : Network is active.Data is being sent and received.

#4 TA (0) : Response error stateThere is no response from thecommunications destination within 25to 50 msec. The communicationsdestination node may not exist on thenetwork.

#5 TO (0) : Time-out stateHigh priority data may be beingtransferred excessively.

#6 RO (0) : Receive buffer overrun has occurred.#7 ML (0) : Message lost has occurred.CAN BUS STATUS2 (1byte Data)

#7 #6 #5 #4 #3 #2 #1 #0

COMMUNICATIONSTATUS:CAN BUS STATUS2 [SA] [05] [02] [01] [--] [--] [BP] [ER]

The meaning of ‘1’ of each bit is as follows.(Values in parentheses () indicate values in thenormal communications status.)#0 ER (0) : A CAN communications error has

occurred.A probable cause is noise or ahardware malfunction.

#1 BP (1) : Network power ON state#2 --#3 --#4 01 : Baud rate is 125 kbps.#5 02 : Baud rate is 250 kbps.#6 05 : Baud rate is 500 kbps.#7 SA (1) : The network scanner is active.


- 21 -

Table 1.2.1 (c): Relationship between STATUS SIZE setting valuesand STATUS information

SettingValue

Item Description

1 STATUS information This 1-byte data notifies the PMC of thecommunications status.00h : Disables communications.01h : Enables communications. (normal

communications status)03h : Communications error has

occurred.For details, check theCOMMUNICATION STATUS andstatus of the master device.

82h : Illegal MAC-ID84h : Duplicate MAC-ID8Eh : Bus error has occurred.8?h : An error other than the above

occurred at start ofcommunications.

This 1-byte data indicates thecommunications status with each nodehaving slave No. 1 to 8 in each of itsrespective eight bits.

Bit #7 #6 #5 #4 #3 #2 #1 #0Node 8 7 6 5 4 3 2 1

2 Slave communicationsstatus 1(slave No. 1 to 8)

Communications status (common to allbits) 1: Enables communications. (normal

communications status) 0: Disables communications.This 1-byte data indicates thecommunications status with each nodehaving slave No. 9 to 16 in each of itsrespective eight bits.

Bit #7 #6 #5 #4 #3 #2 #1 #0Node 16 15 14 13 12 11 10 9



communications status) 0: Disables communications.


- 22 -

Table 1.2.1 (c) (continued): Relationship between setting values ofSTATUS SIZE and STATUS information

SettingValue

Item Description

This 1-byte data indicates thecommunications status with each nodehaving slave No. 17 to 24 in each of itsrespective eight bits.

Bit #7 #6 #5 #4 #3 #2 #1 #0Node 24 23 22 21 20 19 18 17

Slave communicationsstatus 3(slave No. 17 to 24)

4

Slave communicationsstatus 3(slave No. 17 to 24)


communications status) 0: Disables communications.This 1-byte data indicates thecommunications status with each nodehaving slave No. 25 to 32 in each of itsrespective eight bits.

Bit #7 #6 #5 #4 #3 #2 #1 #0Node 32 31 30 29 28 27 26 25



communications status) 0: Disables communications.

6 COMMUNICATIONSTATUS:IDLE/ACTIVEinformation

This 1-byte data notifies the PMC of thestate of Group 2 Master/SlaveConnection Set of the DeviceNet. 00h: IDLE state 01h: ACTIVE stateThis 1-byte data notifies the PMC ofCAN BUS STATUS1 information.

#7 #6 #5 #4 #3 #2 #1 #0[ML] [RO] [TO] [TA] [ A ] [BO] [BW] [OL]

7 COMMUNICATIONSTATUS: CAN BUSSTATUS1 information

For details, refer to the CAN BUSSTATUS1 information described above.This 1-byte data notifies the PMC ofCAN BUS STATUS2 information.

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


For details, refer to the CAN BUSSTATUS1 information described above.


- 23 -

1.2.2 Setting Slave Parameters

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

Pressing soft key [SLAVE] in the DEVICENET MASTER SETTINGinitial screen (screen 1.2 (a)) displays the slave parameter setupscreens (screens 1.2.2 (a) and 1.2.2 (b)).

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

Screen 1.2.2 (b) Bus parameter setup screen (Series 16i/18i/21i-A/B) (2)

Switch between screensusing pagekeys .↑ ↓


- 24 -

Select the slave No. whose parameters are to be set by using soft keys[PRV.NO] and [NXT.NO].Table 1.2.2 (a) describes the parameters that are set in these screens.

You can enter setting values in these screens provided that thefollowing conditions are satisfied:


state.(c) "DISABLE" must be selected at the "1 DIS/ENB" item.


- 25 -

Setting Slave Parameters on the Series 15i-A

In the slave parameter screen, specify slave parameters and addressassignment.

Screen 1.2.2 (c) Bus parameter setup screen (Series 15i-A)

Table 1.2.2(a) lists the parameters to be set up in this screen.

You can enter setting values in this screen provided that the followingconditions are satisfied:<1> Bit 0 (PWE) of setting parameter No. 8000 = 1<2> The unit is in the MDI mode or at an emergency stop.<3> DISABLE is selected at "DISABLE/ENABLE."

Display procedures

Procedure 1



(2) If the bus parameter screen or slave function setup screen isdisplayed, enter the desired slave number, and press soft key[SLAVE PARAM].

Procedure 2



(3) Press soft key [DEVICENET].(4) If the bus parameter screen or slave function setup screen is

displayed, enter the desired slave number, and press soft key[SLAVE PARAM].


- 26 -


- If the cursor is on a "DO SIZE" line, pressing cursor key

moves the cursor to "DISABLE/ENABLE" for the

next slave number.If the cursor is on the last "DO SIZE" line for slave No. 032,pressing the cursor key moves the cursor to"DISABLE/ENABLE" in the bus parameter screen.If the slave function is enabled, the slave function setupscreen is displayed.

- If the cursor is at "DISABLE/ENABLE," pressing cursor

key moves the cursor to "DO SIZE" for the previous

slave number.If the cursor is at "DISABLE/ENABLE" for slave No. 001,pressing the cursor key moves the cursor to "DIHOLD/CLEAR" in the bus parameter screen.If the slave function is enabled, the slave function setupscreen is displayed.

2 Pressing page keys PAGEPAGE displays the slave parameter

screen for the previous or next slave number, respectively.- In the slave parameter screen for slave No. 001, pressing page

key PAGE displays the slave parameter screen for slave No. 002.

- In the slave parameter screen for slave No. 032, pressing page

key PAGE displays the bus parameter screen.

If the slave function is enabled, the slave function setup screen isdisplayed.

- In the slave parameter screen for slave No. 001, pressing page

key PAGE displays the bus parameter screen.

The following procedures can display the slave parameter screenfor the specified slave number.

Procedure 1(1) Press soft key [SLAVE PARAM].(2) Key in the desired slave number.(3) Press soft key [EXEC].

Procedure 2(1) Key in the desired slave number.(2) Press soft key [SLAVE PARAM].


- 27 -

(1) To proceed to "3 VENDOR ID", "4 DEVICE TYPE" and "5PRODUCT CODE", set the respective vendor ID, device typeand product code. These setting values are referenced to asvalues specific to the connected slave. If the setting values donot match the values specific to the connected slave, an error(s)occurs. Note, however, that setting of these items is arbitrary.(Communications will not be influenced if these setting valuesare left at their "0000" settings. If these setting values are set to"0000," the slaves will not be referenced.)In a normal communications state with the connected slaves,these values can be read and the respective items automaticallyset by operating soft key [INIT].(Refer to "1.2.3 Starting communications, Automatic setting ofslave parameters.")

(2) To proceed to "6 CONNECTION" set "0". The connection typewith the slave is Poll I/O Connection. Also set the connectiontype on the slave device to Poll I/O Connection.

STATUS and CONDITION are displayed in this screen as diagnosticsinformation used for verifying the communications status.Table 1.2.2 (b) describes this diagnostics information.


- 28 -

Table 1.2.2 (a): Slave parameter setup itemsItem Description

1 DIS/ENB(DISABLE/ENABLE)

Sets whether to disable or enable communicationswith the node having the selected slave No.Move the left and right cursor keys to select thisparameter setting. (Soft keys are used in the 15i-A.)Set ENABLE after setting of the master functionparameters is completed.Communications is started several seconds aftersetting ENABLE. DISABLE : Disables communications. ENABLE : Enables communications.

2 MAC-ID Sets the number for identifying on the network theslave to be connected.Set a number that does not duplicate the MAC-IDof other nodes on the network within the range 0 to63.(MAC-ID: Media Access Control ID)

3 VENDOR ID 4 DEVICE TYPE 5 PRODUCT CODE

Set the vendor ID/device type/product code of theslave to be connected.Set in hexadecimal within the range 0000 to FFFF.(default: 0000)These setting values are used for specifying thetype of connected type. If the setting value doesnot match the value specific to the connectedslave, an error (INVALID VENDOR ID/INVALIDDEVICE TYPE/INVALID PRODUCT CODE)occurs. Note, however, that this error is notdetected when the setting value is set to "0000".Also, as nodes on the network are identified by aMAC-ID, communications is performed normallyeven if the setting value of these items is set to"0000".In a normal communications state, the values ofthese items can be read from the connected slaveand the read values automatically set to therespective items by operating soft key [INIT].

6 CONNECTION Sets the connection type with the slave."0" must be set.Setting to "0" sets the connection type with theslave to Poll I/O Connection.

7 DI ADDRESS 8 DI SIZE 9 DO ADDRESS10 DO SIZE

Set the areas to be used as the DI/DO data buffer.Set the leading buffer address and buffer size.Use the R area as the address to be set.Size setting range: 0 to 32


- 29 -

Table 1.2.2 (b): Diagnostics information (STATUS/CONDITION)Item Description

STATUS Displays the communications status.DISABLE : Disables communications.ENABLE : Enables communications.ERROR : Communications error has

occurred.For details, check CONDITION,status of COMMUNICATIONSTATUS in the bus parameterscreen, and the status of themaster function.

INVALID MAC ID : The MAC-ID is not set correctly.DUPLICATE MAC ID : Duplicate MAC-IDs have been set.DUPLICATE DEVICE : A MAC-ID duplicating the bus

parameter has been set.INVALID CONNECTION : Connection by the correct I/O

Connection is not made.The connection by theseDeviceNet master functions is PollI/O Connection.

POWER ON ERROR : An error occurred when the powerwas turned ON or when ENABLEwas set.Check the network cableconnections or DeviceNet interfaceboard mounting state.

CONDITION Displays the states of the connected slaves.(00) DISABLE : Disables communications.(01) IDLE : Network scan standby state(02) DEVICE BEING SCANED : Normal communications

statusScanning of connectedslaves is being performedcorrectly.

(03) TIMED-OUT : Time-out stateThere is no response fromthe slaves.

(04) CONNECTION ERROR : The UCMM (UnconnectedMessage Manager)connection cannot beperformed correctly.

(05) CONNECTION BUSY : Master/Slave connection isbusy.

(06) CONNECTION ERROR : Master/Slave connectioncannot be established.

(07) INVALID VENDOR ID : The vendor ID of thecurrently connected slavediffers from the parametersetting value.

(08) VENDOR ID ERROR : The vendor ID of thecurrently connected slavecannot be read.


- 30 -

Table 1.2.2 (b) (continued): Diagnostics information(STATUS/CONDITION)

Item DescriptionCONDITION(continued)

(09) INVALID DEVICE TYPE : The device type of thecurrently connected slavediffers from the parametersetting value.

(0A) DEVICE TYPE ERROR : The device type of thecurrently connected slavecannot be read.

(0B) INVALID PRODUCT CODE: The product code of thecurrently connected slavediffers from the parametersetting value.

(0C) PRODUCT CODE ERROR : The product code of thecurrently connected slavecannot be read.

(0D) INVALID INPUT SIZE : The DI size of the currentlyconnected slave differsfrom the DI SIZEparameter setting value.

(0E) INPUT SIZE ERROR : The DI size of the currentlyconnected slave cannot beread.

(0F) INVALID OUTPUT : The DO size of thecurrently connected slavediffers from the DO SIZEparameter setting value.

(10) OUTPUT SIZE ERROR : The DO size of thecurrently connected slavecannot be read.

(17) SYNC FAULT : Failed to synchronizeMaster/Slave connection.

(??) ERROR : Other error state

Assigning DI/DO addressesSet to parameters the addresses and sizes of the R areas to whichDI/DO areas are to be assigned. For example, to assign six bytes of DIdata (data input to the CNC from the slave) to R1000 onwards andassign two bytes of DO data (data output from the CNC to the slave)to R1100 onwards, set each of the data items as follows in screen1.2.2 (b).

4 DI ADDRESS = R10005 DI SIZE = 66 DO ADDRESS = R11007 DO SIZE = 2

DI/DO is assigned to R area signals as follows according to thissetting.


- 31 -

DI AssignmentsR1000 1st DI data from slaveR1001 2nd DI data from slaveR1002 3rd DI data from slaveR1003 4th DI data from slaveR1004 5th DI data from slaveR1005 6th DI data from slave

DO AssignmentsR1100 1st DO data to slaveR1101 2nd DO data to slave

When a DI only slave or a DO only slave is connected, set the valueof the parameter that specifies the size of the unused DO or DI to "0".

CAUTIONWhen you set the assignment data, carefully set thedata so that areas to be secured as each assigneddata item are not duplicated. Also, thoroughly checkbefore setting to prevent areas that are currentlyused for other slave assignment addresses and PMCladder programs from being duplicated.


- 32 -

1.2.3 Starting CommunicationsAfter you have finished setting up the bus parameters and slaveparameters, start communications by selecting ENABLE at the "1DIS/ENB" item. Move the cursor from DISABLE to ENABLE. Aftera few seconds, communications is started, and the STATUS displaychanges to ERROR and the CONDITION display changes to (01)IDLE as shown in screens 1.2.3 (a) and (b) below.

Case of the Series 16i/18i/21i-A/B

Screen 1.2.3 (a) Case of Series 16i/18i/21i-A/B

Case of the Series 15i-A

Screen 1.2.3 (b) Case of Series 15i-A


- 33 -

When communications with the currently connected slave isperformed normally, the STATUS display changes to ENABLE andthe CONDITION display changes to (02) DEVICE BEINGSCANNED. (See screens 1.2.3 (c) and (d) below.)


Screen 1.2.3 (c) Case of Series 16i/18i/21i-A/BTo continue setting other slave parameters, press soft key [PRV.NO]or [NXT.NO] to change the slave No. Up to 32 slaves can be set.


Screen 1.2.3 (d) Case of Series 15i-A


- 34 -

To set up another slave parameter, press page keys PAGEPAGE to

switch to that slave number.

Cursor operations and switching of screens are not possible forseveral seconds until the connection for communications isestablished.


- 35 -

Automatic setting of slave parametersYou can automatically set "3 VENDOR ID", "4 DEVICE TYPE" and"5 PRODUCT CODE" by pressing soft key [INIT] in screen 1.2.3 (b)in a normal communications state (STATUS display: ENABLE,CONDITION display: (02) DEVICE BEING SCANNED).


When you press soft key [INIT], soft keys [YES] and [NO] aredisplayed. (See screens 1.2.3 (e) and (f) below.)

Screen 1.2.3 (e) Case of Series 16i/18i/21i-A/B

Next, press soft key [YES] to automatically set these items.


- 36 -


Pressing soft keys [INIT] → [EXEC] enables "VENDOR ID,""DEVICE TYPE," and "PRODUCT CODE" to be set upautomatically.

Screen 1.2.3 (f) Case of Series 15i-A

CAUTIONAutomatic setting of parameters is not performedwhen communications is not being performednormally.


- 37 -

1.2.4 Master Function Data Refresh Rate

The "data refresh rate" is the time required for the control unit (CNC)to update all I/O signals assigned to the R areas.

CAUTIONThe data refresh rate does not indicate the I/Oresponse time on the network. The I/O responsetime is dependent on the condition of the network.

Refreshing of I/O signals in the master function is performed every 8msec at a maximum of 32 bytes for both DI and DO. In other words,the data refresh rate changes as shown in the following tableaccording to the number of communications points on each slave.

Table 1.2.4 (a)Total Number of Slave Communications Points Data Refresh Rate

1 to 32byte 8ms33 to 64byte 16ms65 to 96byte 24ms

In the same way from here on, the data refresh rate is extended by 8 ms at atime as the total number of slave communications points increases by 32bytes.

For example, the total DI size becomes 68 bytes when the sizes of theDI/DO signals on each slave are set as follows. (See table below.)

Table 1.2.4 (b)Slave No. DI Size DO Size

1 16 02 16 163 0 84 8 85 24 06 4 0

Total DI/DO size 68 32

At this time, as the data refresh rate of the DI signal is 24 msec andthe total DO size is 32 bytes according to Table 1.2.4 (a), the datarefresh rate of DO signals becomes 8 msecs. In this instance, the timeuntil all DI/DO signals are updated becomes the slower time of 24msec.


- 38 -

Setting Master Functions on Power Mate i-D/H

On the Power Mate i-D/H, master functions can be set using theregular parameters, and you can confirm "STATUS" and"CONDITION" in the regular diagnostics screen.

NOTE1 When the DeviceNet parameters have been set, the

power must be turned OFF temporarily.2 In the case of Power Mate i-D two-path control,

setting and diagnostics can be performed only fromthe 1st path.

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

Procedure when using DPL/MDI(1) Press the DGNOS

PARAM key to switch to the parameter screen.

(2) Set the parameters described later in the same way as regularparameters.

(3) Press the DGNOS

PARAM key to switch to the diagnostics screen.

(4) Check the diagnostics numbers described later.

Procedure when using the DPL/MDI operation package (PC)(1) Press the F4

PRMDGN key to switch to the parameter screen.


(3) Press the F4

PRMDGN key to switch to the diagnostics screen.

(4) Check the diagnostics numbers described later.


- 39 -

Parameters28100 Enable/disable communications

DI16

[Data type] Byte[Data range] 0, 1

Sets whether to disable or enable communications. Communicationsis started when this parameter is set to "1" and the power is turned ONagain.This parameter is equivalent to the "1 DIS/ENB" setting in screen1.2.1(a) or 1.2.1(b).

Setting Value Meaning0 Disables communications.1 Enables communications.

28101 MAC-IDDI16

[Data type] Byte[Data range] 0 to 63

Sets the number for identifying on the network the DeviceNetinterface board mounted on the control unit (CNC).Set a number that does not duplicate the MAC-ID of other nodes onthe network within the range 0 to 63.(MAC-ID: Media Access Control ID)This parameter is equivalent to the "2 MAC-ID" setting in screen1.2.1(a) or 1.2.1(b).

28102 Baud rateDI16


Sets the baud rate. The baud rate is limited by the maximum networklength and other factors. For details, see the "Connecting theDeviceNet Functions" item in the Connections section.This parameter is equivalent to the "3 BAUD-RATE" setting in screen1.2.1(a) or 1.2.1(b).

Setting Value Baud rate0 125Kbps1 250Kbps2 500Kbps

28116 Status information data buffer area

[Data type] Byte[Data range] 0

Sets the area to be used as the status information data buffer. Use theR area as the address to be set.This parameter is equivalent to the buffer area setting in "4 STATUSADDRESS" in screen 1.2.1(a) or 1.2.1(b).

Setting Value Buffer Area0 R area


- 40 -

28117 Status information data buffer address

[Data type] Word[Data range] 0 to (value obtained by subtracting the setting value of No.28118 from

the maximum value of the R area)Sets the leading address of the status information data buffer.This parameter is equivalent to the buffer address setting in "4STATUS ADDRESS" in screen 1.2.1(a) or 1.2.1(b).

28118 Status information data buffer size


Sets the size of the status information data buffer.This parameter is equivalent to the "5 STATUS SIZE" setting inscreen 1.2.1(a) or 1.2.1(b).

28119 Holding/Clearing the DI data


Sets the state of the DI data when communication is not normal.This parameter is equivalent to the "6 HOLD/CLEAR" setting inscreen 1.2.1(a) or 1.2.1(b).

Setting Value Meaning0 Holding the DI data1 Clearing the DI data

28200 Disable/enable communications with slave No.1.


Sets whether to disable or enable communications with the slave No.1node. Communications is started when this parameter is set to "1" andthe power is turned ON again.This parameter is equivalent to the "1 DIS/ENB" setting in screen1.2.2(a) or 1.2.1(c).


28201 MAC-ID of slave No.1


Sets the number for identifying the slave to be connected.Set a number that does not duplicate the MAC-ID of other nodes onthe network within the range 0 to 63.(MAC-ID: Media Access Control ID)This parameter is equivalent to the "2 MAC-ID" setting in screen1.2.2(a) or 1.2.1(c).


- 41 -

28203 Vendor ID of slave No.1

28204 Device type of slave No.1

28205 Product code of slave No.1

[Data type] Word[Data range] 0 to 65535

Sets the vendor code/device type/product code of the slave to beconnected. Set this parameter in decimal (default=0). This setting isused to specify the type of connected slave. If the setting value doesnot match the value specific to the connected slave, an error(INVALID VENDOR ID/INVALID DEVICE TYPE/INVALIDPRODUCT CODE) occurs. Note, however, that this error is notdetected when the setting value is set to "0". Also, as nodes on thenetwork are identified by a MAC-ID, communications is performednormally even if the setting value of this parameter is set to "0".This parameter is equivalent to the "3 VENDOR ID" / "4 DEVICETYPE" / "5 PRODUCT CODE" settings in screen 1.2.2(a) or 1.2.1(c).

28206 Connection type of slave No.1


Sets the connection type with the slave. "0" must be set. Setting to "0"sets the connection type with the slave to Poll I/O Connection.This parameter is equivalent to the "6 CONNECTION" setting inscreen 1.2.2(a) or 1.2.1(c).

Setting Value Connection Type0 Poll I/O Connection

28210 DI data buffer area of slave No.1


Sets the area to be used as the DI data buffer. Use the R area as theaddress to be set. This parameter is equivalent to the buffer areasetting in "7 DI ADDRESS" in screen 1.2.2(b) or 1.2.1(c).


28211 DI data buffer address of slave No.1


the maximum value of the R area)Sets the area to be used as the DI data buffer. Set the leading addressof the buffer.This parameter is equivalent to the buffer address setting in "7 DIADDRESS" in screen 1.2.2(b) or 1.2.1(c).


- 42 -

28212 DI data buffer size of slave No.1


Sets the area to be used as the DI data buffer. Set the size of the bufferwithin the range 0 to 32.This parameter is equivalent to the "8 DI SIZE" setting in screen1.2.2(b) or 1.2.1(c).

28213 DO data buffer area of slave No.1


Sets the area to be used as the DO data buffer. Set the leading addressof the buffer.This parameter is equivalent to the buffer area setting in "9 DOADDRESS" in screen 1.2.2(b) or 1.2.1(c).


28214 DO data buffer address of slave No.1


the maximum value of the R area)Sets the area to be used as the DO data buffer. Set the leading addressof the buffer.This parameter is equivalent to the buffer address setting in "9 DOADDRESS" in screen 1.2.2(b) or 1.2.1(c).

28215 DO data buffer size of slave No.1


Sets the area to be used as the DO data buffer. Set the size of thebuffer within the range 0 to 32.This parameter is equivalent to the "10 DO SIZE" setting in screen1.2.2(b) or 1.2.1(c).

From here on, parameter numbers for slave number n (where, n=1 to32) are numbers obtained by adding (n-1) x 20 to the parameternumber of slave No.1.


- 43 -

28200+(n-1)×20

Enable/disable communications with slave No. n

28201+(n-1)×20

MAC-ID of slave No. n

28203+(n-1)×20

Vendor ID of slave No. n

28204+(n-1)×20

Device type of slave No. n

28205+(n-1)×20

Product code of slave No. n

28206+(n-1)×20

Connection type of slave No. n

28210+(n-1)×20

DI data buffer area of slave No. n

28011+(n-1)×20

DI data buffer address at slave No. n

28012+(n-1)×20

DI data buffer size at slave No. n

28013+(n-1)×20

DO data buffer area at slave No. n

28014+(n-1)×20

DO data buffer address at slave No. n

28015+(n-1)×20

DO data buffer size at slave No. n


- 44 -

Diagnostics900 Communications status of slave No.1

Indicates the communications status of slave No.1.This diagnostic is equivalent to the "STATUS" setting in screens1.2.2 (a), 1.2.2 (b) and 1.2.2(c).

ValueDisplay on Screens

1.2.2 (a), 1.2.2 (b) and 1.2.2(c)Meaning

0 DISABLE Disables communications. 1 ENABLE Enables communications. 2 Reserved 3 ERROR Communications error has occurred.

For details, check CONDITION, status of STATUS information (R area)and the error status of the slave device.

129 Reserved130 INVALID MAC ID The MAC-ID is not set correctly.131 Reserved132 DUPLICATE MAC ID Duplicate MAC-IDs have been set.133 DUPLICATE DEVICE A MAC-ID duplicating the bus parameter has been set.134135136137138139140141142

Reserved

143 INVALID CONNECTION Connection by the correct I/O Connection is not made.The connection by these DeviceNet master functions is Poll I/OConnection.

144145146

Reserved

POWER ON ERROR An error occurred when the power was turned ON or when ENABLE wasset.Check the network cable connections or DeviceNet interface boardmounting state.


- 45 -

901 Status of slave No.1

Indicates the status of slave No.1.This diagnostic is equivalent to the "CONDITION" setting in screens1.2.2 (a), 1.2.2 (b) and 1.2.2(c).

ValueDisplay on Screens

1.2.2 (a), 1.2.2 (b) and 1.2.2(c)Meaning

0 DISABLE Disables communications.1 IDLE Network scan standby state2 DEVICE BEING SCANNED Normal communications status

Scanning of connected slaves is being performed correctly.3 TIMED-OUT Time-out state

There is no response from the slaves.4 CONNECTION ERROR The UCMM (Unconnected Message Manager) connection cannot be

performed correctly.5 CONNECTION BUSY Master/Slave connection is busy.6 CONNECTION ERROR Master/Slave connection cannot be established.7 INVALID VENDOR ID The vendor ID of the currently connected slave differs from the parameter

setting value.8 VENDOR ID ERROR The vendor ID of the currently connected slave cannot be read.9 INVALID DEVICE TYPE The device type of the currently connected slave differs from the

parameter setting value.10 DEVICE TYPE ERROR The device type of the currently connected slave cannot be read.11 INVALID PRODUCT CODE The product code of the currently connected slave differs from the

parameter setting value.12 PRODUCT CODE ERROR The product code of the currently connected slave cannot be read.13 INVALID INPUT SIZE The DI size of the currently connected slave differs from the DI SIZE

parameter setting value.14 INPUT SIZE ERROR The DI size of the currently connected slave cannot be read.15 INVALID OUTPUT SIZE The DO size of the currently connected slave differs from the DO SIZE

parameter setting value.16 OUTPUT SIZE ERROR The DO size of the currently connected slave cannot be read.23 SYNC FAULT Failed to synchronize Master/Slave connection.?? ERROR Other error state

From here on, diagnostics numbers for slave number n (where, n=1 to32) are numbers obtained by adding (n-1) x 2 to the diagnosticsnumber of slave No.1.

900+(n-1)×2

Communications status of slave No. n

901+(n-1)×2

Status of slave No. n


- 46 -

1.3 SETTING SLAVE FUNCTIONS

To use the DeviceNet slave functions, you must set the MAC-ID,baud rate and address assignments.The "MAC-ID (Media Access Control ID)" is the ID used foridentifying on the network the DeviceNet communications board thatis currently mounted on the CNC.This MAC-ID is set to a value within the range 0 to 63, and must notduplicate the ID of another node on the network. The "baud rate" isthe network's communicating speed. Set the same value as the baudrate currently set for communications on the network. (Refer to thebaud rate setting of the master device currently used on the network.)"Address assignment" refers to setting of the DI/DO sizes when I/O ofthe DI/DO signals is performed and to setting of the PMC addresses(addresses of R areas) that are used.

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

Procedure (CRT/MDI)(1) Press function key SYSTEM and then soft key [PMC] to switch to

the PMC screen.

(2) If you press soft keys [PMCDGN] → ([>])→ [I/OCHK] →[D_NET] in that order, the DeviceNet Function initial screen(screen 1.2 (a) below) is displayed.If you press [SLAVE] in this screen, the slave function setupscreen (screen 1.3(a) or 1.3(c)) is displayed.



state.(c) "DISABLE" must be selected at the "1 DIS/ENB" item.

Table 1.3(a) shows the setting items in this screen.STATUS and COMMUNUNICATION STATUS are displayed in thisscreen as diagnostics information used for verifying thecommunications status.Table 1.3(b) describes this diagnostics information.


- 47 -

Screen 1.3 (a) Slave functions setting screen (Series 16i/18i/21i-A) (1)

Screen 1.3 (b) Slave functions setting screen (Series 16i/18i/21i-A) (2)

Switch between screensusing page keys .↑ ↓


- 48 -

Setting Slave Functions on Series 15i-A

Screen 1.3 (c) Slave functions setting screen (Series 15i-A)

You can enter setting values in this screen provided that the followingconditions are satisfied:<1> Bit 0 (PWE) of setting parameter No. 8000 = 1<2> The unit is in the MDI mode or at an emergency stop.<3> DISABLE is selected at "DISABLE/ENABLE."

Table 1.3(a) lists the items to be set up in this screen.Table 1.3(c) lists the diagnostics information for verifyingcommunication statuses.


- 49 -

Display proceduresProcedure 1



(2) If the bus parameter screen or slave parameter screen isdisplayed, press soft key [SLAVE SETTING] in the operationselection menu.

Procedure 2



(3) Press soft key [DEVICENET].(4) If the bus parameter screen or slave parameter screen is

displayed, press [SLAVE SETTING] in the operation selectionmenu.


If the master function is enabled:- If the cursor is at "DI HOLD/CLEAR," pressing cursor key

moves the cursor to "DISABLE/ENABLE" in the bus

parameter screen.- If the cursor is at "DISABLE/ENABLE", pressing cursor

key moves the cursor to "DI SIZE" in the slave

parameter screen for slave No. 032.

- Pressing page key PAGE

displays the bus parameter screen.

- Pressing page key PAGE displays the slave parameter

screen for slave No. 032.


- 50 -

Table 1.3 (a): Setting items in slave function screenItem Description

1.DIS/ENB(DISABLE/ENABLE)

Sets whether to disable or enablecommunications.Move the left and right cursor keys to select thisparameter setting. (For the 15i-A, use soft keys.)Set ENABLE after setting of the master functionparameters is completed.Communications is started a few seconds aftersetting ENABLE. DISABLE : Disables communications. ENABLE : Enables communications.

2.MAC-ID Sets the number for identifying on the network theDeviceNet interface board mounted on the controlunit (CNC).Set a number that does not duplicate the MAC-IDof other nodes on the network within the range 0 to63.(MAC-ID: Media Access Control ID)

3.BAUD-RATE Sets the baud rate.The setting range is 0 to 2.The baud rate for each setting is as follows: 0: 125 kbps 1: 250 kbps 2: 500 kbpsThe baud rate is limited by the maximum networklength and other factors. For details, refer to"Connecting DeviceNet Functions" in theConnections section.

4 DI ADDRESS5 DI SIZE6 DO ADDRESS7 DO SIZE

Set the areas to be used as the DI/DO databuffers.Set the leading buffer address and buffer size.Use the R area as the address to be set.Size setting range: 0 to 64

8.STATUS ADDRESS9.STATUS SIZE

Set the areas to be used as the status informationdata buffer.Set the leading buffer address and buffer size.Use the R area as the address to be set.Size setting range: 0 to 4

10. DI HOLD/CLEAR

Note) See Chapter 2,"Configuring aSafe System."

Specify whether to hold or clear DI data ifcommunication is abnormal. 0: To hold DI data. 1: To clear DI data.


- 51 -

When the Devicenet Slave Board (A20B-8100-0490) or Slave Board A(A20B-8100-0491)is used

Table 1.3 (b): Diagnostics information(STATUS/COMMUNICATIONS STATUS)

Item DescriptionSTATUS: DISABLE : Disables communications.

ENABLE : Enables communications.(normal communicationsstatus)

ERROR : Communications error hasoccurred.Check COMMUNICATIONSTATUS and the status ofthe master device.

INVALID MAC ID : The MAC-ID is not setcorrectly.

DUPLICATE MAC ID : Duplicate MAC-IDs havebeen set.

BUS FAULT : Bus error has occurred.POWER ON ERROR : An error occurred when

the power was turned ONor when ENABLE was set.Check the DeviceNetinterface board mountingstate.

IDLE/ACTIVE Indicates the status of the Group 2 Master/SlaveConnection Set. "01" indicates an active state.

00: IDLE state(Group 2 Master/Slave Connection Set is notestablished.)

01: ACTIVE state(Group 2 Master/Slave Connection Set isestablished.)

CAN BUS STATUS1 Indicates the status information of the CAN(Controller Area Network) bus. Status informationis expressed in hexadecimal with 1 byteexpressing each item of information. Each of thebits of the status information is significant.

CAN BUS STATUS1 (1byte Data)


The meaning of bits is as follows.(Values in parentheses () indicate values in thenormal communications status.)#01 OL (1) : Online state#1 BW (0) : Bus warning state

A communications error hasoccurred, and the CAN chipautomatically stopped frame transfer.Probable causes are an incorrectbaud rate setting or noise.


- 52 -

Table 1-3 (b) (continued): Diagnostics information(STATUS/COMMUNICATIONS STATUS)

Item DescriptionCAN BUS STATUS1 #2 BO (0) : Bus OFF state

A communications error hasoccurred, and the CAN chipautomatically turned offline. Probablecauses are an incorrect baud ratesetting or a hardware malfunction.

#3 A (1) : Network is active.Data is being sent and received.

#4 TA (0) : Response error stateThere is no response from thecommunications destination within 25to 50 msec. The communicationsdestination node may not exist on thenetwork.

#5 TO (0) : Time-out stateHigh priority data may be beingtransferred excessively.

#6 RO (0) : Receive buffer overrun has occurred.#7 ML (0) : Message lost has occurred.

CAN BUS STATUS2 CAN BUS STATUS2 (1byte Data)

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

The meaning of each bit is as follows.(Values in parentheses () indicate values in thenormal communications status.)#0 ER (0) : A CAN communications error has

occurred.A probable cause is noise or ahardware malfunction.

#1 BP (1) : Network power ON state#2 --#3 --#4 01 : Baud rate is 125 kbps.#5 02 : Baud rate is 250 kbps.#6 05 : Baud rate is 500 kbps.#7 SA (1) : The network scanner is active.


- 53 -

When the DeviceNet Slave Board B(A20B-8100-0650) is used

Table 1.3 (c): Diagnostics information(STATUS/COMMUNICATIONS STATUS)

Item Description00 DISABLE Disables communications.01 ENABLE Enables communications.

(normal communicationsstatus)

STATUS

03 ERROR Communications error hasoccurred.

Check the status and error.The display is in hexadecimal notation and consists of one byte.The individual bits of the status information have their respectivemeanings.When the bits are 1, they mean:

#7 #6 #5 #4 #3 #2 #1 #0[VR] [IC]

(A value enclosed in parentheses corresponds to a normalcommunication status.)#0 IC (1) : Initialization completed

IDLE/ACTIVE

#1 VR (1) : Valid-data-being-received flag00 OFFLINE DISABLE has been selected.01 INITIAL COMPLETE The DeviceNet interface has

been initialized.02 CHECK BAUDRATE A baud rate check is in

progress.- If the specified baud rate is

incorrect, the operation ishalted in this status.

03 CHECK NODE DUPLICATION A check for a duplicate MAC-ID specification is inprogress.

04 WAIT CONNECTION ONLINE The DeviceNet is waiting forcommunication with themaster to begin.The operation is halted in thisstatus if:- A cable is broken or not

connected normally.- The specified MAC-ID is

invalid in the master side.- The DI/DO SIZE setting

does not match that in themaster side.

05 ONLINE Communication is effective(normal communicationstatus).

CONDITIONSTATUS

06 WAIT CONNECTION TIMEOUT Communication isinterrupted.


- 54 -

Table 1.3 (c): Diagnostics information(STATUS/COMMUNICATIONS STATUS)

Item Description80 HARDWARE ABNORMAL ERROR81 SETTING ERROR82 NODE DUPLICATION ERROR83 BUS OFF ERROR

Check the error.STATUS

(Undefined) WATCH DOG ERROR A failure has occurred on theDeviceNet interface board.

00

No alarm condition hasoccurred. (Normalcommunication status)

01 ROM ERROR02 RAM ERROR03 DP-RAM ERROR04 CAN ERROR

A failure has occurred on theDeviceNet interface board.

09 PARAMETER ERROR The setting is incorrect.

0B NODE DUPLICATION ERROR There is a duplicate MAC-IDspecification on the network.

0C BUS OFF ERROR This failure occurs if:- The line is disturbed by

noise or any otherabnormal condition.

- A baud rate does notmatch between nodes.

0D NETWORK POWER ERROR A failure has occurred in thepower supply for DeviceNetcommunication.

ERRORSTATUS

(Undefined) WATCH DOG ERROR Another failure has occurredon the DeviceNet interfaceboard.

Note) For the models other than Series 15i, only numbers aredisplayed.

Setting the MAC-ID and baud rateSet the node No. "2. MAC-ID" of this slave node and the baud rate "3.BAUD RATE" to appropriate values referring to items 2 and 3 inTable 1.3 (a).


- 55 -

Assigning DI/DO addressesSet to parameters the addresses and sizes of the R areas to whichDI/DO areas are to be assigned. For example, to assign six bytes of DIdata (data input to the CNC from the master) to R1000 onwards andassign two bytes of DO data (data output from the CNC to the master)to R1100 onwards, set each of the data items as follows in screen1.3(a) or 1.3(c).

4 DI ADDRESS = R10005 DI SIZE = 66 DO ADDRESS = R11007 DO SIZE = 2

DI/DO is assigned to R area signals as follows according to thissetting.

DI AssignmentsR1000 1st DI data from masterR1001 2nd DI data from masterR1002 3rd DI data from masterR1003 4th DI data from masterR1004 5th DI data from masterR1005 6th DI data from master

DO AssignmentsR1100 1st DO data to masterR1101 2nd DO data to master

When a DI only slave or a DO only slave is connected, set the valueof the parameter that specifies the size of the unused DO or DI to "0".Assign DI/DO in the same way on the master device, too. For detailson how to set parameters on the master device, refer to theSpecifications Manual for the master device to be used.

NOTEWhen you set the assignment data, carefully set thedata so that area to be secured as each assigneddata item are not duplicated. Also, thoroughly checkbefore setting to prevent areas that are currentlyused for other slave assignment addresses and PMCladder programs from being duplicated.


- 56 -

Assigning status informationAssign the status information. This information is used for verifyingthe communications status on the PMC.Set to parameters the address and size of the R area in which thestatus information data is to be assigned.

When the Devicenet Slave Board (A20B-8100-0490) or Slave Board A(A20B-8100-0491)is used

Table 1.3(d) shows the relationship between the STATUS SIZEsetting values and the status information data to be assigned.

Table 1.3 (d): Relationship between STATUS SIZE setting values andSTATUS information

SettingValue

Item Description

1 STATUS information This 1-byte data notifies the PMC of thecommunications status.00h : Disables communications.01h : Enables communications. (normal

communications status)03h : Communications error has

occurred.For details, check theCOMMUNICATION STATUS andstatus of the master device.

82h : Illegal MAC-ID84h : Duplicate MAC-ID8Eh : Bus error has occurred.8?h : An error other than the above

occurred at start ofcommunications.

2 COMMUNICATIONSTATUS:IDLE/ACTIVEinformation

This 1-byte data notifies the PMC of thestate of Group 2 Master/SlaveConnection Set of the DeviceNet. 00h: IDLE state 01h: ACTIVE state


This 1-byte data notifies the PMC ofCAN BUS STATUS1 information.




This 1-byte data notifies the PMC ofCAN BUS STATUS2 information.

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



- 57 -

Setting the status information storage areaThe content up to the STATUS SIZE setting value items (see Table1.3(d)) is assigned continuously starting from the specified R areasignal.For example, to assign four bytes of status information from R1500onwards, set each of the data items as follows in screen 1-5.



Status Information AssignmentsR1500 STATUS informationR1501 IDLE/ACTIVE informationR1502 CAN BUS STATUS 1 informationR1503 CAN BUS STATUS 2 information


- 58 -

When the Devicenet Slave Board C (A20B-8100-0650) is used

Table 1.3(e) lists the relationships between the STATUS SIZEsettings and the status information assigned according to the settings.

Table 1.3(e) Meanings of status informationItem Value Description

00h Communication is disabled. 01h Communication is enabled.

(Normal communication status)

STATUS (This1-byte datanotifies thePMC of thecommunicationstatus.)

03h A communication error has occurred.Check the status and error.

The individual bits have their respective meanings.When the bits are 1, they mean:(Values enclosed in parentheses corresponds to the normalcommunication status.)

#0 (1) Initialization completed. (Normalcommunication status)

IDLE/ACTIVE(This 1-bytedata notifies thePMC of thecommunicationstatus.)

#1 (1) Effective-data-being-received flag (normalcommunication status)

00h DISABLE is selected. 01h Initialization is completed. 02h A check on the baud rate is in progress. 03h A check for a duplicate MAC-ID

specification is in progress. 04h The DeviceNet is waiting for

communication to begin. 05h Communication is enabled.

(Normal communication status) 06h Communication is interrupted. 80h to 83h Communication is disabled.

For details, check the error.

CONDITIONSTATUS (This1-byte datanotifies thePMC of thecommunicationstatus.)

Other values in arange between00h and FFh

A failure has occurred on the DeviceNetinterface board.

00h No alarm condition has occurred.(Normal communication status)

01h to 04h A failure has occurred on the DeviceNetinterface board.

09h The setting is incorrect. 0Bh There is a duplicate MAC-ID specification

on the network.

0Ch This failure occurs if:- The line is disturbed by noise or any

other abnormal condition.- A baud rate does not match between

nodes. 0Dh A failure has occurred in the power supply

for DeviceNet communication.

ERRORSTATUS (This1-byte datanotifies thePMC of thecommunicationstatus.)

Other values in arange between00h and FFh

A failure has occurred on the DeviceNetinterface board.


- 59 -

Setting the status information storage areaStatus information is assigned sequentially starting at the signal in thespecified R area.For example, to assign four bytes of status information from R1500onwards, set each of the data items as follows in screen 1-5.



Status Information AssignmentsR1500 STATUSR1501 IDLE/ACTIVER1502 StatusR1503 Error

On the PMC, start communications using this status information. Alsouse this status information to process on the PMC anycommunications errors that may occur.The error status of this status information is returned to the normalcommunications status when the cause of the error is removed. So, ifthe error status must be held, perform this operation on the PMC.

CAUTIONWhen you set the assignment data, carefully set thedata so that areas to be secured as data do notduplicate areas that are currently used for ladderprograms on the PMC.


- 60 -

1.3.1 Starting Communications


After you have finished setting up the parameters, startcommunications by selecting ENABLE at the "1 DIS/ENB" item.Move the cursor from DISABLE to ENABLE. After several seconds,communications is started, and the STATUS display changes toENABLE as shown in screen 1.3.1 below.

Screen 1.3.1

Case of the Series 16i/18i/21i-A

After parameter setting is completed, setting DISABLE/ENABLE toENABLE triggers communication and changes the status indication toENABLE.

Cursor operations and switching of screens are not possible for a fewseconds until the connection for communications is established.


- 61 -

1.3.2 Slave Function Data Refresh Rate

The "data refresh rate" is the time required for the control unit (CNC)to update all I/O signals assigned to the R areas.

NOTEThe data refresh rate does not indicate the I/Oresponse time on the network. The I/O responsetime is dependent on the condition of the network.

Table 1.3.2(a) shows the relationship between the total number ofDI/DO communications points and the data refresh rate in the slavefunction.

Table 1.3.2 (a)Total Number of Slave Communications Points Data Refresh Rate

1 to 64byte 8ms

The relationship changes as follows when master functions are usedtogether with slave functions.

Table 1.3.2 (b)Number of DI/DO Communications Points (byte) Data Refresh Rate

1 to 32 8ms33 to 64 16ms

* A maximum of 32 bytes of DI/DO is updated every 8 msec.

CAUTIONThis data refresh rate sometimes changes accordingto the configured options taking the overallperformance of the CNC into consideration.


- 62 -

Setting Slave Functions on Power Mate i-D/H

On the Power Mate i-D/H, slave functions can be set using the regularparameters.

NOTE1 When the DeviceNet parameters have been set, the

power must be turned OFF temporarily.2 In the case of Power Mate i-D two-path control,

setting can be performed only from the 1st path.

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

Procedure when using DPL/MDI(1) Press the DGNOS

PARAM key to switch to the parameter screen.


Procedure when using the DPL/MDI operation package (PC)(1) Press the F4

PRMDGN key to switch to the parameter screen.



- 63 -

Parameters28000 Enable/disable communications


Sets whether to disable or enable communications. Communicationsis started when this parameter is set to "1" and the power is turned ONagain.This parameter is equivalent to the "1 DIS/ENB" setting in screen1.3(a) or 1.3(c).


28001 MAC-ID


Sets the number for identifying on the master device the DeviceNetinterface board mounted on the control unit (CNC).Set a number that does not duplicate the MAC-ID of other nodes onthe network within the range 0 to 63.(MAC-ID: Media Access Control ID)This parameter is equivalent to the "2 MAC-ID" setting in screen1.3(a) or 1.3(c).

28002 Baud rate


Sets the baud rate. Set the same value as the baud rate of the masterdevice as the setting value.This parameter is equivalent to the "3 BAUD-RATE" setting in screen1.3(a) or 1.3(c).

Setting Value Baud rate0 125Kbps1 250Kbps2 500Kbps

28010 DI data buffer area


Sets the area to be used as the DI data buffer. Use the R area as theaddress to be set.This parameter is equivalent to the buffer area setting in "4 DIADDRESS" in screen 1.3(a) or 1.3(c).



- 64 -

28011 DI data buffer address


the maximum value of the R area)Sets the area to be used as the DI data buffer. Set the leading addressof the buffer.This parameter is equivalent to the buffer address setting in "4 DIADDRESS" in screen 1.3(a) or 1.3(c).

28012 DI data buffer size


Sets the area to be used as the DI data buffer. Set the size of the bufferwithin the range 0 to 64.This parameter is equivalent to the "5 DI SIZE" setting in screen1.3(a) or 1.3(c).

28013 DO data buffer area


Sets the area to be used as the DO data buffer. Use the R area as theaddress to be set.This parameter is equivalent to the buffer area setting in "6 DOADDRESS" in screen 1.3(a) or 1.3(c).


28014 DO data buffer address


the maximum value of the R area)Sets the area to be used as the DO data buffer. Set the leading addressof the buffer.This parameter is equivalent to the buffer address setting in "6 DOADDRESS" in screen 1.3(a) or 1.3(c).

28015 DO data buffer size


Sets the area to be used as the DO data buffer. Set the size of thebuffer within the range 0 to 64.This parameter is equivalent to the "7 DO SIZE" setting in screen1.3(a) or 1.3(c).


- 65 -

28016 Status information data buffer area


Sets the area to be used as the status information data buffer. Use theR area as the address to be set.This parameter is equivalent to the buffer area setting in "8 STATUSADDRESS" in screen 1.3(a) or 1.3(c).


28017 Status information data buffer address


the maximum value of the R area)Sets the leading address of the status information data buffer. Set theleading address of the buffer.This parameter is equivalent to the buffer address setting in "8STATUS ADDRESS" in screen 1.3(a) or 1.3(c).

28018 Status information data buffer size


Sets the size of the status information data buffer. Set the size of thebuffer within the range 0 to 64.This parameter is equivalent to the "9 STATUS SIZE" setting inscreen 1.3(a) or 1.3(c).

28019 Holding/Clearing the DI data


Sets the state of the DI data when communication is not normal.This parameter is equivalent to the "10 HOLD/CLEAR" setting inscreen 1.3(a) or 1.3(c).

Setting Value Meaning0 Holding the DI data1 Clearing the DI data

2.CONFIGURING A SAFE SYSTEM OPERATION B-63404EN/03

- 66 -

2 CONFIGURING A SAFE SYSTEM

This chapter describes how to configure a safe system when creating asystem using DeviceNet functions.

B-63404EN/03 OPERATION 2.CONFIGURING A SAFE SYSTEM

- 67 -

2.1 TROUBLESHOOTING COMMUNICATIONS ERRORS

Using the Series 16i/18i/21i-A/B (DeviceNet function software series 6576/edition 02or earlier)

With this DeviceNet function, assignment data is not updated when acommunications error occurs. For this reason, DI data is held at thestate that was active when the alarm was detected.

Using the Series 16i/18i/21i-A/B (DeviceNet function software series 6576/edition 03or later) or Series 15i-A

In this DeviceNet function, whether to hold or clear the DI data whena communication error has occurred can be selected by setting the DIHOLD/CLEAR parameter as follows:DI HOLD/CLEAR0: The DI data is held in the state where it was when an alarm

condition was detected.1: The DI data is cleared.

When designing the system, design the system so that the status of thestatus information is monitored at all times and the system operatesstably. You can also prepare signals in DI/DO data, by which data isexchanged, for indicating whether or not communications is beingperformed instead of using the status information, and you can alsojudge whether or not communications is being performed normally bymonitoring whether or not chose signals are being read. On the slavesystem side, start and continue operations after receiving permissionfrom the master device.

2.CONFIGURING A SAFE SYSTEM OPERATION B-63404EN/03

- 68 -

2.2 HANDLING MULTIPLE-BYTE DATA

With this DeviceNet function, data communications on the networkand updating of data assigned to PMC R area are performedasynchronously. For this reason, handling of data of two bytes orlonger must be synchronized on the PMC (in the ladder program).For example, when multiple-byte DI data is read from the masterdevice on a slave, signals for acquiring synchronization must beprovided before and after the data, DI data must be read when thesynchronizing signals set by the master device is correctly read by theslave, and the slave must reset the synchronizing signals when it hasfinished reading the DI data and then notify the master device that ithas finished reading the DI data.

III. CONNECTION

B-63404EN/03 CONNECTION 1.CONNECTING DeviceNet FUNCTIONS

- 71 -

1 CONNECTING DeviceNet FUNCTIONS

This chapter describes information relating to connecting DeviceNetfunctions.Refer to issued DeviceNet specifications from ODVA about thestandard of DeviceNet.

NOTEThe following DeviceNet connecting fixtures aremade available but not supplied by FANUC. Buyconnecting fixtures that comply with the DeviceNetstandard from a third party.• Communications cables• Communications power supply• Terminator• T-branch tap• Power supply tap• Crimped terminals

TrademarkDeviceNet is a trademark of ODVA (OpenDeviceNet Vendor Association.)

1.CONNECTING DeviceNet FUNCTIONS CONNECTION B-63404EN/03

- 72 -

1.1 CONNECTING DeviceNet

With FANUC DeviceNet, one DeviceNet board is needed for eachnetwork. The number of networks that can be connected and availablefunctions is limited to the machine type.

Machine Type Number of Networks FunctionFS16i/18i/21i(LCD-mounted type)

1 Master or slave

FS16i/18i/21i(Stand-alone type)and Power Mate i

2Master 1 control, Slave1 control

1) Master functionThe "master function" refers to controlling I/O of other slaveunits to be connected on the network with the CNC as the masterunit as shown in the figure below.

Up to 32 slaves can be connected to a single master.

2) Slave function

Master/Slave CombinationsGroup Master Slave

1 #1 #11,#12,#132 #2 #21,#22,#23,#24

Up to 64 devices, including masters and slaves, can connected on asingle network.

Master(CNC)

#N#6#5#4#3 • • •

-Slaves

Master(group 2) #2

Master(group 1) #1

slave(CNC)

#11

DeviceNet-Slaves

slave

#12

slave(CNC)

#21

slave

#13

slave

#22

slave

#23

slave

#24


- 73 -

1.2 DeviceNet CABLES

There are two types of DeviceNet cable: thick cable and thin cable.Normally, thick cable is used as the trunk line when a long-distancenetwork is required. Normally, thin cable is used as branch cable as itis thinner and more flexible than thick cable. Thin cable can also usedas the trunk in short-distance networks.

Use cables that comply with the DeviceNet standard.


- 74 -

1.3 CABLE LENGTH AND BAUD RATE

There are some restrictions in configuring a network: maximumnetwork length, branch length and total branch length. These factorsare also restricted by the baud rate.

Maximum network lengthThe "maximum network length" refers to whichever is longer, thedistance between furthermost nodes or the distance betweenterminators.

The following table shows the maximum network length according tocable type.

Cable Type Maximum Network LengthThick cable (5-wire) 500mThin cable (5-wire) 100m

NOTEThin cable can also be used as the trunk if themaximum network length is within 100 m. In thiscase, also pay attention to the maximum currentcapacity of the cable so that this limit value is notexceeded.

The maximum network length is also limited by the baud rate.

Baud RateMaximum Network LengthWhen Only Thick Cable Is

Used

Maximum Network LengthWhen Only Thin Cable Is

Used500 K bit/sec 100m250 K bit/sec 250m 100m125 K bit/sec 500m

Node

Node

NodeBranch length

Node

TerminatorTerminator

Branchlength

T-branch tap T-branch tap

Whichever of these is longer is the maximumnetwork length.

Communicationspower supply


- 75 -

NOTEWhen Thick Cable Is Used Together With ThinCableA mixture of thick cable and thin cable can be usedfor the cable connecting furthermost nodes. Note,however, that in this case, the line lengths of eachtype of cable must satisfy the expression in thefollowing table. So, the total network length becomesshorter than when the network is configured byconnecting only thick cable.

Prevent the maximum current consumption of the cables from beingexceeded.

Baud Rate Maximum Network Length500 K bit/sec Lthick + Lthin < 100m250 K bit/sec Lthick + 2.5 × Lthin < 250m125 K bit/sec Lthick + 5 × Lthin < 500m

Lthick: Length of thick cable, Lthin: Length of thin cable

Example

Baud Rate Maximum Network Length Acceptability

500 K bit/sec Lthick + Lthin=175 < 100m NG250 K bit/sec Lthick + 2.5 × Lthin = 125 + 2.5 × 50=250 < 250m OK125 K bit/sec Lthick + 5 × Lthin = 125 + 5 × 50 = 375 < 500m OK

According to the above calculation, communications at 250 kbit/secand 125 kbit/sec is possible in this case. Note, however, that anetwork cannot be configured if the maximum allowable currentconsumption of the cables is exceeded even if the above conditionsare satisfied.

Node

Node

NodeBranch length

Node


T-branch tap T-branch tap

Maximum network length

1m

5m

40m25m100m1m

3m

2m



- 76 -

Branch lengthThe "branch length" refers to the longest value from where the trunkis divided into a branch up to the first node connected to the branch.The maximum branch length is 6 m.Branches can be sub-divided into further branches.

Total branch lengthThe "total branch length" refers to the length obtained by totaling thelength of all branches. The total branch length is sometimes exceedsthis restriction even if all of the branches is within 6 m. Also, the totalbranch length restriction also varies according to the baud rate.

Baud Rate Maximum Total Branch Length500 K bit/sec 39m250 K bit/sec 78m125 K bit/sec 156m

Node

Branch length (max. 6 m)

T-branch tap

Trunk line

Node B

Node C

Branch length

Node A

T-branch tap A

T-branch tap B

4m

1m

1m

2m

Trunk lineT-branch tap A to node A: 6 mT-branch tap A to node B: 5 mT-branch tap A to node C: 6 m

All branches are within 6 m.

Calculation example

Node D

6m

T-branch tap C

Node B

Node CNode A

T-branchtap A

T-branch tap B

4m

1m

1m

2m

T-branch tap A to T-branch tap B: 4 mT-branch tap B to Node A: 2 mT-branch tap B to Node B: 1 mNode B to Node C: 1 mT-branch tap C to Node D: 6 m

The total branch length is 12 m.

Calculation exampleTerminatorTerminator


- 77 -

1.4 TERMINATOR

To reduce the influence of signal reflection and ensure more stablecommunications, terminators must be attached to both ends of thetrunk. Terminators need not be attached to the ends of branches. Donot attach terminators to the ends of branches; attach them only to theends of the trunk.The following shows the specifications and how to connect aterminator.

NOTENumbers in parentheses () indicate the connectorpin No.Install the terminator within 1 m of the end (node orT-branch tap) of the branch line.

R = 121O, 1/4wAllowable resistance error: 1%Metal sheath

CAN L(2)

CAN H(4)

Node

T-branch tap

Terminator1m


- 78 -

1.5 CONNECTOR

ConnectorDeviceNet interface connector

Terminal No. Signal Name Color Code Signal Type1 V- Black Signal cable - side2 CAN L Blue Communications data Low side3 SHIELD Bare Shield4 CAN H White Communications data High side5 v+ Red Signal cable + side

Cable connector:Manufactured by Phoenix Contacts Inc.MSTB2.5/5-ST-5.08AU (provided with the product)Applicable cable conductor AWG24-12

Connecting the communications cableConnect the communications cable to the DeviceNet interfaceconnector according to the following procedure.

(1) Strip about 30 mm of the cable sheath and remove unwantedsheath.

(2) Peel off the aluminum tape covers the signal leads and the powerleads, and strip the sheath of the signal leads and power leadsmatched to the length of the crimped terminals.

(3) Twist the stripped signal leads and power leads and attach thecrimped terminals.We recommend the following crimped terminal:• Phoenix Contacts Inc. AI series (special tool ZA3)

(4) Loosen the cable fastening screws on the connector so that theline materials can be easily inserted.

(5) Insert each of the signal leads into the holes on the connectorterminal plate so that the sheath colors of the shielded lead,signal leads and power leads match the colors indicated on theconnector.

(6) Tighten the power leads in place with the cable fastening screwson the connector.

Two thin cables can be connected to this connector in a multi-dropconfiguration. In this case, insert two leads into a single hole on theterminal plate. Thick cable cannot be used in a multi-dropconfiguration. In a multi-drop configuration, use T-branch taps.


- 79 -

- Connector (DeviceNet boards B and C)Cable-end connector for DeviceNet boards B and C:

Manufactured by Hirose Electric Co., Ltd.HR31-5.08p-5SC (plug) andHR31-SC-121 × 5 pieces (crimp terminals)Applicable cable conductor 0.25 to 1.65 mm2

The plug is shipped along with DeviceNet boards B and C. The plughas a label indicating a color code. No crimp terminal is shippedunless separately ordered. (A02B-0259-K211).

NOTENo crimp terminal is shipped along with DeviceNetboard B or C.

- Connecting the communication cable (DeviceNet boards B and C)To attach a communication cable to the DeviceNet interfaceconnector, follow this procedure.(1) Remove the sheath of the cable to a length of about 30 mm, and

cut off the excess shielding.(2) Remove the aluminum tape from around the signal and power

supply wires. Also remove the insulator from each wire to alength of about 5 mm.

(3) Twine the stripped signal wire strands. Also twine the strippedpower supply wire strands. Attach a crimp terminal to eachbundle of wire strands.To crimp the terminal, use a crimp tool complying with JISC9711 by setting its indication to 1.25.Recommended crimp tool:HR31-TC-01 manufactured by Hirose Electric Co., Ltd.

(4) Insert the shielding wire, signal wire, and power supply wire intothe plug by matching their insulator colors to the color codesindicated on the connector.When attaching each crimp terminal to the plug, keep them inthe orientation shown below.

(5) Insert the plug into the DeviceNet board, and fasten it with itsbolts using a No. 0 cross-head bit.

These crimp terminals are of a multidrop type. Each terminal can beused to crimp two thin cable wires together. They are not for thickcables.

Crimp terminal Wire


- 80 -

- Pulling out crimp terminals (DeviceNet boards B and C)If you made a misconnection, correct it by pulling out the crimpterminal according to this procedure.A rod 1 mm in diameter can be used to pull out a crimp terminals.Recommended tool: HR31-SC-TP manufactured by Hirose ElectricCo., Ltd.(1) Push a pull-out tool against the molded lance. (See Fig. 1.)(2) While pushing the molded lance, tilt the pull-out tool to release

the crimp terminal lock. (See Fig. 2.)(3) Pull out the pull-out tool.(4) Pull the wire to take out the crimp terminal.

- Extending the line (DeviceNet boards B and C)Adding a CNC to the existing line requires another crimp terminalA02B-0259-K211.(1) Pull out the crimp terminal from the plug of the CNC at the last

stage of the line.(2) Detach the existing communication cable from the crimp

terminal.(3) Attach the detached communication cable and an additional

communication cable to a new crimp terminal, and insert it to theplug.

For details, see "Connecting the communication cable (DeviceNetboards B and C)."

Molded lance Molded lance

Pull-out tool Pull-out tool

Wire Wire

Fig. 1 Fig. 2


- 81 -

1.6 GROUNDING THE CABLE WIRES

Wire the cable referring to the figure below when connecting thecable to the connector.

Grounding the networkIn the DeviceNet specification, it is recommended that only one placeon the network be grounded and a place as near as possible to thecenter of the network be grounded to prevent a ground loop.As shown in the figure above, connect the shielded lead of the cableto frame ground (FG) for the communications power supply andground FG to a maximum resistance of 100.When multiple power supplies are used, connect and ground theshielded lead only at the power supply near the center of the network.Do not connect the shielded lead to the frame ground of other powersupplies, and ground these FGs to a maximum of 100. When you usemultiple power supplies, user a special power supply tap made byother manufacturers.

Only one communications power supply:

Two or more communications power supplies:

Power line (V+)Power line (V-)

V+

Signal line (CAN_H)

1

Communications

power supply

DeviceNetBoard

Connector

Drain wire/shield

32 4 5

Signal line (CAN_L)

V- FG

100 ? min.

MasterPowersupply Slave

T-branch tap or power supply tap

MasterPowersupply Slave

Powersupply Slave

Powersupply

Ground at only one location near the centerPower supply

tap


- 82 -

Obtaining a ground leadThere are three ways of obtaining a ground lead:

• By drawing out from the connector to which the communicationscable is connected

Insert the ground lead into the same hole as the shielded leadof the communications cable and fix in place.

• By drawing out from the T-branch tapConnect only the ground lead to one of the connectors on theT-branch tap.

• By using the cable clampGround the communications cable shield by the cable clamp,and connect the communications power supply ground to theclamp base.

NOTEBe sure to ground the shield lead of eachcommunications cable. If there is even one placethat is not grounded, the shielding effect of the entirenetwork is impaired.


- 83 -

1.7 CABLE CLAMP

The cable clamp has two functions: to support the cable and to shieldthe cable. As shown in the figures below, peel off part of the cablesheath to expose the outer shield cover, and press this part against theearth plate with the earth plate.

Earth plate

Cable

Cable clamp

Earth plate

Cable sheath

Shield


- 84 -

1.8 COMMUNICATIONS POWER SUPPLY

With DeviceNet, power must be supplied for communications. Use apower supply that satisfies the specifications shown in the table belowand that has insulated AC input and DC output as the communicationspower supply. Also, select a communications power supply havingmargin in its current capacity greater than the total currentconsumption of all nodes to which power is to be supplied.

Communications Power Supply SpecificationsItem Specifications

Output voltage 24VDC ± 1%Output current 16 A max.Input fluctuation Max. 0.3%Load fluctuation Max. 0.3%Influence of ambient temperature Max. 0.03%/°COutput ripple 250mVp-pOutput side capacity Max. 7000 µFAmbient temperature During operation : 0 to 50°C

During storage : -40 to +85°CInrush Current Limit Less than 65 A (peak)Protection against overvoltage ProvidedProtection against overcurrent Provided (max. current 125%)Startup time 250 ms up to 5% value of final output

voltageOvershoot at startup Max. 0.2%Insulation Across output and AC power supply,

and output and housingCompliant standards Necessary : UL

Recommended : FCC Class, B, CSATUV, VDE

Ambient humidity 30 to 90% (no condensation allowed)Surge current Max. 10%

Be sure to supply power from the trunk down to the branches. Themaximum current capacity of the communications cable is 8A onthick cables and 3A on thin cables.The communications power supply is connected in various formsdepending on the user's power supply requirements.

The current capacity of the branch varies according to the branchlength. The longer the branch, the smaller the branch's maximumcurrent capacity becomes. The same applies if the cable used as thebranch is thick cable or thin cable. Calculate the possible currentcapacity (I) on a single branch (the total current that is consumed oneach branch) according to the following expression:

I = 4.57/L I: Allowable current (A)L: Branch length (m)


- 85 -

1.8.1 Designing a Power Supply Connection

Design the power supply connection in the following order:

(1) Provisional determine the position of the power supply.(2) Calculate the current consumption of all nodes to be located on

the network.(3) Calculate the length at the provisional position, and calculate a

rough value for the current that can be supplied to the cableaccording to the graph.

(4) Verify whether or not the supplied current satisfies the currentconsumption.

(5) Change the position of the power supply and verify again.(6) If the conditions are not satisfied by the simple calculation

according to the graph in step (3), calculate the supplied currentaccording to the calculation expression and verify again.

(7) If the conditions in the calculation expression are not satisfied instep (6), provide two or more power supplies, separate the powersupply paths, and verify whether or not the supply currentsatisfies the conditions for each of the power supplies.

1.8.2 Determining the Power Supply Locations

Power supplies can be located in the four configurations shownbelow.In principle, select configurations (1) and (2).If the power supply conditions are not satisfied in configurations (1)and (2), study the use of configuration (3). To provide two or morepower supplies for the simultaneous supply of power, configuration(4) is also possible.

(1) When nodes are located both sides of the power supply:

(2) When the nodes are located to one side of the power supply:

NOTEWe recommend the configuration in (1) whensupplying power to many nodes from a single powersupply.

Node


NodeNodeNode Node

Power supply tapor T-branch tap



- 86 -

(3) When the power supply path is separated between two or morepower supplies:

(4) When two or more power supplies are provided tosimultaneously cover all of the nodes in between:

NOTEIf the current capacity flowing to the thick cableexceeds 8A even if the position of thecommunications power supply is changed, the powersupply conditions cannot be satisfied by one powersupply. So, use two or more power supplies.When thick cable is used in the configuration in (1),there will be no problems if the current capacities onboth sides of the trunk from the communicationspower supply are both 8A or less. For this reason, aconfiguration up to a maximum current capacity of16A is possible.If the current capacity flowing to the thin cableexceeds 3A when thin cable is used for the trunk,verify whether or not the conditions are satisfied bychanging to thick cable.

Node

Terminator

Node Node

Power supply tap

Terminator

NodeNode

Power supply tap

path 2Path 1

V+V-

24V 0V

FuseRemove the fuse and separate V+.

Set V- common topaths 1 and 2.



Terminator

Node Node Node

Terminator

NodeNode

Power supply tap Power supply tap




- 87 -

Factors for determining the power supply locationsTwo factors for determining whether or not current can be suppliednormally are the current capacity required by each node and voltagedrop on the cable. Calculate the following two values beforehand:• Current capacity required at each node• Distance from the power supply(ies)

How to calculate the power supplyThere are two ways of calculating the power supply for the trunk:1) Simple calculation according to the graph2) Calculation by calculation expression (Voltage drop is calculated

from the resistance of the communications cable and the currentconsumption.)

NOTECalculate the power supply so that the conditionalexpression for the current consumption on branchesaccording to the branch length is satisfied for eachbranch.

• The conditions are sometimes satisfied by calculating using thecalculation expression even if the power supply conditions arenot satisfied by calculating simply according to the graph. In thiscase, locating the power supply at a hypothetical position posesno problem.

NOTEWhen using a common power supply forcommunications and the NC, the power supplycannot be calculated by graph-based simplecalculation in the following item. Calculate the powersupply according to the calculation expression.

TerminatorNode NodeTerminator Power supply tap NodeNode

Regarded as nodistance

Distance to furthest node on trunkor to branch tap from power supply



- 88 -

1.8.3 Verification by Graph-Based Simple Calculation

Voltage drop occurs when current flows to the communications cable.The longer the communications cable, the larger the current valuebecomes and the larger the voltage drop occurs.The voltage of the communications power supply at each node mustbe 11 VDC or more.The following tables and graphs show the maximum current for eachcable thickness by which a sufficient voltage can be supplied to thecommunications power even if a voltage drop occurs.

• Thick cableThick cable (m) 0 25 50 100 150 200 250 300 350 400 450 500Max. current (A) 8.00 8.00 5.42 2.93 2.01 1.53 1.23 1.03 0.89 0.78 0.69 0.63

• Thin cableThick cable (m) 0 10 20 30 40 50 60 70 80 90 100Max. current (A) 3.00 3.00 3.00 2.06 1.57 1.26 1.06 0.91 0.80 0.71 0.64

0

1

2

3

0 10 20 30 40 50 60 70 80 90 100Thin cable (m)

Max

. cur

rent

(A

)

0

1

2

3

4

5

6

7

8

0 50 100 150 200 250 300 350 400 450 500Thin cable (m)

Max

. cur

rent

(A

)


- 89 -

Graph-based simple calculationThe items must be checked in order (1) to (3) for each of the nodeslocated in the same direction viewed from the power supply.If nodes are located on both sides of the power supply, items (1) to (3)must be checked in each direction.(1) Calculate total current consumption (A) for all nodes located on

the network in each direction.(2) Calculate from the graph maximum current (B) that can flow to

the cable based upon the cable type (thick or thin) and thedistance to the furthermost end on the trunk from the powersupply.

(3) If total current consumption (A) calculated in (1) is less than orequal to maximum current (B) calculated in (2), this means thatthe power supply conditions are satisfied for all nodes.

NOTEThe graph to refer to varies according to the cabletype (thick or thin) used for the trunk.

RemediesIf total current consumption (A) calculated in (1) is greater thanmaximum current (B) calculated in (2), study the following:• Move the power supply towards the center to configure the

network so that nodes are located on both sides of the powersupply.

• If nodes are already located on both sides of the power supply,move the power supply towards the direction on which the largercurrent consumption is required.

• Swap with thick cable if thin cable is used.

If A is grater than B in any of the above measures, study the positionsof the nodes according to the calculation expression taking into theactual positions of the nodes.

When the power supply unit is located at the one of the network (example 1):The following shows an example where thick cable having a totallength of 200 m is used for the power supply, and the communicationspower supply is located at the end of the network.In this example, the current consumptions of each node are assumedto be as shown in the following figure.

Total length of power supply line = 200 m

TerminatorNode NodeTerminator Power supplytap NodeNode

200m

Trunk line (5-lead cable)0.25A0.05A0.25A0.1A



- 90 -

Total current consumption = 0.1A + 0.15A + 0.05A + 0.25A = 0.65AMaximum possible current calculated from the table for thick cable =1.53AThe relationship becomes "total current consumption is less than themaximum current," so you can verify that power can be supplied to allnodes.

When the power supply unit is located at the center (example 2):The following shows an example where thick cable having a totallength of 240 m is used for the power supply, and the communicationspower supply is located at the center of the network.As the communications power supply is located in the center of thenetwork, the maximum current flows to both the left and right of thepower supply. For this reason, a current twice the maximum currentcan be supplied compared with when the communications powersupply is located at the end of the network.In this example, the current consumptions of each node are assumedto be as shown in the following figure.

Total length of power supply line (left side) = Total length of powersupply line (right side) = 120 mTotal current consumption (left side) = 0.1 A + 0.45 A = 0.55 ATotal current consumption (right side) = 0.25 A + 0.3A = 0.55 AMaximum current (left side) calculated from the table for thick cable= Approx. 2.5 AMaximum current (right side) calculated from the table for thick cable= Approx. 2.5 A(The above values are calculated by linear approximation between100 and 150 m.)

The relationship becomes "total current consumption (left side) is lessthan the maximum current (left side)" and the "total currentconsumption (right side) is greater than the maximum current (rightside)," so you can verify that power can be supplied to all nodes.

TerminatorNode Node

Terminator

Power supply tap

NodeNode

120m


120m

Within3 m



- 91 -

When current consumption is uneven on either side of the power supply unit (example 3)The following shows an example where thick cable having a totallength of 240 m is used for the power supply, and the communicationspower supply is located by moving it slightly away from the center ofthe network.If the total current consumption is uneven on either side of the powersupply unit and is insufficient even if the communications powersupply is located in the center of the network, the currentconsumption conditions are sometimes satisfied by moving the powersupply unit slightly.In this example, the current consumptions of each node are assumedto be as shown in the following figure.

When the power supply unit is located in the center:

Total length of power supply line (left side) = Total length of powersupply line (right side) = 120 mTotal current consumption (left side) = 1.1A + 1.25A + 0.5A = 2.85ATotal current consumption (right side) = 0.25A+0.25A+0.85A=1.35AMaximum current (left side) calculated from the table for thick cable= Approx. 2.5 AMaximum current (right side) calculated from the table for thick cable= Approx. 2.5 A(The above values are calculated by linear approximation between100 and 150 m.)

The relationship becomes "total current consumption (left side) isgreater than the maximum current (left side)," so it can be seen thatthe current consumption is insufficient on the left side.To remedy this, move the position of the power supply unit to the leftas shown in the figure below.

Total length of power supply line (left side) = 100 mTotal length of power supply line (right side) = 140 m

TerminatorNode NodeTerminator

Power supply tap

NodeNode

120m


120m

Within3 m

Node

0.5A

Node

0.25A


TerminatorNode NodeTerminator

Power supply tap

NodeNode

120m


100m

Within3 m

Node

0.5A

Node

0.25A



- 92 -

Total current consumption (left side) = 1.1A + 1.25A = 2.35ATotal current consumption (right side) = 0.5A+0.25A+0.25A+0.85A=1.85AMaximum current (left side) calculated from the table for thick cable= 2.93AMaximum current (right side) calculated from the table for thick cable= Approx. 2.1 A(The above values are calculated by linear approximation between100 and 150 m on the right.)

As a result, the relationship becomes "total current consumption isgreater than the maximum current" for both the left and right sides, soyou can verify that power can be supplied to all nodes.


- 93 -

1.8.4 Verifying by Calculation Expression

If the conditions cannot be satisfied by simply calculating from thegraph, verify the conditions according to the actual positions of eachnode and the communications power supply.With DeviceNet, the maximum voltage drop allowed in a system isstipulated as 5V for each of the power supply lines (V+, V-) basedupon the voltage specifications (24 VDC) of the communicationspower supply and the input voltage specifications (11 to 25 VDC) ofthe communications power supply for each device.This 5 V voltage drop comprises an allowable voltage drop of 4.65Aon the trunk and an allowable voltage drop of 0.35V on the branches.The approach for considering voltage drop in the cable is as follows.In the DeviceNet standard, the voltage drop in the communicationscable is stipulated to within 5 V or less including margin taking intoconsideration the voltage specifications (24 VDC) and the inputvoltage specifications (11 to 25 VDC) of the communications powersupply of each device.

V1: Supply voltage of communications power supply. Set V1 to 23 Vtaking into consideration the fluctuation range of the powersupply voltage.

V2: Supply voltage to each node. Set V2 to > 13 V taking the margininto consideration.

VA: Voltage drop at power cable V+VB: Voltage drop at power cable V-

On DeviceNet, set VA to less than or equal to 5V and VB to lessthan or equal to 5V.

The voltage drop on the communications cables is stipulated at 5V orless on each of the power lines (V+, V-).This 5 V voltage drop comprises an allowable voltage drop of 4.65Aon the trunk and an allowable voltage drop of 0.35V on the branches.

Calculation expressionFist, investigate the distance between the power supply and each ofthe nodes, and the current consumption of the communications unit oneach device.Then check whether or not the following conditional expression issatisfied. If the conditional expression is satisfied, the conditions forpower supply to each node are satisfied. However, prevent themaximum current capacity (thick cable: 8A, thin cable: 3A) of thecables from being exceeded.

V1 V2

Voltage drop at V+ (VA)

Voltage drop at V- (VB)

Supply voltage of communications power supply

Supply voltage to each node


- 94 -

These conditions cannot be used if one power supply is shared as thecommunications power supply and the NC power supply. This mustbe studied separately.

• Conditional expression (totalizing expression of voltage drop ontrunk)

Σ (Ln × Rc+Nt × 0.005) × ln < 5V

Ln: Distance between power supply and node (excludingbranch length)

Rc: Maximum cable resistance (thick cable: 0.015Ω/m, thincable: 0.069Ω/m)

Nt: Number of taps between each node and power supplyIn: Current consumption required for communications units on

each node0.005Ω = Contact resistance of tap


- 95 -

When nodes are located to one side of the power supply (configuration example 1)

The voltage drop is calculated for each group.Group 1 : (1×0.015+1×0.005) × 0.25=0.005VGroup 2 : (30×0.015+2×0.005) × 0.24=0.1104VGroup 3 : (50×0.015+3×0.005) × 0.50=0.3825VTotal voltage drop = 0.005 + 0.1104 + 0.3825 = 0.4979V ≥ 4.65VSo, in this configuration example, the conditional expression is notsatisfied.

When nodes are located both sides of the power supply (configuration example 2)

The voltage drop of each group is calculated for each path.Group 1 of path 1 : (20 × 0.015+1 × 0.005) × 0.25=0.07625VGroup 2 of path 2 : (10 × 0.015+1 × 0.005) × 0.24=0.0372VGroup 3 of path 2 : (30 × 0.015+2 × 0.005) × 0.50=0.23V

Voltage drop on path 1 =0.07625V<4.65V

40mA


Node

Powersupply tap

50mA

Node

5 units

Node

40mA

Node30mA

Node8 units

Node30mA

30mA

Node50mA

Node10 units

Node50mA

50mA

1m30m

50m

<Group 1>50mA+40mA×5=250mA

<Group 2>30mA×8=240mA


Communications

power supplies

Branch: thin cable

Trunk line: thick cable


40mA


Node

Power supply tap

50mA

Node

5 units

Node

40mA

Node30mA

Node8 units

Node30mA

30mA

Node50mA

Node10 units

Node50mA

50mA

20m 10m30m

<Group 1>50mA+40mA×5=250mA



Communications

power supplies

Branch: thin cable

Trunk line: thick cable

Path 1 Path 2



- 96 -

Total voltage drop on path 2 =0.0372V+0.23=0.2672V<4.65VSo, in this configuration example, the conditional expression issatisfied on both paths.

1.8.5 Supplying Multiple Power Supplies on Separated Paths

When the conditions cannot be satisfied even by calculating with thecalculation expression, use two or more communications powersupplies and separate the power supply paths.

How to separate power supply pathsAs two or more power supplies are used, use power supply taps foreach of the power supplies. Power supply taps are not provided byFANUC. Power supply tapes that comply with the DeviceNetstandard must be purchased separately from another manufacturer.The figure below shows the internal circuit of the power supply tap.

When the power supply path is separated at the cable A side, removefuse A, and when it is separated at the cable B side, remove fuse Bbefore use.

5-lead cableB side

V+CAN H

Power supply tap

Shot keydiode

shieldCAN LV-

V+CAN HshieldCAN LV-

V-V+

Fuse A Fuse B

GNDterminal

Power supply unit

5-lead cableA side


- 97 -

1.8.6 Relationship with NC Power Supply

In principle, the communications power supply cannot be shared asthe NC power supply. Prepare separate power supplies for thecommunications power supply and for the NC power supply.However, note the following points when a power supply mustunavoidable be shared due to the difficulty of providing separatepower supplies because of space and cost considerations.

The minimum stipulated input voltage of the NC power supply (24VDC input type) is 21.6 V and is higher than that of thecommunications power supply. Satisfy this stipulation taking intoconsideration loss caused by voltage drop on the cables. Also, the NCcontrol unit turns OFF when the communications cable breaks or isdisconnected or when there is a short-circuit caused by shared use.

Turn the communications power supply and NC power supply ONand OFF in the following sequence when separate power supplies areprovided:• Turn ON the communications power supply at the same time or

before turning ON the NC power supply.• Turn OFF the communications power supply at the same time or

after turning OFF the NC power supply on the master node.If only the communications power supply is turned OFF duringnetwork operations, an abnormality may occur on other nodes that arecurrently communicating.

2.DeviceNet FOR 16i/18i/21i (LCD-MOUNTED TYPE) CONNECTION B-63404EN/03

- 98 -

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

This chapter describes hardware specifications and connectioninformation relating to the DeviceNet board 16i/18i/21i (LCD-mounted Type).

B-63404EN/03 CONNECTION 2.DeviceNet FOR 16i/18i/21i (LCD-MOUNTED TYPE)

- 99 -

2.1 SPECIFICATIONS

Item Specifications

NameDeviceNet interface board for LCD-mounted Type iseriesA02B-0236-J301 16i/18i/21i-A

Specification Dwg. No.A02B-0281-J301 16i/18i/21i-B

Hardware Dwg. No. A20B-8001-0880Communications powersupply voltage

11 to 24 VDC (supplied from communicationsconnector)

Current consumptionCommunications power supply: Max. 50 mAInternal power supply circuit: 5 VDC, max. 850 mA(supplied from NC unit)

Weight 200g

2.DeviceNet FOR 16i/18i/21i (LCD-MOUNTED TYPE) CONNECTION B-63404EN/03

- 100 -

2.2 INSTALLATION

2.2.1 Environmental Conditions

When using the DeviceNet board, strictly observe the installationconditions (cabinet internal environment conditions) of the CNCcontrol unit in which it is mounted.

2.2.2 Leading in Cables

The cables are lead in only from the bottom in the same way as otherregular option PCBs.The figure below shows the location of the connector on theDeviceNet board.

DeviceNet interface

View from rear of unit

View from bottom of unit

Note, however, that the board mounting position in the above figureand connector locations of boards other than the DeviceNet boardvary from the actual positions. For details of the actual connectorlocations of boards other than the DeviceNet board, refer to therespective Connections Manual.

NOTEFit or remove the DeviceNet board into the optionslot with the DeviceNet interface connector removed.The DeviceNet board cannot be mounted on slot 2when another optional PCB is mounted at slot 3 on a3-slot type unit.

B-63404EN/03 CONNECTION 2.DeviceNet FOR 16i/18i/21i (LCD-MOUNTED TYPE)

- 101 -

2.2.3 Names of Parts on the DeviceNet Board

DeviceNet interface connector

Communications board status indicators

LED

ALE

D3

LED

2LE

D1

LED

0

Slot status and alarmindicator LED

3.DeviceNet BOARD FOR 16i/18i/21i (STAND-ALONE TYPE), Power Mate i-D/H CONNECTION B-63404EN/03

- 102 -

3 DeviceNet BOARD FOR 16i/18i/21i(STAND-ALONE TYPE), Power Mate i-D/H

This chapter describes hardware specifications and connectioninformation relating to the DeviceNet slave board for the Series16i/18i/21i (Stand-Alone Type) and the Power Mate i-D/H, and theDeviceNet master board.

B-63404EN/03 CONNECTION 3.DeviceNet BOARD FOR 16i/18i/21i (STAND-ALONE TYPE), Power Mate i-D/H

- 103 -

3.1 SPECIFICATIONS

Item SpecificationsName DeviceNet slave board

A02B-0265-J300FS 16i/18i/21i (Stand-AloneType)Specification Dwg. No.

A02B-0259-J240 Power Mate i -D/HFunctions DeviceNet slave function 1 channelPCB Dwg. No. A20B-8100-0490Communications powersupply voltage



Weight 200g

Item SpecificationsName DeviceNet master board


A02B-0259-J241 Power Mate i -D/HFunctions DeviceNet master function, 1 channelPCB Dwg. No. A20B-8100-0490Communications powersupply voltage



Weight 200g

NOTE1 There are two DeviceNet boards, the DeviceNet

slave board and DeviceNet master board. The PCBspecifications are the same, the only differencebeing is the shorted position of setting pin TM1 onthe board. (The position of setting pin changes theunit specifications.) Usually, TM1 is factory-set byFANUC.

2 If a DeviceNet board (A02B-0265-K412) is suppliedtogether with the CNC, TM1 on the DeviceNet boardis factory-set to the MASTER position. To use theDeviceNet board as a slave, set TM1 to the SLAVEposition by referring to Subsection 2.1.3 of Part IV,"Maintenance."

3 The sequence in which this DeviceNet board isattached and removed is fixed. See sections 2 and 3of the Maintenance section.

4 When the axis control card (A17B-3700-050*) ismounted on the opposite PCB, the connector causesinterference. Use DeviceNet board B or C.


- 104 -

3.2 INSTALLATION


When using the DeviceNet board, the ambient temperature rangeduring operation of the control unit is 0°C to 50°C. For details ofother installation environment conditions, refer to the installationenvironment conditions of each CNC control unit.


- 105 -

3.3 MOUNTING

On the FS16i/18i/21i (Stand-Alone Type), the DeviceNet board canbe mounted in the 1-slot or in all mini slots of the 3-slot basic unit. Onthe Power Mate i-D/H, the DeviceNet board can be mounted on eitherof the two mini slots.


- 106 -

3.4 DeviceNet Board B

DeviceNet board B is characterized by a crimp type connector(manufactured by Hirose Electric Co., Ltd.) used in thecommunication connector section. See Section 1.5, "Connector," ofPart III, "Connection," for explanations about how to crimp connectorterminals.The descriptions in Sections 3.1 to 3.3 except for specificationdrawing numbers and PCB drawing numbers apply also to DeviceNetboard B.

Item SpecificationsName DeviceNet slave board


A02B-0259-J242 Power Mate i –D/HPCB Dwg. No. A20B-8100-0491

Item SpecificationsName DeviceNet master board B


A02B-0259-J243 Power Mate i –D/HFunctions DeviceNet master function, 1 channelPCB Dwg. No. A20B-8100-0491


- 107 -

3.5 DeviceNet Board C

DeviceNet board C is characterized by a crimp type connector(manufactured by Hirose Electric Co., Ltd.) used in thecommunication connector section. See Section 1.5, "Connector," ofPart III, "Connection," for explanations about how to crimp connectorterminals.The descriptions in Sections 3.1 to 3.3 except for specificationdrawing numbers and PCB drawing numbers apply also to DeviceNetboard C.

Item SpecificationsName DeviceNet slave board C

Specification Dwg. No. A02B-0265-J304FS 16i/18i/21i (Stand-AloneType)

Functions DeviceNet slave function 1 channelPCB Dwg. No. A20B-8100-0650Communications powersupply voltage



Weight 110g

NOTE1 No fixed procedure applies to the mounting or

dismounting of DeviceNet board C, unlike othertypes of DeviceNet boards.

2 DeviceNet board C has no setting pin.

4.DeviceNet BOARD FOR 15i CONNECTION B-63404EN/03

- 108 -

4 DeviceNet BOARD FOR 15i

This chapter describes hardware specifications and connectioninformation relating to the DeviceNet slave board for the Series 15i/,and the DeviceNet master board.

B-63404EN/03 CONNECTION 4.DeviceNet BOARD FOR 15i

- 109 -

4.1 SPECIFICATIONS

Item SpecificationsName DeviceNet slave board CSpecification Dwg. No. A02B-0261-J132Functions DeviceNet slave function 1 channelHardware Dwg. No. A20B-8100-0650Communications powersupply voltage



Weight 110g

Item SpecificationsName DeviceNet master boardSpecification Dwg. No. A02B-0261-J131Functions DeviceNet master function, 1 channelHardware Dwg. No. A20B-8100-0491Communications powersupply voltage



Weight 200g

NOTE1 Setting pin TM1 on DeviceNet board B is factory-set

by FANUC. See Section 2.4 of Part IV,"Maintenance."

2 A fixed procedure applies to the mounting anddismounting of DeviceNet board B. See Section 2.3of Part IV, "Maintenance." No fixed procedureapplies to the mounting or dismounting of DeviceNetboard C, however.

4.DeviceNet BOARD FOR 15i CONNECTION B-63404EN/03

- 110 -

4.2 INSTALLATION


When using the DeviceNet board, the ambient temperature (in thecabinet) range during operation of the control unit is 0°C to 50°C. Fordetails of other installation environment conditions, refer to theConnection Manual (Hardware) (B-63323EN)

B-63404EN/03 CONNECTION 4.DeviceNet BOARD FOR 15i

- 111 -

4.3 INSTALLATION

On the FS15i, the DeviceNet board can be mounted in the 2-slot or in all mini slots of

the 4-slot basic unit.

IV. MAINTENANCE

B-63404EN/03 MAINTENANCE 1.16i/18i/21i (LCD-MOUNTED TYPE) DeviceNet

- 115 -

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

This chapter describes maintenance related to the DeviceNet boardfor the Series 16i/18i/21i (LCD-mounted Type).

1.16i/18i/21i (LCD-MOUNTED TYPE) DeviceNet MAINTENANCE B-63404EN/03

- 116 -

1.1 LAYOUT OF PARTS

DeviceNet interface connector HEALTH

LED

ALE

D3

LED

2LE

D1

LED

0

Slot status and alarmindicator LED

NS

B-63404EN/03 MAINTENANCE 1.16i/18i/21i (LCD-MOUNTED TYPE) DeviceNet

- 117 -

1.2 DESCRIPTION OF INDICATOR LEDS

This board has five status indicator LEDs (4 green, 1 red), and twoLEDs that light in both the red and green colors on the internaldaughter board. The table below describes the functions of theseLEDs.

Name Color MeaningLED0 ~ 3 Green No particular meaningLEDA Red This LED lights when an error occurs on the

internal daughter board, and goes out when thepower is turned ON.When this LED lights, replace the DeviceNetboard.

NS Red/Green The LED indicates the DeviceNetmodule/network status. This LED indicateswhether or not the DeviceNet board power isturned ON, and whether DeviceNetcommunications is being performed normally.For details of the meaning of the lit states of thisLED, refer to the Specifications Manual issued byODVA.

HEALTH Red/Green This LED indicates the status of the daughterboard.It lights red after the power is turned ON. Whenthe firmware is loaded to the internal daughterboard, it lights green.It lights red if a failure occurs on the daughterboard.If the LED lights red, replace the DeviceNetboard.

1.16i/18i/21i (LCD-MOUNTED TYPE) DeviceNet MAINTENANCE B-63404EN/03

- 118 -

1.3 HOW TO ATTACH AND REMOVE THE DeviceNet BOARD

OutlineTo remove and remove the DeviceNet board from the control unit, theDeviceNet connector terminal plate must first be removed.

Removing the DeviceNet connector terminal plateThe terminal plate can be removed from the DeviceNet boardinterface connector with the cable still connected. Remove theterminal plate by pulling it towards you.

NOTEThe DeviceNet board cannot be removed unless theconnector's terminal plate has been removed first.

Removing and attaching the DeviceNet boardFor details on how to remove and attach the DeviceNet board, refer to"How to Remove and Attach Optional Boards" in the MaintenanceManual in the respective Maintenance Manual.

CAUTIONThe DeviceNet board cannot be mounted on slot 2when another optional PCB is mounted at slot 3 on a3-slot type unit.

B-63404EN/03 MAINTENANCE2.DeviceNet BOARD FOR 15i, 16i/18i/21i (STAND-ALONE TYPE), Power Mate i-D/H

- 119 -

2 DeviceNet BOARD FOR 15i, 16i/18i/21i(STAND-ALONE TYPE), Power Mate i-D/H

This chapter describes the maintenance information relating to theDeviceNet slave board for the Series 15i, Series 16i/18i/21i (Stand-Alone Type) and Power Mate i-D/H, and the DeviceNet master board.

2.DeviceNet BOARD FOR 15i, 16i/18i/21i (STAND-ALONE TYPE), Power Mate i-D/H MAINTENANCE B-63404EN/03

- 120 -

2.1 DeviceNet BOARD

2.1.1 Layout of PartsSettingpin TM1

External lineconnector TBL

LED indicatorsA 3 2 1

MA

ST

ER

SL

AV

E

LED indicatorsMNS (Left),HEALTH (right)

PCB Dwg.No.

PWBversionNo.

LEDHEALTH

LEDMNS


- 121 -

2.1.2 Description Of Indicator LEDs

This board has four status indicator LEDs (3 green, 1 red), and twoLEDs that light in both the red and green colors on the internaldaughter board. The table below describes the functions of theseLEDs.

Name Color MeaningLED1 ~ 3 Green These LEDs indicate whether the DeviceNet

board is a master board or a slave board. TheseLEDs go out when the power is turned ON.

LED1 LED2 LED3Master board Lit Out OutSlave board Lit Lit Out

LEDA Red This LED lights when an error occurs on theinternal daughter board, and goes out when thepower is turned ON.When this LED lights, replace the DeviceNetboard.

MNS Red/Green The LED indicates the DeviceNetmodule/network status. This LED indicateswhether or not the DeviceNet board power isturned ON, and whether DeviceNetcommunications is being performed normally.For details of the meaning of the lit states of thisLED, refer to the Specifications Manual issued byODVA.

HEALTH Red/Green This LED indicates the status of the daughterboard.It lights red after the power is turned ON. Whenthe firmware is loaded to the internal daughterboard, it lights green.It lights red if a failure occurs on the daughterboard.If the LED lights red, replace the DeviceNetboard.


- 122 -

2.1.3 Short Pin TM1This board has a 3-pin short pin TM1. TM1 indicates whether thatboard is used for DeviceNet slave functions or DeviceNet masterfunctions.

When the short pin is set to SLAVE, that board is used for DeviceNetslave functions. When it is set to MASTER, that board is used forDeviceNet master functions.The short pin is already set before the board is shipped from thefactory according to your particular specifications. Do not change thesetting.

NOTEFor some models, machine tool builders arerequested to set TM1.In this case, first find the location of short pin TM1 byreferencing the parts layout drawing shown inSubsection 2.1.1. To use the board as a master,set TM1 to the MASTER position. To use the boardas a slave, set it to the SLAVE position.

MASTER SLAVE

Short pin


- 123 -

2.1.4 How to Attach and Remove the DeviceNet Board

OutlineThe sequence in which this DeviceNet board is attached and removedfrom the control unit is fixed.

CAUTIONTo prevent the inadvertent loss of data in SRAMduring this operation, back up the data in the CNC'sSRAM to built-in FROM (Power Mate i only) or tomemory card before you attach and remove theDeviceNet board.

Removing the DeviceNet Board1) Removing the DeviceNet connector terminal plate

The terminal plate can be removed from the DeviceNet boardinterface connector with the cable still connected. Loosen thetwo screws shown in the figure below, and then remove theterminal plate by pulling it towards you.

NOTEThe base PCB cannot be removed unless theconnector's terminal plate has been removed first.

2) Removing the base PCBRemove the base PCB before you remove the DeviceNet board.For details on how to remove the base PCB, refer to therespective Maintenance Manual.

CAUTIONThe DeviceNet board cannot be removed unless thebase PCB has been removed first. If the DeviceNetboard is removed without removing the base PCB,the DeviceNet board may interfere and break thebase PCB.

Screw

Device net board

Base PCB


- 124 -

3) Removing the DeviceNet boardRemove the DeviceNet board without the base PCB attached.For details on how to remove the DeviceNet board, refer to"How to Remove and Attach Optional Boards" in the respectiveMaintenance Manual.

Attaching the DeviceNet board1) Removing the base PCB

Remove the base PCB before you remove the DeviceNet board.For details on how to remove the base PCB, refer to therespective Maintenance Manual.

CAUTIONThe DeviceNet board cannot be attached unless thebase PCB has been removed first. If you attempt toattach the DeviceNet board without removing thebase PCB, the DeviceNet board may interfere andbreak the base PCB.

2) Removing the DeviceNet connector terminal plateRemove the interface connector terminal plate from theDeviceNet board. Loosen the two screws shown in the figurebelow to remove.

3) Attaching the DeviceNet boardAttach the DeviceNet board without the base PCB attached.For details on how to attach the DeviceNet board, refer to "Howto Remove and Attach Optional Boards" in the respectiveMaintenance Manual.

4) Attaching the base PCBAfter you have attached the DeviceNet board, attach the basePCB. For details on how to attach the base PCB, refer to therespective Maintenance Manual.

5) Attaching the DeviceNet connector terminal plateAttach the interface connector terminal plate to the DeviceNetboard. After attaching the terminal plate, firmly tighten the twoscrews on the terminal plate.

NOTEThe base PCB cannot be attached unless theconnector's terminal plate has been removed first.

Screws


- 125 -

2.2 DeviceNet BOARD B

DeviceNet board B is characterized by a crimp type connector(manufactured by Hirose Electric Co., Ltd.) used in thecommunication connector section. The parts layout, indicator LEDs,and short pin of this board are the same as for DeviceNet board A.See Subsection 2.1.4 also for explanations about how to mount anddismount this board.


- 126 -

2.3 DeviceNet BOARD C

2.3.1 Layout of Parts

Name PCB DRW number RemarksDeviceNet slave board C A20B-8100-0650

TBL

CustomLSI

MPU


- 127 -

2.3.2 Description Of Indicator LEDs

This board has five status indicator LEDs (2 green(MS, NS), 3red(ALM, MS, NS).

NOTEThe face plate is indicated using dotted lines.

TBL4(M

S)(G

RE

EN

)

3(MS

)(RE

D)

2(NS

)(GR

EE

N)

1(NS

)(RE

D)

A(A

LM)(R

ED

)


- 128 -

Status LED indicatorsThe locations of the indicator LEDs and their definitions areexplained below. A : Off B : On C : Blinking D : Don't care

ALM

No.LED indicator

ALM (RED)Board status

1 BThe board is reset, or an error has been detectedon the board.

MS (This is a modular status LED of the DeviceNet. Refer to thespecification document issued by ODVA.)

No.LED indicator

MS(GREEN),(RED)Board status

1 B A The board is running normally.

2 C AA setting has not been completed. Theinsufficient or inaccurate setting requiresadjustment.

3 A C A recoverable error has occurred.4 A B An irrecoverable error has occurred.5 C C Self-diagnosis is in progress.

NS (This is a network status LED of the DeviceNet. Refer to thespecification document issued by ODVA.)

No.LED indicator

NS(GREEN),(RED)Board status

1 A A The communication link is not on-line.

2 C AThe communication link is on-line, but noconnection has been established.

3 B AThe communication link is on-line, and aconnection has been established.

4 A C The connection is in the time-out state.

5 A BA network error was detected which disabledcommunication.

6 C C

The board has detected a network access error, isin the Communication Faulted state, and hasreceived an Identify Communication Faultedrequest.

APPENDIX

B-63404EN/03 APPENDIX A.DEVICE PROFILES AND OBJECT LIBRARIES

- 131 -

A DEVICE PROFILES AND OBJECT LIBRARIES

This appendix presents information about the communication dataand IDs defined for the DeviceNet.

A.DEVICE PROFILES AND OBJECT LIBRARIES APPENDIX B-63404EN/03

- 132 -

A.1 DeviceNet BOARD C

Device profileApplicable DeviceNet specification Volume 1 Release2.0

Volume 2 Release2.0Vendor ID 591Device type 0CH

General data

Product code 1Network current drain 50 mA on 24 VDCConnector type Open plugWhether there is a physical layerinsulation.

Yes

Supported LED ModuleNetwork

MAC ID setting ParameterDefault MAC ID 0Transmission baud rate setting Parameter

Physical conformance data

Supported transmission baud rate 125Kbps,250Kbps,500KbpsPredefined master/slave connection set Group 2-only serverDynamic connection support(UCMM)

NoCommunication data

Explicit message fragmentation Yes

Object installation1. Identity object (01H)

Attribute UnsupportedObject classService Unsupported

ID Description GET SET Value1 Vendor O X 5912 Device type O X 123 Product code O X 14 Revision O X 1.05 Status (bits supported) O X bit0

bit106 Serial number O X (*1)7 Product name O X (*2)8 State X X9 Configuration Consistency Value X X

Attribute

10 Heartbeat Interval X XDeviceNet service Parameter option05H Reset No

Object instance

Service

0EH Get_attribute_Signle No

*1 Value set up for an individual board*2 A20B-8100-0650


- 133 -

2. Message router object (02H)Attribute UnsupportedObject classService UnsupportedAttribute UnsupportedObject instanceService Unsupported

Additional vendor-specific specification No

3. DeviceNet object (03H)ID Description GET SET ValueAttribute1 revision O X 02HDeviceNet service Parameter option

Object class

Service0EH Get_attribute_Signle No

ID Description GET SET Value1 MAC ID O X2 Baud rate O X3 BOI O X 00H4 Bus-off counter O X5 Allocation information O X6 MAC ID switch changed X X7 Baud rate switch changed X X8 MAC ID switch value X X

Attribute

9 Baud rate switch value X XDeviceNet service Parameter option0EH Get_attribute_Signle No4BH Allocate Master/Slave_Connection Set No

Object instance

Service

4CH Release Master/Slave_Connection Set No

4. Assembly object (04H)Attribute UnsupportedObject classService Unsupported

Section Information Maximum number ofinstances

Instance type Static I/O 1ID Description GET SET Value1 Number of Members in List X X2 Member List X X

Attribute

3 Data O ODeviceNet service Parameter option0EH Get_attribute_Signle No

Object instance1

Service

10H Set_attribute_Signle No


- 134 -

5. Connection object (05H)Attribute UnsupportedService Unsupported

Object class

Maximum available number ofactive connections

1

Section Information Maximum number ofinstances

Instance type Explicit Message 1Productiontrigger

Cyclic

Transport type ServerTransport class 3

ID Description GET SET Value1 State O X2 Instance type O X 00H3 Transport class trigger O X 83H4 Produced connection ID O X5 Consumed connection ID O X6 Initial comm. Characteristics O X 21H7 Produced connection size O X FE00H8 Consumed connection size O X FE00H9 Expected packed rate O O12 Watchdog time-out action O O One of 01,0313 Produced connection path length O X 000014 Produced connection path O X15 Consumed connection path length O X 000016 Consumed connection path O X

Attribute

17 Production inhibit time O XDeviceNet service Parameter option05H Reset No0EH Get_attribute_Signle No

Objectinstance 1

Service



- 135 -

Section Information Maximum number of instancesInstance type Polled I/O 1Production trigger CyclicTransport type ServerTransport class 2

ID Description GET SET Value1 State O X2 Instance type O X 01H3 Transport class trigger O X 82H4 Produced connection ID O X5 Consumed connection ID O X6 Initial comm. characteristics O X 01H7 Produced connection size O X (*1)8 Consumed connection size O X (*2)9 Expected packed rate O O12 Watchdog time-out action O O 0013 Produced connection path length O X 0000 (IN:No)

0600 (IN:Yes)14 Produced connection path O X No data (IN:No)

20_04_24_01_30_03 IN:Yes)15 Consumed connection pathlength

O X 0000 (OUT:No)0600 (OUT:Yes)

16 Consumed connection path O X No data (OUT:No) 20_04_24_01_30_03 (OUT:Yes)

Attribute

17 Production inhibit time O X 00DeviceNet service Parameter option05H Reset No0EH Get_attribute_Signle No

Objectinstance 2

Service


*1 Number of IN bytes used, in which the upper byte has beenreplaced with the lower byte (Example: 4000H when 64 bytesare used)

*2 Number of OUT bytes used, in which the upper byte has beenreplaced with the lower byte (Example: 4000H when 64 bytesare used)


- 136 -

Section Information Maximum number of instancesInstance type Bit Strobed I/O 1Production trigger CyclicTransport type ServerTransport class 2

ID Description GET SET Value1 State O X2 Instance type O X 01H3 Transport class trigger O X 82H4 Produced connection ID O X5 Consumed connection ID O X6 Initial comm. Characteristics O X 02H7 Produced connection size O X (*)8 Consumed connection size O X 0800H9 Expected packed rate O O12 Watchdog time-out action O O 0013 Produced connection path length O X 060014 Produced connection path O X 20_04_24_01_30_0315 Consumed connection path length O X 000016 Consumed connection path O X No data

Attribute

17 Production inhibit time O X 00DeviceNet service Parameter option05H Reset No0EH Get_attribute_Signle No

Objectinstance 3

Service


* Number of IN bytes used, in which the upper byte has beenreplaced with the lower byte (example: 0800H when 8 bytesare used)For the bit strobe, up to 8 bytes are usable.

B-63404EN/03 INDEX

i-1

INDEX

1

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

...................................................................... 115

A

Applicable Machine Names................................ 4

C

CABLE CLAMP ................................................ 83

CABLE LENGTH AND BAUD RATE............. 74

COMMUNICATIONS POWER SUPPLY........ 84

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

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

CONNECTING DeviceNet FUNCTIONS ....... 71

CONNECTOR ................................................... 78

D

DEFINITION OF WARNING¥, CAUTION¥,

AND NOTE ....................................................2Description Of Indicator LEDs .............. 121, 127

DESCRIPTION OF INDICATOR LEDS....... 117

Descriptions in This Manual.............................. 3

Designing a Power Supply Connection ........... 85

Determining the Power Supply Locations ...... 85

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

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

DeviceNet Board B ......................................... 106

DeviceNet BOARD B ...................................... 125

DeviceNet Board C .................................. 107, 132

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

DeviceNet BOARD FOR 15i ............................108

DeviceNet BOARD FOR 15i/16i/18i/21i (STAND-

ALONE TYPE)¥, Power Mate i-D/H ..............119

DeviceNet BOARD FOR 16i/18i/21i (STAND-

ALONE TYPE)¥, Power Mate i-D/H........... 102

DeviceNet CABLES .......................................... 73

DeviceNet FOR 16i/18i/21i (LCD-MOUNTED

TYPE)............................................................. 98

DeviceNet FUNCTIONS .................................... 9

E

Environmental Conditions ............. 100, 104, 110

G

GENERAL WARNINGS AND CAUTIONS ...... 3

GROUNDING THE CABLE WIRES ............... 81

H

HANDLING MULTIPLE-BYTE DATA........... 68

How to Attach and Remove the DeviceNet

Board............................................................ 123

HOW TO ATTACH AND REMOVE THE

DeviceNet BOARD....................................... 118

I

INSTALLATION............................. 100, 104, 111

L

Layout of Parts........................................ 120, 126

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

Leading in Cables ........................................... 100

M

Master Function Data Refresh Rate................ 37

MOUNTING.................................................... 105

N

Names of Parts on the DeviceNet Board ....... 101

NSTALLATION .............................................. 110

P

PECIFICATIONS............................................ 109

R

Related Manuals ................................................. 5

INDEX B-63404EN/03

i-2

Relationship with NC Power Supply ............... 97

S

SETTING MASTER FUNCTIONS.................. 11

SETTING SLAVE FUNCTIONS ..................... 46

Setting Slave Parameters................................. 23

Setting the Bus Parameters............................. 14

Short Pin TM1................................................. 122

Slave Function Data Refresh Rate .................. 61

SPECIFICATIONS ................................... 99, 103

Starting Communications .......................... 32, 60

Supplying Multiple Power Supplies on

Separated Paths ............................................ 96

T

TERMINATOR.................................................. 77

TROUBLESHOOTING COMMUNICATIONS

ERRORS ........................................................ 67

V

Verification by Graph-Based Simple Calculation

........................................................................ 88

Verifying by Calculation Expression ............... 93

!"!#

"

$%&""'

(')'*)&'

(

"&

$%&"""

('+

(

(, --. /00

10 02

"'

-$%'333

EUROPEAN HEADQUARTERSGRAND-DUCHE DE LUXEMBOURG

GE Fanuc Automation Europe S.A.Zone Industrielle

L-6468 L-6468 L-6468 L-6468 EchternachEchternachEchternachEchternach (+352) 727979 - 1

(+352) 727979 – 214 (+352) 727979 – 214 (+352) 727979 – 214 (+352) 727979 – 214www.gefanuc-europe.com

BELGIUM / NETHERLANDSGE Fanuc Automation Europe S.A.

- Netherlands Branch -Postbus 7230 - NL-4800 GE Breda

Minervum 1603A - NL-4817 ZL Breda - NL-4817 ZL Breda - NL-4817 ZL Breda - NL-4817 ZL Breda (+31) 76-5783 201 (CNC) (+31) 76-5783 212 (PLC)

(+31) 76-5870 181www.gefanuc.nl

CZECH REPUBLICGE Fanuc

Automation CR s.r.o.U studanky 3

CZ-170 00 CZ-170 00 CZ-170 00 CZ-170 00 Praha 7Praha 7Praha 7Praha 7 (+420) 2 333 72 502 (CNC) (+420) 2 333 72 503 (PLC)

(+420) 2 333 70 821www.gefanuc.cz

FRANCEGE Fanuc Automation France S.A.

39, rue du Saule Trapu, BP 219F-91882 F-91882 F-91882 F-91882 Massy Massy Massy Massy CedexCedexCedexCedex (+33) 1 69 75 86 39 (CNC) (+33) 1 69 75 86 20 (PLC)

(+33) 1 69 75 86 49www.gefanuc.fr

GERMANYGE Fanuc Automation GmbH

Bernhäuser Straße 22D-73765 D-73765 D-73765 D-73765 Neuhausen Neuhausen Neuhausen Neuhausen a.d.Fa.d.Fa.d.Fa.d.F

(+49) 7158 187 400 (+49) 7158 187 455 (CNC) (+49) 7158 187 466 (PLC)www.gefanuc.de

GERMANYGE Fanuc Eberle Automation GmbH

Südwestpark 48D-90449 NürnbergD-90449 NürnbergD-90449 NürnbergD-90449 Nürnberg

(+49) 911 9672 100 (PLC) (+49) 911 9672 200 (PLC)www.gefanuc.de


Elberfelderstr. 45D-40724 D-40724 D-40724 D-40724 HildenHildenHildenHilden

(+49) 2103 247410 (Laser/CNC) (+49) 2103 247420 (Laser/CNC)

www.gefanuc.de

GERMANYGE Fanuc Automation Deutschland

GmbHBensheimer Str. 61

D-65428 D-65428 D-65428 D-65428 RüsselsheimRüsselsheimRüsselsheimRüsselsheim (+49) 6142 357600 (+49) 6142 357611

www.gefanuc.de


Obere Hauptstr. 72D-09244 D-09244 D-09244 D-09244 LichtenauLichtenauLichtenauLichtenau

(+49) 37208 695 20(CNC) (+49) 37208 695 30 (PLC)

(+49) 37208 695 55www.gefanuc.de

ITALYGE Fanuc Automation Italia S.r.l.Largo Brugnatelli 15 – Via Volta 4

I-20090 Buccinasco (MI)I-20090 Buccinasco (MI)I-20090 Buccinasco (MI)I-20090 Buccinasco (MI) (+39) 02 45795 1 (CNC)

(+39) 02 45795 250 (CNC)www.gefanuc.it

ITALYGE Power Controls

Italia S.p.aVia Tortona 27I-20144 MilanoI-20144 MilanoI-20144 MilanoI-20144 Milano

(+39) 02 4242 280 (PLC) (+39) 02 4242 511 (PLC)www.gefanuc.it

POLANDGE Fanuc Automation Polska Sp. z o.o.

ul. Czerwinskiego 640-123 40-123 40-123 40-123 Katowice - PolandKatowice - PolandKatowice - PolandKatowice - Poland

(+48) 32 258 5077 (+48) 32 258 5077

SPAINGE Fanuc Automation España S.A.

Polígono Industrial OlasoCalle Olaso, 57 - Locales 10 y 11

E-20870 ElgoibarE-20870 ElgoibarE-20870 ElgoibarE-20870 Elgoibar (+34) 943 74 82 90 (CNC) (+34) 943 74 44 21 (CNC)www.gefanuc.es

SPAINGE Power Controls

Ibérica S.L.Calle Marqués de Comillas, 1E-08225 Terrassa (Barcelona)E-08225 Terrassa (Barcelona)E-08225 Terrassa (Barcelona)E-08225 Terrassa (Barcelona)

(+34) 93 736 58 28 (PLC) (+34) 93 788 24 03 (PLC)www.gefanuc.es

SWEDENGE Fanuc Automation Nordic AB

Hammarbacken 4BS-19149 S-19149 S-19149 S-19149 SollentunaSollentunaSollentunaSollentuna

(+46) 8 444 5520 (+46) 8 444 5521

www.gefanuc.se

SWITZERLANDGE Fanuc Automation Europe S.A.

Zweigniederlassung Brügg –Swiss Branch

Erlenstrasse 35aP.O. Box CH-2555 P.O. Box CH-2555 P.O. Box CH-2555 P.O. Box CH-2555 Brügg BEBrügg BEBrügg BEBrügg BE

(+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.gefanuc.ch

UNITED KINGDOMGE Fanuc

Automation (UK) Ltd.Unit 1 - Mill SquareFeatherstone Road

Wolverton Mill SouthMilton Milton Milton Milton Keynes MK12 5BZKeynes MK12 5BZKeynes MK12 5BZKeynes MK12 5BZ

(+44) 1908 84 4000 (+44) 1908 84 4001

www.gefanuceur.co.uk

10/01

Printed at GE Fanuc Automation S.A. , LuxembourgPrinted at GE Fanuc Automation S.A. , LuxembourgPrinted at GE Fanuc Automation S.A. , LuxembourgPrinted at GE Fanuc Automation S.A. , Luxembourg March 2001 March 2001 March 2001 March 2001

computer numerical controls -...

Documents