Yaskawa JAPMC-MC2303-E User Manual

Machine Controller MP2000 Series

262IF-01 FL-net Communication Module

USER'S MANUAL

Model: JAPMC-CM2303-E

262IF-01

RUN

TEST

ONOFF

FL-net

LINK

100M

ERR

LNK

FL-net Overview

Overview of 262IF-01 Module

Mounting and Starting the Module

FL-net Transmission Definition

Details of FL-net

Message Send and Receive Functions

Troubleshooting

Appendices

App

MANUAL NO. SIEP C880700 36B

All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form, or by any means, mechanical, electronic, photocopying, recording, or otherwise, without the prior written permission of Yaskawa. No patent liability is assumed with respect to the use of the information contained herein. Moreover, because Yaskawa is constantly striving to improve its high-quality products, the information contained in this manual is subject to change without notice. Every precaution has been taken in the preparation of this manual. Nevertheless, Yaskawa assumes no responsibility for errors or omissions. Neither is any liability assumed for damages resulting from the use of the information contained in this publication.

Purpose

Chapter

Selecting

Models and

Peripheral

Devices

Studying

Specifications

and Ratings

Designing

the

System

Panel Installation and Wiring

Tria l

Operation

Maintenance

and

Inspection

Chapter 1 FL-net Overview 9 − 9 −− −

Chapter 2 Overview of 262IF-01

Module

9 9 999 9

Chapter 3 Mounting and Starting

the Module

− 9 999 9

Chapter 4 FL-net Transmission

Definition

− 99− 99

Chapter 5 Details of FL-net 9 − 999 9

Chapter 6 Message Send and

Receive Functions

−−9 − 9 −

Chapter 7 Troubleshooting − 9 999 9

 This symbol is used to indicate important information that should be memorized or minor precautions,

such as precautions that will result in alarms if not heeded.

S-ON

=　/S-ON

P-CON

　 =　/P-CON

Using this Manual

Read this manual thoroughly before using 262IF-01. This manual describes MP2000 Series Machine Controller FL-net Communication Module 262IF-01. Keep this manual in a safe place for future reference.

 Basic Terms

Unless otherwise specified, the following definitions are used:

• MP2000 Series Machine Controller:

• PLC: Programmable Logic Controller

• MPE720:

MP2100M, MP2200, MP2300, MP2310, MP2300S, and MP2500MD Machine Controllers

The Programming Device Software or a personal computer running the Programming Device Software

 Manual Configuration

This manual consists of the chapters listed in the following table. Read the chapters of this manual as required by the purpose.

 Graphic Symbols Used in this Manual

The graphic symbols used in this manual indicate the following type of information.

 Indication of Reverse Signals

In this manual, the names of reverse signals (ones that are valid when low) are written with a forward slash (/) before the signal name, as shown in the following example:

iii

 Related Manuals

The following table lists the manuals relating to the MP2000 Series Machine Controller 262IF-01 Module. Refer to these manuals as required.

Manual Name Manual Number Contents

Machine Controller MP2100/MP2100M User's Manual Design and Maintenance

Machine Controller MP2200 User's Manual

Machine Controller MP2300 Basic Module User's Manual

Machine Controller MP2310 Basic Module User’s Manual

Machine Controller MP2300S Basic Module User’s Manual

Machine Controller MP2500/MP2500M/ MP2500D/MP2500MD User's Manual

Machine Controller MP2000 Series Motion Module Built-in SVB/SVB-01 User's Manual

Machine Controller MP2000 Series Communication Module User’s Manual

Machine Controller MP900/MP2000 Series User's Manual: Ladder Programming

Machine Controller MP2000 Series User's Manual: Motion Programming

Machine Controller MP2000 Series MPE720 Programming Device Version 6 User's Manual

Machine Controller MP900/MP2000 Series MPE720 Software for Programming Device User's Manual

Machine Controller MP900/MP2000 Series New Ladder Editor Programming Manual

Machine Controller MP900/MP2000 Series New Ladder Editor User's Manual

Machine Controller MP920 User's Manual Communication Modules

SIEPC88070001

SIEPC88070014

SIEPC88070003

SIEPC88073201

SIEPC88073200

SIEPC88075200

SIEPC88070033

SIEPC88070004

SIE-C887-1.2

SIEPC88070038

SIEPC88070030

SIEPC88070005

SIE-C887-13.1

SIE-C887-13.2

SIE-C887-2.6

Describes how to use the MP2100 and MP2100M Machine Controllers.

Describes how to use the MP2200 Machine Controller and the modules that can be connected.

Describes how to use the MP2300 Basic Module and the modules that can be connected.

Describes how to use the MP2310 Basic Module and the modules that can be connected.

Describes how to use the MP2300S Basic Module and the modules that can be connected.

Describes how to use the MP2500, MP2500M, MP2500D, and MP2500MD Machine Controllers.

Provides a detailed description on the MP2000 Series Machine Controller built-in SVB Module and slot-mounting optional SVB-01 Module.

Provides the information on the Communication Module that can be connected to MP2000 Series Machine Controller and the communication methods.

Describes the instructions used in MP900/MP2000 ladder programming.

Describes the instructions used in MP2000 motion programming.

Describes how to install and operate the programming tool MPE720 version 6 for MP2000 Series Machine Controllers.

Describes how to install and operate the MP900/ MP2000 Series programming system (MPE720).

Describes the programming instructions of the New Ladder Editor, which assists MP900/MP2000 Series design and maintenance.

Describes the operating methods of the New Ladder Editor, which assists MP900/MP2000 Series design and maintenance.

