Professional Documents
Culture Documents
Interface Module
Q Corresponding Ethernet
Interface Module
User's Manual
(Basic)
Q Corresponding Ethernet Interface Module User's Manual (Basic)
MODEL
QJ71E71-U-KI-E
MODEL
CODE
13JL88
SH(NA)-080009-F(0210)MEE
When exported from Japan, this manual does not require application to the
Ministry of Economy, Trade and Industry for service transaction permission.
Mitsubishi Programmable
Logic Controller
QJ71E71-100
QJ71E71-B5
QJ71E71-B2
BL
SAFETY PRECAUTIONS
(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 this product. For the safety instructions of the
programmable controller system, please read the user's manual of the CPU module to use.
In this manual, the safety instructions are ranked as "DANGER" and "CAUTION".
DANGER
! CAUTION
Note that the ! CAUTION level may lead to a serious consequence according to the circumstances.
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.
[Design Precautions]
!
DANGER
For details on the operating status of each station when a communication abnormality occurs in
the data link, see the manual for each data link. Erroneous outputs and malfunctions may lead
to accidents.
Not doing so can cause an accident due to false output or malfunction.
To prevent malfunctions of the PLC system that may be caused by illegal e-mails from the
outside, take a proper countermeasure (such as virus detection) so that illegal e-mails are not
received by the mail server of this module.
If it is necessary to ensure the security of the PLC system against unauthorized access from
external devices via the Internet, appropriate measures must be incorporated by the user.
Then controlling a running PLC (modifying data) by connecting peripheral devices to the CPU
module or connecting a personal computer to the intelligent function module, configure an
interlocking circuit in a sequence program so that the safety of the overall system is always
maintained. Also, before performing other control operations (program modifications and
operation status modifications (status control)) on the running PLC, be sure to read the manual
carefully and thoroughly confirm the safety.
Especially in the above mentioned control operations that are performed from an external device
to a remote PLC, any problems on the PLC side may not be dealt with promptly due to abnormal
data communication. In addition to configuring an interlocking circuit in a sequence program,
determine how the system handles data communication abnormalities, etc. between the
opposite devices and the PLC CPU.
A-1
A-1
[Design Precautions]
!
DANGER
Do not write any data in the "system area" of the buffer memory of the intelligent function
module. Also, do not output (turn on) the "use prohibited" signal, which is one of the output
signals from the PLC CPU to the intelligent function module. If data is written to the "system
area" or the "use prohibited" signal is output, there is a risk that the PLC system may
malfunction.
CAUTION
Do not bundle the control wires and the communication cables with the main circuit and the
power wires, and do not install them close to each other. They should be installed at least 100
mm (3.94 in.) away from each other. Failure to do so may generate noise that may cause
malfunctions.
When the status control (remote RUN/STOP, etc) of the PLC CPU is performed from the
external device, select the "Always wait for OPEN" parameter set by an user in advance. (Select
with the initial timing setting in the operational setting.) If "Do not wait for OPEN" is selected the
communication line at remote STOP is closed. The communication line cannot be reopened on
the PLC CPU side after that, and the remote RUN from the external device cannot start either.
[Installation Precautions]
!
DANGER
Use the PLC in the operating environment that meets the general specifications described in the
user's manual of the CPU Module to use. Using the PLC in any other operating environments
may cause electric shocks, fires or malfunctions, or may damage or degrade the module.
While pressing the installation lever located at the bottom of module, insert the module fixing tab
into the fixing hole in the base unit until it stops. Then, securely mount the module with the fixing
hole as a supporting point.
If the module is not installed properly, it may cause the module to malfunction, fail or fall off.
Secure the module with screws especially when it is used in an environment where constant
vibrations may occur.
Be sure to tighten the screws using the specified torque. If the screws are loose, it may cause
the module to short-circuit, malfunction or fall off. If the screws are tightened excessively, it may
damage the screws and cause the module to short-circuit, malfunction or fall off.
Before mounting or dismounting the module, make sure to shut off all phases of the external
power supply. Failure to do so may damage the module.
Do not directly touch the conducting parts and electronic parts of the module.
This may cause the module to malfunction or fail.
A-2
A-2
[Wiring Instructions]
!
CAUTION
A-3
A-3
CAUTION
Never disassemble or modify the module. This may cause breakdowns, malfunctions, injuries or
fire.
Before mounting or dismounting the module, make sure to shut off all phases of the external
power supply. Failure to do so may cause the module to breakdown or malfunction.
Do not mount/remove the module onto/from base unit more than 50 times (IEC61131-2compliant), after the first use of the product.
Failure to do so may cause the module to malfunction due to poor contact of connector.
Do not touch the terminals while the power is on. Doing so may cause electric shocks or
malfunctions.
Before cleaning the module or retightening the terminal screws and the module mounting
screws, make sure to shut off all phases of the external power supply. Failure to do so may
cause the module to breakdown or malfunction. If the screws are loose, it may cause the
module to short-circuit, malfunction or fall off. If the screws are tightened excessively, it may
damage the screws and cause the module to short circuit, malfunction or fall off.
Always make sure to touch the grounded metal to discharge the electricity charged in the body,
etc., before touching the module.
Failure to do so may cause a failure or malfunctions of the module.
[Operating Precautions]
!
CAUTION
Please read the user's manual carefully and confirm the safety thoroughly before proceeding to
perform control operations of the PLC (especially, modifications of data, programs and operation
status (status control)) that is running by connecting personal computers, etc. to the intelligent
function module.
Incorrect modifications of data, programs and operating status may cause system malfunctions,
damages to the machines, or accidents.
CAUTION
A-4
A-4
REVISIONS
The manual number is given on the bottom left of the back cover.
Print Date
Manual Number
Revision
Jun., 2001
A-5
A-5
The manual number is given on the bottom left of the back cover.
Print Date
Manual Number
Jun., 2001
SH (NA)-080009-C
Revision
Addition
Section 1.2 (5) (6), Section 2.2 (1), 2.6, Section 5.4.2, Section 11.3 (6),
11.3.2 (error code 1FH), 11.3.3 (error codes C0F7H and C300H),
Appendix 4, Appendix 7, Appendix 9, Appendix 11
Oct., 2001
SH (NA)-080009-D
Correction
Section 1.2 (4) (7), 1.3, 1.4 (1), Section 2.2 (POINT), 2.5 (1), 2.7 (1),
Section 3.1, 3.5, 3.8, Section 4.1.1 (2), 4.3, 4.4.1 (POINT), 4.7 (5),
Section 5.2.2 (REMARK), 5.2.3, 5.4.2, 5.5 (Table), 5.6.1, 5.6.2, 5.6.3,
Section 10.1, Section 11.2.2 (2), 11.2.4, 11.3.3, Appendix 1.1, Appendix
8.2, Appendix 9
Addition
Section 10.9
Correction
About the Generic Terms and Abbreviations, Section 1.2 (7), Section 2.1
(1), 2.7 (1), Section 3.7 (Table), Section 5.1 (Figure), 5.2.2 (REMARK),
5.2.3, Section 7.5.1, Section 10.9, Section 11.3.1 (Table), 11.3.3
(REMARK), 11.4.2 (Figure), Appendix 1.1 (2) (Table), Appendix 2.2 (2)
(a), Appendix 8
Addition
Section 11.3.3 (error code C1BAH), 11.4
Apr., 2003
SH (NA)-080009-F
2, Appendix 4 (4)
Additional model
QJ71E71-B5
Deleted model
QJ71E71
Correction
SAFETY PRECAUTIONS, About the Generic Terms and Abbreviations,
Section 1.2 (1) (5) (6), 1.3, 1.4 (1), Section 2.1, 2.2, 2.5, 2.6, 2.7, Section
3.1, 3.4, 3.8, Section 4.1, 4.3, 4.4, 4.5, 4.6, Section 5.2.2 (REMARK) (5),
5.2.3 (REMARK), 5.3, 5.4.2 (1)(c), 5.4.3, 5.5 (6), 5.6 (2) (POINT), 5.9.1,
5.9.6 (3) (6), Section 6.2, Section 10.8, 10.9, Section 11.1.1, 11.2.2 (2),
11.3, 11.4.5 (Figure), Appendix 1.1, Appendix 2, Appendix 4, Appendix 7,
Appendix 10, Appendix 11
Addition
Section 11.2.1 (POINT), 11.3.3 (error code C0B2H, C0E0H to C0EFH,
C171H to C17FH), Appendix 9
Jul., 2003
SH (NA)-080009-G
Correction
The Manual's Usage and Structure, Section 1.4 (1), Section 2.2 (1), 2.7,
Section 3.8, Section 4.7, Section 5.2.2 (REMARK), 5.5 (POINT), 5.6.1,
5.6.2, Section 7.5.2, Section 8.6.2, Section 11.4, Appendix 2, Appendix
8.1, Appendix 11, Appendix 12
A-6
A-6
The manual number is given on the bottom left of the back cover.
Print Date
Manual Number
Sep., 2003
SH (NA)-080009-H
Revision
Jun., 2004
Section 1.4 (1), Section 3.8, Section 5.2.3, Appendix 2.1, Appendix 8
SH (NA)-080009-I Addition of the description of function version D
Correction
Correction
About the Generic Terms and Abbreviations, Section 1.1 (7), Section 1.3,
Chapter 2 (entire), Section 3.6, Section 3.8, Section 4.5, Section 4.6,
Section 5.3, Section 5.5, Section 5.6 (2) (POINT), Section 5.8 (POINT),
Section 6.1.4, Section 10.9, Appendix 1, Appendix 4, Appendix 11,
Appendix 12
Addition
Section 1.1 (9), Section 5.10, Section 5.11, Section 11.3.3,
Section 11.4.7, Appendix 8.2
A-7
A-7
INTRODUCTION
Thank you for purchasing the MELSEC-Q series PLC.
Before using the equipment, please read this manual carefully to develop full familiarity with the functions
and performance of the Q series PLC you have purchased, so as to ensure correct use.
Please forward a copy of this manual to the end user.
CONTENTS (This manual)
SAFETY PRECAUTIONS..............................................................................................................................A- 1
REVISIONS ....................................................................................................................................................A- 5
CONTENTS....................................................................................................................................................A- 8
About Manuals ...............................................................................................................................................A-16
Conformation to the EMC Directive and Low Voltage Instruction ................................................................A-16
The Manual's Usage and Structure ...............................................................................................................A-17
About the Generic Terms and Abbreviations ................................................................................................A-21
Product Configuration ....................................................................................................................................A-22
1 OVERVIEW
1.1
1.2
1.3
1.4
2 SYSTEM CONFIGURATIONS
2.1
2.2
2.3
2.4
2.5
2.6
2.7
1- 1 to 1-15
2- 1 to 2-19
Applicable Systems................................................................................................................................. 2- 1
Devices Required for Network Configuration......................................................................................... 2- 3
For Use in Multiple CPU System ............................................................................................................ 2- 8
For Use with Q00J/Q00/Q01CPU .......................................................................................................... 2-10
For Use with Q12PRH/Q25PRHCPU..................................................................................................... 2-11
For Use at MELSECNET/H Remote I/O Station.................................................................................... 2-14
Checking the Function Version and Serial No. ...................................................................................... 2-18
3 SPECIFICATIONS
3- 1 to 3-27
A-8
A-8
4- 1 to 4-25
5- 1 to 5-111
A-9
A-9
6- 1 to 6- 5
6.1 Data Communication Function ............................................................................................................... 66.1.1 Accessing the PLC CPUs using the MC protocol ........................................................................... 66.1.2 Message format and control procedure for data communication ................................................... 66.1.3 PLC CPU setting for performing data communication.................................................................... 66.1.4 Compatibility with multiple CPU system or redundant system ....................................................... 66.1.5 Support for the QCPU remote password function .......................................................................... 66.2 Utilizing the MX Component ................................................................................................................... 67 FIXED BUFFER COMMUNICATION
(WITH THE PROCEDURE EXIST CONTROL METHOD)
1
1
2
3
4
4
5
7- 1 to 7-22
8- 1 to 8-21
A - 10
A - 10
9- 1 to 9-16
10- 1 to 10-26
11 TROUBLESHOOTING
11- 1 to 11-63
A - 11
A - 11
App- 1 to App-65
A - 12
Index- 1 to Index- 3
A - 12
A - 13
(Related Manual-2) Q Corresponding Ethernet Interface Module User's Manual (Web function)
SH-080180-B
1 OVERVIEW
1.1 Overview
2 SYSTEM CONFIGURATIONS
2.1 System Configurations
2.2 Precautions for Using the Web Function
3 OPERATING PROCEDURE
3.1 General Procedure up to Communication
Using the Web Function
3.2 How to Obtain and Set Up the
Communication Library and the Sample
Screen
4 VERIFYING THE OPERATION OF THE WEB
FUNCTION USING A SAMPLE SCREEN
4.1 Web Function Items Available on the Sample
Screen
4.2 Operating Procedure
4.3 Explanation of the Sample Screen
4.4 Example of Data Communication on the
Sample Screen
4.5 Configurations of Files on the Sample Screen
5 EXAMPLE OF CREATING A FILE FOR
ACCESSING THE PLC
6 COMMUNICATION LIBRARY FUNCTIONS
A - 14
A - 14
A - 15
A - 15
About Manuals
The following manuals are also related to this product.
In necessary, order them by quoting the details in the tables below.
Related Manuals
Manual number
Manual name
(Model code)
SH-080010
the communication function via MELSECNET/H, MELSECNET/10 as well as the communication function
(13JL89)
using data link instructions, and how to use file transfer (FTP server), etc.
(sold separately)
SH-080180
(sold separately)
(13JR40)
SH-080008
(13JF89)
(sold separately)
A - 16
A - 16
(2) To find out about the processing required prior to starting the
operation of the Ethernet module
(a) To find out about the startup procedure
Section 4.2 describes an outline of the procedures prior to starting the
operation of the Ethernet module.
(b) To find out about the connection to the Ethernet network system.
Section 2.2 describes the devices required to connect to the Ethernet
network system.
Section 4.4 describes the connection methods for each type of interface.
(c) To find out about the parameter settings required prior to starting the
operation of the Ethernet module
Section 4.5 describes the types of the parameter setting screens for GX
Developer in order to use the Ethernet module.
Section 3.6 describes the parameter settings required for each function to
be used.
Confirm the required parameters, set them according to the relevant
section providing detailed explanation, and save the setting values in the
PLC CPU to which the Ethernet module is installed.
(d) To find out how to check for Ethernet module failures
Section 4.8 describes the self-diagnostic test for the Ethernet module.
A - 17
A - 17
(e) To find out how to check for connection errors with the external devices
Sections 5.4.1 to 5.4.3 describe how to check for connection errors by
performing the PING test and loop back test through GX Developer.
Section 5.4.4 describes how to check for connection errors using the
"PING" command.
Section 5.4.5 describes how to check for connection errors by performing
the loopback test through MC protocol-based communication.
For details of the loopback test commands through MC protocol, refer to the
Q Corresponding MELSEC Communication Protocol Reference Manual.
(3) To find out about the connection between the Ethernet module and
the external devices
(a) To find out about the communication procedures
Section 5.1 describes an outline of the communication procedures
(b) To find out about the connections with the external devices
Section 5.6 describes the connections (open and close processing) for
each of the communication method (TCP/IP, UDP/IP) and the open method
(Active, Passive), including programming procedures.
(4) To find out about the details of the data communication functions
(a) To find out about the communication functions
Section 1.2 describes an overview of the Ethernet module communication
functions and related section numbers and manual names that can be
referenced for more detailed explanations.
Special functions of the Ethernet module are described in the User's
Manual (Application).
Web functions of the Ethernet module are described in the User's Manual
(Web function).
A - 18
(6) To find out how to check for error occurrences and take corrective
actions
(a) To find out about the contents of the error codes
Chapter 11 describes troubleshooting, how to check for errors, and
contents and reference manual of error codes.
(b) To find out about the storage area of the error codes in the buffer memory of
the Ethernet module
Section 11.3 describes the error code storage areas in the buffer memory.
(7) To learn about functions that have been added to function version
B and later
Section 1.3 provides the added function list and detailed explanation manual.
Appendix 1.1 provides the comparison of the Ethernet module functions.
A - 19
A - 19
3) Indicates storage
destination of setting
items and setting
vales. ( 1)
4) Shows the value of
the settings and
relevant section that
provides detailed
explanation.
Hb
The value in parentheses (address:
) indicates the buffer
memory address and the bit position of the Ethernet module that store a
setting value entered from GX Developer.
For details on the buffer memory, see Section 3.8, "List of Applications and
Assignments of the Buffer Memory."
A - 20
A - 20
Ethernet Address
Ethernet module
Ethernet network system
External device
GX Developer
MELSECNET/10
MELSECNET/H
Description
Generic term for AnNCPU, AnACPU, and AnUCPU
Generic term A2ACPU, A2ACPU-S1, A2ACPUP21/R21, A2ACPUP21/R21-S1,
A3ACPU, A3ACPUP21/R21
Generic term A1NCPU, A1NCPUP21/R21, A2NCPU, A2NCPU-S1,
A2NCPUP21/R21, A2NCPUP21/R21-S1, A3NCPU, A3NCPUP21/R21
Generic term for A2UCPU, A2UCPU-S1, A2ASCPU, A2ASCPU-S1, A3UCPU, and
A4UCPU
A machine-specific address that is also referred to as the MAC (Media Access Control)
address. This is used to identify the addresses of external devices over a network.
The Ethernet address of the Ethernet module can be verified on the MAC ADD
column of the rating plate.
Abbreviation for Model QJ71E71-100, QJ71E71-B5 and QJ71E71-B2 Ethernet
Interface Modules
(Described as the Ethernet module or E71 in the figures)
Abbreviation for 10BASE2,10BASE5, 10BASE-T and 100BASE-TX network systems
Generic term for personal computers, computers, workstations (WS) and Ethernet
module etc. that are connected by the Ethernet for data communication
Abbreviation for GX Developer (SWnD5C-GPPW-E). (n in the model name is 4 or greater)
Abbreviation for MELSECNET/10 Network system
MX Component
Network module
(N/W module)
Abbreviation for interface modules compatible with the MELSECNET/10 (H) network
system
OPS
Personal computer
QCPU
QCPU-A
QCPU station
QnACPU
Q/QnA
Reference Manual
Generic term for the partner product installed with redundant system-compatible
EZSocket (operator station).
The OPS can make communication using the Ethernet module's user connection for
OPS connection. (Refer to Section 5.5.)
Generic term for IBM PC/AT (or 100% compatible) personal computer
Generic term for Q00JCPU, Q00CPU, Q01CPU, Q02CPU, Q02HCPU,
Q mode Q06HCPU, Q12HCPU, Q25HCPU, Q12PHCPU, Q25PHCPU,
Q12PRHCPU, and Q25PRHCPU
A mode Generic term for for Q02CPU-A, Q02HCPU-A, and Q06HCPU-A
Abbreviation for the PLC with QCPU installed.
Generic term for Q2ACPU, Q2ACPU-S1, Q2ASCPU, Q2ASCPU-S1, Q2ASHCPU,
Q2ASHCPU-S1, Q3ACPU, Q4ACPU, and Q4ARCPU
Generic term for QCPU and QnACPU
Abbreviation for the Q Corresponding MELSEC Communication Protocol Reference
Manual
A - 21
A - 21
Product Configuration
The following lists the product configuration of the Ethernet interface modules.
Model
Item name
Quantity
QJ71E71-100
QJ71E71-B5
1
1
QJ71E71-B2
A - 22
A - 22
1 OVERVIEW
MELSEC-Q
1 OVERVIEW
This manual provides information on the specifications of the Ethernet interface
modules, models QJ71E71-100, QJ71E71-B5 and QJ71E71-B2 (hereinafter called the
Ethernet module), as well as the procedures prior to starting the operation, the control
procedures and data communication method for communicating with external devices,
maintenance, inspection, and troubleshooting.
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.
Internet service
Provider
Internet service
Provider
Ethernet
module
Router
CPU
Power supply
CPU
Ethernet
module
Power supply
Router
External device
Local station
External device
External device
Web server
GX Developer
1)
1-1
1 OVERVIEW
MELSEC-Q
Response
Ethernet
module
CPU
Power supply
Command
Local station
External device
REMARK
The communication functions using the MC protocol correspond to the
communication functions for reading/writing data from/to the PLC CPU that are
supported by the A/QnA series Ethernet modules (A1SJ71E71/A1SJ71QE71, etc.).
1-2
1-2
1 OVERVIEW
MELSEC-Q
(2) Communication using fixed buffers (Details are explained in
Chapters 7 and 8)
In the "communication using fixed buffers," a maximum of 1 k words of arbitrary
data can be sent or received among PLCs or between the PLC and the host
system.
An Ethernet module is provided with 16 fixed buffer data areas of 1 k word
storage space, and each is assigned as either a sending or receiving buffer for
an arbitrary device.
While the communication using the MC protocol is passive, the communication
using fixed buffers is an active protocol. Data can be sent from the PLC side to
the host system when errors occur in machine equipment or when some
conditions are satisfied. Furthermore, by using the data receiving function in an
interrupt program, retrieval of receive data to the PLC CPU may be expedited.
External device
Ethernet
module
Receive/
send
CPU
Power supply
Ethernet
module
CPU
Power supply
Receive/
send
Local station
External device
Ethernet
module
Read/write
CPU
Power supply
Read/write
Local station
External device
1-3
External device
1-3
1 OVERVIEW
MELSEC-Q
(4) Communication by e-mails (Details are explained in the Users
Manual (Application))
With sending/receiving e-mail, data can be sent to and received from an
external device at a remote location using e-mail via an Internet line.
(a)
(b)
E-mail
sending/
receiving
Internet service
provider
Internet service
provider
Router
Ethernet
module
CPU
Power supply
Router
Local station
External device
1-4
1-4
1 OVERVIEW
MELSEC-Q
(5) Communication by the Web function (Details are explained in the
Users Manual (Web function))
(a)
(b)
A Web server and a Web browser are required to use the Web function.
(Basic operating systems)
HTTP(MCprotocol)
HTTP
Ethernet
module
CPU
Power supply
With communication using the Web function, the system administrator can
monitor a Q Series CPU at a remote location via the Internet using a
commercially available Web browser.
Local station
External device
Web server
Web browser
HTML
ASP
Execution of
the ASP file
Display of
requests/results
Communication
library
1-5
1-5
1 OVERVIEW
MELSEC-Q
(6) Connecting GX Developer, GT SoftGOT and GOT (Details are
explained in the Operating Manuals for GX Developer and GT
SoftGOT, and Users Manual for GOT (Connection System
Manual))
Local station
Ethernet
module
CPU
Ethernet
module
Power supply
CPU
Power supply
(a)
External device
External device
Parameter setting
GX Developer
(b)
GX Developer
1-6
Ethernet
module
Monitor/test
CPU
Power supply
Program/monitor
External device
GOT
GT SoftGOT
1-6
1 OVERVIEW
MELSEC-Q
(c)
2)
[Connections used by the Ethernet module side when connecting a MELSOFT product or GOT]
(External device)
(Protocol used)
Ethernet
module
CPU
Power supply
One unit
Multiple units
One unit
or
1-7
1-7
1 OVERVIEW
MELSEC-Q
(7) Functions supporting Multiple CPU systems (Details are explained
in the Reference Manual.)
(a)
Ethernet module
control PLC
1)
FROM
instruction
3)
4)
Ethernet module
non-control PLCs
(b)
Non-control PLC
2)
Ethernet module
2)
Control PLC
FROM/TO
instruction
Dedicated
instruction
1-8
1) : PLC No.1
2) : PLC No.2
3) : PLC No.3
4) : PLC No.4
1 : Module controlled by
PLC No.1
2 : Module controlled by
PLC No.2
External device
Buffer memory
Data communication
X
Y
1-8
1 OVERVIEW
MELSEC-Q
3)
Non-control PLC
It is possible to access the control PLC and non-control PLCs using the
MC protocol and through GX Developer and file transfer (FTP server)
from the external device.
Also, communication using the fixed buffer and sending/receiving of email are possible with respect to the Ethernet module control PLC.
(Example)
When communicating by MC protocol
Ethernet module
Control PLC
03FFH
Data
External device
Command message
transmitted using
a QnA compatible
3E frame
Response message
Station to be accessed
1) 2) 3) 4)
MELSECNET/H
1'
MELSECNET/H
1) 2) 3) 4)
1) : PLC No.1
2) : PLC No.2
3) : PLC No.3
4) : PLC No.4
1 : Module used for routing, controlled
by PLC No.1
1' : Ethernet module controlled by
PLC No.1
2 : Module used for routing, controlled
by PLC No.2
The QnA compatible 3E frame should be used for access to noncontrol PLCs when communicating using the MC protocol.
Note, however, that the available functions differ, depending on the
QCPU to be accessed (whether it is a control PLC or a non-control
PLC).
See the Reference Manual for the available functions and
accessible range.
The modules used for routing are indicated the following when
accessing other stations:
MELSECNET/H, MELSECNET/10 network module
Q series C24
Ethernet module
If there is a module of function version A among the modules for
routing, it is possible to access the control PLC of module used for
routing only. In addition, it is possible to access other stations via a
module controlled by the same control PLC.
1-9
1-9
1 OVERVIEW
MELSEC-Q
(8) Remote password check function (Details are explained in Chapter
5 of the Reference Manual.)
(a)
(b)
All the remote password checks during data communication from the
external device to the local station or other stations are performed for the
remote passwords set in the local station QCPU.
(c)
When communicating data using the applicable connection for the remote
password check, data communication from external device can be
performed by the remote password unlocked (canceled) processing after
completing open processing.
1) When communicating using the MC protocol, fixed buffer or random
access buffer
Use the dedicated instruction for communication using the MC protocol
to unlock the remote password from the external device.
2) When accessing the PLC through GX Developer
Unlock the remote password through GX Developer at the start of
online operation.
3) When using the file transfer (FTP server) function
Use a dedicated FTP command to unlock the remote password from
the external device.
4) When using the Web function
Unlock the remote password in the dialog box displayed by a Web
browser while accessing the QCPU.
The user performs remote password lock processing prior to closing the
connection.
Accessing source
external device
Ethernet
Remote
password
QCPU
Remote
password
check
Ethernet
module
(Local station)
1 - 10
1 - 10
1 OVERVIEW
MELSEC-Q
(9) Redundant system support function (Detailed explanation: Chapter
5)
(a)
(b)
(c)
(d)
Personal
computer
Ethernet
(Communication with host)
AnACPU
(Normal station)
AnUCPU
(Normal station)
AnNCPU
(Normal station)
QnACPU
(Normal station)
Q4ARCPU
(Normal station/
control station)
Tracking cable
CC-Link
(I/O control, communication with outside)
Remote I/O
station
Remote
device station
Intelligent
device station
1 - 11
Remote I/O
station
Remote I/O
station
1 - 11
1 OVERVIEW
MELSEC-Q
Function
Simplifying access to
other stations
Access with the same
station number
1 - 12
Overview
Sends/receives data using IEEE802.3 frames.
When sending data, selects and sends either an Ethernet frame or IEEE802.3
frame.
When receiving data, receives either an Ethernet frame or IEEE802.3 frame.
Re-initial processing is performed in the following cases:
When updating the Ethernet address of the external device with which data
communication will be performed
When changing the data communication conditions.
Perform a target existence check by sending an ACK message to a remote device
and waiting to see whether or not a response is received.
Simultaneously connects up to 17 MELSOFT product (such as GX Developer) via
TCP/IP communication. This is achieved by using up to 16 user connections and one
dedicated system connection.
It is possible to access other stations without performing conversion setting (network
number, station number, and IP address) if they are accessed from a MELSOFT
product via the Ethernet module.
It is possible to use the same station number if two or more MELSOFT products are
started up from one personal computer in order to perform TCP/IP communication
and UDP/IP communication with one Ethernet module.
The Ethernet diagnostic function of GX Developer enables the following diagnoses:
Monitoring the module status and error status of the Ethernet module.
Confirming the completion of the Ethernet modules initial processing by performing
the PING test and loop back test.
Reference section
Section 5.2.3
Section 5.2.2,
REMARK (5)
Sections 1.2 (6) and 5.5
Applicable MELSOFT
product manual
Section 1.2 (6)
Manual of each
MELSOFT product
Sends a file in CSV format as attachment to e-mail from the Ethernet module.
Sends main text of up to 960 words from the Ethernet module.
The following encoding/decoding is supported.
Encode the Subject using 7 bits encoding and send it from the Ethernet module.
Decode and receive an e-mail encoded with Quoted Printable by the Ethernet
module.
Accesses the PLC from a personal computer at a remote location via an Internet,
using a commercially available Web browser.
In data communication via the connection set up using the parameters for the QCPU,
this function enables data communication after unlock processing from the external
device is completed normally for the remote password set in the QCPU.
Unlocks/locks the remote password of the QCPU. The unlock processing enables
access to the QCPU using various commands.
Unlock the remote password through the dialog box displayed by a Web browser
while accessing the QCPU.
Chapter 2 of Users
Manual (Application)
This function enables access to the control PLC/non-control PLC specified by the user GX Developer
Operating Manual
when performing data communication with a multiple CPU system.
Chapter 5 of Users
Manual (Application)
When an Ethernet module is mounted to the MELSECNET/H remote I/O station, access
to the local station (station on which the Ethernet module is mounted) or other stations is
enabled from the external device.
Section 2.6
1 - 12
1 OVERVIEW
MELSEC-Q
(2)
Function
1 - 13
Reference section
Section 5.11
Section 5.10
Chapter 4, Chapter 6 of
User's Manual
(Application)
1 - 13
1 OVERVIEW
MELSEC-Q
PLC
(Layers)
7
6
5
Buffer memory
System call
Commun- Commu- Commun- Commun- Communication
ication
ication
ication
nication
via
using
using
using
using
MELSEC
fixed
data
random
the MC
NET/H
buffers
link
protocol
access
instructi- MELSEC
buffers
NET/10
ons
Socket
TCP
UDP
IP
FTP
Commun- Communication
ication
by
by
Web
e-mails
SMTP
POP3
DNS
HTTP
Ethernet
module
TCP/UDP
ICMP
ARP
Ethernet
(100BASE-TX, 10BASE-T, 10BASE5,10BASE2)
IP
Application layer
Presentation layer
Session layer
ICMP
ARP
Ethernet
(100BASE-TX,10BASE-T,10BASE5,10BASE2)
Transport layer
Network layer
2
1
1 - 14
1 - 14
1 OVERVIEW
MELSEC-Q
(2) UDP (User Datagram Protocol)
This protocol may not guarantee data credibility and reliability in a communication
between a personal computer/work station and the PLC that are connected via
network. Thus, even if the data does not reach the target node, it will not be
retransmitted.
Because it is connectionless, high-speed transmission is possible.
A check sum is used to increase the reliability of the communication data.
However, when greater reliability must be maintained, a user application or the
TCP should be utilized.
1 - 15
1 - 15
2 SYSTEM CONFIGURATIONS
MELSEC-Q
2 SYSTEM CONFIGURATIONS
This section explains the system configurations that may be combined with the
Ethernet modules.
2
Ethernet modules can be used with the following systems:
Q00JCPU
Q00CPU
Q01CPU
CPU module
Q02CPU
Q02HCPU
Q06HCPU
Q12HCPU
Q25HCPU
Remark
(
Maximum 1
1)
Q12PHCPU
Q25PHCPU
Q12PRHCPU
Q25PRHCPU
QJ72LP25-25
Network module QJ72LP25GE
QJ72BR15
Maximum 4
1) (
4)
2-1
(a)
(b)
Network parameter
Network parameters must be written only to the control PLC of the Ethernet
module.
2-1
2 SYSTEM CONFIGURATIONS
MELSEC-Q
GX Developer
Q00J/Q00/Q01CPU
Q02/Q02H/Q06H/
Q12H/Q25HCPU
Q12PH/Q25PHCPU
Q12PRH/Q25PRHCPU
Version 7 or later
Version 8 or later
Version 4 or later
Version 6 or later
1 Refer to Section 2.7 for the GX Developer versions that support the
additional functions of the improved Ethernet module.
(b)
MX Component
Model
SWnD5C-ACT-E
Remark
Active X control library.
The n in the model name is 0 or greater. (
1)
2-2
2-2
2 SYSTEM CONFIGURATIONS
MELSEC-Q
External device
E
7
1
2-3
2-3
2 SYSTEM CONFIGURATIONS
MELSEC-Q
External device
E
7
1
POINT
During the high-speed communication (100 M bps) via 100BASE-TX connection, a
communication error may occur due to the effect of high frequency noise from
devices other than PLC in a given installation environment.
The following describes countermeasures on the QJ71E71-100 side to prevent the
effect of high frequency noise for construction of a network system.
(1) Wiring connection
Do not bundle the twisted pair cables with the main circuit and power wires,
and do not install them close to each other.
Make sure to place the twisted pair cables in a duct.
2-4
(2)
Communication method
Data communication with an external device is performed using TCP/IP
communication.
Increase the number of communication retries as necessary.
(3)
10 M bps communication
Communication is performed at a data transmission rate of 10 M bps by
changing the connection hub for the QJ71E71-100 to a hub capable of
handling 10 M bps.
2-4
2 SYSTEM CONFIGURATIONS
MELSEC-Q
Transceiver
AUI cable
External device
DC
Power
supply
E
7
1
1)
2)
3) Use a DC power supply (power supply for transceiver) that meets the
specifications of the transceiver and the AUI cable. (Refer to
REMARK.)
REMARK
The transceiver power characteristics are as follows:
Input terminal voltage: 12 V-6% to 15 V+5%
AUI cable direct resistance: 40 /km or less, maximum length 50 m (164 ft.)
Maximum current consumption: 500 mA or less
Thus, the applicable transceiver supply power will be from 13.28 V to 15.75 V.
Calculation of the transceiver supply power's voltage drop (V)
Voltage drop (V) = AUI cable direct current resistance (/m)
AUI cable length (m) 2 (both directions) transceiver
consumption current (A)
(Example)
2.0 (V) = 0.04 (/m) 50 (m) 2 0.5 (A)
In this case, the recommended transceiver supply power is more than 13.28 V.
-6%
13.28 (V) = 12 V (11.28 V) + 2.0 (V)
2-5
2-5
2 SYSTEM CONFIGURATIONS
MELSEC-Q
POINT
(1)
(2)
The following can be used as a countermeasure for errors due to highfrequency noise according to the installation environment.
Mount a ferrite core using the method shown in (3) below.
Increase the retry number when communicating by TCP/IP.
Use the following method to mount a ferrite core when connected to the
network by 10BASE5.
(3)
AUI cable
Transceiver
2-6
2-6
2 SYSTEM CONFIGURATIONS
MELSEC-Q
T-Type connector
External device
E
7
1
POINT
Consult a network specialist for required devices.
2-7
2-7
2 SYSTEM CONFIGURATIONS
MELSEC-Q
When making access from the external device to the non-control CPU of the
Ethernet module using any of the following functions, use the Ethernet module of
function version B or later.
When the Ethernet module of function version A is used, only the control CPU
can be accessed. (Access to the non-control CPU will result in an error.)
Communication using MC protocol
Communication using GX Developer
File transfer (FTP server) function
External device
Communication using MC protocol
Communication using GX Developer
File transfer (FTP server) function
Ethernet
Multiple CPU system
2-8
2-8
2 SYSTEM CONFIGURATIONS
(2)
MELSEC-Q
When the other station at the access destination is in a multiple CPU system and
access is to be made to the non-control CPU of the relayed module of the
accessed station, use the modules of function version B or later as the relayed
modules and QCPUs of the local station and all the relayed and accessed
stations. 1
(Example)
Other station access is enabled independently of whether the control CPUs
of the relayed modules are the same or different.
Local station
External device
1) 2) 3) 4) 1
Setting from
GX Developer
1'
MELSECNET/H
Relayed station
1) 2) 3) 4)
MELSECNET/H
Accessed station
1) : QCPU No. 1
2) : QCPU No. 2
3) : QCPU No. 3
4) : QCPU No. 4
1 : Relayed module controlled by QCPU No. 1
1' : Ethernet module controlled by QCPU No. 1
2 : Relayed module controlled by QCPU No. 2
Relayed module: MELSECNET/H network module
1) 2) 3) 4) 2
2-9
The targets of the relayed modules for other station access are as follows.
MELSECNET/H, MELSECNET/10 network modules
Q series C24
Ethernet module
2-9
2 SYSTEM CONFIGURATIONS
MELSEC-Q
Availability
( 1)
( 3)
( 3)
( 2)
( 3)
( 3)
: Unavailable
1 For the number of its processing time, refer to the Reference Manual.
The devices that can be accessed and its range are different according to
the frame used for data communication.
2 When the target station of the SREAD/SWRITE instruction is the
Q00J/Q00/Q01CPU, the read reporting device to the target station set to the
argument (D3) is ignored.
The operation of the SREAD/SWRITE instruction is the same as that of the
READ/WRITE instruction.
For the SREAD/SWRITE instruction, refer to Chapter 4 or Chapter 6 of the
User's Manual (Application).
3 Available for the Q00J/Q00/Q01CPU (function version B) or later.
To use the function, GX Developer Version 8 or later is required.
2 - 10
2 - 10
2 SYSTEM CONFIGURATIONS
MELSEC-Q
LAN card
Network No.
Station No.
IP address
Sub-net mask
:1
:3
: 10.97.14.3
: 255.255.255.0
Ethernet
Control system
Standby system
Tracking cable
QJ71E71-100 1)
Network No. : 1
Station No. : 1
IP address
: 10.97.14.1
Sub-net mask : 255.255.255.0
2 - 11
QJ71E71-100 2)
Network No. : 1
Station No. : 2
IP address
: 10.97.14.2
Sub-net mask : 255.255.255.0
2 - 11
2 SYSTEM CONFIGURATIONS
(b)
MELSEC-Q
LAN card 1)
Network No. : 1
Station No. : 3
IP address
: 10.97.14.3
Sub-net mask : 255.255.255.0
LAN card 2)
Network No. : 2
Station No. : 3
IP address
: 10.97.24.3
Sub-net mask : 255.255.255.0
External device
Ethernet
network No. 1
Ethernet
network No. 2
: Communication path 1
Standby system
Control system
Tracking cable
QJ71E71-100 1)
Network No. : 1
Station No. : 1
IP address
: 10.97.14.1
Sub-net mask : 255.255.255.0
Grouped
Grouped
QJ71E71-100 4)
Network No. : 2
Station No. : 2
IP address
: 10.97.24.2
Sub-net mask : 255.255.255.0
QJ71E71-100 3)
Network No. : 1
Station No. : 2
IP address
: 10.97.14.2
Sub-net mask : 255.255.255.0
QJ71E71-100 2)
Network No. : 2
Station No. : 1
IP address
: 10.97.24.1
Sub-net mask : 255.255.255.0
1
2
2 - 12
: Communication path 2
When using two LAN cards in the external device, use them at different
sub-net addresses to the set IP address using the sub-net mask.
Perform "Network module redundant group settings" on GX Developer.
(Refer to the QnPRHCPU User's Manual (Redundant System) for "Network
module redundant group settings ".)
The system switches when both of the grouped Ethernet modules become
faulty.
Make the redundant setting of GX Developer to set whether a system
switching request will be issued or not from the Ethernet module at
detection of a communication error or disconnection. (Refer to Section
5.11.3.)
2 - 12
2 SYSTEM CONFIGURATIONS
MELSEC-Q
Availability
: Unavailable
1 Refer to Section 5.11.5 for the precautions for using the functions on the
Q12PRH/Q25PRHCPU.
2 - 13
2 - 13
2 SYSTEM CONFIGURATIONS
MELSEC-Q
QJ72
QJ71
LP25
E71
-25
QJ71
LP21
-25
MELSECNET/H
Remote I/O network
External device
QJ72
LP25
-25
(Remote I/O station)
Sequence program
GX Developer parameter setting
Sequence program
GX Developer parameter setting
Availability
(See (3) (4))
(See (3) (4))
(
(Can be relayed)
(See (3))
: Available
: Unarailable
1 The following explains access made to the MELSECNET/H remote I/O station
using the MC protocol and other station access via the MELSECNET/H remote
I/O station.
(a) Perform communication using a QnA compatible 3E frame. (Communication
cannot be done with the A compatible 1E frame.)
2 - 14
2 - 14
2 SYSTEM CONFIGURATIONS
(b)
MELSEC-Q
The following functions are available for the MELSECNET/H remote I/O
station. For the QnA/A series compatible MELSECNET/10 remote I/O
station, only read/write of the intelligent function module buffer memory can
be performed.
Available function
Function
Read/write of intelligent
function module buffer memory
(c)
Device name
Device symbol
Device name
Device symbol
Special relay
SM
Link relay
Special register
SD
Data register
Input relay
Link register
Output relay
SB
Internal relay
SW
(d)
Other station access via the MELSECNET/H remote I/O station enables
access to the MELSECNET/H remote master station and access to the
MELSECNET/H remote I/O station.
1) In the following figure, access can be made from the external device to
the remote master station and to the MELSECNET/H remote I/O
station.
QJ71
LP21
-25
QJ72
station
LP25 QJ71
-3
-25 E71
Access allowed
Access prohibited
External device
MELSECNET/H
Remote I/O net
station
-1
QJ72
QJ71
LP25
E71
-25
2)
QJ72
station
QJ71 QJ71
(Remote I/O station)
LP25
-2
E71 E71
-25
2 This function is available for the MELSECNET/H remote I/O station of function
version D and later.
GX Developer Version 8.18U or later is required to use the function.
2 - 15
2 - 15
2 SYSTEM CONFIGURATIONS
MELSEC-Q
Setting
I/O assignment
Operational settings
Initial settings
Open settings
Remarks
Setting not
required
POINT
(1)
(2)
(3)
REMARK
It is not necessary to set the Intelligent function module switch settings with GX
Developers I/O assignment.
Each type of setting corresponding to the switch settings is performed in the above
mentioned Operational settings, Initial settings, and Open settings.
2 - 16
2 - 16
2 SYSTEM CONFIGURATIONS
MELSEC-Q
2 - 17
2)
(b)
(c)
2)
(d)
(e)
2)
2 - 17
2 SYSTEM CONFIGURATIONS
MELSEC-Q
QJ71E71-100
Re-initial
processing of
the Ethernet
module
Existence
check function
Checking by KeepAlive
Function version B or
later, whose first 5
digits of the serial No.
are 03102
Function version B or
later, whose first 5
digits of the serial No.
are 05051
Function version B or
later, whose first 5
digits of the serial No.
are 05051
Function version B or
later, whose first 5
digits of the serial No.
are 05051
Ethernet
diagnostic
function of GX
Developer
Simplifying access to
other stations
Access with the same
station number
Function version B or
later, whose first 5 digits of
the serial No. are 05051
When using
the e-mail
function
Function version B or
later, whose first 5
digits of the serial No.
are 05051
Function version B or
later, whose first 5 digits of
the serial No. are 05051
Version 8.05F or
later
Function version B or
later, whose first 5 digits of
the serial No. are 02122
Version 6.05F or
later
Function version B or
later, whose first 5 digits of
the serial No. are 05051
Monitoring of various
Ethernet module statuses
PING test/loopback test
via Ethernet board
PING test via CPU
Version 7 or later
Function version B or
later, whose first 5 digits of
the serial No. are 05051
Connection of up to 17 MELSOFT
products via TCP/IP communication
Simplifying
connection
with
MELSOFT
products
Function version B or
later, whose first 5 digits of
the serial No. are 03102
Function version B or
later, whose first 5 digits of
the serial No. are 03061
Function version B or
later, whose first 5 digits of
the serial No. are 03102
QJ71E71-B2
Function version
A or later, whose
first 5 digits of the
serial No. are
02092
Version 6 or later
Version 7 or later
Function version D or
later
Version 6 or later
Function version B or
later, whose first 5 digits of
the serial No. are 03102
Version 7 or later
Support for
encoding/decoding
Target station CPU type specification for
data link instructions
Function version B or
later, whose first 5
digits of the serial No.
are 03102
Function version D or
later
Function version B or
later, whose first 5 digits of
the serial No. are 03102
Function version D
or later
Function version B or
Function version
later, whose first 5 digits of
B or later
the serial No. are 03102
Function version B or
later, whose first 5 digits of
the serial No. are 05051
Function version
A or later, whose
first 5 digits of the
serial No. are
02092
Version 6 or later
: Unavailable
1 Change was made to the operation of the Ethernet module to be performed when the Active open request is
received again from the external device in the open completion status of TCP. (Refer to POINT in Section 5.6 (2).)
2 - 18
2 - 18
2 SYSTEM CONFIGURATIONS
MELSEC-Q
(2) Checking the function version and serial No. of the Q series PLC
(a)
Conformed standard
"System monitor"
2 - 19
2 - 19
3 SPECIFICATIONS
MELSEC-Q
3 SPECIFICATIONS
This section explains the Ethernet module performance specifications and
transmission specifications.
For more details on the general specifications, refer to the User's Manual for the QCPU
(Q mode).
Specification
Item
QJ71E71-100
100BASE-TX
10BASE-T
10BASE5
10BASE2
10 M bps
Full-duplex/Half-duplex
Half-duplex
Base band
1)
Cascade
connection
Maximum 4
stages
100 units/segment
30 units/segment
Fixed buffer
Attached file
6 k words 1
6 k words 1 ( 4)
Main text
960 words 1 (
QJ71E71-B2
100 M bps
Transmission method
Transmission
specifications
QJ71E71-B5
4)
0.50 A
0.50 A
(
0.60 A (
2)
External dimensions
98 (3.86 in.) (H) 27.4 (1.08 in.) (W) 90 (3.54 in.) (D) [mm]
Weight
3)
3)
3-1
3-1
3 SPECIFICATIONS
MELSEC-Q
Item
Specification
Attached file
Main text
Data size
6 k words x 1
960 words x 1
When sending: Sends either a file as attachment or main text (select one).
When receiving: Received a file as attachment.
MIME format
MIME
Version 1.0
Binary/ASCII/CSV can be selected.
File name: XXXX.bin (binary), XXXX.asc (ASCII), XXXX.csv (CSV)
(CSV: Comma Separated Value)
Subject
: Base64/7 bits
Main text
: 7 bits
Attached file : Base64
Subject
: (Does not decode)
Main text
: (Cannot be received)
Attached file : Base64/7 bits/8 bits/Quoted Printable
* If e-mail is sent from the external device to the PLC side, specify the encoding method (Base64/7 bits/
8 bits/Quoted Printable) of the attached file.
Encryption
Compression
No
No
REMARK
The following explains each of the transmission specification items.
[Connecting using the 10BASE2/10BASE5]
Segment length
Hub
Transciver
Node
Maxmum 100m(5m)
Terminator
Node
Node
Maxumum
node-to-node
distance
Node
Node
3-2
Maxmum
100m
Repeater
Segment length
Repeater
Segment length
Transmission
specifications
Transmission
and reception
data
E
7
1
3-2
3 SPECIFICATIONS
MELSEC-Q
ASCII code
Chapter 6
Reference chapter
Chapter 7
)
Chapter 8
Chapter 9
: Selectable
: Cannot be communicated
1 Communication is performed in binary code regardless of the setting in [Operational Settings] [Communication
data code] (see Section 4.7).
REMARK
When the following data communication functions are used, communication is
performed using the data code handled by each function, regardless of the setting of
the communication data code.
Sending/receiving e-mail
MELSECNET/H, MELSECNET/10 relay communication
Communication using data link instructions
File transfer (FTP server function)
Communication using the Web function
3-3
3-3
3 SPECIFICATIONS
MELSEC-Q
2)
PLC CPU
Binary code
Communication
data
storage
area
External
device
ASCII code
BIN/ASCII conversion
(2)
When communicating using ASCII code, 1-byte binary code data is automatically
converted into 2-byte ASCII code data and then transmitted.
(Example)
Binary code data
(3)
15 H
(One byte)
31 H , 35 H
"1", "5"
(Two bytes)
1234 H
(Two bytes)
31 H , 32 H , 33 H , 34 H
"1", "2", "3", "4"
(Four bytes)
The size of data that can be communicated between the Ethernet module and an
external device at a time is determined by the function used and the data code
(binary/ASCII) that is set by selecting [GX Developer] [Communication data
code].
The following shows the maximum sizes of communication data that can be sent
and received at a time with each data communication function.
Data communication function
Communication using MC protocol
Communication using fixed buffer
Procedure exist
No procedure
3-4
2046 words
1017 words (Binary code)
3-4
3 SPECIFICATIONS
MELSEC-Q
3.3 Relationship between the External Devices and Additional Functions for Each
Communication Function
This section explains with which external devices data communication can be
performed and which additional functions can be used for each function.
QJ71E71
Personal computer
QJ71E71
Function
External device
QJ71E71
QJ71E71
QJ71E71
Conventional model
Conventional model
QJ71E71
1)
: Cannot communicate
Additional function
Communication function
MELSECNET/H,
MELSECNET/10
relay
communication
Router relay
communication (router
relay
function)
Communication using
the MC
protocol
QnA
compatible
3E frame
A
compatible
1E frame
Communic- Procedure
ation using exist
the fixed
No
buffer
procedure
Communication using the
random access buffer
Sending/receiving e-mail
Existence
check of
external
device
(
2)
1)
1)
TCP/IP
UDP/IP
Communication using
data link instructions
File transfer
(FTP server function)
Communication using the
Web function
: Available
: Not available or this function does not correspond to any of the functions in the function column.
3-5
3 SPECIFICATIONS
MELSEC-Q
Communication using
the MC protocol
Communication using
the fixed buffer
Description
QnA
compatible 3E
frame
A compatible
1E frame
Procedure exist
No procedure
Reference section
Chapter 5
Reference Manual
Chapter 7
Chapter 8
Chapter 9
Sending/receiving e-mail
Chapter 2 of Users
Manual
(Application)
Chapter 4 of Users
Manual
(Application)
Chapter 5 of Users
Manual
(Application)
Users Manual
(Web Function)
Description
In a network system on which an Ethernet and a MELSECNET/H or
MELSECNET/10 coexist or in a network system that relays multiple
Ethernets, data communication is performed via multiple number of
such networks.
Performs data communication via a router or gateway. (The router
relay function is not a function by which the Ethernet module works as
a router.)
Checks whether or not the external device is working normally after a
connection is established (open processing).
Pairs and then opens a reception connection and a transmission
connection (for fixed buffer).
Enables communication after the station in which an Ethernet module
is mounted has been started. (Open/close processing by sequence
programs is not required.)
Prevents unauthorized access by a remote user to a QCPU.
Reference section
Chapter 3 of Users
Manual
(Application)
Section 5.3
Section 5.8
Section 5.9
Simultaneous broadcast
Section 8.5
3-6
3-6
3 SPECIFICATIONS
MELSEC-Q
Description
Reference section
Section 4.8.1
Hardware test
Section 4.8.2
When a data communication error occurs, this function stores the error
information (error log), including the message subheader and IP
address of the external device for a maximum of 16 pairs in the buffer
memory.
Chapter 11
3-7
3-7
3 SPECIFICATIONS
MELSEC-Q
Instruction name
Description
Reference section
OPEN
Opens a connection.
Section 10.8
connections
CLOSE
Closes a connection.
Section 10.5
For reinitialization
UINI
Section 10.9
Section 10.2
BUFRCV
For fixed buffer communication
BUFRCVS
BUFSND
ERRCLR
fixed buffer.
Clears the error (turns off the [COM. ERR]
LED, clears the error log).
MRECV
Receives e-mail.
MSEND
Sends e-mail.
READ
WRITE
SWRITE
ZNRD
reading/writing
device data
ERRRD
SREAD
For
PLC
communication
ZNWR
SEND
(instructions for
data link)
For sending/
receiving
messages
(arbitrary data)
RECV
RECVS
Reading/
writing clock
data, remote
RUN/STOP
3-8
Section 10.4
Section 10.6
Section 10.7
Section 6.2 of Users
Manual (Application)
Section 6.3 of Users
Manual (Application)
Section 6.4 of Users
Manual (Application)
Section 6.10 of Users
Manual (Application)
Section 6.12 of Users
Manual (Application)
Section 6.11 of Users
Manual (Application)
Section 6.13 of Users
Manual (Application)
Section 6.14 of Users
Manual (Application)
Section 6.9 of Users
Manual (Application)
Manual (Application)
Manual (Application)
Section 10.3
stations.
Manual (Application)
3-8
3 SPECIFICATIONS
MELSEC-Q
PLC parameter
I/O assignment
settings
Interrupt pointer
settings
Network parameters
Setting the number of
MNET/10H Ethernet
cards
Operational
settings
Description of setting
MC
Fixed
Random
Data
link
FTP
Automatic
notification
1)
Web
Section
4.5
Section
4.7
Initial settings
Open settings
Router relay
parameter
FTP parameters
E-mail settings
Send mail
address setting
News setting
Interrupt settings
Redundant setting
Group settings
Routing
parameters
Remote password
settings
Section
5.2
Chapter
2 of
Application
Section
5.5
Section
5.3
Application in the Reference Section column refers to the Users Manual (Application).
Chapter 3
of
Application
3-9
Section
7.3
Section
4.6
Reference
section
( 2)
Chapter
5 of
Application
Chapter 2
of
Application
Section
7.3
Section
5.11.3
Section
4.6
Chapter 3
of
Application
Section
5.9.5
: Set as needed
3-9
3 SPECIFICATIONS
MELSEC-Q
PLC CPU
Device
number
Signal name
X0
Y0
X1
Y1
X2
Y2
X3
Y3
X4
Y4
X5
Y5
X6
Y6
X7
Y7
X8
X9
XA
XB
XC
XD
XE
XF
3 - 10
Reference Device
section number
Y8
Y9
YA
YB
YC
YD
YE
YF
Ethernet module
Signal name
Reference
section
Connection No. 1
ON : At sending request or reception complete
confirmation signal
OFF:
Connection No. 2
ON : At sending request or reception complete
confirmation signal
OFF:
Connection No. 3
ON : At sending request or reception complete
confirmation signal
OFF:
Connection No. 4
ON : At sending request or reception complete
confirmation signal
OFF:
Connection No. 5
ON : At sending request or reception complete
confirmation signal
OFF:
Connection No. 6
ON : At sending request or reception complete
confirmation signal
OFF:
Connection No. 7
ON : At sending request or reception complete
confirmation signal
OFF:
Connection No. 8
ON : At sending request or reception complete
confirmation signal
OFF:
Connection No. 1
ON : Open request
OFF:
Connection No. 2
ON : Open request
OFF:
Connection No. 3
ON : Open request
OFF:
Connection No. 4
ON : Open request
OFF:
Connection No. 5
ON : Open request
OFF:
Connection No. 6
ON : Open request
OFF:
Connection No. 7
ON : Open request
OFF:
Connection No. 8
ON : Open request
OFF:
3 - 10
3 SPECIFICATIONS
MELSEC-Q
X11
X12
X13
X14
X15
X16
X17
X18
X19
X1A
X1B
X1C
PLC CPU
Signal name
Open completed for connection No. 1
ON : Open complete signal
OFF:
Open completed for connection No. 2
ON : Open complete signal
OFF:
Open completed for connection No. 3
ON : Open complete signal
OFF:
Open completed for connection No. 4
ON : Open complete signal
OFF:
Open completed for connection No. 5
ON : Open complete signal
OFF:
Open completed for connection No. 6
ON : Open complete signal
OFF:
Open completed for connection No. 7
ON : Open complete signal
OFF:
Open completed for connection No. 8
ON : Open complete signal
OFF:
Open abnormal detection signal
ON : Abnormal detection
OFF:
Initial normal completion signal
ON : Normal completion
OFF:
Initial abnormal completion signal
ON : Abnormal completion
OFF:
Use prohibited
COM.ERR LED lit confirmation
ON : Lit (See Section 11.1)
OFF: Off
X1D
X1E
Use prohibited
X1F
Signal name
Ethernet module
Reference
section
Y10
Y11
Y12
Y13
Use prohibited
Y14
Y15
Y16
Y17
Section
5.6
Y18
Use prohibited
Section
5.1
Y19
Section
5.1
Y1A
Section
11.1
Y1B
Section
11.1
Y1C
Use prohibited
Y1D
Y1E
Section
11.1
Y1F
Important
Among the input/output signals for the PLC CPU, do not output (ON) the signals
marked with "Use prohibited." If any of the "Use prohibited" signals is output, the
PLC system may malfunction.
POINT
3 - 11
(1)
The input/output signals shown in this section are used when the QnA series
Ethernet interface module programs are also used for the Q series Ethernet
module (see Section 2 in Appendix).
In the QCPU, the input/output signals for intelligent function modules are
turned on/off with dedicated instructions.
It is not necessary to turn on/off the signals by a sequence program, except
for those that are shown in the programming examples in each of function
explanation sections.
(2)
When the QnA series Ethernet interface module programs are also used for
the Q series Ethernet module, it is also recommended to replace the
instructions with the dedicated instructions shown in the corresponding
function explanation section of each manual for the Q series Ethernet module.
3 - 11
3 SPECIFICATIONS
MELSEC-Q
(b)
1)
2)
3)
System areas
The areas used by the Ethernet module
Important
Do not write data in the "system areas" of the buffer memory.
If data is written to any of the system areas, the PLC system may not be operated
properly.
Some of the user areas contain partially system areas. Care must be taken when
reading/writing to the buffer memory.
POINT
3 - 12
(1)
(2)
When the QnA series Ethernet module programs are used for the Q series
Ethernet module, it is also recommended to replace the instructions with the
dedicated instructions shown in the corresponding function explanation
section of each manual for the Q series Ethernet module.
3 - 12
3 SPECIFICATIONS
MELSEC-Q
Application
Name
0 to 1
(0 to 1H)
2 to 3
(2 to 3H)
System area
Special function settings
Router relay function (b5, b4)
00: Do not use (default)
01: Use
Conversion system setting for MELSECNET/H, MELSECNET/10
relay function (b7, b6)
00: Automatic response system (default)
01: IP address computation system
10: Table exchange system
11: Use-together system
FTP function setting (b9, b8)
00: Do not use
01: Use (default)
4
(4H)
Initial value
(Hexadecimal)
C00001FEH
GX Developer
setting
applicability
1
(
)
Reference
section
2
(
)
Section 4.7
Section 5.3
Chapter 3 of
Application
0100H
Chapter 5 of
Application
System area
Initial processing
parameter setting
area
3CH (60)
14H (20)
13
(DH)
14H (20)
14
(EH)
28H (40)
AH (10)
16
(10H)
3CH (60)
17
(11H)
18
(12H)
14H (20)
19
(13H)
3H (3)
12
(CH)
15
(FH)
20
(14H)
21 to 30
(15 to 1EH)
Monitoring timer
Section 5.2
4B0H (1200)
1388H
Section 5.8
System area
: Setting prohibited
2 "Application" in the reference section column refers to the Users Manual (Application).
3 - 13
3 - 13
3 SPECIFICATIONS
MELSEC-Q
30
(1EH)
31
(1FH)
Application
Name
TCP Maximum
Segment
Transmission
setting area
32
(20H)
Communication Connection
parameter setting usage setting
area
area
Connection No. 1
Usage of fixed buffer (b0)
0: For sending or fixed buffer communication
is not executed
1: For receiving
Destination existence confirmation (b1)
0: No confirm
1: Confirm
Pairing open (b7)
0: No pairs
1: Pairs
Communication method (protocol) (b8)
0: TCP/IP
1: UDP/IP
Fixed buffer communication (b9)
0: Procedure exist
1: No procedure
Open system (b15, b14)
00: Active open or UDP/IP
10: Unpassive open
11: Fullpassive open
Bits other than above are reserved for system use.
Initial value
(Hexadecimal)
GX Developer
setting
applicability
Reference
section
8000H
Section
5.2.3
0H
0H
Section 5.5
33
(21H)
Connection No. 2
(bit configuration is the same as connection No.1)
34
(22H)
Connection No.3
(bit configuration is the same as connection No.1)
35
(23H)
Connection No.4
(bit configuration is the same as connection No.1)
3 - 14
3 - 14
3 SPECIFICATIONS
MELSEC-Q
Application
GX Developer
setting
applicability
Initial value
(Hexadecimal)
Name
Reference
section
36
(24H)
Connection No.5
(bit configuration is the same as connection No.1)
37
(25H)
Connection No.6
(bit configuration is the same as connection No.1)
38
(26H)
Connection No.7
(bit configuration is the same as connection No.1)
39
(27H)
Connection No.8
(bit configuration is the same as connection No.1)
40
(28H)
41 to 42
(29 to 2AH)
Connection
No. 1
43
(2BH)
44 to 46
(2C to 2EH)
47 to 53
(2F to 35H)
Communication
parameters
setting area
Communication
address setting
area
0H
Section 5.5
Destination IP address
0H
Section 5.5
0H
Section 5.5
FFFFFFFFFFFFH
Connection
No. 2
54 to 60
(36 to 3CH)
Connection
No. 3
61 to 67
(3D to 43H)
Connection
No. 4
68 to 74
(44 to 4AH)
Connection
No. 5
75 to 81
(4B to 51H)
Connection
No. 6
82 to 88
(52 to 58H)
Connection
No. 7
89 to 95
(59 to 5FH)
Connection
No. 8
96 to 102
(60 to 66H)
System area
103 to 104
(67 to 68H)
System area
105
(69H)
106 to 107
(6A to 6BH)
108 to 110
(6C to 6EH)
111 to 115
(6F to 73H)
116
(74H)
Communication
status storage
area
0H
0H
0H
Section 11.3
System area
Automatic open UDP port number
0H
117
(75H)
System area
118
(76H)
0H
119
(77H)
0H
3 - 15
3 - 15
3 SPECIFICATIONS
MELSEC-Q
200
(C8H)
201
(C9H)
202
(CAH)
Application
Connection
No. 1
Connection
information area
Communication
status storage
area
Initial value
(Hexadecimal)
Name
GX Developer
setting
applicability
Reference
section
0H
Destination IP address
0H
0H
0H
Section 11.3
0H
Section 11.3
0H
Section 11.3
Fixed buffer
communication
time
Maximum value
0H
Minimum value
0H
Current value
0H
Connection
(Same as connection No. 1)
No. 2
Connection
(Same as connection No. 1)
No. 3
Connection
(Same as connection No. 1)
No. 4
Connection
(Same as connection No. 1)
No. 5
Connection
(Same as connection No. 1)
No. 6
Connection
(Same as connection No. 1)
No. 7
Connection
(Same as connection No. 1)
No. 8
LED on/off status
(Stores the on/off status of the LEDs on the front of
the Ethernet module)
[INIT.] LED (b0)
0: off
1: on (initial processing completed)
[OPEN] LED (b1)
0: off
1: on (connection open processing completed)
0H
[ERR.] LED (b3)
0: off
1: on (setting error)
[COM.ERR.] LED (b4)
0: off
1: on (communication error)
Bits other than above are reserved for system use.
Area for module
status
Hub connection status area
Communication mode (b9)
0: Half duplex
1: Full duplex
Hub connection status (b10)
0: Hub not connected/disconnected
1: Hub connected
Data transmission speed (b14)
0: Operating at 10BASE-T
1: Operating at 100BASE-TX
Bits other than above are reserved for system use.
Switch status (operational mode setting)
0: Online
1: Offline
2: Self refrain test
3: Hardware test (H/W test)
0H
Section 5.10
0H
Section 4.6
3 - 16
3 - 16
3 SPECIFICATIONS
MELSEC-Q
Application
Name
Module status
area
203
(CBH)
Communication
status storage
area
Initial value
(Hexadecimal)
GX Developer
setting
applicability
Reference
section
0H
Section 4.7
0H
Chapter 4 of
Application
0H
Chapter 4 of
Application
0H
Chapter 4 of
Application
System area
205
(CDH)
206
(CEH)
207
(CFH)
208
(D0H)
209
(D1H)
210 to 223
(D2 to DFH)
Area for
sending/
receiving
instructions
System area
Execution result of ZNRD instruction
Data link
instruction
execution
per channel
System area
Execution result of ZNWR instruction
System area
3 - 17
3 - 17
3 SPECIFICATIONS
MELSEC-Q
Application
224 to 226
(E0 to E2H)
Name
Initial value
(Hexadecimal)
228
(E4H)
229
(E5H)
230
(E6H)
Subheader
231
(E7H)
Command code
232
(E8H)
Error log
block 1
233
(E9H)
234 to 235
(EA to EBH)
Connection No.
0H
Section 11.3
0H
Section 11.3
236
(ECH)
237
(EDH)
System area
238 to 246
(EE to F6H)
Error log
block 2
247 to 255
(F7 to FFH)
Error log
block 3
Error log
block 4
Error log
block 5
274 to 282
(112 to 11AH)
Error log
block 6
283 to 291
(11B to 123H)
Error log
block 7
292 to 300
(124 to 12CH)
Error log
block 8
301 to 309
(12D to 135H)
Error log
block 9
310 to 318
(136 to 13EH)
Error log
block 10
319 to 327
(13F to 147H)
Error log
block 11
328 to 336
(148 to 150H)
Error log
block 12
337 to 345
(151 to 159H)
Error log
block 13
346 to 354
(15A to 162H)
Error log
block 14
355 to 363
(163 to 16BH)
Error log
block 15
364 to 372
(16C to 174H)
Error log
block 16
265 to 273
(109 to 111H)
373 to 375
(175 to 177H)
Reference
section
System area
227
(E3H)
256 to 264
(100 to 108H)
GX Developer
setting
applicability
System area
(Continues on the next page)
3 - 18
3 - 18
3 SPECIFICATIONS
MELSEC-Q
Application
Name
376 to 377
(178 to 179H)
378 to 379
(17A to 17BH)
380 to 381
(17C to 17DH)
400 to 407
(190 to 197H)
System area
408 to 409
(198 to 199H)
410 to 411
(19A to 19BH)
412 to 413
(19C to 19DH)
414 to 415
(19E to 19FH)
ICMP
416 to 417
(1A0 to 1A1H)
420 to 421
(1A4 to 1A5H)
442 to 443
(1BA to 1BBH)
TCP
Section 11.4
POINT (3)
0H
0H
446 to 471
(1BE to 1D7H)
System area
472 to 473
(1D8 to 1D9H)
474 to 475
(1DA to 1DBH)
UDP
0H
478 to 481
(1DE to 1E1H)
System area
System area
492 to 493
(1EC to 1EDH)
Receiving
error
496 to 497
(1F0 to 1F1H)
498 to 511
(1F2 to 1FFH)
0H
System area
440 to 441
(1B8 to 1B9H)
494 to 495
(1EE to 1EFH)
Section 11.3
418 to 419
(1A2 to 1A3H)
482 to 491
(1E2 to 1EBH)
0H
System area
Simultaneous transmission error
detection count
476 to 477
(1DC to 1DDH)
Reference
section
398 to 399
(18E to 18FH)
444 to 445
(1BC to 1BDH)
GX Developer
setting
applicability
IP
382 to 397
(17E to 18DH)
422 to 439
(1A6 to 1B7H)
Initial value
(Hexadecimal)
0H
Overflow count
0H
0H
System area
(Continues on the next page)
3 - 19
3 - 19
3 SPECIFICATIONS
MELSEC-Q
Application
512 to 513
(200 to 201H)
Sub-net mask
514 to 515
(202 to 203H)
516
(204H)
(Same as router 1)
Router 3
(Same as router 1)
Router 4
(Same as router 1)
533 to 536
(215 to 218H)
Router 5
(Same as router 1)
537 to 540
(219 to 21CH)
Router 6
(Same as router 1)
541 to 544
(21D to 220H)
Router 7
(Same as router 1)
545 to 548
(221 to 224H)
Router 8
(Same as router 1)
Router relay
parameter
setting area
549
(225H)
System area
550 to 551
(226 to 227H)
System area
552
(228H)
553 to 554
(229 to 22AH)
Conversion
information
number 1
555 to 556
(22B to 22CH)
557 to 558
(22D to 22EH)
559 to 564
(22F to 234H)
0H
Section 5.3
0H
Section 5.3
Router IP address
Router 2
529 to 532
(211 to 214H)
Station No.
<-> IP information
Conversion
setting area
information
number 2
0H
0H
931 to 936
(3A3 to 3A8H)
Conversion
information
number 64
937 to 938
(3A9 to 3AAH)
939 to 943
(3AB to 3AFH)
System area
944 to 949
(3B0 to 3B5H)
"QJ71E71"
950 to 953
(3B6 to 3B9H)
Password
"QJ71E71"
955
(3BBH)
956 to 1663
(3BC to 67FH)
Chapter 3 of
Application
System area
to
954
(3BAH)
Reference
section
Sub-net address
Router 1
519 to 520
(207 to 208H)
525 to 528
(20D to 210H)
GX Developer
setting
applicability
517 to 518
(205 to 206H)
521 to 524
(209 to 20CH)
Initial value
(Hexadecimal)
Name
0H
708H
Chapter 3 of
Application
Chapter 3 of
Application
AH
System area
3 - 20
3 - 20
3 SPECIFICATIONS
MELSEC-Q
Application
Initial value
(Hexadecimal)
Name
Data length
GX Developer
setting
applicability
Reference
section
0H
Chapter 7,
Chapter 8
0H
0H
Section 5.6
System area
Connection
status
Open request signal
information area
0: No open request
1: Open being requested
20482
Connection No. 1 (b0)
(5002H)
Connection No. 2 (b1)
to
Connection No. 16 (b15)
Connection status
20483 to 20484 storage area
System area
(5003 to 5004H)
0H
Section 5.6
20485
(5005H)
0H
Chapter 7
20486
(5006H)
0H
Section 5.9
1665 to 2687
(681 to A7FH)
Fixed buffer
No. 1
2688 to 3711
(A80 to E7FH)
Fixed buffer
No. 2
3712 to 4735
(E80 to 127FH)
Fixed buffer
No. 3
5760 to 6783
(1680 to 1A7FH)
Fixed buffer
No. 5
6784 to 7807
(1A80 to 1E7FH)
Fixed buffer
No. 6
7808 to 8831
(1E80 to 227FH)
Fixed buffer
No. 7
8832 to 9855
(2280 to 267FH)
Fixed buffer
No. 8
20480
(5000H)
20481
(5001H)
3 - 21
3 - 21
3 SPECIFICATIONS
MELSEC-Q
Application
20487
(5007H)
System port
information area
20488
(5008H)
20489 to 20591
(5009 to 506FH)
Initial value
(Hexadecimal)
Name
Remote password status
0: Unlock status/no remote password setting
Remote
1: Lock status
password status
Automatic open UDP port (b0)
storage area
GX Developer (UDP port) (b1)
GX Developer (TCP port) (b2)
FTP port (b3)
0H
0H
Reference
section
Section 5.9
System area
20592
(5070H)
1H
20593
(5071H)
2H
20594
(5072H)
20595
(5073H)
20596
(5074H)
Connection
No.1
20597
(5075H)
Section
5.9.6
0H
20599 to 20603
(5077H to 507B H)
Remote
password
function
monitoring area Connection
No.2
20604 to 20608
(507CH to 5080 H)
Connection
No.3
20609 to 20613
(5081H to 5085 H)
Connection
No.4
20614 to 20618
(5086H to 508A H)
Connection
No.5
20619 to 20623
(508BH to 508F H)
Connection
No.6
20624 to 20628
(5090H to 5094 H)
Connection
No.7
20629 to 20633
(5095H to 5099 H)
Connection
No.8
20634 to 20638
(509AH to 509E H)
Connection
No.9
20639 to 20643
(509FH to 50A3 H)
Connection
No.10
20644 to 20648
(50A4H to 50A8 H)
Connection
No.11
20598
(5076H)
GX Developer
setting
applicability
Monitoring area
3 - 22
3 - 22
3 SPECIFICATIONS
MELSEC-Q
Application
Name
Initial value
(Hexadecimal)
20649 to 20653
(50A9H to 50ADH)
Connection
No.12
20654 to 20658
(50AEH to 50B2H)
Connection
No.13
20659 to 20663
(50B3H to 50B7H)
Connection
No.14
20664 to 20668
(50B8H to 50BCH)
Connection
No.15
Connection
No.16
Automatic
open UDP
port
20669 to 20673
(50BDH to 50C1H)
20674 to 20678 Monitoring area
(50C2H to 50C6H)
Remote
password
function
monitoring area
communication
UDP port
GX Developer
20684 to 20688
(50CCH to 50D0H)
communication
TCP port
FTP
20689 to 20693
(50D1H to 50D5H)
communication
port
20694 to 20736
(50D6 H to 5100H)
System area
20737
(5101H)
20738
(5102H)
20739
(5103H)
20740
(5104H)
20741
(5105H)
20742
(5106H)
20743
(5107H)
System area
20745 to 20746
(5109 to 510AH)
Reference
section
GX Developer
20679 to 20683
(50C7H to 50CBH)
20744
(5108H)
GX Developer
setting
applicability
Section 11.3
0H
Status storage
area
20747 to 20750
(510B to 510EH)
0H
Section 11.3
Error time
20751 to 20757
(510F to 5115H)
20758 to 20764
(5116 to 511CH)
20765 to 20771
(511D to 5123H)
20772 to 20778
(5124 to 512AH)
20779 to 20785
(512B to 5131H)
20786 to 20792
(5132 to 5138H)
3 - 23
3 - 23
3 SPECIFICATIONS
MELSEC-Q
Application
Initial value
(Hexadecimal)
Name
20793 to 20799
(5139 to 513FH)
20800 to 20806
(5140 to 5146H)
20807 to 20813
(5147 to 514DH)
20814 to 20820
(514E to 5154H)
20828 to 20834
(515C to 5162H)
20835 to 20841
(5163 to 5169H)
20842 to 20848
(516A to 5170H)
20849 to 20855
(5171 to 5177H)
20856 to 20991
Use prohibited
(5178 to 51FFH)
System area
20992
(5200H)
20993
(5201H)
20994
(5202H)
"Issue system
switching request Cable disconnection timeout setting
Set time = set value
500ms (setting range: 0 to 60)
at disconnection
detection" status
System area
storage area
20995
(5203H)
21009
(5211H)
System area
22561 to 22562
Communication
(5821 to 5822H)
status storage
22563
area
(5823H)
22564
(5824H)
Connection
Connection
information area No. 9
Section 5.11
4H
Section 5.11
System area
22560
(5820H)
0H
21010 to 22559
Use prohibited
(5212 to 581FH)
Reference
section
1H
20996 to 21007
Use prohibited
(5204 to 520FH)
21008
(5210H)
GX Developer
setting
applicability
Section 5.10
0H
Section 5.11
0H
Section 5.11
0H
Destination IP address
0H
0H
0H
Section 11.3
(Continues on the next page)
3 - 24
3 - 24
3 SPECIFICATIONS
MELSEC-Q
Application
22565
(5825H)
22566
(5826H)
Connection
No. 9
22567
(5827H)
22568
(5828H)
22569
(5829H)
22570 to 22579
Communication
(582A to 5833H)
status storage
22580 to 22589
area
(5834 to 583DH)
Initial value
(Hexadecimal)
Name
0H
Section 11.3
0H
Section 11.3
Maximum value
0H
Minimum value
0H
Current value
0H
Fixed buffer
communication
time
22590 to 22599
(583E to 5847H)
Connection
No. 12
22600 to 22609
(5848 to 5851H)
Connection
No. 13
22610 to 22619
(5852 to 585BH)
Connection
No. 14
22620 to 22629
(585C to 5865H)
Connection
No. 15
22630 to 22639
(5866 to 586FH)
Connection
No. 16
22640
(5870H)
22641
(5871H)
22642
(5872H)
22645
(5875H)
22646
(5876H)
22647
(2877H)
22648
(5878H)
E-mail status
storage area
Receive
0H
Section 11.3
0H
Section 11.3
22649
(5879H)
Error code
22650
(587AH)
Command code
22651 to 22658
(587B to 5882H)
Reference
section
Connection
No. 10
Connection
information area Connection
No. 11
22643
(5873H)
22644
(5874H)
GX Developer
setting
applicability
Error log
block 1
From
22659 to 22662
(5883 to 5886H)
Date
22663 to 22692
(5887 to 58A4H)
Subject
22693 to 22736
(58A5 to 58D0H)
Error log
block 2
22737 to 22780
(58D1 to 58FCH)
22781 to 22824
(58FD to 5928H)
Error log
block 3
Error log
block 4
3 - 25
3 - 25
3 SPECIFICATIONS
MELSEC-Q
Application
Initial value
(Hexadecimal)
Name
22825 to 22868
(5929 to 5954H)
22869 to 22912
(5955 to 5980H)
Error log
block 5
Error log
block 6
22913 to 22956
(5981 to 59ACH)
Error log
block 7
22957 to 23000
(59AD to 59D8H)
23001 to 23044
(59D9 to 5A04H)
Error log
block 8
Error log
block 9
Error log
block 11
23133 to 23176
(5A5D to 5A88H)
Error log
block 12
23177 to 23220
(5A89 to 5AB4H)
Error log
block 13
23221 to 23264
(5AB5 to 5AE0H)
Error log
block 14
23265 to 23308
(5AE1 to 5B0CH)
Error log
block 15
23309 to 23352
(5B0D to 5B38H)
Error log
block 16
Receive
23089 to 23132
(5A31 to 5A5CH)
23353
(5B39H)
23354
(5B3AH)
23355
(5B3BH)
E-mail status
storage area
23356
(5B3CH)
23357
(5B3DH)
23358
(5B3EH)
23359
(5B3FH)
23360
(5B40H)
23361
(5B41H)
Send
0H
Section 11.3
0H
Section 11.3
Error code
23362
(5B42H)
23363 to 23370
(5B43 to 5B4AH)
Reference
section
Error log
block 10
23045 to 23088
(5A05 to 5A30H)
GX Developer
setting
applicability
Command code
Error log
block 1
To
23371 to 23374
(5B4B to 5B4EH)
Date
23375 to 23404
(5B4F to 5B6CH)
Subject
23405 to 23448
(5B6D to 5B98H)
Error log
block 2
23449 to 23492
(5B99 to 5BC4H)
Error log
block 3
23493 to 23536
(5BC5 to 5BF0H)
Error log
block 4
23537 to 23580
(5BF1 to 5C1CH)
Error log
block 5
3 - 26
3 - 26
3 SPECIFICATIONS
MELSEC-Q
Application
Name
23581 to 23624
(5C1D to 5C48H)
23625 to 23668
(5C49 to 5C74H) E-mail status
23669 to 23712 storage area
(5C75 to 5CA0H)
23713 to 24575
(5CA1 to 5FFFH)
24576
(6000H)
24577 to 25599
(6001 to 63FFH)
Send
Initial value
(Hexadecimal)
Error log
block 6
Error log
block 7
Error log
block 8
Reference
section
System area
Fixed buffer
No. 9
Data length
0H
Fixed buffer data
25600 to 26623
(6400 to 67FFH)
Fixed buffer
No. 10
26624 to 27647
(6800 to 6BFFH)
Fixed buffer
No. 11
28672 to 29695
(7000 to 73FFH)
Fixed buffer
No. 13
29696 to 30719
(7400 to 77FFH)
Fixed buffer
No. 14
30720 to 31743
(7800 to 7BFFH)
Fixed buffer
No. 15
31744 to 32767
(7C00 to 7FFFH)
Fixed buffer
No. 16
3 - 27
GX Developer
setting
applicability
3 - 27
MELSEC-Q
(1)
Since it is made of resin, the Ethernet module case should not be dropped or
subjected to any shock.
(2)
Tighten the module terminal and fixing screws within the following specified
clamping torque range:
Screw location
40 Ncm
2
36 to 48 Ncm
1 This terminal is used as an external power input terminal for supplying power to the transceiver when being
connected to a 10BASE5.
2 The module can be easily fixed onto the base unit using the hook provided at the top of the module. However, it
is recommended that the module will be secured with the dedicated installation screws if it is subject to
significant vibration or shock.
DANGER
4-1
Do not touch the terminals and connectors while the power is on.
Doing so may result in electric shocks and malfunctions.
Make sure to turn off all phases of the external power supply before cleaning or retightening the screws. Failure to do so may cause damages or malfunctions of the
module.
If the screws are loose, it may cause the module to short circuit, malfunction or fall
off.
Tightening the screws excessively may damage the screws and/or the module and
cause the module to short circuit, malfunction or fall off.
Check the safety before performing control operations to the running PLC
(especially, modifications of data, programs and operation status (status control)).
4-1
CAUTION
MELSEC-Q
To install the module, securely insert the module fastening latch in the installation
hole on the base unit while holding down the module installation lever on the lower
part of the module.
If the module is not installed properly, it may cause the module to malfunction, fail or
fall off.
Secure the module with screws especially when it is used in an environment where
constant vibrations may occurs.
Be careful not to let any foreign matter such as wire chips get inside the module.
They may cause fire, as well as breakdowns and malfunctions of the module.
Never disassemble or modify the module.
This may cause breakdowns, malfunctions, injuries or fire.
Before mounting or dismounting the module, make sure to switch all phases of the
external power supply off.
Failure to do so may cause the module to breakdown or malfunction.
Tighten the terminal screws using the specified torque.
If the terminal screws are loose, it may cause the module to short-circuit,
malfunction or fall off.
Tightening the terminal screws excessively may damage the screws and/or the
module and cause the module to short-circuit, malfunction or fall off.
Do not directly touch the conducting parts and electronic parts of the module.
This may cause the module to malfunction or fail.
When disposing of this product, treat it as industrial waste.
A protective sheet is pasted on the upper part of the module in order to prevent
foreign matter such as wire chips to get inside the module while wiring.
Do not remove this protective sheet during wiring work.
However, be sure to remove the protective sheet before operating the module to
allow heat radiation during operation.
CAUTION
4-2
Use the PLC in the operating environment that meets the general specifications
described in the users manual of the CPU module to use.
Using the PLC in any other operating environments may cause electric shocks, fires
or malfunctions, or may damage or degrade the module.
4-2
MELSEC-Q
Operation
POINT
To operate the Ethernet module after the parameter settings are added or modified
with GX Developer, the PLC CPU must be reset after saving the parameter values
in the PLC CPU.
4-3
4-3
MELSEC-Q
Important
4-4
(1)
Do not write any data in the "System area" of the buffer memory of the
intelligent function module.
(2)
Do not output (turn on) the "Use prohibited" signal, which is one of the output
signals.
(3)
(4)
(5)
When the Ethernet module is replaced, reset the external device as well. (If
the external device retains the Ethernet address, it may be impossible to
continue the communication because a module is replaced and the Ethernet
address changes.)
In the same may, when the external device (personal computer, etc.)is
replaced, restart the Ethernet module.
4-4
MELSEC-Q
1)
RUN
INIT.
OPEN
SD
QJ71E71-B5
ERR.
COM.ERR.
100M
RD
RUN
INIT.
OPEN
SD
1)
3)
10BASE-T/100BASE-TX
ERR.
COM.ERR.
QJ71E71-B2
1)
RD
RUN
INIT.
OPEN
SD
ERR.
COM.ERR.
RD
10BASE 5
4)
2)
+12
5)
12V
12G
QJ71E71-B5 EXT. POWER
QJ71E71-100
Name
QJ71E71-B2
Description
1)
LED display
2)
10BASE-T/100BASE-TX
1
connector (RJ45) (
)
3)
10BASE5 connector
4)
10BASE2 connector
5)
Power supply terminal for supplying power to the transceiver when connecting by
10BASE5 (13.28 V to 15.75 V)
4-5
4-5
MELSEC-Q
1) LED display
QJ71E71-100
RUN
INIT.
OPEN
SD
QJ71E71-B5
ERR.
COM.ERR.
100M
RD
RUN
INIT.
OPEN
SD
QJ71E71-B2
ERR.
COM.ERR.
RD
RUN
INIT.
OPEN
SD
ERR.
COM.ERR.
RD
LED name
Display description
QJ71E71-100
QJ71E71-B5,
QJ71E71-B2
RUN
RUN
Normal
INIT.
INIT.
Normal completion
Not processed
OPEN
OPEN
SD
SD
ERR.
ERR.
Communication abnormal
4
occurrence
Abnormal
Normal setting
COM.ERR.
COM.ERR.
100 M
(Not used)
100Mbps
RD
RD
1 Refer to Section 11.1.1 for causes of error displays and the corresponding
corrective actions.
2 The [OPEN] LED turns on/off depending on the open states of user
connections 1 to 16.
(The open states of the system connections (e.g., automatic open UDP port)
are not included.)
3 The [ERR.] LED turns on in the following cases:
When setting values in GX Developer (mode, station number, and/or
network number) are incorrect.
When an error has occurred in the Ethernet module or PLC CPU and the
operation is disabled due to the error.
4 Refer to Section 11.1.2 for the time when "COM.ERR" LED is on.
4-6
4-6
MELSEC-Q
CAUTION
4-7
Do not bundle the control wires and the communication cables with the main circuit
and the power wires, and do not install them close to each other. They should be
installed at least 100 mm (3.94 in.) away from each other. Failure to do so may
generate noise that may cause malfunctions.
Do not connect the AUI cables while the power to the module installed station is on.
Make sure to place the communication and power cables to be connected to the
module in a duct or fasten them using a clamp.
If the cables are not placed in a duct or fastened with a clamp, their positions may
be unstable or moved, and they may be pulled inadvertently. This may damage the
module and the cables or cause the module to malfunction because of faulty cable
connections.
When disconnecting the communication and power cables from the module, do not
pull the cables by hand.
When disconnecting a cable with a connector, hold the connector to the module by
hand and pull it out to remove the cable.
When disconnecting a cable without a connector, loosen the screws on the terminal
block first before removing the cable.
If a cable is pulled while being connected to the module, it may cause the module to
malfunction or damage the module and the cable.
4-7
MELSEC-Q
<Operating procedure>
(Step 1) Connect the twisted-pair cable to the hub.
(Step 2) Connect the twisted-pair cable to the Ethernet module.
POINT
(1) The Ethernet module detects whether it is 10BASE-T or 100BASE-TX, and the
full-duplex or half-duplex transmission mode according to the hub.
For connection to the hub without the auto detection function, set the halfduplex mode on the hub side.
(2) For devices required for 10BASE-T or 100BASE-TX connection and a sample
system configuration, refer to Section 2.2 (1) and (2).
4-8
4-8
MELSEC-Q
Retainer
A
B
AUI cable
<Operating procedure>
(Step 1) Slide the retainer toward the direction B as shown above.
(Step 2) Push in the AUI cable connector all the way.
(Step 3) Slide the retainer toward the direction A as shown above.
(Step 4) Confirm that the AUI cable is locked.
(Step 5) Supply power to the transceiver ( 1).
1 Use a transceiver with a function that is generally called SQETEST or heart
beat (a transceiver function that emits signals to notify whether the
transceiver is operating normally at the end of communication).
CAUTION
Do not connect the AUI cable while the power to the module installed station is on.
POINT
4-9
(1)
(2)
See Section 2.2 (2) (b) for the device and system configration explanation that
is required for 10BASE5 connection.
4-9
MELSEC-Q
[2]
[1]
<Operating procedure>
(Step 1) Push in the connector by aligning the groove [1] and tab [2] as shown
above.
(Step 2) While pushing in the connector, rotate it clockwise a 1/4 turn.
(Step 3) Turn until the connector locks.
(Step 4) Check that the connector is locked.
POINT
See (3) in Section 2.2 for the device and system configuration example that is
required for 10BASE2 connection.
4 - 10
4 - 10
MELSEC-Q
REMARK
Attaching the connector for the coaxial cable
The following section explains how to attach the BNC connector (connector plug for
the coaxial cable) to the cable.
Nut
Washer
Gasket
External conductor
Insulation
material
Outer sheath
Plug shell
Clamp
Contact
Internal conductor
(2) How to attach the BNC connector and the coaxial cable
The following shows how to attach the BNC connector and the coaxial cable.
(a)
(b)
(c)
(d)
(e)
15 mm
(0.6 in.)
Clamp
Nut
Washer
Gasket
Insulation material
Internal conductor
3 mm
(0.11 in.) 6 mm
(0.23 in.) Clamp and
external conductor
Solder here
POINT
Pay attention to the following when soldering the internal conductors and contacts:
4 - 11
(1)
Make sure that the solder does not bead up on the soldered section.
(2)
Make sure that there are no gaps between the connector and the cable
insulator and that they do not cut into each other
(3)
4 - 11
MELSEC-Q
[PLC Parameter]
I/O assignment
[Display contents]
Item name
I/O assignment
4 - 12
Type
Select "Intelli."
Model name
Points
Select 32 points.
Start-XY
Enter the start I/O signal (hexadecimal) for the target module.
Detailed setting
Select the control PLC of the Ethernet module when a multiple CPU system is
employed.
Select when using a multiple CPU system.
Remarks
4 - 12
MELSEC-Q
(3) "Initial settings" (Details are explained in Section 5.2 and Chapter 2
of the Users Manual (Application).)
This screen is for setting common timer values for TCP/IP communication to be
used in the Ethernet module as well as for setting the DNS server in order to use
the e-mail function.
It is not necessary to set the timer values when communicating using the default
timer values.
4 - 13
4 - 13
MELSEC-Q
4 - 14
4 - 14
MELSEC-Q
REMARK
It is not necessary to set the "Intelligent function module switch settings" with GX
Developers I/O assignment.
Each type of setting corresponding to the switch settings is performed in the above
mentioned "Operational settings," "Initial settings," and "Open settings."
4 - 15
4 - 15
MELSEC-Q
Item name
Description of setting
Setting range/selection
Select the module by which the access is made when the access request does not
specify the network number.
Network type
Network No.
Group No.
1 to 32
Station No.
1 to 64
Mode
Operational settings
Initial settings
Open settings
FTP Parameters
E-mail settings
Interrupt settings
Redundant setting
Group settings
Settings for disabling system switching if an error occurs in one communication path
when the redundant communication paths are used for the external device and
Ethernet module in a redundant system.
(Refer to the QnPRHCPU User's Manual (Redundant System).)
Routing parameters
4 - 16
1 to 8
Ethernet
0000 to 0FE0H
1 to 239
Online
Offline
Self refrain test
H/W test
4 - 16
MELSEC-Q
This item designates the network module to which the request is directed,
when the local station issues a data communication request and it cannot
specify the network number of the access destination PLC station. This
should be one of the following:
A network module for the MELSECNET/H, MELSECNET/10
An Ethernet module
Select "Ethernet," then each setting item is displayed as shown in the above
screen.
The following items must be set.
Starting I/O No.
Network No.
Group No.
Station No.
Mode
Operational settings
Initial settings (Settings not required when using the default values)
Set the head I/O number of the Ethernet module in units of 16 points
(hexadecimal).
(b)
Set the network number of the target Ethernet module (setting range from 1
to 239) for the MELSECNET/H, MELSECNET/10.
(b)
4 - 17
(a)
Set the group number of the target Ethernet module (setting range from 1 to
32) for the MELSECNET/H, MELSECNET/10.
(b)
4 - 17
MELSEC-Q
Set the station number of the target Ethernet module (setting range from 1
to 64) for the MELSECNET/H, MELSECNET/10.
(b)
Do not set the number to a value already assigned to existing systems and
other Ethernet modules.
Name of setting
Description of setting
Online
Offline
Self refrain test
H/W test
(b)
POINT
4 - 18
(1)
Both the "Setting the number of MNET/10H Ethernet cards" and "Operational
setting" parameters must always be specified. If the settings are changed, the
QCPU (PLC No.1 when used in a multiple CPU system) must be reset.
(2)
Write the network parameters in the control PLC of the Ethernet module when
the module is used in a multiple CPU system.
4 - 18
MELSEC-Q
Item name
Setting range/selection
Binary code
ASCII code
Initial Timing
Input format
Decimal
Hexadecimal
IP address
IP Address
Ethernet (V2.0)
IEEE 802.3
ASCII code
(b)
4 - 19
Description of setting
Binary code
For more details on the data communication codes, see Section 3.2, "Data
Codes for Communication."
4 - 19
MELSEC-Q
Select the timing to open for connections for which TCP-Passive open or
UDP open are selected with the "Open settings" parameter ( 1).
1 For more details on the open settings, see Section 5.5 "Open Settings".
Name of setting
Do not wait for OPEN
(Communication impossible at
STOP time)
Always wait for OPEN
(Communication possible at
STOP time)
Description of setting
Execute open/close processing using a sequence program.
Communication cannot be performed while the PLC CPU is in the STOP status.
Passive open and UDP open connections always wait for open according to the
parameter settings (a sequence program for open/close processing is not required)
2
(
).
Communication can be performed while the PLC CPU is in the STOP status.
2 If the sequence program of the local station's PLC CPU executes the close processing, the station is not
placed in the OPEN request wait status after the connection is shut off.
(b)
Set the IP address of the local station according to the specified input format
(decimal or hexadecimal).
It should be set so that the local station Ethernet module and the
communicating external device have the same class and sub-net address
(two words).
[IP address]
Values bits 7 to 0
to
Values bits 31 to 24
4 - 20
(b)
(c)
Set the IP address after consulting a network administrator (the person who
plans the network and manages IP addresses).
4 - 20
MELSEC-Q
Select the frame of the Ethernet header for the data link layer to be sent by
the Ethernet module.
Setting item
Description of setting
Ethernet (V2.0)
IEEE802.3
(b)
When receiving data from the external device, reception should occur
regardless of whether the Ethernet frame or IEEE802.3 frame is used
REMARK
(1) Transmission using Ethernet frames is generally recommended.
(2) When communication with the external device fails, check whether or not
communication is possible using a PING command.
Name of setting
Description of setting
Check mark
(Enable write at RUN time)
No check mark
(Disable write at RUN time)
Description of setting
*1 Do not use GX Developer incompatible with this setting together with compatible GX Developer. (Doing
so may change the setting to "Use the Ping".)
This setting is ignored when the Ethernet module does not support the KeepAlive check function. (Ping is
used for the existence check.)
Refer to Section 2.7 for applicable versions of the Ethernet module and GX Developer.
POINT
(1) The "Setting the number of MNET/10H Ethernet cards" and "Operational
settings" parameters must always be set.
If the settings are changed, the PLC CPU must be reset.
(2) If the re-initial processing of the Ethernet module is required due to the
occurrence of an error, perform re-initial processing using sequence programs
(see Section 5.2.3).
(3) When using the programs for conventional models, be sure to delete or disable
the program for initial processing that uses I/O signals.
4 - 21
4 - 21
MELSEC-Q
Status of LED
Description of operation
[RUN]
Stop QCPU.
Reset QCPU.
[OPEN]
[ERR.]
Normal
Error
: Lit
: Off
1 For QJ71E71-100, when the line is not connected, the self refrain test is not performed and end normally.
POINT
There will be no hardware interference even if the self refrain test is conducted
while an external device is online. If the packets are congested over the line, packet
collisions may occur and the test may not finish with the error end or within the
expected 5-second time frame.
In this case, perform the test again after terminating the data communication
between other devices.
4 - 22
4 - 22
MELSEC-Q
Status of LED
Description of operation
[RUN]
Stop QCPU.
Reset QCPU.
[OPEN]
[ERR.]
Normal
Error
: Lit
: Off
POINT
If the result of the hardware test shows an error, conduct the test again.
If this test result also shows an error, the hardware of the Ethernet module may be
faulty.
Please consult the nearest branch office or dealer with details of the errors.
4 - 23
4 - 23
MELSEC-Q
DANGER
CAUTION
4 - 24
Do not touch the terminals and connectors while the power is on.
Doing so may cause in electric shocks and malfunctions.
Do not touch the connector inside the cover at the upper section of the module.
Doing so may cause damages and malfunctions of the module.
Make sure to turn off all phases of the external power supply before cleaning or retightening the screws. Failure to do so may cause damages or malfunctions of the
module.
If the screws are loose, it may cause the module to short-circuit, malfunction or fall
off.
Tightening the screws excessively may damage the screws and/or the module and
cause the module to short circuit, malfunction or fall off.
Be careful not to let any foreign matter such as wire chips get inside the module.
They may cause fire, as well as breakdowns and malfunctions of the module.
Never disassemble or modify the module.
This may cause breakdowns, malfunctions, injuries or fire.
4 - 24
MELSEC-Q
4 - 25
4 - 25
5 COMMUNICATION PROCEDURE
MELSEC-Q
5 COMMUNICATION PROCEDURE
This chapter explains an overview of the communication procedure using the Ethernet
module, as well as the required initial processing of the Ethernet prior to starting data
communication and the open processing for communication with an external device.
The sequence program for setting the parameters required to perform communication
can be greatly simplified by setting the parameters of the Ethernet module supported
by GX Developer.
The following explains the communication procedure using GX Developer.
REMARK
When utilizing a sequence program for a conventional module, see Appendix,
"Using Programs Designed for Conventional Modules".
Initial processing
Open processing
Communication using
fixed
buffers
Close processing
5-1
Communication using
the MC
protocol
Communication using
random
access
buffers
Communication
using the
NC protocol
E-mail
sending/
receiving
MELSECNET/H
MELSECNET/10
relay communication
Communication using
data link
instructions
File transfer
(FTP)
Communication using
Web
function
Communication using
GX
Developer
5-1
5 COMMUNICATION PROCEDURE
MELSEC-Q
REMARK
Each of the following three types of communication can be performed with an
external device opened by the user.
Communication using the MC protocol
Sending/receiving in fixed buffer communication (procedure exists)
Communication using random access buffers
When receiving communication request data from an external device
Ethernet module
PLC CPU
(Subheader code)
60H
E0H
Data
61H/62H
Confirm the
request contents
with the
subheader.
Header
Sub header
Application data
OS
TCP
IP
Store data
received
Ethernet
E1/E2H
00H to 3CH, 50H
IP
Data
80H to BCH, D0H
5-2
5-2
Ethernet
Header
TCP
Sub header
Application data
5 COMMUNICATION PROCEDURE
MELSEC-Q
INIT.LED
I/O signal
Initial normal completion signal X19
At normal completion
: On
ON
OFF
At abnormal completion
: Off
OFF
ON
If the initial processing does not complete normally, correct the above parameter
setting value and write to the PLC CPU. Then reset the PLC CPU.
5-3
5-3
5 COMMUNICATION PROCEDURE
MELSEC-Q
Item name
Timer setting
Description of setting
Set the time of packet existence at TCP data transmission.
2 to 32767
2 to 32767
2 to 32767
2 to 32767
IP assembly timer
1 to 32766
2 to 32767
1 to 32767
Destination existence confirmation interval timer Set the time interval between reconfirming existence.
Destination existence confirmation resend timer
DNS setting
1
)
(
Setting range/options
Input format
1 to 32767
1 to 32767
Decimal/hexadecimal
5-4
5-4
5 COMMUNICATION PROCEDURE
MELSEC-Q
This item sets the time of packet existence during TCP data sending.
This timer is passed through the parameter when TCP opens or data is
sent.
(b)
(c)
(b)
(c)
(d)
Set the resend time if ACK is not returned at TCP opening or data
transmission. This timer is also used for the existence time of the ARP
function.
(ARP is resent in TCP resend timer value/2 if a response is not returned in
reply to the sent ARP request.)
It also serves as the minimum setting time for the data link instruction
arrival monitoring time.
(b)
(c)
5-5
(a)
When the TCP connection is closed from the local station, this timer sets the
monitoring time for how long the local station waits for a FIN request from
an external device after it sends an FIN request and the external device
returns an ACK.
(b)
If the FIN request cannot be received from the external device before the
time designated by the TCP end timer setting, a RST should be sent to the
external device to forcefully close the connection.
(c)
(d)
5-5
5 COMMUNICATION PROCEDURE
MELSEC-Q
(b)
(c)
2)
The time to wait for the last message after receiving the first message
when the message is divided.
(b)
(c)
This timer sets the time interval before starting to confirm the existence of
an external side when an open connection for which existence confirmation
is set to confirm stops dead.
(b)
(c)
This timer sets the time interval before reconfirming the existence of an
external device on an open connection for which existence confirmation is
set to confirm that does not respond.
(b)
(c)
5-6
(a)
This timer sets the number of times to reconfirm existence when there is no
response from an external device on an open connection for which
existence confirmation is set to confirm.
(b)
5-6
5 COMMUNICATION PROCEDURE
MELSEC-Q
REMARK
(1) Designate the setting value of each timer on the Ethernet module side in such a
way that the following relations are met.
Response
monitoring timer
value
>
=
TCP
resend
timer value
TCP ULP
timer value
TCP end
timer value
>
=
>
=
TCP
resend
timer value
IP assembly
timer value
>
Furthermore, when connecting a line using our products, you should make sure
that both nodes have the same settings.
(2) Designate the setting value of each timer on the external device side in such a
way that the following relations are met.
Communication errors such as transmission timeouts may occur more
frequently if the timer values are not set so that they satisfy the following
relationships.
>
>
11 n is the number of TCP segment transmissions and can be obtained via the following calculation:
n=
(fractions below
decimal point are rounded up)
5-7
5 COMMUNICATION PROCEDURE
MELSEC-Q
(3) When communication errors occur due to noise or other factors, the settings
should be changed to increase the number of retries.
The number of retries is obtained by using the following equation:
(In case of the default values, 2 = (60/20) - 1)
Number
of retries
Example: Assuming the values are set in such a way that the number of retries is
two, a data transmission error will occur at the timing shown in the figure
below if data transmission fails (when communicating using fixed buffer).
BUFSND instruction
1 scan
BUFSND instruction
completion device + 1
Ethernet module
First retry
Data
command
Second retry
(4) Perform the following setting in order to eliminate the retries explained in (3)
(i.e., to set the number of retries to 0).
TCP ULP
timer value
TCP end
timer value
TCP resend
timer value
(5) The target existence check is a function whereby the Ethernet module checks
whether or not a remote device is functioning normally by sending an existence
check message and then waiting to see whether a response message is
received. It is used if a connection to a remote device is open but
communication with the remote device has not been performed for a certain
period of time.
(a) The existence check function has two methods of checking: PING and
KeepAlive.
The Ethernet module performs each of the existence checks based on the
setting values explained in (7) to (9) of this section and the existence
check setting of the open settings (refer to Section 5.5 (6)).
The existence check function (Ping or KeepAlive) can be selected at the
time of operation setting or re-initialization.
For the operation setting, refer to Section 4.7.
Refer to Section 5.2.3 for the explanation about the re-initial processing.
5-8
5-8
5 COMMUNICATION PROCEDURE
1)
MELSEC-Q
Checking by KeepAlive
This method is used for a connection opened via the TCP/IP protocol.
The Ethernet module performs an existence check by sending an
existence check ACK message to a remote device with which
communication has not been performed for a certain period of time
and waiting to see whether or not a response is received. ( 1)
1 The connection may be cut off if the remote device does not
support the TCP KeepAlive function (response to KeepAlive ACK
messages).
2)
Checking by PING
This method is used for a connection opened via the TCP/IP or
UDP/IP protocol.
The Ethernet module performs an existence check by sending a PING
command (using the ICMP echo request/response function) to a
remote device with which communication has not been performed for
a certain period of time and waiting to see whether or not a response
is received. ( 2)
2 Note that the Ethernet module automatically returns an echo
response packet when it receives a PING echo request
command. (It sends a response to the received PING command
even if the connection used in the data communication with the
remote device is closed.)
(b)
PING
command
Target
existence
check starting
interval timer
value
5-9
Target
existence
check interval
timer value
PING
command
PING
command
Target
existence
check interval
timer value
5-9
5 COMMUNICATION PROCEDURE
MELSEC-Q
(b)
(c)
U0\
G20480.
Store control data in D250 to D255
ZP.UINI
M250
"U0" D250
M250
M251
Processing upon normal completion
M251
Processing upon abnormal completion
X19
Data communication enabled
5 - 10
5 - 10
5 COMMUNICATION PROCEDURE
MELSEC-Q
Close processing
Initial normal completion signal X19
Open completion signal
(address: 5000H)
UINI instruction
Re-initial processing
1)
2)
3)
1)
2)
3)
4)
(3) Precautions for combination with the MELSOFT products when the
setting is changed to "Enable TCP Maximum Segment Size Option
transmission" in re-initial processing
(a) MELSOFT series products supporting the TCP Maximum Segment
transmission function
For setting the "Enable TCP Maximum Segment Size Option transmission",
use the following MELSOFT products.
GX Developer
: Version8.07H or later
MX Component
: Version3.03D or later
MX Links
: Version3.08J or later
(b) MELSOFT series products not listed above (a)
When using a MELSOFT product that is not listed above (a) to make
communication via Ethernet, set it to "Disable TCP Maximum Segment
Size Option transmission" or use UDP/IP type communication.
Otherwise, the sequence program may not function correctly (read/write is
incorrect).
5 - 11
5 - 11
5 COMMUNICATION PROCEDURE
MELSEC-Q
POINT
Please keep the following points in mind when re-initializing the Ethernet module.
(Failure to do so may cause errors in the data communication with the external
devices.)
(1) Be sure to end all current data communication with external devices and close
all connections before performing a re-initial processing.
(2)
Do not mix a re-initial processing done by writing directly into buffer memory, for
instance by using a TO instruction, with a re-initial processing via UINI instruction.
Also, do not request another re-initial processing while a re-initial processing
is already being performed.
(3)
Be sure to reset external devices if the IP address of the Ethernet module has
been changed. (If an external device maintains the Ethernet address of a
device with which it communicates, the communication may not be continued
after the IP address of the Ethernet module has been changed.)
REMARK
It is possible to change the operational settings when performing re-initial processing
by a sequence program.
In the case of Ethernet module, parameters other than the operational settings, the
settings should be changed via GX Developer, after which the QCPU (PLC No. 1 in
the case of a multiple CPU system) should be reset.
Parameter setting item
PLC parameters
I/O assignment settings
Interrupt pointer settings
Network parameters
Setting the number of
MNET/10H Ethernet cards
Operational settings
Initial
settings
Section 4.5
Section 4.6
1 FH
Timer setting
BH to 13H
Reference section
DNS settings
Open settings
Parameter changes
Section 7.3
1)
Section 5.2
User's Manual (Application),
Chapter 2
20H to 5FH
1)
Section 5.5
1)
Section 5.3
1)
FTP parameters
1)
E-mail settings
News setting
Redundant setting
Routing parameters
Section 5.9.5
Interrupt settings
Section 7.3
Section 5.11.3
: Valid,
: Invalid
*1 The PLC CPU operates with the settings performed during the re-initial processing
in the applicable buffer memories. Do not change the settings in the applicable
buffer memories.
5 - 12
5 - 12
5 COMMUNICATION PROCEDURE
MELSEC-Q
Re-initial
instruction
Re-initial
instruction
INCP
D260
INCP
D261
Re-initial
instruction
POINT
This is an example program that can be used to perform re-initial processing when
communicating with connections 1 and 2. The corresponding numbers and bits for
each connection should be specified if other connections are used.
5 - 13
5 - 13
5 COMMUNICATION PROCEDURE
MELSEC-Q
REMARK
Direct write to the following buffer memory addresses enables the re-initial
processing of the Ethernet module.
The procedure for performing the re-initial processing by directly writing to the buffer
memory is explained below:
(a) Change the value stored in the TCP Maximum Segment transmission area
(address: 1EH).
0000H: Enable TCP Maximum Segment Size Option transmission
8000H: Disable TCP Maximum Segment Size Option transmission
(b) Change the values stored in the communication condition setting area (address:
1FH).
Bits 0 to 14 : Specify the values set in the operation settings.
Bit 15
: "1"
b15
Buffer memory
address 1FH
b8
6)
1)
2)
5)
b6
b5
b4
b1
4)
3)
2)
1)
3)
4)
5)
6)
5 - 14
5 COMMUNICATION PROCEDURE
MELSEC-Q
Always ON
Connection 1
open completion
signal
Re-initial
instruction
Re-initial
instruction
>
>
<Set to KeepAlive
>
>
>
>
>
Connection 1
open
completion
signal
Re-initial
instruction
Initial
normal
completion
signal
Connection 2
open
completion
signal
Initial
completion
status
>
Initial error
code
storage area
Re-initial
instruction
Initial normal
completion signal
Initial
completion
status
POINT
This is an example program that can be used to perform re-initial processing when
communicating with connections 1 and 2. The corresponding numbers and bits for
each connection should be specified if other connections are used.
5 - 15
5 - 15
5 COMMUNICATION PROCEDURE
MELSEC-Q
Item name
Description of setting
Setting range/options
Use
Not used
C0000000H to FFFFFFFCH
Input format
Decimal
Hexadecimal
Sub-net address
Set the sub-net address or network address of the external device when
communicating with an external device on another Ethernet via a router other
than the default router.
Router IP address
Set the IP address of a router used when communicating with an external device
on another Ethernet via a router other than the default router.
5 - 16
5 - 16
5 COMMUNICATION PROCEDURE
MELSEC-Q
(b)
(c)
One default router and a maximum of any eight routers can be set for the
router relay function.
(b)
When not using the subnet mask, set any of the following table values
according to the class.
Class
Mask value
Class A
FF000000H
Class B
FFFF0000H
Class C
FFFFFF00H
81H
05H
2FH
01H
1 0 0 0 0 0 0 1 0 0 0 0 0 1 0 1 0 0 1 0 1 1 1 1 0 0 0 0 0 0 0 1
Subnet mask
FFH
FFH
FCH
00H
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0
Subnet address
IP address
Host address
81H
05H
2FH
01H
1 0 0 0 0 0 0 1 0 0 0 0 0 1 0 1 0 0 1 0 1 1 1 1 0 0 0 0 0 0 0 1
POINT
(1)
(2)
5 - 17
All devices on the same sub-network must have common subnet masks.
When not administrated by the sub-network, the connected devices need not
have subnet masks. (Set the network address of the corresponding class.)
5 - 17
5 COMMUNICATION PROCEDURE
MELSEC-Q
POINT
If the corresponding sub-net address does not exist in the router information (refer
to (4) in this section) when the connection is opened or data communication is
made, communication is made via the default router.
(b)
Router 1
Ethernet1
Setting example 1
Target device 1)
Class B
IP address: 81044001H
(129.4.64.1)
5 - 18
Router 2
Ethernet2
Setting example 2
Target device 2)
Class A
IP address: 71044001H
(113.4.64.1)
Router 3
Ethernet3
Setting example 3
Target device 3)
Class B
IP address: 81052902H
(129.5.41.2)
5 - 18
5 COMMUNICATION PROCEDURE
MELSEC-Q
(Setting example 1) When the network addresses of the local station Ethernet module and target device differ
Network address
Local station Ethernet
module
IP address (Class B)
81H
05H
2FH
01H
1 0 0 0 0 0 0 1 0 0 0 0 0 1 0 1 0 0 1 0 1 1 1 1 0 0 0 0 0 0 0 1
Target device 1)
IP address (Class B)
81H
04H
40H
01H
1 0 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1
Set the network address of the target device 1)
Network address
81H
04H
00H
00H
1 0 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
(Setting example 2) When the classes of the local station Ethernet module and target device differ
Network address
Local station Ethernet
module
IP address (Class B)
81H
05H
2FH
01H
1 0 0 0 0 0 0 1 0 0 0 0 0 1 0 1 0 0 1 0 1 1 1 1 0 0 0 0 0 0 0 1
Target device 2)
IP address (Class A)
71H
04H
40H
01H
0 1 1 1 0 0 0 1 0 0 0 0 0 1 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1
Set the network address of the target device 2)
Network address
71H
00H
00H
00H
0 1 1 1 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
(Setting example 3) When the network addresses of the local station Ethernet module and target device are
the same
Network address
Local station Ethernet
module
IP address (Class B)
81H
05H
2FH
01H
1 0 0 0 0 0 0 1 0 0 0 0 0 1 0 1 0 0 1 0 1 1 1 1 0 0 0 0 0 0 0 1
Subnet mask
FFH
FFH
FCH
00H
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0
Target device 3)
IP address (Class B)
81H
05H
29H
02H
1 0 0 0 0 0 0 1 0 0 0 0 0 1 0 1 0 0 1 0 1 0 0 1 0 0 0 0 0 0 2 0
Set the subnet address of the target device 3)
Subnet address
5 - 19
81H
05H
28H
00H
1 0 0 0 0 0 0 1 0 0 0 0 0 1 0 1 0 0 1 0 1 0 0 0 0 0 0 0 0 0 0 0
5 - 19
5 COMMUNICATION PROCEDURE
MELSEC-Q
POINT
(1)
(2)
5 - 20
When the Ethernet module communicates with the external device via the
router in Passive open (TCP/IP) status, communication can be made without
use of the router relay function.
The router relay function is not needed in a system that uses the Proxy router.
5 - 20
5 COMMUNICATION PROCEDURE
MELSEC-Q
POINT
The status of the Ethernet module becomes communication enabled when the
initial processing is completed normally. See reference sections for each
communication function to perform communication.
When the initial processing has not been completed normally, do the following to
check the contents of the error, take corrective actions, then execute the initial
processing again.
Check the error code using the "Parameter status" of the Ethernet diagnostics.
(See Section 11.2.)
Check the contents of the error corresponding to the error code, then take
corrective actions. (See Section 11.3.3.)
5 - 21
(a)
(b)
The following can be checked by performing the PING test for the Ethernet
module:
Whether a line has been properly connected to the test target Ethernet
module
Whether the parameters for the Ethernet module have been correctly set
Whether the initial processing for the Ethernet module has been
completed normally
5 - 21
5 COMMUNICATION PROCEDURE
MELSEC-Q
(c)
The PING test can be performed for an Ethernet module in the same
Ethernet as the local station (same sub-net address.)
(d)
If the external device subject to the PING test is an Ethernet module, do not
designate the UDP port for GX Developer of the Ethernet module as a valid
port for the remote password check. If it is designated as a valid port for the
remote password check, the PING test cannot be performed.
Station No.: 2
[10.97.85.222]
QCPU Ethernet
2)
module
Ethernet
QCPU
1)
Ethernet
module
Station No.: 1
[10.97.85.221]
(a)
Setting screen
Set the following Ethernet module parameters for the PING test target
station through GX Developer.
Use default values for setting items other than those listed below.
Setting item
QCPU 1)
QCPU 2)
Ethernet
Ethernet
0000
0000
Network No.
Group No.
Station No.
IP address
[10.97.85.221]
[10.97.85.222]
Network type
Network parameters setting
the number of MNET/10H
Ethernet cards
Operational setting
5 - 22
Setting description
2)
3)
5 - 22
5 COMMUNICATION PROCEDURE
MELSEC-Q
(b)
(c)
2)
[Diagnostics]
[Ethernet diagnostics]
PING test
Perform the settings indicated below, then click the Execute button.
The execution results of the PING test are displayed.
(Example) The following shows the flow of the PING test when "4" is
designated as the transmission count.
Time of the communication time check: 1 s
GX Developer
Ethernet line
Normal Normal
response response
Abnormal
response
Normal
response
Ethernet module
Normal response occurs when the PING test response is received
within the time of the communication time check.
5 - 23
5 - 23
5 COMMUNICATION PROCEDURE
MELSEC-Q
[Display contents]
Item name
Address
specification
Option
specification
IP address
IP address input form Select the input format for the IP address.
Setting range/options
(Target station IP address)
Decimal/hexadecimal
Host name
Specify the host name for the PING test target station.
Results are displayed using the host name corresponding to the IP address in
the result display field.
Specify the data size Specify the size of the system data transmitted during the PING test.
1 to 30 s
Result
Success/transmissions
Display the total packet transmission count and the number of successes
during the PING test.
5 - 24
5 - 24
5 COMMUNICATION PROCEDURE
MELSEC-Q
(Address specification)
The PING test target station (external device subject to the PING test) is
specified by the IP address or the host name.
1)
2)
(Option specification)
Set the details for the PING test. (No setting required if the default is used.)
Selection item
1)
2)
3)
4)
Remarks
Transmission count: 1 to 50 times
(default: 4 times)
(Result)
Results of the PING test are displayed.
5 - 25
5 COMMUNICATION PROCEDURE
MELSEC-Q
The PING test is used to check the existence of an Ethernet module on the
same Ethernet line as the connection station of GX Developer that has
completed the initial processing ( 1) or an external device (such as a
personal computer) with the designated IP address.
1 The PING test can also be performed for the QnA/A Series Ethernet
modules. However, the PING test can be performed for the following A
Series Ethernet modules starting with software version S:
AJ71E71, AJ71E71-B2, AJ71E71-B5
(b)
The following items can be checked by performing the PING test for the
Ethernet module:
Whether a line has been properly connected to the test target Ethernet
module.
Whether the parameters for the Ethernet module have been correctly set.
Whether the initial processing for the Ethernet module has been
completed normally.
(c)
The PING test can be performed for an Ethernet module on the same
Ethernet as that of the local station (same sub-net address).
Note that the PING test is not available for the Ethernet module mounted on
the station to which GX Developer is directly connected (local station). (The
PING test addressed to the local station is not available.)
(d)
If the external device subject to the PING test is an Ethernet module, do not
designate the UDP port for GX Developer of the Ethernet module as a valid
port for the remote password check. If the port is designated as such, the
PING test cannot be performed.
Station number: 2
[10.97.85.222]
Ethernet
Network No. 1
QCPU Ethernet
1)
module
Station number: 1
[10.97.85.221]
5 - 26
5 - 26
5 COMMUNICATION PROCEDURE
(a)
Setting screen
MELSEC-Q
Setting item
Network type
Starting I/O No.
Network No.
Group No.
Station No.
IP address
2)
3)
Setting description
QCPU 1)
QCPU 2)
Ethernet
Ethernet
0000
0000
1
1
1
1
1
2
[10. 97. 85. 221]
[10. 97. 85. 222]
(b)
(c)
GX Developer
Ethernet line
Normal Normal
response response
Abnormal
response
Normal
response
Ethernet module
Normal response occurs when the PING test response is received
within the time of the communication time check.
5 - 27
5 - 27
5 COMMUNICATION PROCEDURE
MELSEC-Q
[Display contents]
Item name
Execute
station of
PING
Target of
PING
Option
specification
Network No.
Station No.
IP address
IP address input
form
Specify the time of
the communication
time
Specify the number
of transmissions
Result
Specify the network number of the Ethernet module in the PING executing
station.
Specify the station number of the Ethernet module in the PING executing
station.
Specify the IP address of the PING test target station.
1 to 239
1 to 64
00000001H to FFFFFFFEH
Decimal/hexadecimal
1 to 30 s
success/transmissions
Setting range/option
(Connection Setup)
1)
Execute station of PING (station connected to GX Developer)
Specify the network number and station number of the Ethernet module that will
execute the PING test.
The network number and the station number will be set on the " network
parameters setting the number of MNET/10H Ethernet cards" screen of GX
Developer.
2)
Target of PING
Specify the IP address of the PING test target station (the External device subject
to the PING test).
Select the input format of the IP address (select decimal or hexadecimal).
Specify the IP address of the PING test target station according to the input
format (decimal or hexadecimal).
5 - 28
5 - 28
5 COMMUNICATION PROCEDURE
MELSEC-Q
(1)
The loop back test is performed in the network for GX Developer connection
destination. The test involves transmission of loop back test messages in
order with respect to the network specified by the loop back test request
destination and all Ethernet modules within the station number range
(function version B and later) to check whether the initial processing for
each module has been completed.
A loop back test can be performed on a network connected via the
Ethernet board.
Since the Ethernet module of function version A and QnA/A series
Ethernet module do not have a function to respond to this request, the
test results cannot be checked.
GX Developer
5 - 29
Ethernet
module
Ethernet
module
Station No.: 7
Station No.: 9
Ethernet
module
Ethernet
module
Ethernet
module
Ethernet
module
Ethernet
module
Ethernet
module
Station No.: 2
Station No.: 4
Station No.: 6
Station No.: 8
Network No.1
(b)
(c)
The loop back test can be performed for an Ethernet module in the same
Ethernet as the local station (same sub-net address).
(d)
In the station on which the Ethernet module subject to the loop back test is
mounted, do not designate the UDP port for GX Developer of the Ethernet
module as a valid port for the remote password check. If it is designated as
a valid port for the remote password check, the loop back test cannot be
performed.
(e)
When performing a loop back test using GX Developer, set the router relay
function in the router relay parameter of GX Developer to "Not used."
5 - 29
5 COMMUNICATION PROCEDURE
MELSEC-Q
QCPU Ethernet
1)
module
Station No.: 1
[10.97.85.221]
(a)
Setting item
Operational setting
MNET/10 routing
information
2)
module
Station No.: 2
[10.97.85.222]
Set the following Ethernet module parameters for each PLC CPU
through GX Developer.
Use default values for setting items other than those listed below.
Setting description
QCPU 1)
QCPU 2)
Ethernet
Ethernet
0000
0000
Network No.
Group No.
Station No.
IP address
[10.97.85.221]
[10.97.85.222]
Network type
Network parameters
setting the number of
MNET/10H Ethernet
cards
QCPU Ethernet
Setting screen
Ethernet
MNET/10 routing
system
Network No.
Station No.
IP address
[10.97.85.223]
[10.97.85.223]
Remarks
It is not necessary to set the network No., station No. and IP address for
GX Developer (station performing the loop back test) when "Automatic
response system" is specified as the MNET/10 routing system under the
MNET/10 routing information.
5 - 30
2)
3)
5 - 30
5 COMMUNICATION PROCEDURE
MELSEC-Q
(b)
(c)
2)
Perform the settings indicated below, then click the Execute button.
The execution results of the loop back test are displayed.
[Display contents]
Item name
Setting item
5 - 31
Setting range/options
Network No.
Specify the network No. for the loop back test target module.
1 to 239
Number of
confirmation node
Specify the station number range for the loop back test target module.
1 to 64
Check at
communication time
Specify the response wait time for the loop back test.
1 to 99 s
5 - 31
5 COMMUNICATION PROCEDURE
MELSEC-Q
The IP address for the Ethernet module that has completed the loop
back test normally is displayed.
If the same IP address or station number has been set to multiple
stations due to a parameter setting error on the loop back test
target module side, only the results for the station that issued a
response first will be displayed.
2)
3)
If the local station is specified as a loop back test target station (station
performing a loop back test), "No response" will be displayed as the
loop back test results for the local station.
"No response" is not shown with GX Developer Version 6.03D or former products.
(d)
Display contents of
loop back test results
Cause
Corrective action
"IP address"
"No response"
5 - 32
No error
5 - 32
5 COMMUNICATION PROCEDURE
Display contents of
loop back test results
MELSEC-Q
Cause
IP address for the target Ethernet module is
incorrect. (Class or sub-net address differs from the
Ethernet module setting.)
The same IP address has been set to multiple target
Ethernet modules.
Error exists
No error
"Error code"
Error exists
No error
"No response"
Corrective action
POINT
5 - 33
(1)
The loop back test can only be performed for the Ethernet module of function
version B and later.
Test results cannot be checked for the following modules. ("No response" will
be displayed. However, nothing is shown under the use of GX Developer
version 6.03D or former products.)
Also, they will not be counted in the total number of stations.
Ethernet module of function version A, QnA/A series Ethernet module
(This is because there is no function to respond to this request.)
Ethernet module that has not completed the initial processing
(This is because the initial processing has not been completed.)
If the Ethernet module of function version A or QnA/A series Ethernet
module that does not have a function to respond to the loop back test
receives a loop back test request, the following error codes will be stored
in the error log area of the buffer memory.
Error code 4080H in the case of an Ethernet module of function version
A or QnA series Ethernet module of function version B
Error code 50H in the case of a QnA series Ethernet module of function
version A or A series Ethernet module.
(2)
After checking the contents of the error and taking corrective actions for an
Ethernet module in which the loop back test has been completed abnormally,
reboot the station on which the Ethernet module is mounted.
With rebooting, the initial processing for the Ethernet module will be
performed.
Check the completion of the initial processing for the Ethernet module using
the PING test.
The PING test can also be performed on the "Loop back test" screen.
(3)
If an error code is displayed due to abnormal completion of the loop back test,
check the contents of the error corresponding to the error code, then take
corrective actions by referring to Section 11.3.3.
5 - 33
5 COMMUNICATION PROCEDURE
MELSEC-Q
Ethernet module)
The following example illustrates how to confirm the completion of the initial processing
by issuing the PING command to the local stations Ethernet module from an external
device connected on the same Ethernet. (In the example, the confirmation is made
between devices whose IP address class and sub-net address are identical.)
<Designation method>
ping IP address
<Example>
IP address of the Ethernet module: 192.0.1.254
Example of screen at normal completion
C:\>ping 192.0.1.254Execute the ping command
Pinging 192.0.1.254 with 32 bytes of data:
Reply from 192.0.1.254: bytes=32 time=1ms TTL=128
Reply from 192.0.1.254: bytes=32 time<10ms TTL=128
Reply from 192.0.1.254: bytes=32 time<10ms TTL=128
Reply from 192.0.1.254: bytes=32 time<10ms TTL=128
Ping statistics for 192.0.1.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
C:\>_
Example of screen at abnormal completion
C:\>ping 192.0.1.254Execute the ping command
Pinging 192.0.1.254 with 32 bytes of data:
Request timed out:
Request timed out:
Request timed out:
Request timed out:
Ping statistics for 192.0.1.254:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\>_
5 - 34
5 - 34
5 COMMUNICATION PROCEDURE
MELSEC-Q
(2)
(3)
This function can only be used for the Ethernet module of the local station. The
function cannot be used for the Ethernet module of another station via a network
system.
(Station sending a loop back test command)
Ethernet
QCPU
5 - 35
Ethernet
module
QCPU
Ethernet
module
QCPU
5 - 35
5 COMMUNICATION PROCEDURE
MELSEC-Q
Description of setting
Setting range/options
TCP/IP
UDP/IP
Open system
Fixed buffer
Send
Receive
Procedure exist
No procedure
Pairing open
Pairs
No pairs
Existence confirmation
No confirm
Confirm
Destination IP address
1H to FFFFFFFFH
(FFFFFFFFH: Simultaneous Broadcast)
401H to FFFFH
(FFFFH: Simultaneous Broadcast, can be
set only when receiving)
Protocol
5 - 36
Active open
Unpassive open
Fullpassive open
MELSOFT connection
OPS connection
5 - 36
5 COMMUNICATION PROCEDURE
MELSEC-Q
(1) Protocol
(connection numbers 1 to 8; addresses: 20H to 27H b8)
(connection numbers 9 to 16; addresses: System area is used)
(a)
Name of setting
Description of setting
TCP
UDP
(b)
Select the connection open system for each connection for which "TCP" is
selected in "(1) Protocol". If "UDP" is selected, the specification of this item
is not required.
Name of setting
Description of setting
Active
Unpassive
Fullpassive
MELSOFT connection
1 2 3
OPS connection
Perform active open processing to an external device that waits for a passive open
(Fullpassive/Unpassive) on the TCP connection.
Perform passive open processing on the TCP connection addressing all the devices connected
to a network.
(The local station is placed in the wait status to wait for an Active open request to be sent.
Perform passive open processing on the TCP connection, only addressing specific devices.
(The local station is placed in the wait status to wait for an Active open request to be sent.)
The local station waits for an Active open request from the opposite station set in "(8)
Destination IP address".
Used to connect MELSOFT products via TCP/IP communication.
Perform passive open processing on the TCP connection, addressing all the MELSOFT
products connected to a network.
(The local station is placed in the wait status for an Active open request to be sent.)
Used to connect the OPS via TCP/IP communication.
Perform passive open processing on the TCP connection, addressing only specific OPSs. (The
local station waits for an Active open request from the OPS set in "(8) Destination IP address".)
1 Regardless of the initial timing setting in the operation setting (refer to Section 4.7),
this connection will always wait for the open status.
2 The set connection is dedicated to data communication with the MELSOFT products.
3 When simultaneously connecting to multiple MELSOFT products, set the connections
as many as the number of MELSOFT products. (Setting is unnecessary when only
one product is connected. The connection dedicated to the system is used.)
4 When using the MELSOFT product, such as GX Developer, on the OPS to make
TCP/IP communication with the Ethernet module, use the dedicated connection for
system (GX Developer communication TCP port) or set "MELSOFT connection" in
this setting.
PLC CPU
Initial processing
Initial
completion
Fullpassive/
Unpassive
open
Ethernet module
Ethernet module
Initial request
Initial request
Initial completion
Initial completion
Open
Initial processing
Initial processing
completion
Active open
Open request
Open completion
Open completion
Open completion
5 - 37
PLC CPU
Open completion
5 - 37
5 COMMUNICATION PROCEDURE
MELSEC-Q
Name of setting
Description of setting
Send
Receive
For receiving.
(b)
When both sending and receiving are performed with an external device
using fixed buffer communication, one buffer for sending and one for
receiving are required. Thus, two connections should be set.
(c)
Whether the fixed buffers are set for sending or receiving, external devices
can communicate using the MC protocol or the random access buffers.
For this item, select the communication method when communicating using
the fixed buffers.
Name of setting
Description of setting
In fixed buffer communication, data is communicated in 1:1 by handshaking with the
external device.
Communication using the MC protocol and the random access buffers can be
performed as well.
Procedure exist
No procedure
Name of setting
5 - 38
Description of setting
No pairs
Pairs
5 - 38
5 COMMUNICATION PROCEDURE
MELSEC-Q
This setting selects whether or not the Ethernet module should confirm that
an external device still operates normally when there is no communication
for a fixed period of time. The open processing for the connection with the
external device must have been completed.
Name of setting
Description of setting
No confirm
Confirm
(b)
(c)
(d)
5 - 39
(a)
In this item the port number of each connection for the Ethernet module is
set in hexadecimal.
(b)
The setting values are designated in a range from 401H to 1387H and from
138BH to FFFEH. Set port numbers that are not already used by other port.
(Port numbers 1388H to 138AH cannot be designated because they are
used by the operating system of the Ethernet module.)
(c)
Set the port numbers for the Ethernet module upon consulting a network
administrator.
5 - 39
5 COMMUNICATION PROCEDURE
MELSEC-Q
5 - 40
(b)
Set the IP addresses (two words) for external devices in the chosen input
format (decimal/hexadecimal).
(c)
The IP addresses of external devices must be given values other than 0H.
Furthermore, FFFFFFFFH is the setting value for simultaneous broadcast
communication.
(d)
5 - 40
5 COMMUNICATION PROCEDURE
MELSEC-Q
Set the port numbers of the external devices for each connection in
hexadecimal.
(b)
The port numbers of the external devices are set in a range from 401H to
FFFFH. Furthermore, FFFFH is the setting value for simultaneous broadcast
communication.
(c)
Set the port numbers for the external device upon consulting a network
administrator.
(d)
Description of connection
Communication
protocol
TCP
UDP
External device
Ethernet module
External device
External device
Ethernet module
External device
Ethernet module
External device
Ethernet module
External device
Ethernet module
External device
Ethernet module
External device
Important
Parameters for connections that communicate by Passive open and UDP open
must always be set from this screen when "Always wait for OPEN (communication
possible at STOP time)" is selected in the Operational settings (see Section 4.7).
5 - 41
5 - 41
5 COMMUNICATION PROCEDURE
MELSEC-Q
POINT
Set parameters according to the open method to be used for open connection.
Communication system
open system
TCP
UDP
Active
Passive
ARP function of
external device
Yes
Parameter
Un-passive
No
Full-passive
ARP function of
external device
Yes
No
Communication
Destination Port
address
No.
Destination
Ethernet address
2
(
)
5 - 42
5 - 42
5 COMMUNICATION PROCEDURE
MELSEC-Q
(b)
2)
(c)
In order to perform the open processing, the initial processing must have
been completed.
(d)
(e)
POINT
During communication using the MC protocol or random access buffers, if data
communication still continues even after the PLC CPU in a station where an
Ethernet module is installed has been placed in the STOP status, set "Always wait
for OPEN (communication possible at STOP time)" under "Initial timing setting"
(see 4.7, "Operation Settings").
5 - 43
5 - 43
5 COMMUNICATION PROCEDURE
MELSEC-Q
(b)
(c)
Perform the close processing for connections that have been established by
the open processing using sequence programs.
(d)
The examples in the following sections describe the procedures for establishing a
connection from the Ethernet module to an external device and subsequently closing it
again by open and close processing for connection number 1.
TCP/IP Active open
: See 5.6.1, "Active open processing/close processing".
TCP/IP Passive open : See 5.6.2, "Passive open processing/close processing".
UDP/IP Open
: See 5.6.3, "UDP/IP open processing/close processing".
Important
Never execute the open/close processing to the same connection using the
input/input signals and use together with dedicated OPEN/CLOSE instructions for
OPEN/CLOSE processing. It may result in malfunctions.
POINT
Except when the close processing is requested, the open completion signal
(address: applicable bit of 5000H) automatically turns off and the communication
line is closed in the following cases:
(1) When the existence confirmation function times out occur (see Section 5.5).
( 1)
5 - 44
(2)
(3)
When the Active open request is received again from the external device in
the open completion status of TCP.
Depending on its version, the Ethernet module operates as described below.
(a) Ethernet module whose first 5 digits of the serial No. are 05051 or later
After returning ACK to the external device, the Ethernet module closes
the connection when the RST command is received from the external
device.
(b) Ethernet module whose first 5 digits of the serial No. are 05049 or earlier
After sending the RST command, the Ethernet module closes the
connection.
However, when receiving the Active open request again from the external
device with a different IP address or port No., the Ethernet module only sends
the RST command. (It does not close the connection.)
5 - 44
5 COMMUNICATION PROCEDURE
MELSEC-Q
"U0" K1
D0
M0
M1
Processing for normal completion
M1
Processing for abnormal completion
M101
Processing for normal completion
M101
Processing for abnormal completion
Power-on
Open status
Parameter
communication
completed
1)
Closed status
5)
CLOSE instruction
One scan
SYN
3)
4)
SYN + ACK
5 - 45
6)
7)
FIN + ACK
5 - 45
5 COMMUNICATION PROCEDURE
MELSEC-Q
1)
2)
3)
4)
:
:
:
:
ON
ON
OFF
0000H
6)
:
:
:
:
5 - 46
OFF
ON
OFF
0000H
4)
OFF
ON
ON
Value other than
0000H
5 - 46
5 COMMUNICATION PROCEDURE
MELSEC-Q
POINT
This example uses connection number 1 for explanation. Use the corresponding
signals and bits for other connection numbers.
1 The end code at completion is stored in the dedicated instruction
complete status area. For details on the dedicated instructions, see
Chapter 10, "Dedicated Instructions".
2 Processing when the open processing is abnormally completed (TCP)
When opening from the Ethernet module under a normal situation, if the
Ethernet module sends a SYN, the external device returns an ACK and
a SYN.
However, if the Ethernet module sends a SYN and then the external
device returns a RST, the open abnormal completion (X18) is
immediately turned on and open processing ends.
3 The open status and error code at abnormal end can be confirmed with
the following buffer memory.
Each connection open abnormal code area of the communication
status storage area
(Connection numbers 1 to 8; addresses: 78H to C7H)
(Connection numbers 9 to 16; addresses: 5020H to 586FH)
Error log area (addresses: E0H to 177H)
Error codes stored in the open abnormal code area are cleared
(n 0) when the dedicated OPEN instruction is executed again.
4 Processing when the close processing is abnormally completed (TCP)
When closing normally from the Ethernet module, the Ethernet module
sends a FIN request and the external device returns an ACK and a FIN.
However, if an ACK and a FIN are not returned because the external
device is faulty, the Ethernet module forcefully disconnects the
connection (send a RST message).
PLC CPU
1)
2)
Ethernet
module
7)
Ethernet
At normal completion
FIN
5 - 47
4)
ACK
FIN
6)
RST
5 - 47
5 COMMUNICATION PROCEDURE
MELSEC-Q
1)
2)
3)
4)
The external device sends back FIN and ACK messages in reply to the
FIN request sent by the Ethernet module.
(When the reply is not returned, the Ethernet module sends the FIN
request again.)
5)
The Ethernet module waits for the external device to send an ACK and
a FIN.
(The module waits for the amount of time set in the TCP end timer
value. For details on how to set it, see Section 5.2, "Initial Settings".)
If the ACK and FIN messages are received at this point, it returns an
ACK as in the normal processing.
6)
If an ACK and a FIN are not received within the time designated in the
TCP end timer value, an RST message is sent to the external device.
7)
REMARK
(1) When the procedure above is performed, the Ethernet module determines that
the closing of the external device is executed normally, thus the close
processing result is not stored in the error log area.
(2) The procedure described above is a special function of the Ethernet module; it
is not available for general TCP/IP protocols.
5 - 48
5 - 48
5 COMMUNICATION PROCEDURE
MELSEC-Q
Program example
This example explains a program for open processing/close processing when
Active open is selected in the Open system setting.
The Ethernet module is installed in the "0" slot of the basic base unit.
(b)
(c)
: 1000H
: 0A.61.55.DFH (10.97.85.223)
: 2000H
5 - 49
5 COMMUNICATION PROCEDURE
MELSEC-Q
(e)
(f)
(g)
For details on the dedicated OPEN instruction, see Chapter 10, "Dedicated
Instructions".
After each parameter is set from GX Developer and write to PLC CPU,
restart the PLC CPU and confirm the completion of the initial processing.
(b)
The Ethernet module performs the open processing for connection No. 1 to
the external device set in the [Open settings] or control data.
(c)
REMARK
The "U0\G20480" and "U0\G20482" codes shown in the program designate the
following areas in the buffer memory.
U0\G20480: Open completion signal storage area (address: 5000H (20480))
U0\G20482: Open request signal storage area (address: 5002H (20482))
5 - 50
5 - 50
5 COMMUNICATION PROCEDURE
MELSEC-Q
X19: Initial normal completion signal
M0: Connection 1 open completion signal
M20: Connection 1 open request signal
Open processing of connection No. 1
(TCP/IP Active open)
Read the open completion signal information
Read the open request signal information
Change the open command to pulse
Designate the control data for the OPEN instruction
5 - 51
5 - 51
5 COMMUNICATION PROCEDURE
MELSEC-Q
(1) When "Always wait for OPEN" is selected in the operational setting
When [Operational setting] - [Initial timing setting] - [Always wait for OPEN
(Communication possible at STOP time)] is selected from GX Developer, the
open processing/close processing is performed as explained below.
In this case, sequence programs for open processing and close processing are
not required because the Ethernet module keeps the connection in the always
wait for the OPEN status according to the [Open settings] parameter setting.
For detail on the [Open settings] parameter, see Section 5.5, "Open Settings".
Open status
Parameter
communication
1)
Power-on completed
( 1)
Close status
SYN + ACK
2)
SYN
5 - 52
FIN + ACK
3)
FIN
5 - 52
5 COMMUNICATION PROCEDURE
MELSEC-Q
1)
After the parameters are sent, the normal completion of the Ethernet
module initial processing is confirmed (Initial normal completion signal
(X19): ON)
After the initial processing is normally completed, the connection is
placed in the open allowed status and Ethernet module waits for an
open request from the external device.
2)
The Ethernet module starts the open processing upon receiving the
open request (SYN) from the external device.
When the open processing is normally completed, the open
completion signal (address: 5000H b0) turns on and data
communication is enabled.
3)
The Ethernet module starts the close processing upon receiving the
close request (FIN) from the external device.
When the close processing is completed, the open completion signal
turns off and data communication is disabled.
4)
REMARK
For Passive open connections for which [Always wait for OPEN (Communication
possible at STOP time)] is selected in [Operational settings], the connection
open/close processing of Ethernet module side is performed according to the
open/close request from the external device.
When the close processing is performed from the Ethernet module side using the
dedicated CLOSE instruction, the applicable connection will not return to the open
acknowledge enabled status after the close processing. (It requires the same open
processing as for Passive open connection for which "Do not wait for OPEN
(Communications impossible at STOP time)" is selected).
5 - 53
5 - 53
5 COMMUNICATION PROCEDURE
MELSEC-Q
(2) When "Do not wait for OPEN" is selected in the operational setting
When [Operational setting] - [Initial timing setting] [Do not wait for OPEN
(communications impossible at STOP time)] is selected from GX Developer, the
open processing/close processing is performed as explained below.
Since open processing/close processing is executed by a sequence program, an
external device can be changed while the connection is established.
<<Open processing for connection No. 1
using the dedicated OPEN instruction>>
direction
Set the control data to D0 to D9
ZP.OPEN
M0
"U0" K1
D0
M0
M1
M101
Processing for normal completion
M101
Processing for abnormal completion
Open status
Parameter
communication
Power-on completed
1)
( 1)
Closed status
5)
CLOSE instruction
(For Open abnormal processing)
One scan
SYN + ACK
3)
SYN
5 - 54
FIN + ACK
4)
FIN
5 - 54
5 COMMUNICATION PROCEDURE
MELSEC-Q
1)
2)
3)
The Ethernet module starts the open processing upon receiving the
open request (SYN) from the external device.
At normal completion
Open completion signal (address: 5000H b0)
OPEN instruction complete device
OPEN instruction complete device + 1
OPEN instruction complete status area ( 2)
Data communication is enabled.
: ON
: ON
: OFF
: 0000H
At abnormal completion
Open completion signal
: OFF
OPEN instruction complete device
: ON
OPEN instruction complete device + 1
: ON
The open error code is stored in the buffer memory
OPEN instruction complete status area ( 2)
: Value other
than 0000H
Open abnormal detection signal (X18)
: ON
4)
The Ethernet module starts the close processing upon receiving the
close request (FIN) from the external device.
When the close processing is completed, the open completion signal
turns off and data communication is disabled.
5)
: OFF
: ON
: OFF
: 0000H
: OFF
: ON
: ON
: Value other
than 0000H
POINT
This example uses connection number 1 for explanation. Use the corresponding
signals and bits for other connection numbers.
5 - 55
5 - 55
5 COMMUNICATION PROCEDURE
MELSEC-Q
REMARK
5 - 56
(1)
(2)
5 - 56
5 COMMUNICATION PROCEDURE
MELSEC-Q
Program example
This example explains a program for open processing/close processing when
Unpassive open is selected in the open system setting.
The Ethernet module is installed in the "0" slot of the basic base unit.
(b)
(c)
The [Operational settings] parameters are assumed to have been set using
GX Developer as follows.
The [Open settings] are assumed to have been set using GX Developer as
follows.
: 2000H
5 - 57
5 COMMUNICATION PROCEDURE
MELSEC-Q
(e)
(f)
(g)
For details on the dedicated OPEN instruction, see Chapter 10, "Dedicated
Instructions".
After each parameter is set from GX Developer and write to PLC CPU,
restart the PLC CPU and confirm the completion of the initial processing.
(b)
(c)
REMARK
The "U0\G20480" and "U0\G20482" codes shown in the program designate the
following areas in the buffer memory.
U0\G20480: Open completion signal storage area (address: 5000H (20480))
U0\G20482: Open request signal storage area (address: 5002H (20482))
5 - 58
5 - 58
5 COMMUNICATION PROCEDURE
MELSEC-Q
X19: Initial normal completion signal
M0: Connection 1 open completion signal
M20: Connection 1 open request signal
Open processing of connection No. 1
(TCP/IP Unpassive open)
5 - 59
5 - 59
5 COMMUNICATION PROCEDURE
MELSEC-Q
REMARK
Even when "Always wait for OPEN (Communication possible at STOP time)" is
selected at "Operational settings", if there is a dedicated OPEN instruction from the
Ethernet mudule, open processing using the CLOSE instruction and close
processing, there is a need to perform all open processing and close processing
after the relevant connection using the sequence program.
If "Do not wait for OPEN (Communication impossible at STOP time) is selected,
there is a need to perform open processing and close processing in the same
manner as a connection.
(2) When "Do not wait for OPEN" is selected in the operational settings
(Communications impossible at STOP time)
In this case, the open processing and close processing in the sequence program
shown in the next page are required. Data transmission and reception are
enabled after the open processing is normally completed.
Perform the open processing and close processing using the applicable
dedicated instructions.
For more details, see Chapter 10, "Dedicated Instructions".
5 - 60
5 - 60
5 COMMUNICATION PROCEDURE
MELSEC-Q
"U0" K1
D0
M0
M1
Processing for normal completion
M1
Processing for abnormal completion
M101
Processing for normal completion
M101
Processing for abnormal completion
Power-on
Parameter
communication
completed
1)
Open status
Open allowed status
(closed)
Closed status
5)
CLOSE instruction
One scan
3)
4)
Internal
processing
5 - 61
6)
7)
Internal
processing
5 - 61
5 COMMUNICATION PROCEDURE
MELSEC-Q
1)
2)
3)
4)
:
:
:
:
ON
ON
OFF
0000H
6)
7)
:
:
:
:
OFF
ON
OFF
0000H
:
:
:
:
OFF
ON
ON
Value other than
0000H
5 - 62
5 - 62
5 COMMUNICATION PROCEDURE
MELSEC-Q
Port
External device
Receive data
POINT
5 - 63
(1)
When setting the pairing open method, the fixed buffer of the applicable
connection number (for receiving only) and the fixed buffer of the immediately
succeeding connection number (for sending only) are paired.
For the applicable connection (for receiving only), designate in ranges of
connection No. 1 to 7 and 9 to 15.
(2)
The range of external devices that can be communicated by the pairing open
method are limited to devices in the Ethernet to which the Ethernet module is
connected and devices connected with the router relay function (see Section
5.3, "Router Relay Parameter").
(3)
5 - 63
5 COMMUNICATION PROCEDURE
MELSEC-Q
(1) Protocol
Both "TCP/IP" and "UDP/IP" are allowed.
5 - 64
5 - 64
5 COMMUNICATION PROCEDURE
MELSEC-Q
(b)
5 - 65
(a)
(b)
5 - 65
5 COMMUNICATION PROCEDURE
MELSEC-Q
Ethernet
module
Ethernet
Request Response
Request Response
Open timing
The port opens automatically according to the parameters registered by the
user after the Ethernet module completes the initial processing, and the
communication line is connected.
(b)
Close timing
It automatically closes again when the station in which the Ethernet module
is installed is reset/powered off.
5 - 66
5 - 66
5 COMMUNICATION PROCEDURE
(b)
MELSEC-Q
POINT
(1)
(2)
(3)
(4)
(5)
Accessible range
Reference
section
Chapter 4 of
Application
5 - 67
Reference
section
The number of data that can be designated with the commands for the
QnA compatible 3E frame
Chapter 6
The number of data that can be designated with the commands for data
link
Chapter 4 of
Application
5 - 67
5 COMMUNICATION PROCEDURE
MELSEC-Q
5 - 68
5 - 68
5 COMMUNICATION PROCEDURE
MELSEC-Q
Station that the remote password and remote password check are set
1) In the case of single network system
Accessing source
external device
Ethernet
GX Developer
parameter setting
Remote password
Applicable connection for the remote
password check (See (3).)
Remote
password
QCPU
2)
Remote
password
check
Ethernet
module
(Local station)
Accessing source
external device
Ethernet
Remote password
QCPU
Remote
password check
Ethernet
module
Ethernet
module
(Local station)
Ethernet
Set in the local station to allow/
prohibit access from the external
device to the network system 1.
QCPU
Ethernet
Ethernet Ethernet
module module
(Relay
station)
QCPU
Ethernet (Station to
module be accessed)
Setting in a station other than the QCPU station that serves as the entrance to the
PLC system (relay station and station to be accessed in the above diagram), access
to other stations beyond the set station is prohibited. (See (3).)
5 - 69
5 - 69
5 COMMUNICATION PROCEDURE
(2)
2)
Access processing
Normal completion of the remote password unlock processing allows to
access the specified station.
Perform any access.
3)
1) Unlock processing
2) Access
Remote password
QCPU
MELSEC-Q
A station
( 1)
1) Unlock processing
Ethernet
3) Lock processing
Remote
password check (Local station)
Ethernet
module
A station
( 1)
Ethernet
3) Lock processing
Remote
password
Remote
password check
( 2)
QCPU
Ethernet
module
Ethernet
module
(Local station)
Ethernet
5 - 70
QCPU
Ethernet
module
Ethernet
module
(Relay station)
Ethernet
2) Access
QCPU
Ethernet
module
(Station to be accessed)
5 - 70
5 COMMUNICATION PROCEDURE
MELSEC-Q
POINT
(1)
The remote password unlock processing and lock processing are performed
for the only Ethernet module in the local station directly connected to the
external device.
The remote password unlock processing and lock processing cannot be
performed for an Ethernet module in any other station (relay station and
station to be accessed).
(2)
The remote password unlock processing and lock processing are performed from
the external device using dedicated instructions for MC protocol communication.
(They are performed with dedicated FTP commands when using the file
transfer (FTP server) function. The remote password is input with the dialog
box when using the Web function or GX Developer.)
(3)
5 - 71
When the following parameters have been set for the Ethernet module
mounted on the QCPU station, the Ethernet module performs a remote
password check for communication requests as indicated below:
When a remote password is set in the QCPU.
When the connection that is communicating data with the external
device is set as a target for the remote password check.
2)
3)
5 - 71
5 COMMUNICATION PROCEDURE
MELSEC-Q
Ethernet module
QCPU
Remote password
(Local station)
Remotepassword
check 1)
2)
(Other station)
3)
3)
GX Developer
QCPU
Remote
password
Remote
password check
( 1)
GX Developer
Ethernet module
(c)
5 - 72
2)
5 - 72
5 COMMUNICATION PROCEDURE
MELSEC-Q
(Example 1)
When a remote password is set in the QCPU station of the PLC system
station 1-1, and the remote password check is set in 1) of station 1-1
Station 1-2
1)
A station
QCPU
Ethernet
module
Ethernet
Network No.1
Station 1-1
Remote
password
B station
GX Developer
Ethernet
QCPU
1)
Remote
password
check
Ethernet
module
2)
QCPU
1)
Ethernet
module
1)
QCPU
Ethernet
module
Ethernet
module
Network No.2
Station 2-1
Station 3-2
Network No.3
Station 2-2
QCPU
1)
2)
Ethernet
module
Ethernet
module
Ethernet
Station 3-1
QCPU
1)
Ethernet
module
C station
D station
Network system -1
(Request destination)
(Request source)
External
device
2
( )
Station 1-2
QCPU
Station 2-1
QCPU
Station 2-2
QCPU
Station 3-1
QCPU
Station 3-2
QCPU
A station
B station
C station
D station
: Stations that can be accessed form the external device after the remote password unlock processing
: Stations that can be accessed from the external device without performing the remote password unlock
processing
2 A station can access the stations after the remote password unlock processing
for the module 1) of station 1-1 is completed. The stations can be accessed if
the communication line is open. B station, C station and D station can access the
stations if the communication line to those stations is open.
5 - 73
5 - 73
5 COMMUNICATION PROCEDURE
MELSEC-Q
(Example 2)
When a remote password and the remote password check are set in
multiple QCPU stations in the PLC system
Station 1-2
1)
A station
QCPU
Ethernet
module
Ethernet
Network No.1
Station 1-1
Remote
password
B station
GX Developer
Ethernet
QCPU
1)
Remote
password
check
Ethernet
module
2)
QCPU
1)
Ethernet
module
Remote
password
Remote
password
check
Ethernet
module
QCPU
Network No.3
Station 2-2
Remote
password
QCPU
C station
1)
Ethernet
module
Network No.2
Station 2-1
Station 3-2
2)
1)
Remote
password
check
Ethernet
module
Ethernet
Station 3-1
QCPU
Ethernet
module
1)
Ethernet
module
D station
Network system -1
(Request destination)
(Request source)
External
device
3
( )
Station 1-2
QCPU
Station 2-1
QCPU
Station 2-2
QCPU
Station 3-1
QCPU
Station 3-2
QCPU
A station
B station
C station
D station
: Stations that can be accessed form the external device after the remote password unlock processing
: Stations that can be accessed from the external device without performing the remote password unlock
processing
: Stations that cannot be accessed from the external device
3 A station can access the stations after the remote password unlock processing
for the module 1) of station 1-1 is completed. The stations can be accessed if
the communication line is open.
B station can access the stations if the communication line to those stations is
open.
C station can access the stations after the remote password unlock processing
for the module 1) of station 2-2 is completed. The stations can be accessed if
the communication line is open.
D station can access the stations after the remote password unlock processing
for the module 1) of station 3-2 is completed. The stations can be accessed if
the communication line is open.
5 - 74
5 - 74
5 COMMUNICATION PROCEDURE
MELSEC-Q
POINT
To prohibit access to another station from the external device using the Ethernet
module MELSECNET/H, MELSECNET/10 relay communication function, place a
check mark at the following setting items in the remote password setting for the
relay station and station to be accessed.
"GX Developer communication port (UDP/IP) ( ), dedicated instructions,
MELSECNET/H, MELSECNET/10 relay communication port"
Set this on the remote password setting screen of GX Developer.
Other stations can be accessed if a check mark is not placed in the above
setting items.
5 - 75
5 - 75
5 COMMUNICATION PROCEDURE
MELSEC-Q
After a remote password is set in the QCPU, reboot the QCPU (PLC No.1 for a
multiple CPU system) (reset using the RESET/L.CLR switch or power reset).
By rebooting the QCPU, the remote password becomes valid.
(2)
Set the remote password check to only the connection to be used in data
communication with the external device that can perform the unlock processing
and lock processing.
(Example) The remote password check should not be set in the reception
connection for receiving data transmitted from the MELSEC PLC CPU
when communicating by fixed buffer.
A check mark should not be placed at the applicable connection on
the "Remote password detail settings" screen shown in Section
5.9.5.
(3)
The remote password check should not be set, since the remote password check
is not performed for the connection performing communication using a nonprocedure fixed buffer.
(4)
When the external device accesses the PLC other station via the Ethernet
module, it may not be able to access the PLC if a remote password has been set
in the QCPU of the relay station or station to be accessed. (See Section 5.9.1 (1)
and (3).)
(5)
(6)
5 - 76
1)
2)
5 - 76
5 COMMUNICATION PROCEDURE
MELSEC-Q
Set the target connection for the remote password check in the "Remote
password detail settings" through GX Developer and write the parameters in the
QCPU. (See Section 5.9.5.)
(2)
After booting the QCPU, write the setting values to the following buffer memory in
the Ethernet module as necessary: (See Section 5.9.6 (3).)
Accumulated count designation area for remote password mismatch notification
Address 20592 to 20593 (5070H to 5071H)
(3)
The remote password unlock (release) processing is performed after the open
processing for the connection is completed.
All data received before the unlock processing will be processed as an error.
(See the troubleshooting section for error codes.)
(4)
When the unlock processing for the remote password is performed from the
external device, the specified station can be accessed from the external device if
the remote password specified by the user matches the remote password set in
the local station QCPU.
(5)
(6)
The remote password unlock processing and lock processing are performed from
the external device connected to the Ethernet module using the dedicated
instructions for MC protocol communication. (They are performed with dedicated
FTP commands when using the file transfer (FTP server) function. The remote
password is input with the dialog box when using the Web function or GX
Developer.)
REMARK
When the "GX Developer communication port" is set as the remote password check
connection, access the PLC after performing the unlock processing on the GX
Developer screen shown when access begins.
(7)
5 - 77
The remote password unlock and lock processing can only be performed for the
local station QCPU on which the Ethernet module is mounted. The remote
password unlock and lock processing cannot be performed for other station
QCPU. (See Section 5.9.1 (2).)
5 - 77
5 COMMUNICATION PROCEDURE
MELSEC-Q
...
Initial processing
Open processing
Automatically processed
(Communication No.1 to 16
for user)
Communication
using tne MC
protocol
Communication
using fixed
buffer
Communication
using random
access buffer
E-mail
sending/
receiving
MELSECNET/H,
MELSECNET/10
relay
communication
(: 1)
Remote password
unlock processing
File transfer
Communication
using Web
function
Communication
using
GX Developer
Remote password
lock processing
Remote password
lock processing
(FTP)
Remote password
unlock processing
( 1)
Remote password
lock processing
Close processing
Communication
using data
link
instructions
Remote password
unlock processing
1 When accessing the PLC of other station, access to the other station may not be
allowed if a remote password is set in the QCPU of the relay station on which the
Ethernet module is mounted and the station to be accessed. (See Section 5.9.1
(1) and (3).)
POINT
5 - 78
(1)
(2)
5 - 78
5 COMMUNICATION PROCEDURE
MELSEC-Q
5.9.4 When the remote password unlock processing or lock processing is completed
abnormally
This section explains the procedures to be performed by the user when the remote
password unlock processing or lock processing is completed abnormally.
5 - 79
(1)
Perform the unlock/lock processing again after checking the remote password set
in the QCPU.
(2)
The Ethernet module performs the following when the number of occurrence
times for an unlock processing/lock processing abnormal completion is greater
than the accumulated notification count ( 1) set in the buffer memory.
(a)
(b)
The code C200H is stored in the error code and end code storage area of
the buffer memory error log area (address 227 to 372 (E3H to 174H)).
1 This is the count set from the QCPU in the remote password mismatch
notification accumulated count designation area (address 20592
(5070H), 20593 (5071H)) when the Ethernet module starts up. (Count is
set with T0 instruction, etc.)
(3)
Monitor the above buffer memory when the COM.ERR LED of the Ethernet
module lights up.
If the error code C200H is stored, monitor the storage area for abnormal
completion accumulated count in the buffer memory (address 20595 (5073H),
20597 (5075H), ) and check for which connection the unlock processing or
lock processing has been completed abnormally.
(4)
(b)
Write "0" in the storage area for abnormal completion accumulated count in
the buffer memory.
If the accumulated count is not cleared by writing "0", the process in (2)
above is performed each time an abnormal completion in excess of the
accumulated notification count occurs.
(c)
(d)
Inform the system manager that the number of occurrence times for an
unlock processing/lock processing abnormal completion is greater than the
accumulated notification count and take appropriate actions.
5 - 79
5 COMMUNICATION PROCEDURE
MELSEC-Q
REMARK
5 - 80
(1)
The following accumulated counts stored in the buffer memory can be cleared
under the user's option. (Write "0" to the applicable area from the QCPU.)
Storage area for unlock processing normal completion accumulated count:
Address 20594 (5072H)
Storage area for lock processing normal completion accumulated count:
Address 20596 (5074H)
(2)
See Section 11.1.2 of User's Manual (Basic) for how to turn off the COM.ERR
LED for the Ethernet module after it has lit up.
5 - 80
5 COMMUNICATION PROCEDURE
MELSEC-Q
5.9.5 How to set the target connection for the remote password check
Set the connection for the remote password check with the parameter settings through
GX Developer.
[Startup procedure]
"GX Developer"
Detail
Remote password
[Setting screen]
[Setting items]
Item name
Password settings
Password
active module
settings
).
Model name
Select the model name for the module performing the check for the remote
password set in the QCPU.
Start XY
Set the head address of the module performing the remote password check.
Module condition
Setting range/options
QJ71E71
0000H to 0FE0H
Detail settings
GX Developer
transmission port
(TCP/IP)
GX Developer
transmission port
(UCP/IP)
HTTP port
5 - 81
5 - 81
5 COMMUNICATION PROCEDURE
MELSEC-Q
POINT
5 - 82
(1)
When using the Ethernet module in a multiple CPU system, set the remote
password by writing it to the control PLC of the Ethernet module.
(2)
After the remote password is set in the QCPU, reboot the QCPU (the first
QCPU module for a multiple CPU system) (reset using the RESET/L.CLR
switch or power reset).
By rebooting the QCPU, the remote password becomes valid.
(3)
5 - 82
5 COMMUNICATION PROCEDURE
MELSEC-Q
20486 (5006H)
20487 (5007H)
20488 (5008H)
20592 (5070H)
20593 (5071H)
20594 (5072H)
20595 (5073H)
20596 (5074H)
20597 (5075H)
Connection
No. 1
20669 (50BDH)
20671
20672 (50C0H)
:
Accumulated count unlock process normal completion
Connection
No. 16
20673 (50C1H)
20674 (50C2H)
20675 (50C3H)
Connection for
20676 (50C4H)
automatic open
20677 (50C5H)
UDP port
20678 (50C6H)
20679 (50C7H)
Connection for
20680 (50C8H)
GX Developer
20681 (50C9H)
communication
20682 (50CAH)
(for UDP/IP
20683 (50CBH)
communication)
20684 (50CCH)
Connection for
20685 (50CDH)
GX Developer
20686 (50CEH)
communication
20687 (50CFH)
(for TCP/IP
20688 (50D0H)
communication)
20689 (50D1H)
20690 (50D2H)
Connection for
20691 (50D3H)
FTP
20692 (50D4H)
communication
20693 (50D5H)
5 - 83
Monitor
(50BFH)
Setting
20598 (5076H)
20670 (50BEH)
Application
5 - 83
5 COMMUNICATION PROCEDURE
MELSEC-Q
The current unlock/lock status of the remote password for each connection
is stored.
The unlock/lock status for connection No. 1 to No. 16 that use the user port
is stored in the address 20486.
The unlock/lock status for connections that use the system port is stored in
the address 20487.
(b)
b8
b7
b6
b5
b4
b3
b2
b1
b0
1/0 1/0 1/0 1/0 1/0 1/0 1/0 1/0 1/0 1/0 1/0 1/0 1/0 1/0 1/0
Status of connection No. 1
20487
b8
b6
b5
b4
b3
b2
b1
b0
(2)
(b)
b8
b7
b6
b5
b4
b3
b2
b1
b0
(c)
5 - 84
GX Developer
communication port
(For UDP/IP communication)
If the remote password check is performed and the remote password status
of the connection using the applicable port is in the lock status, the use of
the applicable port can be prohibited.
5 - 84
5 COMMUNICATION PROCEDURE
(d)
MELSEC-Q
If improper access from the opposite device has been performed during the
above data communication, set the applicable port to "use prohibited." (See
Section 5.9.4 for details.)
REMARK
To prohibit data communication from the opposite device using the Ethernet module
FTP function, set "Not used" in the FTP function setting item under the "Setting the
Ethernet FTP parameters" through GX Developer. (See Section 5.3 of User's
Manual (Application).)
(3)
5 - 85
Use 0 to FFFFH to designate the count that will be the notification timing to
the user when the number of occurrence of remote password mismatches
become the permit or more during the unlock/lock processing from the
user/external device after the Ethernet module starts up. (This designation
is common to all connections.)
0H: No designation
(The process (c) when a remote password mismatch occurs is not
performed.)
1 to FFFFH: Notification accumulated count
(b)
(c)
(d)
5 - 85
5 COMMUNICATION PROCEDURE
MELSEC-Q
(b)
The user should clear the value stored in each of the accumulated count
storage areas. (Write "0" to the applicable area from the QCPU.)
(5) Storage area for accumulated count of lock process based on close
(Address 20598 (5076H) )
(a)
When the user closes the applicable connection without performing the
remote password lock processing, the Ethernet module will automatically
perform the lock processing.
The accumulated number of times the Ethernet module performed the lock
processing automatically is stored in this area.
(b)
The user should clear the value stored in this accumulated count storage
area. (Write "0" to the applicable area from the QCPU.)
POINT
The maximum value that can be stored in the areas indicated in (4) and (5) above
is FFFFH. An accumulated count that exceeds FFFFH (65535) is not stored.
5 - 86
5 - 86
5 COMMUNICATION PROCEDURE
MELSEC-Q
Communication
using the MC
protocol
User open
port
Automatic
open UDP
port
There is a
procedure
Communication
using the fixed
buffer
Non
procedure
Sending/receiving of e-mail
Remarks
See Chapter 5 of
User's Manual
(Application).
1 See Section 5.9.1 (3) for access to the PLC of other stations.
2 A dedicated connection is used for the non-procedure fixed buffer communication.
Do not perform the remote password setting for the applicable connection.
3 If a remote password has been set in the QCPUs of the relay station and access
station where Ethernet modules are installed, when accessing other station's PLC,
it may not be possible to access other stations. (See items (1) and (3) in Section
5.9.1.)
5 - 87
5 - 87
5 COMMUNICATION PROCEDURE
MELSEC-Q
10BASE-T/100BASE-TX,
Full duplex/half duplex
Hub
Ethernet module
External device
3)
2)
b0
to
1)
1) Communication mode
0: Half duplex
1: Full duplex
2) Hub connection status
0: Hub not connected/disconnected
1: Hub connected
3) Data transmission speed
0: Operating at 10BASE-T
1: Operating at 100BASE-TX
(Bits other than above are reserved for system use.)
5 - 88
(a)
(b)
5 - 88
5 COMMUNICATION PROCEDURE
MELSEC-Q
Communication
error occurrence
System switching
request
Tracking cable
Existence check
ULP timeout
Disconnection detection
5 - 89
Description
After the connection is opened (after open processing),
the existence of the external device cannot be checked.
There is no ACK response from the external device
within the TCP ULP timer value.
The cable connected to the Ethernet module was
disconnected. (QJ71E71-100 only)
5 - 89
5 COMMUNICATION PROCEDURE
MELSEC-Q
POINT
When any of the system switching request issuing conditions indicated in (2) of this
section is satisfied, the system is switched between the control system and standby
system. In either of the following cases, however, the system will not be switched if
the system switching request is issued from the Ethernet module.
The standby system is already in a faulty status (e.g. power-off, reset or stop
error) (For the reasons for system switching, refer to the QnPRHCPU User's
Manual (Redundant System).)
The network module redundant group settings have been mode for Ethernet
modules and either one is operating normally (For the "network module
redundant group setting", refer to the QnPRHCPU User's Manual (Redundant
System).)
(b)
5 - 90
Description
After the connection is opened (after open processing), the
existence of the external device cannot be checked.
There is no ACK response from the external device within
the TCP ULP timer value.
"Target connection"
A communication error is detected on the connections set in the "system
switching settings when communication error occurs" in the redundant
setting of GX Developer. (Refer to Section 5.11.3 for the redundant
settings.)
The following connections can be the targets of monitoring.
Connection No. 1 to 16
Automatic open UDP port
FTP communication port
GX Developer communication port (TCP, UDP)
HTTP communication port
5 - 90
5 COMMUNICATION PROCEDURE
(c)
External device
Normal communication
MELSEC-Q
Tracking cable
External device
Communication
error occurrence
2) At error detection ( 2)
When the Ethernet module mounted on
the main base unit of the control system
CPU detects the communication error that
occurred between the external device and
Ethernet module, it issues a system
switching request to the control system
CPU. ( 3)
Tracking cable
System switching
request
External device
Normal communication
Tracking cable
5 - 91
5 - 91
5 COMMUNICATION PROCEDURE
MELSEC-Q
1 By connecting the external device and the Ethernet module mounted on the main
base unit of the standby system CPU via TCP, a standby system CPU side error
can be detected.
2 System switching timing at communication error
The timing of issuing the system switching request to the control system CPU at a
communication error is shown below.
(a)
1)
2)
(b)
Existence
check
message
Existence
check
message
Existence
check
message
Target
existence
check starting
interval timer
value
Target
existence
check interval
timer value
Target
existence
check interval
timer value
BUFSND instruction
BUFSND instruction
completion device+1
ACK is not returned from external device
Ethernet module
Data
command
TCP resend
timer value
First retry
Second retry
TCP resend
timer value
TCP resend
timer value
1)
If ACK is not returned from the external device within the TCP ULP
timer period at TCP opening or data transmission, a transmission error
occurs and the Ethernet issues a system switching request to the
control system CPU. (Refer to Section 5.2.2 for the TCP ULP timer.)
(The above chart shows a setting example of two retries.)
3 Set whether the system switching request will be issued or not to the control
system CPU in the redundant settings of GX Developer. (Refer to Section 5.11.3.)
5 - 92
5 - 92
5 COMMUNICATION PROCEDURE
MELSEC-Q
External device
Disconnection
occurrence
1) Disconnection monitoring
The Ethernet module always checks the
connected cable for disconnection. ( 1)
The monitoring result is stored into the
hub connection status area (address: 201
(C9H)) of the buffer memory. (Refer to
Section 5.10.)
Tracking cable
External device
System switching
request
2) At disconnection detection ( 2)
When the Ethernet module mounted on
the main base unit of the control system
CPU detects disconnection, it executes a
disconnection status time check, and
when a disconnection status continues for
the period of cable disconnection timeout
setting, the Ethernet module issues a
system switching request to the control
system CPU. ( 3)
Tracking cable
5 - 93
5 COMMUNICATION PROCEDURE
MELSEC-Q
Tracking cable
1 When the cable is not connected from the start, the Ethernet module does not
regard it as disconnection. (Disconnection is detected only when normal status
turns to abnormal.)
2 System switching timing at disconnection detection
The timing of issuing a system switching request to the control system CPU at
disconnection detection is shown below.
Disconnection
occurrence
(Link down)
Ethernet
module
Disconnection
detection start
after initial
processing
completion
Cable connection
(Link up)
Disconnection
Cable disconnection
timeout
Disconnection
occurrence
(Link down)
Disconnection
Cable disconnection
timeout
System switching request issued
to control system CPU
1)
2)
3)
3 Set whether the system switching request will be issued or not to the control
system CPU in the redundant setting of GX Developer. (Refer to Section 5.11.3.)
5 - 94
5 - 94
5 COMMUNICATION PROCEDURE
MELSEC-Q
5 - 95
5 - 95
5 COMMUNICATION PROCEDURE
MELSEC-Q
Tracking cable
External device
Redundant
system-support
application
(1)
Communication
error occurrence
(2)
Tracking cable
5 - 96
5 - 96
5 COMMUNICATION PROCEDURE
MELSEC-Q
[Starting procedure]
[Setting the number of MNET/10H Ethernet cards]
"Redundant settings screen"
Redundant settings
[Setting screen]
[Setting items]
Item name
Description
System B settings
Set the station number and IP address of the Ethernet module mounted on the system B.
Set whether a system switching request will be issued or not to the control system CPU at
disconnection timeout
disconnection detection.
Set whether a system switching request will be issued or not to the control system CPU at
communication error
a communication error.
POINT
(1)
(2)
(3)
(4)
5 - 97
5 COMMUNICATION PROCEDURE
MELSEC-Q
Description
Set whether a system switching request will
be issued or not at disconnection detection.
Setting range/choices
Checked (System switching request is issued)
Not checked (System switching request is not
issued)
(Default: Checked)
Set the time from when disconnection is
0.0s to 30.0s
detected until the system switching request is (Default: 2.0s)
issued to the control system CPU.
POINT
Set the cable disconnection timeout setting to several seconds to several ten
seconds.
If it is shorter than the above, a system switching request may be generated due to
noise, etc.
Description
Set whether a system switching request will
be issued or not at communication error.
System switching
settings when
communication error
occurs 1 2 3
Setting range/choices
Checked (System switching request is issued)
Not checked (System switching request is not
issued)
(Default: Not checked)
Check the target connection.
(Default: Not checked)
1 The settings of the automatic open UDP port and GX Developer communication UDP
port are made valid when the following conditions are satisfied.
1) The remote password setting is valid.
2) The remote password is canceled.
When the above conditions are not satisfied, a system switching request is not issued
if a communication error occurs on the target connection.
2 Do not set the following connection as the target connection. (Do not check its check
box.)
Initial timing setting of operation setting : "Always waiting for OPEN (communication
enabled during STOP)"
Protocol of open setting
: "UDP"
Existence check of open setting
: "Check"
If the above connection is set as the target connection, system switching may occur
consecutively in the redundant system when a communication error occurs due to
cable disconnection or external device power-off.
3 It is recommended not to set the connection, which has been set to "MELSOFT
connection" in the open system of the open setting, as the target connection. (Do not
check the check box.)
If the above connection is set as the target connection, all the MELSOFT products
connected to the network will be targets, and therefore, the target external device
(MELSOFT product) cannot be identified.
5 - 98
5 - 98
5 COMMUNICATION PROCEDURE
MELSEC-Q
b8 b7
b6 b5
b4 b3
b2 b1
b0
Address: 21008(5210H)
Connection No. 1
Connection No. 2
Connection No. 16
to
b5 b4
b3 b2 b1 b0
(For system)
Automatic open UDP port
GX Developer communication
UDP port
GX Developer communication
TCP port
FTP communication port
HTTP communication port
MELSOFT connection included
5 - 99
5 - 99
5 COMMUNICATION PROCEDURE
MELSEC-Q
(b)
(c)
5 - 100
5 - 100
5 COMMUNICATION PROCEDURE
MELSEC-Q
(b)
(c)
POINT
When using the user connection for communication, it is recommended to prepare
the connections for communication with system A and for communication with
system B.
If a communication error occurs in the host system or the system switching occurs,
the above enables immediate communication with the other system.
On the Ethernet module, up to 16 user connections can be set.
5 - 101
5 - 101
5 COMMUNICATION PROCEDURE
MELSEC-Q
Access to
control system
Tracking cable
(System switching occurrence)
External device
QnA-compatible 3E frame
Request destination
module I/O No.
: 03D0H
Network No.
: 00H
PLC No.
: FFH
Access to control
system is continued
via tracking cable.
Tracking cable
Access to
standby system
QnA-compatible 3E frame
Request destination
module I/O No.
: 03D1H
Network No.
: 00H
PLC No.
: FFH
Accessible if communication
line is faulty
Tracking cable
5 - 102
5 - 102
5 COMMUNICATION PROCEDURE
(b)
MELSEC-Q
ON:
System A is control
system
Is SM1515 ON?
(Operation system type)
OFF: System A is standby system
Is SM1516 ON?
(Operation system type)
OFF
OFF
Is response message
normally terminated?
NO
NO
Is response message
normally terminated?
YES
YES
Is it repeated?
YES
Is it repeated?
NO
YES
NO
Close system A.
Close system B.
Close system A.
Close system B.
End
5 - 103
5 - 103
5 COMMUNICATION PROCEDURE
(c)
MELSEC-Q
Complete
5 - 104
5 - 104
5 COMMUNICATION PROCEDURE
MELSEC-Q
(b)
(c)
YES
NO
Receive a response from
system A.
YES
NO
Receive a response from
system B.
5 - 105
Error occurrence
5 - 105
5 COMMUNICATION PROCEDURE
MELSEC-Q
POINT
Note the following when executing re-transmission processing at system switching.
(1) When making communication while synchronizing transmission and reception
During communication, system switching may occur with transmission and
reception not synchronized.
When system switching has occurred, resume communication after initializing
synchronization to ensure safety.
(2) When using the dedicated instruction
Since whether the execution of the write instruction is completed or not is
difficult to judge, the same instruction must be executed again.
In this case, note that the same instruction may be executed twice.
5 - 106
Receive of e-mail
1) After receiving an e-mail by the Ethernet module, send a reply mail to
the mail transmission source so that the mail transmission source
confirms that it received the e-mail.
If receipt cannot be confirmed, send the e-mail again.
2) After the MRECV instruction is executed, the read e-mail is deleted
from the mail server. Therefore, when system switching occurs during
execution of the MRECV instruction, the mail may not be received by
the new control system CPU after system switching if the MRECV
instruction is re-executed. (The e-mail has been deleted from the mail
server.)
5 - 106
5 COMMUNICATION PROCEDURE
(b)
MELSEC-Q
(c)
5 - 107
5 - 107
5 COMMUNICATION PROCEDURE
MELSEC-Q
(b)
Ethernet
module
Station
No. 3
Network No. 2
Control system
QnPRH
CPU
Ethernet
module
Station
No. 1
Standby system
Ethernet
module
Station
No. 1
QnPRH
CPU
Ethernet
module
Station
No. 2
Ethernet
module
Station
No. 2
Network No. 1
Request destination
station
QCPU
Ethernet
module
Station
No. 3
Change the routing parameter setting with the RTWRITE instruction at the
relay source station or relay station so that access is made via the station of
the new control system after system switching when system switching
occurs. (For the RTWRITE instruction, refer to the QCPU (Q
Mode)/QnACPU Programming Manual (Common Instructions).)
Request source station
QCPU
Ethernet
module
Station
No. 3
Network No. 2
QnPRH
CPU
Change using
RTWRITE instruction.
Standby system
Ethernet
module
Station
No. 1
Control system
Ethernet
module
Station
No. 1
QnPRH
CPU
Ethernet
module
Station
No. 2
Ethernet
module
Station
No. 2
Network No. 1
Request destination
station
QCPU
5 - 108
Ethernet
module
Station
No. 3
5 - 108
5 COMMUNICATION PROCEDURE
MELSEC-Q
(8) "When QCPU accesses other station PLC using data link
instruction"
(a)
E71
Channel 3
Device
Control system
(Local station)
Device
Tracking cable
(b)
5 - 109
5 - 109
5 COMMUNICATION PROCEDURE
5 - 110
MELSEC-Q
(c)
SEND instruction
1) Execution of SEND instruction
When the target station is in a redundant system, the communication
request source station must identify that the target station is the control
system to execute the SEND instruction.
When the target station is the standby system, the target station
storage channel cannot be used since the RECV instruction is not
executed at the target station after data is sent by the SEND
instruction. (Channel being used)
2) When performing broadcast
When a redundant system exists on the network where a broadcast is
performed, the storage channel cannot be used since the RECV
instruction is not executed for the standby system. (Channel being
used)
(d)
5 - 110
5 COMMUNICATION PROCEDURE
MELSEC-Q
Complete
1
2
After writing a parameter file, simultaneously reset the both redundant CPUs.
When the operation status of the control system CPU is switched from STOP to
RUN, check the error status of the standby system CPU, and if an error has
occurred, set the error code (6010H) to SD50, and then turn on SM50 to clear the
error.
5 - 111
5 - 111
MELSEC-Q
6-1
6-1
MELSEC-Q
L
00H
FFH
0AH
Head device
IP
TCP
/
UDP
Subheader
PC ACPU
No. monitoring
timer
0CH
00H
80H
Text (response)
Complete code
TCP
/
UDP
Header
Ethernet
IP
Text (Command)
Number of
device points
Ethernet
Header
Subheader
(Example)
Read data
POINT
The following manual is available for performing data communication using the MC
protocol.
Q Corresponding MELSEC Communication Protocol Reference Manual (sold
separately)
6-2
6-2
MELSEC-Q
2)
3)
POINT
(1) By using the automatic open UDP ports of the Ethernet module,
communication using the MC protocol can be performed regardless of the
RUN/STOP status of the PLC CPU.
When the automatic open UDP ports are not used, connect the user open port
first and perform data communication referring to Chapter 4, "Settings and
Procedures Prior to Starting the Operation" and Chapter 5, "Communication
Procedure" of this manual.
(2) When writing from an external device to the PLC CPU, the enable/disable write
at CPU RUN time setting can be set using the GX Developer "Ethernet
operational settings" parameters.
When writing data to the remote I/O station of the MELSECNET/H, set the
enable/disable write at CPU RUN time parameter to "Enable".
6-3
6-3
MELSEC-Q
Number of
device points
Head device
Subcommand
Command
CPU
monitoring
timer
Request
data
length
Request destination
module station No.
Request
destination
module I/O No.
PC No.
Q header
Network No.
Subheader
Header
When the external device accesses the QPU in a multiple CPU system or redundant
system, specifying the target QCPU with the "request destination module I/O number"
in the QnA-compatible 3E frame for MC protocol enables access to the control CPU or
non-control CPU of the multiple CPU system or to the control system CPU/standby
system CPU or system A CPU/system B CPU of the redundant system.
Refer to the Reference Manual for details.
Refer to Chapter 2 of this manual for the system configuration.
(Example) When multiple system CPU No. 1 is specified
H L H L H L H L H L H L H L H L
H L H L
5 0 0 0 0 0 F F 0 3 E 0 0 0 0 0 1 8 0 0 1 0 0 4 0 1 0 0 0 1 M
0 0 0 1 0 0 0 0 0 8
35H 30H 30H 30H 30H 30H46H 46H 30H 33H 45H 30H 30H 30H 30H 30H 31H 38H 30H 30H 31H 30H30H 34H 30H 31H 30H 30H 30H 31H 4D H2AH 30H 30H 30H 31H 30H 30H 30H 30H 30H 38H
REMARK
When using the Ethernet module in a multiple CPU system, set the QCPU
controlling the Ethernet module (hereinafter referred to as the control CPU)
through GX Developer.
It is possible to mount an Ethernet module of function version A on a multiple CPU
system, in which case the access is limited to the control PLC (PLC No.1).
6-4
6-4
MELSEC-Q
6-5
6-5
MELSEC-Q
7 FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST
CONTROL METHOD)
This chapter explains how the PLC CPU and external device communicate in a 1:1
mode using the fixed buffers (with the procedure exist control method) of the Ethernet
module.
Fixed buffer
No. 1
External device
No. 2
No. 3
No. 4
PLC CPU
BUFRCV
instruction
to
No. 16
7-1
External device 1
External device 8
to
For sending to external
device 28
External device 28
7-1
MELSEC-Q
POINT
In communication where the procedure exist control method is selected, the data
can be communicated by the following methods after the open processing is
completed.
Fixed buffer communication with the procedure exist control method (sending or
receiving)
Communication using the random access buffers
Communication using the MC protocol
(3) At data sending/receiving, the Ethernet module performs the following processing.
(a)
At data sending
When the PLC CPU executes the dedicated BUFSND instruction ( 1) in a
sequence program, the Ethernet module sends data of the applicable fixed
buffer (No. n) to the external device that is specified in the communication
address setting area (addresses: 28H to 5FH and 5038H to 507FH)
corresponding to fixed buffer No. n ( 2).
(b)
At data receiving
The Ethernet module processes the received data if the data is received
from an external device set in the communication setting area that
corresponds to fixed buffer No. n. ( 2)
If data is received from an external device not set in the connection
information area of the buffer memory, the Ethernet module does not
request to read the receive data to the PLC CPU side.
1 For details on the dedicated instructions, see Chapter 10, "Dedicated
Instructions".
2 In case of TCP/IP Unpassive open, data is communicated with an
external device stored in the connection information area
corresponding to fixed buffer No. n.
POINT
When the Ethernet module stores the receive data in the corresponding fixed buffer
in the receive processing for the simultaneous broadcasting, it updates the
destination IP address and destination port No. in the connection information area
(addresses: 78H to C7H and 5820H to 586FH) that corresponds to fixed buffer No. n.
7-2
7-2
MELSEC-Q
7.2 Sending Control Method
This section explains the control method when data is sent from the Ethernet module
to an external device using the fixed buffer No. 1 and the area corresponding to
connection No. 1 as an example.
<<Data sending using the dedicated BUFSND instruction>>
Send data
[D100]: Word count for send data
From [D101]: Send data
direction
Set the send data in D100 and D101
ZP.BUFSND "U0" K1
M0
D0
D100
M0
M1
Processing for normal completion
M1
Processing for abnormal completion
Data sending
Response receiving
1)
2)
Open completion signal
(Address: 5000H [b0])
BUFSND instruction
3)
6)
One scan
ACK
(only TCP)
4)
7-3
Response
Data sending
ACK
(only TCP)
5)
7-3
MELSEC-Q
1)
2)
3)
4)
The size of send data in the fixed buffer (No. 1) area designated by the
send data length is sent to the designated external device (set in the
open processing).
5)
Upon receiving the data from the Ethernet module, the external device
returns a "Response" to the Ethernet module.
6)
Upon receiving the "Response" from the external device, the Ethernet
module ends the data transmission.
If the "Response" is not returned within the response monitoring timer
values (see Section 5.2), a data send error occurs.
At normal completion
BUFSND instruction complete device
:
BUFSND instruction complete device + 1
:
BUFSND instruction complete status area ( 2) :
Response end code ( 3)
:
ON
OFF
0000H
00H
At abnormal completion
BUFSND instruction complete device
: ON
BUFSND instruction complete device + 1
: ON
BUFSND instruction complete status area ( 2) : Value other than
0000H
Response end code ( 3)
: Value other than
00H
After the data transmission is abnormally completed, execute the
dedicated BUFSND instruction again to repeat the transmission
processing.
2 The status at completion is stored in the complete status area of the
BUFSND instruction. For details on the dedicated instructions, see
Chapter 10, "Dedicated Instructions".
3 The response end code is stored in the communication storage status
area of the buffer memory.
For details on the response end code, see Section 7.4.2, "Application
Data, (5) End codes".
POINT
The destination setting (see Section 5.5) for a connection whose parameters are
set with GX Developer becomes valid when the open completion signal (address:
5000H corresponding bit) of the Ethernet module switches from off to on.
7-4
7-4
MELSEC-Q
7.3 Receiving Control Method
This section explains the control method when the Ethernet module receives data from
an external device.
Fixed buffer communication employs the following receive processing methods:
Receive processing with the main program (dedicated instruction: BUFRCV)
: See Section 7.3.1
Receive processing with an interrupt program (dedicated instruction: BUFRCVS)
: See Section 7.3.2
7.3.1 Receive processing with the main program (dedicated instruction: BUFRCV)
This section explains about the receive processing to be performed with the main
program, using an example in which the fixed buffer No. 1 and the area corresponding
to connection No. 1.
<<Data receiving using the dedicated BUFRCD instruction (main program)>>
direction
ZP.BUFRCV "U0" K1
M100
D0
D100 M100
M101
Receive data
[D100]: Word count of receive data stored
From [D101]: Receive data
Data receiving
Response sending
1)
2)
BUFRCV instruction
4)
6)
One scan
ACK
(only TCP)
3)
7-5
Response
Data receiving
ACK
(only TCP)
5)
7-5
MELSEC-Q
1)
2)
3)
Upon receiving data from the designated external device (set in the
open processing), the Ethernet module processes the following.
Stores the receive data to the fixed buffer (No. 1) area.
Receive data length
: The head address area of the target fixed
address
Receive data
: Area beginning from the head address of
the target fixed buffer + 1
Fixed buffer receive status signal (address: 5005H b0) : ON
4)
5)
When the receive data length and reception data are read, the
following processing is performed.
At normal completion
Return "Response" to communication destination.
BUFRCV instruction complete device
: ON
BUFRCV instruction complete device + 1
: OFF
BUFRCV instruction complete status area ( 1) : 0000H
At abnormal completion
Return "Response" to communication destination.
BUFRCV instruction complete device
: ON
BUFRCV instruction complete device + 1
: ON
BUFRCV instruction complete status area ( 1) : Value other than
0000H
6)
POINT
7-6
(1)
The destination setting (see Section 5.5) for a connection whose parameters
are set with GX Developer becomes valid when the open completion signal
(address: 5000H corresponding bit) of the Ethernet module switches from
off to on.
(2)
(3)
7-6
MELSEC-Q
7.3.2 Receive processing with an interrupt program (dedicated instruction: BUFRCVS)
This section explains about the receive processing when an interrupt program is used.
When an interrupt program is set to handle the receive processing, the interrupt
program starts up when data is received from an external device and reading the
receive data destined for the PLC CPU is enabled.
In order to start up the interrupt program, set the parameters using GX Developer.
Ethernet module
<Program>
Connection No. 1
Connection No. 2
Setting
of (a)
Connection No. 16
Control
number
Interrupt
(SI) No.
0 to 15
Setting
of (b)
Interrupt
pointer
(Ixx)
Ixx
BUFRCVS
50 to 255
7-7
7-7
MELSEC-Q
Item name
Description of setting
Setting range/option
Input format
Decimal
Hexadecimal
Device code
Fixed buffer
RECV instruction
Device No.
Detection method
(Edge detection)
Interrupt condition
(Scan complete)
0 to 15
1) Input format
Select the input format (decimal/hexadecimal) of each setting item.
2) Device code
Select "Fixed buffer".
The interrupt program starts up when the receive data is stored in
the fixed buffer of the connection that opened the port set in "3)
Board No." below.
3) Board No.
Set the connection No. (1 to 16) of the fixed buffer that will initiate the
startup of the interrupt program.
4) Interrupt (SI) No.
Set the interrupt control No. (0 to 15) on the Ethernet module side
when the interrupt request is issued from the Ethernet module to the
PLC CPU.
Set a unique interrupt (SI) No. that does not overlap with the ones for
interrupts of other fixed buffer communication and the RECV
instruction.
The interrupt (SI) No. (0 to 15) can be arbitrarily assigned by the user
to receive data in communication using up to 16 fixed buffers as well
as to receive data using the RECV instruction by the interrupt program.
The user must manage the interrupt (SI) No. assigned to each data
reception method.
(Example)
For receiving by the fixed buffer communication, assign the same
interrupt (SI) No. as the target data communication connection.
For receiving using the RECV instruction, assign an interrupt
(SI) No. that is not assigned to the fixed buffer communication.
REMARK
Items other than the ones mentioned above do not need to be set by the user on the
"Ethernet interrupt settings" screen.
The setting values shown in the table above are automatically displayed for items
related to the detection method and event conditions.
POINT
In order to start up the interrupt program, the "Network parameter Ethernet interrupt
setting" and "PLC parameters" "Intelligent function module interrupt pointer
setting" are required.
7-8
7-8
MELSEC-Q
(b)
Item name
PLC side
Intelli. module side
7-9
Description of setting
Set the interrupt pointer Start No. on the PLC CPU side.
Start SI No.
Set the interrupt pointer (SI) starting No. on the PLC CPU.
Setting range/option
50 to 255
1 to 16
0000 to 0FE0H
0 to 15
1)
2)
3)
4)
7-9
MELSEC-Q
POINT
In order to start up the interrupt program, the "Network parameters Ethernet
interrupt setting" and "PLC parameters" "Intelligent function module interrupt
pointer setting" are required.
FEND
SM400
I50
Receive data
[D200]: Word count for receive data stored
From [D201]: Receive data
Data receiving
Response sending
1)
2)
4)
BUFRCVS instruction
6)
ACK
(only TCP)
Response
Data receiving
3)
Cycle
Sequence program
Interrupt program
7 - 10
Scan
ACK
(only TCP)
5)
Cycle
END
processing
Scan
Scan
END
processing
7 - 10
MELSEC-Q
1)
2)
3)
Upon receiving data from the designated external device (set in the
open processing), the Ethernet module processes the following.
Stores the receive data to the fixed buffer (No. 2) area.
Receive data length
: The head address area of the target fixed
address
Receive data
: Area beginning from the head address of
the target fixed buffer + 1
Fixed buffer receive status signal (address: 5005H b1) : ON
Request the PLC CPU to start up the interrupt program.
4)
5)
When the receive data length and reception data are read, the
following processing is performed.
6)
At normal completion
Return a "Response" to the destination.
PLC CPU error flag (SM0) ( 1)
: OFF
At abnormal completion
PLC CPU error flag (SM0) ( 1)
PLC CPU error code (SD0) ( 1)
: ON
: error code
REMARK
To start up an interrupt program, create an interrupt enable/disable program in the
main program.
The instructions to be used for this are EI and DI.
7 - 11
7 - 11
MELSEC-Q
7.4 Data Format
When communicating data between the Ethernet module and an external device, the
data format explained below is used.
The communication data consists of a "header" and "application data" as follows:
Header
Application data
Maximum of 2040 bytes
7.4.1 Header
The header for TCP/IP or UDP/IP is used. In case of the Ethernet module, the Ethernet
module adds and deletes the header. Thus, the user does not need to set it.
(Details of the size of the header section)
1)
Ethernet
14 bytes
2)
Ethernet
14 bytes
7 - 12
In case of TCP/IP
IP
20 bytes
TCP
20 bytes
In case of UDP/IP
IP
20 bytes
UDP
8 bytes
7 - 12
MELSEC-Q
7.4.2 Application data
As shown below, the data code in the application data can be expressed in either
binary or ASCII code. Switching between binary code and ASCII code is performed
with GX Developer as follows.
[GX Developer] [Network parameters] [Operational settings] [Communication
data code]
For more details, see Section 4.7, "Operational Settings".
(1) Format
(a)
2 bytes
Communication
request
source side
Data length
setting
L
H
Subheader
L
Maximum of
1017 words
2 bytes
Text
(command)
Communication request
destination side
Subheader
End code
1 byte
1 byte
(b)
Communication
request
source side
4 bytes
4 bytes
Maximum of
1016 words
Subheader
Data length
setting
Text
(command)
H
Communication request
destination side
L
Subheader
H
L
2 byte
End code
L
H
2 byte
7 - 13
7 - 13
MELSEC-Q
(2) Subheader
The format of the subheader is as shown below.
The user does not need to set the subheader when using the Ethernet module
since the Ethernet module adds and deletes it.
b7
b6
b5
b4
b3
b2
b1
b0
Command/response type
(The bit status indicated in the figure shows that communication
using fixed buffers is being performed.)
Command/response flag
At command0
At response1
Command
to
b7
0
1
"6"
1
6H
Response
to
1
b0
E0 H
Subheader
Subheader
to
b7
60 H 00 H
b7
0
0
"0"
36 H 30 H 30 H 30 H
Subheader
7 - 14
b0
0
0H
b0
b7
to
1
"E"
EH
b0
0
"0"
45 H
0H
30 H
Subheader
7 - 14
MELSEC-Q
(3) Data length setting
This value indicates the data size of the text (command) section.
POINT
The data length can be designated in the following range:
Communication using binary code: Maximum of 1017 words
Communication using ASCII code: Maximum of 508 words (*1)
1 Since data is sent/received as ASCII data, the communication data size is
approximately half of the data size when using binary code.
00H
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
Subheader
Data designation/storage device
for sending/receiving instructions
Data length
setting
Send/
receive data
n+1
(H)
(L)
n+2
(H)
(L)
n+3
(H)
(L)
to
n + setting data
Length
(H)
(L)
1 word (2 bytes)
7 - 15
7 - 15
MELSEC-Q
(H) to (L)
(H) to (L)
(H) to (L)
Subheader
Data designation/storage device
for sending/receiving instructions
ASCII-BIN conversion
Data length
setting
Send/
receive data
n+1
(H)
(L)
n+2
(H)
(L)
to
n + setting data
length
(H)
(L)
1 word (2 bytes)
(Example)
36 H
30 H
n+1
12 H
34 H
n+2
56 H
78 H
30 H
30 H
30 H
30 H
Subheader
30 H
Data length
32 H
31 H
(H)
32 H
33 H
to
34 H
35 H
(L)
(H)
36 H
37 H
to
38 H
(L)
7 - 16
7 - 16
MELSEC-Q
7.5 Programming
This section explains the programming method when the Ethernet module and an
external device communicate using the fixed buffers and the procedure exist control
method.
In order to communicate using the fixed buffer, the initial processing and the
connection open processing must be completed.
(2)
The contents of the parameter settings have been loaded into the Ethernet
module when the Ethernet module open completion signal (address: 5000H
corresponding bit) switches from off to on.
(3)
The data length in word count is designated (stored) using the dedicated
instruction for the communication with the procedure exist control method.
If the send data length exceeds this range at data sending, a communication
error occurs and the data is not sent.
(4)
Perform the fixed buffer communication using the following dedicated instructions.
Data sending
: BUFSND instruction
Data receiving
: BUFRCV instruction (for main program)
: BUFRCVS instruction (for interrupt program)
For details on the dedicated instructions, see Chapter 10, "Dedicated
Instructions".
(5)
(6)
When reading of the data received from the same connection, reading of data
received by the main program and the reading of data received by the interrupt
program cannot be done together.
Use only one of the above-mentioned programs for reading the data received.
Reading of data received by the main program cannot be performed when
setting is being performed by GX Developer for reading of received data using
the interrupt program.
(7) For data (commnd) transmission, the next data (commnd) should be after the
completion of data commnication (such as after the reception of a response) for
the transmission of the previous data (commnd).
7 - 17
7 - 17
MELSEC-Q
7.5.2 Fixed buffer communication program example (with the procedure exist control method)
This section explains the programming method in order to communicate data
(procedure exist control method) with an external device using the fixed buffers.
QCPU-1 side
QCPU-2 side
7 - 18
MELSEC-Q
6)
The "Open settings" parameters are assumed to have been set with
GX Developer as follows.
: 2000H
(for main program)
: 3000H
(for interrupt program)
7)
8)
9)
POINT
Secure sufficient device memory according to the maximum length of data sent
from the source in order to prevent device areas used for other purposes from
being overwritten by the reception data.
7 - 19
7 - 19
MELSEC-Q
(2) Outline of the program example
(a) Send program (QCPU-1st station side)
1)
2)
3)
4)
7 - 20
1)
2)
3)
7 - 20
MELSEC-Q
(Send program)
Open processing program
7 - 21
7 - 21
MELSEC-Q
(Receive program)
X19: Initial normal completion signal
M0: Connection 1 open completion signal
M40: Connection 1 data receiving signal
Read the open completion signal information
Read the open request signal information
Read the fixed buffer receiving status signal information
7 - 22
7 - 22
MELSEC-Q
8 FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE
CONTROL METHOD)
This chapter explains how the PLC CPU and external device communicate using the
fixed buffers (with the no procedure control method) of the Ethernet module.
POINT
The following points are difference overview from the "Procedure exist" when
communicating using the fixed buffers:
1)
It is possible to send and receive data which match to the message format of
the external device.
At data sending, subheader, data length, etc. are not included in the
application data field of a message; only the data in the fixed buffer is sent. At
data receiving, all the data in the message excluding the header is stored in
the fixed buffer.
2)
3)
4)
5)
Fixed buffer
No. 1
No. 2
External device
No. 3
PLC CPU
No. 4
BUFRCV
instruction
8-1
to
No. 16
8-1
MELSEC-Q
(2) Data can be communicated with the following external devices.
Device on the Ethernet to which the Ethernet module is connected.
Devices connected with the router relay function (see Section 5.3)
As shown in the diagram below, when using each fixed buffer (No. 1 to 16), the
destination devices and usage conditions (for sending/receiving, procedure
exist/no procedure, etc.) should be set when the connection via the Ethernet
module is opened to fix the external device for each buffer.
(a)
At TCP/IP communication
It is allowed to change external devices only when the open completion
signal of the applicable connection is off.
(b)
At UDP/IP communication
External devices can be changed regardless of the status of the applicable
connection.
("Destination IP address" and "Destination Port No." in the communication
address setting area can be changed. However, "Local station Port No."
cannot be changed.)
When changing external devices, do not use the "Pairing open" and
"Existence confirmation" functions.
to
External device 1
External device 8
to
External device 28
POINT
The connections for which no procedure is selected are dedicated to the fixed
buffer sending or receiving after the completion of open processing.
8-2
8-2
MELSEC-Q
(3) At data sending/receiving, the Ethernet module performs the following processing.
1)
At data sending
When the PLC CPU executes the dedicated BUFSND instruction ( 1)
in a sequence program, the Ethernet module sends data in the
applicable fixed buffer (No. n) to the external device that is specified in
the communication address setting area (addresses: 28H to 5FH and
5038H to 507FH) corresponding to fixed buffer No. n. ( 2)
2)
At data receiving
The Ethernet module processes the receive data if the data is received
from an external device set in the communication setting area that
corresponds to fixed buffer No. n. ( 2)
Also, when the Ethernet module stores the receive data in the
corresponding fixed buffer in the receive processing, it updates the
destination IP address and destination port No. in the connection
information area (addresses: 78H to C7H and 5820H to 586FH) that
corresponds to fixed buffer No. n.
If data is received from an external device not set in the connection
information area of the buffer memory, the Ethernet module ignores
the receive data to.
8-3
8-3
MELSEC-Q
8.2 Sending Control Method
This section explains the control method when data is sent from the Ethernet module
to an external device using fixed buffer No. 1 and the area corresponding to connection
No. 1 as an example.
<<Data sending using the dedicated BUFSND instruction>>
Send data
[D100]: Byte count for send data
From [D101]: Send data
direction
Set the send data in D100 and D101
ZP.BUFSND "U0" K1
M0
D0
D100
M0
M1
Processing for normal completion
M1
Processing for abnormal completion
Initial processing
Open processing
Data sending
1)
Initial normal completion signal X19
2)
Open completion signal
(Address: 5000H [b0])
3)
BUFSND instruction
5)
BUFSND instruction complete device
One scan
Data sending
ACK
(only TCP)
4)
8-4
8-4
MELSEC-Q
1)
2)
3)
4)
Only the size of the send data in the fixed buffer (No. 1) designated by
the send data length is sent to the designated external device (set in
the open processing).
5)
: ON
: ON
: Value other than
0000H
After the data transmission is abnormally completed, execute the
dedicated BUFSND instruction again to repeat the transmission
processing.
2 The status at completion is stored in the complete status area of
the dedicated instructions. For details on the dedicated instructions,
see Chapter 10, "Dedicated Instructions".
POINT
The following precaution should be observed when communicating using UDP/IP:
When the Ethernet modules internal processing is normally completed, data
send processing ends even if the communication line between the PLC CPU and
an external device is disconnected because of cable disconnection, etc. It is
recommended to send/receive data using a communication procedure defined by
the user.
8-5
8-5
MELSEC-Q
8.3 Receiving Control Method
This section explains the control method when the Ethernet module receives data from
an external device.
Fixed buffer communication employs the following receive processing methods:
Receive processing with the main program (dedicated instruction: BUFRCV)
: See Section 8.3.1
Receive processing with an interrupt program (dedicated instruction: BUFRCVS)
: See Section 8.3.2
8.3.1 Receive processing with the main program (dedicated instruction: BUFRCV)
This section explains about the receive processing to be performed with the main
program, using an example in which the fixed buffer No. 1 and the area corresponding
to connection No. 1.
<<Data receiving using the dedicated BUFRCV instruction (main program)>>
direction
ZP.BUFRCV "U0" K1
M100
D0
D100 M100
M101
Receive data
[D100]: Byte count of receive data stored
From [D101]: Receive data
Initial processing
Open processing
Data sending
1)
Initial normal completion signal X19
2)
Open completion signal
(Address: 5000H [b0])
4)
BUFRCV instruction
5)
BUFRCV instruction complete device
One scan
BUFRCV instruction complete device + 1
Data receiving
ACK
(only TCP)
3)
8-6
8-6
MELSEC-Q
1)
2)
3)
Upon receiving data from the designated external device (set in the
open processing), the Ethernet module processes the following.
Stores the receive data to the fixed buffer (No. 1) area.
(Area beginning from the head address of the target fixed buffer + 1)
Stores the data length to the head address area of the target fixed
address ( 1)
Fixed buffer receive status signal (address: 5005H b0) : ON
1 The receive data length is expressed by a byte count.
When an odd number of data bytes is received, the last received
data is stored at the lower byte of the last data storage area. (The
higher byte becomes a non-constant value.)
4)
Execute the dedicated BUFRCV instruction and read the receive data
length and receive data from the fixed buffer (No. 1).
5)
POINT
(1) The destination setting (see Section 5.5) for a connection whose parameters
are set with GX Developer becomes valid when the open completion signal
(address: 5000H corresponding bit) of the Ethernet module switches from
off to on.
(2) Execute the BUFRCV instruction when the corresponding connections bit in
the fixed buffer receive status signal storage area (address: 5005H) of the
buffer memory switches from off to on.
(3) At abnormal data receiving, the fixed buffer receive completion signal
(address: 5005H b0) does not turn on.
In addition, data is not stored in the fixed buffer (No. 1) area.
8-7
8-7
MELSEC-Q
8.3.2 Receive processing with an interrupt program (dedicated instruction: BUFRCVS)
This section explains about the receive processing when an interrupt program is used.
When an interrupt program is set up to handle the receive processing, the interrupt
program starts up when data is received from an external device and reading the
receive data destined for the PLC CPU is enabled.
In order to start up the interrupt program, set the parameters using GX Developer.
FEND
SM400
I50
Initial processing
Open processing
Receive data
[D100]: Byte count for receive data stored
From [D101]: Receive data
Data receiving
1)
Initial normal completion signal X19
2)
Open completion signal
(Address: 5000H [b1])
4)
BUFRCVS instruction
5)
Data receiving
ACK
(only TCP)
3)
Cycle
Sequence program
Interrupt program
8-8
Scan
Cycle
END
processing
Scan
Scan
END
processing
8-8
MELSEC-Q
1)
2)
3)
Upon receiving data from the designated external device (set in the
open processing), the Ethernet module processes the following.
Stores the receive data in the fixed buffer (No. 2) area.
(Area beginning from the head address of the target fixed buffer + 1)
Stores the data length in the head address area of the target fixed
address ( 1)
Request the PLC CPU to start up the interrupt program.
1 The receive data length is expressed by a byte count.
When an odd number of data bytes is received, the last received
data is stored at the lower byte of the last data storage area. (The
higher byte becomes a non-constant value.)
4)
: OFF
: ON
: error code
2 For more details on the PLC CPU error flag (SMO) and error code
(SDO), see the manual for the PLC CPU used.
5)
REMARK
(1) To start up an interrupt program, create an interrupt enable/disable program in
the main program using the EI and DI instructions.
(2) The programming for reading of receive data with an interrupt program is the
same as that for communicating (procedure exist) by fixed buffer. Refer to
program example indicated in Section 7.5.2 when programming.
8-9
8-9
MELSEC-Q
8.4 Data Format
When communicating data between the Ethernet module and an external device, the
data format explained below is used.
The communication data consists of a "header" and "application data" as shown
below.
Header
Application data
(1) Header
The header for TCP/IP or UDP/IP is used. In case of the Ethernet module, the
Ethernet module adds and deletes the header. Thus, the user does not need to
set it.
(Details of the size of the header section)
1)
In case of TCP/IP
Ethernet
14 bytes
2)
IP
20 bytes
TCP
20 bytes
In case of UDP/IP
Ethernet
14 bytes
IP
20 bytes
UDP
8 bytes
REMARK
The subheader and data length that are added for communications using the fixed
buffers in the procedure exist control method are not present for communications in
the no procedure control method. All data is treated as valid text.
8 - 10
8 - 10
MELSEC-Q
8.5 Simultaneous Broadcast Using UDP/IP
When UDP/IP is used for no procedure fixed buffer communication, data can be
broadcast simultaneously to all Ethernet module installed stations on the same
Ethernet where the Ethernet module is located. This allows writing the same data to all
stations, etc.
POINT
(1)
(2)
The user needs to determine the port numbers dedicated to the transmission
and reception by simultaneous broadcasting, after which simultaneous
broadcasting can be performed by designating these port numbers.
8 - 11
(a)
Protocol
Select "UDP/IP".
(b)
Open system
Setting is not required.
(c)
Fixed buffer
Select "Send".
8 - 11
MELSEC-Q
(d)
(e)
Pairing open
Select "No pairs".
(f)
Existence confirmation
Select "No confirm".
(g)
2)
Designate the setting value in a range from 401H to 1387H and 138BH
to FFFEH upon consulting a network administrator. Select a port No.
not used by other ports.
(h)
Destination IP address
Set "FFFFFFFFH".
(i)
2)
3)
8 - 12
8 - 12
MELSEC-Q
8.5.2 Receiving by simultaneous broadcasting
Data is received through simultaneous broadcasting, by setting FFFFFFFFH for the IP
address of an external device that is to send data to the Ethernet module, and FFFFH
for the port No., then performing the open processing.
8 - 13
(a)
Protocol
Select "UDP/IP".
(b)
Open system
Setting is not required.
(c)
Fixed buffer
Select "Receive".
(d)
(e)
Pairing open
Select "No pairs".
(f)
Existence confirmation
Select "No confirm".
8 - 13
MELSEC-Q
(g)
2)
Designate the setting value in a range from 401H to 1387H and 138BH
to FFFEH.
3)
(h)
Destination IP address
Set "FFFFFFFFH".
(i)
8 - 14
8 - 14
MELSEC-Q
REMARK
The following flowchart illustrates an outline of the Ethernet modules internal
processing when data is received by simultaneous broadcasting in the no procedure
control method.
The values designated in the buffer memory addresses 0H to 1H
and 28H to 5FH are used for the IP addresses and port numbers of
the local station's Ethernet module as well as those of external devices.
Data receiving
IP address of the
local station's Ethernet module = IP address
of receive data request source?
NO
YES
Is the network address
(sub-net address) in the IP address of the local
station's Ethernet module the same as the network
address (sub-net address) of the receive data,
and are all bits of the host address
in the receive data "1" ?
NO
YES
NO ( 1)
Destination IP address = FFFFFFFFH ?
Destination IP address =
request source IP address of the
receive data?
YES
(Simultaneous Broadcasting)
NO
YES
NO
Destination Port No. = FFFFH ?
YES
(Simultaneous Broadcasting)
NO
YES
1 If the bits in the range that indicates the host address of the receive data request destination
IP address are all "1's," the processing is performed by the YES side.
8 - 15
8 - 15
MELSEC-Q
8.5.3 Precautions when using the simultaneous broadcast function
The following precautions should be observed when broadcasting simultaneously in
the no procedure communication using the fixed buffers.
(1)
The user needs to determine the port No. dedicated to the sending and receiving
by simultaneous broadcasting, after which simultaneous broadcasting can be
performed by designating these port No..
(2)
(3)
A maximum of 2046 bytes of data in the application data field can be processed
per sending/receiving.
When it is necessary to send/receive data that exceeds 2047 bytes, divide it into
smaller portions at the send source.
(4)
REMARK
The size of the internal buffer for the operating system is approximately 40 k bytes
and any received data that exceeds this size will be discarded.
8 - 16
8 - 16
MELSEC-Q
8.6 Programming
This section explains the programming method when the Ethernet module and an
external device communicate using the fixed buffers and the no-procedure control
method.
8 - 17
(1)
In order to communicate using the fixed buffers, the initial processing and the
connection open processing must be completed.
(2)
The contents of the parameter settings have been loaded into the Ethernet
module when the Ethernet module open completion signal (address: 5000H
corresponding bit) switches from off to on.
(3)
The data length in byte count is designated (stored) using the dedicated
instruction for the no procedure communication.
If the send data length exceeds this range at data sending, a communication
error occurs and the data is not be sent.
(4)
Perform the fixed buffer communication using the following dedicated instructions.
Data sending
: BUFSND instruction
Data receiving
: BUFRCV instruction (for main program)
: BUFRCVS instruction (for interrupt program)
For details on the dedicated instructions, see Chapter 10, "Dedicated Instructions".
(5)
(6)
(7)
(8)
When reading of the data received from the same connection, reading of data
received by the main program and the reading of data received by the interrupt
program cannot be done together.
Use only one of the above-mentioned programs for reading the data received.
Reading of data received by the main program cannot be performed when
setting is being performed by GX Developer for reading of received data using
the interrupt program.
8 - 17
MELSEC-Q
8.6.2 Fixed buffer communication program example (with the no procedure control method)
This section explains the programming method in order to communication data (through
the no procedure control method) with an external device using the fixed buffers.
QCPU-1 side
QCPU-2 side
(b)
4)
Network type
: Ethernet
Head I/O No.
: 0000
Network No.
:1
Group No.
:1
Station No.
:2
The "Operational settings" parameters are assumed to have been set
with GX Developer as follows.
8 - 18
MELSEC-Q
5)
The "Open settings" parameters are assumed to have been set with
GX Developer as follows.
Connection No. 1 Local station Port No.: 2000H (for main program)
6)
7)
8)
9)
POINT
Secure sufficient device memory according to the maximum length of data sent
from the source in order to prevent device areas used for other purposes from
being overwritten by the reception data.
After setting each parameter with GX Developer and write to PLC CPU,
reset the PLC CPU and confirm that the initial processing is completed.
2)
3)
4)
8 - 19
8 - 19
MELSEC-Q
2)
3)
(Send program)
Open processing program
8 - 20
8 - 20
MELSEC-Q
(Receive program)
X19: Initial normal completion signal
M0: Connection 1 open completion signal
M40: Connection 1 data receiving signal
Read the open completion signal information
Read the open request signal information
Read the fixed buffer receiving status signal information
8 - 21
8 - 21
MELSEC-Q
POINT
The communication function using the random access buffer and the e-mail
sending/receiving function of the PLC CPU cannot be used together.
The communication function using the random access buffer and the e-mail
sending function of the PLC CPU monitoring function can, however, be used
together.
The random access buffer can be written to and read from freely by any external
device (excluding the Ethernet module) without giving access to a specific
external device.
Thus, it can be used as a common buffer area for all of the external devices
connected to the Ethernet.
Ethernet module
External
device
Read
Write
External
device
Write
Write
Random
access
buffer
Write
Read
Write
Read
Read
External
device
External
device
Read
External
device
9-1
9-1
(2)
MELSEC-Q
The following shows the data flow in the communication processing using the
random access buffer.
Ethernet module
Data written
TO instruction
PLC CPU
FROM instruction
(3)
Random
access
buffer
Read request
Data read
External
device
The random access buffer communication can be performed from all external
devices except from the Ethernet module itself (including conventional modules).
The random access buffer communication cannot be used for communication
between PLC CPUs.
(External devices that can perform communication using the random access
buffer)
External devices on the Ethernet to which the Ethernet module is connected.
External devices on the Ethernet that are connected with the router relay
function (see Section 5.3)
9-2
9-2
MELSEC-Q
ACK
(only TCP)
1)
PLC CPU
3)
Ethernet module
ACK
(only TCP)
2)
External device
1)
The PLC CPU writes data to the random access buffer of the Ethernet
module according to the TO instruction of the sequence program.
Or, the external device writes data to the random access buffer of the
Ethernet module.
2)
3) Upon receiving the read request from the external device, the Ethernet
module sends the data written in the random access buffer to the
external device which sent the read request.
(The Ethernet module side: response sending)
POINT
9-3
(1)
(2)
9-3
MELSEC-Q
2)
ACK
(only TCP)
3)
PLC CPU
Ethernet module
ACK
(only TCP)
Response
1)
External device
1)
The external device writes data to the random access buffer of the
Ethernet module.
(The Ethernet module side: command receiving)
2)
The Ethernet processes the write request from the external device and
returns the writing result to the external device that sent the write
request.
(The Ethernet module side: response sending)
3)
POINT
9-4
(1)
(2)
9-4
MELSEC-Q
Application data
9.2.1 Header
The header for TCP/IP or UDP/IP is used. In case of the Ethernet module, the Ethernet
module adds the header.
(Details of the size of the header section)
1)
Ethernet
14 bytes
2)
Ethernet
14 bytes
9-5
In case of TCP/IP
IP
20 bytes
TCP
20 bytes
In case of UDP/IP
IP
20 bytes
UDP
8 bytes
9-5
MELSEC-Q
(1) Format
(a) Communication using binary code
Application data area
(command message)
2 bytes
Communication
request source side
2 bytes
Subheader
H
00H
2 bytes
Data length
Head address
setting
L
H
L
H
Maximum of
1017 words
Text
(command)
(none at read
request)
Communication
request destination side
Subheader
End code
1 byte
1 byte
Text
(response)
(none at write
request)
Maximum of
1017 words
Communication
request source side
4 bytes
4 bytes
Subheader
Head address
H
Communication
request destination side
L 30H 30H H
4 bytes
Data length
setting
L H - - L
Maximum of
1016 words
Text
(command)
(none at read
request)
Subheader
H
2 byte
End code
H
2 byte
Text
(response)
(none at write
request)
Maximum of
1016 words
9-6
9-6
MELSEC-Q
(2) Subheader
The format of the subheader is as shown below.
The user does not need to set the subheader when using the Ethernet module
since the Ethernet module adds and deletes it automatically to the text.
b7
b6
b5
b4
b3
b2
b1
b0
00 H
Only for command (no response)
Command/response type
(When communicating using the random access buffer, use the status shown in the diagram.)
When reading: 61 H
When writing: 62 H
Command/response flag
At command: 0
At response: 1
When reading
Command (External device to Ethernet module)
to
b7
b0
0
1
"6"
1
6H
E1 H
Subheader
Subheader
to
61 H 00 H
b7
0
0
"1"
36 H 31 H 30 H 30 H
Subheader
9-7
0
1H
b0
b7
to
1
"E"
EH
b0
0
"1"
45 H
1H
31 H
Subheader
9-7
MELSEC-Q
2 bytes
4 bytes
2 bytes
4 bytes
POINT
The data length can be designated in the following range:
Communication using binary code: Maximum of 1017 words
Communication using ASCII code: Maximum of 508 words ( 1)
1 Since data is sent/received as ASCII data, the communication data size is
approximately a half of the data size when using binary code.
9-8
9-8
MELSEC-Q
(5) Text
Indicate the data written to and read from the random access buffer.
(a) Communication using binary code
Data length (maximum of 1017 words)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
Random access
buffer
Designated address
(H)
(L)
n+1
(H)
(L)
n+2
(H)
(L)
to
n+
Setting value of
word count read
(H)
(L)
1 word (2 bytes)
to (L) (H)
to (L)
(H)
to (L)
ASCII-BIN conversion
Random access
buffer
Designated address
(H)
(L)
n+
(H)
(L)
to
n+
Setting value of
word count read
(L)
(Example)
(H)
(L)
12 H
34 H
n+1
56 H
78 H
31 H
(H)
9-9
32 H
33 H
to
34 H
35 H
(L)
(H)
36 H
37 H
to
38 H
(L)
9-9
(H)
MELSEC-Q
9 - 10
9 - 10
MELSEC-Q
Subheader
62 H
00 H
Data
length
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
00 H
00 H
0A H
00 H
34 H
12 H
78 H
56 H
BC H
9A H
BC H
9A H
(H)
(L)
Logical address
2680 H ( 9856)
12 H
34 H
0 H ( 0)
2681 H ( 9857)
56 H
78 H
1 H ( 1)
2682 H ( 9858)
9A H
BC H
2 H ( 2)
to
to
2689 H ( 9865)
9A H
to
BC H
to
9 H ( 9)
(10 words)
to
to
to
17FF H (6143)
3E7F H (15999)
2)
9 - 11
End code
E2 H
00 H
9 - 11
(b)
MELSEC-Q
Subheader
Head address
Data length
(H)
(L)
(H)
(L)
00 H
00 H
00 H
41 H
36 H
32 H
30 H
30 H
00 H
00 H
00 H
00 H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
31 H
32 H
33 H
34 H
35 H
36 H
37 H
38 H
39 H
41 H
42 H
43 H
39 H
41 H
42 H
43 H
ASCII-BIN conversion
(H)
(L)
Logical address
2680 H ( 9856)
12 H
34 H
0 H ( 0)
2681 H ( 9857)
56 H
78 H
1 H ( 1)
2682 H ( 9858)
9A H
BC H
2 H ( 2)
to
2689 H ( 9865)
to
9A H
to
BC H
to
9 H ( 9)
(10 words)
to
to
to
3E7F H (15999)
17FF H (6143)
2)
9 - 12
End code
45 H
30 H
32 H
30 H
9 - 12
MELSEC-Q
(2) Reading from the random access buffer by a read request from an
external device
(a)
61 H
2)
00 H
Head
address
Data length
(L)
(H)
(L)
(H)
14 H
00 H
0A H
00 H
End code
E1H
00H
(H)
(L)
(H)
34H
12H
78H
56H
(L)
(H)
BCH 9AH
(L)
(H)
BCH 9AH
2680H ( 9856)
to
to
2694H ( 9876)
12H
34H
14H ( 20)
2695H ( 9877)
56H
78H
15H ( 21)
2696H ( 9878)
9AH BCH
16H ( 22)
to
269DH ( 9885)
to
3E7FH (15999)
9 - 13
to
to
9AH BCH
to
to
1DH ( 29)
to
(10 words)
17FFH (6143)
9 - 13
(a)
Subheader
36 H
31 H
2)
Subheader
End code
45H
30H
31H
MELSEC-Q
30 H
30 H
Data length
(H)
(L)
(H)
(L)
00 H
00 H
31 H
34 H
00 H
00 H
00 H
41 H
30H
Text (20 words)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
31H
32H
33H
34H
35H
36H
37H
38H
39H
41H
42H
43H
39H
41H
42H
43H
ASCII-BIN conversion
(H)
(L)
2680H ( 9856)
to
to
to
2694H ( 9876)
12H
34H
14H ( 20)
2695H ( 9877)
56H
78H
15H ( 21)
2696H ( 9878)
9AH BCH
16H ( 22)
to
to
269DH ( 9885)
9AH BCH
to
3E7FH (15999)
9 - 14
Logical address
0H ( 0)
to
to
1DH ( 29)
to
(10 words)
17FFH (6143)
9 - 14
MELSEC-Q
Physical address
Buffer memory
680H ( 1664)
Fixed buffer
267FH ( 9855)
Logical address
2680H ( 9856)
0H ( 0)
to
3E7FH (15999)
9 - 15
Random access
buffer
to
17FFH (6143)
9 - 15
MELSEC-Q
9 - 16
(1)
In order to communicate using the random access buffer, the initial processing
and the connection open processing must be completed.
(2)
The PLC CPU cannot issue a send request when communicating using the
random access buffer.
Also, receive completion is not confirmed to the PLC CPU.
When it is necessary to synchronize data sending/receiving between the PLC
CPU and an external device, use the fixed buffer communication function.
(3)
The address designated for the random access buffer by an external device and
the address designated with the FROM/TO instructions of the sequence program
are different.
For more detail, see Section 9.3.
9 - 16
10 DEDICATED INSTRUCTIONS
MELSEC-Q
10 DEDICATED INSTRUCTIONS
Dedicated instructions are used to simplify programming for using the functions of the
intelligent function module.
This chapter explains the dedicated instructions for the functions that are explained in
this manual, among those dedicated commands available for the Ethernet module that
can be used by the QCPU.
Dedicated instruction
Description of function
Reference section
OPEN
Establishes a connection.
Section 10.8
CLOSE
Disconnects a connection.
Section 10.5
BUFRCV
Section 10.2
BUERCVS
Section 10.3
BURSND
Sends data.
Section 10.4
ERRCLR
Section 10.6
ERRRD
Section 10.7
UINI
Section 10.9
POINT
(1) The user should not change any data (control data, request data, etc.) that is
specified with a dedicated instruction until the execution of that dedicated
instruction is completed.
(2) All dedicated instructions must be executed online.
If any of the dedicated instructions is executed offline, no error will occur, but
the execution of the dedicated instruction will not be completed.
10
10 - 1
10 - 1
10 DEDICATED INSTRUCTIONS
MELSEC-Q
Internal device
(System, user)
Bit
File
register
Word
MELSECNET/H,
MELSECNET/10
Direct J \
Bit
Special module
U \G
Word
Index
register
Zn
Constant
K, H
Others
(S1)
(S2)
(D1)
(D2)
ZP.BUFRCV
"Un"
(S1)
(S2)
(D1)
(D2)
Setting data
Setting data
"Un"
(S1)
(S2)
(D1)
(D2)
Set by (
Description
Start input/output signal of the Ethernet module
(00 to FE: The two most significant digits of the 3-digit input/output signal)
Connection number (1 to 16)
Head number of the devices that designate control data
Head number of the device that stores receive data
Head number of the local station bit device that turns on for one scan
upon completion of instruction.
(D2) + 1 also turns on if the instruction execution ends abnormally.
User
Data type
Binary 16 bits
Binary 16 bits
Binary 16 bits
Binary 16 bits
System
Bit
The file registers for each of the local device and the program cannot be used as
devices to be used in the setting data.
Control data
Device
Item
(S2) + 0
System area
(S2) + 1
Complete status
Setting data
Stores the status at completion.
0000H: Normal completion
Other than 0000H
: Abnormal completion (error code) (
Setting range
Set by (
System
2
Receive data
Device
(D1) + 0
(D1) + 1
to
(D2) + n
Item
Receive data
length
Receive data
Setting data
Setting range
Set by (
1 to 1017
System
1 to 508
10
1 to 2046
System
10 - 2
10 - 2
10 DEDICATED INSTRUCTIONS
MELSEC-Q
Functions
(1) This instruction reads receive data (for fixed buffer communication) from the
connection specified by (S1) for the module designated by Un.
PLC CPU
Ethernet module
Fixed buffer data area
No.1
Receive data
BUFRCV
No.n
Receive data
No.16
(2) Whether or not the BUFRCV instruction has been completed can be checked by
the complete bit devices (D2) + 0 and (D2) + 1.
(a)
(b)
Scan
END
processing
Scan
END
processing
Scan
END
processing
Instruction execution
BUFRCV instruction
Complete device
Abnormal completion
Complete device + 1
Receive data
10 - 3
(3)
(4)
When reading receive data from the same connection, this cannot be used
together with BUFRCVS instructions (for interrupt programs).
10 - 3
10 DEDICATED INSTRUCTIONS
MELSEC-Q
Errors
(1)
When a dedicated instruction ends with an error, the abnormal completion signal,
(D2) + 1, turns on and the error code is stored in the complete status area (S2) + 1.
Refer to the following manuals regarding the error codes, check the errors and
take corrective actions.
<Error codes>
4FFFH or less
: QCPU (Q Mode) Users Manual (Hardware Design,
Maintenance and Inspection)
C000H or higher : Section 11.3.3 of this manual
Program example
A program that reads receive data from the fixed buffer for connection number 1:
When the input/output signals of the Ethernet module are X/Y00 to X/Y1F
X19: Initial normal completion signal
M0: Connection 1 open completion signal
M40: Connection 1 data receiving signal
Read the open completion signal information
Read the open request signal information
Read the fixed buffer receiving status signal information
10 - 4
10 - 4
10 DEDICATED INSTRUCTIONS
MELSEC-Q
Internal device
(System, user)
Bit
File
register
Word
MELSECNET/H,
MELSECNET/10
Direct J \
Bit
Special module
U \G
Word
Index
register
Zn
Constant
K, H
Others
(S1)
(D1)
[Instruction code]
[Executing condition]
Command
BUFRCVS
Z.BUFRCVS
(S1)
"Un"
(D1)
Setting data
Setting data
Description
"Un"
(S1)
(D1)
Set by (
User
Data type
Binary 16 bits
Binary 16 bits
System
Binary 16 bits
The file registers of each of the local device and the program cannot be used as device
to be used in the setting data.
Receive data
Device
(D1) + 0
(D1) + 1
to
(D1) + n
Item
Receive data
length
Receive data
Setting data
Stores the data length of the data read from the
fixed buffer data area in word units.
There is a procedure (for communication
using binary code): Number of words
There is a procedure (for communication
using ASCII code): Number of words
Non procedure (for communication using
binary code): Number of bytes
Stores the data read from the fixed buffer data area
sequentially in ascending order.
Setting range
Set by (
1 to 1017
System
1 to 508
1 to 2046
System
10 - 5
10 - 5
10 DEDICATED INSTRUCTIONS
MELSEC-Q
Functions
(1)
This instruction reads receive data (for fixed buffer communication) from the
connection specified by (S1) for the module designated by Un.
PLC CPU
Ethernet module
Fixed buffer data area
No.1
Receive data
BUFRCVS
No.n
Receive data
No.16
Sequence program
Interrupt program
Instruction execution
BUFRCVS instruction
Data receiving
(2)
The Z.BUFRCVS instruction is used by the interrupt programs and its processing
completes within one scan.
(3)
(4)
When reading receive data from the same connection, this cannot be used
together with BUFRCV instructions (for main programs).
Errors
(1)
10 - 6
When the dedicated instruction is completed abnormally, the error flag (SM0)
turns on and the error code is stored in SD0.
Refer to the following manuals regarding the error code, check the errors and
take corrective actions.
<Error codes>
4FFFH or less
: QCPU (Q Mode) Users Manual (Hardware Design,
Maintenance and Inspection)
C000H or higher : Section 11.3.3 of this manual
10 - 6
10 DEDICATED INSTRUCTIONS
MELSEC-Q
Program example
A program that reads receive data from the fixed buffer for connection number 2:
When the input/output signals of the Ethernet module are X/Y00 to X/Y1F
Enable (permit) the execution of the interrupt program
10 - 7
10 - 7
10 DEDICATED INSTRUCTIONS
MELSEC-Q
Internal device
(System, user)
Bit
File
register
Word
MELSECNET/H,
MELSECNET/10
Direct J \
Bit
Special module
U \G
Word
Index
register
Zn
Constant
K, H
Others
(S1)
(S2)
(S3)
(D1)
[Instruction code]
[Executing condition]
Command
BUFSND
ZP.BUFSND
"Un"
(S1)
(S2)
(S3)
(D1)
Setting data
Set by (
Setting data
Description
"Un"
(S1)
(S2)
User
Data type
Binary 16 bits
Binary 16 bits
(S3)
(D1)
Head number of the local station bit device that turns on for one scan
upon completion of instruction.
(D1) + 1 also turns on if the instruction execution ends abnormally.
System
Binary 16 bits
User
Binary 16 bits
System
Bit
The file registers for each of the local device and the program cannot be used as
devices to be used in the setting data.
Control data
Device
(S2) + 0
(S2) + 1
Item
Setting data
Setting range
System area
Complete status
Set by (
System
2
Send data
Device
(S3) + 0
(S3) + 1
to
(S3) + n
Item
Send data
Setting data
Setting range
Set by (
1 to 1017
1 to 508
User
1 to 2046
User
10 - 8
10 - 8
10 DEDICATED INSTRUCTIONS
MELSEC-Q
Functions
(1)
This instruction sends the data designated by (S3) to the external device of the
connection specified by (S1) for the module designated by Un.
PLC CPU
Ethernet module
Fixed buffer data area
(S3)
No.1
Send data
BUFSND
(2)
No.n
Send data
No.16
External device
Whether or not the BUFSND instruction has been completed can be checked by
the complete bit devices (D1) + 0 and (D1) + 1.
(a)
(b)
Scan
END
processing
Scan
END
processing
Scan
END
processing
Instruction execution
BUFSND instruction
Complete device
Abnormal completion
Complete device + 1
Send data
(3)
10 - 9
The ZP.BUFSND instruction is executed when the send instruction switches from
off to on.
10 - 9
10 DEDICATED INSTRUCTIONS
MELSEC-Q
Errors
(1)
When a dedicated instruction ends with an error, the abnormal completion signal,
(D1) + 1, turns on and the error code is stored in the complete status area (S2) + 1.
Refer to the following manuals regarding the error code, check the errors and
take corrective actions.
<Error codes>
4FFFH or less
: QCPU (Q mode) Users Manual (Hardware Design,
Maintenance and Inspection)
C000H or higher : Section 11.3.3 of this manual
Program example
A program that sends data from the fixed buffer of connection number 1:
When the input/output signals of the Ethernet module are X/Y00 to X/Y1F
X19: Initial normal completion signal
M0: Connection 1 open completion signal
Fixed buffer No. 1 sending program
Change the send data read command to
pulse
Designate the BUFSND instruction data
Designate the send data length
Designate the send data
10 - 10
10 - 10
10 DEDICATED INSTRUCTIONS
MELSEC-Q
Internal device
(System, user)
Bit
File
register
Word
MELSECNET/H,
MELSECNET/10
Direct J \
Bit
Special module
U \G
Word
Index
register
Zn
Constant
K, H
Others
(S1)
(S2)
(D1)
ZP. CLOSE
"Un "
(S 1)
(S 2)
(D1)
Setting data
Set by (
Setting data
Description
"Un"
(S1)
Binary 16 bits
(S2)
Binary 16 bits
(D1)
Head number of the local station bit device that turns on for one scan
upon completion of instruction.
(D1) + 1 also turns on if the instruction execution ends abnormally.
User
System
Data type
Binary 16 bits
Bit
The file registers for each of the local device and the program cannot be used as
devices to be used in the setting data.
Control data
Device
(S2) + 0
(S2) + 1
Item
Setting data
Setting range
Set by (
System area
Complete status
System
2
10 - 11
10 - 11
10 DEDICATED INSTRUCTIONS
MELSEC-Q
Functions
(1)
This instruction closes the connection specified by (S1) for the module designated
by Un (disconnecting connections).
(2)
Whether or not the CLOSE instruction has been completed can be checked by
the complete bit devices (D1) + 0 and (D1) + 1.
(a)
(b)
Scan
END
processing
Scan
END
processing
Scan
END
processing
Instruction execution
CLOSE instruction
Complete device
Abnormal completion
Complete device + 1
Connection
closed
(3)
The ZP.CLOSE is executed when the close instruction switches from off to on.
Important
Never execute the open/close processing using input/output signals and the
open/close processing using the OPEN or CLOSE dedicated instructions
simultaneously for the same connection. It will result in malfunctions.
Errors
(1)
10 - 12
When a dedicated instruction ends with an error, the abnormal completion signal,
(D1) + 1, turns on and the error code is stored in the complete status area (S2) + 1.
Refer to the following manuals regarding the error codes, check the errors and
take corrective actions.
<Error codes>
4FFFH or less
: QCPU (Q Mode) Users Manual (Hardware Design,
Maintenance and Inspection)
C000H or higher : Section 11.3.3 of this manual
10 - 12
10 DEDICATED INSTRUCTIONS
MELSEC-Q
Program example
A program that closes the connection number 1:
When the input/output signals of the Ethernet module are X/Y00 to X/Y1F
M0: Connection 1 open completion signal
M150: OPEN instruction execution normal completion
flag
Set the flag by the close processing from the external
device
Change the close processing from the external
device to pulse
Change the close request from the Local station side to
pulse
Perform close processing
Set the close processing executing flag
Set the normal completion flag
Set the abnormal completion flag
Reset the close processing execution flag
10 - 13
10 - 13
10 DEDICATED INSTRUCTIONS
MELSEC-Q
Internal device
(System, user)
Bit
(S1)
File
register
Word
MELSECNET/H,
MELSECNET/10
Direct J \
Bit
Special module
U \G
Word
(D1)
Index
register
Zn
Constant
Others
K, H
ZP. ERRCLR
"Un "
(S1)
(D1)
Setting data
Setting data
"Un"
Set by (
Description
Start input/output signal of the Ethernet module
(00 to FE: The two most significant digits of the 3-digit input/output signal)
(S1)
(D1)
Head number of the local station bit device that turns on for one scan
upon completion of instruction.
(D1) + 1 also turns on if the instruction execution ends abnormally.
Data type
User
Binary 16 bits
User, system
Binary 16 bits
System
Bit
The file registers for each of the local device and the program cannot be used as
devices to be used in the setting data.
Control data
Device
(S1) + 0
(S1) + 1
Item
System area
Complete status
Set by (
Setting data
Setting range
System
(as described
in the left)
User
0000H
FFFFH
User
(S1) + 2
Clearing target
designation
(S1) + 3
Clearing function
designation
(S1) + 4
to
(S1) + 7
System area
10 - 14
10 - 14
10 DEDICATED INSTRUCTIONS
MELSEC-Q
Functions
(1)
This instruction turns [COM.ERR] LEDs off and clears error information listed
below for the module designated by Un.
Target
designation
(S1) + 2
Function
designation
(S1) + 3
Initial error
0000H
0000H
Open error
0001H to 0016H
0000H
Target item
Error log
0100H
FFFFH
Status by each
protocol
0101H
FFFFH
0102H
FFFFH
0103H
FFFFH
E-mail sending
(address: 5B39H to 5CA0H)
FFFFH
FFFFH
(2)
Whether or not the ERRCLR instruction has been completed can be checked by
the complete bit devices (D1) + 0 and (D1) + 1.
(a)
(b)
Scan
END
processing
Scan
END
processing
Scan
END
processing
Instruction execution
ERRCLR instruction
Complete device
Abnormal completion
Complete device + 1
Error cleared
(3)
10 - 15
The ZP.ERRCLR function is executed when the clear instruction switches from off
to on.
10 - 15
10 DEDICATED INSTRUCTIONS
MELSEC-Q
Errors
(1)
When a dedicated instruction ends with an error, the abnormal completion signal,
(D1) + 1, turns on and the error code is stored in the complete status area (S1) + 1.
Refer to the following manuals regarding the error code, check the errors and
take corrective actions.
<Error codes>
4FFFH or less
: QCPU (Q Mode) Users Manual (Hardware Design,
Maintenance and Inspection)
C000H or higher : Section 11.3.3 of this manual
Program example
A program that clears the open abnormal code for connection 1:
When the input/output signals of the Ethernet module are X/Y00 to X/Y1F
M0: Connection 1 open completion signal
Designate the ERRCLR instruction data
Designate to clear the connection 1 open abnormal
code
Designate to turn off ERR LED and clear the error
code
Set the ERRCLR instruction execution flag
Execute error information clearing
Clear the retained error code at normal completion of
the error information clear processing
Retain the error code at abnormal completion of the
error information clear processing
Reset the ERRCLR instruction execution flag
10 - 16
10 - 16
10 DEDICATED INSTRUCTIONS
MELSEC-Q
Internal device
(System, user)
Bit
File
register
Word
Applicable device
MELSECNET/H,
MELSECNET/10
Special module
Direct J \
U \G
Bit
Word
Index
register
Zn
Constant
K, H
Others
(S1)
(D1)
ZP.ERRRD
"Un "
(S 1)
(D1)
Setting data
Setting data
"Un"
(S1)
(D1)
Set by (
Description
Start input/output signal of the Ethernet module
(00 to FE: The two most significant digits of the 3-digit input/output signal)
Head number of the device that stores control data
Head number of the local station bit device that turns on for one scan
upon completion of instruction.
(D1) + 1 also turns on if the instruction execution ends abnormally.
Data type
User
Binary 16 bits
User, system
Binary 16 bits
System
Bit
The file registers for each of the local device and the program cannot be used as
devices to be used in the setting data.
Control data
Device
(S1) + 0
(S1) + 1
Item
Setting data
Setting range
System area
Complete status
(S1) + 2
Read information
designation
(S1) + 3
Read target
information
designation
(S1) + 4
Error information
(S1) + 5
to
(S1) + 7
System area
Set by (
System
0
1 to 16
User
0000H
User
0000H
System
Functions
(1)
This instruction reads the error code and information in the error log of the module
designated by Un.
Target item
10 - 17
Initial error
0000H
0H
Open error
0001H to 0016H
0H
10 - 17
10 DEDICATED INSTRUCTIONS
(2)
MELSEC-Q
Whether or not the ERRRD instruction has been completed can be checked by
the complete bit devices (D1) + 0 and (D1) + 1.
(a)
(b)
Scan
END
processing
Scan
END
processing
Scan
END
processing
Instruction execution
ERRRD instruction
Complete device
Abnormal completion
Complete device + 1
Error
information
read
(3)
The ZP.ERRRD is executed when the read instruction switches from off to on.
Errors
(1)
When a dedicated instruction ends with an error, the abnormal completion signal,
(D1) + 1, turns on and the error code is stored in the complete status area (S1) + 1.
Refer to the following manuals regarding the error code, check the errors and
take corrective actions.
<Error codes>
: QCPU (Q Mode) Users Manual (Hardware Design,
4FFFH or less
Maintenance and Inspection)
C000H or higher : Section 11.3.3 of this manual
Program example
A program to read the open abnormal code for connection 1:
When the input/output signals of the Ethernet module are X/Y00 to X/Y1F
Designate the open abnormal code of Connection No. 1
Designate the latest error information
10 - 18
10 - 18
10 DEDICATED INSTRUCTIONS
MELSEC-Q
Internal device
(System, user)
Bit
File
register
Word
Applicable device
MELSECNET/H,
MELSECNET/10
Special module
Direct J \
U \G
Bit
Word
Index
register
Zn
Constant
K, H
Others
(S1)
(S2)
(D1)
[Instruction code]
[Executing condition]
Command
ZP.OPEN
ZP.OPEN
"Un"
(S1)
(S2)
(D1)
Setting data
Setting data
Description
"Un"
(S1)
(S2)
(D1)
Head number of the local station bit device that turns on for one scan
upon completion of instruction.
(D1) + 1 also turns on if the instruction execution ends abnormally.
Set by (
User
Data type
Binary 16 bits
Binary 16 bits
User, system
Binary 16 bits
System
Bit
The file registers for each of the local device and the program cannot be used as
devices to be used in the setting data.
10 - 19
10 - 19
10 DEDICATED INSTRUCTIONS
MELSEC-Q
Control data
Device
(S2) + 0
(S2) + 1
Item
Setting data
Setting range
Complete status
Set by (
0000H
8000H
User
System
(as described in
the left)
User
407H to 1387H
138BH to FFFEH
User
1H to FFFFFFFFH
(FFFFFFFFH:
simultaneous
broadcast)
User
6)
(S2) + 2
(S2) + 3
to
b10 b9
b8
b7
5) 4) 3)
b6
to
b2
b1
b0
2) 1)
(S2) + 4
(S2) + 5
Destination IP
address
(S2) + 6
Destination
Port No.
401H to FFFFH
(FFFFH:
simultaneous
broadcast)
User
(S2) + 7
to
(S2) + 9
Destination
Ethernet address
n
000000000000H
FFFFFFFFFFFFH
User
10 - 20
10 - 20
10 DEDICATED INSTRUCTIONS
MELSEC-Q
Functions
(1)
This instruction performs the open processing for a connection specified by (S1)
for the module designated by Un.
The selection of the setting values to be used for the open processing is
designated by (S2) + 0.
(2)
Whether or not the OPEN instruction has been completed can be checked by the
complete bit devices (D1) + 0 and (D1) + 1.
(a)
(b)
Scan
END
processing
Scan
END
processing
Scan
END
processing
Instruction execution
OPEN instruction
Complete device
Abnormal completion
Complete device + 1
Connection
open
(3)
The ZP.OPEN is executed when the open instruction switches from off to on.
POINT
Never execute the open/close processing using input/output signals and the
open/close processing using the OPEN or CLOSE dedicated instruction
simultaneously for the same connection. It will result in malfunctions.
10 - 21
10 - 21
10 DEDICATED INSTRUCTIONS
MELSEC-Q
Errors
(1)
When a dedicated instruction ends with an error, the abnormal completion signal,
(D1) + 1, turns on and the error code is stored in the complete status area (S2) + 1.
Refer to the following manuals regarding the error code, check the errors and
take corrective actions.
<Error codes>
4FFFH or less
: QCPU (Q Mode) Users Manual (Hardware Design,
Maintenance and Inspection)
C000H or higher : Section 11.3.3 of this manual
Program example
A program that Active open the connection 1 for TCP/IP communication:
When the input/output signals of the Ethernet module are X/Y00 to X/Y1F
X19: Initial normal completion signal
M0: Connection 1 open completion signal
M20: Connection 1 open request signal
Open processing of connection No. 1
(TCP/IP Active open)
Read the open completion signal information
Read the open request signal information
Change the open command to pulse
Designate the control data for the OPEN instruction
1)
2)
10 - 22
10 - 22
10 DEDICATED INSTRUCTIONS
MELSEC-Q
Internal device
(System, user)
Bit
File
register
Word
Applicable device
MELSECNET/H,
MELSECNET/10
Special module
Direct J \
U \G
Bit
Word
Index
register
Zn
Constant
K, H
Others
(S1)
(D1)
[Instruction code]
[Executing condition]
Command
UINI
ZP.UINI
(S1)
"Un"
(D1)
Setting data
Setting data
Description
"Un"
(S1)
(D1)
Head number of the local station bit device that turns on for one scan
upon completion of instruction.
(D1) + 1 also turns on if the instruction execution ends abnormally.
Set by (
Data type
User
Binary 16 bits
User, system
Binary 16 bits
System
Bit
The file registers for each of the local device and the program cannot be used as
devices to be used in the setting data.
10 - 23
10 - 23
10 DEDICATED INSTRUCTIONS
MELSEC-Q
Control data
Device
(S1) + 0
(S1) + 1
Item
Setting range
System
0H to 3H
User
00000001H to
FFFFFFFEH
User
(See the
description to
the left.)
User
System area
Completion status
Set by (
Setting data
Stores the status at completion.
0000H: Normal completion
Other than 0000H
: Abnormal completion (error code) (
b15
(S1) + 2
Specification of
target of change
(S1) + 3
(S1) + 4
Local station
IP address
b2 b1 b0
2) 1)
(S1) + 5
to
0
b9 b8 b7 b6 b5 b4 b3 b2 b1 b0
5) 0 4) 3) 2)
0
1) 0
POINT
When performing re-initial processing of the Ethernet module only, i.e., without
changing the local station IP address and operation settings, the control data
should be specified so that the value (0H) is stored in ((S1) + 2)), the specification of
target of change, before executing the UINI instruction.
The Ethernet module clears external device address information that it has been
maintaining and performs re-initial processing in order to allow data communication
to restart. (The initial normal completion signal (X19) is on.)
10 - 24
10 - 24
10 DEDICATED INSTRUCTIONS
MELSEC-Q
Functions
(1)
(2)
Whether or not the UINI instruction has been completed can be checked by the
complete bit devices (D1) + 0 and (D1) + 1.
(a)
(b)
Scan
END
processing
Scan
END
processing
Scan
END
processing
instruction execution
Complete device
Complete device + 1
Abnormal completion
Reinitialization
request
(3)
Initialization
of module
The ZP.UINI is executed when the open instruction switches from off to on.
POINT
Please keep the following points in mind when reinitializing Ethernet module. (Failure
to do so may cause errors in the data communication with the external devices.)
(1) Be sure to end all current data communication with external devices and close
all connections before performing a re-initial processing.
(2)
Do not mix a re-initial processing done by writing directly into buffer memory, for
instance by using a TO instruction, with a re-initial processing via UINI instruction.
Also, do not request another re-initial processing while a re-initial processing
is already being performed.
(3)
Be sure to reset external devices if the IP address of the Ethernet module has
been changed. (If an external device maintains the Ethernet address of a
device with which it communicates, the communication may not be continued
after the IP address of the Ethernet module has been changed.)
(4)
Errors
(1)
10 - 25
When a dedicated instruction ends with an error, the abnormal completion signal,
(D1) + 1, turns on and the error code is stored in the complete status area (S1) + 1.
Refer to the following manuals regarding the error code, check the errors and
take corrective actions.
<Error codes>
4FFFH or less
: QCPU (Q Mode) Users Manual (Hardware Design,
Maintenance and Inspection)
C000H or higher : Section 11.3.3 of this manual
10 - 25
10 DEDICATED INSTRUCTIONS
MELSEC-Q
Program example
The following figure shows a sample program that performs a re-initial processing.
When I/O signals of the Ethernet module are X/Y00 to X/Y1F
Re-initial
instruction
Re-initial
instruction
INCP
D260
INCP
D261
Re-initial
instruction
POINT
This is an example program that can be used to perform re-initial processing when
communicating with connections 1 and 2. The corresponding numbers and bits for
each connection should be specified if other connections are used.
10 - 26
10 - 26
11 TROUBLESHOOTING
MELSEC-Q
11 TROUBLESHOOTING
11
This section explains the contents of the errors that may occur during communications
between the Ethernet module and an external device as well as the troubleshooting
procedures.
The following are methods for checking whether there is an error on the Ethernet
module side and the contents of the error.
Use one of the following methods to check whether there is an error and its content,
then take corrective actions.
(1) Check using the display LED on the front of the Ethernet module
(See Section 11.1.)
The display LED on/off status can be used to check whether an error is occurring
in the Ethernet module.
(b)
(c)
2)
3)
4)
2)
(3) Check the contents of the error using the error code (See Section
11.3.)
The contents of the error can be checked using the error code confirmed on the
above dedicated screen or by monitoring the buffer memory by referring to
Section 11.3.
REMARK
If line errors and other errors occur when connecting devices of multiple
manufacturers, the users needs to isolate the malfunctioning parts using line
analyzers, etc.
11 - 1
11 - 1
11 TROUBLESHOOTING
MELSEC-Q
LED name
[RUN]
[ERR.]
[COM.ERR]
Status to check
QJ71E71-B5
ERR.
COM.ERR.
100M
RD
RUN
INIT.
OPEN
SD
QJ71E71-B2
ERR.
COM.ERR.
RD
RUN
INIT.
OPEN
SD
ERR.
COM.ERR.
RD
Cause/corrective action
1) Check the contents of the error using the error codes stored by the error detection of the following
processing and remove the causes.
Initial processing
Fixed buffer send processing
E-mail send/receive processing
Open processing
Data communication processing
Other processing (processing for which error codes are stored in the error log area)
2) For a list of error codes, see Section 11.3.
(Continues on the following page)
11 - 2
11 - 2
11
11 TROUBLESHOOTING
MELSEC-Q
[SD]
Status to check
Cause/corrective action
[RD]
1 Conduct a hardware test (H/W test) and check whether or not the Ethernet module operates normally.
For details on the hardware test, see Section 4.8.2, "Hardware test".
2 Conduct a confirmation of the completion for the initial processing and check whether or not there is any problem
in the cable connection and the Ethernet lines.
See Section 5.4, "Confirming the completion of the Initial Processing" for details on confirming the completion for
the initial processing. (Perform either one of the "Confirming the completion of the initial processing completion"
actions described in Section 5.4.)
POINT
The on/off status of the [INIT], [OPEN], [ERR.] and [COM.ERR] LEDs is stored in
the module status area (address: C8H) of the buffer memory.
For more details, see Section 3.8, "List of Applications and Assignments of the
Buffer Memory".
11 - 3
11 - 3
11 TROUBLESHOOTING
MELSEC-Q
11.1.2 How to turn off COM.ERR LED and to read/clear error information
This section explains how to turn off [COM.ERR] LED and to read/clear error
information using the sequence program.
The [COM.ERR] LED is turned off by turning on the off request signal (Y17).
(LED off)
(LED on)
Error occurrence
Error
occurrence
Error
occurrence
Error
occurrence
(b)
The off request is processed continuously while the off request signal (Y17)
is on.
(c)
The error information in the error log area of the buffer memory is not
cleared (deleted) by turning the off request signal (Y17) is on.
Clicking on the COM.ERR off button turns the [COM.ERR] LED off.
(b)
The error information in the error log area of the buffer memory is not
cleared (deleted).
(b)
For the details of the dedicated instruction, see Chapter 10, "Dedicated
Instructions".
11 - 4
11 - 4
11 TROUBLESHOOTING
MELSEC-Q
Parameter status
Checks the stored parameters after the
initial processing for the Ethernet module.
(See Section 5.2.)
Error log
Checks the error stored in the error log area.
(See Section 11.3.)
Status of each connection
Checks the status of each connection after the
connection to the external device is established
with the open processing. (See Section 5.6.)
Status of each protocol
Checks the communication status of each
protocol supported by the Ethernet module.
LED status
Checks the on/off status of the LED on the
front of the Ethernet module. (See Section 11.1.)
(b)
H/W information
LED on/off status, connection status and parameter status of an Ethernet
module can be checked.
POINT
See Section 11.2.3 for the buffer memory that can be checked on the "Ethernet
diagnostics" screen and "System monitor" screen.
11 - 5
11 - 5
11 TROUBLESHOOTING
MELSEC-Q
[Diagnostics]
Ethernet diagnostics
2)
3)
10)
9)
4)
5)
8)
6)
7)
[Explanation of items]
No.
Item
Description
PING test
Performs the PING test on the external device. (See Section 5.4.1, Section 5.4.2.)
Loop test
Performs the loop back test for the network. (See Section 5.4.3.)
Clicking this button turns the [COM.ERR] LED off. (See Section 11.1.2.)
Start monitor
Stop monitor
Clear history
10
Clear information
11 - 6
Setting range
Card 1 to Card 4
Decimal/hexadecimal
11 - 6
11 TROUBLESHOOTING
MELSEC-Q
POINT
When accessing a PLC on other station with a data link instruction during Ethernet
diagnostics, it may take some time to execute the data instruction.
Take the following actions and then execute the Ethernet diagnostics when
executing data link instructions.
Execute the COM instruction.
Using the special register SD315, ensure the time for communication processing
of 2 to 3 ms.
11 - 7
11 - 7
11 TROUBLESHOOTING
MELSEC-Q
(1) Checking the module status and error codes on the detailed
module information screen for the diagnostic functions.
[Startup procedure]
GX Developer [Diagnostics]
[System monitor]
[Displays]
Module
The following information is displayed:
Model name
: the model name of the module installed
Starting I/O No.
: the starting input/output signal number of the target
module
Mounting position : the slot position where the module is mounted
Product information : Product information
The function version of the module is shown at the end of the product
information.
(Example) A "B" at the end of the product information indicates this is a
module of function version B.
Unit access (Module access)
Displays access permissions when the WDT error signal (X1F) is turned off.
Status of I/O Address Verify
Displays whether or not the module for which the user has set the parameters
matches the module installed.
Remote password setting status
Displays the remote password setting status.
Present Error
Displays the error code of the latest error occurred.
11 - 8
11 - 8
11 TROUBLESHOOTING
MELSEC-Q
Error Display
Displays the error codes stored in the error log area (address: E5H, EEH ,
16CH) of the buffer memory.
Error details, corrective action
Displays the error details and corrective action for the error code selected in
Error Display.
(2) Checking the LED on/off status and operation mode number on the
H/W information screen of the diagnostic functions
[Startup procedure]
GX Developer [Diagnostics]
[System monitor]
H/W Information
[Displays]
This screen displays the Ethernet module information stored in the following
areas of the buffer memory.
No.
Display content
Address
C8H (200)
5000H (20480)
Network No.
76H (118)
Group No.
77H (119)
Station No.
76H (118)
Mode No.
Communication status (
CAH (202)
CBH (203)
3
4
H/W switch
information
1 b15 to b5 b4
1/0
b3
b2
b1
b0
1/0
1/0
1/0
ERR.LED
COM.ERR LED
1: On
0: Off
11 - 9
INIT.LED
OPEN LED
2 b15 to b9 b8
1/0
6)
b7
b6
b5
b4
b3
b2
b1
b0
1/0
1/0
1/0
1/0
1/0
5)
4)
3)
2)
1)
4) Send frame
0: Ethernet
1: IEEE802.3
5) Write enable/disable at
RUN time
0: Disable
1: Enable
6) Initial timing
0: Do not wait for OPEN
1: Always wait for OPEN
11 - 9
11 TROUBLESHOOTING
MELSEC-Q
11.2.3 Buffer memory that can be monitored with the GX Developer diagnostic function
The following is a list of the buffer memory addresses that can be displayed on the
"Ethernet diagnostics" screen and "System monitor" screen of GX Developer.
The display screen and display contents are mentioned for the Ethernet diagnostics
screen. See Section 11.2.2 for how to display the System monitor screen.
Address
Dec (Hex)
32 (20H)
33 to 39
(21 H to 27H)
105 (69H)
106 to 107
(6A H to 6B H)
108 to 110
(6C H to 6E H)
116 (74 H)
119 (77 H)
Connection No. 1
Open system
Connection No. 2 to 8
Initial error code
IP address
Parameter status
Module information
202 (CA H)
203 (CB H)
Group No.
Local station Port No.
Destination IP address
Status of each
connection
Connection No. 1
LED status
INIT.
OPEN
ERR.
COM.ERR
Drive mode
Latest
Error log
Destination IP address
Destination IP address
IP packet
Connection No. 2 to 8
IP
Ethernet address
Automatic open UDP port number
Network No.
Station No.
Destination IP address
Connection No. 1
Pairing open
Protocol
200 (C8 H)
11 - 10
Existence confirmation
118 (76 H)
227 (E3 H)
229 (E5 H)
230 (E6 H)
231 (E7 H)
232 (E8 H)
233 (E9 H)
234 to 235
(EA H to EB H)
236 (EC H)
238 to 372
(EE H to 174 H)
376 to 377
(178 H to 179 H)
378 to 379
(17A H to 17B H)
380 to 381
(17C H to 17D H)
408 to 409
(198 H to 199 H)
410 to 411
(19A H to 19B H)
412 to 413
(19C H to 19D H)
414 to 415
(19E H to 19F H)
416 to 417
(1A0 H to 1A1 H)
418 to 419
(1A2 H to 1A3 H)
Display contents
120 (78 H)
121 to 122
(79 H to 7A H)
123 (7B H)
124 (7C H)
125 (7D H)
126 (7E H)
130 to 199
(82 H to C7 H)
Ethernet diagnostics
display screen
11 - 10
11 TROUBLESHOOTING
Address Decimal
(hexadecimal)
420 to 421
(1A4 H to 1A5 H)
440 to 441
(1B8 H to 1B9 H)
442 to 443
(1BA H to 1BB H)
444 to 445
(1BC H to 1BD H)
472 to 473
(1D8 H to 1D9 H)
474 to 475
(1DA H to 1DB H)
476 to 477
(1DC H to 1DD H)
20480 (5000 H)
1
22560 to 22639
(5820 H to 586F H)
22640 (5870 H)
22641 (5871 H)
22642 (5872 H)
22643 (5873 H)
22644 (5874 H)
22645 (5875 H)
22646 (5876 H)
22647 (5877 H)
22649 (5879 H)
22650 (587A H)
22651 to 22658
(587B H to 5882 H)
22659 to 22662
(5883 H to 5886 H)
22663 to 22692
(5887 H to 58A4 H)
22693 to 23352
(58A5 H to 5B38 H)
MELSEC-Q
TCP
Ethernet diagnostics
display screen
Display contents
ICMP packet
UDP packet
23353 (5B39 H)
23354 (5B3A H)
23355 (5B3B H)
23356 (5B3C H)
23357 (5B3D H)
23358 (5B3E H)
23359 (5B3F H)
Send
23361 (5B41 H)
23362 (5B42 H)
23363 to 23370
(5B43 H to 5B4A H)
23371 to 23374
(5B4B H to 5B4E H)
23375 to 23404
(5B4F H to 5B6C H)
23405 to 23712
(5B6D H to 5CA0 H)
status of each
connection
Received e-mail
information
From
Error log block 1
From
Latest error log
Date
Receive date
Subject
Subject
Error log 2 to 16
Number of normal end dedicated instructions
Number of error end of dedicated instructions
Number of normal end mails
Number of attached file sends
Number of server sends
Number of error end mails
Number of Error log writes
Error code
Command code
To
Error log block 1
Send To
Latest error log
Date
Send date
Subject
Subject
Error log 2 to 16
1 Can be monitored on the System monitor screen of GX Developer. See Section 11.2.2.
11 - 11
11 - 11
11 TROUBLESHOOTING
MELSEC-Q
11.2.4 Checking the error information by the buffer memory batch monitoring function
It is explained here how the Ethernet module errors can be checked from GX
Developer.
Error codes stored in the buffer memory of the Ethernet module can be monitored
using the "Buffer memory batch monitoring" function of GX Developer.
[Operating procedure]
(Step 1) Select [Online] [Monitor] [Buffer memory batch] from the GX Developer
menu bar, and start the "Buffer memory batch monitoring" screen.
(Step 2) Enter [Module start address:].
For the module start address, enter the start I/O signal of the Ethernet module
to be monitored using four digits.
(Example)
Start I/O signal: Enter "0020" when monitoring modules of X/Y0020 to
003F
(Step 3) Enter [Buffer memory start address:].
Enter the buffer memory address to be monitored, using the selected input
format (decimal/hexadecimal).
For a list of the buffer memory addresses where error codes are stored, see
Section 11.3, "Error Code List".
(Example)
When monitoring the initial abnormal code (buffer memory storage
address: 69H):
Enter "69" + "hexadecimal"
(Step 4) Click the Start Monitor button.
The contents of the buffer memory after the specified address are displayed.
(In case of the above example, the contents of 69H and succeeding
addresses are displayed.)
REMARK
The display format can by modified as follows:
Monitor format
: Bits & words/ Multiple bit points/ Multiple word points
Display
: 16-bit integer/32-bit integer/real number/ASCII character
Numerical value : Decimal/hexadecimal
For details, refer to the "Operating Manual" for GX Developer.
11 - 12
11 - 12
11 TROUBLESHOOTING
MELSEC-Q
Description
Communication error
5101H
(HTTP status stroage area)
5870H: Receive
(E-mail status storage area)
5B39H: Send
(E-mail status storage area)
Not stored
(Stored in the complete status area of the instruction)
Explanation
Section 11.3.3
Section 11.3.1
Section 11.3.3
Section 11.3.1
Section 11.3.2
Section 11.3.3
CPU module
manual
Section 11.3.3
Not stored
(Stored in the complete status area of the instruction)
For details on the error codes returned by MX Component when communicating data using MX Component, refer to
the MX Component Programming Manual.
11 - 13
11 - 13
11 TROUBLESHOOTING
MELSEC-Q
This address stores the error codes generated when the initial processing is
executed.
(b)
Error codes are stored as binary values when the initial abnormal
completion signal (X1A) is on.
(c)
An error code is cleared when the initial normal completion signal (X19) is
turns on, but can also be cleared by the following operations.
1)
2)
Writing "0" to the initial error code storage area with a sequence
program
These addresses store the result of the open processing for the applicable
connections.
(b)
(c)
(b)
A sending error code is cleared when the next data sending is normally
completed.
11 - 14
(a)
(b)
Determine how to handle the end codes in the responses by arranging with
the particular external device.
11 - 14
11 TROUBLESHOOTING
MELSEC-Q
(b)
POINT
(1) An error log block area consists of sixteen error log blocks that have the same
data order.
(2) The error information is continued to be stored into the following areas even if the
count of the error occurrences is stopped and no longer stored:
Error log write pointer storage area
Error log block
b15
(c)
Error log block Error code/end code (address: Starting from E5H)
1) In the error code/end code area, the error codes that indicate error
content are stored. (See Section 11.3.)
(d)
(e)
b0
or
b15
to
Sub-request type
b8
b7
b0
to
Request type
11 - 15
11 - 15
11 TROUBLESHOOTING
(f)
(g)
(h)
(i)
(j)
MELSEC-Q
2)
For errors below the TCP and UDP levels, "0" is stored.
Error log block Local station Port No. (address: starting from E9H)
1)
This block stores the local stations port No. when an error occurred.
2)
"0" is stored for errors below the TCP and UDP levels.
Error log block Destination IP address (address: EAH and starting from
EBH)
1)
2)
Error log block Destination Port No. (address: starting from ECH)
1)
This block stores the external devices port No. when an error
occurred.
2)
"0" is stored for errors below the TCP and UDP levels.
This address stores the count of the occurrence for the applicable
contents of each protocols condition.
(The value counted by the Ethernet module.)
2)
When the count value exceeds two words, the count stops at
FFFFFFFFH (4294967295).
POINT
Values stored in the buffer memory are cleared when the station in which the
Ethernet module is installed is powered on or reset. (They are not cleared during
the initial processing.)
Normally, it is not necessary to read this area; so, read it as needed during
maintenance.
11 - 16
11 - 16
11 TROUBLESHOOTING
MELSEC-Q
POINT
The error log block area consists of 16 error log blocks that have the same data
order.
(b)
(c)
Error log block : HTTP response code (address: starting from 5108H)
This error log block stores the HTTP response code when an error occurs.
(See Section 11.3.)
(d)
(e)
Error log block : Error occurrence time (address: starting from 510BH)
This block stores the time when the error occurs in BCD code.
b15
to
b8
b15
to
b7
b8
b7
to
to
b8
b7
b8
b7
to
b0
to
b0
11 - 17
b0
to
to
b0
11 - 17
11 TROUBLESHOOTING
MELSEC-Q
11 - 18
2)
3)
4)
5)
6)
7)
11 TROUBLESHOOTING
MELSEC-Q
8)
9)
POINT
The error log block area consists of 16 error log blocks that have the same data
order.
10) Error log block Error code (address: starting from 5879H)
This block stores the error codes that indicate the contents of errors.
(See Section 11.3.)
11) Error log block Command code (address: starting from 587AH)
This block stores the system command codes for the error causing
messages.
12) Error log block From (address: starting from 587BH)
This block stores eight words from the beginning of the sending
source mail address of an error causing e-mail during
communication with the mail server, in ASCII code characters.
(Example)
If the sending source mail address was
"use@from.add.sample.co.jp",
"use@from.add.sam" is stored as ASCII code characters.
13) Error log block Date (address: starting from 5883H)
This block stores the time and date on which the e-mail is received in
BCD code.
b15
to
b8
b15
to
b7
b8
b7
b15
to
to
b0
to
b0
b8
b7
b15
to
to
b0
Minute (00H to 59 H)
b8
b7
to
b0
11 - 19
11 TROUBLESHOOTING
(b)
11 - 20
MELSEC-Q
E-mail status storage area for sending (addresses: 5B39H to 5CA0H)
1)
2)
3)
4)
5)
6)
7)
11 - 20
11 TROUBLESHOOTING
MELSEC-Q
8)
POINT
The sending error log block area consists of eight error log blocks that have the
same order of data items.
9)
10) Error log block Command code (address: starting from 5B42H)
This block stores the system command codes for the error causing
messages.
11) Error log block To (address: starting from 5B43H)
This block stores eight words from the beginning of the sending
source mail address of an error causing e-mail during
communication with the mail server, in ASCII code characters.
(Example)
If the sending source mail address was
"use@from.add.sample.co.jp",
"use@from.add.sam" is stored as ASCII code characters.
12) Error log block Date (address: starting from 5B4BH)
This block stores the time and date on which the e-mail is sent in
BCD code.
The order of date and time to be stored is the same as for the date
and time of e-mail reception shown in (a) 13).
13) Error log block Subject (address: starting from 5B4FH)
This block stores 15 words from the beginning of the Subject of the
e-mail.
11 - 21
11 - 21
11 TROUBLESHOOTING
MELSEC-Q
11.3.1 End codes (Complete codes) returned to an external device during data
communication
This section explains the end codes (complete codes) that are added to responses
when communicating using the fixed buffer, the random access buffer or the MC
protocol.
For more details on the error codes that are added to responses during communication
using A compatible 1E frames through the MC protocol, see Section 11.3.2.
For more details on the end codes (error codes) that are stored in the buffer memory of
the Ethernet module, see Section 11.3.3.
End code
Description
Communication function
Processing
Fixed
00H
Normal completion
02H
Designation of device range of devices to be read/written from/to is Check and correct the designated head
incorrect.
device and number of points.
Random
MC
50H
51H
52H
54H
55H
Fixed
11 - 22
Random
MC
11 - 22
11 TROUBLESHOOTING
End code
56H
57H
58H
Description
MELSEC-Q
Processing
Communication function
Fixed
Random
MC
5BH
60H
63H
A0H
to
FFFFH
11 - 23
The content of the error and the error handling for each end code are the same as for the error codes from A0H to FFFFH that are stored in the
buffer memory. Take a necessary action by referring to the description of the applicable error code shown in Section 11.3.3.
11 - 23
11 TROUBLESHOOTING
MELSEC-Q
Subheader
End code
Abnormal code
00H
Error code
(hexadecimal)
10H
Error
Description of error
Corrective action
11H
Mode error
Poor communication between the Ethernet module and the PLC CPU
(1) Communicate again. If an error occurs again,
(1) After the Ethernet module receives a request successfully from an
check noise, etc. and replace the Ethernet
external device, the Ethernet module and the PLC CPU could not
module, then communicate again.
communicate for some reason (noise, etc.).
12H
Intelligent function
module designation
error
18H
Remote error
1FH
Device error
20H
Link error
21H
Intelligent function
module bus error
11 - 24
11 - 24
11 TROUBLESHOOTING
MELSEC-Q
Buffer memory
Initial
69H (105)
Open
7CH (124)
Fixed sending
7DH (125)
Connection
7EH (126)
Error code
E5H (229)
Data link
HTTP log
5108 H (20744)
E-mail log
Dedicated instruction
5879H (22649)
Data link
7DH
7EH
E5H
5108H 5879H
Dedicated
instruction
Error code
7CH
E-mail log
Connection
69H
Error handling
HTTP log
Fixed
sending
Description of error
Open
Error code
(abnormal
code)
Initial
Storage destination
02H
0050H
0051H
0052H
0054H
0055H
0056H
The content of these errors and the error handling for each error code is the
same as the end codes (02H to 0063H) returned to the external device.
Check the explanation of the applicable code shown in Section 11.3.1, and
take actions accordingly.
0057H
0058H
0059H
005BH
0060H
0063H
00A0H
00A1H
00A2H
3E8H
to
4FFFH
11 - 25
11 - 25
11 TROUBLESHOOTING
MELSEC-Q
7EH
E5H
B000H
to
BFFFH
C001H
C002H
C003H
C004H
C005H
C006H
C007H
C010H
C011H
C012H
C013H
C014H
5108H 5879H
Dedicated
instruction
Data link
7DH
E--mail log
Error code
7CH
HTTP log
Connection
69H
Error handling
7000H
to
7FFFH
11 - 26
Fixed
sending
Description of error
Open
Error code
(abnormal
code)
Initial
Storage destination
11 - 26
11 TROUBLESHOOTING
MELSEC-Q
C015H
C016H
C017H
C018H
C020H
C021H
C022H
C023H
C031H
11 - 27
7EH
E5H
5108H 5879H
Dedicated
instruction
Data link
7DH
E-mail log
Error code
7CH
HTTP log
Connection
69H
Error handling
C030H
Fixed
sending
Description of error
Open
Error code
(abnormal
code)
Initial
Storage destination
11 - 27
11 TROUBLESHOOTING
MELSEC-Q
C032H
C033H
C035H
C036H
C040H
C041H
C042H
C043H
11 - 28
E5H
5108H 5879H
Dedicated
instruction
7EH
E-mail log
Data link
7DH
HTTP log
Error code
69H 7CH
Check the operation of the external
device.
Correct the TCP ULP timeout value and
execute the initial processing again.
A TCP ULP timeout error occurred
Send after an arbitrarily selected time has
in the TCP/IP communication.
elapsed because packets may be
(An external device does not return
congested on the line.
ACK.)
Check that the connection cable is not
dislocated.
Check that connections to the transceiver
and terminator are not faulty.
Connection
Error handling
Fixed
sending
Description of error
Open
Error code
(abnormal
code)
Initial
Storage destination
11 - 28
11 TROUBLESHOOTING
MELSEC-Q
C044H
to
C048H
Dedicated
instruction
E-mail log
E5H
HTTP log
7EH
Data link
7DH
5108H 5879H
C049H
C04AH
C04BH
C04CH
C04DH
C050H
C051H
to
C054H
C055H
The number of file data read/write Correct the number of read/write points
points is outside the allowable
(or byte points) and send to the Ethernet
range.
module again.
C056H
11 - 29
Error code
69H 7CH
Connection
Error handling
Fixed
sending
Description of error
Open
Error code
(abnormal
code)
Initial
Storage destination
11 - 29
11 TROUBLESHOOTING
MELSEC-Q
C057H
C058H
C059H
C05AH
C05BH
C05CH
C05DH
C05EH
C05FH
C060H
C061H
C062H
C070H
C071H
C072H
C073H
11 - 30
E5H
5108H 5879H
Dedicated
instruction
7EH
E-mail log
Data link
7DH
HTTP log
Error code
69H 7CH
Connection
Error handling
Fixed
sending
Description of error
Open
Error code
(abnormal
code)
Initial
Storage destination
11 - 30
11 TROUBLESHOOTING
MELSEC-Q
C074H
C080H
C081H
C082H
C083H
7EH
E5H
5108H 5879H
Dedicated
instruction
Data link
7DH
E-mail log
Error code
7CH
HTTP log
Connection
69H
Error handling
C084H
C085H
C086H
C087H
C0B2H
C0B3H
C0B5H
C0B6H
C0B7H
11 - 31
Fixed
sending
Description of error
Open
Error code
(abnormal
code)
Initial
Storage destination
11 - 31
11 TROUBLESHOOTING
MELSEC-Q
C0B8H
C0B9H
C0BAH
C0BBH
System error
The OS detected any error.
C0BCH
C0BDH
C0BFH
System error
The OS detected any error.
C0C1H
C0C2H
to
C0C4H
System error
The OS detected any error.
5108H 5879H
Dedicated
instruction
Data link
E-mail log
Error code
HTTP log
Connection
E5H
C0C5 H
C0C6H
System error
The OS detected any error.
C0C7H
C0C8H
to
C0CAH
System error
The OS detected any error.
C0CBH
1)
1)
1)
C0D0H
C0D1H
11 - 32
7EH
1)
System error
The OS detected any error.
7DH
1)
C0C0H
C0CFH
7CH
1)
C0CCH
69H
Error handling
C0BEH
Fixed
sending
Description of error
Open
Error code
(abnormal
code)
Initial
Storage destination
11 - 32
11 TROUBLESHOOTING
MELSEC-Q
C0D5H
C0D6H
C0D7H
C0D8H
The number of blocks exceeded the Correct the designation value for the
range.
number of blocks.
C0D9H
C0DAH
C0DBH
C0D3H
C0D4H
C0DCH
C0DDH
System error
The OS detected any error.
C0DEH
C0DFH
System error
The OS detected any error.
E5H
5108H 5879H
Dedicated
instruction
Data link
7EH
E-mail log
Error code
7DH
HTTP log
Connection
7CH
1)
1)
C0E0H
to
C0EFH
C0F0H
C0F1H
11 - 33
69H
Error handling
C0D2H
Fixed
sending
Description of error
Open
Error code
(abnormal
code)
Initial
Storage destination
11 - 33
11 TROUBLESHOOTING
MELSEC-Q
C0F3H
C0F4H
to
C0F6H
System error
The OS detected any error.
C100H
System error
The OS detected any error.
E5H
5108H 5879H
Dedicated
instruction
Data link
7EH
E-mail log
Error code
7DH
HTTP log
Connection
7CH
1)
1)
C102H
C103H
C104H
to
C106H
System error
The OS detected any error.
C101H
69H
Error handling
C0F7 H
Fixed
sending
Description of error
Open
Error code
(abnormal
code)
Initial
Storage destination
1)
C110H
C111H
C112H
11 - 34
11 - 34
11 TROUBLESHOOTING
MELSEC-Q
C113H
C114H
C115H
to
C118H
System error
The OS detected any error.
C119H
C11AH
C11BH
C11CH
C11DH
11 - 35
Data link
7DH
7EH
E5H
5108H 5879H
Dedicated
instruction
Error code
7CH
E-mail log
Connection
69H
Error handling
HTTP log
Fixed
sending
Description of error
Open
Error code
(abnormal
code)
Initial
Storage destination
1)
11 - 35
11 TROUBLESHOOTING
MELSEC-Q
7EH
E5H
5108H 5879H
Dedicated
instruction
Data link
7DH
E-mail log
Error code
7CH
HTTP log
Connection
69H
Error handling
C120H
C121H
C122H
C123H
C124H
C125H
C126H
C127H
C130H
C131H
C132H
C133H
C134H
to
C137H
System error
The OS detected any error.
C138H
C139H
System error
The OS detected any error.
C13AH
C13BH
C13CH
System error
The OS detected any error.
11 - 36
Fixed
sending
Description of error
Open
Error code
(abnormal
code)
Initial
Storage destination
1)
1)
1)
11 - 36
11 TROUBLESHOOTING
MELSEC-Q
7EH
E5H
5108H 5879H
Dedicated
instruction
Data link
7DH
E-mail log
Error code
7CH
HTTP log
Connection
69H
Error handling
C140H
C141H
C142H
C143H
C144H
C145H
C146H
C147H
C150H
C151H
The Ethernet modules mail address Check the account name in the mailbox
(e-mail address setting parameter) is
on the server side and correct the
different from the account name in
mailbox account set for the Ethernet
the mailbox on the server side.
module.
C152H
The Ethernet modules password (e Check the password on the server side
mail setting parameter) is different
and correct the password set for the
from the password on the server
Ethernet module.
side.
C153H
C154H
C160H
C161H
11 - 37
Fixed
sending
Description of error
Open
Error code
(abnormal
code)
Initial
Storage destination
11 - 37
11 TROUBLESHOOTING
MELSEC-Q
C162H
C163H
C171H
to
C17FH
A response to a request could not be Review and correct the response wait
received.
time.
C1A4H
C1A5H
C1A6H
C1A7H
C1A8H
C1A9H
C1AEH
C1AFH
C1B0H
C1B1H
C1B2H
C1B3H
C1B4H
C1B5H
C1B6H
11 - 38
5108H 5879H
Dedicated
instruction
Data link
E5H
E-mail log
Error code
7EH
HTTP log
Connection
7DH
Execute again.
If the same error occurs, the Ethernet
modules hardware may be faulty.
Consult your nearest dealer with the
details of the error.
C1A2H
C1ADH
7CH
C1ACH
69H
Error handling
C1A0H
C1AAH
Fixed
sending
Description of error
Open
Error code
(abnormal
code)
Initial
Storage destination
11 - 38
11 TROUBLESHOOTING
MELSEC-Q
C1B7H
C1B8H
C1B9H
C1BA H
C1BBH
C201H
C202H
C203H
System error
The OS detected any error.
C205H
C206H
System error
The OS detected any error.
C207H
C300 H
F000H
to
FFFFH
5108H 5879H
Dedicated
instruction
E5H
E-mail log
7EH
HTTP log
7DH
1)
1)
11 - 39
7CH
69H
C200H
C204H
Data link
Error code
Connection
Error handling
Fixed
sending
Description of error
Open
Error code
(abnormal
code)
Initial
Storage destination
11 - 39
11 TROUBLESHOOTING
MELSEC-Q
REMARK
Depending on the restrictions of the buffers of the local station and external device,
data may be divided for communication.
Data received separately is restored (reassembled) by the Ethernet module to be
communicated using the fixed buffer, random access buffer, etc. The received data
is restored (reassembled) based on the data length in the communication data.
The Ethernet module performs the following processing if data among the
communication data is incorrect.
(1) When communication is performed using fixed buffer (with procedure) and
random buffer
(a) If the data length specified immediately after the subheader is smaller than
the amount of text data received
1) The data immediately following the part of the text data equivalent to
the data length specified immediately after the subheader will be
regarded as the next message.
2) Since the header of each message will be a subheader, the Ethernet
module performs processing according to the code in the subheader.
3) If the subheader contains a code that is not recognized by the
Ethernet module, the Ethernet module will send a response notifying
about abnormal completion to the external device.
Data sent by an external device
Sub
header
(Second data)
Sub
header
This section is processed as a subheader.
11 - 40
11 - 40
11 TROUBLESHOOTING
MELSEC-Q
(b) If the data length specified immediately after the subheader is larger than
the amount of text data received
1) The Ethernet module waits for the reception of the remaining missing
data.
2) If the remaining data could be received within the time allotted by the
response monitoring timer, the Ethernet module performs processing
according to the code in the subheader.
3) If the remaining data could not be received within the time allotted by
the response monitoring timer, the Ethernet module performs the
following processing.
Sends the ABORT (RST) instruction to the external device and
closes the line.
Notifies about occurrence of an open error to the PLC CPU side via
the open error detection signal (X18 = ON).
Stores the error code in the open error code storage area. (The
error code is not stored in the error log storage area.)
POINT
Designate the actual data size of the text field for "data length" specified in the
application data field of a message sent from the external device to the Ethernet
module.
The Ethernet module never sends a text whose size is different from the specified
data length to the external device.
(2) When communication is performed using fixed buffer (non-procedure)
Since no message data length is specified in non-procedure communication,
the data received is stored in the receive buffer area as is.
It is recommended to set up some method of checking that the data is received
correctly. This can for instance be achieved by including the data length and
data type code in the application data of the message, so that the number of
bytes and data type of application data can be identified on the receiving side.
11 - 41
11 - 41
11 TROUBLESHOOTING
MELSEC-Q
POINT
If trouble occurs when using the Ethernet module, check the module status, error
status and others for the Ethernet module using the Ethernet diagnostic function of
GX Developer described in Section 11.2.
Data cannot be communicated.
Did an error
that makes the PLC CPU
stop processing
occur?
YES
NO
Check the status of the applicable
Ethernet module.
NO
YES
NO
YES
NO
YES
11 - 42
NO
11 - 42
11 TROUBLESHOOTING
MELSEC-Q
1)
Is initial processing
normally completed
(X19 = ON)?
NO(X19 = OFF)
YES
NO
YES
Check the contact status of the power
supply module of the station in which
the Ethernet module is installed.
(LG and FG terminal grounding)
NO
YES
YES
NO
Check and fix the faulty part for each
communication processing.
Data length
Subheader
Subheader
Text
60 H00 H
45 H 30 H 35 H 34 H
11 - 43
End code
11 - 43
11 TROUBLESHOOTING
MELSEC-Q
3 If the LG and FG terminals of the power supply module of the station in which the Ethernet module is installed are not grounded, the
communication line is closed (disconnected) due to the effects of noise, and as a result communication with an external device may not
be performed.
Turn off the power to the station in which the Ethernet module is installed and ground the LG and FG terminals of the power supply
module after referring to the section in the PLC CPU User's Manual that explains the wiring procedure.
POINT
(1)
When the Ethernet module is replaced due to an error, reboot the following
external devices and restart data communication:
All external devices that communicated with the station whose Ethernet
module was replaced.
All external devices that communicated with other stations PLC CPU via a
station whose Ethernet module was replaced.
(2)
When connecting a device to the Ethernet module, see the following sections
for the required devices and connection method:
Section 2.2: Devices Required for Network Configuration
Section 4.4: Connection Method Check
(3)
If the Ethernet module could not receive messages sent from external devices
frequently, check the values stored in the following buffer memory.
(a) Simultaneous transmission error detection count storage area (address:
18EH to 18FH) and Error/End code storage area for each error log block
(address: E5H)
When the error detection count number is high or when the error code
C0C7H has been stored, high load may be applied to the Ethernet
connection line to transfer data among connected devices.
To reduce the load to the Ethernet line, it is necessary to take corrective
measures such as dividing the network or reducing the data transmission
frequency.
Consult your network administrator and take appropriate measures.
(b) TCP packet reception count storage area (address: 1B8H, 1B9H)
When data cannot be received even though TCP packet reception count
has been renewed, set 8000H (Disable TCP Maximum Segment Size
Option transmission) to the TCP Maximum Segment Transmission setting
area (address: 1EH) and execute re-initialization.
(For re-initialization, refer to Section 5.2.3.)
(4)
11 - 44
11 - 44
11 TROUBLESHOOTING
MELSEC-Q
Is the applicable
connection open?
(Buffer memory address:
applicable bit of 5000H)
NO
YES
Read the open abnormal code (buffer
memory address 124, 134...) of the
communication status storage area
and check that no errors have occurred.
Have parameter
errors occurred?
NO
NO
NO
YES
Read the content of the communication
abnormal code storage area
(buffer memory address 125, 135...)
corresponding to the fixed buffer of the
buffer memory and check whether or not
a communication error has occurred.
Has a communication
error occurred?
YES
Is the parameter,
IP address of the external device,
correct?
YES
Does the
communication protocol
(TCP/UDP) match that of
the external device?
NO
YES
1)
11 - 45
11 - 45
11 TROUBLESHOOTING
MELSEC-Q
1)
NO
YES
Did the BUFSND
instruction complete
normally?
NO
YES
Is the send data
length set in the
control data?
NO
YES
Check the communication status of
the external device.
NO
YES
Are there any
open errors or initial errors
in the error log area?
NO
YES
The Ethernet module hardware on the
sending side may be faulty.
Consult your nearest dealer with the
details of the errors.
11 - 46
11 - 46
11 TROUBLESHOOTING
MELSEC-Q
NO
YES
Check the open status of the
connection with an external device.
Is the applicable
connection open?
(Buffer memory address:
applicable bit of 5000H)
NO
YES
Read the open abnormal code (buffer
memory address 124, 134...) of the
communication status storage area
and check that no errors have occurred.
NO
NO
YES
Read the content of the communication
abnormal code storage area (buffer
memory address 126, 136...)
corresponding to the fixed buffer of the
buffer memory and check whether or not
a communication error has occurred.
Has a
communication error occurred in the
error log area?
YES
1)
11 - 47
11 - 47
11 TROUBLESHOOTING
MELSEC-Q
1)
Is the parameter,
IP address of the external
device, correct?
NO
NO
YES
YES
Is the receive
completion signal (buffer
memory address: corresponding
bit of 5005H) of the applicable
fixed buffer on?
NO
YES
Did the error
occur in the device on the
sending side?
NO
YES
NO
YES
Was the dedicated BUFRCV
instruction executed?
Was the dedicated BUFRCVS
instruction executed?
YES
NO
YES
NO
NO
YES
YES
NO
2)
11 - 48
11 - 48
11 TROUBLESHOOTING
MELSEC-Q
2)
NO
YES
11 - 49
11 - 49
11 TROUBLESHOOTING
MELSEC-Q
Is the applicable
connection open? (buffer memory
address: corresponding bit
of 5000H)
NO
YES
Was a command
sent form the external
device?
NO
Send the command to the Ethernet module.
YES
Was a response
returned to the device that
sent the command?
NO
Is the IP address
designation of the command
correct?
YES
NO
NO
YES
Does the
communication protocol
(TCP/UDP) match with that of
the external device?
YES
The command may not be sent to the
Ethernet module from the external
device on the command sending side.
Check the sending side.
NO
YES
1)
11 - 50
11 - 50
11 TROUBLESHOOTING
MELSEC-Q
1)
Is the IP address
of the command
correct?
NO
YES
Is the buffer
memory address designation
of the Ethernet module set for
the command
correct?
NO
YES
Is the command
a data write from the external
device?
NO (Data read)
YES
NO
YES
Is the data to
be written set on the
external side?
NO
Write data.
YES
Are there
any open errors or initial
errors in the error
log area?
NO
YES
The Ethernet module hardware may
be faulty. Consult your nearest
dealer with the details of the errors.
11 - 51
11 - 51
11 TROUBLESHOOTING
MELSEC-Q
Is the applicable
connection open? (buffer
memory address: corresponding
bit of 5000 H)
NO
YES
NO
Send the command to the Ethernet module.
YES
Was a response
returned to the device that sent
the command?
NO
Is the IP address
designation of the command
correct?
YES
NO
NO
YES
Does the
communication protocol
(TCP/UDP) match with that of the
external device?
YES
The command may not be sent to the
Ethernet module from the external device
on the command sending side. Check the
sending side.
NO
YES
1)
11 - 52
11 - 52
11 TROUBLESHOOTING
MELSEC-Q
1)
NO
NO
YES
Are the
command formats,
such as command type, device
designation, and address
designation, designated
correctly?
YES
NO
YES
The Ethernet module hardware may
be faulty. Consult your nearest dealer
with the details of the errors.
11 - 53
11 - 53
11 TROUBLESHOOTING
MELSEC-Q
NO
Correct the execution condition of the
MSEND instruction.
YES
YES
NO
YES
11 - 54
11 - 54
11 TROUBLESHOOTING
MELSEC-Q
YES
NO
YES
NO
NO
YES
Modify the condition devices.
YES
1) Correct the following so that the
monitoring condition disable time satisfies
"Disable time > CPU inquiry interval."
CPU inquiry interval
Device value of the notification condition.
2) Perform the following so that the
sending time between the SMTP
server and the Ethernet module satisfies
"sending time < CPU inquiry interval."
Decrease the load on the SMTP server.
If the SMTP server and the Ethernet
module are connected via routers, etc.,
connect the Ethernet module to the
same main line as the SMTP server.
POINT
Check the following items before using the e-mail function:
(1) System configuration and environment:
Section 2.2 of the Users Manual (Application)
11 - 55
(2)
(3)
11 TROUBLESHOOTING
MELSEC-Q
YES
NO
Is the e-mail
receiving error log
normal?
NO
YES
Was the
dedicated MRECV
instruction
executed?
NO
YES
NO
No inquiry?
YES
Correct the executing condition of the
dedicated MRECV instruction.
Was the
dedicated MRECV
instruction normally
completed?
NO
Correct the error according to the error code in the MRECV instruction complete status area.
For details on the MRECV instruction, refer to Section 2.6.4 of the User's Manual (Application).
YES
YES
No attached file.
NO
Receiving
stops in the middle of
process?
NO
YES
1)
11 - 56
11 - 56
11 TROUBLESHOOTING
MELSEC-Q
1)
Is the receive
data value incorrect?
(Characters got
garbled)
NO
YES
NO
YES
Codes other than "0 to 9" and "A to F" are used.
Is the
NO
sending side the Ethernet
module?
YES
11 - 57
11 - 57
11 TROUBLESHOOTING
MELSEC-Q
YES
4)
NO
Check the error log area (buffer
memory address: E3H to 174H) of the
Ethernet module mounted on the main
base unit of the control system CPU.
C032H
(TCP ULP timeout error)
or
C035H
(Existence check error)
Is "Issue
system switching request at
communication error" checked
in the redundant
setting?
No error code
NO
YES
Is "Systemswitching
settings when communication
error occurs" checked in the
redundant setting?
NO
YES
Check the "System switching settings
when communication error occurs"
status storage area. (Buffer memory
address: 5210H, 5211H)
NO
YES
4)
11 - 58
11 - 58
11 TROUBLESHOOTING
MELSEC-Q
1)
Is disconnection detected?
NO
2)
YES
Check the Ethernet parameters.
Is "Issue
system switching request
at disconnection detection"
checked in the redundant
setting?
NO
YES
Check the "Issue system switching
request at disconnection detection"
status storage area. (Buffer memory
address: 5200H)
Are the
settings of
GX Developer consistent with the
contents of the buffer
memory?
NO
YES
Check the "cable disconnection
timeout setting". (Buffer memory
address: 5201H)
Is the setting
of the cable disconnection
timeout setting
correct?
NO
YES
4)
11 - 59
11 - 59
11 TROUBLESHOOTING
MELSEC-Q
2)
Is the communication
target in the error status?
NO
3)
YES
Check the Ethernet parameters.
NO
YES
Is the "existence
check" of the open setting set
to "Check"?
NO
YES
Is the "existence
check starting interval timer"
setting value of the initial
setting correct?
NO
NO
YES
Is the "existence
check interval timer" setting value
of the initial setting
correct?
YES
Is the
"communication target IP
address" of the open setting set
to broadcast?
YES
NO
Check the initial processing
parameter setting area (buffer
memory address: 0 to 14H) and
communication parameter setting
area (buffer memory area: 20 to 5FH).
NO
YES
Check the connection status.
NO
YES
4)
11 - 60
11 - 60
11 TROUBLESHOOTING
MELSEC-Q
3)
YES
NO
4)
11 - 61
11 - 61
11 TROUBLESHOOTING
MELSEC-Q
4)
YES
NO
Check the mounted CPU.
Is the standby
system powered ON?
NO
YES
Is the RESET/L.CLR
switch of the standby system
CPU in the neutral position
(unreset)?
NO
YES
Is the tracking cable
connected normally?
NO
YES
Is the standby system
CPU normal?
NO
YES
Is the mounted CPU a
control system?
NO
YES
Has any
reason for system
switching failure (e.g. stop
error of standby system CPU),
if a system switching request
is issued from the Ethernet
module, occurred?
NO
YES
Is the CPU in the
backup mode?
NO
YES
Please consult your local Mitsubishi
service center or representative,
explaining a detailed description of
the problem.
11 - 62
11 - 62
11 TROUBLESHOOTING
MELSEC-Q
Has "OPS
connection" been set in the
open system of the
open setting?
NO
YES
Is the local
station port number of the
Ethernet module
correct?
NO
YES
NO
YES
YES
NO
YES
NO
Is the MELSOFT
product used?
NO
Is EZSocket used on
the OPS side?
YES
The possible cause is other than
above or external device fault.
Execute the troubleshooting for the
case where data communication
cannot be made.
(Refer to Section 11.4.)
11 - 63
11 - 63
APPENDIX
MELSEC-Q
APPENDIX
Appendix 1 Function Upgrade for the Ethernet Module
The Ethernet module of function version B or later contains several functions not
included in the earlier product (function version A).
This section gives a comparison of functions of the Ethernet module based on the
function change or addition and explains program utilization and incorporation into an
existing system.
QJ71E71-100
QJ71E71-B5
QJ71E71-B2
100 Mbps
10 Mbps
Sequence program
GX Developer network parameter setting
Sequence program
Dedicated instruction
Sequence program
GX Developer network parameter setting
QnA compatible 3E frame
A compatible 1E frame
No procedure
Procedure exist
Sending/receiving e-mail
Checking by PING
Checking by KeepAlive
Unlock processing/
lock processing
GX Developer
File transfer (FTP server)
function
Communication using the Web
function
App - 1
App - 1
App
APPENDIX
MELSEC-Q
Function
QJ71E71-100
QJ71E71-B5
QJ71E71-B2
App
Access to non-control
PLC
PING test
Self-loop back test
PING test
: Can be used.
: Can be used. (However, there are restrictions on the product serial No.
(manufactured date)) ( 1)
: Cannot be used.
1 : There is a time limit on the manufacturing date of Ethernet modules that
can support this function. For how to check the function version, see
Section 2.7.
POINT
For the description of the following items, see Section 2.7.
How to check the function version of the Ethernet module
Correspondence with related products (CPU modules, GX Developer) that can
use added functions.
App - 2
App - 2
APPENDIX
MELSEC-Q
Appendix 1.2 Precautions when updating the module from function version A to function
version B or later
This section explains the utilization of programs created for the Ethernet module of
function version A and incorporation into an existing system.
App - 3
App - 3
APPENDIX
MELSEC-Q
Product name
AJ71E71
AJ71E71-S3
AJ71E71N
QE71
QE71N
Appendix 2.1 Functional comparisons between the Ethernet modules and QnA/A series
modules
The following tables list the functional comparisons of the Ethernet modules and
QnA/A series modules.
The symbol in the model name columns indicates that the corresponding functions
are compatible between the applicable models. (See each modules manual for details.)
indicates functions that have been added to or modified from the QnA/A
series modules.
Function
1 Initial processing
2 Open processing
3
AJ71E71
AJ71E71QE71, QE71N
S3,
Products earlier Products
after 9706B
AJ71E71N than 9706
QJ71E71-100,
QJ71E71-B5,
QJ71E71-B2
Sequence program
Sequence program
Interrupt processing
(at data receiving)
Sending/receiving of
8
e-mail
)
)
)
10
For communication
between the PLC CPUs
BUFRCVS instruction
RECVS instruction
11
Simultaneous broadcast
function
(
For communication
using the fixed buffer
Ping
KeepAlive
(Fixed)
(Fixed)
(Fixed)
(Fixed)
UDP/IP
(
20 Installation of EEPROM
21 TCP Maximum Segment Size Option transmission
13
13
App - 4
11 Simultaneous broadcast
9 File transfer
10 Sending by the Web function
18
Remark
12
App - 4
APPENDIX
MELSEC-Q
1 Applicable when the modules software version is earlier than "Q version".
2 The availability of the function depends on the date of manufacture/software version of the PLC CPU and SWnIVD/NX-GPPQ model GPP function
software package.
3 A sequence program using input/output signals cannot be used together with the parameter settings from GX Developer.
4 Compatible with the input/output signals and the buffer memory of the QE71, QE71N.
5 The function is compatible, but cannot be used together with the e-mail sending/receiving function for sequence program.
6 When "Always wait for OPEN" is set in the network parameters of GX Developer, the conventional sequence programs are not required.
When using this function in the conventional sequence programs, the following conditions are not applicable. (It will not operate correctly because the
same area is used.)
"Always wait for OPEN" is set in the operational setting of the network parameters.
"MELSOFT connection" is set in the open setting of the network parameters.
Re-initial processing (with UINI instruction, buffer memory) is used in the sequence programs.
7 EEPROM is not installed. Items that were previously stored in the EEPROM in the QE71, QE71N are now stored by parameter setting from GX Developer.
8 By performing parameter setting from GX Developer, the initial processing is executed when the Ethernet module starts up. A conventional sequence
program is not required.
9 The number of connections which can be opened from the PLC CPU has been increased to 16 for the Ethernet module. Also, when executing the Passive
open processing for TCP/IP communication and the open processing for UDP/IP, the open processing is executed when the Ethernet module starts up by
setting the "Always wait for OPEN" parameter from GX Developer. A conventional sequence program is not required.
10 When the Ethernet module is used, a maximum of 960 words can read/written (a maximum of 480 words for the QE71, QE71N).
11 This cannot be used together with the communication function using the random access buffer.
12 TCP Maximum Segment Size Option transmission is available for the product with the serial number which first 5 digits are 05051 or later.
In the QJ71E71-100, QJ71E71-B5, QJ71E71-B2 with the first 5 digits of serial No. 05051 to 05081, the default value is preset to "Enable TCP Maximum
Segment Size Option transmission". If normal communication cannot occur due to incorrect combination with the other node, change the setting to
"Disable TCP Maximum Segment Size Option transmission".
To change the TCP Maximum Segment Size Option transmission setting, change the TCP Maximum Segment Transmission setting area and execute
re-initialization. (For re-initialization, refer to Section 5.2.3.)
13 TCP Maximum Segment Size Option transmission is applicable when the software version of the QE71N or AJ71E71N is "E" or later.
Note that the default is set to disable TCP Maximum Segment Size Option transmission. (Enabled when retransmitting TCP data)
POINT
The Ethernet modules response speed to an external device is faster than that of
the Ethernet modules for the A/QnA series.
Keeping compatibility with the Ethernet modules for the A/QnA series strictly is not
possible when using this Ethernet module. If this becomes a problem when
considering the performance of an external device, try to make the timing similar to
that of the conventional system using the QCPU constant scan setting or other
applicable settings.
App - 5
App - 5
APPENDIX
MELSEC-Q
Appendix 2.2 Using the programs designed for QnA/A series modules
The data communication that was previously performed between the PLC CPU and an
external device on the Ethernet using a QnA/A series Ethernet interface module (such
as the AJ71E71) can also be performed using an Ethernet module.
The following explains how to use the programs designed for conventional modules to
perform data communication using the Ethernet module.
(1) Using the programs designed for the AJ71E71(-S3) and AJ71E71N
(a)
Ethernet module
External device
E71
Ethernet
module
Ethernet
module
E71
(b)
Using the sequence programs designed for the local stations E71.
The Ethernet module and the E71 have different buffer memory
assignments, thus the sequence programs designed for the E71 cannot be
utilized for the Ethernet module.
Create a new program referring to the chapters that explain each of the
applicable functions.
App - 6
App - 6
APPENDIX
MELSEC-Q
(b)
2)
3)
However, since the Ethernet module and the QE71 have different response
speeds, the programs may not be used as is. Make sure to test the
operation first.
REMARK
Keep the following points in mind when utilizing the programs.
Do not use the sequence program for initial processing together with initial
processing by parameter setting from GX Developer.
Do not execute the following operations to the same connection simultaneously:
open/close processing using input/output signals and open/close processing using
the OPEN/CLOSE dedicated instructions, as well as the fixed buffer
sending/receiving and sending/receiving processing using the
BUFSND/BUFRCV/BUFRCVS instruction.
Furthermore, when setting parameters for the Ethernet module and communicating
with the QCPU, make sure to use GX Developer (SW4D5C-GPPW-E or later).
App - 7
App - 7
APPENDIX
MELSEC-Q
POINT
(1) The operating mode and communication conditions can be set via the following
parameter setting screen of GX Developer when using Q Series Ethernet
modules:
"Network Parameters Setting the number of MNET/10H Ethernet cards"
screen
"Ethernet operational setting" screen
(2) On Q Series Ethernet modules, there are no setting switches for making the
operating mode settings and communication condition settings like there were
on QnA/A Series Ethernet interface modules.
(3) The Q Series Ethernet module cannot cancel an open request before
completing the open processing once the passive open processing is executed.
Perform the close processing after the open processing is complete.
App - 8
App - 8
APPENDIX
MELSEC-Q
QJ71E71-B5, QJ71E71-B2
Communication using
Communication using
TCP/IP
UDP/IP
Ke
Kdf
Ke
Kdf
Ke
Kdf
Ke
Kdf
12
0.0065
10
0.0069
25
0.020
20
0.019
12
0.030
10
0.029
26
0.068
21
0.068
(b)
QJ71E71-B5, QJ71E71-B2
Communication using
Communication using
TCP/IP
UDP/IP
Ke
Kdf
Ke
Kdf
Ke
Kdf
Ke
Kdf
0.0018
0.0014
16
0.0057
0.0025
[Calculation example]
Calculate the time from the start of sending to the completion of
sending (unit: ms) when the QJ71E71-B5 communicate using TCP/IP
and send 1017 words of binary code data using fixed buffer
communication (procedure exist).
Assume that the scan time on the receiving side is 10 ms and the
scan time on the transmission side is 8 ms:
63.34 (ms) 10 + 25 + (0.020 1017) + 8
App - 9
App - 9
APPENDIX
MELSEC-Q
(2) Minimum processing time of communication using the random
access buffer
Trs = Kr + (Kdr Df) + ACK processing time of an external device
(Added only for TCP/IP communication)
Trs
Read
Write
QJ71E71-B5, QJ71E71-B2
Communication using
UDP/IP
Communication using
TCP/IP
Communication using
UDP/IP
Kr
Kdr
Kr
Kdr
Kr
Kdr
Kr
Kdr
3.1
0.004
2.1
0.005
9.4
0.008
6.6
0.008
3.1
0.016
2.2
0.016
9.1
0.030
6.5
0.030
3.1
0.006
2.1
0.005
9.5
0.014
6.6
0.012
3.1
0.017
2.2
0.015
9.6
0.042
6.7
0.036
[Calculation example 1]
Calculate the time the QJ71E71-B5 takes to complete the processing
of a data request from a PC after receiving it, when the QJ71E71-B5
and the PC communicate using TCP/IP and read 508 words of binary
code data from the random access buffer (unit: ms).
13.46 + ACK processing time of the external device (ms)
9.4 (0.008 508) + ACK processing time of the external device
[Calculation example 2]
Calculate the time the QJ71E71-B5 takes to complete the processing
of a data request from a PC after receiving it, when the QJ71E71-B5
and the PC communicate using TCP/IP and write 508 words of binary
code data to the random access buffer (unit: ms).
16.61 + ACK processing time of the external device (ms)
9.5 + (0.014 508) + ACK processing time of the external device
App - 10
App - 10
APPENDIX
MELSEC-Q
(3) Minimum processing time of communication using the MC protocol
(batch read and batch write)
Tfs = Ke + (Kdt Df) + Scr number of scans required for processing +
ACK processing time of external device
Tfs
Response
message
ACK
(TCP only)
ACK
(TCP only)
Ethernet module
END
Step 0
END
Step 0
2 When data is relayed via the tracking cable of the redundant system,
add the tracking time. For the data transfer time in the tracking cable,
refer to the QnPRHCPU User's Manual (Redundant System).
QJ71E71-100
Communication using
Communication using
TCP/IP
UDP/IP
Ke
Kdt
Ke
Kdt
Batch
read
Batch
write
App - 11
QJ71E71-B5, QJ71E71-B2
Communication using
Communication using
TCP/IP
UDP/IP
Ke
Kdt
Ke
Kdt
14
0.009
13
0.008
21
0.012
19
0.011
18
0.015
13
0.017
23
0.020
18
0.020
14
0.009
13
0.008
21
0.020
19
0.013
16
0.027
14
0.027
22
0.037
20
0.033
App - 11
APPENDIX
MELSEC-Q
[Calculation example 1]
Calculate the time the QJ71E71-B5 takes to complete the processing
of a data request from a PC after receiving it, when the QJ71E71-B5
and the PC perform TCP/IP communication and read 100 points of
ASCII code data from the data register (D) of the local station (unit:
ms) using the MC protocol communication.
Assume that the scan time of the station in which QJ71E71-B5 is
installed is 10 ms:
37.64 + ACK processing time of the external device (ms)
23 + (0.020 (21 + 211)) + 10 1 + ACK processing time of the
external device
Command data length = 21 words
Response data length = 211 words
[Calculation example 2]
Calculate the time the QJ71E71-B5 takes to complete the processing
of a data request from a PC after receiving it, when the QJ71E71-B5
and the PC performs TCP/IP communication and write 100 points of
ASCII code data to the data register (D) of the local station (unit: ms)
using the MC protocol communication.
When "Enable Write at RUN time" is set
Assume that the scan time of the station in which QJ71E71-B5 is
installed is 10 ms:
40.58 (ms)
App - 12
App - 12
APPENDIX
MELSEC-Q
(4) Processing Time of the Dedicated Instructions
The following table shows approximate operation processing time of each
dedicated instruction. The operation processing time differs slightly depending on
the system configuration and communication protocol.
(a) QJ71E71-100
Instruction name
BUFRCV
BUFRCVS
2)
1 word
1017 words
BUFSND
CLOSE
ERRCLR
ERRRD
For 1)
1.3
0.5
For 2)
1.8
0.9
12.8
19.2
11.5
18.1
Q00J/Q00/Q01CPU
For 1)
2.2
For 2)
5.8
14.0
23.5
1 port
3.3
3.2
4.2
2.2
1.2
2.0
0.8
3.4
2.4
OPEN
RECVS
READ,SREAD
RECV
SEND
WRITE,SWRITE
ZNRD
ZNWR
Q02CPU
1 port
3.8
480 words
1 word
230 words
UINI
0.6
14.2
2.1
7.9
14.3
14.4
14.2
3.0
0.8
19.7
3.2
11.2
20.0
17.1
17.5
0.3
14.1 1
2.0
7.5
14.0 1
13.8
13.9
21.5
4.2
0.5
18.7 1
2.9
10.8
19.2 1
16.6
16.4
11.7
1.8
11.5
11.5
12.1
12.0
21.2
17.9
4.3
16.8
16.8
14.1
14.8
Instruction execution
condition
TCP/IP communication,
binary code communication,
fixed buffer communication
(procedure exist)
Closes the UDP/IP
communication port
Communication between
stations in which Ethernet
modules are installed
21.8
1 When data is relayed via the tracking cable of the redundant system,
add the tracking time. For the data transfer time in the tracking cable,
refer to the QnPRHCPU User's Manual (Redundant System).
(b) QJ71E71-B5, QJ71E71-B2
Instruction name
BUFRCV
BUFRCVS
2)
1 word
1017 words
BUFSND
CLOSE
ERRCLR
ERRRD
UINI
For 1)
1.9
0.5
For 2)
2.4
0.9
27.6
45.3
24.5
45.0
Q00J/Q00/Q01CPU
For 1)
2.3
For 2)
5.8
28.2
50.0
1 port
4.5
4.5
6.0
2.7
1.7
2.2
1.1
3.4
2.5
OPEN
RECVS
READ,SREAD
RECV
SEND
WRITE,SWRITE
ZNRD
ZNWR
Q02CPU
1 port
480 words
1 word
230 words
4.3
0.6
30.1
5.3
21.4
30.0
29.0
29.7
3.3
0.8
41.1
6.6
30.4
41.8
34.3
36.4
21.5
0.3
27.7 1
5.2
20.3
29.4 1
29.0
29.4
5.2
0.5
40.0 1
6.3
29.1
40.9 1
34.7
35.2
21.2
27.7
5.3
22.8
28.2
27.8
27.6
38.9
8.2
30.8
37.9
33.2
33.4
21.8
Instruction execution
condition
TCP/IP communication,
binary code communication,
fixed buffer communication
(procedure exist)
Closes the UDP/IP
communication port
Communication between
stations in which Ethernet
modules are installed
1 When data is relayed via the tracking cable of the redundant system,
add the tracking time. For the data transfer time in the tracking cable,
refer to the QnPRHCPU User's Manual (Redundant System).
App - 13
App - 13
APPENDIX
MELSEC-Q
(5) System switching time of redundant system
The following indicates the system switching time required when the Ethernet
module mounted on the main base unit of the control system CPU in the
redundant system issues a system switching request to the control system CPU
at communication error or disconnection detection.
The system switching time is the time from when a communication error or
disconnection is detected until the control system CPU is switched to the standby
system CPU.
(a)
Communication
error occurrence
QJ71E71-100
Station No. 1
Tracking cable
System switching
request
Control system
operation
Ttu
Standby system
operation
System switching
request is issued
Control system
Standby system
Tsw
System B
Standby system
Control system
QJ71E71-100
(Station No. 2)
App - 14
App - 14
APPENDIX
MELSEC-Q
2)
Communication
error occurrence
QJ71E71-100
Station No. 1
QJ71E71-100
Station No. 2
System switching
request
QJ71E71-100
(Station No. 1)
Tracking cable
Ti
Ti
Ti
System switching
request is issued
Control system
System B
Standby system
Standby system
Tsw
Control system
QJ71E71-100
(Station No. 2)
App - 15
App - 15
APPENDIX
MELSEC-Q
(b)
Disconnection
occurrence
QJ71E71-100
(Station No. 1)
QJ71E71-100
(Station No. 2)
Tracking cable
Disconnection occurrence
QJ71E71-100
(Station No. 1)
Control system
operation
Td
Standby system
operation
System switching
request is issued
Control system
System B
Standby system
Control system
Standby system
Tsw
QJ71E71-100
(Station No. 2)
App - 16
App - 16
APPENDIX
MELSEC-Q
000
001
010
011
100
101
110
111
0000
NUL
DLE
(SP)
0001
SOH
DC1
0010
STX
DC2
0011
ETX
DC3
0100
EOT
DC4
0101
ENQ
NAK
0110
ACK
SYN
&
0111
BEL
ETB
1000
BS
CAN
1001
HT
EM
1010
LF
SUB
1011
VT
ESC
1100
FF
FS
<
1101
CR
GS
1110
SO
RS
>
1111
SI
US
DEL
Appendix 6 References
For details on TCP/IP, refer to the DDN Protocol Handbook (3 volumes).
Publisher
DDN Network Information Center
SRI International
333 Ravenswood Avenue, EJ291
Menlo Park, California 94025
RFC Number
TCP RFC793
UDP RFC768
IP
RFC791
ICMP RFC792
ARP RFC826
App - 17
App - 17
APPENDIX
MELSEC-Q
98 (3.86)
RUN
INIT.
OPEN
SD
10BASE-T/100BASE-TX
R1
( 1)
QJ71E71-100
90 (3.54)
27.4 (1.08)
(Unit: mm (in.))
1 When connecting a twisted pair cable, set the bending radius near the
connector (reference value: R1) as four times the cables outside diameter or
larger.
(2) QJ71E71-B5
QJ71E71-B5
RUN
INIT.
OPEN
SD
ERR.
COM.ERR.
RD
98 (3.86)
8.5 (0.33)
10BASE 5
R2
( 1)
12V
+ 12
12G
DC power supply
for transceiver
90 (3.54)
QJ71E71-B5
EXT. POWER
27.4 (1.08)
(Unit: mm (in.))
1 When connecting an AUI cable, set the bending radius near the connector
(reference value: R2) as four times the cables outside diameter or larger.
App - 18
App - 18
APPENDIX
MELSEC-Q
(3) QJ71E71-B2
QJ71E71-B2
RUN
INIT.
OPEN
SD
ERR.
COM.ERR.
RD
98 (3.86)
29.2 (1.15)
23.65 (0.93)
QJ71E71-B2
90 (3.54)
11.5
(0.45)
27.4 (1.08)
(Unit: mm (in.))
App - 19
App - 19
APPENDIX
MELSEC-Q
Receive remaining
response messages
Was the reception data
received within the time allotted
by the monitoring timer?
Insufficient size
of data received
Check the size of the received data
If a response message to
the next request was received
End
Error handling
Background
For Ethernet communications, the TCP socket functions are used inside the
personal computer. However, these functions do not have any limits. Therefore,
when the "send" function is executed once to transmit data, the receiving end (node)
needs to execute the "recv" function once or more in order to read the data ("send"
and "recv" is not proportional to 1:1 execution). For this reason, the receiving
procedure explained above, is required.
App - 20
App - 20
APPENDIX
MELSEC-Q
(2) When the transmission target does not support the receive
processing flow chart shown in section (1)
If the transmission target does not support the receive processing shown in
Section (1), the following results will occur when communicating with the "TCP
Maximum Segment Size Option transmission" is set to enable.
! Incorrect data read, when batch read is executed from the transmission
target using MC protocol.
! Incorrect data read, after replacing the Ethernet module (which does not
support the TCP Maximum Segment Size Option transmission function) with
the alternative module supporting the function.
! Data is not received, even though the value of "Number of packet reception"
area (Address: 1B8H, 1B9H) in the buffer memory was changed.
If this occurs, change the "TCP Maximum Segment Size Option transmission"
setting to disable.
(b)
(c)
: Microsoft Windows 95
operating system
Ethernet interface board model name : WINSOCK compatible board
Library
: WSOCK32.LIB
Communication protocol
: TCP/IP
App - 21
(a)
(b)
APPENDIX
MELSEC-Q
(3) GX Developer setting
Set the PLC CPU parameters as follows.
(a)
Operational settings
Open settings
App - 22
App - 22
APPENDIX
MELSEC-Q
(4) Program on the external device side
The program example of the external device shown below accesses the
Q25HCPU of the station in which the Ethernet module is installed.
When this program is executed, the contents of the following communication
messages are displayed in sequencer:
1)
2)
3)
4)
REMARK
(1)
(Create socket)
socket()
bind()
(Bind)
Passive open
(Open)
listen()
Active open
UDP
connect()
accept()
(Communicate)
(Disable sending/receiving)
(Close)
send()/recv()
sendto()/recvfrom()
shutdown()
closesocket
Complete
App - 23
App - 23
APPENDIX
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
MELSEC-Q
Sample program
This program is a sample program to conduct a
connection test between the Ethernet module
and target device.
This program accesses the data register (D) of
the PLC CPU installed together with the Ethernet
module.
Copyright(C) 1996 Mitsubishi Electric
Corporation
All Rights Reserved
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
#include <stdio.h>
#include <winsock.h>
#define FLAG_OFF
#define FLAG_ON
#define SOCK_OK
#define SOCK_NG
#define BUF_SIZE
#define ERROR_INITIAL
#define ERROR_SOCKET
#define ERROR_BIND
#define ERROR_CONNECT
#define ERROR_SEND
#define ERROR_RECEIVE
#define ERROR_SHUTDOWN
#define ERROR_CLOSE
0
1
0
-1
4096
0
1
2
3
4
5
6
7
App - 24
App - 24
APPENDIX
int nErrorStatus;
int Dmykeyin;
int Closeflag;
int socketno;
int main()
{
WORD wVersionRequested=MAKEWORD(1,1);
WSADATA wsaData;
int length;
unsigned char s_buf[BUF_SIZE];
unsigned char r_buf[BUF_SIZE];
int rbuf_idx;
int recv_size;
struct sck_inf sc;
struct sockaddr_in hostdata;
struct sockaddr_in aj71e71;
void Sockerror(int);
MELSEC-Q
sc.my_addr.s_addr=htonl(INADDR_ANY);
sc.my_port=htons(0);
sc.aj_addr.s_addr=inet_addr("192.0.1.253");
sc.aj_port=htons(0x2000);
Closeflag=FLAG_OFF;
// Error handling
// Error handling
hostdata.sin_family=AF_INET;
hostdata.sin_port=sc.my_port;
hostdata.sin_addr.s_addr=sc.my_addr.s_addr;
App - 25
App - 25
APPENDIX
MELSEC-Q
if(bind(socketno,(LPSOCKADDR)&hostdata,sizeof(hostdata))!=SOCK_OK){
// Bind
Sockerror(ERROR_BIND);
// Error handling
return(SOCK_NG);
}
aj71e71.sin_family=AF_INET;
aj71e71.sin_port=sc.aj_port;
aj71e71.sin_addr.s_addr=sc.aj_addr.s_addr;
if(connect(socketno,(LPSOCKADDR)&aj71e71,sizeof(aj71e71))!=SOCK_OK){
// Connection (Active open)
Sockerror(ERROR_CONNECT);
// Error handling
return(SOCK_NG);
}
//
Closeflag=FLAG_ON;
strcpy(s_buf, "03FF000A4420000000000500112233445566778899AA");
// D0 to D4 batch write request (1E frame)
strcpy(s_buf, "500000FF03FF00002C000A14010000D*0000000005112233445566778899AA");
// D0 to D4 batch write request (3E frame)
length=strlen(s_buf);
if(send(socketno,s_buf,length,0)==SOCKET_ERROR){
Sockerror(ERROR_SEND);
return (SOCK_NG);
}
printf("\n send data\n%s\n",s_buf);
// Data sending
// Error handling
App - 26
App - 26
APPENDIX
MELSEC-Q
if(length == SOCKET_ERROR) {
nErrorStatus = WSAGetLastError();
if(nErrorStatus != WSAEWOULDBLOCK) {
Sockerror(ERROR_RECIEVE);
return (SOCK_NG);
} else {
continue;
}
} else {
rbuf_idx += length;
recv_size += length;
if(recv_size >= RECV_ANS_1)
break;
}
}
r_buf[rbuf_idx] = '\0' ;
// Error handling
strcpy(s_buf, "01FF000A4420000000000500");
// Data sending
// Error handling
App - 27
App - 27
APPENDIX
MELSEC-Q
if(length == SOCKET_ERROR) {
nErrorStatus = WSAGetLastError();
if(nErrorStatus != WSAEWOULDBLOCK) {
Sockerror(ERROR_RECIEVE);
return (SOCK_NG);
} else {
continue;
}
} else {
rbuf_idx += length;
recv_size += length;
if(recv_size >= RECV_ANS_2)
break;
}
}
r_buf[rbuf_idx] = '\0' ;
// Error handling
// Processing to disable
// sending/receiving
// Error handling
}
if(closesocket(socketno)!=SOCK_OK){
Sockerror(ERROR_CLOSE);
return(SOCK_NG);
}
// Close processing
// Error handling
Closeflag=FLAG_OFF;
WSACleanup();
return(SOCK_OK);
}
void Sockerror(int error_kind)
{
if(error_kind==ERROR_INITIAL){
printf("Initial processing is abnormal.");
}
App - 28
App - 28
APPENDIX
MELSEC-Q
else{
nErrorStatus=WSAGetLastError();
switch(error_kind){
case ERROR_SOCKET:
printf("Failed to create socket.");
break;
case ERROR_BIND:
printf("Failed to bind.");
break;
case ERROR_CONNECT:
printf("Failed to establish connection.");
break;
case ERROR_SEND:
printf("Sending failed.");
break;
case ERROR_RECIEVE:
printf("Receiving failed.");
break;
case ERROR_SHUTDOWN:
printf("Failed to shutdown.");
break;
case ERROR_CLOSE:
printf("Failed to close normally.");
break;
}
}
printf("Error code is %d.\n", nErrorStatus);
if(Closeflag==FLAG_ON){
nErrorStatus=shutdown(socketno,2);
nErrorStatus=closesocket(socketno);
Closeflag=FLAG_OFF;
}
// Shutdown processing
// Close processing
// Connection completion flag off
App - 29
App - 29
APPENDIX
MELSEC-Q
(b)
(c)
App - 30
App - 30
APPENDIX
MELSEC-Q
(3) GX Developer settings
Set the parameters of the PLC CPU as described below.
: 2000H
App - 31
App - 31
APPENDIX
MELSEC-Q
(4) External device side program
The following shows a program example of the external device that accesses the
Ethernet module-mounted station Q25PRHCPU.
When this program is executed, the following contents are displayed in due
order.
1) Version of used Winsock
2) Test starting message
3) Write of batch command messages in word unit
4) Write of batch response messages in word unit
5) Test end message
REMARK
The following describes the general compile procedure for the program created
App - 32
App - 32
APPENDIX
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
MELSEC-Q
/
/
/
/
/
/
/
/
/
/
/
/
/
/
Sample program
This program is a sample program for testing the
connection of the Ethernet module and external
device.
This program accesses the data registers (D) of
the redundant CPU (control system) mounted
with the Ethernet module.
Copyright(C) 2004 Mitsubishi Electric Corporation
All Rights Reserved
/
#include <stdio.h>
#include <winsock.h>
#define FLAG_OFF
#define FLAG_ON
#define SOCK_OK
#define SOCK_NG
#define BUF_SIZE
#define ERROR_NO_ERROR
#define ERROR_INITIAL
#define ERROR_SOCKET
#define ERROR_BIND
#define ERROR_CONNECT
#define ERROR_SEND
#define ERROR_SHUTDOWN
#define ERROR_CLOSE
0
1
0
-1
4096
0
1
2
3
4
5
6
7
App - 33
App - 33
APPENDIX
int CloseflagA;
int CloseflagB;
int socketnoA;
int socketnoB;
int ConnectLastErrorA;
int ConnectLastErrorB;
int SendFlag;
MELSEC-Q
// Connection end flag (for System A connection)
// Connection end flag (for System B connection)
int main()
{
WORD wVersionRequested = MAKEWORD(1, 1);
WSADATA wsaData;
int length;
unsigned char s_buf[BUF_SIZE];
unsigned char r_bufA[BUF_SIZE],r_bufB[BUF_SIZE];
struct sck_inf scA,scB;
struct sockaddr_in hostdataA,hostdataB;
struct sockaddr_in qj71e71A,qj71e71B;
BOOL DataRecv(int, unsigned char *, int);
void Sockerror(int, int);
unsigned long ulCmdArgA,ulCmdArgB;
ConnectLastErrorA = ERROR_NO_ERROR;
// Connect processing error information initialization (for System A)
ConnectLastErrorB = ERROR_NO_ERROR;
// Connect processing error information initialization (for System B)
if(nErrorStatus != SOCK_OK) {
Sockerror(ERROR_INITIAL, ERROR_INITIAL);
return (SOCK_NG);
}
// Error handling
App - 34
App - 34
APPENDIX
MELSEC-Q
App - 35
App - 35
APPENDIX
MELSEC-Q
SendFlag = FLAG_OFF;
// Send completion flag OFF
// System A send processing
if( CloseflagA == FLAG_ON && (SendFlag == FLAG_OFF) ){
if(send(socketnoA, s_buf, length, 0) != SOCKET_ERROR) {
// Data send (System A)
printf("\n Send data (System A) \n%s\n", s_buf);
// Send data display (System A)
SendFlag = FLAG_ON;
// Send completion flag ON
// Receive processing
if(DataRecv(socketnoA, r_bufA, RECV_ANS_1) == TRUE) {
// Data receive
printf("\n Receive data (System A) \n%s\n", r_bufA);
// Receive data display
} else {
printf("Receive failure (System A) \n");
}
} else {
printf("Send failure (System A) \n");
}
}
App - 36
App - 36
APPENDIX
MELSEC-Q
// Error handling
if(CloseflagA == FLAG_ON) {
ShutdownflagA = FLAG_OFF;
// Shutdown flag OFF
if(shutdown(socketnoA, 2) != SOCK_OK) {
// Send/receive inhibit processing (System A)
Sockerror(ERROR_SHUTDOWN, ERROR_NO_ERROR);
// Error handling
return (SOCK_NG);
}
}
if(CloseflagB == FLAG_ON) {
ShutdownflagB = FLAG_OFF;
// Shutdown flag OFF
if(shutdown(socketnoB, 2) != SOCK_OK) {
// Send/receive inhibit processing (System B)
Sockerror(ERROR_NO_ERROR, ERROR_SHUTDOWN);
// Error handling
return (SOCK_NG);
}
}
CloseflagA = FLAG_OFF;
if(closesocket(socketnoA) != SOCK_OK) {
Sockerror(ERROR_CLOSE, ERROR_NO_ERROR);
return (SOCK_NG);
}
App - 37
App - 37
APPENDIX
MELSEC-Q
CloseflagB = FLAG_OFF;
if(closesocket(socketnoB) != SOCK_OK) {
Sockerror(ERROR_NO_ERROR, ERROR_CLOSE);
return (SOCK_NG);
}
WSACleanup();
// Winsock.DLL release
return (SOCK_OK);
}
App - 38
App - 38
APPENDIX
return (TRUE);
MELSEC-Q
// Normal termination
App - 39
App - 39
APPENDIX
MELSEC-Q
}
}
printf("Error code is %d. \n", nErrorStatus);
if (ShutdownflagA == FLAG_ON){
nErrorStatus = shutdown(socketnoA, 2);
ShutdownflagA = FLAG_OFF;
}
if (ShutdownflagB == FLAG_ON){
nErrorStatus = shutdown(socketnoB, 2);
ShutdownflagB = FLAG_OFF;
}
if (CloseflagA == FLAG_ON){
nErrorStatus = closesocket(socketnoA);
CloseflagA = FLAG_OFF;
}
if (CloseflagB == FLAG_ON){
nErrorStatus = closesocket(socketnoB);
CloseflagB = FLAG_OFF;
}
printf("Program is closed. Press any key. \n");
Dmykeyin = getchar();
WSACleanup();
return;
App - 40
App - 40
APPENDIX
MELSEC-Q
The settings of the PLC CPU side are the same as those of the execution
environment described in Section 8.1 (1) (a) and (3) of Appendix.
2)
The settings of the external device side are the same as those of the
execution environment described in Section 8.1 (1) (b) of Appendix,
except for the following including the software development:
App - 41
(a)
(b)
Create the (example) window shown in (4) below using "Command Button"
in the toolbox.
(c)
(d)
APPENDIX
MELSEC-Q
(4) Window example (Form 1)
(Object name)
Winsock
Set the properties.
App - 42
App - 42
APPENDIX
MELSEC-Q
App - 43
App - 43
APPENDIX
MELSEC-Q
MELSECNET/H communication
Ethernet communication
GOT
Modem communication
App - 44
App - 44
APPENDIX
MELSEC-Q
(3) Support for wide choice of basic operating systems
MX Component can run on IBM PC/AT compatible personal computers running
the following basic operating systems:
Visual Basic
Visual C++
VBScript
Development software
VBA
(5) Support for functions dedicated for data communication with PLCs
MX Component provides the functions necessary for data communication with
PLCs, including functions for opening/closing communication lines and
reading/writing devices.
Multi-function communication programs can thus easily be developed with MX
Component.
Function name
App - 45
Function
Connect
Open
Close
Disconnect
GetErrorMessage
ReadDeviceBlock
WriteDeviceBlock
ReadDeviceBlock2
WriteDeviceBlock2
ReadDeviceRandom
WriteDeviceRandom
ReadDeviceRandom2
WriteDeviceRandom2
SetDevice
GetDevice
SetDevice2
GetDevice2
App - 45
APPENDIX
MELSEC-Q
Function name
Function
ReadBuffer
WriteBuffer
GetClockData
SetClockData
GetCpuType
SetCpuStatus
EntryDeviceStatus
FreeDeviceStatus
OnDeviceStatus
Announces event.
App - 46
App - 46
APPENDIX
MELSEC-Q
2)
Paste the ACT control icon onto the form and assign
the logical station number set in step 1 to the
property of the pasted control.
3)
Completed
App - 47
App - 47
APPENDIX
MELSEC-Q
(2) Sample program
The following sample program reads D0 to D4 (five points) of the target PLC
using the logical station number.
Command1
' Connect to the communication line.
Command2
' Read the device data.
Command3
' Cut the communication line.
ACT control (ActEasy IF)
' ACT control for utility setting type
2)
Program example
App - 48
APPENDIX
MELSEC-Q
//
//
Connection
//
void CVCDlg::OnOpen()
{
long lRet;
CString szMessage;
UpdateData();
// Get LogicalStationNumber
m_actEasyIF. SetActLogicalStationNumber ( m_lLogicalStationNumber ):
// Connection
lRet = m_actEasyIF. Open();
if ( lRet == 0) {
MessageBox ( "The connection was successful" )
} else {
szMessage. Format ( "Connection Error: %x", lRet );
MessageBox ( szMessage )
}
}
App - 49
App - 49
APPENDIX
MELSEC-Q
//
//
Read
//
void CVCDlg::OnRead()
{
long lRet;
short sData[5];
CString szMessage;
// D0-D4 are read
lRet = m_actEasyIf. ReadDeviceBlock2 ( "D0", 5, sData );
if ( lRet == 0) {
szMessage. Format ( "D0-D5 = %d, %d, %d, %d, %d",
sData[0], sData[1], sData[2], sData[3], sData[4] );
MessageBox ( szMessage );
} else {
szMessage. Format ( "Read Error: %x", lRet );
MessageBox ( szMessage )
}
}
//
//
Disconnection
//
void CVCDlg::OnOpen()
{
long lRet;
CString szMessage;
// Disconnection
lRet = m_actEasyIF. Close();
if ( lRet == 0) {
MessageBox ( "The disconnection was successful" )
} else {
szMessage. Format ( "Disconnection Error: %x", lRet );
MessageBox ( szMessage )
}
}
App - 50
App - 50
APPENDIX
MELSEC-Q
Ethernet module
(1) Ethernet
Destination address
Source address
Type
FCS
Source address
Length
FCS
(2) IEEE802.3
Destination address
ICMP name/description
Echo Reply
Result of IP packet loopback
Destination Unreachable
Failed to deliver IP packet to the destination.
Echo Request
Requests loopback of IP packet
Others
1 The Ethernet module can simultaneously receive two ICMP ECHO requests (type 8, Ping message), which are used for
existence confirmation, etc., and handles them accordingly.
When three or more ICMP ECHO requests are received at the same time, the third and succeeding requests will be
ignored.
If a response is not returned to the external device when an ICMP ECHO request is sent to the Ethernet module, send an
ICMP ECHO request to the Ethernet module again.
The Ethernet module is able to receive a maximum of 1460-byte ICMP message at one time.
Do not send an ICMP message request exceeding 1460 bytes to the Ethernet module.
App - 51
App - 51
APPENDIX
MELSEC-Q
Ethernet operations
Recording sheet 2
Recording sheet 3
Recording sheet 4
Recording sheet 5
Recording sheet 6
Recording sheet 7
Recording sheet 8
App - 52
Recording sheet 9
Recording sheet 10
Recording sheet 11
Recording sheet 12
Recording sheet 13
App - 52
APPENDIX
MELSEC-Q
Recording sheet 1
[Module number
GX Developer setting
screen
Setting data
Data item
Setting value
Remark
Group No.
Station No.
Online
Off line
Mode
Initial Timing
Ethernet Operations
IP address
setting
Input format
IP address
App - 53
IP address
Input format
Hexadecimal
.
Ethernet (V2.0)
IEEE802.3
TCP Existence
Confirmation setting
App - 53
APPENDIX
MELSEC-Q
Recording sheet 2
[Module number
GX Developer setting
screen
Setting data
Data item
Timer setting
Network parameter
Ethernet Initial settings
Setting value
TCP zero
window Timer
IP assembly timer
Response monitoring
timer
Destination existence
confirmation
starting interval
Destination existence
confirmation
Interval timer
Destination existence
confirmation resend
timer
Default: 3 (times)
Decimal
Input format
DNS setting
App - 54
Remark
Hexadecimal
DNS server 1
IP address
DNS server 2
IP address
DNS server 3
IP address
DNS server 4
IP address
App - 54
APPENDIX
MELSEC-Q
Recording Sheet 3
[Module number
GX Developer setting
screen
Setting data
Data item
Setting value
Remark
TCP
Protocol
UDP
Active
Unpassive
Open system
Fullpassive
Send
Fixed buffer
Receive
Procedure exist
Fixed buffer
communication
Connection
No.
No procedure
No pairs
Paring open
Pairs
No confirm
Existence confirmation
Confirm
Destination
IP address
Hexadecimal
.
Network parameter
Ethernet open settings
TCP
Protocol
UDP
Active
Unpassive
Open system
Fullpassive
Send
Fixed buffer
Receive
Procedure exist
Fixed buffer
communication
Connection
No.
No procedure
No pairs
Paring open
Pairs
No confirm
Existence confirmation
Confirm
Destination
IP address
.
Destination Port No.
App - 55
Hexadecimal
.
App - 55
APPENDIX
MELSEC-Q
Recording sheet 4
[Module number
GX Developer setting
screen
Setting data
Data item
Setting value
Use
.
Decimal
Input format
Sub-net address
No.1
Router IP address
Sub-net address
No.2
Router IP address
Sub-net address
No.3
Network parameters
Setting the Ethernet
router relay parameter
Router IP address
Sub-net address
No.4
Router IP address
Sub-net address
No.5
Router IP address
Sub-net address
No.6
Router IP address
Sub-net address
No7
Router IP address
Sub-net address
No.8
Router IP address
App - 56
Remark
Do not use
Hexadecimal
.
App - 56
APPENDIX
MELSEC-Q
Recording sheet 5
[Module number
GX Developer setting
screen
Setting data
Data item
Setting value
Remark
Decimal
Input format
Hexadecimal
Network No.
Input format: Decimal
No.
Station No.
IP address
Network parameters
Setting the Ethernet
Station No. <-> IP
information
Network No.
Input format: Decimal
No.
Station No.
IP address
Network No.
Input format: Decimal
No.
Station No.
IP address
Network No.
Input format: Decimal
No.
Station No.
IP address
App - 57
App - 57
APPENDIX
MELSEC-Q
Recording sheet 6
[Module number
GX Developer setting
screen
Setting data
Data item
Setting value
Remark
Do not use
Use
Default: "QJ71E71"
Current
Password
New
Command input monitoring timer
Unit: Setting value 500ms
PLC CPU monitoring timer
App - 58
App - 58
APPENDIX
MELSEC-Q
Recording sheet 7
[Module number
GX Developer setting
screen
Setting data
Data item
Setting value
Remark
Password
Mail address
General
settings
Interval of inquiry
min
h
Network parameters
Ethernet e-mail settings
SMTP
Server name
Decimal
Send setting
IP address
Mail
Server
name
Hexadecimal
.
POP
Server name
Decimal
Hexadecimal
IP address
.
No execute
Execute news
No execute
Execute news
No execute
Execute news
No execute
Execute news
No execute
Execute news
App - 59
No execute
Execute news
App - 59
APPENDIX
MELSEC-Q
Recording sheet 8
[Module number
GX Developer setting
screen
Data item
Setting data
Setting value
Remark
No settings
Normal STOP
Send method
ASCII
CSV
Attached file name
Interval of CPU inquiry
numeric value setting
PLC inquiry Interval
s
min
h
Decimal
Hexadecimal
Condition device
Condition for inspection
Ethernet news settings
No.
Monitoring value
Monitoring value
Monitoring value
App - 60
App - 60
APPENDIX
MELSEC-Q
Recording sheet 9
[Module number
GX Developer setting
screen
Data item
Input format
Device code
No.
Network parameters
Ethernet interrupt
settings
Decimal
Hexadecimal
RECV instruction
Fixed buffer
Detection method
Edge detection
Automatic setting
Interrupt condition
Scan completed
Automatic setting
Board No.
Device No.
Detection method
Edge detect
Automatic setting
Interrupt condition
Scan completed
Automatic setting
Board No.
Device code
RECV instruction
Fixed buffer
Device No.
No.
App - 61
Detection method
Edge detect
Interrupt condition
Scan completed
Automatic setting
Automatic setting
Board No.
Device code
No.
Remark
Word device setting value
input format
Device No.
Device code
No.
Setting data
Setting value
RECV instruction
Fixed buffer
Device No.
Detection method
Edge detect
Automatic setting
Interrupt condition
Scan completed
Automatic setting
Board No.
App - 61
APPENDIX
MELSEC-Q
Recording sheet 10
GX Developer setting
screen
Data item
PLC CPU
side
No.
Intelligent
module
side
PLC CPU
side
No.
Intelligent
module
side
Intelligent function
module interrupt pointer
setting
PLC CPU
side
No.
Intelligent
module
side
PLC CPU
side
No.
Intelligent
module
side
App - 62
Interrupt pointer
start No.
Interrupt pointer
No. of module
Start I/O No.
Setting data
Setting value
Remark
Start SI No.
Interrupt pointer
start No.
Interrupt pointer
No. of module
Start I/O No.
Start SI No.
Interrupt pointer
start No.
Interrupt pointer
No. of module
Start I/O No.
Start SI No.
Interrupt pointer
start No.
Interrupt pointer
No. of module
Start I/O No.
Start SI No.
App - 62
APPENDIX
MELSEC-Q
Recording sheet 11
GX Developer setting
screen
Data item
Setting data
Setting value
Remark
No.
No.
Network parameters
MNET/10H Ethernet
routing information
settings
No.
No.
App - 63
App - 63
APPENDIX
MELSEC-Q
Recording sheet 12
GX Developer setting
screen
Remote password
settings
Setting data
Data item
Setting value
Remark
Password settings
Password active
module settings
Model name
QJ71E71
Start X/Y
Connection 1
Connection 2
Connection 3
Connection 4
Connection 5
Connection 6
Connection 7
Connection 8
Connection 11
Connection 12
Connection 13
Connection 14
Connection 15
Connection 16
Auto open UDP port
FTP transmission port (TCP/IP)
System connection
App - 64
App - 64
APPENDIX
MELSEC-Q
Recording sheet 13
[Module number
GX Developer setting
screen
]
Setting data
Data item
Setting value
Remark
Station number
Station number and
mode setting
(System B)
Online
Offline
Mode
Self-loopback test
H/W test
IP address settings
Decimal
Input format
System B
Hexadecimal
.
Connection 1
Connection 2
Connection 3
Connection 4
Connection 5
Connection 6
Connection 7
Redundant settings
Connection 8
Connection 9
Connection 10
System switching settings when
communication error occurs
Connection 11
Connection 12
Connection 13
Connection 14
Connection 15
Connection 16
Enable auto open UDP port
Enable GX Developer UDP communication port
Enable GX Developer TCP communication port
Enable FTP communication port
Enable HTTP communication port
App - 65
App - 65
INDEX
Ind
[1 to 10]
10BASE2 ............................................2 - 7, 4 - 10
10BASE5 .............................................. 2 - 5, 4 - 9
10BASE-T............................................. 2 - 4, 4 - 8
100BASE-TX ........................................ 2 - 3, 4 - 8
[A]
A compatible 1E frame................................. 6 - 2
(end codes)............................................ 11 - 24
(abnormal codes)................................... 11 - 24
Abnormal code .......................................... 11 - 24
Accessible range
Fixed buffer communication
(procedure exist)........................................ 7 - 1
Fixed buffer communication
(no procedure) ........................................... 8 - 1
Communication using the random
access buffer ............................................. 9 - 1
Active open........................... 5 - 37, 5 - 42, 5 - 45
AJ71E71 ........................................... Appendix - 4
AJ71E71-S3 ..................................... Appendix - 4
Applicable systems ....................................... 2 - 1
Application data
Fixed buffer communication
(procedure exist)...................................... 7 - 13
Fixed buffer communication
(no procedure) ......................................... 8 - 10
Communication using the random
access buffer ............................................. 9 - 6
ARP...................................................1 - 15, 5 - 42
AUI cable (transceiver cable)........................ 2 - 5
Automatic open UDP port ........................... 5 - 66
[B]
Buffer memory list ....................................... 3 - 13
Buffer memory............................................. 3 - 12
BUFRCV instruction ................. 7 - 5, 8 - 6, 10 - 2
BUFRCVS instruction............... 7 - 7, 8 - 8, 10 - 5
BUFSND instruction ................. 7 - 3, 8 - 4, 10 - 8
[C]
CLOSE instruction..........................5 - 44, 10 - 11
Close processing......................................... 5 - 44
Communication by e-mails............................ 1 - 4
Index - 1
[D]
Data communication using the MELSEC
communication protocol.................................1 - 2
Data format
Fixed buffer communication
(procedure exist) ......................................7 - 12
Fixed buffer communication
(no procedure)..........................................8 - 10
Communication using the random
access buffer ..............................................9 - 5
Data length
Fixed buffer communication
(procedure exist) ......................................7 - 15
Communication using the random
access buffer ..............................................9 - 8
Dedicated instruction list................................3 - 8
Default router IP address.............................5 - 18
Destination IP address..................... 5 - 40, 5 - 42
Destination Port No......................................5 - 41
DNS setting ....................................................5 - 7
DNS ..............................................................1 - 15
[E]
Enable write at RUN time ............................4 - 21
End code
Fixed buffer communication
(procedure exist) ......................................7 - 16
Index - 1
[F]
Fixed buffer (setting) ................................... 5 - 38
Fixed buffer communication
(no procedure) .......................................Chapter 8
Fixed buffer communication
(procedure exist) ...................................Chapter 7
Fixed buffer communication (setting) ......... 5 - 38
FTP parameters .......................................... 4 - 14
FTP .............................................................. 1 - 15
Full passive open .............................5 - 37, 5 - 52
Functional comparisons between the
QnA/A series modules ..................... Appendix - 4
[G]
Generic terms and abbreviations................A - 21
GX Developer..............................................A - 21
Setting item list .......................................... 3 - 9
Setting value recording sheets...Appendix - 52
Group No. .................................................... 4 - 17
[H]
Head address .....................................9 - 8, 9 - 15
Header
Fixed buffer communication
(procedure exist)...................................... 7 - 12
Fixed buffer communication
(no procedure) ......................................... 8 - 10
Communication using the random
access buffer ............................................. 9 - 5
[I]
ICMP................................... 1 - 15, Appendix - 51
Improper access.......................................... 5 - 68
Initial processing............................................ 5 - 3
Initial settings................................................. 5 - 4
Index - 2
[L]
LED display ........................................ 4 - 6, 11 - 9
List of input/output signals ...........................3 - 10
Local station Port No. (setting) ....................5 - 39
Local station (Ethernet module)
IP address ....................................................4 - 20
Logical address............................................9 - 15
[M]
MAC address .............................................. A - 21
MELSECNET/H, MELSECNET/10
relay communication......................................3 - 6
Mode.............................................................4 - 18
Monitoring function.........................................1 - 6
Multiple CPU system .................. 1 - 8, 2 - 8, 6 - 4
MX Component .....................6 - 5, Appendix - 44
[N]
Network No. .................................................4 - 17
Network parameter
Number of MNET/10H Ethernet cards ....4 - 16
Network type ................................................4 - 17
[O]
OPEN instruction ............................. 5 - 43, 10-19
Open processing
Active open processing............................5 - 45
Passive open processing.........................5 - 52
Pairing open processing ..........................5 - 63
Open settings ...............................................5 - 36
Pairing open settings ...............................5 - 64
Sending by simultaneous
broadcasting.............................................8 - 11
Index - 2
Ind
Receiving by simultaneous
broadcasting ............................................ 8 - 13
Open system ............................................... 5 - 37
Operational settings .................................... 4 - 19
[P]
Pairing open ................................................ 5 - 63
Parameter setting
Setting item list .......................................... 3 - 9
Setting screen list .................................... 4 - 13
Setting value recording sheets...Appendix - 52
Passive open ........................ 5 - 37, 5 - 42, 5 - 52
Physical address ......................................... 9 - 15
POP3 ........................................................... 1 - 15
Port No..............................................5 - 40, 5 - 41
Program example
Open/close processing (Active) .............. 5 - 49
Open/close processing (Passive) ........... 5 - 57
Fixed buffer communication
(procedure exist)...................................... 7 - 18
Fixed buffer communication
(no procedure) ......................................... 8 - 18
Protocol........................................................ 5 - 37
[Q]
QE71................................................. Appendix - 4
QnA compatible 3E frames........................... 6 - 2
[R]
Re-initial processing...................................... 5 - 9
Redundant System...........................1 - 11, 5 - 89
Related manuals .........................................A - 13
Remote password check............................. 5 - 68
Remote password mismatch notification
accumulated count ...................................... 5 - 85
Response format
Fixed buffer communication
(procedure exist)...................................... 7 - 13
Communication using the random
access buffer ............................................. 9 - 6
Router IP address ....................................... 5 - 20
Router relay function ................................... 5 - 17
Router relay parameter ............................... 5 - 16
[T]
TCP .................................................. 1 - 14, 5 - 37
Test
Self refrain test .........................................4 - 22
Hardware test (H/W test) .........................4 - 23
Loop back test ..........................................5 - 29
PING command test.................................5 - 34
Text (command)
Fixed buffer communication
(procedure exist) ......................................7 - 15
Communication using the random
access buffer ..............................................9 - 9
Timer setting ..................................................5 - 4
[U]
UDP ................................................. 1 - 15, 5 36
UINI instruction............................... 5 - 13, 10 - 23
Unpassive ........................................ 5 - 37, 5 - 52
Usage setting ................................... 3 - 14, 5 - 36
[V]
Valid module during other station access ...4 - 17
[S]
Setting the number of cards.............4 - 13, 4 - 16
Settings and procedures prior to
starting the operation .................................... 4 - 3
Index - 3
Index - 3
WARRANTY
Please confirm the following product warranty details before using this product.
3. Overseas service
Overseas, repairs shall be accepted by Mitsubishi's local overseas FA Center. Note that the repair conditions at each FA
Center may differ.
6. Product application
(1) In using the Mitsubishi MELSEC programmable logic controller, the usage conditions shall be that the application will
not lead to a major accident even if any problem or fault should occur in the programmable logic controller device, and
that backup and fail-safe functions are systematically provided outside of the device for any problem or fault.
(2) The Mitsubishi programmable logic controller has been designed and manufactured for applications in general
industries, etc. Thus, applications in which the public could be affected such as in nuclear power plants and other
power plants operated by respective power companies, and applications in which a special quality assurance system
is required, such as for Railway companies or Public service purposes shall be excluded from the programmable logic
controller applications.
In addition, applications in which human life or property that could be greatly affected, such as in aircraft, medical
applications, incineration and fuel devices, manned transportation, equipment for recreation and amusement, and
safety devices, shall also be excluded from the programmable logic controller range of applications.
However, in certain cases, some applications may be possible, providing the user consults their local Mitsubishi
representative outlining the special requirements of the project, and providing that all parties concerned agree to the
special circumstances, solely at the users discretion.
Microsoft, Windows, Windows NT are registered trademarks of Microsoft Corporation in the United States
and other countries.
Netscape is a registered trademark of Netscape Communication Corporation in the United States and other
countries.
Adobe and Acrobat are registered trademarks of Adobe Systems Incorporation.
Pentium and Celeron are trademarks of Intel Corporation in the United States and other countries.
Ethernet is a trademark of Xerox Co., Ltd. in the United States.
Other company names and product names used in this document are trademarks or registered trademarks of
respective owners.
Q Corresponding Ethernet
Interface Module
Q Corresponding Ethernet
Interface Module
User's Manual
(Basic)
Q Corresponding Ethernet Interface Module User's Manual (Basic)
MODEL
QJ71E71-U-KI-E
MODEL
CODE
13JL88
SH(NA)-080009-I(0406)MEE
When exported from Japan, this manual does not require application to the
Ministry of Economy, Trade and Industry for service transaction permission.
Mitsubishi Programmable
Logic Controller
QJ71E71-100
QJ71E71-B5
QJ71E71-B2
BL