Mitsubishi Electric RD81MES96, MELSEC IQ-R, SW1DND-RMESIF-E, MX MESInterface-R User Manual

MELSEC iQ-R MES Interface Module User's Manual (Startup)

-RD81MES96

-SW1DND-RMESIF-E(MX MESInterface-R)

SAFETY PRECAUTIONS

WARNING

Indicates that incorrect handling may cause hazardous conditions, resulting in death or severe injury.

CAUTION

Indicates that incorrect handling may cause hazardous conditions, resulting in minor or moderate injury or property damage.

(Read these precautions before using this product.)

Before using this product, please read this manual and the relevant manuals carefully, and pay full attention to safety to

handle the product correctly.

In this manual, the safety precautions are classified into two levels: " WARNING" and " CAUTION".

Under some circumstances, failure to observe the precautions given under " CAUTION" may lead to serious

consequences.

Observe the precautions of both levels because they are important for personal and system safety.

Make sure that the end users read this manual and then keep the manual in a safe place for future reference.

[Design Precautions]

WARNING

● Configure safety circuits external to the programmable controller to ensure that the entire system operates safely even when a fault occurs in the external power supply or the programmable controller. Failure to do so may result in an accident due to an incorrect output or malfunction. (1) Emergency stop circuits, protection circuits, and protective interlock circuits for conflicting

operations (such as forward/reverse rotations or upper/lower limit positioning) must be configured external to the programmable controller.

(2) When the programmable controller detects an abnormal condition, it stops the operation and all

outputs are:

• Turned off if the overcurrent or overvoltage protection of the power supply module is activated.

• Held or turned off according to the parameter setting if the self-diagnostic function of the CPU module detects an error such as a watchdog timer error.

(3) All outputs may be turned on if an error occurs in a part, such as an I/O control part, where the

CPU module cannot detect any error. To ensure safety operation in such a case, provide a safety mechanism or a fail-safe circuit external to the programmable controller. For a fail-safe circuit example, refer to "General Safety Requirements" in the MELSEC iQ-R Module Configuration Manual.

(4) Outputs may remain on or off due to a failure of a component such as a relay and transistor in an

output circuit. Configure an external circuit for monitoring output signals that could cause a serious accident.

● In an output circuit, when a load current exceeding the rated current or an overcurrent caused by a load short-circuit flows for a long time, it may cause smoke and fire. To prevent this, configure an external safety circuit, such as a fuse.

● Configure a circuit so that the programmable controller is turned on first and then the external power supply. If the external power supply is turned on first, an accident may occur due to an incorrect output or malfunction.

● For the operating status of each station after a communication failure, refer to manuals relevant to the network. Incorrect output or malfunction due to a communication failure may result in an accident.

● When connecting an external device with a CPU module or intelligent function module to modify data of a running programmable controller, configure an interlock circuit in the program to ensure that the entire system will always operate safely. For other forms of control (such as program modification, parameter change, forced output, or operating status change) of a running programmable controller, read the relevant manuals carefully and ensure that the operation is safe before proceeding. Improper operation may damage machines or cause accidents.

● Especially, when a remote programmable controller is controlled by an external device, immediate action cannot be taken if a problem occurs in the programmable controller due to a communication failure. To prevent this, configure an interlock circuit in the program, and determine corrective actions to be taken between the external device and CPU module in case of a communication failure.

[Design Precautions]

WARNING

● Do not write any data to the "system area" and "write-protect area" of the buffer memory in the module. Also, do not use any "use prohibited" signals as an output signal from the CPU module to each module. Doing so may cause malfunction of the programmable controller system. For the "system area", "write-protect area", and the "use prohibited" signals, refer to the user's manual for the module used.

● If a communication cable is disconnected, the network may be unstable, resulting in a communication failure of multiple stations. Configure an interlock circuit in the program to ensure that the entire system will always operate safely even if communications fail. Incorrect output or malfunction due to a communication failure may result in an accident.

● To maintain the safety of the programmable controller system against unauthorized access from external devices via the network, take appropriate measures. To maintain the safety against unauthorized access via the Internet, take measures such as installing a firewall.

[Design Precautions]

CAUTION

● Do not install the control lines or communication cables together with the main circuit lines or power cables. Keep a distance of 100 mm or more between them. Failure to do so may result in malfunction due to noise.

● During control of an inductive load such as a lamp, heater, or solenoid valve, a large current (approximately ten times greater than normal) may flow when the output is turned from off to on. Therefore, use a module that has a sufficient current rating.

● After the CPU module is powered on or is reset, the time taken to enter the RUN status varies depending on the system configuration, parameter settings, and/or program size. Design circuits so that the entire system will always operate safely, regardless of the time.

● Do not power off the programmable controller or do not reset the CPU module while the settings are being written. Doing so will make the data in the flash ROM or SD memory card undefined. The values need to be set in the buffer memory and written to the flash ROM or the SD memory card again. Doing so may cause malfunction or failure of the module.

● When changing the operating status of the CPU module from external devices (such as remote RUN/ STOP functions), select "Do Not Open in Program" for "Open Method Setting" in the module parameters. If "Open in Program" is selected, an execution of remote STOP causes the communication line to close. Consequently, the CPU module cannot reopen the communication line, and the external device cannot execute the remote RUN.

[Installation Precautions]

WARNING

● Shut off the external power supply (all phases) used in the system before mounting or removing the module. Failure to do so may result in electric shock or cause the module to fail or malfunction.

[Installation Precautions]

CAUTION

● Use the programmable controller in an environment that meets general specifications written in Safety Guidelines included in the base unit. Failure to do so may result in electric shock, fire, malfunction, or damage to or deterioration of the product.

● To mount a module, place the concave part(s) located at the bottom onto the guide(s) of the base unit, and push in the module, and make sure to fix the module with screws since this module has no module fixing hook. Incorrect interconnection may cause malfunction, failure, or drop of the module.

● Tighten the screws within the specified torque range. Undertightening can cause drop of the screw, short circuit, or malfunction. Overtightening can damage the screw and/or module, resulting in drop, short circuit, or malfunction.

● When using an extension cable, connect it to the extension cable connector of the base unit securely. Check the connection for looseness. Poor contact may cause malfunction.

● When using an SD memory card, fully insert it into the memory card slot. Check that it is inserted completely. Poor contact may cause malfunction.

● Securely insert an extended SRAM cassette into the cassette connector of a CPU module. After insertion, close the cassette cover and check that the cassette is inserted completely. Poor contact may cause malfunction.