Describes the functions, specifications, and application methods of the MP920 Communication Modules (217IF, 215IF, and 218IF).

 Copyrights

 DeviceNet is a registered trademark of the ODVA (Open DeviceNet Venders Association).  Ethernet is a registered trademark of the Xerox Corporation.  PROFIBUS is a trademark of the PROFIBUS User Organization.  MPLINK is a trademark of the Yaskawa Electric Corporation.  MECHATROLINK is a trademark of the MECHATROLINK Members Association.  Other product names and company names are the trademarks or registered trademarks of the respective company.

“TM” and the mark do not appear with product or company names in this manual.

WARNING

CAUTION

PROHIBITED

●

WARNING

Safety Information

The following conventions are used to indicate precautions in this manual. Information marked as shown below is important for the safety of the user. Always read this information and heed the precautions that are provided. The conventions are as follows:

Indicates precautions that, if not heeded, could possibly result in loss of life or serious injury.

Indicates precautions that, if not heeded, could result in relatively serious or minor injury, or property damage.

If not heeded, even precautions classified under can lead to serious results

depending on circumstances.

Indicates prohibited actions. Specific prohibitions are indicated inside .

For example, indicates no fire or open flame.

MANDATORY

Indicates mandatory actions. Specific actions are indicated inside .

For example, indicates that grounding is required.

Safety Precautions

The following precautions are for checking products on delivery, storage, transportation, installation, wiring, operation, application, inspection, and disposal. These precautions are important and must be observed.

 General Precautions

 Before starting operation while connected to the machine, ensure that an emergency stop procedure has

been provided and is working correctly.

There is a risk of injury.

 Do not touch anything inside the product.

There is a risk of electrical shock.

 Always keep the front cover attached when power is being supplied.

There is a risk of electrical shock.

 Observe all procedures and precautions given in this manual for trial operation.

Operating mistakes while the Servomotor and machine are connected can cause damage to the machine or even accidents resulting in injury or death.

 Do not remove the front cover, cables, connector, or options while power is being supplied.

There is a risk of electrical shock.

 Do not damage, pull on, apply excessive force to, place heavy objects on, or pinch cables.

There is a risk of electrical shock, operational failure of the product, or burning.

 Do not attempt to modify the product in any way.

There is a risk of injury or device damage.

 Do not approach the machine when there is a momentary interruption to the power supply. When power is

restored, the MP2000 Series Machine Controller or machine connected to it may start operation suddenly. Provide suitable safety measures to protect people when operation restarts.

There is a risk of injury.

 Do not allow installation, disassembly, or repairs to be performed by anyone other than specified person-

nel.

There is a risk of electrical shock or injury.

CAUTION

 Storage and Transportation

 Do not store or install the product in locations subject to the following. There is a risk of fire, electric shock,

and machine product damage.

 Direct sunlight  Ambient temperatures exceeding the storage or operating conditions  Ambient humidity exceeding the storage or operating conditions  Extreme changes in temperature that would result in condensation  Corrosive or flammable gas  Excessive dust, dirt, salt, or metallic powder  Water, oil, or chemicals  Vibration or shock

 Do not overload the product during transportation.

There is a risk of injury or an accident.

 Never subject the product to an atmosphere containing halogen (fluorine, chlorine, bromine, or iodine) dur-

ing transportation or installation.

There is a risk of device damage or an accident.

 If disinfectants or insecticides must be used to treat packing materials such as wooden frames, pallets, or

plywood, the packing materials must be treated before the product is packaged, and methods other than fumigation must be used. Example: Heat treatment, where materials are kiln-dried to a core temperature of 56 minutes or more.

If the electronic products, which include stand-alone products and products installed in machines, are packed with fumigated wooden materials, the electrical components may be greatly damaged by the gases or fumes resulting from the fumigation process. In particular, disinfectants containing halogen, which includes chlorine, fluorine, bromine, or iodine can contribute to the erosion of the capacitors.

°C for 30

 Installation

 Never use the product in locations subject to water, corrosive atmospheres, or flammable gas, or near

burnable objects.

There is a risk of electrical shock or fire.

 Do not step on the product or place heavy objects on the product.

There is a risk of injury.

 Do not block the air exhaust port on the product. Do not allow foreign objects to enter the product.

There is a risk of element deterioration inside, an accident, or fire.

 Always mount the product in the specified orientation.

There is a risk of an accident.

 Do not subject the product to strong shock.

There is a risk of an accident.

CAUTION

Steel separator

Example of Separated External Cables

Power circuit

cables

General

control circuit

cables

Digital I/O

signal cables

 Wiring

 Check the wiring to be sure it has been performed correctly.

There is a risk of motor run-away, injury, or an accident.

 Always use a power supply of the specified voltage.

There is a risk of burning.

 In places with poor power supply conditions, take all steps necessary to ensure that the input power is sup-

plied within the specified voltage range.

There is a risk of device damage.

 Install breakers and other safety measures to provide protection against shorts in external wiring.

There is a risk of fire.

 Provide sufficient shielding when using the product in the locations subject to the following.

There is a risk of device damage.

 Noise, such as from static electricity  Strong electromagnetic or magnetic fields  Radiation  Near power lines

 Selecting, Separating, and Laying External Cables

 Consider the following items when selecting the I/O signal lines (external cables) to connect the product to

external devices.

 Mechanical strength  Noise interference  Wiring distance  Signal voltage, etc.

 Separate the I/O signal lines from the power lines both inside and outside the control box to reduce the

influence of noise from the power lines.

If the I/O signal lines and power lines are not separated properly, malfunctioning may result.

vii

CAUTION

 Maintenance and Inspection Precautions

 Do not attempt to disassemble the product.

