(Always read these instructions before using this equipment.)
Before using this product, please read this manual and the relevant manuals introduced in this manual
carefully and pay full attention to safety to handle the product correctly.
The instructions given in this manual are concerned with MELSEC communication protocol. For the safety
instructions of the programmable controller system, please read the user's manual for the CPU module to
use.
!
In this manual, the safety instructions are ranked as "
!
WARNING
!
CAUTION
!
Note that the
Always follow the instructions of both levels because they are important to personal safety.
Please save this manual to make it accessible when required and always forward it to the end user.
CAUTION level may lead to a serious consequence according to the circumstances.
Indicates that incorrect handling may cause hazardous conditions,
resulting in death or severe injury.
Indicates that incorrect handling may cause hazardous conditions,
resulting in minor or moderate injury or property damage.
[Design Precautions]
WARNING" and "!CAUTION".
!
WARNING
When changing data of the running programmable controller from a peripheral connected to the
CPU module or from a personal computer connected to an intelligent function module, configure
an interlock circuit in the sequence program to ensure that the entire system will always operate
safely.
For program modification and operating status change, read relevant manuals carefully and
ensure the safety before operation.
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 sequence program, and determine corrective
actions to be taken between the external device and CPU module in case of a communication
failure.
Do not write any data to the "system area" of the buffer memory in the intelligent function
module.
Also, do not use any "use prohibited" signals as an output signal from the programmable
controller CPU to the intelligent function module.
Doing so may cause malfunction of the programmable controller system.
A - 1 A - 1
[Operation Precautions]
!
CAUTION
When changing data and operating status, and modifying program of the running programmable
controller from 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.
While set values in the buffer memory are being registered to the flash ROM in the module, do
not turn off the power to the module and do not reset the CPU module.
Doing so will affect the flash ROM data, and setting to the buffer memory and registration to the
flash ROM need to be performed again.
Also, it may cause failure or malfunction of the module.
A - 2 A - 2
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.
A - 3 A - 3
REVISIONS
The manual number is given on the bottom left of the back cover.
Print Date Manual Number Revision
Dec., 1999 SH(NA)-080008-A First edition
Oct., 2000 SH(NA)-080008-B Reflect the contents of the function version B.
Put Windows base software products together from Mitsubishi
Programmable Controller MELSEC series to Mitsubishi integrated FA
software MELSOFT series. Standardize the name from software package
(GPP function) to product name (GX Developer).
Correction
Contents, Entire manual (change MELSECNET/10H to
MELSECNET/H), About Manuals, About the Generic Terms and
Abbreviations, Section 1.1(5), Section 2.2, 2.4, 2.6, 2.7 (g), 2.9, 2.10,
Section 3.1.1, 3.1.2 (figure), 3.1.3, 3.1.4 (figure), 3.1.5 (figure), 3.1.6
(5), REMARKS, 3.2 (table), 3.3.1 (table 6.3), 3.3.8 (POINT (screen)),
Jun., 2001 SH(NA)-080008-C Standardize the name from utility package (QSCU) to product name (GX
Configurator-SC).
Correction
About Manuals, The Manual's Use and Structure, About the Generic
Terms and Abbreviations, Meanings and Descriptions of Terminology,
Section 1.1(5), Section 2.2(table), 2.6.1(1)(table), 2.6.2(table), 2.10(4),
Section 3.2(table), 3.3.1(table), 3.3.2, 3.3.3, 3.3.7, 3.3.8(2)(3),
This manual confers no industrial property rights or any rights of any other kind, nor does it confer any patent
licenses. Mitsubishi Electric Corporation cannot be held responsible for any problems involving industrial property
rights which may occur as a result of using the contents noted in this manual.
1999 MITSUBISHI ELECTRIC CORPORATION
A - 6 A - 6
INTRODUCTION
Thank you for purchasing the MELSEC-Q/L series programmable controller.
This manual describes the functions of the MELSEC-Q/L series programmable controllers.
Before using this product, please read this manual and the relevant manuals carefully and develop familiarity
with the functions and performance of the MELSEC-L series programmable controller to handle the product
correctly.
Please always forward this manual to the end user.
1.1 Overview of the MELSEC Communication Protocol............................................................................ 1- 1
1.2 Features of the MELSEC Communication Protocol ............................................................................ 1- 3
2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL 2- 1 to 2- 34
2.1 Types and Applications of Data Communication Frames ...................................................................2- 1
2.2 Accessible Range of Each Data Communication Frames .................................................................. 2- 3
2.3 How to Read the Control Procedures of the MC Protocol................................................................... 2- 5
2.4 Access Timing of the Programmable Controller CPU Side ................................................................. 2- 6
2.5 Setting Method for Writing to the Programmable Controller CPU during RUN .................................. 2- 8
2.6 Accessing Other Stations ..................................................................................................................... 2- 9
2.6.1 Accessible programmable controllers of other stations ................................................................ 2- 9
2.6.2 Example of accessible station when each frame is used .............................................................2- 12
2.6.3 Example of designating data items for accessing other station designated within each data
communication frame .................................................................................................................... 2- 16
2.7 Precautions on Data Communication................................................................................................... 2- 19
2.7.1 When using E71 ............................................................................................................................. 2- 19
2.7.2 When using C24............................................................................................................................. 2- 21
2.8 Time Chart and Communication Time of the Transmission Sequence of
the Serial Communication Module ....................................................................................................... 2- 22
2.9 Transmission Time When Accessing Other Stations via CC-Link IE Controller Network,
CC-Link IE Field Network, MELSECNET/H, MELSECNET/10 ........................................................... 2- 25
2.10 Compatibility with Multiple CPU Systems .......................................................................................... 2- 28
2.11 Compatibility with the Serial Communication Function in the CPU Module ..................................... 2- 32
2.12 Compatibility with Programmable Controller CPU with Built-In Ethernet Port.................................. 2- 34
A - 7 A - 7
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME
3.8 File Control ............................................................................................................................................ 3-160
3.8.1 Commands and contents of character area..................................................................................3-161
3.8.2 Precautions on file control.............................................................................................................. 3-176
A - 8 A - 8
3.8.3 File control execution procedure for the Q/LCPU .........................................................................3-178
3.8.4 File control execution procedure for the QnACPU........................................................................ 3-183
3.8.5 Read directory/file information (command: 1810): for the Q/LCPU.............................................. 3-187
3.8.6 Search directory/file information (command: 1811): for the Q/LCPU........................................... 3-189
3.8.7 Open file (command: 1827): for the Q/LCPU................................................................................3-190
3.8.8 Close file (command: 182A): for the Q/LCPU ...............................................................................3-192
3.8.9 Read file (command: 1828): for the Q/LCPU ................................................................................3-193
3.8.10 Create new file (command: 1820): for the Q/LCPU .................................................................... 3-195
3.8.11 Write to file (command: 1829): for the Q/LCPU ..........................................................................3-196
3.8.12 Delete files (command: 1822): for the Q/LCPU .......................................................................... 3-198
3.8.13 Copy files (command: 1824): for the Q/LCPU ............................................................................ 3-200
3.8.14 Change date of file creation (command: 1826): for the Q/LCPU ............................................... 3-203
3.8.15 Change file attributes (command: 1825): for the Q/LCPU.......................................................... 3-204
3.8.16 Read file information list: for the QnACPU.................................................................................. 3-206
3.8.17 Reading file presence information (file search) (command: 0203): for the QnACPU................ 3-212
3.8.18 Registering and clearing file locks (command: 0808): for the QnACPU ....................................3-214
3.8.19 Reading the contents of a file (command: 0206): for the QnACPU ........................................... 3-216
3.8.20 Creating a new file (filename registration) (command: 1202): for the QnACPU........................ 3-218
3.8.21 Writing to a file (command: 1203): for the QnACPU................................................................... 3-220
3.8.22 Deleting files (command: 1205): for the QnACPU ...................................................................... 3-224
3.8.23 Copying files (command: 1206): for the QnACPU ...................................................................... 3-226
3.8.24 Changing the file information (command: 1204): for the QnACPU ............................................3-228
3.9 Registering, Deleting and Reading User Frames: for Serial Communication Modules ..................... 3-234
3.9.1 Commands and contents of character area..................................................................................3-234
3.9.2 Registering and deleting user frames (command: 1610).............................................................. 3-237
3.9.3 Reading user frames (command: 0610)........................................................................................ 3-239
3.10 Global Function: for Serial Communication Modules ........................................................................ 3-241
3.10.1 Commands and contents of the character area.......................................................................... 3-241
3.10.2 Control procedure of the global function (command: 1618) .......................................................3-243
3.11 Data Transmission to an External Device (On-Demand Function): for
Serial Communication Modules .........................................................................................................3-245
3.11.1 Execution procedure of the on-demand function ........................................................................ 3-246
3.11.2 Data transmission format of the on-demand function ................................................................. 3-249
3.11.3 Control procedure of the on-demand function (command: 2101) .............................................. 3-251
3.12 Initializing the Transmission Sequence: for Serial Communication Modules ................................... 3-256
This manual explains how to use the Web function of the Ethernet interface module. (Sold separately)
SH-080007
(13JL87)
Manual number
(model code)
SH-080009
(13JL88)
SH-081105ENG
(13JZ73)
SH-080180
(13JR40)
A - 13 A - 13
(3) CPU module user’s manual
Manual name
QnUCPU User's Manual (Function Explanation, Program Fundamentals)
Functions, methods, and devices for programming (Sold separately)
Manual number
(model code)
SH-080807ENG
(13JZ27)
Qn(H)/QnPH/QnPRHCPU User's Manual(Function Explanation, Program Fundamentals)
Functions, methods, and devices for programming (Sold separately)
MELSEC-L CPU Module User's Manual (Function Explanation, Program Fundamentals)
Functions, methods, and devices for programming (Sold separately)
QnUCPU User's Manual (Communication via Built-in Ethernet Port)
Functions of the built-in Ethernet port of the CPU module (Sold separately)
MELSEC-L CPU Module User's Manual (Built-In Ethernet Function)
Functions of the built-in Ethernet port of the CPU module (Sold separately)
(4) Operating manual
Manual name
GX Works2 Version1 Operating Manual (Common)
System configuration, parameter settings, and online operations (common to Simple project and
Structured project) of GX Works2. (Sold separately)
GX Developer Version 8 Operating Manual
Operating methods of GX Developer, such as programming, printing, monitoring, and debugging.
(Sold separately)
SH-080808ENG
(13JZ28)
SH-080889ENG
(13JZ35)
SH-080811ENG
(13JZ29)
SH-080891ENG
(13JZ37)
Manual number
(model code)
SH-080779ENG
(13JU63)
SH-080373E
(13JU41)
A - 14 A - 14
MANUAL PAGE ORGANIZATION
• How to use this manual
This manual explains the communication functions via the MC protocol, with each
section covering a specific function.
(1) To learn about the communication functions using the MC protocol
• A summary of the data communication using the MC protocol is explained in
Section 1.1
• The main data communication functions using the MC protocol are explained in
Section 1.2
(2) To learn about the types and access ranges of frames for the MC
protocol
(a) To learn how to read the frame names for the MC protocol
(b) To learn about the types and access ranges of frames
(3) When communicating through the MC protocol
• How to read the frame names is explained in Chapter 1.
• The correspondence between the communication frames of the
conventional modules and those for the MC protocol are explained in
Section 2.1.
• The types of frames that can be used for the serial communication
modules and Ethernet Interface modules are explained in Section 2.1.
• The application and access range of each frame are explained in Section
2.2 and succeeding sections.
• The common information on communication through the MC protocol is
explained in Chapter 2, Section 2.3 and succeeding sections.
• The commands, message formats, and control procedures for A
compatible 1C frame are explained in Chapter 5.
• The commands, message formats, and control procedures for A
compatible 1E frame are explained in Chapter 6.
• The commands, message formats, and control procedures for QnA
compatible 2C frame are explained in Chapter 4.
• The commands, message formats, and control procedures for QnA
compatible 3E, QnA compatible 3C, QnA compatible 4C frames, and 4E
frame are explained in Chapter 3.
A - 15 A - 15
• Structure of this manual
The explanations of the message formats and the control procedures while
communicating through the MC protocol are given in the following format:
[Control procedure]
(1) Reading eight points of data from internal
relays M100 to M107 in communication in
ASCII code
) in both the command message and the response message indicates the same order of data
items as in the control procedures when other commands are used.
Number of points to be read
Number of
device points
H
0 (30H) indicates off
1 (31
(Refer to Section 3.1.5.)
Data for the number of
designed device points
00010010
30H30H30H31H30H30H31H30
M100 = OFF
H) indicates on.
H
M106 = ON
M107 = OFF
This is a description of the
request from the external
device side for the control
procedure explained in the
example.
This diagram illustrates the
sequence of data items in the
command message to be sent
by the external device.
This diagram illustrates the
sequence of data items in the
response message (the
message providing the
processing result) to be sent by
the programmable controller
CPU side for the request sent
from the external device side.
(The head and end sections of the command and response messages.)
Confirm the order of data items in the fields marked with "
" by referring to the reference sections listed
below.
The order of data items in the fields marked with "
" differs between Ethernet interface modules and serial
communication modules.
(1) When communicating via an Ethernet Interface module
A compatible 1E frame : Refer to Section 6.1.
QnA compatible 3E frame : Refer to Section 3.1.2.
4E frame : Refer to Section 3.1.2.
(2) When communicating via a serial communication module
A compatible 1C frame : Refer to Section 5.1.
QnA compatible 2C frame : Refer to Section 4.1.
QnA compatible 3C frame : Refer to Section 3.1.4.
QnA compatible 4C frame : Refer to Section 3.1.5.
A - 16 A - 16
GENERIC TERMS AND ABBREVIATIONS
This manual uses the following generic terms and abbreviations to explain the serial communication modules,
Ethernet interface modules, and devices for data communication unless otherwise specified.
(1) Generic terms and abbreviations for CPU modules
Generic term
/abbreviation
ACPU
AnACPU Generic term for A2ACPU, A2ACPU-S1, A2ACPUP21/R21, A2ACPUP21/R21-S1, A3ACPU, A3ACPUP21/R21.
AnA/AnU/QnACPU Generic term for AnACPU, AnUCPU, QnACPU.
AnNCPU
AnUCPU Generic term for A2UCPU, A2UCPU-S1, A2ASCPU, A2ASCPU-S1, A3UCPU, A4UCPU.
AnU/QnACPU Generic term for AnUCPU, QnACPU.
LP25/BR15 Generic term for AJ72LP25, AJ72BR15.
QCPU
QnUDVCPU Generic term for Q03UDVCPU, Q04UDVCPU, Q06UDVCPU, Q13UDVCPU, Q26UDVCPU.
QCPU (A mode) Generic term for Q02CPU-A, Q02HCPU-A, Q06HCPU-A.
Basic model QCPU Generic term for Q00JCPU, Q00CPU, Q01CPU.
High Performance model
QCPU
Process CPU Generic term for Q02PHCPU, Q06PHCPU, Q12PHCPU, Q25PHCPU.
Redundant CPU Generic term for Q12PRHCPU, Q25PRHCPU.
Universal model QCPU
LCPU Generic term for MELSEC-L series CPU modules.
Safety CPU
QCPU station Abbreviation for the programmable controller with QCPU installed.
QE71
QLP21/QBR11 Generic term for AJ71QLP21, AJ71QBR11.
QLP25/QBR15 Generic term for AJ72QLP25 (G), AJ72QBR15, A1SJ72QLP25, A1SJ72QBR15.
QnACPU
QnACPU station Abbreviation for the programmable controller with QnACPU installed.
C24
E71 Abbreviation for QJ71E71-100, QJ71E71-B5, QJ71E71-B2 and LJ71E71-100 Ethernet interface modules.
Serial communication
module
UC24
Computer link module
Generic term for AnNCPU, AnACPU, AnUCPU, QCPU (A mode).
Generic term for A1NCPU, A1NCPUP21/R21, A2NCPU, A2NCPU-S1, A2NCPUP21/R21, A2NCPUP21/R21-S1,
A3NCPU, A3NCPUP21/R21.
Generic term for the Basic model QCPU, High Performance model QCPU, Process CPU, Redundant CPU, and Universal
model QCPU.
Generic term for Q02CPU, Q02HCPU, Q06HCPU, Q12HCPU, Q25HCPU.
Secure Digital Memory Card, which is a flash memory device.
The L1MEM-2GBSD and L1MEM-4GBSD are available.
A MELSEC-A/QnA series module that has other than input or output, such as A/D converter module
and D/A converter module.
Devices used to directly accesses the buffer memory of the special function module from the CPU
module.
In a redundant system, the Redundant CPU on the side to which the system A connector of the tracking
cable is connected.
In a redundant system, the Redundant CPU on the side to which the system B connector of the tracking
cable is connected.
Data name used when registering the fixed format section of a message to be communicated between
the serial communication module and an external device using the functions listed below, in order to use
it for data transmission and reception. (The contents of data in a user frame should be consistent with
the specifications of the external device.)
Used for registering the sequence of data of each of the head and ending sections in a communication
message (transmission control code, C24 station number, sum check, fixed data, etc.) to the serial
communication module.
• The on-demand function of the MC protocol
• Data transmission and reception functions through the non-procedure protocol.
One of the message formats for the Ethernet interface modules, in which ASCII or binary code data are
transferred with the MC protocol.
Any given number (serial No.) for message identification is added to the QnA compatible 3E frame.
By the serial No. which is added by the external device for message identification, the correspondence
between command and response messages can be checked.
A - 20 A - 20
1 OVERVIEW
1 OVERVIEW
This manual provides information on the methods that are employed by external
devices to read and write data from/to the programmable controller CPU using the data
communication functions of the MELSEC communication protocol (referred to as the
MC protocol in this manual) via the serial communication modules or Ethernet interface
modules.
When applying the following program examples to the actual system, make sure to
examine the applicability and confirm that it will not cause system control problems.
Operating procedures are explained using GX Developer.
Note that some screen names and items may differ when using GX Works2.
When performing data communication using the MC protocol, please read Chapter 2.
1.1 Overview of the MELSEC Communication Protocol
The following is an overview of the MC protocol:
(1) The MC protocol is the name of a communication method for Q/L series
programmable controller and is used by external devices to read and write device
data and programs of the programmable controller CPU via the C24 or E71.
Communications through the MC protocol can be performed if a device can
incorporate application programs and send/receive data using the control
procedures of the MC protocol.
(2) The message formats and control procedures for an external device to access the
programmable controller CPU are defined separately for the C24 and E71.
QJ71E71
QJ71C24
RUN
PRM
S
T
D LINK
MODE
RUN
N
O
MODE
ERR.
x10010 1
RUN
ERR.
USER
BAT.
BOOT
IN
USB
OUT
RS-232
ERR.
SD
RD
INIT.
COM.ERR
CH1. CH2.
OPEN
RD
SD
10BASE-T
CH1.
RS-232
10BASE
CH.2
SDA
1
SG
2
SDB
(FG)
3
RDA
4
(FG)
5
RDB
+
12V
6
12G
RS-422
7
/485
PULL
MITSUBISHI
Q25HCPU
POWER
MELSEC
1
QJ71E71
QJ71E71
QJ71C24
RUN
PRM
S
T
MODE
D LINK
RUN
N
O
MODE
ERR.
x10010 1
RUN
ERR.
USER
BAT.
BOOT
IN
USB
OUT
RS-232
ERR.
SD
RD
INIT.
COM.ERR
CH2.
CH1.
OPEN
SD
RD
10BASE-T
CH1.
RS-232
10BASE
CH.2
SDA
1
SG
2
SDB
(FG)
3
RDA
4
(FG)
5
RDB
+
12V
6
12G
RS-422
7
/485
PULL
MITSUBISHI
Q25HCPU
POWER
MELSEC
Q25HCPU
MELSEC
POWER
PULL
MITSUBISHI
QJ71C24
RUN
PRM
S
T
MODE
D LINK
RUN
N
O
MODE
ERR.
x100101
RUN
ERR.
USER
BAT.
BOOT
IN
USB
OUT
RS-232
ERR.
SD
RD
INIT.
COM.ERR
CH2.
CH1.
OPEN
SD
RD
10BASE-T
CH1.
RS-232
10BASE
CH.2
SDA
1
SG
2
SDB
(FG)
3
RDA
4
(FG)
5
RDB
+
12V
6
12G
RS-422
7
/485
(3) The message formats and control procedures during data communication using
the MC protocol are the same as when accessing the programmable controller
(Command message of the A compatible 1C frame)(Response message of the A compatible 1C frame)
CPU via conventional A/QnA series modules.
Number of
Sum
check
code
H
Station
number
PC number
Command
Head device
Message wa it
device point s
2 characters
(hexadecima l)
S
T
X
02H30H30H30H31H31H32H33H34H42H43H44
Data for the number
of device points
Station
number
HL H L
000 11234 BCD
device points
X 4 characters
PC number
Number of
A
H
41
Sum
E
check
T
code
X
HL
9
8
H
H
H
39H38
03
1 - 1 1 - 1
1
An external device can access a Q/L series programmable controller using a program
with which the programmable controller is accessed via one of the following A/QnA
series modules.
1) Accessing the programmable controller via the C24
It is possible to access the programmable controller using a program
on the external device via the following A/QnA series modules.
• A series computer link module
• QnA series serial communication module
2) Accessing the programmable controller via the E71
It is possible to access the programmable controller using a program
on the external device via the following A/QnA series modules.
• A series Ethernet interface module
• QnA series Ethernet interface module
The data communication functions using the MC protocol correspond
to the following data communication function of the conventional
modules.
• In case of the C24
Corresponds to the data communication functions using the
dedicated protocol supported by A series computer link modules and
QnA series serial communication modules.
• In case of the E71
Corresponds to the functions for reading/writing data from/to the
programmable controller CPU supported by A series/QnA series
Ethernet interface modules.
(4) At the programmable controller CPU side, the C24/E71 sends/receives data
according to the commands from an external device.
Thus, a sequence program for data communication is not required at the
programmable controller CPU side.
In case of the C24, a sequence program for data communication is required
when using the on-demand function for sending data from the programmable
controller CPU.
(5) If the external device is a personal computer, it is possible to create a
communication program for the external device without considering the message
formats or transmission/reception procedures of the MC protocol by using a
separately-available communication support tool (MX Component).
Depending on the version of MX Component used, different operating
systems are supported.
For details, refer to the MX Component manual.
1 OVERVIEW
1 - 2 1 - 2
1.2 Features of the MELSEC Communication Protocol
This section explains the features of the MC protocol.
(1) The data communication using the MC protocol is a function that enables the
reading/writing of data from/to the programmable controller CPU in order to
control and monitor the programmable controller equipment from the external
device side.
Reading/writing device data and program files for the programmable controller
CPU and controlling the programmable controller CPU status (remote
RUN/STOP) can be performed from the external devices (personal computer,
indicator, etc.)
(a) Reading and writing data
By reading/writing data to/from the device memory of the programmable
controller CPU and the buffer memory of the intelligent function modules,
the following control operations can be performed:
Data read and write operations can also be performed for A/QnA series
programmable controller CPUs (other stations) and intelligent function
modules.
1) Reading data
Operation monitoring, data analysis, production control, etc. can be
performed from the external device side.
2) Writing data
Production instructions, etc. can be issued from the external device
side.
(b) Reading and writing files
By reading and writing files for sequence programs and parameters stored
in the programmable controller CPU, the following control operations can
be performed:
1) Reading files
File management for the local station’s QCPU/LCPU and other station'
QCPU/LCPU/QnACPU can be performed from the external device
side.
2) Writing files
Programs such as execution programs can be modified (replaced) by
writing file data stored in the external device to the programmable
controller CPU as needed.
(c) Remote control of the programmable controller CPU
The programmable controller CPU can be remotely controlled from the
external device by performing remote RUN/STOP/PAUSE/LATCH
CLEAR/RESET operations.
1 OVERVIEW
1 - 3 1 - 3
(2) In a system using -Link IE Controller Network, CC-Link IE Field Network,
MELSECNET/H, MELSECNET/10, and Ethernet, an external device can access
programmable controller CPUs of other stations over the respective network.
1 OVERVIEW
(3) The C24 is equipped with the programmable controller CPU monitoring function.
By using this function, the programmable controller CPU status and data in the
device memory can be sent to an external device at constant intervals, upon the
occurrence of a mechanical error, or when certain conditions are satisfied.
This helps reduce the number of data read processes performed by the external
device.
The E71 also has the programmable controller CPU monitoring function that
uses e-mail transmission.
(Refer to the User's Manual (Application).)
POINT
To check what functions can be performed by external devices when
communicating data through the MC protocol, refer to the "Commands and function
list" reference sections in Chapters 3 to 6.
1 - 4 1 - 4
2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL
2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION
PROTOCOL
This chapter explains the data communication using the MC protocol when an external
device reads data from and writes data to a programmable controller CPU using the
C24/E71.
2.1 Types and Applications of Data Communication Frames
This section provides information about the types and applications of frames (data
communication messages) used by the external device to access the programmable
controller CPU using the MC protocol.
When the external device accesses the programmable controller via the C24/E71, the data
communication is performed by transmission/reception of command messages (access
requests) and response messages (responses) of one of the following frames listed below.
Choose the frame to be used by considering the accessible range of each frame
Target module Available communication frame Code of communication data Control procedure reference section
QnA compatible 3C frame Formats 1 to 4 ASCII code
C24
E71
QnA compatible 4C frame Format 5 Binary code
QnA compatible 2C frame Chapter 4
A compatible 1C frame
4E frame
QnA compatible 3E frame
A compatible 1E frame
shown in Section 2.2.
Chapter 3
Formats 1 to 4 ASCII code
ASCII code or binary code
Chapter 5
Chapter 3
Chapter 6
(1) QnA compatible 3C, QnA compatible 4C and QnA compatible 3E
frames
(a) These frames are mainly used to access all devices and files of the
Q/L/QnACPU from the external device.
(b) These frames enable access to A series programmable controller devices
also through CC- Link IE Controller Network, CC-Link IE Field Network,
MELSECNET/H, MELSECNET/10, and Ethernet. (Refer to Section 2.2 (1))
(2) 4E frame
(a) These frames are mainly used to access all devices and files of the Q/LCPU
from the external devices.
(b) These frames enable access to A/QnA series programmable controller
devices also through CC- Link IE Controller Network, CC-Link IE Field
Network, MELSECNET/H, MELSECNET/10, and Ethernet. (Refer to
Section 2.2 (2))
(3) QnA compatible 2C frame
(a) This frame can access the device memory of QCPU/LCPU stations on which
the C24 is loaded and Q/L/QnACPU stations linked by multidrop connection.
(b) The message format is simplified compared to the QnA compatible
3E/3C/4C frames.
(c) Since smaller amounts of transmission data are used, the messages are
easier to be processed by the external device and the transmission times of
the messages are shortened.
2
2 - 1 2 - 1
2
(4) A compatible 1C and A compatible 1E frames
(a) These frames have the same message structure as when accessing the
programmable controller CPU using an A series computer link module or
Ethernet interface module.
(b) By utilizing the software for data communication on the external device that
has been created for the A series programmable controllers, Q/L/QnACPUs
linked by multidrop connection or network connection, and programmable
controller CPUs other than Q/L/QnACPU can be accessed using the same
frame.
With respect to the Q/L/QnACPUs, only those devices with the same
names as those existing in the AnCPUs, AnNCPUs, AnACPUs and
AnUCPUs can be accessed within the AnACPU device range.
• When using the C24 : Refer to Section 5.2.1(2)
• When using the E71 : Refer to Section 6.3.1(2)
Devices that have been newly added to Q/L/QnACPUs cannot be accessed.
(c) To access a Universal model QCPU, the serial No. (first five digits) of the
module must be 10102 or later.
If the serial No. (first five digits) is 10101 or earlier, make access using the
QnA compatible 2C/3C/4C frame, QnA compatible 3E frame, or 4E frame.
2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL
REMARKS
(1) The following explains how to read the data communication frame names
when performing data communication using the MC protocol.
A data communication frame name indicates a relevant programmable
controller CPU series to show command compatibility with conventional
modules, a frame designation of the corresponding conventional module, and
the target module.
xxx compatible n m frame
a) b) c)
(Examples: QnA compatible 3C frame, QnA compatible 3E frame)
(a) Relevant programmable controller CPU series, showing command
compatibility with conventional modules
A : A series programmable controller CPU
QnA : QnA series programmable controller CPU
(b) Frames of the corresponding conventional modules
1 : Corresponds to the communication frames of commands supported
by A series computer link modules and Ethernet interface modules.
2 : Corresponds to the QnA simplified frames supported by QnA
series serial communication modules.
3 : Corresponds to the QnA frames supported by QnA series serial
communication modules and the communication frames supported
by QnA series Ethernet interface modules.
4 : Corresponds to the QnA extension frames supported by QnA
series serial communication modules.
(c) Modules described in this manual with which data communication can be
performed using the applicable frames.
C : C24
E : E71
2 - 2 2 - 2
2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL
(2) When accessing via the C24
The external device accesses the programmable controller CPU using frames
with a format number selected in the "Communication protocol setting" in the
switch settings using the programming tool.
When any of Formats 1 to 4 is selected, access is enabled using each of the
four types of frames shown above and data communication is performed by
the transmission/reception of command messages and response messages
in the selected format.
(3) When accessing via the E71
The external device can access using any of the two types of frames shown
above; it accesses the programmable controller CPU by sending/receiving
command messages and response messages using frames corresponding to
the setting selected in the operation settings using the programming tool.
(4) Time required for communication in binary code is shortened because the
amount of the communication data is approximately a half of what is required
for communication in ASCII code data.
2.2 Accessible Range of Each Data Communication Frames
In a communication using the MC protocol, access to programmable controller stations
on which the C24/E71 is not loaded is possible via CC-Link IE Controller Network,
CC-Link IE Field Network, MELSECNET/H, MELSECNET/10 and Ethernet.
This section explains the range of programmable controllers of other stations that can
be accessed from an external communication device when the access destination
programmable controller is not directly connected by a serial communication line or
Ethernet.
Target module Frame used
QnA compatible 3C frame Formats 1 to 4
C24
E71
QnA compatible 4C frame
QnA compatible 2C frame
A compatible 1C frame
4E frame
QnA compatible 3E frame
A compatible 1E frame
Formats 1 to 4
Format 5
Formats 1 to 4
: Accessible, : Not accessible
Range of accessible stations
1) 2) 3) 4)
2 - 3 2 - 3
(1) When using the C24
1 The network represents CC-Link IE Controller Network,
CC-Link IE Field Network, MELSECNET/H, MELSECNET/10, or Ethernet.
(2) When using the E71
2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL
1 The network represents CC-Link IE Controller Network, CC-Link IE Field
Network, MELSECNET/H, MELSECNET/10, or Ethernet.
POINT
By setting the routing parameter (communication path) in advance, access to
programmable controllers on the following network systems is also available.
• CC-Link IE Controller Network
• CC-Link IE Field Network
• MELSECNET/H
• MELSECNET/10
• Ethernet
Accessible range is up to the eighth network (number of relay stations: 7).
2 - 4 2 - 4
Loading...
+ 502 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.