● Do not directly touch any conductive parts and electronic components of the module, SD memory card, extended SRAM cassette, or connector. Doing so may cause malfunction or failure of the module.

[Wiring Precautions]

WARNING

● Shut off the external power supply (all phases) used in the system before installation and wiring. Failure to do so may result in electric shock or cause the module to fail or malfunction.

● After installation and wiring, attach the included terminal cover to the module before turning it on for operation. Failure to do so may result in electric shock.

[Wiring Precautions]

CAUTION

● Individually ground the FG and LG terminals of the programmable controller with a ground resistance of 100 ohms or less. Failure to do so may result in electric shock or malfunction.

● Use applicable solderless terminals and tighten them within the specified torque range. If any spade solderless terminal is used, it may be disconnected when the terminal screw comes loose, resulting in failure.

● Check the rated voltage and signal layout before wiring to the module, and connect the cables correctly. Connecting a power supply with a different voltage rating or incorrect wiring may cause fire or failure.

● Connectors for external devices must be crimped or pressed with the tool specified by the manufacturer, or must be correctly soldered. Incomplete connections may cause short circuit, fire, or malfunction.

● Securely connect the connector to the module. Poor contact may cause malfunction.

● Do not install the control lines or communication cables together with the main circuit lines or power

cables. Keep a distance of 100 mm or more between them. Failure to do so may result in malfunction due to noise.

● Place the cables in a duct or clamp them. If not, dangling cable may swing or inadvertently be pulled, resulting in damage to the module or cables or malfunction due to poor contact. Do not clamp the extension cables with the jacket stripped. Doing so may change the characteristics of the cables, resulting in malfunction.

● Check the interface type and correctly connect the cable. Incorrect wiring (connecting the cable to an incorrect interface) may cause failure of the module and external device.

● Tighten the terminal screws or connector screws within the specified torque range. Undertightening can cause drop of the screw, short circuit, fire, or malfunction. Overtightening can damage the screw and/or module, resulting in drop, short circuit, fire, or malfunction.

● When disconnecting the cable from the module, do not pull the cable by the cable part. For the cable with connector, hold the connector part of the cable. For the cable connected to the terminal block, loosen the terminal screw. Pulling the cable connected to the module may result in malfunction or damage to the module or cable.

● Prevent foreign matter such as dust or wire chips from entering the module. Such foreign matter can cause a fire, failure, or malfunction.

● A protective film is attached to the top of the module to prevent foreign matter, such as wire chips, from entering the module during wiring. Do not remove the film during wiring. Remove it for heat dissipation before system operation.

[Wiring Precautions]

CAUTION

● Programmable controllers must be installed in control panels. Connect the main power supply to the power supply module in the control panel through a relay terminal block. Wiring and replacement of a power supply module must be performed by qualified maintenance personnel with knowledge of protection against electric shock. For wiring, refer to the MELSEC iQ-R Module Configuration Manual.

● For Ethernet cables to be used in the system, select the ones that meet the specifications in the user's manual for the module used. If not, normal data transmission is not guaranteed.

[Startup and Maintenance Precautions]

WARNING

● Do not touch any terminal while power is on. Doing so will cause electric shock or malfunction.

● Correctly connect the battery connector. Do not charge, disassemble, heat, short-circuit, solder, or

throw the battery into the fire. Also, do not expose it to liquid or strong shock. Doing so will cause the battery to produce heat, explode, ignite, or leak, resulting in injury or fire.

● Shut off the external power supply (all phases) used in the system before cleaning the module or retightening the terminal screws, connector screws, or module fixing screws. Failure to do so may result in electric shock.

[Startup and Maintenance Precautions]

CAUTION

● Do not disassemble or modify the modules. Doing so may cause failure, malfunction, injury, or a fire.

● Use any radio communication device such as a cellular phone or PHS (Personal Handy-phone

System) more than 25cm away in all directions from the programmable controller. Failure to do so may cause malfunction.

● Shut off the external power supply (all phases) used in the system before mounting or removing the module. Failure to do so may cause the module to fail or malfunction.

● Tighten the screws within the specified torque range. Undertightening can cause drop of the component or wire, short circuit, or malfunction. Overtightening can damage the screw and/or module, resulting in drop, short circuit, or malfunction.

● After the first use of the product, do not mount/remove the module to/from the base unit, and the terminal block to/from the module, and do not insert/remove the extended SRAM cassette to/from the CPU module more than 50 times (IEC 61131-2 compliant) respectively. Exceeding the limit may cause malfunction.

● After the first use of the product, do not insert/remove the SD memory card to/from the CPU module more than 500 times. Exceeding the limit may cause malfunction.

● Do not touch the metal terminals on the back side of the SD memory card. Doing so may cause malfunction or failure of the module.

● Do not touch the integrated circuits on the circuit board of an extended SRAM cassette. Doing so may cause malfunction or failure of the module.

● Do not drop or apply shock to the battery to be installed in the module. Doing so may damage the battery, causing the battery fluid to leak inside the battery. If the battery is dropped or any shock is applied to it, dispose of it without using.

● Startup and maintenance of a control panel must be performed by qualified maintenance personnel with knowledge of protection against electric shock. Lock the control panel so that only qualified maintenance personnel can operate it.

[Startup and Maintenance Precautions]

CAUTION

● Before handling the module, touch a conducting object such as a grounded metal to discharge the static electricity from the human body. Failure to do so may cause the module to fail or malfunction.

[Operating Precautions]

CAUTION

● When changing data and operating status, and modifying program of the running programmable controller from an external device such as a personal computer connected to an intelligent function module, read relevant manuals carefully and ensure the safety before operation. Incorrect change or modification may cause system malfunction, damage to the machines, or accidents.

● Do not power off the programmable controller or reset the CPU module while the setting values in the buffer memory are being written to the flash ROM in the module. Doing so will make the data in the flash ROM or SD memory card undefined. The values need to be set in the buffer memory and written to the flash ROM or SD memory card again. Doing so can cause malfunction or failure of the module.

[Disposal Precautions]

CAUTION

● When disposing of this product, treat it as industrial waste.

● When disposing of batteries, separate them from other wastes according to the local regulations. For

details on battery regulations in EU member states, refer to the MELSEC iQ-R Module Configuration Manual.

[Transportation Precautions]

CAUTION

● When transporting lithium batteries, follow the transportation regulations. For details on the regulated models, refer to the MELSEC iQ-R Module Configuration Manual.