There is a risk of electrical shock or injury.

 Do not change wiring while power is being supplied.

There is a risk of electrical shock or injury.

 Disposal Precautions

 Dispose of the product as general industrial waste.

 General Precautions

Observe the following general precautions

to ensure safe application.

 The products shown in illustrations in this manual are sometimes shown without covers or protective

guards. Always replace the cover or protective guard as specified first, and then operate the products in accordance with the manual.

 The drawings presented in this manual are typical examples and may not match the product you received.  If the manual must be ordered due to loss or damage, inform your nearest Yaskawa representative or one

of the offices listed on the back of this manual.

viii

Warranty

( 1 ) Details of Warranty

 Warranty Period

The warranty period for a product that was purchased (hereinafter called “delivered product”) is one year from the time of delivery to the location specified by the customer or 18 months from the time of shipment from the Yaskawa factory, whichever is sooner.

 Warranty Scope

Yaskawa shall replace or repair a defective product free of charge if a defect attributable to Yaskawa occurs during the warranty period above. This warranty does not cover defects caused by the delivered product reaching the end of its service life and replacement of parts that require replacement or that have a limited service life. This warranty does not cover failures that result from any of the following causes.

1. Improper handling, abuse, or use in unsuitable conditions or in environments not described in product catalogs or manuals, or in any separately agreed-upon specifications

2. Causes not attributable to the delivered product itself

3. Modifications or repairs not performed by Yaskawa

4. Abuse of the delivered product in a manner in which it was not originally intended

5. Causes that were not foreseeable with the scientific and technological understanding at the time of shipment from Ya sk a wa

6. Events for which Yaskawa is not responsible, such as natural or human-made disasters

( 2 ) Limitations of Liability

1. Yaskawa shall in no event be responsible for any damage or loss of opportunity to the customer that arises due to failure of the delivered product.

2. Yaskawa shall not be responsible for any programs (including parameter settings) or the results of program execution of the programs provided by the user or by a third party for use with programmable Yaskawa products.

3. The information described in product catalogs or manuals is provided for the purpose of the customer purchasing the appropriate product for the intended application. The use thereof does not guarantee that there are no infringements of intellectual property rights or other proprietary rights of Yaskawa or third parties, nor does it construe a license.

4. Yaskawa shall not be responsible for any damage arising from infringements of intellectual property rights or other proprietary rights of third parties as a result of using the information described in catalogs or manuals.

( 3 ) Suitability for Use

1. It is the customer’s responsibility to confirm conformity with any standards, codes, or regulations that apply if the Yaskawa product is used in combination with any other products.

2. The customer must confirm that the Yaskawa product is suitable for the systems, machines, and equipment used by the customer.

3. Consult with Yaskawa to determine whether use in the following applications is acceptable. If use in the application is acceptable, use the product with extra allowance in ratings and specifications, and provide safety measures to minimize hazards in the event of failure.

• Outdoor use, use involving potential chemical contamination or electrical interference, or use in conditions or environments not described in product catalogs or manuals

• Nuclear energy control systems, combustion systems, railroad systems, aviation systems, vehicle systems, medical equipment, amusement machines, and installations subject to separate industry or government regulations

• Systems, machines, and equipment that may present a risk to life or property

• Systems that require a high degree of reliability, such as systems that supply gas, water, or electricity, or systems that operate continuously 24 hours a day

• Other systems that require a similar high degree of safety

4. Never use the product for an application involving serious risk to life or property without first ensuring that the system is designed to secure the required level of safety with risk warnings and redundancy, and that the Yaskawa product is properly rated and installed.

5. The circuit examples and other application examples described in product catalogs and manuals are for reference. Check the functionality and safety of the actual devices and equipment to be used before using the product.

6. Read and understand all use prohibitions and precautions, and operate the Yaskawa product correctly to prevent accidental harm to third parties.

( 4 ) Specifications Change

The names, specifications, appearance, and accessories of products in product catalogs and manuals may be changed at any time based on improvements and other reasons. The next editions of the revised catalogs or manuals will be published with updated code numbers. Consult with your Yaskawa representative to confirm the actual specifications before purchasing a product.

Using this Manual - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - iii Safety Information - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - v Safety Precautions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - v Warranty - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ix

1 FL-net Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-1

1.1 What is FL-net? - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-2

1.2 FL-net Protocol- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-2

1.3 FL-net Features - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-3

1.4 FAQ on FL-net - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-4

1.5 Basic FL-net Terminology - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-6

2 Overview of 262IF-01 Module - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-1

2.1 Overview of 262IF-01 Module - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-2

2.1.1 Module Specifications - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-3

2.1.2 Appearance and Connectors - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-6

2.1.3 Status Indicators (LEDs)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-6

2.1.4 Communication Status Indicators (LED) (Included with Ethernet Connector) - - - - - - - - - - - - - 2-6

2.1.5 Switch Settings - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-7

2.2 Connection Specifications - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-8

2.2.1 Connector Specifications - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-8

2.2.2 Cable Specifications - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-8

2.3 System Configuration Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-9

2.3.1 Small-scale Configuration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-9

2.3.2 Basic Configuration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-9

2.3.3 Locally Concentrated Device Configuration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-10

2.3.4 Long Distant, Locally Distributed Device Configuration - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-11

3 Mounting and Starting the Module - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-1

3.1 Applicable Machine Controllers and Supported Versions - - - - - - - - - - - - - - - - 3-2

3.1.1 Applicable Machine Controllers- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-2

3.1.2 Supported CPU and MPE720 Versions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-2

3.2 Mounting and Removing a Module on Machine Controller - - - - - - - - - - - - - - - 3-3

