YASKAWA MP3000 User Manual

Machine Controller MP3000 Series

Communications

USER'S MANUAL

MANUAL NO. SIEP C880725 12B

Outline of Communications

Ethernet Communications

1

2

Copyright © 2011 YASKAWA ELECTRIC CORPORATION

All rights reserved. No part of this publication may be reproduced, stored in a retrieval sys­tem, or transmitted, in any form, or by any means, mechanical, electronic, photocopying,
recording, or otherwise, without the prior written permission of Yaskawa. No patent liabil­ity 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 informa­tion 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.

About this Manual

This manual describes the specifications, system configuration, and communications connection methods for
the Ethernet communications that are used with an MP3000-series Machine Controller.

Read this manual carefully to ensure the correct usage of the Machine Controller and apply the Machine Con­troller to control your manufacturing system.

Keep this manual in a safe place so that it can be referred to whenever necessary.

Using this Manual

 Basic Terms

Unless otherwise specified, the following definitions are used:

• MP3000: A Machine Controller in the MP3000 Series

• MPE720: The Engineering Tool or a personal computer running the Engineering Tool

• PLC: A Programmable Logic Controller

 MPE720 Engineering Tool Version Number

In this manual, the operation of MPE720 is described using screen captures of MPE720 version 7.

For this reason, the screen captures and some descriptions may differ for MPE720 version 6.

 Copyrights

• DeviceNet is a registered trademark of the ODVA (Open DeviceNet Venders Association).

• PROFIBUS is a trademark of the PROFIBUS User Organization.

• Ethernet is a registered trademark of the Xerox Corporation.

• Microsoft, Windows, Windows NT, and Internet Explorer are trademarks or registered trademarks of the
Microsoft 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 com­pany. “TM” and the ® mark do not appear with product or company names in this manual.

iii

Important

Note

Example

Information

Terms

 Visual Aids

The following aids are used to indicate certain types of information for easier reference.

Indicates precautions or restrictions that must be observed.

Indicates alarm displays and other precautions that will not result in machine damage.

Indicates items for which caution is required or precautions to prevent operating mistakes.

Indicates operating or setting examples.

Indicates supplemental information to deepen understanding or useful information.

Indicates definitions of difficult terms or terms that have not been previously explained in this
manual.

Related Manuals

The following table lists the manuals that are related to the MP2000/MP3000-series Machine Controllers.
Refer to these manuals as required.

Function Manual Name Manual Number Contents

Describes the functions of the MP2000/
MP3000-series Machine Controllers and
the procedures that are required to use the
Machine Controller, from installation and
connections to settings, programming,
trial operation, and debugging.

Describes troubleshooting an MP3000­series Machine Controller.

Describes the specifications and system
configuration of the Basic Units in an
MP3000-series Machine Controller and
the functions of the CPU Unit.

Describes the specifications and system
configuration of an MP3000-series
MP3300 Machine Controller and the
functions of the CPU Module.

Provides information on the Communica­tions Modules that can be connected to
an MP2000-series Machine Controller
and describes the communications meth­ods.

Describes the ladder programming speci­fications and instructions of MP3000­series Machine Controller.

Continued on next page.

Basic func­tionality

Communica­tions func­tionality

Program­ming

Machine Controller MP2000/MP3000
Series Machine Controller System
Setup Manual

Machine Controller MP3000 Series
MP3200/MP3300
Troubleshooting Manual

Machine Controller MP3000 Series
MP3200
User’s Manual

Machine Controller MP3000 Series
MP3300
Product Manual

Machine Controller MP2000 Series
Communication Module
User’s Manual

Machine Controller MP3000 Series
Ladder Programming Manual

SIEP C880725 00

SIEP C880725 01

SIEP C880725 10

SIEP C880725 21

SIEP C880700 04

SIEP C880725 13

iv

Continued from previous page.

CAUTION

MANDATORY

Function Manual Name Manual Number Contents

MPE720 Version 7 System Integrated
Engineering
Tool

Engineering Tool for MP2000/MP3000

Series Machine Controller

User’s Manual

SIEP C880761 03

Describes how to operate MPE720 ver­sion 7.

Safety Precautions

The following signal words and marks are used to indicate safety precautions in this manual.

Information marked as shown below is important for safety. Always read this information and heed the pre­cautions that are provided.

DANGER

CAUTION

PROHIBITED

The following precautions are for storage, transportation, installation, wiring, operation, maintenance, inspec­tion, and disposal. These precautions are important and must be observed.

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 as cautions ( ) can lead to
serious results depending on circumstances.

Indicates prohibited actions. For example, indicates prohibition of open
flame.

Indicates mandatory actions. For example, indicates that grounding is
required.

v

WARNING

CAUTION

 General Precautions

• The installation must be suitable and it must be performed only by an experienced technician.

There is a risk of electrical shock or injury.

• Before connecting the machine and starting operation, make sure that an emergency stop pro­cedure has been provided and is working correctly.

There is a risk of injury.

• Do not approach the machine after a momentary interruption to the power supply. When power
is restored, the Machine Controller and the device connected to it may start operation suddenly.
Provide safety measures in advance to ensure human safety when operation restarts.

There is a risk of injury.

• Do not touch anything inside the Machine Controller.

There is a risk of electrical shock.

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

There is a risk of electrical shock, malfunction, or damage.

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

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

• Do not attempt to modify the Machine Controller in any way.

There is a risk of injury or device damage.

 Storage and Transportation

• Do not store the Machine Controller in any of the following locations.

• Locations that are subject to direct sunlight

• Locations that are subject to ambient temperatures that exceed the storage conditions

• Locations that are subject to ambient humidity that exceeds the storage conditions

• Locations that are subject to rapid temperature changes and condensation

• Locations that are subject to corrosive or inflammable gas

• Locations that are subject to excessive dust, dirt, salt, or metallic powder

• Locations that are subject to water, oil, or chemicals

• Locations that are subject to vibration or shock
There is a risk of fire, electrical shock, or device damage.

• Hold onto the main body of the Machine Controller when transporting it.

Holding the cables or connectors may damage them or result in injury.

• Do not overload the Machine Controller during transportation. (Follow all instructions.)

There is a risk of injury or an accident.

• Never subject the Machine Controller to an atmosphere containing halogen (fluorine, chlorine,
bromine, or iodine) during transportation.

There is a risk of malfunction or damage.

• 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°C for 30 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.

vi

 Installation

• Do not install the Machine Controller in any of the following locations.

• Locations that are subject to direct sunlight

• Locations that are subject to ambient temperatures that exceed the operating conditions

• Locations that are subject to ambient humidity that exceeds the operating conditions

• Locations that are subject to rapid temperature changes and condensation

• Locations that are subject to corrosive or inflammable gas

• Locations that are subject to excessive dust, dirt, salt, or metallic powder

• Locations that are subject to water, oil, or chemicals

• Locations that are subject to vibration or shock
There is a risk of fire, electrical shock, or device damage.

• Never install the Machine Controller in an atmosphere containing halogen (fluorine, chlorine,
bromine, or iodine).

There is a risk of malfunction or damage.

• Do not step on the Machine Controller or place heavy objects on the Machine Controller.

There is a risk of injury or an accident.

• Do not block the air exhaust ports on the Machine Controller. Do not allow foreign objects to
enter the Machine Controller.

There is a risk of internal element deterioration, malfunction, or fire.

• Always mount the Machine Controller in the specified orientation.

There is a risk of malfunction.

• Leave the specified amount of space between the Machine Controller, and the interior surface
of the control panel and other devices.

There is a risk of fire or malfunction.

• Do not subject the Machine Controller to strong shock.

There is a risk of malfunction.

• Suitable battery installation must be performed and it must be performed only by an experi­enced technician.

There is a risk of electrical shock, injury, or device damage.

• Do not touch the electrodes when installing the Battery.

Static electricity may damage the electrodes.

CAUTION

vii

CAUTION

Example of Separated Cables

Power cable

I/O signal

cables in

control circuits

Steel separator

 Wiring

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

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

• Always use a power supply of the specified voltage.

There is a risk of fire or accident.

• In places with poor power supply conditions, ensure that the input power is supplied 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 wir­ing.

There is a risk of fire.

• Provide sufficient shielding when using the Machine Controller in the following locations.

• Locations that are subject to noise, such as from static electricity

• Locations that are subject to strong electromagnetic or magnetic fields

• Locations that are subject to radiation

• Locations that are near power lines
There is a risk of device damage.

• Configure the circuits to turn ON the power supply to the CPU Unit/CPU Module before the 24­V I/O power supply. Refer to the following manuals for details on circuits.

MP3000 Series CPU Unit Instructions (Manual No.: TOBP C880725 16)
MP3000 Series MP3300 CPU Module Instructions (Manual No.: TOBP C880725 23)

If the power supply to the CPU Unit/CPU Module is turned ON after the external power supply, e.g., the
24-V I/O power supply, the outputs from the CPU Unit/CPU Module may momentarily turn ON when
the power supply to the CPU Unit/CPU Module turns ON. This can result in unexpected operation that
may cause injury or device damage.

• Provide emergency stop circuits, interlock circuits, limit circuits, and any other required safety
measures in control circuits outside of the Machine Controller.

There is a risk of injury or device damage.

• If you use MECHATROLINK I/O Modules, use the establishment of MECHATROLINK commu­nications as an interlock output condition.

There is a risk of device damage.

• Connect the Battery with the correct polarity.

There is a risk of battery damage or explosion.

• Select the I/O signal wires for external wiring to connect the Machine Controller to external
devices based on the following criteria:

• Mechanical strength

• Noise interference

• Wiring distance

• Signal voltage

• Separate the I/O signal cables for control circuits from the power cables both inside and outside
the control panel to reduce the influence of noise from the power cables.

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

viii

 Operation

CAUTION

• Follow the procedures and instructions in the user’s manuals for the relevant Machine Control­lers to perform normal operation and trial operation.

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

• Implement interlock signals and other safety circuits external to the Machine Controller to
ensure safety in the overall system even if the following conditions occur.

• Machine Controller failure or errors caused by external factors

• Shutdown of operation due to Machine Controller detection of an error in self-diagnosis and the subse-

quent turning OFF or holding of output signals

• Holding of the ON or OFF status of outputs from the Machine Controller due to fusing or burning of out-

put relays or damage to output transistors

• Voltage drops from overloads or short-circuits in the 24-V output from the Machine Controller and the

subsequent inability to output signals

• Unexpected outputs due to errors in the power supply, I/O, or memory that cannot be detected by the

Machine Controller through self-diagnosis.

There is a risk of injury, device damage, or burning.

CAUTION

 Maintenance and Inspection

• Do not attempt to disassemble or repair the Machine Controller.

There is a risk of electrical shock, injury, or device damage.

• Do not change any wiring while power is being supplied.

There is a risk of electrical shock, injury, or device damage.

• Suitable battery replacement must be performed and it must be performed only by an experi­enced technician.

There is a risk of electrical shock, injury, or device damage.

• Do not forget to perform the following tasks when you replace the CPU Unit/CPU Module:

• Back up all programs and parameters from the CPU Unit/CPU Module that is being replaced.

• Transfer all saved programs and parameters to the new CPU Unit/CPU Module.
If you operate the CPU Unit/CPU Module without transferring this data, unexpected operation may

occur. There is a risk of injury or device damage.

• Do not touch the heat sink on the CPU Unit/CPU Module while the power supply is turned ON
or for a sufficient period of time after the power supply is turned OFF.

The heat sink may be very hot, and there is a risk of burn injury.

 Disposal

CAUTION

• Dispose of the Machine Controller as general industrial waste.

• Observe all local laws and ordinances when you dispose of used Batteries.

ix

 Other General Precautions

Observe the following general precautions to ensure safe application.

• The products shown in the 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 illustrations that are 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 representa­tive or one of the offices listed on the back of this manual.

x

Warranty

 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 reach­ing 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.

• Improper handling, abuse, or use in unsuitable conditions or in environments not described in product cata­logs or manuals, or in any separately agreed-upon specifications

• Causes not attributable to the delivered product itself

• Modifications or repairs not performed by Yaskawa

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

• Causes that were not foreseeable with the scientific and technological understanding at the time of shipment
from Yaskawa

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

 Limitations of Liability

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

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

• The information described in product catalogs or manuals is provided for the purpose of the customer pur­chasing 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.

• 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 manu­als.

xi

 Suitability for Use

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

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

• 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, medi­cal 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

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

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

• Read and understand all use prohibitions and precautions, and operate the Yaskawa product correctly to pre­vent accidental harm to third parties.

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

xii

1

Contents

About this Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Using this Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Related Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .iv

Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Warranty. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Outline of Communications

2

1.1

1.2

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

System Configuration Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Configuration with the MP3200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Configuration with the MP3300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Ethernet Communications

2.1

2.2

2.3

2.4

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Ethernet Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Communications Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Detail Definition Setting Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Displaying the 218IFD Detail Definition Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

218IFD Detail Definition Dialog Box Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Communications Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18

Communications with MP-series Controllers . . . . . . . . . . . . . . . . . . . . .2-20

Using Automatic Reception with the MP3000 as a Slave . . . . . . . . . . . . . . . . . . . . . . . 2-20

Using the MSG-RCVE Function with the MP3000 as a Slave . . . . . . . . . . . . . . . . . . . . 2-30

Using I/O Message Communications with the MP3000 as the Master . . . . . . . . . . . . . 2-42

Using the MSG-SNDE Function with the MP3000 as the Master . . . . . . . . . . . . . . . . . 2-51

Message Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59

2.5

2.6

2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) 2-139

Communications with a Touch Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-90

Using Automatic Reception with the MP3000 as a Slave . . . . . . . . . . . . . . . . . . . . . . . 2-90

Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) 2-98

Using Automatic Reception with the MP3000 as a Slave . . . . . . . . . . . . . . . . . . . . . . . 2-98

Using I/O Message Communications with the MP3000 as the Master . . . . . . . . . . . . 2-105

Message Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-111

Using I/O Message Communications with the MP3000 as the Master . . . . . . . . . . . . 2-139

Using the MSG-SNDE Function with the MP3000 as the Master . . . . . . . . . . . . . . . . 2-146

Message Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-157

xiii

2.8

2.9

2.10

2.11

2.12

Communications with an OMRON PLC (FINS Communications Service) . 2-186

Using Automatic Reception with the MP3000 as a Slave . . . . . . . . . . . . . . . . . . . . . . . 2-186

Using the MSG-RCVE Function with the MP3000 as a Slave . . . . . . . . . . . . . . . . . . . . 2-195

Using I/O Message Communications with the MP3000 as the Master . . . . . . . . . . . . . 2-204

Using the MSG-SNDE Function with the MP3000 as the Master . . . . . . . . . . . . . . . . . 2-211

Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-221

Message Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-223

Communications with a KOYO PLC (MODBUS/TCP Protocol) . . . . . .2-250

Using Automatic Reception with the MP3000 as a Slave . . . . . . . . . . . . . . . . . . . . . . . 2-250