● The halogens (such as fluorine, chlorine, bromine, and iodine), which are contained in a fumigant used for disinfection and pest control of wood packaging materials, may cause failure of the product. Prevent the entry of fumigant residues into the product or consider other methods (such as heat treatment) instead of fumigation. The disinfection and pest control measures must be applied to unprocessed raw wood.

CONDITIONS OF USE FOR THE PRODUCT

(1) Mitsubishi programmable controller ("the PRODUCT") shall be used in conditions;

i) where any problem, fault or failure occurring in the PRODUCT, if any, shall not lead to any major or serious accident;

and

ii) where the backup and fail-safe function are systematically or automatically provided outside of the PRODUCT for the

case of any problem, fault or failure occurring in the PRODUCT.

(2) The PRODUCT has been designed and manufactured for the purpose of being used in general industries.

MITSUBISHI SHALL HAVE NO RESPONSIBILITY OR LIABILITY (INCLUDING, BUT NOT LIMITED TO ANY AND ALL

RESPONSIBILITY OR LIABILITY BASED ON CONTRACT, WARRANTY, TORT, PRODUCT LIABILITY) FOR ANY

INJURY OR DEATH TO PERSONS OR LOSS OR DAMAGE TO PROPERTY CAUSED BY the PRODUCT THAT ARE

OPERATED OR USED IN APPLICATION NOT INTENDED OR EXCLUDED BY INSTRUCTIONS, PRECAUTIONS, OR

WARNING CONTAINED IN MITSUBISHI'S USER, INSTRUCTION AND/OR SAFETY MANUALS, TECHNICAL

BULLETINS AND GUIDELINES FOR the PRODUCT.

("Prohibited Application")

Prohibited Applications include, but not limited to, the use of the PRODUCT in;

• Nuclear Power Plants and any other power plants operated by Power companies, and/or any other cases in which the

public could be affected if any problem or fault occurs in the PRODUCT.

• Railway companies or Public service purposes, and/or any other cases in which establishment of a special quality

assurance system is required by the Purchaser or End User.

• Aircraft or Aerospace, Medical applications, Train equipment, transport equipment such as Elevator and Escalator,

Incineration and Fuel devices, Vehicles, Manned transportation, Equipment for Recreation and Amusement, and

Safety devices, handling of Nuclear or Hazardous Materials or Chemicals, Mining and Drilling, and/or other

applications where there is a significant risk of injury to the public or property.

Notwithstanding the above, restrictions Mitsubishi may in its sole discretion, authorize use of the PRODUCT in one or

more of the Prohibited Applications, provided that the usage of the PRODUCT is limited only for the specific

applications agreed to by Mitsubishi and provided further that no special quality assurance or fail-safe, redundant or

other safety features which exceed the general specifications of the PRODUCTs are required. For details, please

contact the Mitsubishi representative in your region.

INTRODUCTION

Thank you for purchasing the Mitsubishi Electric MELSEC iQ-R series programmable controllers.

This manual describes the performance specifications, procedure before operation, wiring, and operation examples to use the

module listed below.

Before using this product, please read this manual and the relevant manuals carefully and develop familiarity with the

functions and performance of the MELSEC iQ-R series programmable controller to handle the product correctly.

When applying the example programs provided in this manual to an actual system, ensure the applicability and confirm that it

will not cause system control problems.

Please make sure that the end users read this manual.

The program examples shown in this manual are the examples in which MES interface module (RD81MES96)

is assigned to the input/output No. X/Y0 to X/Y1F unless otherwise specified. To use the program examples

shown in this manual, the input/output number assignment is required. For details on the assignment of input/

output number, refer to the following manual. MELSEC iQ-R Module Configuration Manual

Relevant product

RD81MES96

COMPLIANCE WITH THE EMC AND LOW VOLTAGE DIRECTIVES

Method of ensuring compliance

To ensure that Mitsubishi programmable controllers maintain EMC and Low Voltage Directives when incorporated into other

machinery or equipment, certain measures may be necessary. Please refer to one of the following manuals.

• MELSEC iQ-R Module Configuration Manual

• Safety Guidelines (included in a base unit)

The CE mark on the side of the programmable controller indicates compliance with EMC and Low Voltage Directives.

Additional measures

To ensure that this product maintains EMC and Low Voltage Directives, please refer to one of the following manuals.

• MELSEC iQ-R Module Configuration Manual

• Safety Guidelines (included in a base unit)

SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

CONDITIONS OF USE FOR THE PRODUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

INTRODUCTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

COMPLIANCE WITH THE EMC AND LOW VOLTAGE DIRECTIVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

RELEVANT MANUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

CHAPTER 1 PART NAMES 16

CHAPTER 2 SPECIFICATIONS 18

2.1 Performance Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Hardware specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Software specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.2 Accessible Devices and Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Accessible CPU modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Accessible routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Accessible devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Access units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

2.3 Accessible Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Software corresponding to accessible database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Access route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

2.4 Usable Data for MES Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Data category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Data type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Device tag component/variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Constant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Macro. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

CONTENTS

CHAPTER 3 FUNCTION LIST 41

3.1 Function Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3.2 Function List of an MES Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

3.3 Function List of MES Interface Function Configuration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.4 Function List of DB Connection Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.5 Function List of DB Connection Service Setting Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.6 Function List of Project File Conversion Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

CHAPTER 4 PROCEDURE BEFORE OPERATION 45

4.1 Starting Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

DB Connection Service/DB Connection Service Setting Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

4.2 Starting an MES Interface Module and an Configuration Personal Computer . . . . . . . . . . . . . . . . . . . . . . 48

MES Interface Function Configuration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Parameter settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

4.3 SD Memory Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Connectable SD memory cards (sold separately) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Inserting and removing method of SD memory cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Considerations for using SD memory cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

CHAPTER 5 SYSTEM CONFIGURATION 61

5.1 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Overall system configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Software configuration of MX MESInterface-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

System configuration when installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

System configuration for the initial setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

5.2 Operating Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Configuration personal computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Server (Database server/Application server). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

5.3 Considerations for System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

CHAPTER 6 WIRING 69

6.1 Ethernet Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Connectable twisted pair cables (sold separately) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Wiring of an Ethernet cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Wiring considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

CHAPTER 7 INSTALLATION AND UNINSTALLATION 71

7.1 Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Environment after installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

7.2 Uninstallation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Environment after uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