3.2.1 Mounting a 262IF-01 Module - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-3

3.2.2 Removing a 262IF-01 Module- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-6

3.3 Setting the Communication Manager - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-8

3.3.1 Opening the Communication Manager - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-8

3.3.2 Setting the Communication Manager- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-9

3.4 Self-configuration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-19

3.4.1 Executing Self-configuration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-19

3.5 Starting the MPE720 and Setting Communication or Network Parameters - - - - 3-20

3.5.1 Starting MPE720 Ver. 6 and Setting Communication- - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-20

3.5.2 Starting MPE720 Ver. 5.  and Setting the Network - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-21

4 FL-net Transmission Definition - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-1

4.1 Displaying the FL-net Transmission Configuration Window- - - - - - - - - - - - - - - - 4-2

4.1.1 Displaying the Module Configuration Window - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-2

4.1.2 Displaying the FL-net Transmission Configuration Window from the Module Configuration Window - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-3

4.2 FL-net Transmission Definition- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-4

4.2.1 Transmission Parameters Tab Page - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-4

4.2.2 Link Assignment Tab Page - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-6

4.2.3 Link Status Tab Page - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-9

4.2.4 Status Detail Window - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-10

4.2.5 Status Tab Page - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-12

4.2.6 Network Configuration Window - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-13

4.2.7 Saving FL-net Transmission Definitions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-14

5 Details of FL-net - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-1

5.1 Ethernet Segment Configuration Example - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-2

5.1.1 10BASE5 System - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-2

5.1.2 10BASE-T System - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-2

5.1.3 100BASE-TX system - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-3

5.1.4 Ethernet IP Address - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-4

5.2 About FL-net - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-5

5.2.1 FL-net Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-5

5.3 FL-net Data Communication - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-9

5.3.1 Cyclic Transmission - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-9

5.3.2 Message Transmission - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-12

5.3.3 Details of Supported Messages - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-14

6 Message Send and Receive Functions - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-1

6.1 Message Send Function - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-2

6.1.1 Outline Specifications - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-2

6.1.2 MSG-SND Function Setting Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-3

6.1.3 Inputs and Outputs for the Message Send Function - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-3

6.1.4 Parameter List for MSG-SND Function - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-9

6.1.5 Parameter Details for MSG-SND Function - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-10

6.1.6 Specifying an FL-net Virtual Address Space Using the MSG-SND Function - - - - - - - - - - - - 6-15

6.1.7 Relationship among the Data Address, Data Size, and Offset in the MSG-SND Function - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-16

6.2 Message Receive Function - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-17

6.2.1 Basic Specifications - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-17

6.2.2 MSG-RCV Function Setting Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-18

6.2.3 Inputs and Outputs for the Message Receive Function - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-18

6.2.4 Parameter List for MSG-RCV Function - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-23

6.2.5 Parameter Details for MSG-RCV Function - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-24

6.2.6 Relationship among the Data Address, Data Size, and Offset in the MSG-RCV Function - - 6-28

xii

6.3 Combination of FL-net Messages and Message Functions - - - - - - - - - - - - - - - 6-29

6.4 Displaying a Register List and Notes at Register Input - - - - - - - - - - - - - - - - - - 6-30

6.4.1 Displaying a Register List - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-30

6.4.2 Notes at Register Input - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-32

6.5 Programming Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-33

6.5.1 Word Block Data Read (Client) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-33

6.5.2 Word Block Data Write (Client)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-36

6.5.3 Word Block Data Read/Write (Server) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-39

6.5.4 Sending Request (Client)/Response (Server) according to Non-procedure Protocol - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-42

6.5.5 Sending Request/Receiving Response (Client) according to Non-procedure Protocol - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-45

6.5.6 Receiving Transparent Message Request (Server)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-51

7 Troubleshooting- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-1

7.1 Before Starting to Locate Faults - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-2

7.2 Common Network Problems and Countermeasures- - - - - - - - - - - - - - - - - - - - 7-3

7.2.1 When Communication Is not Possible or It Is Unstable - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-3

7.2.2 Confirming 262IF-01 Setting - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-4

7.2.3 System I/O Error Status - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-5

7.2.4 Details on I/O Error Status - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-9

7.3 Notes on Regular Usage of FL-net - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-12

Appendices - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-1

Appendix A Network System Definition - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-2

A.1 Communication Protocol Standard- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-2 A.2 Hierarchical Structure of Communication Protocol- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-2 A.3 FL-net Physical Layer - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-2 A.4 FL-net IP Address - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-3 A.5 FL-net Subnet Mask- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-3 A.6 TCP/IP, UDP/IP Communication Protocol- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-4 A.7 FL-net Port Number - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-4 A.8 FL-net Data Format - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-5

Appendix B FL-net Network Management - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-7

B.1 FL-net Token Management - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-7 B.2 Joining/Leaving FL-net - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-9 B.3 Node Status Management - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-11 B.4 FL-net Local Node Management Table - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-11 B.5 FL-net Join Node Management Table - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-12 B.6 FL-net Status Management- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-13 B.7 FL-net Message Serial Number Management- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-13

Appendix C FL-net System Grounding - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-14

C.1 Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-14 C.2 Power Supply Wiring and Grounding - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-15 C.3 Network Equipment Connection in the FL-net System - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-16 C.4 Laying and Grounding a Wiring Duct and a Conduit - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-17 C.5 FL-net Construction Work Check Sheet - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-18

Appendix D Supplement on FL-net Profile - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-19

D.1 262IF-01 Profile- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-19 D.2 ANS.1 Transfer Syntax Summary - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-20