Using I/O Message Communications with the MP3000 as the Master . . . . . . . . . . . . . 2-257

Communications with a JTEKT PLC (TOYOPUC Protocol) . . . . . . . .2-262

Using Automatic Reception with the MP3000 as a Slave . . . . . . . . . . . . . . . . . . . . . . . 2-262

Using the MSG-RCVE Function with the MP3000 as a Slave . . . . . . . . . . . . . . . . . . . . 2-270

Using the MSG-SNDE Function with the MP3000 as the Master . . . . . . . . . . . . . . . . . 2-280

Message Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-291

Communications with a Windows PC (FA-Server) . . . . . . . . . . . . . . . .2-316

Using Automatic Reception with the MP3000 as a Slave . . . . . . . . . . . . . . . . . . . . . . . 2-316

Communications with a Windows PC (Visual Basic Application) . . . . .2-324

Using Automatic Reception with the MP3000 as a Slave . . . . . . . . . . . . . . . . . . . . . . . 2-324

2.13

2.14

2.15

2.16

Communications with a Windows PC (Visual C++ Application) . . . . . .2-340

Using Automatic Reception with the MP3000 as a Slave . . . . . . . . . . . . . . . . . . . . . . . 2-340

Communications Buffer Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-357

Using Message Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-359

Function Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-359

Using Function Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-360

Details on Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-378

Extended MEMOBUS Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-378

MEMOBUS Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-402

No-protocol Communications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-410

Index

Revision History

xiv

Outline of Communications

This chapter describes the communications of the MP3000 Con­troller.

1

1.1

1.2

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

System Configuration Examples . . . . . . . . . . . . . 1-3

Configuration with the MP3200 . . . . . . . . . . . . . . . . . . . . . . . 1-3

Configuration with the MP3300 . . . . . . . . . . . . . . . . . . . . . . . 1-4

1.1 Overview

1.1

Overview

The MP3000 Controller provides engineering communications (used to connect to the MPE720) and addi­tional support for an Ethernet connection to host devices.

The following table describes the communication features.

Function Features Description

Ethernet

The MP3000 Controller supports multiple
protocols to enable general-purpose Ether­net communications with PLCs and touch
panels from various manufacturers without
writing special applications.

• Protocols:
MODBUS/TCP, FINS, A-compatible 1E/
QnA-compatible 3E, TOYOPUC, Extended
MEMOBUS, and MEMOBUS

1-2

1.2 System Configuration Examples

Outline of Communications

MP

2200

MBU-02

PO

W

ER

DC

EXIOIF

MP2200

MBU-02

PO

W

ER

DC

EXIOIF

PC

Ethernet

Ethernet

Up to 42 stations, including I/O (Up to 32 stations can be Servos.)

Host PLC

I/O

Servomotor

Servomotor

Servomotor

MP3200

Reference-type SERVOPACK
with MECHATROLINK-III
Communications

I/O Module with
MECHATROLINK-III
Communications

MPE720 Integrated
Engineering Tool Version 7

24-VDC power

supply, AC power

supply, or status

monitoring device

24-VDC power

supply or

AC power supply

MECHATROLINK-III

EXIOIF

*

24-VDC power

supply or

AC power supply

24-VDC power

supply or

AC power supply

24-VDC power

supply or

AC power supply

Configuration with the MP3200

1.2

System Configuration Examples

Configuration with the MP3200

The following figure shows a typical system configuration.

* This manual primarily describes this area.

1-3

1.2 System Configuration Examples

PC

Host PLC

MP3300

MPE720 Integrated
Engineering Tool Version 7

24-VDC power

supply, AC power

supply, or status

monitoring device

24-VDC power

supply or

AC power supply

*

Up to 21 stations, including I/O (Up to 16 stations can be Servos.)

I/O

Servomotor

Servomotor

Servomotor

Reference-type SERVOPACK
with MECHATROLINK-III
Communications

MECHATROLINK-III

I/O Module with MECHATROLINK-III
Communications

HUB

Configuration with the MP3300

Configuration with the MP3300

* This manual primarily describes this area.

1-4

Ethernet Communications

This chapter describes the Ethernet communications of the
MP3000-series Controller.

2

2.1

2.2

2.3

2.4

2.5

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Ethernet Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Communications Specifications . . . . . . . . . . . . . . . . . . . . . . . 2-5

Detail Definition Setting Procedures . . . . . . . . . . 2-6

Displaying the 218IFD Detail Definition Dialog Box . . . . . . . . 2-6

218IFD Detail Definition Dialog Box Details . . . . . . . . . . . . . . 2-7

Communications Protocols . . . . . . . . . . . . . . . . 2-18

Communications with MP-series Controllers . . . 2-20

Using Automatic Reception with the MP3000 as a Slave . . . 2-20
Using the MSG-RCVE Function with

the MP3000 as a Slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30

Using I/O Message Communications with

the MP3000 as the Master . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42

Using the MSG-SNDE Function with

the MP3000 as the Master . . . . . . . . . . . . . . . . . . . . . . . . . . 2-51

Message Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59

Communications with a Touch Panel . . . . . . . . . 2-90

Using Automatic Reception with the MP3000 as a Slave . . . 2-90

2.6

Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) . . .2-98

Using Automatic Reception with the MP3000 as a Slave . . . 2-98
Using I/O Message Communications with

the MP3000 as the Master . . . . . . . . . . . . . . . . . . . . . . . . . 2-105

Message Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-111

2.7

Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) 2-139

Using I/O Message Communications with

the MP3000 as the Master . . . . . . . . . . . . . . . . . . . . . . . . . 2-139

Using the MSG-SNDE Function with

the MP3000 as the Master . . . . . . . . . . . . . . . . . . . . . . . . . 2-146

Message Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-157

2.8

2.9

2.10

Communications with an OMRON PLC (FINS Communications Service) . . 2-186

Using Automatic Reception with the MP3000 as a Slave . 2-186
Using the MSG-RCVE Function with

the MP3000 as a Slave . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-195

Using I/O Message Communications with

the MP3000 as the Master . . . . . . . . . . . . . . . . . . . . . . . . . 2-204

Using the MSG-SNDE Function with

the MP3000 as the Master . . . . . . . . . . . . . . . . . . . . . . . . . 2-211

Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-221

Message Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-223

Communications with a KOYO PLC (MODBUS/TCP Protocol) . . 2-250

Using Automatic Reception with the MP3000 as a Slave . 2-250
Using I/O Message Communications with

the MP3000 as the Master . . . . . . . . . . . . . . . . . . . . . . . . . 2-257

Communications with a JTEKT PLC (TOYOPUC Protocol) . 2-262

Using Automatic Reception with the MP3000 as a Slave . 2-262
Using the MSG-RCVE Function with

the MP3000 as a Slave . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-270

Using the MSG-SNDE Function with

the MP3000 as the Master . . . . . . . . . . . . . . . . . . . . . . . . . 2-280

Message Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-291

2.11 Communications with a Windows PC (FA-Server) . . 2-316

Using Automatic Reception with the MP3000 as a Slave . 2-316

2.12

2.13

2.14

Communications with a Windows PC (Visual Basic Application) . 2-324

Using Automatic Reception with the MP3000 as a Slave . 2-324

Communications with a Windows PC (Visual C++ Application) . .2-340

Using Automatic Reception with the MP3000 as a Slave . 2-340

Communications Buffer Channels . . . . . . . . . . 2-357

2.15

Using Message Functions . . . . . . . . . . . . . . . . 2-359

Function Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-359

Using Function Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-360

2.16

Details on Protocols . . . . . . . . . . . . . . . . . . . . . 2-378

Extended MEMOBUS Protocol . . . . . . . . . . . . . . . . . . . . . . 2-378

MEMOBUS Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-402

No-protocol Communications . . . . . . . . . . . . . . . . . . . . . . . 2-410

2.1 Overview

Important

Ethernet Communications

2.1

Overview

Ethernet Communications

Ethernet communications connects the MP3000-series Controller to Ethernet devices. The MP3000-series
Controller is equipped with one 100Base-TX Ethernet port that conforms to IEEE802.3u. It can be easily
connected to controllers manufactured by other companies, personal computers, or other types of comput­ers. By connecting a computer running the MPE720 Integrated Engineering Tool, you can perform engi­neering tasks on the MP3000-series Controller from the computer.

Ethernet communications can be used for message communications and engineering communications.

The MP3000-series Controller supports the following communications protocols.

Protocol Description Master/Slave

MEMOBUS Yaskawa’s standard MEMOBUS protocol. Master/Slave

Extended MEMOBUS Yaskawa’s extended MEMOBUS protocol. Master/Slave

A-compatible 1E frame A protocol for Mitsubishi PLCs. Master/Slave

QnA-compatible 3E
frame

FINS A protocol for OMRON PLCs. Master/Slave

MODBUS/TCP

TOYOPUC A protocol for JTEKT PLCs. Master/Slave

No-protocol

A protocol for Mitsubishi PLCs. Master/Slave

An Ethernet protocol proposed by Modicon and used in
industrial applications.

A protocol provided to implement general-purpose message
communications.

Master/Slave

Master/Slave

The Extended MEMOBUS protocol is used for all message communications between the CPU Function
Module and the 218IFD Function Module in the CPU Unit or the CPU Module of the MP3000-series
Machine Controllers.

MP3000-series Controller

CPU Function Module

MSG-SNDE and MSG-RCVE functions

Extended MEMOBUS Protocol

(MEMOBUS/No-protocol)

Extended MEMOBUS
(MEMOBUS/No-protocol)

218IFD

stack

This manual describes message communications using the MSG-SNDE and MSG-RCVE functions. If
you use the MSG-SND and MSG-RCV functions, substitute the corresponding information for the
MSG-SND and MSG-RCV functions. These functions are slightly different when used in ladder pro­grams. Refer to the following manual for information on using the MSG-SND and MSG-RCV func­tions in ladder programs.

MP2000-series Communication Module User’s Manual (Manual No.: SIEP C880700 04)

TCP UDP

Other supported protocols

SOCKET

IP, ARP, ICMP

CSMA/CD

Application protocol

2-4

Communications Specifications

Ethernet Communications

Communications Specifications

The following table lists the communications specifications of the MP3000-series Controller.

Item Specification Remarks

Abbreviation 218IFD −

Com­mon
Items

Ethernet
Commu­nications

Communications Interface 10Base-T or 100Base-TX −

Number of Communications Ports
(Connectors)

Communications Protocols TCP, UDP, IP, ARP, or ICMP −

Maximum Number of Communications
Connections

Maximum Number of Communications
Channels

Automatic Reception Supported.

Number of Automatic Reception
Connections

MEMOBUS

Extended MEMOBUS

MELSEC

Maximum
Size of Mes­sage Com­munications

Maximum
Size of I/O
Message
Communica­tions

Receive Buffer Mode Selection for
No-protocol Communic

Communications Platform Ethernet −

Controller Searches with Engineering Tool Supported. −

(A-compatible 1E)

MELSEC
(QnA-compatible 3E)

MODBUS/TCP

OMRON

TOYOPUC Write: 1,022 words −

No-protocol Write: 2,046 words −

MEMOBUS

Extended MEMOBUS

MELSEC
(A-compatible 1E)

MELSEC
(QnA-compatible 3E)

MODBUS/TCP

OMRON

Execution Conditions

Execution Status
Monitoring

ations

2 2-port hub

20 + 2 (I/O message communica­tions)

10 + 2 (I/O message communica­tions)

10 −

Write: 100 words
Read: 125 words

Write: 2,043 words
Read: 2,044 words

Write: 256 words
Read: 256 words

Write: 960 words
Read: 960 words

Write: 100 words
Read: 125 words

Write: 996 words
Read: 999 words

Write: 100 words
Read: 125 words

Write: 1,024 words
Read: 1,024 words

Write: 256 words
Read: 256 words

Write: 256 words
Read: 256 words

Write: 100 words
Read: 125 words

Write: 996 words
Read: 999 words

After the power is turned ON,
cyclic communications, or start/
stop control from ladder programs.

Supported.

Supported. −

−

−

Not supported for
no-protocol com­munications.

−

−

−

−

−

−

−

−

−

−

−

−

Currently under
development.

Currently under
develop

2.1 Overview

ment.

2-5

2.2 Detail Definition Setting Procedures



Displaying the 218IFD Detail Definition Dialog Box

2.2

Detail Definition Setting Procedures

The 218IFD Detail Definition Dialog Box is used to make detailed definitions for Ethernet communica­tions.

Displaying the 218IFD Detail Definition Dialog Box

Follow these steps to display the 218IFD Detail Definition Dialog Box.

1.

Open the Module Configuration Definition Tab Page.

2. Double-click the cell for the 218IFD.

The 218IFD Detail Definition Dialog Box will be displayed.

2-6

2.2 Detail Definition Setting Procedures

Ethernet Communications

Note




















13

12

11

14

218IFD Detail Definition Dialog Box Details

Items 1 and 2 display the configuration information for the 218IFD Function Module. This is the same
configuration information that appears in the Module Configuration Definition Tab Page.

 Circuit No.

The circuit number of the Ethernet port on the 218IFD is displayed here.

 Start - End Register Range for the I/O Registers

The I/O register range of the 218IFD Function Module is displayed here.

1. The module configuration information can also be changed in the Module Configuration Definition Tab
Page. If you do so, specify a circuit number that is not in use by other Ethernet Modules (218IF/218IFB).