CHAPTER 8 OPERATION EXAMPLE 74

8.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

8.2 Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

System configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Device setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

8.3 Creating a Database Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Database table creation procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

8.4 ODBC Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

ODBC setting procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

8.5 MES Interface Function Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Parameter setting procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Operation check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

APPENDIX 100

Appendix 1 External Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Appendix 2 ODBC Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

INDEX 108

REVISIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

WARRANTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

RELEVANT MANUALS

Manual name [manual number] Description Available form

MELSEC iQ-R MES Interface Module User's Manual (Startup) [SH-081422ENG] (this manual)

MELSEC iQ-R MES Interface Module User's Manual (Application) [SH-081423ENG]

This manual does not include detailed information on the following:

• General specifications

• Applicable CPU modules and the number of mountable modules

• Applicable remote head modules and the number of mountable modules

• Installation

For details, refer to the following manual. MELSEC iQ-R Module Configuration Manual

e-Manual refers to the Mitsubishi Electric FA electronic book manuals that can be browsed using a dedicated

tool.

e-Manual has the following features:

• Required information can be cross-searched in multiple manuals.

• Other manuals can be accessed from the links in the manual.

• Hardware specifications of each part can be found from the product figures.

• Pages that users often browse can be bookmarked.

• Sample programs can be copied to an engineering tool.

Explains the specifications, procedure before operation, wiring, and operation examples of an MES interface module.

Explains the functions, MES Interface Function Configuration Tool, DB Connection Service, parameter setting, troubleshooting, input/output, and buffer memory of an MES interface module.

Print book e-Manual PDF

TERMS

Unless otherwise specified, this manual uses the following terms.

Ter m Description

Account A right to use MES interface module or a server, or an ID necessary for their use.

Action A unit for processing defined in a job.

There are three kinds of actions: DB communication action for communicating with a database, operation action for calculating values of device tag component, and external communication action for executing programs in an application server. The DB communication action is a processing unit for sending one SQL statement (Select, Update, Insert, Multiple Select, or Delete) or one DB procedure execution request. The operation action is a processing unit for performing a maximum of 20 binary operations.

Configuration personal computer A personal computer to set various settings required for operating MES interface module.

This computer can be shared with a server.

Data source Connection information which is necessary for accessing data using ODBC.

With Windows, a data source name is assigned to connection information for management. The database is accessed via ODBC by specifying the data source name with the information linkage function.

Database (DB) or relational database (RDB)

DB buffering A function that temporarily stores SQL statements, that failed to be sent due to a communication error, to an SD memory

DB procedure A program that combines sequential processing procedures into one program against the database, and saves it to the

Device memory or device Various memory data in a CPU module.

Device tag (Tag) Data table that contains a set of information (component) required to access device data in each CPU module on a

Device tag component (Component)

Engineering tool A tool for setting, programming, debugging, and maintaining programmable controllers.

Handshake For highly reliable processing, devices in a CPU module are used for managing processing between the CPU module

High-speed access A generic term for the following access types.

Item A setting group unit that each setting type in the edit items has.

Job A unit of process for linking information by a MES interface module.

LCPU A generic term for MELSEC-L series CPU modules.

MES An acronym for Manufacturing Execution Systems.

MES Interface Function Configuration Tool

MES interface module An abbreviation for RD81MES96 MES interface module.

MX MESInterface-R A product name for SW1DND-RMESIF-E.

Network module A generic term for the following modules:

QCPU (Q mode) A generic term for MELSEC-Q series CPU modules and MELSEC-Q series C Controller modules.

RCPU A generic term for MELSEC iQ-R series CPU modules and MELSEC iQ-R series C Controller modules.

RnENCPU A generic term for R04ENCPU, R08ENCPU, R16ENCPU, R32ENCPU, and R120ENCPU.

RnPCPU A generic term for R08PCPU, R16PCPU, R32PCPU, and R120PCPU.

Data management method that follows relational data model logic. A piece of data is expressed as a collection of multiple items (fields) and a data collection is expressed as a table. Data can be easily merged and selected using key data.

card, and resends them when the communications have been recovered.

database management system. This performs processing based on arguments received from MES interface module, and returns the results to MES interface module.

There are devices handled in each bit and in each word.

network. MES interface module collects device data for each tag at an interval defined in the tag.

A generic term for components (device data) which configures a device tag. Data that contains communication routes, data types, devices, etc. required to access device data in each CPU module.

For the supported tools, refer to the following manual. MELSEC iQ-R Module Configuration Manual

and MES interface module.

• High-speed access (interval specification)

• High-speed access (each scan)

A system for controlling and monitoring the plant status in real time to optimize production activities. The system enables to speed up responses to changes of a production plan and situation that lead to efficient production processes and optimization of production activities.

An abbreviation for MELSEC iQ-R series MES Interface Function Configuration Tool.

• CC-Link IE Controller Network module

• CC-Link IE Field Network module

• MELSECNET/H network module

• Ethernet interface module

• CC-Link module

Term Description

Server A generic term for a database server and application server.

Database server is a computer with a relational database which links information with MES interface module. Application server is a computer with a program which operates upon request from MES interface module.

Server service A generic term for the services of a server to which DB Connection Service is installed.

There are a database server service and an application server service. Database server service is a service for accessing a database. Application server service is a service for linking with a program.

SQL An abbreviation for Structured Query Language.

A database manipulation language that is used for operating a relational database.

Trigger buffering When trigger conditions (conditions for data transmission) of multiple jobs are satisfied at the same time, their data and

times are buffered in a internal memory of a module so that actions (data operation/transmission) can be executed later using the buffered data. Even if the frequency of data transmission triggers is high, jobs are executed without missing any trigger.

Trigger condition Startup conditions for job operation.

Update settings Processing that updates the settings in MES interface module using MES Interface Function Configuration Tool.

Variable (temporary variable) A variable that can be used for saving values selected from a database temporarily, and for writing operation values to a

database or device tag components. There are two types of variables: local variable which has variable area for each job and global variable which can be used for other jobs since it has a common variable area for all jobs.

Windows 8 or later A generic term for Windows 8, Windows 8.1, and Windows 10.

For definitions of terms for safety CPUs, refer to the following manual. MELSEC iQ-R CPU Module User's Manual (Application)

1 PART NAMES

(3)

(2)

(4)

(5)

(10)

(6)

(1)

(7)

(8)

(9)

This chapter shows the part names of an MES interface module.

No. Name Description