Appendix E Differences from CP Series/262IF - - - - - - - - - - - - - - - - - - - - - - - - - A-23

INDEX - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Index-1

Revision History

xiii

1

FL-net Overview

FL-net Overview

This chapter gives an overview of FL-net.

 For details on FL-net, refer to Chapter 5 Details of FL-net.

1.1 What is FL-net? - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -1-2

1.2 FL-net Protocol - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -1-2

1.3 FL-net Features - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -1-3

1.4 FAQ on FL-net - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -1-4

1.5 Basic FL-net Terminology - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -1-6

1-1

1.1 What is FL-net?

MP2200

218IF-02 262IF-01

LIO-04SVB-01

CPU-02

LIO-04 LIO-04 LIO-01 LIO-01

MP2300

218IF-02 262IF-01

SVB-01

PC PC PC EWS

PLCPLCPLC

Server

WAN

Panel controller

CNC RC

Sensor actuator

Computer

Controller

Equipment

Upper LAN Ethernet 䋨TCP/IP, UDP/IP䋩

FL-net (Ethernet-based control network)

Field network

1.1 What is FL-net?

As shown in Fig. 1.1, FL-net is a network capable of interconnecting various FA controllers such as the programmable controllers (PLC) and computer numeric control equipment (CNC) from many manufacturers, and personal computers for control and monitoring.

1.2 FL-net Protocol

The following shows a basic FL-net protocol structure.

The transport and network layers use UDP/IP, while the data link and physical layers use Ethernet.

Fig. 1.1 Example of FA Control Network Configuration

Application layer

FA link protocol layer

Transport layer

Network layer

Data link layer

Physical layer

Controller or interface

Service function

Cyclic transmission

Message transmission

Token function

UDP

Ethernet

(Based on IEEE802.3)

Fig. 1.2 Basic FL-net Protocol Structure

FL-net protocol

1-2

FL-net Overview

1.3 FL-net Features

FL-net has the following features:

• Open control network

• Realization of multi-vendor environments

• FL-net is capable of interconnecting controllers such as the programmable controllers (PLC) and computer numeric control equipment (CNC) from many manufacturers, and personal computers for control and monitoring.

In addition, FL-net has the following features.

 Compliant with Worldwide Standards

Efficient communication based on standard UDP/IP is realized as well as de facto standard Ethernet for OA equipment communication. Ethernet provides the following advantages.

– Low cost

Prevailing communication devices can be used, resulting in low cost.

– Availability of prevailing network devices

A wide variety of prevailing network devices such as transceivers, hubs, cables, and PC LAN cards for Ethernet can be used.

1.3 FL-net Features

– Realization of high-speed communication

In the future, the baud rate can be increased to support 10 Mbps, 100 Mbps, and 1 Gbps.

– Communication via optical fiber cables

The prevailing Ethernet optical repeater allows optical fibers to be used in the corresponding section for communication over distances of 500 m or more, improves noise resistance, and prevents of surge currents caused by lightning strikes in outside wiring.

 Support of Necessary Communication Functions between FA Controllers

Because user requirements are fully examined as specifications, various features required for FA are supported.

– Large network

A maximum of 254 pieces of equipment (nodes) can be connected.

– Support of two types of communication functions according to purpose

The common memory function allows each node to share the same data through cyclic communication, and the message communication function allows only necessary information to be transferred on demand.

– Large common memory

A large common memory (8 kbits + 8 kwords) is supported.

– Fast response

A fast response of 50 ms/32 nodes (2 kbits +2 kwords) can be realized.

– High reliability by masterless system

Because no master station is needed, each node can join or leave without affecting communications between other nodes. Thus, each node can be turned ON or OFF and maintained independently.

1-3

1.4 FAQ on FL-net

The following gives a list of frequently asked questions and answers.

Question Answer

What is Ethernet?

What is FL-net?

What is the difference between

FL-net and Ethernet?

How should we use the FN-net

unit?

What is a protocol?

What protocol is supported by FL-net?

Does FL-net allow general PC

connections?

What is topology?

What types of network cables are available? How long are

the cables and how many nodes can be connected to them?

When a system uses FL-net,

does it need a special Ethernet?

How should we make FL-net

connections?

Ethernet refers to a cable type specification, and is available with local area networks (LAN). Ethernet enables data transfer between computers at a baud rate from 10 Mbps to 100 Mbps. Presently, the prevailing Ethernet cable for office automation is a 100-Mbp twisted pair cable (UTP). Ethernet allows communication through the use of multi-vendor software protocols.

FL-net refers to a network capable of interconnecting FA controllers such as programmable controllers (PLC) and computer numeric control (CNC) equipment so as to transfer control data at high speed between controllers. Cables are identical to those employed for Ethernet.

Ethernet is used to connect controllers to the host computer or PC so that production directions can be given or performance information can be obtained for informational or control purposes. On the other hand, FL-net is used to connect controllers for highspeed control data transfer. When one controller is used for both an FL-net to connect controllers and an Ethernet to connect controllers to the host devices, care should be taken for correct cable connection.

The FL-net unit should be installed in FA controllers such as a programmable controller (PLC) and computer numeric control (CNC) equipment so that data transfer can take place cyclically between the controllers as long as link assignments for station numbers (node numbers) and common memory (also called “link register”) are simply made in the same manner as for regular PLC CPU link units. In this case, no special communication program is required for PLC, etc. In addition, when PLC memory contents or communication parameters are read or written from PC, no special communication program is required for PLC, etc. However, note that each controller should be provided with a communication program when data transfer is attempted between controllers through message transmission.

Protocol refers to a set of rules required for communication. FL-net employs an FL-net-dedicated FA link protocol that lies in the UDP/IP or upper layers.