2. If you use the MSG-SNDE or MSG-RCVE function, set the circuit number input parameter (CIR#)
to the circuit number that is displayed here.

218IFD Detail Definition Dialog Box Details

The 218IFD Detail Definition Dialog Box has two tab pages, Transmission Parameters and Status. Each
tab page is displayed by clicking the corresponding tab.

Transmission Parameters Tab Page

This tab page is used to set the parameters that are required to use Ethernet communications.

2-7

2.2 Detail Definition Setting Procedures

11

12

13

14

Note

11000000 10101000 00000001 00000001

Field 1: 0 to 255 excluding 127

Field 2: 0 to 255

Field 3: 0 to 255

Field 4: 1 to 254

Least significant bitMost significant bit

218IFD Detail Definition Dialog Box Details

 Display Items

The following table lists the items that are displayed on the Transmission Parameters Tab Page.

For the valid setting ranges and setting precautions, refer to the descriptions of the items on the following
pages.

Number Item Description












IP Address Sets the IP address of the local station.

Subnet Mask Sets the subnet mask for the IP address of the local station.

Gateway IP Address Sets the IP address of the gateway.

Module Name Definition Sets the name for the 218IFD.

Detail Definition Button Click to set details for the local station.

Connection Number (CNO) Displays the connection number.

Local Port Sets the local port number.

Node IP Address Sets the remote IP address.

Node Port Sets the port number for the remote station.

Connect Type Sets the transport layer protocol.

Protocol Type Sets the application layer protocol.

Code Sets the code type.

Detail

Node Name
(Remote Station Name)

Used to set automatic reception and the local station for the
FINS protocol.

Used to enter a comment for the connection.

 Display Item Details

This section provides details on the items that are displayed on the Transmission Parameters Tab Page.

Always save all settings to the flash memory after changing them.

 IP Address

Enter the IP address of the local station.
There are four 8-bit fields delimited by periods. Input a decimal number in each field.

Note: 1. Enter an IP address that is not in use by another node on the Ethernet.

2. IP addresses 192.168.1.1 to 192.168.1.254 are recommended as private addresses. Check with your net­work administrator for unused IP addresses.

 Subnet Mask

Enter the subnet mask for the IP address of the local station.
Fields 1 to 3 can be set to 0 to 255. Field 4 can be set to 1 to 254. When a subnet mask is not being used, enter

0 in fields 1 to 4.

2-8

2.2 Detail Definition Setting Procedures

Ethernet Communications

192. 168. 100. 200

Field 4: 1 to 254

Field 1: 0 to 255 excluding 127

Field 2: 0 to 255

Field 3: 0 to 255

Setting Example

Terms

218IFD Detail Definition Dialog Box Details

 Gateway IP Address

Enter the IP address of the gateway.
If a gateway is not being used, enter 0 in fields 1 to 4 for the gateway IP address.
The data input range for the gateway IP address depends on the field as shown below.

Note: Enter different addresses for the IP address and gateway IP address.

 Module Name Definition

Set the name for the 218IFD.
Enter a comment of up to 16 characters.

Subnet Mask

A subnet mask is a mask used to derive the network address of the subnet from the IP address. The
result of an AND operation of the IP address and the subnet mask produces the subnet address.
Check with your network administrator for unused subnet mask values.

Gateway IP Address

The gateway IP address identifies the gateway device (i.e., router) through which communications are
performed between multiple network segments. Check with your network administrator when setting a
gateway device.

 Detail Definition Button

The button displays the Detail Setting (Local Port TCP/IP Setting) Dialog Box to set the engineering port,
response time, number of retries (Count of Retry), and receive buffer.

Engineering Port

Enter the Ethernet port number (between 256 and 65535) for the 218IFD to use for engineering communica­tions with the MPE720. The default is 9999.

Note: 1. If this value is changed, also change the port set in the Engineering Port Box in the Detail Setting

Dialog Box of the Communications Port Setting Tab Page on the MPE720 communications platform.

2. Do not use the port number assigned to the local port number.

3. Do not set 9998 or 10000. These are used by the system.

2-9

2.2 Detail Definition Setting Procedures

218IFD Detail Definition Dialog Box Details

Response Time

Enter the time (between 0 and 255) to wait for a response after sending a command using the MSG-SNDE
function. If a response is not returned, causing a timeout, the transmission will be retried as many times as set
in the Count of Retry Box.

The Count of Retry Box is disabled if 0 is set for the response time.

Note: Enter 0 for the response time if 0 is set for the Count of Retry Box and MEMOBUS is selected in the Pro-

tocol Type Column in the Connection Parameter Area.

Count of Retry

Enter the number of retries (0 to 255) to be attempted if a timeout is detected after sending a command with
the MSG-SNDE function. An error is returned for the MSG-SNDE function if a response is not returned
after the set number of retries.

Note: If the TCP is the only protocol set for the connect type, it is not necessary to set the number of retries. Enter 0.

Receive Buffer Selection

This parameter selects the buffer type when no-protocol communications is selected in the Protocol Type
Column.

 Connection Number (CNO)

This column displays the connection numbers between 1 and 20.
With Ethernet communications, the connection number is used to identify remote stations.
The connection number corresponds to parameter 10 (Remote Connection Number) in the MSG-SNDE and

MSG-RCVE functions.

 Local Port

Enter the local port number (between 256 and 65535) for each connection.
Do not enter a port number that is used for another connection, an engineering port number, or a diagnostics
port number. If 0 is entered for the local port number, the data for that connection number will be cleared and
“-----” will be displayed in the Local Port Column.

Note: The port number that is set for the engineering port, as well as 9998 and 10000, cannot be used if the connect

type is UDP.

 Node IP Address

Enter the IP address of the remote station for each connection.
The data input range depends on the field of the remote IP address.

Field 1: 0 to 255 excluding 127
Field 2: 0 to 255
Field 3: 0 to 255
Field 4: 1 to 254

Enter 0 in all four fields to connect in Unpassive Open Mode.

2-10

 Node Port

Enter the port number (0 or 256 to 65535) of the remote station for the connection.

Note: The combination of the node IP address and node port must not be in use for any other connection.

 Connect Type

Select the transport layer protocol.

TCP: Communications is performed using TCP (Transmission Control Protocol).
UDP: Communications is performed using UDP (User Datagram Protocol).

2.2 Detail Definition Setting Procedures

Ethernet Communications

Note

11

218IFD Detail Definition Dialog Box Details

If an error occurs during message communications with UDP (connectionless protocol), the following
may occur.

• The LINK/ACT indicator on the Ethernet connector may light or flash, communications data may be
lost, and communications may stop.

If this occurs, implement the following countermeasures.

1. Use Ethernet cables that meet the following requirements.

100Base-TX category 5 or better straight or cross twisted-pair cable with RJ-45 connectors

2. Separate the Ethernet cables from power cables.

If the problem persists even after implementing the above countermeasures, implement the following
countermeasures.

1. Change to TCP (connection protocol).

2. If you continue to use UDP, add the following retry programming.
Retry programming: If processing does not end within a specific time after sending a command,

implement a timeout and execute the send execution command again.

Refer to the ladder program in the following section for a programming example.

2.4 Communications with MP-series Controllers - Using the MSG-SNDE Function with the MP3000 as the
Master

Protocol Type

Select the application layer protocol for each connection according to the protocol supported by the remote

station.
The following table lists the protocols.
Refer to the following section for details on the protocols.

2.1 Overview (page 2-4)

Protocol Description

MEMOBUS Yaskawa’s standard MEMOBUS protocol.

Extended MEMOBUS Yaskawa’s extended MEMOBUS protocol.

A-compatible 1E frame A protocol for Mitsubishi PLCs.

QnA-compatible 3E frame A protocol for Mitsubishi PLCs.

FINS A protocol for OMRON PLCs.

MODBUS/TCP

An Ethernet protocol proposed by Modicon and used in
industrial applications.

TOYOPUC A protocol for JTEKT PLCs.

No-protocol

A protocol provided to implement general-purpose message
communications.

2-11

2.2 Detail Definition Setting Procedures

Terms

12

218IFD Detail Definition Dialog Box Details

Connections

A connection is a series of operations to confirm communications and transfer data in one-to-one com­munications between a local station program and a remote station program.

Port Numbers

A port number is used to identify the target program in the remote station. There is a one-to-one corre­spondence between port numbers and communications programs. A port number is entered in the
header section of the data, together with the IP address and other information. The remote station trans­fers the data to the target program identified by the destination port number.

The port number, including the one for the local station, is used to identify the communications service
program at both the local and remote stations.

Unpassive Open Mode

If the remote station’s address is set to 000.000.000.000 and the remote station’s port number is set to
0, the connection is set in the Unpassive Open Mode.
In Unpassive Open Mode, the MP3000 connects to any station that accesses its connection number. If
multiple stations access this connection number, the connection will be established with the station to
which the connection request was sent first. If a connection request is sent from a station while a con­nection is established with another station in Unpassive Open Mode, the connection that was estab­lished first is disconnected and a connection will be established with the station for which the
connection request was sent later.

TCP and UDP

TCP is a connection protocol and UDP is a connectionless protocol.
A connection protocol ensures reliable communications because it performs various steps of communi­cations control, such as arrival checks, error detection and correction, sequence number checks, and

send data size control.
In contrast, a connectionless protocol does not provide the procedures that ensure the quality of com-

munications, and data transmissions are performed in only one direction. Connectionless protocols
thus provide high-speed communications, but less communications reliability.
The selection of TCP or UDP depends on the requirements for communications. Select TCP if reliabil­ity is important and select UDP if speed is important.

Code

Select the code of the data to be transmitted for each connection according to the code to set at the remote
station.

RTU: Specifies RTU Mode when the MEMOBUS protocol is being used.
ASCII: Specifies ASCII Mode.
BIN: Specifies Binary Mode.
The code that can be selected is restricted by the selection of the protocol type in the Protocol Type Box as

shown in the following table.

Protocol Type

RTU ASCII BIN

Code

MEMOBUS  ×
Extended MEMOBUS × 
A-compatible 1E frame × 
QnA-compatible 3E frame × 
FINS ××
MODBUS/TCP ××
TOYOPUC ××
No-protocol × 

: Can be selected.
× : Cannot be selected.

2-12

2.2 Detail Definition Setting Procedures

Ethernet Communications

13

218IFD Detail Definition Dialog Box Details

Detail

This button displays the Detail Setting Dialog Box to set the automatic reception settings. If the FINS
protocol is selected, set the local station for the FINS protocol.

Item Setting Range Description Default

Disable/Enable Enable or Disable

Sets whether to enable automatic
reception.

Sets the buffer channel for Ethernet
Communica­tions Buffer
Channel (Trans­mission Buffer
Channel)

Readout of
Input Relay

Readout of
Input Register

Readout/Write­in of Coil

Readout/Write­in of Hold Reg­ister

Readout/Write­in of Data Relay

Readout/Write­in of Data Reg­ister

Readout/Write­in of Output
Coil

Readout/Write­in of Output
Register

1 to 10

IW00000 to IW17FFF

IW00000 to IW17FFF

MW00000 to
MW1048576

MW00000 to
MW1048576

GW00000 to
GW2097151

GW00000 to
GW2097151

OW00000 to OW17FFF

OW00000 to OW17FFF

communications to use when auto-

matic reception is executed. Connec-

tions and channel numbers may be

used in any combination.

Note: Do not assign a number that is

already used for another connection.

Sets the first register for the input

relays that are used with automatic

reception.

Sets the first register for input registers

that are used with automatic reception.

Sets the first register for reading/writ-

ing coils that are used with automatic

reception.

Sets the first register for reading/writ-

ing hold registers that are used with

automatic reception.

Sets the first register for reading/writ-

ing data relays that are used with auto-

matic reception.

Sets the first register for reading/writ-

ing data registers that are used with

automatic reception.

Sets the first register for reading/writ-

ing output coils that are used with

automatic reception.

Sets the first register for reading/writ-

ing output registers that are used with

automatic reception.

Same as the connec-

Continued on next page.

Disable

tion number

IW00000

IW00000

MW00000

MW00000

GW00000

GW00000

OW00000

OW00000

2-13

2.2 Detail Definition Setting Procedures

14

218IFD Detail Definition Dialog Box Details

Item Setting Range Description Default

Write-in width
of Coil/Hold
Register, LO

Write-in width
of Coil/Hold
Register, HI

Write-in width
of Data Relay/
Register, LO

Write-in width
of Data Relay/
Register, HI

Write-in width
of Output Coil/
Register, LO

Write-in width
of Output Coil/
Register, HI

Automatic input
processing
delay time

MW00000 to
MW1048576

MW00000 to
MW1048576

GW00000 to
GW2097151

GW00000 to
GW2097151

OW00000 to OW17FFF

OW00000 to OW17FFF

0 to 100 (ms)

Continued from previous page.

Sets the low end of the range for writ­ing hold registers (coils) that are used
with automatic reception.

Sets the high end of the range for writ­ing hold registers (coils) that are used
with automatic reception.

Sets the low end of the range for writ­ing data registers (data relays) that are
used with automatic reception.

Sets the high end of the range for writ­ing data registers (data relays) that are
used with automatic reception.

Sets the low end of the range for writ­ing output registers (output coils) that
are used with automatic reception.

Sets the high end of the range for writ­ing output registers (output coils) that
are used with automatic reception.

Sets the delay time for sending
responses to adjust the influence on the
low-speed scan during automatic
reception processing.

MW00000

MW1048575

GW00000

GW2097151

OW00000

OW17FFF

0

Node Name (Remote Station Name)

Used to enter a comment for the connection.
Enter a comment of up to 32 characters.

2-14

2.2 Detail Definition Setting Procedures

Ethernet Communications

  











11

12

13

Note

218IFD Detail Definition Dialog Box Details

Status Tab Page

The Status Tab Page displays the communications status and detail definition settings for the 218IFD. The
settings cannot be changed.

1. If the Status Tab is clicked without saving the 218IFD detail definition data, a confirmation mes-

sage to save the data or an error message (if inconsistencies exist in the data) will appear. If a confir­mation message to save the data is displayed, click the Yes Button to save the detail definition data
and display the Status Tab Page. If an error message is displayed, click the OK Button, enter the
correct parameters, and save the data. Then, click the Status Tab.

2. The data on the Status Tab Page is displayed only in online mode. Nothing is displayed in offline
mode.

 Display Item Details

This section provides details on the items that are displayed on the Status Tab Page.

 Station IP Address, Equipment Name, and Baud Rate (Transmission Speed)

The local station’s IP address and equipment name that are set on the Transmission Parameters Tab Page are
displayed here.

 Subnet Mask, Gateway IP Address, and Engineering Port

The subnet mask, gateway (router) IP address, and engineering port that are set on the Transmission Parame-

ters Tab Page are displayed here.

 CNO

The connection numbers from 1 to 20 are displayed.

 Trans Status (Transmission Status)

The status of each connection is displayed.

Status Description

IDLE Standby mode for executing message functions.

WA I T

CONNECT Ready to send/receive data to the remote station.

− Unused connection.

Waiting for the TCP connection to be established with the remote station (only
if the connection type is set to TCP).

 Error Status

Details on the error are displayed if an error has occurred in the communications status.

2-15

2.2 Detail Definition Setting Procedures

218IFD Detail Definition Dialog Box Details

Status Display Description Remarks

No error Normal −

Socket Creation Error System error A socket could not be created.

Local Port Number Error

Changing Socket Attribute
Error

M-SND Connection Error

M-RCV Connection Error

System Error System error

TCP Data Send Error

UDP Data Send Error

TCP Data Receive Error

UDP Data Receive Error

Changing Socket Option
Error

Data Conversion Error Error in converting data Error in protocol conversion.

Note: The last error in the error status will be retained until the power is turned OFF, even if communications

recover. To clear the error, cycle the power to the Controller.

 Send Count

The number of data packets that were sent to the remote station is displayed.

 Receive Count

The number of data packets that were received from the remote station is displayed.

 Error Count

The number of times an error has occurred for each connection is displayed.

Setting error in local station port
number

(The same address is bound during
disconnection of the TCP connec­tion.)

System error (for TCP)

Connection error
(The connection was rejected by
the remote station when establish­ing a connection with an unpassive

open for TCP.)

Connection error
(connection passive open for TCP)

Data sending error
(The remote station does not exist
or has not started when using
TCP.)

Data sending error (for UDP)

Data reception error
(The MP3000 received a request to

disconnect from the remote station
for TCP.)

Data reception error (for UDP)

System error

Binding error (port number duplication)

When a MSG function was aborted, a
binding error occurred during discon­nection.
This error occurs if the Execute Bit is
turned ON within 1 minute after com­pletion of abortion processing.

A command was sent to the same
remote station for another function
before the completion of connection
processing.

An error occurred while setting the
socket attribute.

The command was reset because the
remote station rejected the connection
that was attempted for the MSG-SNDE
function.

Connection failed even after retrying 1
minute (default) after the cable was dis­connected.

MSG-RCVE function connection
acceptance error

Socket polling error (using SELECT)
when receiving data.

A response transmission error occurred
for the MSG-RCVE function. The same
error occurred for the MSG-SNDE
function.

This error occurs when the target
remote station for sending the data does
not exist, or has rebooted (only with a
TCP connection).

The data send request was sent to a
socket that does not exist.

This error occurs when the connection
is disconnected by the remote station.
The error occurs even if close process­ing is performed normally.

A data reception instruction was exe­cuted for a socket that does not exist.

An error occurred when changing the
socket option.

2-16

2.2 Detail Definition Setting Procedures

Ethernet Communications

11

12

13

218IFD Detail Definition Dialog Box Details

 Response Time

The time (ms) that was required to receive a response for a command that was sent using the MSG-SNDE
function is displayed.

 Connection Type

The connect type (TCP or UDP) that is set in the connection parameters on the Transmission Parameters Tab
Page is displayed here.

Protocol Type

The protocol type that is set in the connection parameters on the Transmission Parameters Tab Page is dis­played here.

Code

The code (ASCII, binary, or RTU) that is set in the connection parameters on the Transmission Parameters
Tab Page is displayed here.

Node Name (Remote Station Name)

The remote node name that is set in the connection parameters on the Transmission Parameters Tab Page is
displayed here.

2-17

2.3 Communications Protocols

2.3

Communications Protocols

The following table lists the communications protocols according to the remote device and purpose.

Communications Interface Function

used by

Master Slave

the

MP3000

Automatic

Other
MP-series
Controller

MP3000

reception

MSG­RCVE
function

I/O mes­sage com­munications

MSG­SNDE

MP3000

Other
MP-series
Controller

function

Touch Panel MP3000

Mitsubishi
PLCs, Q/A

MP3000

Series

Mitsubishi

MP3000

PLCs, Q/A
Series

Automatic
reception

Automatic
reception

I/O mes­sage com­munications

I/O mes­sage com­munications

MSG­SNDE

MP3000

Mitsubishi
PLCs, Q/
QnA Series

function

Automatic

OMRON
PLCs

MP3000

reception

MSG­RCVE
function

I/O mes­sage com-

MP3000

OMRON
PLCs

munications

MSG­SNDE
function

KOYO PLCs MP3000

Automatic
reception

I/O mes-

MP3000 KOYO PLCs

sage com­munications

Reference

Using Automatic Reception with the
MP3000 as a Slave (page 2-20)

Using the MSG-RCVE Function with the
MP3000 as a Slave (page 2-30)

Using I/O Message Communications with
the MP3000 as the Master (page 2-42)

Using the MSG-SNDE Function with the
MP3000 as the Master (page 2-51)

Using Automatic Reception with the
MP3000 as a Slave (page 2-90)

Using Automatic Reception with the
MP3000 as a Slave (page 2-98)

Using I/O Message Communications with
the MP3000 as the Master (page 2-105)

Using I/O Message Communications with
the MP3000 as the Master (page 2-139)

Using the MSG-SNDE Function with the
MP3000 as the Master (page 2-146)

Using Automatic Reception with the
MP3000 as a Slave (page 2-186)

Using the MSG-RCVE Function with the
MP3000 as a Slave (page 2-195)

Using I/O Message Communications with
the MP3000 as the Master (page 2-204)

Using the MSG-SNDE Function with the
MP3000 as the Master (page 2-211)

Using Automatic Reception with the
MP3000 as a Slave (page 2-250)

Using I/O Message Communications with
the MP3000 as the Master (page 2-257)

Continued on next page.

Remote

Device

MP Series

Touch Panel

Mitsubishi
PLCs, Q/A
Series

Mitsubishi
PLCs, Q/
QnA Series

OMRON
PLCs

KOYO PLCs

Communi-

cations

Protocol

Extended
MEMOBUS

Extended
MEMOBUS

A-compati­ble 1E frame

QnA-com­patible 3E
frame

FINS

MODBUS/
TCP

2-18

Ethernet Communications

Remote

Device

Communi-

cations

Protocol

JTEKT PLCs TOYOPUC

Windows PC,
FA-Server

Windows PC,
Visual Basic
Application

Windows PC,
Vis u al C++
Application

Extended
MEMOBUS

Extended
MEMOBUS

Extended
MEMOBUS

Communications Interface Function

used by

Master Slave

the

MP3000

Automatic
reception

JTEKT PLCs MP3000

MSG­RCVE
function

MSG-

MP3000 JTEKT PLCs

SNDE
function

Windows
PC, FA­Server

MP3000

Automatic
reception

Windows
PC, Visual
Basic Appli-

MP3000

Automatic
reception

cation

Windows
PC, Visual
C++ Appli-

MP3000

Automatic
reception

cation

2.3 Communications Protocols

Continued from previous page.

Reference

Using Automatic Reception with the
MP3000 as a Slave (page 2-262)

Using the MSG-RCVE Function with the
MP3000 as a Slave (page 2-270)

Using the MSG-SNDE Function with the
MP3000 as the Master (page 2-280)

Using Automatic Reception with the
MP3000 as a Slave (page 2-316)

Using Automatic Reception with the
MP3000 as a Slave (page 2-324)

Using Automatic Reception with the
MP3000 as a Slave (page 2-340)

2-19

2.4 Communications with MP-series Controllers

EthernetEthernet

MP2300MP3000

218IFD

DC24V

DC 0V

MP2300

YASKAWA

TEST

RDY

ALM

TX

RUN

ERR

BAT

MON

CNFG

INT

SUP

STOP

SW1

OFF ON

BATTERY

CPU I/O

218IF-01

ERR

COL

RX

RUN

STRX

TX

INIT

TEST

ONOFF

PORT

10Base-T

MP3000

(local station)

Slave

Master

Communications Protocol
Connection Type

Data Code

Binary or ASCII

Automatic reception

(no ladder programming)

MSG-SND function
(ladder application)

218IF-01

Optional

Module

Extended MEMOBUS protocol

TCP or UDP

Extended MEMOBUS protocol

MP2300

(remote station)

Using Automatic Reception with the MP3000 as a Slave

2.4

Communications with MP-series Controllers

When using Ethernet communications between the MP3000 and other MP-series Controllers, use the
Extended MEMOBUS protocol as the communications protocol. The Extended MEMOBUS protocol
allows the master to read and write the slave registers.
This section describes communications when the MP3000 acts as a slave and as the master.
When the MP3000 acts as a slave, communications can take place using automatic reception or using the
MSG-RCVE function.
When the MP3000 acts as the master, communications can take place using I/O message communications
or the MSG-SNDE function.

Using Automatic Reception with the MP3000 as a Slave

This section describes how to communicate with the MP2300 by using automatic reception.

2-20

2.4 Communications with MP-series Controllers

Ethernet Communications

TCP

DC24V

DC 0V

MP2300

YASKAWA

TEST

RDY

ALM

TX

RUN

ERR

BAT

MON

CNFG

INT

SUP

STOP

SW1

OFF ON

BATTERY

CPU I/O

218IF-01

ERR

COL

RX

RUN

STRX

TX

INIT

TEST

ONOFF

PORT

10Base-T

MW00000

Ethernet

MW00001

MW00099

MW00000

MW00001

MW00099

MW00098 MW00098

MP3000

(local station)

MP2300

(remote station)

IP address: 192.168.001.001

Slave

Communications Protocol
Connection Type

Data Code

Port number: 10001

Local Station

Hold registers (M registers)

Written.

Hold registers (M registers)

Data size:

100 words

Data size:

100 words

Remote Station

Port number: 10001

Extended MEMOBUS protocol

Master

IP address: 192.168.001.002

Binary

Using Automatic Reception with the MP3000 as a Slave

Setting Example

The following figure illustrates how the contents of the MW00000 to MW00099 hold registers in the
MP2300 master are written to the MW00000 to MW00099 hold registers in the MP3000 slave.

2-21

2.4 Communications with MP-series Controllers

Note

cd e

Using Automatic Reception with the MP3000 as a Slave

MP3000 Setup

Use the following procedure to set up the MP3000.

If the communications parameters (IP address and subnet mask) have already been set, skip to step 3.

1.

Double-click the cell for 218IFD in the Module Configuration Definition Tab Page.

The 218IFD Detail Definition Dialog Box will be displayed.

2. Set the communications parameters.

In the IP Address Boxes, enter the following address: 192.168.001.001.
In the Subnet Mask Boxes, enter the following mask: 255.255.255.000.
In the Gateway IP Address Boxes, enter the following address: 000.000.000.000.

3.

Click the

ters

Easy Setting

Area.

Button in the

Message Communications

Area in the

Connection Parame-

2-22

The Message Communications Easy Setting Dialog Box will be displayed.

Ethernet Communications

4. Set the connection parameters.

    





2.4 Communications with MP-series Controllers

Using Automatic Reception with the MP3000 as a Slave

Select 1 in the Connect No. Box.
Enter “10001” in the Port No. Box for the MP-series Controller.
Select Extended MEMOBUS in the Communications Protocol Type Box, and then click the

Default Button.

Select TCP in the Connect Type Box.
Select BIN in the Code Box.
Enter the following address in the Node Port IP Address Boxes for the other device:

192.168.001.002.

Enter “10001” in the Port No. Box for the other device.

5. Click the OK Button.

6. Click the Yes Button in the Transmission Parameters Confirmation Dialog Box.

Note: If parameters have already been set for the same connection number and you click the Yes Button in the

Transfer Parameters Confirmation Dialog Box, the settings will be overwritten by the parameters that are set
in the Message Communications Easy Setting Dialog Box.

2-23

2.4 Communications with MP-series Controllers

Using Automatic Reception with the MP3000 as a Slave

7. Check the settings and double-click the Setting Button in the Detail Column.

8. Select the Enable Option on the Automatically Reception Tab Page and then click the OK Button.

2-24

Note: 1. Refer to the following section for details on automatic reception.

2.2 Detail Definition Setting Procedures (page 2-6)

2. Disable automatic reception for any connection for which message functions (MSG-SNDE and MSG­RCVE) are used. If message functions are used while automatic reception is enabled, the communications
will not function properly.

9. Save the data to flash memory.

Note: Changes made to the communications or connection parameters will become effective only after the changes

have been saved to flash memory and the power supply has been cycled.

This concludes the settings for using the MP3000 as a slave.

2.4 Communications with MP-series Controllers

Ethernet Communications

Note

  

Using Automatic Reception with the MP3000 as a Slave

 Setting Up the Other Device (MP2300) to Connect

Use the following procedure to set up the MP2300.

If the communications parameters (IP address and subnet mask) have already been set, skip to step 3.

1.

Double-click the cell for
Page.

218IF

in the

Module Details

Area of the Module Configuration Definition Tab

The 218IF Detail Definition Dialog Box will be displayed.

2. Set the communications parameters.

In the IP Address Boxes, enter the following address: 192.168.001.002.
Select Edit - Local Station: TCP/IP Setting in the Engineering Manager Window.
In the Subnet Mask Boxes, enter the following mask: 255.255.255.000.
In the Gateway IP Address Boxes, enter the following address: 000.000.000.000.

2-25

2.4 Communications with MP-series Controllers

   

Using Automatic Reception with the MP3000 as a Slave

3. Set the connection parameters.

Enter “10001” in the Local Port Box.
Enter the following address in the Node IP Address Boxes: 192.168.001.001.
Enter “10001” in the Node Port Box.
Select TCP in the Connect Type Box.
Select Extended MEMOBUS in the Protocol Type Box.
Select BIN in the Code Box.

Note: Changes made to the communications or connection parameters will become effective only after the changes

have been saved to flash memory and the power supply has been cycled.

2-26

Using Automatic Reception with the MP3000 as a Slave

Ethernet Communications

4. Create a ladder program for the MSG-SND function.

A ladder program example is shown below.

2.4 Communications with MP-series Controllers

2-27

2.4 Communications with MP-series Controllers

Using Automatic Reception with the MP3000 as a Slave

2-28

2.4 Communications with MP-series Controllers

Ethernet Communications



Using Automatic Reception with the MP3000 as a Slave

5. Save the data to flash memory.

This concludes the setup.

 Starting Communications

1. Turn ON the power to the MP3000 to start receiving messages.

The system will automatically start the message reception operation. No further operation is required.

2. Turn ON the Execute Bit (e.g., DB000200) for the MSG-SND function in the MP2300 to start

sending messages.

The ladder program example is designed to send a message every second after five seconds have elapsed
from when the low-speed scan (or high-speed scan) starts.
To change the message transmission interval, change the timer value .

2-29

2.4 Communications with MP-series Controllers

MP2300MP3000

218IFD

EthernetEthernet

DC24V

DC 0V

MP2300

YASKAWA

TEST

RDY

ALM

TX

RUN

ERR

BAT

MON

CNFG

INT

SUP

STOP

SW1

OFF ON

BATTERY

CPU I/O

218IF-01

ERR

COL

RX

RUN

STRX

TX

INIT

TEST

ONOFF

PORT

10Base-T

MP3000

(local station)

Slave

Master

Communications Protocol
Connection Type
Data Code Binary or ASCII

MSG-RCVE function

(ladder application)

MSG-SND function
(ladder application)

218IF-01

Optional

Module

Extended MEMOBUS protocol

TCP or UDP

MEMOBUS protocol

MP2300

(remote station)

Using the MSG-RCVE Function with the MP3000 as a Slave

Using the MSG-RCVE Function with the MP3000 as a Slave

You can use the MSG-RCVE function together with automatic reception by maintaining a separate con­nection.

This section describes how to communicate with an MP2300-series Controller by using the MSG-RCVE
function.

2-30

2.4 Communications with MP-series Controllers

Ethernet Communications

MW00100

MW00101

MW00199

MW00100

MW00101

MW00199

MW00198 MW00198

DC24V

DC 0V

MP2300

YASKAWA

TEST

RDY

ALM

TX

RUN

ERR

BAT

MON

CNFG

INT

SUP

STOP

SW1

OFF ON

BATTERY

CPU I/O

218IF-01

ERR

COL

RX

RUN

STRX

TX

INIT

TEST

ONOFF

PORT

10Base-T

Ethernet

TCP

Binary

MP3000

(local station)

IP address: 192.168.001.001

IP address: 192.168.001.002

Slave

Master

Communications Protocol Extended MEMOBUS protocol
Connection Type
Data Code

Port number: 10002 Port number: 10002

Local Station

Hold registers (M registers)

Data size:

100 words

Write.

Hold registers (M registers)

Data size:

100 words

Remote Station

MP2300

(remote station)

Using the MSG-RCVE Function with the MP3000 as a Slave

Setting Example

The following figure illustrates how the contents of the MW00100 to MW00199 hold registers in the
MP2300 master are written to the MW00100 to MW00199 hold registers in the MP3000 slave.

2-31

2.4 Communications with MP-series Controllers

Note

cd e

Using the MSG-RCVE Function with the MP3000 as a Slave

MP3000 Setup

Use the following procedure to set up the MP3000.

If the communications parameters (IP address and subnet mask) have already been set, skip to step 3.

1.

Double-click the cell for 218IFD in the Module Configuration Definition Tab Page.

The 218IFD Detail Definition Dialog Box will be displayed.

2. Set the communications parameters.

In the IP Address Boxes, enter the following address: 192.168.001.001.
In the Subnet Mask Boxes, enter the following mask: 255.255.255.000.
In the Gateway IP Address Boxes, enter the following address: 000.000.000.000.

3.

Click the

ters

Easy Setting

Area.

Button in the

Message Communications

Area in the

Connection Parame-

2-32

The Message Communications Easy Setting Dialog Box will be displayed.

Ethernet Communications

4. Set the connection parameters.

    

 

2.4 Communications with MP-series Controllers

Using the MSG-RCVE Function with the MP3000 as a Slave

Select 2 in the Connect No. Box.
Enter “10002” in the Port No. Box for the MP-series Controller.
Select Extended MEMOBUS in the Communications Protocol Type Box, and then click the

Default Button.

Select TCP in the Connect Type Box.
Select BIN in the Code Box.
Enter the following address in the Node Port IP Address Boxes for the other device:

192.168.001.002.

Enter “10002” in the Port No. Box for the other device.

Note: Disable automatic reception for any connection for which message functions (MSG-SNDE and MSG-RCVE)

are used. If message functions are used while automatic reception is enabled, the communications will not
function properly.

5. Click the OK Button.

6. Click the Yes Button in the Transmission Parameters Confirmation Dialog Box.

Note: If parameters have already been set for the same connection number and you click the Ye s Button in the

Transfer Parameters Confirmation Dialog Box, the settings will be overwritten by the parameters that are set
in the Message Communications Easy Setting Dialog Box.

2-33

2.4 Communications with MP-series Controllers

Using the MSG-RCVE Function with the MP3000 as a Slave

7. Check the settings and double-click the Setting Button in the Detail Column.

8. Select the Disable Option on the Automatically Reception Tab Page and then click the OK But-

ton.

2-34

Note: Changes made to the communications or connection parameters will become effective only after the changes

have been saved to flash memory and the power supply has been cycled.

Using the MSG-RCVE Function with the MP3000 as a Slave

Ethernet Communications

9. Create a ladder program for the MSG-RCVE function.

A ladder program example is shown below.

2.4 Communications with MP-series Controllers

2-35

2.4 Communications with MP-series Controllers

Using the MSG-RCVE Function with the MP3000 as a Slave

2-36

10. Save the data to flash memory.

This concludes the settings for using the MP3000 as a slave.

2.4 Communications with MP-series Controllers

Ethernet Communications

Note



 

Using the MSG-RCVE Function with the MP3000 as a Slave

 Setting Up the Other Device (MP2300) to Connect

Use the following procedure to set up the MP2300.

If the communications parameters (IP address and subnet mask) have already been set, skip to step 3.

1.

Double-click the cell for
Page.

218IF

in the

Module Details

Area of the Module Configuration Definition Tab

The 218IF Detail Definition Dialog Box will be displayed.

2. Set the communications parameters.

In the IP Address Boxes, enter the following address: 192.168.001.002.
Select Edit − Local Station: TCP/IP Setting in the Engineering Manager Window.
In the Subnet Mask Boxes, enter the following mask: 255.255.255.000.
In the Gateway IP Address Boxes, enter the following address: 000.000.000.000.

2-37

2.4 Communications with MP-series Controllers

     

Using the MSG-RCVE Function with the MP3000 as a Slave

3. Set the connection parameters.

Enter “10002” in the Local Port Box.
Enter the following address in the Node IP Address Boxes: 192.168.001.001.
Enter “10002” in the Node Port Box.
Select TCP in the Connect Type Box.
Select Extended MEMOBUS in the Protocol Type Box.
Select BIN in the Code Box.

Note: Changes made to the communications or connection parameters will become effective only after the changes

have been saved to flash memory and the power supply has been cycled.

2-38

Using the MSG-RCVE Function with the MP3000 as a Slave

Ethernet Communications

4. Create a ladder program for the MSG-SND function.

A ladder program example is shown below.

2.4 Communications with MP-series Controllers

2-39

2.4 Communications with MP-series Controllers

Using the MSG-RCVE Function with the MP3000 as a Slave

2-40

5. Save the data to flash memory.

This concludes the setup.

2.4 Communications with MP-series Controllers

Ethernet Communications



Using the MSG-RCVE Function with the MP3000 as a Slave

 Starting Communications

1. Turn ON the power to the MP3000 to start receiving messages.

In the ladder program example, message reception starts immediately after the system starts. No further
operation is required.

2. Turn ON the Execute Bit (e.g., DB000200) for the MSG-SND function in the MP2300 to start

sending messages.

The ladder program example is designed to send a message every second after five seconds have elapsed
from when the low-speed scan (or high-speed scan) starts.

To change the message transmission interval, change the timer value .

2-41

2.4 Communications with MP-series Controllers

MP2300MP3000

218IFD

EthernetEthernet

DC24V

DC 0V

MP2300

YASKAWA

TEST

RDY

ALM

TX

RUN

ERR

BAT

MON

CNFG

INT

SUP

STOP

SW1

OFF ON

BATTERY

CPU I/O

218IF-01

ERR

COL

RX

RUN

STRX

TX

INIT

TEST

ONOFF

PORT

10Base-T

MP3000

(local station)

Master

Communications Protocol
Connect Type
Data Code

TCP or UDP
Binary or ASCII

I/O message communications

(no ladder programming)

218IF-01

Optional

Module

MSG-RCV function
(ladder application)

Extended MEMOBUS protocol

Extended MEMOBUS protocol

Slave

MP2300

(remote station)

Using I/O Message Communications with the MP3000 as the Master

Using I/O Message Communications with the MP3000 as the
Master

This section describes how to communicate with an MP2300-series Controller by using I/O message com­munications.

Note: 1. I/O message communications use 1-to-1 communications.

2. When using the Extended MEMOBUS protocol to communicate with an MP-series Controller, you can only
read and write hold registers.

3. When communicating with multiple remote devices or when you need to perform any operations other than
reading or writing to hold registers, use the Send Message function (MSG-SNDE).

2-42

2.4 Communications with MP-series Controllers

Ethernet Communications

Using I/O Message Communications with the MP3000 as the Master

Setting Example

The following figure illustrates how the contents of the MW00200 to MW00299 hold registers in the
MP2300 slave are read to the IW0000 to IW0063 input registers in the MP3000 master and how the con­tents of the OW0064 to OW00C7 output registers in the MP3000 master are written to the MW00300 to
MW00399 hold registers in the MP2000 slave.

MP3000

(local station)

IP address: 192.168.001.001

IP address: 192.168.001.002

MP2300

(remote station)

Master

Data size:

100 words

c

Data size:

100 words

d

Port number: 10005

c

Port number: 10006

d

Local Station

Input registers (I registers)

IW0000

IW0063

Output registers (O registers)

OW0064 MW00300

Communications Protocol
Connect Type

Data Code

Extended MEMOBUS protocol

TCP

Binary

Read.

Written.

YASKAWA

218IF-01

ERR

RUN

RUN

RDY

COL

STRX

ALM

ERR

TX

BAT

RX

TX

STOP

INIT

SUP

TEST

INT

CNFG

ONOFF

MON

SW1

TEST

PORT

OFF ON

CPU I/O

10Base-T

MP2300

BATTERY

DC24V

DC 0V

EthernetEthernet

Port number: 10005

c

Port number: 10006

d

Remote Station

Hold registers (M registers)

MW00200

MW00299

Slave

Data size:

100 words

Data size:

100 words

c

d

OW00C7

MW00399

2-43

2.4 Communications with MP-series Controllers

Note

cd e

Using I/O Message Communications with the MP3000 as the Master

 MP3000 Setup

Use the following procedure to set up the MP3000.

If the communications parameters (IP address and subnet mask) have already been set, skip to step 3.

1.

Double-click the cell for 218IFD in the Module Configuration Definition Tab Page.

The 218IFD Detail Definition Dialog Box will be displayed.

2. Set the communications parameters.

In the IP Address Boxes, enter the following address: 192.168.001.001.
In the Subnet Mask Boxes, enter the following mask: 255.255.255.000.
In the Gateway IP Address Boxes, enter the following address: 000.000.000.000.

3. Select the Enable Option in the I/O Message Communications Area of the Connection Param-

eter settings.

2-44

2.4 Communications with MP-series Controllers

Ethernet Communications

   

 



  

11

12

13

14

Using I/O Message Communications with the MP3000 as the Master

4. Click the Easy setting Button.

The Message Communications Easy Setting Dialog Box will be displayed.

5. Set the connection parameters.

Select



Extended MEMOBUS

Button.

Note: If you select the Extended MEMOBUS communications protocol, you will be able to read and write

only hold registers (MW).

in the

Communications Protocol Type

Box, and then click the

Enter “10005” and “10006” in the Port No. Boxes for the MP-series Controller.
Select TCP in the Connect Type Box.
Select BIN in the Code Box.
Enter the following address in the Node Port IP Address Boxes for the other device:

192.168.001.002.

Enter “10005” and “10006” in the Port No. Boxes for the other devices.

Note: In I/O message communications, a message is transmitted from each port for which a register read/write

is initiated. Therefore, for this example, the connected remote device must support a message reception
function to receive two messages.

Enter “IW0000” in the Input Reg Box as the read data destination.
Enter “100” in the Read Size Box as the size of data to read.
Enter “OW0064” in the Output Reg Box as the write data destination.
Enter “100” in the Write Size Box as the size of data to write.

Default

2-45

2.4 Communications with MP-series Controllers

11

12

13

Using I/O Message Communications with the MP3000 as the Master

Select Low in the Data update timing Box as the timing to update input and output data between the

CPU Function Module and 218IFD.

Note: The data update timing is the timing at which the CPU Function Module and 218IFD exchange data.

Communications with the remote device are performed asynchronously. The data update timing there­fore does not necessarily mean that the messages are sent to the remote device.

Enter “MW00200” in the Read Reg Box as the register type and first address to read from on the

remote device.

Enter “MW00300” in the Write Reg Box as the register type and first address to write to on the remote

device.

6. Click the OK Button.

7. Click the Yes Button in the Transmission Parameters Confirmation Dialog Box.

Note: If parameters have already been set for the same connection number and you click the Ye s Button in the

Transfer Parameters Confirmation Dialog Box, the settings will be overwritten by the parameters that are set
in the Message Communications Easy Setting Dialog Box.

8. Check the settings.

9. Save the data to flash memory.

Note: Changes made to the communications or connection parameters will become effective only after the changes

have been saved to flash memory and the power supply has been cycled.

This concludes the settings for using the MP3000 as the master.

2-46

2.4 Communications with MP-series Controllers

Ethernet Communications

Note



 

Using I/O Message Communications with the MP3000 as the Master

 Setting Up the Other Device (MP2300) to Connect

Use the following procedure to set up the MP2300.

If the communications parameters (IP address and subnet mask) have already been set, skip to step 3.

1.

Double-click the cell for
Page.

218IF

in the

Module Details

Area of the Module Configuration Definition Tab

The 218IF Detail Definition Dialog Box will be displayed.

2. Set the communications parameters.

In the IP Address Boxes, enter the following address: 192.168.001.002.
Select Edit − Local Station: TCP/IP Setting in the Engineering Manager Window.
In the Subnet Mask Boxes, enter the following mask: 255.255.255.000.
In the Gateway IP Address Boxes, enter the following address: 000.000.000.000.

2-47

2.4 Communications with MP-series Controllers

     

Using I/O Message Communications with the MP3000 as the Master

3. Set the connection parameters.

Enter “10005” and “10006” in the Local Port Boxes.
Enter the following address in the Node IP Address Boxes: 192.168.001.001.
Enter “10005” and “10006” in the Node Port Boxes.
Select TCP in the Connect Type Box.
Select Extended MEMOBUS in the Protocol Type Box.
Select BIN in the Code Box.

Note: Changes made to the communications or connection parameters will become effective only after the changes

have been saved to flash memory and the power supply has been cycled.

2-48

2.4 Communications with MP-series Controllers

Ethernet Communications

X.01

[MSG-RCV]

X.02

[MSG-RCV]

MP3000

I/O message

communications

Read.

For

receiving

read request

For receiving
write request

Written.

Remote device (MP2300)

Using I/O Message Communications with the MP3000 as the Master

4. Create a ladder program for the MSG-RCV function.

A ladder program example is shown below.
This ladder program example is for receiving the read request. Ladder programming for receiving the write

request is required separately.

Set DW0002 to 6 to
receive the write
request.

2-49

2.4 Communications with MP-series Controllers

Set DW0002 to 6 to
receive the write
request.

Set Ch-No to 6 to
receive the write
request.

Using I/O Message Communications with the MP3000 as the Master

2-50

5. Save the data to flash memory.

This concludes the setup.

 Starting Communications

1. Turn ON the power to the MP2300 to start receiving messages.

In the ladder program example, message reception starts immediately after the system starts. No further
operation is required.

2. Turn ON the power to the MP3000 to send the messages.

The system will automatically start the message transmission operation. No further operation is required.

2.4 Communications with MP-series Controllers

Ethernet Communications

MP2300MP3000

218IFD

EthernetEthernet

DC24V

DC 0V

MP2300

YASKAWA

TEST

RDY

ALM

TX

RUN

ERR

BAT

MON

CNFG

INT

SUP

STOP

SW1

OFF ON

BATTERY

CPU I/O

218IF-01

ERR

COL

RX

RUN

STRX

TX

INIT

TEST

ONOFF

PORT

10Base-T

MP3000

(local station)

MP2300

(remote station)

Master

Slave

Communications Protocol

Extended MEMOBUS protocol

Connect Type

TCP or UDP

Data Code Binary or ASCII

MSG-SNDE function

(ladder application)

MSG-RCV function
(ladder application)

218IF-01

Optional

Module

Extended MEMOBUS protocol

Using the MSG-SNDE Function with the MP3000 as the Master

Using the MSG-SNDE Function with the MP3000 as the Master

In I/O message communications, operations can be performed only on hold registers (M registers). No
other register types are supported. Additionally, this protocol supports communications with only one
slave.

To communicate with two or more slaves, you must use the MSG-SNDE function. You can use the MSG­SNDE function together with I/O message communications by maintaining a separate connection.

This section describes how to communicate with an MP2300-series Controller by using the MSG-SNDE
function.

2-51

2.4 Communications with MP-series Controllers

TCP

DC24V

DC 0V

MP2300

YASKAWA

TEST

RDY

ALM

TX

RUN

ERR

BAT

MON

CNFG

INT

SUP

STOP

SW1

OFF ON

BATTERY

CPU I/O

218IF-01

ERR

COL

RX

RUN

STRX

TX

INIT

TEST

ONOFF

PORT

10Base-T

MW00400

Ethernet

MW00401

MW00499

MW00400

MW00401

MW00499

MW00498 MW00498

MP3000

(local station)

IP address: 192.168.001.001 IP address: 192.168.001.002

Master

Slave

Communications Protocol

Connect Type
Data Code

Port number: 10003

Port number: 10003

Local Station

Hold registers (M registers)

Read.

Remote Station

Hold registers (M registers)

Data size:

100 words

Data size:

100 words

Extended MEMOBUS protocol

MP2300

(remote station)

Binary

Using the MSG-SNDE Function with the MP3000 as the Master

Setting Example

The following figure illustrates how the contents of the MW00400 to MW00499 hold registers in the
MP2300 slave are written to the MW00400 to MW00499 hold registers in the MP3000 master.

2-52

2.4 Communications with MP-series Controllers

Ethernet Communications

Note

cd e

Using the MSG-SNDE Function with the MP3000 as the Master

 MP3000 Setup

Use the following procedure to set up the MP3000.

If the communications parameters (IP address and subnet mask) have already been set, skip to step 3.

1.

Double-click the cell for 218IFD in the Module Configuration Definition Tab Page.

The 218IFD Detail Definition Dialog Box will be displayed.

2. Set the communications parameters.

In the IP Address Boxes, enter the following address: 192.168.001.001.
In the Subnet Mask Boxes, enter the following mask: 255.255.255.000.
In the Gateway IP Address Boxes, enter the following address: 000.000.000.000.

3.

Click the

ters

Easy Setting

Area.

Button in the

Message Communications

Area in the

Connection Parame-

The Message Communications Easy Setting Dialog Box will be displayed.

2-53

2.4 Communications with MP-series Controllers





 



 

Using the MSG-SNDE Function with the MP3000 as the Master

4. Set the connection parameters.

Select 3 in the Connect No. Box.
Enter “10003” in the Port No. Box for the MP-series Controller.
Select Extended MEMOBUS in the Communications Protocol Type Box, and then click the

Default Button.

Select TCP in the Connect Type Box.
Select BIN in the Code Box.
Enter the following address in the Node Port IP Address Boxes for the other device: 192.168.001.002.
Enter “10003” in the Port No. Box for the other device.

Note: Disable automatic reception for any connection for which message functions (MSG-SNDE and MSG-RCVE)

are used. If message functions are used while automatic reception is enabled, the communications will not
function properly.

5. Click the OK Button.

6. Click the Yes Button in the Transmission Parameters Confirmation Dialog Box.

Note: If parameters have already been set for the same connection number and you click the Ye s Button in the

Transfer Parameters Confirmation Dialog Box, the settings will be overwritten by the parameters that are set
in the Message Communications Easy Setting Dialog Box.

7. Check the settings.

2-54

2.4 Communications with MP-series Controllers

Ethernet Communications

Using the MSG-SNDE Function with the MP3000 as the Master

Note: Changes made to the communications or connection parameters will become effective only after the changes

have been saved to flash memory and the power supply has been cycled.

8. Create a ladder program for the MSG-SNDE function.

A ladder program example is shown below.

2-55

2.4 Communications with MP-series Controllers

Using the MSG-SNDE Function with the MP3000 as the Master

2-56

9. Save the data to flash memory.

This concludes the settings for using the MP3000 as the master.

2.4 Communications with MP-series Controllers

Ethernet Communications

Note



 

Using the MSG-SNDE Function with the MP3000 as the Master

 Setting Up the Other Device (MP2300) to Connect

Use the following procedure to set up the MP2300.

If the communications parameters (IP address and subnet mask) have already been set, skip to step 3.

1.

Double-click the cell for
Page.

218IF

in the

Module Details

Area of the Module Configuration Definition Tab

The 218IF Detail Definition Dialog Box will be displayed.

2. Set the communications parameters.

In the IP Address Boxes, enter the following address: 192.168.001.002.
Select Edit − Local Station: TCP/IP Setting in the Engineering Manager Window.
In the Subnet Mask Boxes, enter the following mask: 255.255.255.000.
In the Gateway IP Address Boxes, enter the following address: 000.000.000.000.

2-57

2.4 Communications with MP-series Controllers

     



Using the MSG-SNDE Function with the MP3000 as the Master

3. Set the connection parameters.

Enter “10003” in the Local Port Box.
Enter the following address in the Node IP Address Boxes: 192.168.001.001.
Enter “10003” in the Node Port Box.
Select TCP in the Connect Type Box.
Select Extended MEMOBUS in the Protocol Type Box.
Select BIN in the Code Box.

Note: Changes made to the communications or connection parameters will become effective only after the changes

have been saved to flash memory and the power supply has been cycled.

4. Create a ladder program for the MSG-RCV function.

Refer to the following section for a ladder program example.
The sample uses a different communications buffer channel and connection number.



Setting Up the Other Device (MP2300) to Connect (page 2-47)

5. Save the data to flash memory.

This concludes the setup.

 Starting Communications

1. Turn ON the power to the MP2300 to start receiving messages.

In the ladder program example, message reception starts immediately after the system starts. No further
operation is required.

2. Turn ON the Execute Bit (e.g., DB000200) for the MSG-SNDE function in the MP3000 to start

sending messages.

The ladder program example is designed to send a message every second after five seconds have elapsed
from when the low-speed scan (or high-speed scan) starts.

To change the message transmission interval, change the timer value .

2-58

2.4 Communications with MP-series Controllers

Ethernet Communications

Execute

Abort

Dev - Typ

Pro - Typ

Cir - No

Ch - No

MSG-SNDE

Busy

Complete

Error

Param

Note

Message Functions

Message Functions

The message functions are used in user communications applications for the Extended MEMOBUS proto­col. You can send and receive message data by setting the necessary input items and parameters for the
message functions.

Inputs and Outputs for the MSG-SNDE Function

Function

Name

Function

Function
Definition

I/O Definitions No. Name

Input Items

Output Items

Sends a message to a remote station on the specified circuit of the communications device type.
This function can be used with various protocols.

1 Execute B-VAL Executes the transmission.

2 Abort B-VAL Forces the transmission to end.

3 Dev-Typ I-REG

4 Pro-Typ I-REG

5 Cir-No I-REG

6 Ch-No I-REG

7 Param Address input

1 Busy B-VAL Processing.

2 Complete B-VAL Process completed.

3 Error B-VAL Error occurred.

I/O

Designation

MSG-SNDE

Description

Communications device type
218IFD = 16

Communications Protocols
MEMOBUS = 1, No-protocol communications 1 = 2,
No-protocol communications 2 = 3

Circuit number
218IFD = 1 to 8

Communications buffer channel number
218IFD = 1 to 10

First address of parameter list
(MA or DA)

 Execute

Specify the bit to use to execute the message transmission.

When the Execute Bit turns ON, the message will be sent.

Keep the Execute Bit ON until the Complete or Error Bit turns ON. To send another message, turn
OFF the Execute Bit for at least one scan and then turn it ON again.

2-59

2.4 Communications with MP-series Controllers

Message Functions

 Abort

Specify the bit to use to abort the message transmission.

When the Abort Bit turns ON, the message transmission will be stopped unconditionally. The Abort Bit
takes precedence over the Execute Bit.

 Dev-Typ (Communications Device Type)

Specify the type code of the communications device.

Communications Device Type Code

218IFD 16

 Pro-Typ (Communications Protocol)

Specify the type code of the communications protocol.

Type Code

1 MEMOBUS

2

3

Communications

Protocols

No-protocol communica­tions 1 (unit: words)

No-protocol communica­tions 2 (unit: bytes)

Remarks

Select this protocol when using the Extended MEMOBUS protocol.
MEMOBUS is automatically converted to Extended MEMOBUS inside
the 218IFD.

This code is not used for the Extended MEMOBUS protocol.

This code is not used for the Extended MEMOBUS protocol.

 Cir-No (Circuit Number)

Specify the circuit number for the communications device.

Specify the same circuit number as displayed in the MPE720 Module Configuration Definition Tab Page.

The following table gives the valid circuit numbers.

Communications Device Valid Circuit Numbers

218IFD 1 to 8

2-60

2.4 Communications with MP-series Controllers

Ethernet Communications

Note

Note

Example

PARAM00

PARAM01

PARAM02

PARAM03

PARAM04

PARAM05

PARAM06

PARAM07

PARAM23

PARAM24

PARAM25

PARAM26

PARAM27

PARAM28

DW00000

DW00001

DW00002

DW00003

DW00004

DW00005

DW00006

DW00007

DW00023

DW00024

DW00025

DW00026

DW00027

DW00028

Registers

Parameter List

F xxx xxxx xxxx xxx 0

 Ch-No (Communications Buffer Channel Number)

Specify the channel number of the communications buffer.

You can specify any channel number provided it is within the valid range.

When executing more than one function at the same time, do not use the same channel number for the
same connection. You can use the same channel number as long as multiple functions are not executed
at the same time.

The following table gives the valid channel numbers.

Message Functions

Communications Device

Valid Channel

Numbers

218IFD 1 to 10

If the communications device is the 218IFD, there are 10 channels of communications buffers available
for both transmission and reception. Therefore, 10 connections may be used for sending and receiving at
the same time by using channels 1 to 10.

There must be as many MSG-SNDE or MSG-RCVE functions as the number of connections used at
the same time.

 Param (First Address of Parameter List)

Specify the first address of the parameter list.

A total of 29 words starting from the specified first word are automatically used for the parameter list. The
parameter list is used by inputting function codes and relevant parameter data. It is also where the process
results and status are output.

A parameter list with the first address set to DA00000 is shown below.

2-61

2.4 Communications with MP-series Controllers

t

Input: Execute

To send another message, turn OFF
the Execute Bit for at least one scan
after the completion of processing.

1 scan

Input: Abort

Output: Busy

Output: Complete

Output: Error

Message Functions

 Busy

Specify the bit that shows that the message transmission is in progress.

The Busy Bit is ON while a message transmission or abort is in progress.

Keep the Execute Bit or Abort Bit turned ON while the Busy Bit is ON.

 Complete

Specify the bit that shows when the message transmission has been completed.

The Complete Bit turns ON only for one scan when message transmission or forced abort processing has
been completed normally.

 Error

Specify the bit that shows if an error occurred when sending the message.
When an error occurs, the Error Bit will turn ON only for one scan.

The following diagrams show timing charts for the bit I/O items in the MSG-SNDE function.

• Normal Execution

Input: Execute

Input: Abort

Output: Busy

Output: Complete

Output: Error

• When Execution Is Aborted

To send another message, turn OFF
the Execute Bit for at least one scan
after the completion of processing.

1 scan

2-62

Ethernet Communications

• Execution When an Error Occurs

t

Input: Execute

Input: Abort

Output: Busy

Output: Complete

Output: Error

To send another message, turn
OFF the Execute Bit for at least
one scan after the error occurs.

1 scan

MSG-SNDE Function Parameters

2.4 Communications with MP-series Controllers

Message Functions

The following table describes the contents of the addresses specified by the PARAM input parameter to
the MSG-SNDE function.

No. I/O Meaning Description

00

01 Status Gives the status of the current function.

02

03

04 Status 1 Gives the communications status.

Out­puts

05 Status 2 Gives status information on the most recent error.

Status

06 Status 3 Gives the value of the send pass counter.

07 Status 4 Gives the value of the receive pass counter.

08 Status 5 Gives the value of the error counter.

09 Status 6 Reserved for system.

10

11 Option Not used for the Extended MEMOBUS protocol.

12 Function Code

13 Reserved for system. −

14

15

16 Remote Station Register Type Sets the register type to read/write at the remote station.

Inputs

17 Data Size

Parameters

18 Remote CPU Module Number Sets the CPU number at the remote station.

19 Reserved for system. −

20

21

22 Local Station Register Type

23 Reserved for system. −

Processing Result Gives the processing status.

Detail Error Code, Lower Word

Detail Error Code, Upper Word

Connection Number

Gives the details of an error.

Sets the connection number used to determine the remote station.

Sets the code of the function in the Extended MEMOBUS protocol.

Remote Station Data Address,
Lower Word

Remote Station Data Address,

Sets the data address to read/write at the remote station. (Use word
addresses for registers, bit addresses for relays or coils.)

Upper Word

Sets the size of the data to read/write. (Use word sizes for regis­ters, bit sizes for relays or coils.)

Local Station Data Address,
Lower Word

Local Station Data Address,
Upper Word

Sets the data address to store read/write data in the local station.
(Use word addresses for registers, bit addresses for relays or
coils.)

Sets the register type of the read/write data to store in the local
station.

Continued on next page.

2-63

2.4 Communications with MP-series Controllers

Message Functions

No. I/O Meaning Description

24

25 Reserved for system. −

26 Reserved for system. −

System

27 Reserved for system. −

28 Reserved for system. −

For system use −

−

 Processing Result (PARAM00)

This parameter gives the processing result.

Continued from previous page.

Processing

Result Value

00xx hex Busy

10xx hex Complete

8yxx hex Error

Note: The lower byte is used for system analysis.

Meaning

Refer to the following section for details on errors.



Detail Error Code (PARAM02 and PARAM03) (page 2-66)

 Status (PARAM01)

This parameter gives the status of the communications device.

The following figure shows the bit assignments and it is followed by a detailed description of each assign­ment.

FEDCBA9876543210

Bits 0 to 7:

Bits 8 to B:
COMMAND

PARAMETER

2-64

Bits C to E:
RESULT

Bit F:
REQUEST



REQUEST

This bit gives the status of the processing request for the MSG-SNDE function.

Bit Status Meaning

1 Processing is being requested.

0 Processing request has ended.

2.4 Communications with MP-series Controllers

Ethernet Communications



RESULT

These bits give the execution result of the MSG-SNDE function.

Code Abbreviation Meaning

0 CONN_NG

1 SEND_OK The message was sent normally.

2 REC_OK The message was received normally.

3 ABORT_OK The request to abort execution was completed.

4 FMT_NG A parameter formatting error occurred.

5 SEQ_NG A command sequence error occurred.

6 RESET_NG A reset occurred.

7 REC_NG A data reception error (error detected in the lower-layer program) occurred.



COMMAND

The message send failed or connection ended with an error in Ethernet
communications.

These bits indicate the processing command of the MSG-SNDE function.

Code Abbreviation Meaning

1 U_SEND General-purpose message transmission (for no-protocol communications)

2 U_REC General-purpose message reception (for no-protocol communications)

3 ABORT Forced abort

8M_SEND

9

C

* MR_SEND is executed after M_REC is executed.

M_REC

MR_SEND

∗

MEMOBUS command transmission: Completed when response is
received.

MEMOBUS command reception

∗

MEMOBUS response transmission

Message Functions



PARAMETE R

When RESULT = 4 (FMT_NG: parameter formatting error), these bits will indicate an error code from the
following table. For any other value, the bits will contain the connection number.

RESULT Code (Hex) Meaning

00 No error

01 Connection number out of range

02 Watchdog error for MEMOBUS response

When RESULT = 4 (FMT_NG:
Parameter Formatting Error)

Others  Connection number

03 Error in number of retries setting

04 Error in cyclic area setting

05 CPU number error

06 Data address error

07 Data size error

08 Function code error

2-65

2.4 Communications with MP-series Controllers

Message Functions

 Detail Error Code (PARAM02 and PARAM03)

These parameters give the detail error code.

Processing

Result Value

(PARAM00)

81 hex 1 Function code error

82 hex 2

83 hex 3 Data size error

84 hex 4

85 hex 5

86 hex 6

88 hex

89 hex 9 Device select error

C0 hex 40 hex Register type error

C1 hex 41 hex Data type error

C2 hex 42 hex

Detail

Error

Code

7 Data reception error

8 Data sending error

10H Connection error

Error Description Description

Address setting
error

Circuit number set­ting error

Channel number
setting error

Connection number
error

Local station
register type error

An unused function code was sent or received. Check
PARAM12 (Function Code).

The setting of one or more of the following parameters is out of
range. Check the settings.
PARAM14 and PARAM15 (Remote Station Data Address)
PARAM20 and PARAM21 (Local Station Data Address)

The data size for sending or receiving is out of range. Check
PARAM17 (Data Size).

The circuit number is out of range. Check the circuit number
(Cir-No) in the MSG-SNDE function.

The channel number for the communications buffer is out of
range. Check the communications buffer channel number (Ch­No) in the MSG-SNDE function.

The connection number is out of range. Check PARAM10
(Connection Number).

An error response was received from the communications
device. Check the connections to the device. Also check to see
if the remote device is ready to communicate.

A device that cannot be used was selected. Check the communi­cations device type (Dev-Typ) in the MSG-SNDE function.

The register type for the remote station is out of range. Check
PARAM16 (Remote Station Register Type).

The data type is out of range. Check the address table at the
remote station. This error occurs when using function code
434D hex or 434E hex.

The register type for the local station is out of range. Check
PARAM22 (Local Station Register Type).

2-66

 Status 1 (PARAM04)

This parameter gives status information.

Status 1 Value Meaning Description

1 IDLE The connection is idle.

2 WAIT The connection is waiting to be made.

3 CONNECT The connection is established.

−−−

Note: The status is updated when the function is executed in each scan.

 Status 2 (PARAM05)

This parameter gives information on the most recent error.

Status 2 Value Meaning Description

0 No error Normal

1 Socket Creation Error A socket could not be created.

2 Local Port Number Error Setting error in local station port number

3 Changing Socket Attribute Error

A system error occurred while setting the socket attri­bute.

Continued on next page.

2.4 Communications with MP-series Controllers

Ethernet Communications

Status 2 Value Meaning Description

4 Connection Error

5 Connection Error

6 System Error A socket polling error occurred while receiving data.

7 TCP Data Send Error The remote station does not exist.

8 UDP Data Send Error

9 TCP Data Receive Error

10 UDP Data Receive Error

11 Changing Socket Option Error

12 Data Conversion Error Error in protocol conversion

Note: The status is updated when the function is executed in each scan.

M-SND: The remote station rejected an attempt to
open a TCP connection.

M-RCV: An error occurred while passively opening a
TCP connection.

The data send request command was sent to a socket
that does not exist.

A disconnection request was received from the remote
station.

A data receive request was executed for a socket that
does not exist.

A system error occurred while changing the socket
options.

Message Functions

Continued from previous page.

 Status 3 (PARAM06)

This parameter gives the value of the send pass counter.

Status 3 Value Meaning Description

0 to 65535 Send Count Counts the number of times a message was sent.

Note: The status is updated when the function is executed in each scan.

 Status 4 (PARAM07)

This parameter gives the value of the receive pass counter.

Status 4 Value Meaning Description

0 to 65535 Receive Count Counts the number of times a message was received.

Note: The status is updated when the function is executed in each scan.

 Status 5 (PARAM08)

This parameter gives the value of the error counter.

Status 5 Value Meaning Description

0 to 65535 Error Count

Note: The status is updated when the function is executed in each scan.

Counts the number of errors that occurred during message pro­cessing.

 Status 6 (PARAM09)

This parameter is not used for the Extended MEMOBUS protocol.

 Connection Number (PARAM10)

Specify the remote station.

If the communications device is the 218IFD, enter the connection number. The valid setting range is given
in the following table.

2-67

2.4 Communications with MP-series Controllers

Message Functions

Communications

Device

218IFD 1 to 20

Note: Enter the same connection number as displayed in the 218IFD Detail Definition Dialog Box in the MPE720.

Connection

Number

Description

Specifies the connection number of the remote station to send the
message to.

 Options (PARAM11)

This parameter is not used for the Extended MEMOBUS protocol.

 Function Code (PARAM12)

Set the function code to send.

You can use the functions that are registered to the function codes.

Target

Function Code

00 hex − Not used for the Extended MEMOBUS protocol.

01 hex B Reads the states of coils.

02 hex B Reads the states of input relays.

03 hex W Reads the contents of hold registers.

04 hex W Reads the contents of input registers.

05 hex B Changes the state of a single coil.

06 hex W Writes to a single hold register.

07 hex − Not used for the Extended MEMOBUS protocol.

08 hex − Performs a loopback test.

09 hex W Reads the contents of hold registers (extended).

0A hex W Reads the contents of input registers (extended).

0B hex W Writes to hold registers (extended).

0C hex − Not used for the Extended MEMOBUS protocol.

0D hex W

0E hex W

0F hex B Changes the states of multiple coils.

10 hex W Writes to multiple hold registers.

Data
Type

Function

Reads the contents of non-consecutive hold
registers (extended).

Writes to non-consecutive hold registers
(extended).

Registers When Acting as

the Master

Send

Registers

MM

Continued on next page.

Receive

Registers

2-68

2.4 Communications with MP-series Controllers

Ethernet Communications

Note

Example

Target

Function Code

Data

Function

Type

4341 hex B Reads the states of bits.

4345 hex B Changes the state of a single bit.

4346 hex W Writes to a single register.

4349 hex W Reads the contents of registers.

434B hex W Writes to multiple registers.

434D hex W Reads the contents of non-consecutive registers.

434E hex W Writes to non-consecutive registers.

434F hex B Changes the states of multiple bits.

Note: B: Bit data, W: Integer data

 Reserved for System (PARAM13)

This parameter is used by the system.

Message Functions

Continued from previous page.

Registers When Acting as

the Master

Send

Registers

S, M, G, I, or

O

Receive

Registers

M or G

Do not change the value of PARAM13 from a user program or by any other means.

 Remote Station Data Address (PARAM14 and PARAM15)

Set the first address for data in the remote station.

Enter the first address as a decimal or hexadecimal number.

If the first address is MW01000, enter “1000” (decimal) or “3E8” (hexadecimal).

Target

Function Code

Data
Type

00 hex −

01 hex B

02 hex B

03 hex W

04 hex W

05 hex B

06 hex W

07 hex −

Not used for the Extended MEMOBUS
protocol.

Reads the states of coils.

Reads the states of input relays.

Reads the contents of hold registers.

Reads the contents of input registers.

Changes the state of a single coil.

Writes to a single hold register.

Not used for the Extended MEMOBUS
protocol.

08 hex − Performs a loopback test. Disabled.

09 hex W

0A hex W

0B hex W

Reads the contents of hold registers

(extended).

Reads the contents of input registers

(extended).

Writes to hold registers (extended).

Function Data Address Setting Range

∗1

∗1

∗2

∗2

∗1

∗2

∗2

∗2

∗2

0 to 65535 (0 to FFFF hex)

0 to 65535 (0 to FFFF hex)

0 to 65534 (0 to FFFE hex)

0 to 65535 (0 to FFFF hex)

0 to 65535 (0 to FFFF hex)

0 to 65534 (0 to FFFE hex)

0 to 65534 (0 to FFFE hex)

0 to 65535 (0 to FFFF hex)

0 to 65534 (0 to FFFE hex)

Disabled.

Disabled.

Continued on next page.

2-69

2.4 Communications with MP-series Controllers

Message Functions

Target

Function Code

Data

Type

0C hex −

0D hex W

0E hex W

0F hex B

10 hex W

4341 hex B

4345 hex B

4346 hex W

4349 hex W

434B hex W

434D hex W

434E hex W

434F hex B

*1. Coil or input relay read/write requests: Enter the address of the first bit of the data.
*2. Continuous register read/write requests: Enter the address of the first word of the data.
*3. Non-consecutive register read/write requests: Enter the address of the first M register of the address table.

Not used for the Extended MEMOBUS
protocol.

Reads the contents of non-consecutive hold

registers (extended).

Writes to non-consecutive hold registers

(extended).

Changes the states of multiple coils.

Writes to multiple hold registers.

Reads the states of bits.

Changes the state of a single bit.

Writes to a single register.

Reads the contents of registers.

Writes to multiple registers.

Reads the contents of non-consecutive

registers.

Writes to non-consecutive registers.

Changes the states of multiple bits.

Continued from previous page.

Function Data Address Setting Range

Disabled.

∗3

∗3

∗1

∗2

∗1

∗1

∗2

∗2

∗2

0 to 65534 (0 to FFFE hex)

0 to 65534 (0 to FFFE hex)

0 to 65535 (0 to FFFF hex)

0 to 65534 (0 to FFFE hex)

0 to 4294967295

(0 to FFFFFFFF hex)

Adjust the address to the remote
device’s address range.

Refer to the following section for the

∗3

∗3

∗1

address ranges of an MP3000-series
Controller.

Details on Protocols (page 2-378)

 Remote Station Register Type (PARAM16)

Set the register type in the remote station. This parameter is valid when using function codes 43 hex.

Enter the register type as a decimal or hexadecimal number.

Register Type Value Type Remarks

0 M Sets the target data type to MB for bits and MW for words.

1 G Sets the target data type to GB for bits and GW for words.

2 I Sets the target data type to IB for bits and IW for words.

3 O Sets the target data type to OB for bits and OW for words.

4 S Sets the target data type to SB for bits and SW for words.

5 or higher − Not used for the Extended MEMOBUS protocol.

The register types that can be used depend on whether you are reading or writing.

The following table lists the combinations of register types.

Function Code Applicable Register Types

4341 or 4349 hex M, G, I, O, or S

4345, 4346, 434B, or 434F hex M, G, O, or S

434D hex

434E hex

* The address table at the remote station is stored in registers in the local station. The contents of the M, G, I, O, and S

registers in the remote station can be read by specifying the register type in the address table at the remote station.
For more information on remote station address tables, refer to the following sections.

2.15 Using Message Functions − Function Code: 434D Hex (page 2-369)

2.15 Using Message Functions

∗

∗

−

Function Code: 434E Hex (page 2-371)

M or G

M or G

2-70

2.4 Communications with MP-series Controllers

Ethernet Communications

Message Functions

 Data Size (PARAM17)

Set the data size for the read/write request as the number of bits or words.

Be sure that the last data address that is determined by the offset, data address, and data size does not
exceed the valid data address range.

The range that is allowed for the data size depends on the function code and data area.

Target

Function Code

00 hex −

01 hex B Reads the states of coils. 1 to 2000

02 hex B Reads the states of input relays. 1 to 2000

03 hex W Reads the contents of hold registers. 1 to 125

04 hex W Reads the contents of input registers. 1 to 125

05 hex B Changes the state of a single coil. Disabled.

06 hex W Writes to a single hold register. Disabled.

07 hex −

08 hex − Performs a loopback test. Disabled.

09 hex W

0A hex W

0B hex W Writes to hold registers (extended). 1 to 2043 (binary) or 1 to 1019 (ASCII)

0C hex −

0D hex W

0E hex W

0F hex B Changes the states of multiple coils. 1 to 800

10 hex W Writes to multiple hold registers. 1 to 100

4341 hex B Reads the states of bits. 1 to 32704

4345 hex B Changes the state of a single bit. Disabled.

4346 hex W Writes to a single register. Disabled.

4349 hex W Reads the contents of registers. 1 to 2044

434B hex W Writes to multiple registers. 1 to 2041

434D hex W

434E hex W Writes to non-consecutive registers. 1 to 511

434F hex B Changes the states of multiple bits. 1 to 32640

Note: 1. The data sizes in the table are in decimal notation.

2. B: Bit data, W: Integer data

Data
Type

Not used for the Extended MEMOBUS
protocol.

Not used for the Extended MEMOBUS
protocol.

Reads the contents of hold registers
(extended).

Reads the contents of input registers
(extended).

Not used for the Extended MEMOBUS
protocol.

Reads the contents of non-consecutive
hold registers (extended).

Writes to non-consecutive hold regis­ters (extended).

Reads the contents of non-consecutive
registers.

Function Data Size Setting Range

Disabled.

Disabled.

1 to 2044 (binary) or 1 to 1020 (ASCII)

1 to 2044 (binary) or 1 to 1020 (ASCII)

Disabled.

1 to 2044 (binary) or 1 to 1020 (ASCII)

1 to 1022 (binary) or 1 to 510 (ASCII)

1 to 681

 Remote CPU Module Number (PARAM18)

Set the CPU Module number at the remote station.

Specify 1 if the remote device is an MP2000-series Controller.

If the remote device is a Yaskawa Controller that is not part of the MP2000 Series and it is comprised of
multiple CPU Modules, specify the destination CPU Module number.

For all other devices, specify 0.

2-71

2.4 Communications with MP-series Controllers

Note

Note

Message Functions

 Reserved for System (PARAM19)

This parameter is used by the system.

Do not change the value of PARAM19 from a user program or by any other means.

 Local Station Data Address (PARAM20 and PARAM21)

Set the address of the read data destination or write data source in the MP3000-series Controller.

The address is set as the word offset from address 0.

 Local Station Register Type (PARAM22)

Set the register type of the read data destination or write data source in the MP3000.

Register Type Value Type Remarks

0 M Sets the target data type to MB for bits and MW for words.

1 G Sets the target data type to GB for bits and GW for words.

2 I Sets the target data type to IB for bits and IW for words.

3 O Sets the target data type to OB for bits and OW for words.

4 S Sets the target data type to SB for bits and SW for words.

5 or higher − Not used for the Extended MEMOBUS protocol.

The register types that can be used depend on whether you are reading or writing.

The following table lists the combinations of register types.

Function Code Applicable Register Types

01, 02, 03, 04, 09, or 0A hex M, G, or O

05, 06, 0B, 0F, or 10 hex M, G, I, O, or S

0D hex M

0E hex M

4341 or 4349 hex M, G, or O

4345, 4346, 434B, or 434F hex M, G, I, O, or S

434D hex M or G

434E hex

No-protocol Communications

(No function code)

* You can store the write data address table in registers in the local station. The data stored in the M, G, I, O, and S regis-

ters in the local station can be read from or written to the remote station by specifying the register type in the write data
address table.

∗

M or G

M, G, I, O, or S

 Reserved for System (PARAM23)

This parameter is used by the system.

2-72

Do not change the value of PARAM23 from a user program or by any other means.

2.4 Communications with MP-series Controllers

Ethernet Communications

Note

Note

Message Functions

 For System Use (PARAM24)

This parameter is used by the system. It contains the channel number of the communications buffer that is
currently in use.

A user program must set PARAM24 to 0 on the first scan after startup. Thereafter, do not change the
value of PARAM24 from a user program or any other means. PARAM24 will be used by the system.

 Reserved for System (PARAM25 to PARAM28)

This parameter is used by the system.

Do not change the values of PARAM25 to PARAM28 from a user program or any other means.

2-73

2.4 Communications with MP-series Controllers

Message Functions

Inputs and Outputs for the MSG-RCVE Function

Function

Name

Function

Function
Definition

I/O
Definitions

Input Items

Output Items

MSG-RCVE

Receives a message from a remote station on the specified circuit of the communications device
type. This function can be used with various protocols.

MSG-RCVE

Execute

Abort

Dev - Typ

Pro - Typ

Cir - No

Ch - No

Param

No. Name

1 Execute B-VAL Executes the reception.

2 Abort B-VAL Forces the reception to end.

3 Dev-Typ I-REG

4 Pro-Typ I-REG

5 Cir-No I-REG

6Ch-No I-REG

7 Param Address input

1 Busy B-VAL Processing.

2 Complete B-VAL Process completed.

3 Error B-VAL Error occurred.

I/O

Designation

Communications device type
218IFD = 16

Communications Protocols
MEMOBUS = 1, No-protocol communications 1 = 2,
No-protocol communications 2 = 3

Circuit number
218IFD = 1 to 8

Communications buffer channel number
218IFD = 1 to 10

First address of parameter list
(MA or DA)

Busy

Complete

Error

Description

2-74

 Execute

Specify the bit to use to execute the message reception.

When the Execute Bit turns ON, the message will be received.

 Abort

Specify the bit to use to abort the message reception.

When the Abort Bit turns ON, the message reception will be stopped unconditionally. The Abort Bit takes
precedence over the Execute Bit.

 Dev-Type (Communications Device Type)

Specify the type code of the communications device.

Device Type Code

218IFD 16

Ethernet Communications

 Pro-Typ (Communications Protocol)

Note

Specify the type code of the communications protocol.

2.4 Communications with MP-series Controllers

Message Functions

Type Code

1 MEMOBUS

2

3

Communications

Protocols

No-protocol communica­tions 1 (unit: words)

No-protocol communica­tions 2 (unit: bytes)

Remarks

Select this protocol when using the Extended MEMOBUS protocol.
MEMOBUS is automatically converted to Extended MEMOBUS
inside the 218IFD.

This code is not used for the Extended MEMOBUS protocol.

This code is not used for the Extended MEMOBUS protocol.

 Cir-No (Circuit Number)

Specify the circuit number for the communications device.

Specify the same circuit number as displayed in the MPE720 Module Configuration Definition Tab Page.

The following table gives the valid circuit numbers.

Communications Device Valid Circuit Numbers

218IFD 1 to 8

 Ch-No (Communications Buffer Channel Number)

Specify the channel number of the communications buffer.

You can specify any channel number provided it is within the valid range.

When executing more than one function at the same time, do not use the same channel number for the
same connection. You can use the same channel number as long as multiple functions are not executed
at the same time.

2-75

2.4 Communications with MP-series Controllers

Note

Example

Message Functions

The following table gives the valid channel numbers.

Communications Device Valid Channel Numbers

218IFD 1 to 10

If the communications device is the 218IFD, there are 10 channels of communications buffers available
for both transmission and reception. Therefore, 10 connections may be used for sending and receiving at
the same time by using channels 1 to 10.

There must be as many MSG-RCVE or MSG-SNDE functions as the number of connections used at
the same time.

 Param (First Address of Parameter List)

Specify the first address of the parameter list.

A total of 52 words starting from the specified first word are automatically used for the parameter list. The
parameter list is used by inputting the connection number and relevant parameter data. It is also where the
process results and status are output.

A parameter list with the first address set to DA00000 is shown below.

Registers

DW00000

DW00001

DW00002

DW00003

DW00004

DW00005

DW00006

DW00007

DW00046

DW00047

DW00048

DW00049

DW00050

DW00051

Parameter List

F xxx xxxx xxxx xxx 0

PARAM00

PARAM01

PARAM02

PARAM03

PARAM04

PARAM05

PARAM06

PARAM07

PARAM46

PARAM47

PARAM48

PARAM49

PARAM50

PARAM51

2-76

2.4 Communications with MP-series Controllers

Ethernet Communications

t

Input: Execute

Input: Abort

Output: Busy

Output: Complete

Output: Error

To receive another message, keep
the Execute Bit ON even after the
completion of processing.

1 scan

t

Input: Execute

Input: Abort

Output: Busy

Output: Complete

Output: Error

To receive another message, keep
the Execute Bit ON even after the
completion of processing.

1 scan

Message Functions

 Busy

Specify the bit that shows that the message reception is in progress.

The Busy Bit is ON while a message reception or abort is in progress.

Keep the Execute Bit or Abort Bit turned ON while the Busy Bit is ON.

 Complete

Specify the bit that shows when the message reception has been completed.

The Complete Bit turns ON only for one scan when message reception or forced abort processing has been
completed normally.

 Error

Specify the bit that shows if an error occurred when receiving the message.
When an error occurs, the Error Bit will turn ON only for one scan.

The following diagrams show timing charts for the bit I/O items in the MSG-RCVE function.

• Normal Execution

• When Execution Is Aborted

2-77

2.4 Communications with MP-series Controllers

t

Input: Execute

Input: Abort

Output: Busy

Output: Complete

Output: Error

To receive another message,
keep the Execute Bit ON
even after the error occurs.

1 scan

Message Functions

• Execution When an Error Occurs

MSG-RCVE Function Parameters

The following table describes the contents of the addresses specified by the PARAM input parameter to
the MSG-RCVE function.

No. I/O Meaning Description

00

01 Status Gives the status of the current function.

02 Detail Error Code, Lower Word

03 Detail Error Code, Upper Word

04 Status 1 Gives the communications status.

Outputs

05 Status 2 Gives status information on the most recent error.

Status

06 Status 3 Gives the value of the send pass counter.

07 Status 4 Gives the value of the receive pass counter.

08 Status 5 Gives the value of the error counter.

09 Status 6 Reserved for system.

Processing Result Gives the processing status.

Gives the details of an error.

Continued on next page.

2-78

2.4 Communications with MP-series Controllers

Ethernet Communications

Message Functions

Continued from previous page.

No. I/O Meaning Description

10 Inputs Connection Number

11 I/O Option Not used for the Extended MEMOBUS protocol.

12 Outputs Function Code

13 I/O Reserved for system. −

14

15 Data address, upper word

16 Register type

Outputs

17 Data Size

18 Remote CPU Module Number Not used for the Extended MEMOBUS protocol.

19 I/O Reserved for system. −

20

21 Coil offset, upper word

22 Input relay offset, lower word

23 Input relay offset, upper word

24 Input register offset, lower word

25 Input register offset, upper word

26 Hold register offset, lower word

27 Hold register offset, upper word

28 Data relay offset, lower word

Parameters

29 Data relay offset, upper word

30 Data register offset, lower word

31 Data register offset, upper word

32 Output coil offset, lower word

33 Output coil offset, upper word

Inputs

34 Output register offset, lower word

35 Output register offset, upper word

36 M register writing range LO, lower word

37 M register writing range LO, upper word

38 M register writing range HI, lower word

39 M register writing range HI, upper word

40 G register writing range LO, lower word

41 G register writing range LO, upper word

42 G register writing range HI, lower word

43 G register writing range HI, upper word

44 O register writing range LO, lower word

45 O register writing range LO, upper word

46 O register writing range HI, lower word

47 O register writing range HI, upper word

48

49 Reserved for system. −

50 Reserved for system. −

System

51 Reserved for system. −

−

Data address, lower word

Coil offset, lower word

For system use −

Sets the connection number used to determine the
remote station.

Gives the function code requested by the remote
station.

Gives the first address of the data that was
requested by the remote station.

Gives the register type that was requested by the
remote station.

Gives the data size that was requested by the
remote station.

Sets the offset word address for a coil (MB).

Sets the offset word address for an input relay (IB).

Sets the offset word address for an input register
(IW).

Sets the offset word address for a hold register
(MW).

Sets the offset word address for a data relay (GB).

Sets the offset word address for a data register
(GW).

Sets the offset word address for an output coil
(OB).

Sets the offset address for an output register (OW).

Sets the first address of the writing range for hold
register coils.

Sets the last address of the writing range for hold
register coils.

Sets the first address of the writing range for data
register data relays.

Sets the last address of the writing range for data
register data relays.

Sets the first address of the writing range for out­put registers.

Sets the last address of the writing range for output
registers.

2-79

2.4 Communications with MP-series Controllers

FEDCBA9876543210

Bits 0 to 7:
PARAMETER

Bits 8 to B:
COMMAND

Bits C to E:
RESULT

Bit F:
REQUEST

Message Functions

 Processing Result (PARAM00)

This parameter gives the processing result.

Processing

Result Value

00xx hex Busy

10xx hex Complete

8yxx hex Error

Note: The lower byte is used for system analysis.

Meaning

Refer to the following section for details on errors.



Detail Error Code (PARAM02 and PARAM03) (page 2-81)

 Status (PARAM01)

This parameter gives the status of the communications device.

The following figure shows the bit assignments and it is followed by a detailed description of each assign­ment.



REQUEST

This bit gives the status of the processing request for the MSG-RCVE function.

Bit Status Meaning

1 Processing is being requested.

0 Processing request has ended.



RESULT

These bits give the execution result of the MSG-RCVE function.

Code Abbreviation Meaning

0 CONN_NG

1 SEND_OK The message was sent normally.

2 REC_OK The message was received normally.

3 ABORT_OK The request to abort execution was completed.

4 FMT_NG A parameter formatting error occurred.

5 SEQ_NG A command sequence error occurred.

6 RESET_NG A reset occurred.

7REC_NG

2-80

The message send failed or connection ended with an error in
Ethernet communications.

A data reception error (error detected in the lower-layer program)
occurred.

2.4 Communications with MP-series Controllers

Ethernet Communications

Message Functions



COMMAND

These bits indicate the processing command of the MSG-RCVE function.

Code (Hex) Abbreviation Meaning

1U_SEND

2U_REC

3 ABORT Forced abort

8M_SEND

9

C

* MR_SEND is executed after M_REC is executed.



PARAMETE R

M_REC

MR_SEND

∗

∗

General-purpose message transmission (for no-protocol communi­cations)

General-purpose message reception (for no-protocol communica­tions)

MEMOBUS command transmission: Completed when response is
received.

MEMOBUS command reception

MEMOBUS response transmission

When RESULT = 4 (FMT_NG: parameter formatting error), these bits will indicate an error code from the
following table. For any other value, the bits will contain the connection number.

RESULT Code (Hex) Meaning

00 No error

01 Connection number out of range

02 Watchdog error for MEMOBUS response

When RESULT = 4 (FMT_NG:
Parameter Formatting Error)

Others  Connection Number

03 Error in number of retries setting

04 Error in cyclic area setting

05 CPU number error

06 Data address error

07 Data size error

08 Function code error

 Detail Error Code (PARAM02 and PARAM03)

These parameters give the detail error code.

Processing

Result Value

(PARAM00)

81 hex 1 Function code error

82 hex 2 Address setting error

83 hex 3 Data size error

84 hex 4

Detail

Error

Code

Error Description Description

An unused function code was received. Check the function
code of the remote station.

The setting of one or more of the following parameters is out
of range. Check the settings.
PARAM14 and PARAM15 (Data Address)

PARAM20 and PARAM21 (Coil Offset)
PARAM26 and PARAM27 (Hold Register Offset)

The data size for receiving is out of range.
Check the data size at the remote station.

Circuit number setting
error

The circuit number is out of range. Check the circuit num­ber (Cir-No) in the MSG-RCVE function.

Continued on next page.

2-81

2.4 Communications with MP-series Controllers

Message Functions

Processing

Result Value

(PARAM00)

85 hex 5

86 hex 6

88 hex

89 hex 9 Device select error

C0 hex 40 hex Register type error

C1 hex 41 hex Data type error

Detail

Error

Code

7 Data reception error

8 Data sending error

10H Connection error

Error Description Description

Channel number
setting error

Connection number
error

Continued from previous page.

The channel number for the communications buffer is out
of range. Check the communications buffer channel num­ber (Ch-No) in the MSG-RCVE function.

The connection number is out of range. Check PARAM10
(Connection Number).

An error response was received from the communications
device. Check the connections to the device. Also check to
see if the remote device is ready to communicate.

A device that cannot be used was selected. Check the com­munications device type (Dev-Typ) in the MSG-RCVE
function.

The register type specified by the sending node is out of
range. Check the remote station register type setting at the
sending node.

The data type is out of range. Check the remote station
address table at the sending node. This error occurs when
using function code 434D hex or 434E hex.

 Status 1 (PARAM04)

This parameter gives status information.

Status 1 Value Meaning Description

1 IDLE The connection is idle.

2 WAIT The connection is waiting to be made.

3 CONNECT The connection is established.

−−−

 Status 2 (PARAM05)

This parameter gives information on the most recent error.

Status 2 Value Meaning Description

0 No error Normal

1 Socket Creation Error A socket could not be created.

2 Local Port Number Error Setting error in local station port number

3 Changing Socket Attribute Error A system error occurred while setting the socket attribute.

4 Connection Error

5 Connection Error

6 System Error A socket polling error occurred while receiving data.

7 TCP Data Send Error The remote station does not exist.

8 UDP Data Send Error

9 TCP Data Receive Error

10 UDP Data Receive Error

11 Changing Socket Option Error

12 Data Conversion Error Error in protocol conversion

M-SND: The remote station rejected an attempt to open a
TCP connection.

M-RCV: An error occurred while passively opening a
TCP connection.

The data send request command was sent to a socket that
does not exist.

A disconnection request was received from the remote sta­tion.

A data receive request was executed for a socket that does
not exist.

A system error occurred while changing the socket
options.

2-82