(1) RUN LED Indicates the operating status.

• ON: In operation

• Flashing: Checking module, selecting the module for online module change (Flashes for 10 seconds when checking modules by clicking the [Module Confirmation] button on the "MES Interface Module Search" screen of MES Interface Function Configuration Tool.)

• OFF: Watchdog timer error (hardware failure), module replacement allowed in the process of the online module change

ERR LED Indicates the error status of MES interface module.

• ON: Module continuation error or watchdog timer error (hardware failure)

• Flashing: Module stop error

• OFF: In normal status

DB COM LED Indicates the connection status with a database.

• ON: Database normal connection status (Communication is normally being established with all databases excluding unconnected databases.)

• Flashing: Database communication error status (A communication error is detected in communication with some or all databases.)

• OFF: Database unconnected status (Communication has never been established with any database after powering ON, resetting a CPU module, or updating the setting.)

DB BUF LED Indicates the execution status of DB buffering.

• ON: Executing DB buffering (Turns ON when the DB buffering setting is enabled and while buffering, or when either DB buffering setting 1 or 2 is buffering.)

CARD RDY LED Indicates the availability of SD memory card.

CARD ACS LED Indicates the access status of SD memory card.

• Flashing: DB buffer full (Flashes when the DB buffering setting is enabled and the buffer is full (no capacity), or when either DB buffering setting 1 or 2 is buffer full.)

• OFF: DB buffering unexecuted (The DB buffering setting is disabled, or the DB buffering setting is enabled and the buffer is empty.)

• ON: Accessible to an SD memory card

• Flashing: Preparing or formatting an SD memory card

• OFF: Not accessible to an SD memory card (Removable status)

For the considerations when handling SD memory cards, refer to the following section. Page 59 Considerations for using SD memory cards

• ON: Accessing an SD memory card

• OFF: Not access an SD memory card

1 PART NAMES

No. Name Description

(2) Dot matrix LED Displays the contents of each display mode or the results of the self-diagnostic test.

The following contents are displayed in each display mode.

• User specification character: Scrolled and displayed by the width of approximately 3 characters (3.3 characters).

• Error code: Displayed in four digits in hexadecimal (When multiple errors occur, only the latest error code is displayed.)

• IP address: Scrolled and displayed by 4 characters in decimal.

• DB buffer use rate: Displayed in three digits in decimal + %.

For the display when performing the self-diagnostic test, refer to the following manual. MELSEC iQ-R MES Interface Module User's Manual (Application)

(3) Slot cover A cover of the SD memory card slot and the switches.

Open this cover to insert/remove an SD memory card or to operate the switches. Close the cover unless inserting/removing an SD memory card or operating the switches to prevent foreign material intrusion such as dust.

(4) SPEED LED(CH1, CH2) Indicates the communication speed and the link status for Ethernet.

• ON (orange): Linking-up (1000 Mbps)

• ON (green): Linking-up (100 Mbps)

• OFF: Linking-down or linking-up (10 Mbps)

(5) SD/RD LED(CH1, CH2) Indicates the data sending/receiving status for Ethernet.

• ON: Sending/receiving data

• OFF: Not send/receive data

(6) Ethernet port (CH1, CH2)

(7) Dot matrix LED display mode switch

(SELECT/MODE/SHOW switch)

(8) SD memory card lock switch

(SD CARD OFF button)

(9) SD memory card slot A slot to insert an SD memory card

(10) Product information marking Displays the product information (16 digits) of the module.

A port for connecting to an Ethernet device (IEEE802.3, 1000BASE-T/100BASE-TX/10BASE-T standards-compliant)

A switch for switching the display of dot matrix LED.

• MODE: Displays the display mode name that is currently selected.

• SELECT: Selects (switches) the display mode Order: USR → ENo. → IP1 → IP2 → BUF1 → BUF2 → USR

• SHOW: Displays the contents of the selected display mode (Page 17 Dot matrix LED display)

Keep this display mode switch in the SHOW state during operation, and operate the switch only when switching the display mode.

A switch for disabling access to an SD memory card to remove it. Removing an SD memory card is prohibited while the CARD RDY LED is ON or flashing. For the procedure to insert/remove SD memory cards, refer to the following section. Page 58 Inserting and removing method of SD memory cards

(SD, SDHC standards-compliant: 2 GB (SD) to 16 GB (SDHC))

*1 Only CH1 can be connected to MES Interface Function Configuration Tool with direct connection.

Dot matrix LED display

The following table shows the contents of the display mode displayed on the dot matrix LED when switching the display mode

to "SHOW".

Display mode name Description

USR Displays the characters specified in the action.

ENo. Displays the error code.

IP1 Displays the IP address of the Ethernet port CH1.

IP2 Displays the IP address of the Ethernet port CH2.

BUF1 Displays the use rate of the DB buffer 1.

BUF2 Displays the use rate of the DB buffer 2.

The following display switching of dot matrix LED can be set by using MES Interface Function Configuration

To ol .

• Default display mode at power ON (Initial value: USR)

• The display mode is switched to ENo. (error code) forcibly when an error occurs.

• ENo. (error code) is highlighted.

Substitute characters to display on the S_MATRIXLED_DISP (dot matrix LED display) of the system variable in the action. For details on the action, refer to the following manual. MELSEC iQ-R MES Interface Module User's Manual (Application)

1 PART NAMES

2 SPECIFICATIONS

This chapter explains the performance specifications and accessible devices/device range of an MES interface module.

2.1 Performance Specifications

This section shows the performance specifications of a hardware (MES interface module) and software (MX MESInterface-R).

Hardware specifications

The following table shows the specifications of an MES interface module.

Item Specification

SD memory card slot Interface SD memory card/SDHC memory card (2 GB to 16 GB)

Power supply +3.3 VDC, up to 200 mA

Ethernet port Number of channels 2

Interface

Data transmission rate 1000 Mbps 100 Mbps 10 Mbps

Number of cascaded

stages

Communication mode Full-duplex/half-duplex

Transmission method Base band

Maximum segment

length

Applicable connector for external wiring

Supported function • Auto-negotiation (automatic recognition of 1000BASE-T/100BASE-TX/10BASE-T)

Number of occupied I/O points 32 points/slot (I/O assignment: Intelli. 32 points)

Clock Acquired from a CPU module (in multiple CPU system, CPU No.1).

5 VDC internal current consumption 1.25 A

External dimensions Height 106 mm

Width 27.8 mm

Depth 110 mm