The FL-net units to be installed in FA controllers such as a programmable controller (PLC) and computer numeric control (CNC) equipment are intelligent units with processors on their boards. Because PC Ethernet cards are non-intelligent cards called “dumb cards,” it is generally recommended to use FL-net boards according to PC performance and usage.

A networking topology refers to a network wiring method. Though star (tree), bus, and ring topologies are available as main topologies, they can be understood more easily from a viewpoint of logical wiring rather than physical wiring. A star topology is used for 10BASE-T/100BASE-TX in FL-net. On the other hand, a bus topology is used for 10BASE5 in FL-net.

The following summarizes the standards, characteristics, and restrictions of the most popular Ethernet cables.

•

10BASE-T/100BASE-TX: Twisted pair cable (UTP), maximum transmission dista

nce per segment: 100 m (500 m), maximum number of connectable nodes per seg-

ment: 254

• 10BASE5: Thick coaxial cable (yellow cable), maximum transmission distance per segment: 500 m (2,500 m), maximum number of connectable nodes per segment: 100 (254)

• 10BASE-FL/100BASE-FX: Optical fiber cable, maximum transmission distance per segment: 2,000 m, maximum number of connectable nodes per segment: 254

∗ Values in ( ) assume the use of repeaters.

No. To build an FL-net system, Ethernet is used (which is formally compliant with IEEE802.3). Special specifications are not required.

Different types of Ethernet media can be interconnected with Ethernet cables through repeaters, media conversion adaptors, etc. These products can be purchased from many vendors.

1-4

FL-net Overview

Question Answer

What cable should be used to

build an FL-net system?

How should we set FL-net IP

addresses?

How conformance and interconnectivity have been

assured among FL-net support devices?

1.4 FAQ on FL-net

(cont’d)

Generally, cables should be used as follows.

• 10BASE5 (thick coaxial cable: yellow cable) is used for the backbone.

• 10BASE-T/100BASE-TX (twisted pair cable: UTP category 5) is used for cabling in control panels and offices.

• 10BASE-FL/100-BASE-FX (optical fiber cable) is used for cabling near high-voltage power supplies or places affected by electrical noise.

The FL-net IP addresses are:

Network address: 192.168.250,

Host number (node number): 1 to 254 These settings are standard. Note that numbers 250 to 254 have been reserved for use by maintenance tools.

There is an FL-net certification organization that conducts conformance and interconnectivity tests. Because certificates are issued to devices that have passed the tests, they can be used safely.

1-5

1.5 Basic FL-net Terminology

The following gives an overview of basic FL-net terminology.

FA equipment

Refers to an FA system component device connected to FL-net. Control equipment (controllers) such as the programmable controller (PLC), computer numeric control (CNC) equipment, and personal computer (PC) are all classified as FA equipment.

Network

Refers to a local area network (LAN) whose data link level complies with IEEE802.3 in FL-net. The existing standard supports a baud rate of 10 Mbps in both 10BASE5 and 10BASE-T.

Node

Refers to FA equipment connected to FL-net. Each node is assigned a node number (1 to 254) for identification.

Communication unit

Generally, refers to a set of a communication board and communication module necessary for communication via FL-net.

Networking equipment

Refers to IEEE802.3-compliant communication devices such as communication cables, transceivers, and hubs necessary for communication via FL-net.

Switching hub

Refers to a hub (line concentrator) equipped with a bridge function. A received packet is temporarily stored in the buffer for regenerative relaying.

Repeater hub

Refers to a hub (line concentrator) equipped with functions for electrically regenerating and relaying transmission signals on cables.

1-6

2

Overview of 262IF-01 Module

Overview of 262IF-01 Module

This chapter describes the 262IF-01 Module specifications and system configuration examples.

2.1 Overview of 262IF-01 Module - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -2-2

2.1.1 Module Specifications - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-3

2.1.2 Appearance and Connectors - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-6

2.1.3 Status Indicators (LEDs) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-6

2.1.4 Communication Status Indicators (LED) (Included with Ethernet Connector) - - - - - - - - 2-6

2.1.5 Switch Settings - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-7

2.2 Connection Specifications - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -2-8

2.2.1 Connector Specifications - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-8

2.2.2 Cable Specifications - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-8

2.3 System Configuration Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -2-9

2.3.1 Small-scale Configuration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-9

2.3.2 Basic Configuration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-9

2.3.3 Locally Concentrated Device Configuration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-10

2.3.4 Long Distant, Locally Distributed Device Configuration - - - - - - - - - - - - - - - - - - - - - - 2-11

2-1

2.1 Overview of 262IF-01 Module

MPE720

262IF-01

Ethernet

262IF-01

There is no serial port (RS-232C).

2.1 Overview of 262IF-01 Module

The 262IF-01 has been designed as a communication module for connecting to FL-net via an Ethernet interface (100BASE-TX or 10BASE-T). FL-net allows this module to be connected to equipment of other manufacturers. The 262IF-01 supports FL-net (OPCN-2) Version 2.0.

 Notes on 262IF-01

The 262IF-01 Module has been designed as a communication module dedicated for use in FL-net. Note the following points:

The 262IF-01 cannot be connected to a regular Ethernet from the 218IF-01 or 218IF-02.

Though the 262IF-01 Module uses a standard Ethernet cable, it does not allow connection for communications based on general-purpose TCP/IP or UDP/IP because it serves only as an FL-net-dedicated module.

MP2300 controller

MP2200 controller

Ethernet

218IF-02218IF-01

MPE720 262IF-01

The MPE720 engineering tool cannot be connected to the 262IF-01 directly.