Weight 0.25 kg

1000BASE-T 100BASE-TX 10BASE-T

 Maximum 2 stages Maximum 4 stages

100 m (length between a hub and a node)

RJ45

• Auto-MDI/MDI-X (automatic recognition of a straight/crossing cable)

Page 19 Basic operation specification

*1 1000BASE-T/100BASE-TX/10BASE-T, and full-duplex/half-duplex communication mode are identified by an MES interface module

depending on the hub. For connection with a hub not having the auto-negotiation function, set the setting on the hub side according to the communication mode.

*2 It is for a repeater hub.

For a switching hub, consult the manufacturer of the hub used.

*3 For the maximum segment length (length between hubs), consult the manufacturer of the switching hub used.

2 SPECIFICATIONS

2.1 Performance Specifications

Software specifications

The following table shows the specifications of MX MESInterface-R.

Item Description Reference

Basic operation specification Specification for the operation (job), startup condition for the job (trigger condition),

operation unit of a job (action), and network information.

Device memory input/output specification

DB input/output specification Specification for the accessible database, access units (access table/procedure,

Variable input/output specification

Data operation and processing specification

External communication client Specification for the communication from an MES interface module to external

Security Specification for security. Page 22 Security

Specification for the accessible target device type and the access units. Page 20 Device memory input/output

access field/procedure argument), and buffering of output data (DB buffering) at disconnecting.

Specification for user variables (local variables, global variables) which can be defined freely, system variables to refer to system information, and data types of variable.

Specification for the operation processing such as addition and subtraction. Page 22 Data operation and

devices.

Basic operation specification

Item Specification

Job (Number of settings) Maximum 64 jobs

Action (Number of settings) Maximum 1920 actions

For one job 30 actions

Trigger condition For one job 2 events/condition

Event/condition type • Condition (Value monitoring)

Condition combination type • OR combination

Trigger buffering count 192 (The value is cleared due to power interruption/reset/setting update.)

Time information handling (Time information)

Ethernet Connection method IPv4

MES Interface Function Configuration Tool

Time Acquired from a CPU module (in multiple CPU system, CPU No.1).

Daylight saving time

Time zone

Number of channels 2 channels (CH1/CH2) (Unconnectable to a same network, and no routing function between

Number of default gateways 1 (Only CH1 or CH2 can be registered.)

Simultaneously connectable number

*1 When using the daylight saving time function of a CPU module, use an MES interface module with the firmware version '03' or later. If an

MES interface module with the firmware version '02' or earlier is used, it may cause the malfunction of the module due to the time information difference with the CPU module. For information on the firmware version of a CPU module, refer to the manual of a CPU module used.

• Main processing: 20 actions

• Pre/post-processing: 10 actions

• Condition (Period of time)

• Event (Value changed)

• Event (Fixed time)

• Event (Fixed cycle) (timer interval/time interval)

• Event (Module monitoring) (MES interface module/Control CPU)

• Handshake

• AND combination

CH1 and CH2)

5 (Maximum number of connections to a single MES interface module)

Page 19 Basic operation specification

Page 21 DB input/output

Page 22 Variable input/output

processing

Page 22 External communication client

2 SPECIFICATIONS

2.1 Performance Specifications

Device memory input/output

Item Specification

Access target device Maximum 16 devices

Type of target device • RCPU

Device tag Maximum 64 device tags

Access type • General access

Shortest access interval Each scan

Access interval (general access) • 1 to 9 × 100 ms

Access interval (high-speed access (interval specification))

Access interval (high-speed access (each scan))

Device tag component Maximum 65536 components/project (64 tags × 1024 components)

Maximum (for one device tag) 1024 components

Maximum (for one job) 20480 components

Number of data points (Device tag component)

Number of data points

(Job)

Access data Data type • Bit

Maximum number (per project) 131072 (total number without array tag setting)

Maximum number (for one device tag component)

Maximum number (per project)

Maximum number (for one job) 46080

*1 For high-speed access, up to 8192 components (points) can be set. *2 When the trigger buffering is enabled, the maximum is 8192 components (points). *3 The double word device is counted as 2 points. *4 When using a same device tag component in multiple jobs, the number is counted for each job.

When using a same device tag component in a same job, the number is not counted for each job.

• QCPU (Q mode)

•LCPU

• High-speed access (interval specification)

• High-speed access (each scan)

• 1 to 3600 sec.

• 1 to 9 ms

• 1 to 9 × 10 ms

• 1 to 9 × 100 ms

• 1 to 60 sec.

• Each scan

2621440 (total number with array tag setting)

40960 (at Multiple Select)

131072 (total number excluding the data assignment settings of the Multiple Select setting) 2949120 (total number only for the data assignment settings of the Multiple Select)

The total size of character string type: 2048 characters/job (total of the device tag, variable, constant, and macro)

• Word [Unsigned]/Bit String [16-bit]

• Double Word [Unsigned]/Bit String [32-bit]

• Word [Signed]

• Double Word [Signed]

• 16bit BCD

• 32bit BCD

• FLOAT[Single Precision]

• FLOAT[Double Precision]

• Character string [Unicode]

• Character string [ASCII/SJIS]

2 SPECIFICATIONS

2.1 Performance Specifications

DB input/output

Item Specification

Access target server Database type • Oracle

Maximum number of settings 16 servers

Access table/procedure DB communication type • Select

Maximum number of settings (for one project)

Maximum number of settings (for one job)

Maximum number of settings (for one action)

Maximum number of settings (per access table)

Access field/procedure argument

DB buffer Number of settings 2 settings

Maximum number of settings (per

project)

Maximum number of settings (for one

job)

Maximum number of settings for access field (for one table)

Maximum number of settings for access procedure argument (for one procedure)

Data type • Integer

Maximum capacity 2048 MB (up to 1024 MB for each buffer)

*1 Maximum number of settings in the job settings. *2 Maximum number of settings in the access table/procedure settings. *3 A data type when a character string is set to an access procedure argument. *4 Data types when a character string is set to an access field.

• Microsoft SQL Server

• Microsoft Access

•MySQL

•PostgreSQL

• Insert

• Update (Data can be inserted if no update target data exist.)

• Delete

• Multiple Select

• Stored Procedure

64 tables/procedures

20 tables/procedures

1 table/procedure

Total length of DB field name: 16384 characters

65536 settings

• When the trigger buffering is disabled: 20480 settings

• When the trigger buffering is enabled: 8192 settings

However, the following limits are applied.

• Date and time type access field/procedure argument: Up to 50 settings

• The total number of characters of character string type: Up to 2048 characters (The total number of characters of character string type for the device tag, variable, and constant)

1024 fields

256 settings

• Real number

• Character string [Unicode]

• Character string [Unicode(NCHAR)]

• Character string [Unicode(CHAR)]

• Date and time

2 SPECIFICATIONS

2.1 Performance Specifications

Variable input/output

Item Specification

Variable type Type • Local variable (retains data only at a job execution and can be used in a same job.)

Data type Type • Bit

Capacity Maximum number of settings (per

project)

Maximum number of settings (for

one job)

• Global variable (retains data until the power supply is turned OFF or the CPU is reset, and can be used between different jobs.)

• System variable

• Word [Unsigned]/Bit String [16-bit]

• Double Word [Unsigned]/Bit String [32-bit]

• Word [Signed]

• Double Word [Signed]

• FLOAT[Single Precision]

• FLOAT[Double Precision]

• Character string [Unicode]

• Local variable: 1024 words (2048 bytes)

• Global variable: 4096 words (8192 bytes)

• System variable: A defined variable is used.

• Local variable: 1024 words (2048 bytes)

• Global variable: 512 words (1024 bytes)

*1 The number of settings depends on the data size. However, 2 bytes are used even when the data type is bit. *2 The total number of characters of character string type for one job is up to 2048 characters.

Data operation and processing

Item Specification

Operator Substitution 

Arithmetic operation 5 types

Maximum number of operation settings

Character string operation

Bit operation 5 types

Type conversion 4 types

Maximum 38400 settings (600 settings × 64 jobs)

For one job 600 settings (20 settings × 30 actions)

For one action 20 settings

8 types

External communication client

Item Specification

External communication client (program execution)

Number of characters for execution command

Function • Return value evaluation

Up to 127 characters

• Execution completion standby

Security

Item Specification

Security (user authentication) Number of accounts 16 accounts

2 SPECIFICATIONS

2.1 Performance Specifications

2.2 Accessible Devices and Range

This section shows the accessible devices and range.

Accessible CPU modules

Series Model name Access type

RCPU

QCPU (Q mode)

LCPU

*1 When using high-speed access, use a CPU module supporting the sequence scan synchronization sampling function and an MES

interface module with the firmware version '03' or later.

For a CPU module supporting the sequence scan synchronization sampling function, refer to the manual for the CPU module. *2 Use an MES interface module with the firmware version '07' or later. *3 Use an MES interface module with the firmware version '03' or later. *4 Use an MES interface module with the firmware version '05' or later. *5 It cannot be used as a relay station. *6 Only a module with a serial number of which the first five digits are 12042 or higher can be accessed.

Programmable controller CPU

Process CPU

Safety CPU

C Controller module

Programmable controller CPU

Process CPU Q02PHCPU, Q06PHCPU, Q12PHCPU, and Q25PHCPU

C Controller module

Programmable controller CPU

R00CPU*2, R01CPU*2, R02CPU*2, R04CPU, R04ENCPU*3, R08CPU, R08ENCPU R120CPU, and R120ENCPU

R08PCPU, R16PCPU, R32PCPU, and R120PCPU • General access

R08SFCPU, R16SFCPU, R32SFCPU, and R120SFCPU

*3,*5

R12CCPU-V

Q00JCPU, Q00UJCPU, Q00CPU, Q00UCPU, Q01CPU, Q01UCPU, Q02CPU, Q02HCPU, Q02UCPU, Q03UDCPU, Q03UDECPU, Q03UDVCPU, Q04UDHCPU, Q04UDEHCPU, Q04UDVCPU, Q06HCPU, Q06UDHCPU, Q06UDEHCPU, Q06UDVCPU, Q10UDHCPU, Q10UDEHCPU, Q12HCPU, Q13UDHCPU, Q13UDEHCPU, Q13UDVCPU, Q20UDHCPU, Q20UDEHCPU, Q25HCPU, Q26UDHCPU, Q26UDEHCPU, Q26UDVCPU, Q50UDEHCPU, and Q100UDEHCPU

Q12DCCPU-V*6, Q24DHCCPU-V, Q24DHCCPU-LS, Q24DHCCPUVG, and Q26DHCCPU-LS

L02SCPU, L02SCPU-P, L02CPU, L02CPU-P, L06CPU, L06CPU-P, L26CPU, L26CPU-P, L26CPU-BT, and L26CPU-PBT

, R16CPU, R16ENCPU*3, R32CPU, R32ENCPU*3,

• General access

• High-speed access (interval specification)

• High-speed access (each scan)

When using a multiple CPU system, refer to the following manual. MELSEC iQ-R Module Configuration Manual

2 SPECIFICATIONS

2.2 Accessible Devices and Range

Accessible routes

1···8

ÒÓ Ô Õ

Ö×

(1)

(2)

(3)

2···8

The following figure shows accessible routes from an MES interface module.

: Access route from an MES

interface module

: Connection from an Ethernet

port of an MES interface module

: Connection by specifying the network number and the station number of a target station

: Connection by specifying the start I/O No. of a module to be routed and the station number of a target station

Accessible route Reference

(1) Own station (control CPU, another

CPU in a multiple CPU system)

(2) Another station via a single

network

(3) Another station via a co-existence

network

 Indicates the own station (control CPU, another CPU in a multiple CPU system)

 Access via an Ethernet port of an MES interface module Page 26 Access via an Ethernet port

 Access by specifying the network number and the station number of a

target station (CC-Link IE Controller Network module, CC-Link IE Field Network module, MELSECNET/H network module, or Ethernet interface module)

 Access by specifying the start I/O No. of a module to be routed and the station number of a target station (CC-Link module)

 Access from the station accessed in  by specifying the network number and the station number of a target station

 Access from the station accessed in  by specifying the start I/O No. of a module that is routed through and the station number of a target station

Page 25 Own station (control CPU, another CPU in a multiple CPU system)

of an MES interface module

Page 27 Access by specifying the network number and the station number of a target station

Page 27 Access by specifying the start I/O number of a module to be routed and the station number of a target station

Page 28 Access by specifying the network number and the station number via another station on CCLink

Page 28 Accessing from another station specified by the network number and the station number via CC-Link

2 SPECIFICATIONS

2.2 Accessible Devices and Range

Own station (control CPU, another CPU in a multiple CPU system)