When connecting the MPE720, separately prepare a module with any of the RS232C, Ethernet, and CP-215 ports for connection.

2-2

No serial port (RS-232C) has been mounted.

Overview of 262IF-01 Module

2.1.1 Module Specifications

This section provides the specifications of the 262IF-01 Module.

( 1 ) Hardware Specifications

Item Specifications

Name

Model Number

Communication Port

Indicators

Switch

Dimensions (mm)

Mass

262IF-01

JAPMC-CM2303-E

FL-net: 1 port

Module status indicators LED

RUN (green)

TX (green)

FL-net status indicator LED

LINK (orange), 100M (green)

TEST

125 × 95 mm (H × D)

80 g

2.1 Overview of 262IF-01 Module

2.1.1 Module Specifications

ERR (red) LNK (green) RX (green)

( 2 ) Transmission Specifications

Ethernet Transmission Specifications

FL-net Specifications

Item Specifications

100BASE-TX 10BASE-T

Interface RJ-45 connector

Compliance Standard

Media Access Mode CSMA/CD

Communication Mode Full duplex/half duplex

Modulation Method Baseband

Transmission Path Type Star topology

Baud Rate

Maximum Number of Cascade Connections

Transmission Path Length (Full length at repeater usage)

Transmission Media

Maximum Segment Length

Link Function

Transmission Control System

IP Address

Port Number

Protocol

Version

IEEE802.3u IEEE802.3i

100 Mbps 10 Mbps

2 layers 4 layers

100 m (205 m max.

Twisted pair cable (UTP)

Category 5 or 5e

Twisted pair cable (STP)

Category 5 or 5e (100 W)

(not possible to fix transmission and communication modes)

Token passing

Class C is used.

192. 168. 250. is used as standard ( indicates a number from 1 to 254 and corresponds to a node number).

For receiving: 3 ports (55000, 55001, and 55002) are used by the system. For sending: 1 port (55003) is used by the system.

FA link protocol

2.0

) 100 m (500 m max.*1)

Twisted pair cable (UTP)

Category 3, 4, 5, or 5e

Twisted pair cable (STP)

Category 3, 4, 5, or 5e (100 W)

100 m (distance between hub and node at UTP usage)

Support for auto-negotiation

Support for Auto MDI/MDI-X

2-3

2.1 Overview of 262IF-01 Module

2.1.1 Module Specifications

Number of Nodes

Cyclic Transmission Specifications

Maximum Data Size

Data Exchange

Number of Message Channels

Engineering

Message

Communication

Transmission Specifications

Message Service

Number of Transmission Words

Item Specifications

Up to 254 nodes (at repeater usage)

(262IF-01 I/O can be assigned to 64 nodes only including the self-node.)

Within network:

Area 1 (bit data): 8 kbits Area 2 (word data): 8 kwords

Per station:

Area 1 + area 2: Area allocation is allowed up to 8 kbits + 8 kwords.

N : N

Not supported

Word block read, word block write, network parameter read, network parameter

, stop command*3, start command*3,

write profile read, transparent message, log data read, log data clear, message loopback

Up to 512 words

(cont’d)

∗ 1. The cable length restriction in repeater (repeater hub or switching hub) usage varies depending on a selected

baud rate. For repeater or switching hubs, use a commercially available hub for Ethernet. Hubs manufactured by the Japan Electrical Manufacturer’s Association (JEMA) are recommended.

Restrictions on 100BASE-TX connection

•

Item

Cable length between node and hub

Cable length between hubs

Number of hubs between nodes

Restrictions on 10BASE-T connection

•

Item

Cable length between node and hub

Cable length between hubs

Number of hubs between nodes

When Repeater Hub Is

Connected

100 m or less 100 m or less

5 m or less 100 m or less

Up to 2 hubs Not limited

When Repeater Hub Is

Connected

100 m or less 100 m or less

Up to 4 hubs Not limited

When Switching Hub Is

Connected

When Switching Hub Is

Connected

∗ 2. The I/O assignment restriction, which defines that the maximum number of nodes as 64 nodes including the self-

node, is based on MP Series Machine Controller specifications.

∗ 3. A message can be only sent from the client. (Client: Data sending side, Server: Data receiving side)

2-4

Overview of 262IF-01 Module

( 3 ) Operating Environment Specifications

Item Specifications

Environmental Conditions

Mechanical Operating Conditions

Ambient Operating Temperature

Ambient Storage Temperature

Ambient Operating Humidity

Ambient Storage Humidity

Pollution Level Pollution level: 2 (conforming to JIS B3502)

Corrosive Gas There must be no combustible or corrosive gas.

Operating Altitude

Vibration Resistance

Shock Resistance

0 to +55 °C

–25 to +85 °C

30% to 95% (with no condensation)

5% to 95% (with no condensation)

2,000 m above sea level or lower

Conforming to JIS B3502

(1) Frequency: 16.7 Hz Vibration strength: 14.7 m/s (2) Frequency: 10 to 57 Hz Vibration strength: 0.075 mm of single-ampli

(3) Frequency: 57 to 150 Hz

Conforming to JIS B3502

Peak acceleration of 147 m/s directions

2.1 Overview of 262IF-01 Module

2.1.1 Module Specifications

tude

Vibration strength: 9.8 m/s2 of fixed acceleration

(15G) twice for 11 ms each in the X, Y, and Z

Electrical Operating Conditions

Installation Requirements

Conforming to EN 61000-6-2, EN 55011 (Group 1 Class A) Power supply noise (FT noise): ±2 kV min., for one minute

Noise Resistance

Ground Ground to 100Ω max.

Cooling Method Natural cooling

Radiation noise (FT noise): ±1 kV min., for one minute Ground noise (impulse noise): ±1 kV min., for ten minutes Electrostatic noise (contact discharge method): ±6 kV min., ten times

2-5

2.1 Overview of 262IF-01 Module

262IF-01

ERR

LNK

RUN

TEST

ONOFF

LINK

100M

FL-net

(25)

FL-net connector 100Base-TX/10Base-T

Status indicators (LEDs)

Switches

Communication status indicator (LED) (included with connector)

Unit: mm

ERR

LNK

RUN

2.1.2 Appearance and Connectors

The following diagram shows the appearance of the 262IF-01 Module and gives the external dimensions of the connectors.

2.1.3 Status Indicators (LEDs)

2.1.4 Communication Status Indicators (LED) (Included with Ethernet Connector)

The following table shows the status of the 262IF-01 Module shown by the LED indicators.

Indicator Color Meaning When Lit Meaning When Blinking Meaning When Not Lit

RUN Green

ERR Red

LNK Green

TX Green

RX Green

The indicators (LEDs) included with the Ethernet connector show the status of Ethernet communication.

Indicator Color Meaning When Lit Meaning When Not Lit

LINK Yellow

100M Green

FL-net link established. FL-net link not established.

Green: 100 Mbps 10 Mbps or not connected

Operating normally – An error has occurred.

• When RUN is lit:

–

Parameter setting error

• When RUN is not lit:

Normal

Hardware error

Joining FL-net – Not joining FL-net

Sending data – Not sending data

Receiving data – Not receiving data

2-6

Overview of 262IF-01 Module

2.1.5 Switch Settings

TEST

ONOFF

The following table shows the 262IF-01 Module switch settings.

2.1 Overview of 262IF-01 Module

2.1.5 Switch Settings

Label

(Switch No.)

–

(2)

TEST

(1)

 Always leave the unused switches (3 and 4) set to OFF.

Name Status Function

–

Operating Mode Selection

–OFF

OFF

Reserved

OFF

 Leave this switch set to OFF.

Fac-

tory

Setting

OFF

2-7

2.2 Connection Specifications

LINK

100M

FL-net

LINK

100M

FL-net

2.2.1 Connector Specifications

2.2 Connection Specifications

2.2.1 Connector Specifications

This section provides the connector specifications for the 262IF-01 Module.

( 1 ) Connector Specifications

Connector

Shape

( 2 ) Connector Pin Arrangement

The connector is used to connect the MP2000 Series Machine Controller to the devices on the FL-net via an FL-net connection.

Name Connector Name No. of Pins

FL-net FL-net 8

Connector Model

Module Cable Manufacturer

JOG-0001NL (LED/Pulse transformer builtin modular jack)

Pulse Engineering

Number

TXD+ O

TXD- O

RXD+ I

−−

2.2.2 Cable Specifications

Yaskawa does not provide FL-net cables. Obtain a commercially available category 5 cross or straight cable.

 The AUTO MDI/MDI-X automatically determines cross/straight when using the 262IF-01 Module.

Signal

Name

IO Description

Send data+ 5

Send data- 6

Receive data+ 7

− 8

Number

Signal Name

−−

RXD- I

−−

IO Description

−

Receive data-

−

2-8

Overview of 262IF-01 Module

2.3 System Configuration Example

Twisted pair cable (STP category 5) (Maximum cable length: 100 m)

RJ-45 connector

Hub

PLC from other manufacturer

MP2300

218IF-02 262IF-01

SVB-01

MP2200

218IF-02 262IF-01

LIO-04SVB-01

CPU-02

LIO-04 LIO-04 LIO-01 LIO-01

Twisted pair cable (STP category 5)

(Maximum cable length: 100 m)

AUI cable

(Maximum cable length: 50 m)

Ground terminal

Coaxial cable

(Maximum cable length: 500 m)

Single-port transceiver

Multi-port transceiver

Terminator

Hub

MP2300

218IF-02 262IF-01

SVB-01

PLC from other manufacturer

The following shows a system configuration example using the 262IF-01.

2.3.1 Small-scale Configuration

A network system of several devices can be constructed through the use of one hub.

2.3 System Configuration Example

2.3.1 Small-scale Configuration

2.3.2 Basic Configuration

A network system of dozens of devices can be constructed by connecting several multi-transceivers and hubs to one coaxial cable.

2-9

2.3 System Configuration Example

MP2200

218IF-02 262IF-01

LIO-04SVB-01

CPU-02

LIO-04 LIO-04 LIO-01 LIO-01

MP2300

218IF-02 262IF-01

SVB-01

Hub

Stackable hub

Twisted pair cable

(STP category 5)

(Maximum cable length: 100 m)

PLC from other manufacturer

2.3.3 Locally Concentrated Device Configuration

When dozens of devices locally concentrate in a location, a stackable hub can be used to build a network system.

2-10

Overview of 262IF-01 Module

2.3.4 Long Distant, Locally Distributed Device Configuration

When a particular controller is far away in a basic configuration of a network system or there is a high-voltage power supply or noise source near the network, the network can be divided into two segments that are connected with an optical repeater so that a long distant noise-proof network system can be built.

Optical fiber cable

(Maximum cable length: 2 km)

2.3 System Configuration Example

MP2300

SVB-01

218IF-02 262IF-01

Optical repeater

Hub

Twisted pair cable (STP category 5) (Maximum cable length: 100 m)

RJ-45 connector

PLC from other manufacturer

Coaxial cable

(Maximum cable length: 500 m)

Optical repeater

AUI cable

(Maximum cable length: 50 m)

2-11

+ 148 hidden pages