The following table shows the accessibility to a CPU module of a station on which an MES interface module is mounted. : Accessible, : No combination

Access route Type of target device (series)

RCPU QCPU (Q mode) LCPU

Programm able controller CPU/ Process CPU/ Safety CPU

Control CPU 

Other CPUs in multiple CPU system 

*1 No combination with RnENCPUs.

(CPU No.1 to

C Controller module



(CPU No.1 to

Programm able controller CPU/ Process CPU



C Controller module

Programm able controller CPU

2 SPECIFICATIONS

2.2 Accessible Devices and Range

Another station via a single network

■Access via an Ethernet port of an MES interface module

A target device can be accessed via an Ethernet port of an MES interface module in the status where the target device is

connected to a network.

For the communication destination from an Ethernet port of an MES interface module, an Ethernet interface module or a CPU

module (Ethernet port) can be specified.

For accessing a target station, direct access and access via another system

*1 It is not available when the series of a target device and a system to be routed differ.

(Example) Access is available when the series of a target device and a system to be routed are 'QCPU'.

: Accessible, : No combination

Access route Type of target device (series)

RCPU QCPU (Q mode) LCPU

Programm able controller CPU/ Process CPU/ Safety CPU

Ethernet Ethernet port of an MES

interface module → Ethernet interface module

Ethernet port of an MES interface module → CPU module (Ethernet port)

Direct 

Via another system

Direct 

Via another system

CC-Link IE Controller Network

CC-Link IE Field Network

MELSECNET/H network

Ethernet

CC-Link IE Controller Network

CC-Link IE Field Network

MELSECNET/H network

Ethernet

*2,*3

(CPU No.1 to

are available.

C Controller module

Programm able controller CPU/

C Controller module

Programm able controller

CPU Process CPU





(CPU No.1 to



(CPU No.1 to



(CPU No.1 to





(CPU No.1 to





(CPU No.1 to











*2 It can access to an RnENCPU only in a single CPU system. *3 No combination with the MELSECNET/H network for process CPUs and safety CPUs. *4 It is also supported by a QCPU (Q mode) for which the MELSOFT connection extended setting was set. *5 To access an Ethernet port of Q12DCCPU-V (Basic mode) directly, MELSOFT connection is required to be permitted in the

Q12DCCPU-V (Basic mode) setting. For details on the setting, refer to the following manual. C Controller Module User's Manual (Utility Operation, Programming)

2 SPECIFICATIONS

2.2 Accessible Devices and Range

■Access by specifying the network number and the station number of a target station

A target device can be accessed via a relay station when the target device is connected within eight networks from a station,

on which an MES interface module is mounted, and can be identified by the network number and the station number (or CPU

number). : Accessible, : No combination

Access route Type of target device (series)

RCPU QCPU (Q mode) LCPU

Programm able controller CPU/ Process CPU/

C Controller module

Programm able controller CPU/ Process CPU

C Controller module

Programm

able

controller

CPU

Safety CPU

CC-Link IE Controller Network 

CC-Link IE Field Network 

MELSECNET/H network 

Ethernet

*1,*2

(CPU No.1 to



(CPU No.1 to



(CPU No.1 to



(CPU No.1 to





*1 It can access to an RnENCPU only in a single CPU system. *2 No combination with the MELSECNET/H network for process CPUs and safety CPUs. *3 It is also supported by a QCPU (Q mode) for which the MELSOFT connection extended setting was set.

■Access by specifying the start I/O number of a module to be routed and the station number of a target station

The following table shows the accessible routes to connect with a target device and a station on which an MES interface

module is mounted directly. : Accessible, : No combination

Access route Type of target device (series)

RCPU QCPU (Q mode) LCPU

CC-Link 

*1 It can access to an RnENCPU only in a single CPU system.

Programm able controller CPU/ Process CPU/ Safety CPU

(CPU No.1 to

C Controller module



(CPU No.1 to

Programm able controller CPU/ Process CPU



(CPU No.1 to

C Controller module



(CPU No.1 to

Programm able controller CPU



2 SPECIFICATIONS

2.2 Accessible Devices and Range

Another station via a co-existence network

■Access by specifying the network number and the station number via another station on CCLink

The following table shows the accessible route to a target station from a station, on which an MES interface module is

mounted by specifying the network number and the station number of the target station. In this route, another station on CC-

Link is accessed first (first route), then a target station is accessed from there. : Accessible, : No combination

First access route Second access route (co-existence

network)

CC-Link CC-Link IE Controller Network 

CC-Link IE Field Network 

MELSECNET/H network 

Ethernet

Type of target device (series)

RCPU QCPU (Q mode) LCPU

Programm able controller CPU/ Process CPU/

C Controller module

Programm able controller CPU/ Process CPU

C Controller module

Programm able controller CPU

Safety CPU

*1,*2

(CPU No.1 to



(CPU No.1 to



(CPU No.1 to



(CPU No.1 to





■Accessing from another station specified by the network number and the station number via CC-Link

The following table shows the accessible route to a target station from a station, on which an MES interface module is

mounted, by specifying the start I/O No. of a module that is routed through and the station number of the target station. In this

route, another station on CC-Link is accessed first by specifying the network number and the station number (first route), then

the target device is accessed from there. : Accessible, : No combination

First access route Second access route

(co-existence network)

CC-Link IE Controller Network CC-Link 

CC-Link IE Field Network 

MELSECNET/H network 

Ethernet

Type of target device (series)

RCPU QCPU (Q mode) LCPU

Programm able controller CPU/ Process CPU/

C Controller module

Programm able controller CPU/ Process CPU

C Controller module

Programm able controller CPU

Safety CPU

*1,*2

(CPU No.1 to



(CPU No.1 to



(CPU No.1 to



(CPU No.1 to





2 SPECIFICATIONS

2.2 Accessible Devices and Range

+ 86 hidden pages

Mitsubishi Electric RD81MES96, MELSEC IQ-R, SW1DND-RMESIF-E, MX MESInterface-R User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

SAFETY PRECAUTIONS

CONDITIONS OF USE FOR THE PRODUCT

INTRODUCTION

COMPLIANCE WITH THE EMC AND LOW VOLTAGE DIRECTIVES

CONTENTS

RELEVANT MANUALS

TERMS

1 PART NAMES

Hardware specifications

2 SPECIFICATIONS

2.1 Performance Specifications

Software specifications

Accessible CPU modules

2.2 Accessible Devices and Range

Accessible routes