QJ71C24N PDF
QJ71C24N PDF
QJ71C24N PDF
MELSEC System Q
User's Manual
(Basic)
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".
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 Instructions]
! DANGER
• See manuals of each data link for the operating status of each station when there is a
communication error in the data link.
There is the risk of an accident occurring due to output error or malfunctioning.
• When using the notification function, the pager receiver may not be contacted due to the frequency
transmission status from the system setup environment and error on the receiver side.
To ensure the safety of the PLC system, install a call circuit with a lamp display or buzzer sound.
• When performing the control of the PLC in operation (changing data) by connecting a peripheral
devices to the CPU module or personal computer, etc. to the intelligent device module, configure an
interlock circuit in a sequence program so the safety of the overall system is always maintained.
Also when performing other controls of the PLC in operation (changing program and operation
status (status control)), read this manual carefully and confirm if the overall safety is maintained.
Especially, when this control is performed to a remote PLC from an external device, troubles
that have occurred on the PLC side may not be able to immediately be handled if there is a data
communication error.
Define a troubleshooting agreement between external devices and the PLC CPU for data
communication error occurrences, as well as construct an interlock circuit in the sequence program.
• Do not write data into the "system area" of the buffer memory of intelligent function modules.
Also, do not use any "prohibited to use" signals as an output signal to an intelligent function
module from the PLC CPU.
Writing data into the "system area" or outputting a signal for "prohibited to use" may cause a
PLC system malfunction.
A-1 A-1
[Design Instructions]
! CAUTION
• Do not bunch the control wires or communication cables with the main circuit or power wires, or
install them close to each other.
They should be installed 100mm(3.9inch) or more from each other.
Not doing so could result in noise that may cause malfunction.
• When using the module while values, such as buffer memory set values, are registered in the
Flash ROM, do not turn off the power supply for the module loading station nor reset the PLC
CPU.
If the power supply for the module loading station is turned off or the PLC CPU is reset while any
values are registered, the data contents in the Flash ROM become inconsistent and as a result the
values must be set again in the buffer memory, etc. and reregistered to the Flash ROM.
Also, this may cause failure and malfunction of the module.
[Installation Instructions]
! CAUTION
• Use the PLC in an environment that meets the general specifications contained in the user's
manual of the CPU module to use.
Using this PLC in an environment outside the range of the general specifications may cause
electric shock, fire, malfunction, and damage to or deterioration of the product.
• 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.
• Tighten the screws within the range of specified torque.
If the screws are loose, it may cause the module to fallout, short circuits, or malfunction.
If the screws are tightened too much, it may cause damage to the screw and/or the module,
resulting in fallout, short circuits or malfunction.
• Switch all phases of the external power supply off when mounting or removing the module.
Not doing so may cause damage to the module.
• Do not directly touch the conductive area or electronic components of the module.
Doing so may cause malfunction or failure in the module.
A-2 A-2
[Wiring Instructions]
! CAUTION
• When turning on the power and operating the module after installation and wiring are completed,
always attach the terminal cover that comes with the product.
There is a risk of electric shock if the terminal cover is not attached.
• Perform correct pressure-displacement, crimp-contact or soldering for external wire connections
using the tools specified by the manufactures.
Incorrect connection may cause short circuits, fire, or malfunction.
• Attach connectors to the module securely.
• Be sure to fix communication cables or power supply cables leading from the module by placing
them in the duct or clamping them.
Cables not placed in the duct or without clamping may hang or shift, allowing them to be
accidentally pulled, which may cause a module malfunction and cable damage.
• Before connecting the cables, check the type o f interface to be connected.
Connecting or erroneous wiring to the wrong interface may cause failure to the module and
external devices.
• Tighten the terminal screws within the range of specified torque.
If the terminal screws are loose, it may result in short circuits or malfunction.
If the screws are tightened too much, it may cause damage to the screw and/or the module,
resulting in fallout, short circuits or malfunction.
• When removing the communication cable or power supply cable from the module, do not pull the
cable. When removing the cable with a connector, hold the connector on the side that is
connected to the module.
When removing the cable connected to the terminal block, first loosen the screws on the part
that is connected to the terminal block.
Pulling the cable that is still connected to the module may cause malfunction or damage to the
module or cable.
• Be careful not to let foreign matters such as sawdust or wire chips get inside the module.
They may cause fires, failure or malfunction.
• The top surface of the module is covered with protective film to prevent foreign objects such as
cable offcuts from entering the module when wiring.
Do not remove this film until the wiring is complete.
Before operating the system, be sure to remove the film to provide adequate heat ventilation.
A-3 A-3
[Startup/Maintenance Instructions]
! CAUTION
• Do not disassemble or modify each module.
Doing so could cause failure, malfunction injury or fire.
• Switch all phases of the external power supply off when mounting or removing the module.
Not doing so may cause failure or malfunction of the module.
• Do not mount/remove the module onto/from base unit more than 50 times (IEC61131-2-
compliant), 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 connector while the power is on.
Doing so may cause malfunction.
• Switch all phases of the external power supply off when cleaning or retightening terminal screws
and module installing screws.
Not doing so may cause failure or malfunction of the module.
If the screws are loose, it may cause the module to fallout, short circuits, or malfunction.
If the screws are tightened too much, it may cause damages to the screws and/or the module,
resulting in the module falling out, short circuits or malfunction.
• 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.
[Operation Instructions]
! CAUTION
• When performing the control of the PLC in operation (especially changing data, program, and
operation status (status control)) by connecting a personal computer, etc. to the intelligent
function module, read this manual carefully and confirm if the overall safety is maintained.
Failure to perform correct operation s to change data, program, or the status may result in
system malfunction, machine damage, or an accident.
[Disposal Instructions]
! CAUTION
• When disposing of this product, treat it as industrial waste.
A-4 A-4
REVISIONS
The manual number is given on the bottom left of the back cover.
Print Date Manual Number Revision
Dec., 1999 SH (NA)-080006-A First Printing
Oct., 2000 SH (NA)-080006-B Add the contents of the function version B.
Correction
Contents, Entire manual (change MELSECNET/10H to MELSECNET/H),
About Manuals, About The Generic Terms and Abbreviations, Product
Configuration, Section 1.2, 1.2(8), 1.3 POINT, Section 2.2, 2.3, 2.5, 2.6,
Section 3.1, 3.6, 3.9, Section 4.2, 4.4.1(2)(a)(Figure), 4.6(1), Chapter
5(all), Section 6.1.1, 6.1.3, 6.1.4, Section 7.1.1, 7.1.2, 7.2.2, Section 8.1,
8.2.1, 8.2.2, 8.3.1, 8.3.2, Section 9.2 to 9.7, Section 10.1.1, 10.2.1,
10.3.8, 10.3.18, Appendix 1.1(2), Appendix 2(all), appendix 3(2),
Appendix 7, appendix 8
Addition
Entire manual (add the explanation on MELSECNET/H remote I/O
station), The Manual's Use and Structure, Section 2.1, Section
3.1(Table), Section 4.4.2(1)(d), 4.9.2, Section 8.3.2 POINT, Section
10.2.1 (7164H, 7E70H), Appendix 3(1)
®
Jun., 2001 SH (NA)-080006-C Put Windows base software product together from Mitsubishi
Programmable Logic Controller MELSEC Series to Mitsubishi integrated
FA Software MELSOFT Series.
Standardize the name from software package (GPP function) to Product
name (GX Developer).
Standardize the name from utility package (QSCU) to Product name (GX
Congifurator-SC).
Correction
Conformation to the EMC Directive and Low Voltage Instruction, About
the Generic Terms and Abbreviations, Product Configuration, Program
Examples (Section 6.1.4, 6.2.3, Section 7.2.3, Section 9.3, 9.5, Appendix-
8), Section 1.2(1)(d), 1.2(4)(b)(Diagram), 1.2(8)(b), 1.3, Section 2.1, 2.3,
2.4, 2.5, 2.7, Section 3.1(Table), 3.2.1(3), 3.3.3(2), 3.4(Table), 3.9,
Section 4.3, 4.5.2, Section 5.1.5(3), 5.2, Section 6.1.4, Section 8.2, 8.3.2
POINT, 8.4.2, 8.4.9(Table), 8.6.3(Table), 8.6.7(Table), Section 10.1.2(b),
10.3(Table), Appendix 1.1, 2.1, 6, 7, 9
Addition
Section 2.6, Section 8.4.4, 8.6.2(Table), Section 10.2.1(716FH, 7FEFH),
10.2.3(7FE9H), 10.3.14, Appendix 3
Feb., 2002 SH (NA)-080006-D Addition
About The Generic Terms and Abbreviations, Section 1.2, Section 2.1,
2.7, Section 4.5.2, Section 8.2.1, 8.2.2, Section 10.2.1, Appendix 1.1, 6
Oct., 2002 SH (NA)-080006-E Addition
The Manual’s Use and Structure, About The Generic Terms and
Abbreviations, Section 1.2(1)(4), Section 2.1, 2.4, Section 5.2, Section
6.1.4, Section 9.8, Appendix 7
Jan., 2003 SH (NA)-080006-F Addition model
QJ71C24N, QJ71C24N-R2, QJ71C24N-R4
A-5 A-5
The manual number is given on the bottom left of the back cover.
Print Date Manual Number Revision
Jan., 2003 SH (NA)-080006-F Addition
SAFETY PRECAUTIONS, About Manuals, About The Generic Terms
and Abbreviations, Product Configuration, Section 1.3, Section 2.1, 2.2,
2.3, 2.5, 2.6, 2.7, Section 3.1, 3.2.1, 3.3.1, 3.6, 3.8, 3.9, Section 4.1, 4.3,
4.4, 4.5, 4.6, 4.7.1, Section 6.1.1, 6.1.2, Section 7.1, 7.2.2, Chapter 8(all),
Section 9.1, 9.6, Section 10.1.2(b), 10.1.3(1), 10.2, Appendix 1, Appendix
2.1, Appendix 3, Appendix 5, Appendix 9
Jun., 2004 SH (NA)-080006-G Correction
About The Generic Terms and Abbreviations, Product Configuration,
Chapter 2 (all), Section 3.8, Section 4.2.2 (1), Section 5.1.3 POINT,
Section 5.1.4, Chapter 8 (screen change), Section 8.6.10, Section 10.1.1,
Section 10.2
Addition
Appendix 9
Sep., 2004 SH (NA)-080006-H Correction
Section 1.3, Section 2.5, 2.6, Section 3.5, 3.6, 3.9, Section 4.1, Chapter 8
(screen change), Section 8.6.9, 8.6.10, Section 10.1, 10.2, Appendix 1.1
Addition
Appendix 9.12
This manual confers no industrial property rights or any rights of any other kind, nor does it confer any patent
licenses. Mitsubishi Electric Corporation cannot be held responsible for any problems involving industrial property
rights which may occur as a result of using the contents noted in this manual.
1999 MITSUBISHI ELECTRIC CORPORATION
A-6 A-6
INTRODUCTION
SAFETY PRECAUTIONS..............................................................................................................................A- 1
REVISIONS ....................................................................................................................................................A- 5
CONTENTS....................................................................................................................................................A- 7
About Manuals ...............................................................................................................................................A-15
Conformation to the EMC Directive and Low Voltage Instruction ................................................................A-15
The Manual’s Use and Structure ...................................................................................................................A-16
About The Generic Terms and Abbreviations...............................................................................................A-19
Definitions and Descriptions of Terminology.................................................................................................A-21
Product Configuration ....................................................................................................................................A-23
1 OVERVIEW 1- 1 to 1-11
3 SPECIFICATIONS 3- 1 to 3-31
A-7 A-7
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION 4- 1 to 33
A-8 A-8
7 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL 7- 1 to 7-28
A-9 A-9
8.6.5 Non procedure monitor/test ............................................................................................................. 8-41
8.6.6 Bidirectional monitor......................................................................................................................... 8-43
8.6.7 PLC CPU monitoring monitor .......................................................................................................... 8-44
8.6.8 Transmission user frame No. designation monitor ......................................................................... 8-46
8.6.9 Monitor/test others............................................................................................................................ 8-47
8.6.10 Display LED off and communication error information/error code initialization ........................... 8-49
8.7 Non Procedure Protocol Receive Data Clear ........................................................................................ 8-51
10.1 Checking the Status of the Serial Communication Module ............................................................... 10- 1
10.1.1 Checking the LED ON status, communications error status, and switch setting status of
the serial communication module ................................................................................................ 10- 1
10.1.2 Initializing error information of the serial communication module............................................... 10- 6
10.1.3 Reading the RS-232 control signal status................................................................................... 10- 9
10.1.4 Reading the data communication status (Transmission sequence status) ............................... 10-10
10.1.5 Reading the switch setting status ................................................................................................ 10-11
10.1.6 How to read the current operation status .................................................................................... 10-13
10.2 Error Code Tables............................................................................................................................... 10-15
10.2.1 Error code table............................................................................................................................ 10-15
10.2.2 A compatible 1C frame communications error code table.......................................................... 10-24
10.2.3 Error code list while modem function is used.............................................................................. 10-25
10.3 Troubleshooting by Symptom............................................................................................................. 10-27
10.3.1 Troubleshooting when "RUN" LED is turned OFF ...................................................................... 10-29
10.3.2 Troubleshooting when "RD" LED does not blink even though an external device is
transmitting a message................................................................................................................ 10-30
10.3.3 Troubleshooting when the Q series C24 does not return a response message even
though an external device transmitted a message and the "RD" LED blinked.......................... 10-31
10.3.4 Troubleshooting when an external device transmitted a message and "RD" LED blinked,
but the Read Request signal was not turned ON ....................................................................... 10-32
10.3.5 Troubleshooting when communication error "NAK" generates .................................................. 10-33
10.3.6 Troubleshooting when communication error "C/N" generates ................................................... 10-33
10.3.7 Troubleshooting when communication error "P/S" generates.................................................... 10-34
10.3.8 Troubleshooting when communication error "PRO." generates................................................. 10-35
10.3.9 Troubleshooting when communication error "SIO" generates ................................................... 10-36
10.3.10 Troubleshooting when communication error "CH1 ERR.", "CH2 ERR." generate .................. 10-37
10.3.11 Troubleshooting when communications is intermittently established and lost ........................ 10-38
10.3.12 Troubleshooting when data that cannot be decoded is transmitted and received .................. 10-39
A - 10 A - 10
10.3.13 Troubleshooting when it is unclear whether the communication error cause is in
the Q series C24 or an external device .................................................................................... 10-40
10.3.14 Troubleshooting when data cannot be communicated via modem.......................................... 10-41
10.3.15 Troubleshooting when data cannot be communicated with the ISDN sub-address................ 10-42
10.3.16 Troubleshooting when constant cycle transmission does not operate normally...................... 10-42
10.3.17 Troubleshooting when condition agreement transmission does not operate normally ........... 10-42
10.3.18 Troubleshooting when data cannot be received by an interrupt program ............................... 10-42
10.3.19 Troubleshooting when data cannot be written to Flash ROM .................................................. 10-42
10.3.20 Troubleshooting when the "ERR" LED is lit .............................................................................. 10-43
A - 11 A - 11
(Related Manual-1) … Q Corresponding Serial Communication Module User's Manual (Application)
SH-080007-G
A - 12 A - 12
(Related Manual-1) … Q Corresponding Serial Communication Module User's Manual (Application)
SH-080007-G
17 DEDICATED INSTRUCTIONS
17.1 Dedicated Instruction List
17.2 BUFRCVS Instruction
17.3 CSET Instruction (PLC CPU Monitoring
Register/Cancel)
17.4 CSET Instruction (Initial Settings)
17.5 GETE Instruction
17.6 PRR Instruction
17.7 PUTE Instruction
17.8 UINI Instruction
A - 13 A - 13
(Related Manual-2) … Q Corresponding MELSEC Communication Protocol Reference Manual
SH-080008-F
A - 14 A - 14
About Manuals
The following table lists the manuals relating to this product. Please order the desired manual(s) as needed.
Related manuals
Manual Number
Manual Name
(Model Code)
Q Corresponding Serial Communication Module User's Manual (Application)
This manual explains the specifications and operating procedures for the special module functions, the SH-080007
settings for use of special functions, and data-communication method for use with external devices. (13JL87)
(sold separately)
(sold separately)
(sold separately)
For details on making Mitsubishi PLC conform to the EMC directive and low voltage
instruction when installing it in your product, please see Chapter 3, "EMC Directive
and Low Voltage Instruction" of the User's Manual (Hardware) of the CPU module to
use.
The CE logo is printed on the rating plate on the main body of the PLC that conforms
to the EMC directive and low voltage instruction.
By making this product conform to the EMC directive and low voltage instruction, it is
not necessary to make those steps individually.
A - 15 A - 15
The Manual's Use and Structure
(e) To learn how to check for a connection error with the external devices
• Section 4.8 describes how to perform the individual module test and the
loopback test using MC protocol-based communication.
Details of the loopback test command are described in the reference
manual.
A - 16 A - 16
(3) To learn about data communication functions and detailed
explanations
(a) To learn about the communication functions
• Section 3.4 describes an overview of the serial communication module
functions.
(b) To learn how to send and receive data between the PLC CPU and the
external devices
• Data communication between the PLC CPU and the external devices is
performed with a communication function using the non procedure
protocol or the bidirectional protocol.
• Chapter 6 explains details of the communication functions and
programming using the non procedure protocol.
• Chapter 7 explains details of the communication functions and
programming using the bidirectional protocol.
(5) To learn how to check for error occurrences and take corrective
actions
Chapter 10 describes troubleshooting, how to check for errors, and detailed
explanations of error codes.
A - 17 A - 17
The structure of this manual
The module's buffer memory stores default values that are used as initial settings
to execute the data send/receive functions in order to communicate with the
external devices.
Data can be sent to or received from the external devices using these default
values. However, it may be necessary to change the default values, depending on
system specifications.
This manual explains how to perform the initial settings in order to use each
function of the utility package available for this module (GX-Configurator-SC).
When changing a default value for sending and receiving data to/from an opposite
device, first see the section describing the applicable function to verify the initial
setting item and setting value you wish to change, then change the default value
as explained in Chapter 8.
A - 18 A - 18
About The Generic Terms and Abbreviations
This manual uses the following generic terms and abbreviations to describe the serial communication
modules, unless otherwise specified.
A - 19 A - 19
(2) Other generic terms and abbreviations
This manual uses the following generic terms and abbreviations to explain the
data-communication devices for the serial communication module. The
names/model names are provided when it is necessary to explicitly identify the
model being discussed.
Generic term/abbreviation Description of generic term/abbreviation
Generic term for memory of the intelligent function modules/special function modules used for
Buffer memory
storing data sent to or received from the PLC CPU (setting values, monitor values, etc.)
Generic term for one of the external devices with which data can be sent/received using the MC
Computer
protocol or the bidirectional protocol.
Data communication functions Generic term for MC protocol, non procedure protocol, and bidirectional protocol.
Abbreviation for GX Configurator-SC (SW0D5C-QSCU-E or later).
• Initial settings for the module, monitoring and testing can be performed without using a sequence
program and without considering I/O signals or buffer memory. (Intelligent function utility)
GX Configurator-SC • Converting sequence programs necessary for data communication processing into FB can
shorten program production man-hours.
In addition, the monitoring and analysis of the transmitted/received data by the communication
network can shorten the system start-up time. (Protocol FB support function)
GX Developer Abbreviation for GX Developer (SWnD5C-GPPW-E). (n in the model should be 4 or greater)
I/F Abbreviation for interface
Generic term for buffer memory of the intelligent function modules used for storing data sent to or
Intelligent function module devices
received from the PLC CPU (setting values, monitor values, etc.)
Generic term for the Q series PLC modules that are operated by commands from the PLC CPU
(equivalent to the A series PLC special function modules).
Examples:
Intelligent function modules • CC-Link interface module
• A/D and D/A conversion modules
• Ethernet interface module
• Serial communication module
MELSECNET/10 Abbreviation for MELSECNET/10 network system.
MELSECNET/H Abbreviation for MELSECNET/H network system.
MX Component Abbreviation for MX Component (SW0D5C-ACT-E or later).
Operating Manual
GX Configurator-SC Version 2 Operating Manual (Protocol FB support function)
(Protocol FB support function)
Generic term for computers, indicators, measuring instruments, ID modules, bar code readers,
Opposite devices
regulators, other serial communication modules, UC24, etc. that are connected to this serial
(external devices)
communication module for data communication.
Reference Manual Q Corresponding MELSEC Communication Protocol Reference Manual
RS-232 (interface) Abbreviation for interface conforming to RS-232.
RS-422/485 (interface) Abbreviation for interface conforming to RS-422 and RS-485.
Generic term for the A/QnA series PLC modules that are operated by commands from the PLC
CPU (equivalent to the Q series PLC intelligent function modules).
Examples:
• CC-Link interface module
Special function modules
• A/D and D/A conversion modules
• High-speed counter module
• Ethernet interface module
• Computer link module and serial communication module
Switch setting Generic term for intelligent function module switch setting
User's Manual (Application) or
Q Corresponding Serial Communication Module User's Manual (Application)
Application
User's Manual (Basic) or Basic Q Corresponding Serial Communication Module User's Manual (Basic)
A - 20 A - 20
Definitions and Descriptions of Terminology
The following table lists the definitions and descriptions of terminology used in this manual and related
manuals for the Q series serial communication modules.
Terms Description
One of the message formats for the serial communication module for performing communication
using the MC protocol and ASCII code data.
A compatible IC frame This is the same message format as when communicating using the protocol for the A series
(Formats 1 to 4) computer link modules. Device memory read/write operations for the QCPU are allowed within
the device range of the AnACPU.
For details, see Chapter 5 of the Reference Manual.
A communication procedure for the serial communication modules and one of the data
Bidirectional protocol communication functions for communicating any data between the PLC CPU and an opposite
device. Details are explained in Chapter 7.
A mode of interface operation to communicate data with external devices using a function
Independent operation specified in each communication protocol setting. Two interfaces of serial communication
modules do not interact.
The operation mode of each of the two interfaces for a serial communication module that are
connected to external devices and linked to one another in order to send/receive data to/from the
external devices.
Linked operation
The two interfaces communicate data using the identical data-communication function (MC
protocol (identical format) or non procedure protocol) and the identical transmission
specifications. (Linked operation using the bidirectional protocol is not allowed.)
A communication procedure for the Q series serial communication modules or the Ethernet
interface modules, and a name of communication method for accessing to the PLC CPU from an
MELSEC communication protocol opposite device. (This is called the MC protocol in this manual.)
(MC protocol) There are two communication methods; one uses ASCII code data and the other uses binary
code data.
Details are explained in the Reference Manual.
This function registers character data (messages) to be sent to external devices (mainly printers)
Message send function in the serial communication module as an user frame in advance, and sends the registered data
(Printer function) for multiple user frames using the non procedure protocol (sent by an instruction from the PLC
CPU).
A name of the connection when multiple external devices or other serial communication modules are
Multidrop connection
connected in a 1:n or m:n mode using the serial communication module's RS-422/485 interface.
An user's communication procedure and one of the data communication functions for
Non procedure protocol communicating any data between the PLC CPU and an opposite device. Details are explained in
Chapter 6.
One of the message formats for the serial communication module for performing communication
using the MC protocol and ASCII code data.
QnA compatible 2C frame This is the same message format as the communication frame using the protocol for the QnA
(Formats 1 to 4) series serial communication modules.
• QnA compatible 2C frame (Formats 1 to 4): QnA simplified frame (Formats 1 to 4)
Details are explained in Chapter 4 of the Reference Manual.
One of the message formats for the serial communication module for performing communication
using the MC protocol and ASCII code data.
QnA compatible 3C frame
This is the same message format as the communication frame using the protocol for the QnA
(Formats 1 to 4)
series serial communication modules.
QnA compatible 4C frame
• QnA compatible 3C frame (Formats 1 to 4): QnA frame (Formats 1 to 4)
(Formats 1 to 4)
• QnA compatible 4C frame (Formats 1 to 4): QnA extension frame (Formats 1 to 4)
Details are explained in Chapter 3 of the Reference Manual.
A - 21 A - 21
Terms Description
One of the message formats for the serial communication module for performing communication
using the MC protocol and binary code data.
QnA compatible 4C frame This is the same message format as the communication frame using the protocol for the QnA
(Format 5) series serial communication modules.
• QnA compatible 4C frame (Format 5): QnA extension frame (Format 5)
Details are explained in Chapter 3 of the Reference Manual.
Data name when the fixed format portion of messages to be sent or received between a serial
communication module and an opposite device is registered in the module and used for sending
and receiving data with the functions listed below. (The contents of an user frame data should
conform to the specifications of the opposite device).
The data array of the head and tail sections of a message (transmission control code, C24 station
User frame
number, sum check, fixed data, etc.) to be sent and received is registered in the serial
communication module before use.
• MC protocol on-demand function.
• Data communication function using the non procedure protocol.
Details are explained in Chapter 9 of the User's Manual (Applications).
A - 22 A - 22
Product Configuration
The following lists the product configuration of the Q series serial communication modules.
A - 23 A - 23
1 OVERVIEW
MELSEC-Q
1 OVERVIEW
1 This manual describes the specifications for the QJ71C24N, QJ71C24N-R2,
QJ71C24N-R4, QJ71C24, QJ71C24-R2 serial communication module (hereinafter
referred to as "Q series C24"), as well as the procedures prior to starting the operation,
maintenance, inspection, data communication methods for use with external devices
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.
The Q series C24 is a module that connects the Q series PLC CPU and an external
device using an RS-232 or RS-422/485 line for serial communication, in order to
achieve the data communication described below.
By using a modem/terminal adapter, a public line (analog/digital) can be used for data
communication with a remote location.
• PLC data collection/change from the external devices
(See the MELSEC Communication Protocol Reference Manual.)
• PLC monitoring and control from the external devices (See Chapter 2 of the User's
Manual (Application).)
• Data receiving and sending in any formats that conform to the external device
specifications (See (2) and (3) of Section 1.2.)
• Collection of measured data from a measuring device (See (2) of Section 1.2.)
• Operation of a PLC CPU that is connected to a personal computer (hereinafter
abbreviated as PC) installed with GX Developer (SW4D5C-GPPW-E or later,
hereinafter abbreviated as GX Developer). (See the GX Developer Manual.)
• Collection of measured
data QJ71C24-R2 • PLC data collection/change
RUN ERR.
CH.1
NEU
SD
NEU
SD CH.2
• PLC monitoring and control from an
RD RD
external device
• Data receiving and sending in any
CH. 1 formats that conform to the external
device specifications
• GX Developer
• File writing/reading
• Collection of read data • Device monitoring/testing
(a) External devices can read/write the PLC device data and sequence
programs, and can monitor PLC equipment status.
With the exception of the on-demand function described below, the PLC
does not require a sequence program because the PLC sends and receives
data based solely on commands from external devices.
(b) Using the on-demand function, data can be sent from the PLC CPU to the
external devices in each frame format of the MC protocol.
1-2 1-2
1 OVERVIEW
MELSEC-Q
Command
ERR.
CH1. 10BASE-T
USER
BAT.
BOOT
RS-232
CH.2 10BASE
SDA
SG 1
PULL
RS-422 12G
MITSUBISHI /485 7
MELSECNET/H
(MELSECNET/H mode)
Q25HCPU QJ71C24 QJ71E71 Q25HCPU QJ71C24 QJ71E71
MELSEC MELSEC
RUN ERR. RUN ERR.
POWER MODE INIT. COM.ERR POWER MODE INIT. COM.ERR
CH1. CH2. CH1. CH2.
RUN OPEN RUN OPEN
SD RD SD RD
ERR. ERR.
CH1. 10BASE-T CH1. 10BASE-T
USER USER
BAT. BAT.
BOOT BOOT
RS-232 RS-232
SDA SDA
SG 1 SG 1
PULL 2 PULL 2
SDB SDB
USB (FG) 3
USB (FG) 3
RDA RDA
4 4
(FG) (FG)
5 5
RS-232 RDB
6
RS-232 RDB
6
+12V
In the MELSECNET/10 mode, other stations (including the A/QnA series PLC
CPUs) can be accessed during data link operation.
The MC protocol is equivalent to the communication function using a dedicated
protocol that is supported by the A/QnA series computer link module/serial
communication modules.
(a) Data can be transferred in any message formats that conform to the
specifications of external devices (measuring devices, PCs, etc.).
(b) Fixed or variable length messages can be received in accordance with the
external device specifications.
• How to receive the variable length data
The external device sends data by adding at the end of the message the
end-code data (CR+LF or any one-byte data) that is set for the Q series C24.
• How to receive the fixed length data
The external device sends the amount of data equivalent to the size of the
end data that is set for the Q series C24.
Q25HCPU QJ71E71 QJ71C24
MELSEC
RUN ERR.
POWER MODE INIT. COM.ERR CH1. CH2.
RUN OPEN
End
SD RD
ERR.
10BASE-T CH1.
Reception data
USER
BAT.
BOOT
RS-232
code
10BASE CH.2
SDA
SG 1
(When receiving variable length data)
PULL 2
SDB
USB (FG) 3
RDA
4
(FG)
5
RS-232 +12 V RDB
6
12G RS -422
MITSUBISHI /485
7
(c) ASCII code data can be used for communication using the ASCII-BIN
conversion function.
ASCII
QJ71C24
MELSEC Q25HCPU QJ71E71 QJ71C24 data
POWER MODE
RUN
ERR.
RUN
INIT.
OPEN
SD
ERR.
COM.ERR
RD
CH1. CH2.
ASCII-BIN
10BASE-T CH1.
USER
BAT.
BOOT conversion
Binary
RS-232
data
10BASE CH.2
SDA
1
Binary
SG
PULL 2
SDB
USB (FG) 3
RDA
4
(FG)
5
RS-232
data
+12V RDB
6
12G RS -422
MITSUBISHI /485
7
1-3 1-3
1 OVERVIEW
MELSEC-Q
(e) Communication can be performed using an user frame by registering the fixed
format portion of the head and tail sections of a message as an user frame.
• When sending data, the Q series C24 adds an user frame to any data
specified by the user.
• When receiving data, the Q series C24 transfers any data excluding the
user frame to the PLC CPU.
RS-232
10BASE CH.2
PULL
SDA
SG
2
1 ETX Any data format STX
SDB
USB (FG) 3
RDA 4
(FG)
MITSUBISHI
RS-232 +12V
12G
RDB
RS-422
/485
6
5
7
When sending data
(f) It is possible to clear the current reception data without interrupting the
transmission processing by using the dedicated instruction "CSET."
(b) Error check of received data can be performed using the sum-check code,
while the occurrence of a reception error at an external device can be
checked via an ACK/NAK response.
Q25HCPU QJ71E71 QJ71C24
MELSEC
RUN ERR.
POWER MODE INIT. COM.ERR CH1. CH2.
OPEN
RUN SD RD
ERR.
USER
10BASE-T CH1.
10BASE CH.2
SDA
SG 1
PULL
USB (FG)
SDB
RDA
2
4
3 ACK
RS-232 +12V
(FG)
RDB
6
5
Sending completed normally
12G RS-422
MITSUBISHI /485
7
Error NAK
Sending completed code
abnormally
(c) ASCII code data can be used for communication using the ASCII-BIN
conversion function.
ASCII
QCPU QJ71C24
Q25HCPU data
MODE
RUN
ERR.
ASCII-BIN
USER
BAT.
BOOT conversion
Binary
data
USB Binary
RS-232
data
1-4 1-4
1 OVERVIEW
MELSEC-Q
Data
RS-232
10BA SE CH.2
SDA
SG 1
PULL 2
SDB
USB (FG) 3
RDA 4
(FG)
5
RS-232 +12V RDB
6
12G RS-422
MITSUBISHI /485
7
RS-232
Notification
Modem Pager
10BA SE CH.2
SDA
1
message
SG
PULL 2
SDB
USB (FG) 3
RDA
4
(FG)
5
RS-232 +12V RDB
6
12G RS-422
MITSUBISHI /485
7
Modem Modem
RS-232
10BASE CH.2
SDA
SG 1
PULL 2
SDB
USB (FG) 3
RDA
4
(FG)
5
RS-232 +12V RDB
6
12G RS-422
MITSUBISHI /485 7
1-5 1-5
1 OVERVIEW
MELSEC-Q
(b) Connecting the GOT (Details are explained in the GOT User's Manual
(Connection).)
• By connecting a GOT (graphic operation terminal) to the interface for the
Q series C24 operations such as monitoring the PLC CPU can be
performed.
• Operations such as monitoring the PLC CPU can be performed by setting
the communication protocol of the Q series C24 interface to which a GOT
is connected to "0" with the switch setting using a GX Developer.
(c) Simultaneous connection of GX Developer and GOT
• It is possible to connect a PC with GX Developer and the GOT to two
interfaces of the Q series C24 at the same time. It is thus possible for more
than one user to perform programming, monitoring, etc. simultaneously.
• When the GOT and the PC with GX Developer are connected at the same
time, the two interfaces of the Q series C24 cannot perform an interlock
operation.
GX Developer GOT
QJ71C24-R2
Q25HCPU
MODE
RUN
CH1. CH2. or
ERR.
USER
BAT.
BOOT
CH1.
GX Developer GOT
RS-232 cable
USB
CH2.
RS-232 or
POINT
When GX Developer and/or the GOT is connected directly to the Q series C24,
switching settings using GX Developer need not be made to perform access to the
QCPU, monitoring and other operations. (They can also be performed when the
communication protocol is set to "0" by making switch settings using GX
Developer.)
1-6 1-6
1 OVERVIEW
MELSEC-Q
Q series C24
Peripheral device control PLC
1) 2) 3) 4) 1 2 1
C24
Communication through GX Developer
Communication using the MC protocol
Q series C24
Setting from non-control PLCs 1) : PLC No.1
GX Developer 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
(b) When a Q series C24 CPU of function version B is used in a multiple CPU
system, the following forms of data communication can be performed with
the Q series C24.
1) It is possible to perform data communication using the non
procedure/bidirectional protocols from the control PLC
2) It is possible to read the buffer memory from non-control PLCs.
Input/output signals can be used as contacts.
External
Non-control PLC Control PLC Q series C24 device
FROM
instruction
1-7 1-7
1 OVERVIEW
MELSEC-Q
3) It is possible to access the control PLC and non-control PLCs using the
MC protocol and through GX Developer from the external device.
In addition, data communication with the control PLC of the Q series C24
can be performed using the non procedure/bidirectional protocol.
(Example) When communicating with the MC protocol
External
Non-control PLC Control PLC Q series C24 device
Command message
Communication using the
transmitted using a
MC protocol (read/write)
QnA compatible 4C
03E0H to 03E3H 03FFH Specify the QCPU to be frame
accessed by the I/O number
of the requested module.
Response message
Data
Device memory, etc.
Data
Device memory, etc.
Local station
Peripheral device
Communication through GX Developer
1) 2) 3) 4) 1 2 1' Communication using the MC protocol
1-8 1-8
1 OVERVIEW
MELSEC-Q
(a) The remote password check function of the Q series C24 prevents users at
a remote location to access QCPUs illegally using the modem function of the
Q series C24.
(The remote password is checked in the following forms of data communication)
• Communication using the MC protocol
(The remote password check is not carried out in data communication
using the non procedure/bidirectional protocols.)
• Access to the PLC through GX Developer
The remote password function is one of the QCPU functions and used for
preventing illegal access to the QCPU by other users.
Use GX Developer to set a remote password for the QCPU in order to
activate the remote password function of the QCPU.
(b) If the Q series C24 is specified in the parameters of a QCPU as being
subject to the remote password check, the remote password can be
unlocked (canceled) using either one of the methods below, to allow data
communication from the external device. It is necessary to connect a line to
the modem first.
• When communicating using the MC protocol
Use the dedicated command for communication using the MC protocol to
unlock the remote password from the external device.
• When accessing the PLC through GX Developer
Unlock the remote password using GX Developer at the start of online
operation.
The remote password is automatically locked by disconnecting the line to
the modem.
1-9 1-9
1 OVERVIEW
MELSEC-Q
The table below lists the functions that have been added or changed in the Q series
C24 of function version B.
See Section 2.6 for the function version, serial NO. and software version of products
(CPU module, GX Developer, GX Configurator-SC) related to the Q series C24 which
can use added/changed functions.
See Appendix 1.1 concerning a comparison of functions in the different Q series C24
function versions.
QJ71C24N QJ71C24
Function Outline of function Reference section
(-R2/R4) (-R2)
This function allows access to the PLC from a PC with GX Developer and a Section 1.2 of
Simultaneous connection of
GOT connected to two different interfaces of the Q series C24 at the same User’s Manual
GX Developer and GOT
time. (Basic)
Control of RS and DTR This function allows the control of the on or off state of the RS and DTR Remark of section
signal states signals with the PLC program. 3.2.1
This function allows data communication with an external device at a
Support for 230,400 bps Chapter 4 of
transmission speed of 230,400 bps.
User’s Manual
Data transmission/reception This function allows data communication with an external device at a
(Basic)
at low speed transmission speed of 50 bps.
This function allows clearing reception data using the CSET instruction Chapter 6, Section
Clearing reception data by a
during data communication using the non procedure protocol. 9.8 of User’s
dedicated instruction
It is possible to clear the data even when data is being transmitted. Manual (Basic)
Transmission of the PLC
When the PLC CPU monitoring function is active, this function sends the Chapter 2 of
CPU monitoring information
monitoring information of the PLC CPU to the external device through the User’s Manual
through combined use of the
modem. (Application)
modem function
This function allows data communication after the external device
completes the unlock processing of the remote password set at a QCPU. It Chapter 3 of
is executed when the QCPU is accessed from a remote location using the User’s Manual
Remote password check modem function of the Q series C24 in the following forms of data (Application)
communication: Section 3.18 of
• Communication using the MC protocol Reference Manual
• Communication using GX Developer
Automatic initialization for
Initializes the modem automatically when Q Series C24 starts up.
modem
Chapter 3 of the
After line connection from the GX Developer, access to the QCPU from the
User’s Manual
GX Developer is made possible through line reconnection from the Q Series
Callback (Application)
C24 (callback). Transmission costs after line connection from the Q Series
C24 side are borne by the Q Series C24 side.
Addition of non reception This function allows messages to be received in the non reception protocol Chapter 6 of
monitoring time format in by time-out in non reception monitoring time (timer 0) if the received User’s Manual
non procedure protocol complete code and received data count have been not determined. (Application)
Transmission control This function allows the designation of the available capacity of the OS area Chapter 7 of
start/end free area that notifies the data reception failure at the time of transmission control User’s Manual
designation (DTR/DSR signal control and DC code control). (Application)
Addition of changeable data
to the user frame These functions allow the following codes to be registered as the
Chapter 9 of
(05H, 0BH, 11H, 17H) changeable data of user frames for data communication.
User’s Manual
Addition of changeable data • Horizontal parity code
(Application)
to the user frame • Sum check code of two’s-complement number
(04H, 0AH, E5H, EBH)
This function allows reception of a message consisting of the head frame
and any data field when receiving data by specifying the head frame.
Adding a reception function Chapter 11 of
The data length of the data field can be specified freely for each
through the use of user User’s Manual
combination of user frames for reception set by the user.
frames (Application)
(Receiving 1 byte providing ACK/NAK only is also possible by setting the
data length of the data field to “0.”)
1 - 10 1 - 10
1 OVERVIEW
MELSEC-Q
QJ71C24N QJ71C24
Function Outline of function Reference section
(-R2/R4) (-R2)
This function allows specification of a maximum of 10 types of transparent
Multiple specification of codes for transmission per interface when sending data using one of the Chapter 12 of
transparent codes for following protocols: User’s Manual
transmission • Non procedure protocol (Application)
• Bidirectional protocol
Chapter 15 of
Switching to the GX User’s Manual
This functions allows the GX Developer connection mode to be switched by
Developer connection mode (Application)
an external device or the PLC CPU.
by switching the mode Section 3.13 of
Reference Manual
Chapter 16 of
User’s Manual
Communication data This function allows the monitoring of communication data transmitted on (Application)
monitoring function the communication network of the Q series C24 and an external device. Operating Manual
(Protocol FB
support function)
Chapter 17 of
The UINI instruction allows change of the mode, transmission specifications
UINI instruction User’s Manual
and host station No. of the Q series C24.
(Application)
This function allows access to the control/non-control PLCs specified by the
user when performing the following forms of data communication with a
Support for multiple CPU Section 2.10 of
multiple CPU system:
system Reference Manual
• Communication using the MC protocol
• QCPU access from GX Developer
1 - 11 1 - 11
2 SYSTEM CONFIGURATION AND AVAILABLE FUNCTIONS
MELSEC-Q
(2) The base module to which the Q series C24 can be mounted
The Q series C24 can be mounted into any I/O slot ( 1) of the base module.
1 Limited to within the range of I/O points for the CPU module and network
module (for remote I/O station)
2-1 2-1
2 SYSTEM CONFIGURATION AND AVAILABLE FUNCTIONS
MELSEC-Q
2-2 2-2
2 SYSTEM CONFIGURATION AND AVAILABLE FUNCTIONS
MELSEC-Q
2.2 Combinations of PLC CPU and External Device, and Available Functions
The following describes the system configurations and available functions when using
the Q series C24.
(a) External device and Q series C24 with 1:1 system configuration
RS-232/422
Q25HCPU QJ71E71 QJ71C24
MELSEC
RUN ERR.
POWER MODE INIT. COM.ERR CH1. CH2.
RUN OPEN
SD RD
ERR.
10BASE-T CH1.
USER
BAT.
BOOT
RS-232
10BASE CH.2
SDA
SG 1
PULL SDB
2
USB (FG) 3
RDA
4
(FG)
5
RS-232 +12V RDB
6
12G RS-422
MITSUBISHI /485
7
(b) External device and Q series C24 with n:1 system configuration
RS-485
QJ71E71 QJ71C24
MELSEC Q25HCPU
RUN ERR.
POWER MODE INIT. COM.ERR CH1. CH2.
RUN OPEN
SD RD
ERR.
10BASE-T CH1.
USER
BAT.
BOOT
RS-232
10BASE CH.2
SDA
SG 1
PULL SDB
2
USB (FG) 3
RDA
4
(FG)
5
RS-232 +12V RDB
6
12G RS-422
MITSUBISHI /485
7
2-3 2-3
2 SYSTEM CONFIGURATION AND AVAILABLE FUNCTIONS
MELSEC-Q
(c) External device and Q series C24 with 1:n system configuration
RS-485
Q25HCPU QJ71E71 QJ71C24 Q25HCPU QJ71E71 QJ71C24 Q25HCPU QJ71E71 QJ71C24 Q25HCPU QJ71E71 QJ71C24
MELSEC MELSEC MELSEC MELSEC
RUN ERR. RUN ERR. RUN ERR. RUN ERR.
POWER MODE INIT. COM.ERR POWER MODE INIT. COM.ERR POWER MODE INIT. COM.ERR POWER MODE INIT. COM.ERR
CH1. CH2. CH1. CH2. CH1. CH2. CH1. CH2.
OPEN OPEN OPEN OPEN
RUN RUN RUN RUN
SD RD SD RD SD RD SD RD
ERR. ERR. ERR. ERR.
10BASE-T CH1. 10BASE-T CH1. 10BASE-T CH1. 10BASE-T CH1.
US ER US ER US ER US ER
BAT. BAT. BAT. BAT.
BOOT BOOT BOOT BOOT
RS-232 RS-485
Q25HCPU QJ71E71 QJ71C24 Q25HCPU QJ71E71 QJ71C24 Q25HCPU QJ71E71 QJ71C24 Q25HCPU QJ71E71 QJ71C24
MELSEC MELSEC MELSEC MELSEC
RUN ERR. RUN ERR. RUN ERR. RUN ERR.
POWER MODE INIT. COM.ERR POWER MODE INIT. COM.ERR POWER MODE INIT. COM.ERR POWER MODE INIT. COM.ERR
CH1. CH2. CH1. CH2. CH1. CH2. CH1. CH2.
OPEN OPEN OPEN OPEN
RUN SD RD
RUN SD RD
RUN SD RD
RUN SD RD
ERR. ERR. ERR. ERR.
10BASE-T CH1. 10BASE-T CH1. 10BASE-T CH1. 10BASE-T CH1.
US ER US ER US ER US ER
BAT. BAT. BAT. BAT.
BOOT BOOT BOOT BOOT
SG 1 SG 1 SG 1 1
PULL SDB
2 PULL SDB
2 PULL SDB
2 PULL SDB
2
USB (FG)
USB (FG)
USB (FG)
USB (FG)
3 3 3 3
RDA 4 RDA 4 RDA 4 RDA 4
(FG) (FG) (FG) (FG)
5 5 5 5
RS-232 +12V RDB
6
RS-232 +12V RDB
6
RS-232 +12V RDB
6
RS-232 +12V RDB
6
12G 12G 12G 12G
RS-422 RS-422 RS-422 RS-422
MITSUBISHI /485
7 MITSUBISHI /485
7 MITSUBISHI /485
7 MITSUBISHI /485
7
(d) External device and Q series C24 with m:n system configuration
Q25HCPU QJ71E71 QJ71C24 Q25HCPU QJ71E71 QJ71C24 Q25HCPU QJ71E71 QJ71C24 Q25HCPU QJ71E71 QJ71C24
MELSEC MELSEC MELSEC MELSEC
RUN ERR. RUN ERR. RUN ERR. RUN ERR.
POWER MODE INIT . COM.ERR POWER MODE INIT. COM.ERR CH1. CH2. POWER MODE INIT. COM.ERR CH1. CH2. POWER MODE INIT. COM.ERR CH1. CH2.
CH1. CH2.
OPEN OPEN OPEN OPEN
RUN RUN RUN RUN
SD RD SD RD SD RD SD RD
ERR. ERR. ERR. ERR.
10BASE-T CH1. 10BASE-T 10BASE-T CH1. 10BASE-T CH1.
US ER US ER US ER US ER
BAT. BAT. BAT. BAT.
BOOT BOOT BOOT BOOT
2-4 2-4
2 SYSTEM CONFIGURATION AND AVAILABLE FUNCTIONS
MELSEC-Q
2-5 2-5
2 SYSTEM CONFIGURATION AND AVAILABLE FUNCTIONS
MELSEC-Q
This section explains the use of the Q series C24 in a multiple CPU system.
(1) When making access from the external device to the non-control CPU of the Q
series C24 using either of the following functions, use the Q series C24 of function
version B.
When the Q series C24 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
External device
(2) If the other stations to be accessed belong to the multiple CPU system, the
modules used for routing and QCPUs at the local station, all the relay stations,
and the accessed station should be modules of function version B or later. This
has to hold in all cases of accessing the non-control PLC of the module used for
routing and the accessed station. 1
(Example)
It is possible to access other stations regardless
of whether the control PLC of the module to be
routed through is the same or different. External device
Local station
Peripheral device
Communication through GX Developer
1) 2) 3) 4) 1 2 1' Communication using the MC protocol
1 When accessing other stations, a module used for routing can access the
following modules:
• MELSECNET/H, MELSECNET/10 network modules
• Q series C24
• Ethernet interface modules
2-6 2-6
2 SYSTEM CONFIGURATION AND AVAILABLE FUNCTIONS
MELSEC-Q
This section describes the use of the Q series C24 with the Q00J/Q00/Q01CPU.
2-7 2-7
2 SYSTEM CONFIGURATION AND AVAILABLE FUNCTIONS
MELSEC-Q
This section describes the use of the Q series C24 at a MELSECNET/H remote I/O
station.
It is not necessary to read this section if the Q series C24 is used with the QCPU.
External device
MELSECNET/H
Remote I/O network
QJ72
LP25
-25
(Remote I/O station)
2-8 2-8
2 SYSTEM CONFIGURATION AND AVAILABLE FUNCTIONS
MELSEC-Q
REMARK
It is only possible to read/write from/to the buffer memory of an intelligent function
module for the MELSECNET/10 remote I/O station compatible with the QnA/A series.
2-9 2-9
2 SYSTEM CONFIGURATION AND AVAILABLE FUNCTIONS
MELSEC-Q
3 The dedicated instructions are unavailable for the MELSECNET/H remote I/O
station.
For the functions that use the dedicated instructions to make communication,
perform programming by the following methods.
Dedicated instruction Method Explanation section
FROM, TO Perform programming using the REMFR/REMTO instruction. Appendix 9.2
ONDEMAND Appendix 9.3
INPUT Appendix 9.4
Perform programming using the REMFR/REMTO instruction
OUTPUT Appendix 9.5
and I/O signal.
BIDIN Appendix 9.4
BIDOUT Appendix 9.5
SPBUSY No method
Perform programming using the receive data clear request
CSET (Receive data clear) Appendix 9.6
area of the buffer memory.
No method
BUFRCVS
(Data cannot be received using an interrupt program)
PRR Perform programming using the REMFR/REMTO instruction Appendix 9.7
CSET (Initial setting) and I/O signal. Appendix 9.8
No method
CSET (PLC CPU monitoring
(Register/delete the PLC CPU using the MC protocol or GX
function)
Configurator-SC.)
Appendix 9.9
PUTE Perform programming using the REMFR/REMTO instruction
Appendix 9.11
and I/O signal.
GETE Appendix 9.10
Perform programming using the REMFR/REMTO instructions
UINI Appendix 9.12
and I/O signals. (However, the station No. cannot be changed.)
2 - 10 2 - 10
2 SYSTEM CONFIGURATION AND AVAILABLE FUNCTIONS
MELSEC-Q
POINT
(1) Connect GX Developer to a MELECNET/H remote I/O station and set the
parameters.
(2) Reset the MELECNET/H remote I/O station after changing the setting.
POINT
(1) GX Configurator-SC should be connected to a MELECNET/H remote I/O
station before the monitoring/setting.
(2) The MELECNET/H remote I/O station should be reset after changing the
setting.
2 - 11 2 - 11
2 SYSTEM CONFIGURATION AND AVAILABLE FUNCTIONS
MELSEC-Q
2.6 Checking the Function Version, Serial No., and Software Version
This section explains how to check the the function version, serial No. and software
version of related products that can use the functions added by the improvement of the
Q series C24.
(2) Checking the version and serial No. of Q series PLC functions
(a) Using the rated plate on the side of the module to check
The serial No. and function version of the corresponding module is shown in
the SERIAL column of the rated plate.
Compliant standard
2 - 12 2 - 12
2 SYSTEM CONFIGURATION AND AVAILABLE FUNCTIONS
MELSEC-Q
[Start Procedure]
"Diagnostics" "System monitor" "Product Inf. List"
[Start Procedure]
"Help" Product Information
Software version
2 - 13 2 - 13
2 SYSTEM CONFIGURATION AND AVAILABLE FUNCTIONS
MELSEC-Q
REMARK
The version indication for the GX Configurator-SC has been changed as shown
below from the SW0D5C-QSCU-E 40E upgrade product.
Previous product Upgrade and subsequent versions
SW0D5C-QSCU-E 40E GX Configurator-SC Version 1.10L
2 - 14 2 - 14
3 SPECIFICATIONS
MELSEC-Q
3 SPECIFICATIONS
The following shows the Q series C24 performance specifications. For the
transmission specifications when communicating via the modem function, see this
section and Chapter 3 of User's Manual (Application).
3
(1) Transmission specification
Specifications
Item QJ71C24N QJ71C24N-R2
QJ71C24N-R4
QJ71C24 QJ71C24-R2
RS-422/485-compliance
RS-232-compliance RS-232-compliance
CH1 (2-piece plug-in connector socket
(D-sub 9 pin) (D-sub 9 pin)
block)
Interface
RS-422/485-compliance
RS-422/485-compliance RS-232-compliance
CH2 (2-piece plug-in connector socket
(2-piece terminal block) (D-sub 9 pin)
block)
Line Full-duplex/half-duplex communications
MC protocols
Half-duplex communications
communication
Communications
Non procedure protocol
system ( 1) Full-duplex/full-duplex communications
communication
Bidirectional protocol
Full-duplex/full-duplex communications
communication
Synchronization method Start-stop synchronization method
[QJ71C24N(-R2/R4)]
50 300 600 1200 2400 4800 9600
14400 19200 28800 38400 57600 115200 230400 (bps)
• Transmission speed 230400 bps is available for only CH1. (Not available for CH2)
• Total transmission speed of two interfaces is available up to 230400 bps.
Transmission speed • Total transmission speed of two interfaces is available up to 115200 bps when the communication data
monitoring function is used.
[QJ71C24(-R2)]
50 300 600 1200 2400 4800 9600
14400 19200 28800 38400 57600 115200 - (bps)
• Total transmission speed of two interfaces is available up to 115200 bps.
Start bits 1
Data bits 7/8
Data format
Parity bits 1 (vertical parity) or none
Stop bits 1/2
Processes one request during installed PLC CPU END processing.
MC protocol communication Number of scans that must be processed/number of link scans depends on the contents of the request.
(See Reference Manual.)
Access cycle Non procedure protocol
communication
Sends each time a send request is issued. Can receive at any time.
Bidirectional protocol
communication
Parity check All protocols and when ODD/EVEN is selected by parameter.
Error detection MC protocol/bidirectional protocol selected by parameter.
Sum check code
Non procedure protocol selected by user frame.
3-1 3-1
3 SPECIFICATIONS
MELSEC-Q
RS-232 RS-422/485
DTR/DSR (ER/DR) control Enabled Disabled
RS/CS control Enabled Disabled
Transmission control
CD signal control Enabled Disabled
DC1/DC3 (Xon/Xoff) control
Enabled Enabled
DC2/DC4 control
• DTR/DSR signal control and DC code control are selected by the user.
Line configuration RS-232 1:1 1:1 —
3 (Connection) ( 2) RS-422/485 1:1, 1:n, n:1, m:n — 1:1, 1:n, n:1, m:n
MC protocols
1:1, 1:n, m:n 1:1
communication
Non procedure
RS- protocol 1:1, 1:n, n:1 1:1
—
232 communication
Bidirectional
Line configuration protocols 1:1 1:1
(Data communication
communication) MC protocols
1:1, 1:n, m:n 1:1, 1:n, m:n
( 2) communication
Non procedure
RS-
protocol 1:1, 1:n, n:1 1:1, 1:n, n:1
422/ —
communication
485
Bidirectional
protocols 1:1 1:1
communication
Maximum 15 m Maximum 15 m
Transmission RS-232 —
(49.2 ft.) (49.2 ft.)
distance (Overall
Maximum 1200 m (4592.4 ft.) Maximum 1200 m (4592.4 ft.)
distance) RS-422/485 —
(overall distance) (overall distance)
Flash ROM write count Maximum 100,000 times to the same area
Number of occupied I/O points 32 points per slot (I/O assignment: Intelli: 32 points) ( 3)
7/0. 127 P HRV-SV Outside diameter 8.5mm (0.33in.) or more
RS-232
Recommended (Oki Electric Cable Co., Ltd. Applicable number is specified in .)
cable SPEV (SB)-MPC-0.2 3P Outside diameter approx. 6.5mm (0.26 in.) (Mitsubishi Cable Industries, LTD.)
RS-422/485
SPEV(SB)-0.2 3P Outside diameter approx. 7.5mm (0.3 in.) (Mitsubishi Cable Industries, LTD.) ( 4)
Applicable connector for external wiring D-sub 9 pin (male) screw type ( 5) —
5V DC internal current consumption 0.31A 0.26A 0.39A
External dimensions 98 (3.86 in.) (H) 27.4 (1.08 in.) (W) 90 (3.54 in.) (D)[mm]
Weight 0.20kg (0.44lb)
1 Set to transfer data with external devices using a full-duplex communication system when the Q series C24
is started. For switching to a half-duplex communication system, refer to the User’s Manual (Application).
2 Indicates possible combinations when connecting the PLC CPU and external devices (external device
side: PLC CPU side). The total number of n and m+n is up to 32 stations.
3 In order to use the Q series C24, it is necessary to set the GX Developer switches.
To set the GX Developer switches, refer to section 4.5.
4 Recommended cables SPEV (SB)-MPC-0.2 3P and SPEV (SB)-0.2 3P are equivalent in the electrical
characteristics, but partially different in the outside diameter, internal wire colors, etc.
5 See Section 3.2.1 (3) for the recommended connector.
3-2 3-2
3 SPECIFICATIONS
MELSEC-Q
The following shows the specifications of the RS-232 connector that connects the Q
series C24 to an external device.
Signal direction
Signal
Pin number Signal name
abbreviation C24 External
device
1 1 CD Carrier detect
6 2 RD(RXD) Receive data
2
7 3 SD(TXD) Send data
3 4 DTR(ER) Data terminal ready
8 5 SG Signal ground
4
9 6 DSR(DR) Dataset ready
5 7 RS(RTS) Request to send
8 CS(CTS) Clear to send
9 RI(CI) Call Indicate
(1) The control signals are described below. (The pin numbers of the connector are
enclosed in parentheses.)
1) CD signal (1)
• The Q series C24 operates according to the setting CD terminal check (see
Section 8.4.5) of the Q series C24.
CD terminal check enabled CD terminal check disabled
• The Q series C24 performs send and receive • The Q series C24 performs send and receive
processing when the CD signal (receive processing regardless of the ON/OFF status
Full-duplex carrier detection) is ON. of the CD signal.
communication • If the CD signal is turned off during data • Data communications is possible with an
communication, the Q series C24 initializes external device that cannot turn the CD
the transmission sequence. signal ON/OFF.
Half-duplex
See Chapter 8 of User's Manual (Application) Setting impossible.
communication
2) RD signal
This is a signal to receive data.
3) SD signal
This is a signal to send data.
3-3 3-3
3 SPECIFICATIONS
MELSEC-Q
(2) The ON and OFF states of each signal indicate the following conditions:
(Output side) (Input side)
ON ……… 5 V DC to 15 V DC, 3 V DC to 15 V DC
OFF ……… –5 V DC to –15 V DC, –3 V DC to –15 V DC
3-4 3-4
3 SPECIFICATIONS
MELSEC-Q
REMARK
(1) Confirmation of RS-232 control signal status
The control signal status of DTR, DSR, RS, and CD can be confirmed during
data communication by the RS-232 control signal status storage area (address
254H, 264H) of the GX Configurator-SC or Q series C24 buffer memory.
Buffer memory address
Bit position CH1 side CH2 side
254H 264H
b0 RS
b1 DSR
b2 DTR
b3 CD
1
b4 CS
b5 RI
b6 to b15 —
System 1:ON
RS
DTR 0:OFF
1 The RS signal is controlled by the Q series C24 in the following cases. (Ignore setting
contents.)
• When data is communicated with half-duplex communication
• When communication time and the RS and CS signals are controlled by the modem function
2 The DTR signal is controlled by the Q series C24 in the following cases. (Ignore setting
contents.)
• When the DTR and DSR signals are controlled
• When data is communicated by the modem function
3 After writing in the buffer memory, a lag of 0 to 20 ms occurs until it is reflected in the signal.
POINT
Be sure to control the RS and DTR signals with the Q series C24. Control of the RS
and DTR signals by the user is a prime factor for data communication errors.
• Use a 15 m (49.21 ft.), or shorter, cable conforming to the RS-232 standard as the
RS-232 cable.
(Recommended cable)
7/0. 127 P HRV-SV… : Designates the number of pairs. (For 13 pairs 7/0.127
13P HRV-SV)
(Oki Electric Cable Co., Ltd)
3-5 3-5
3 SPECIFICATIONS
MELSEC-Q
The following shows the specifications of the RS-422 connector and RS-422/485
terminal block that connect to an external device.
SDA
SDB SDA Signal Signal direction
Signal name External
SG abbreviation C24
RDA
SDB device
RDB
(FG) SDA Send data (+)
SG RDA
SDB Send data (–)
(FG)
RDB RDA Receive data (+)
(FG) RDB Receive data (–)
SG Signal ground
FG Frame ground
QJ71C24N
QJ71C24N-R4 QJ71C24 FG Frame ground
1
SDA
RDA
+
3-6 3-6
3 SPECIFICATIONS
MELSEC-Q
(1) Use a 1200 m (3937 ft.), or shorter, cable that satisfies the following specification
for the RS-422/485 cable (cable to connect the Q series C24 terminal block).
(2) Make the total distance within 1200 m (3937 ft.) when two or more device are
connected in a 1:n or m:n configuration.
(Recommended cable)
SPEV (SB)-MPC-0.2 3P ..... (MITSUBISHI CABLE INDUSTRIES, Ltd.)
SPEV (SB)-0.2 3P .............. (MITSUBISHI CABLE INDUSTRIES, Ltd.)
SPEV (SB)-MPC-0.2 3P and SPEV (SB)-0.2 3P have the same electrical
characteristics, but different external diameter and internal wire colors.
3-7 3-7
3 SPECIFICATIONS
MELSEC-Q
The following precautions must be observed when transferring data with an external
device through the Q series C24 RS-422/485 interface.
Take the following into account when the transferring data with the external device.
External device
POINT
When there is a pull-up or pull-down resistor at the external device, erroneous data
is not received.
REMARK
The following describes the case when a pull-up or pull-down resistor is not installed
to the external device.
When no station is sending, the send line becomes high impedance and noise, etc.
may cause the send line to change and the external device to receive erroneous
data.
In this case, there is probably a parity error or framing error.
Therefore, skip the erroneous data.
Since the first data during data reception is fixed in the following cases, also skip the
receive data until the fixed head data is received.
• When using an MC protocol to send data, the first data is fixed according to the
frame and format the user uses.
• When transferring data using user frames with non procedure protocol or
bidirectional protocol, the first data is selected according to the user frame that the
user registers to the Q series C24.
3-8 3-8
3 SPECIFICATIONS
MELSEC-Q
SDR Driver
1 "Output control input" (also called send gate) of
Send data the driver (send) section of the illustration at
SDB
the left determines whether or not data from
Output control input ( 1) SDA/SDB is output to the outside.
RDA Receiver
Receive data
RDB
3) Timing to start sending and to complete the transmission processing for the Q
series C24
• Timing to start sending
During data transmission, the Q series C24 outputs the actual data after
sending a mark for 2 characters, or longer, after the high impedance set by
the operations described in 1) and 2) above is reset.
• Transmission processing completion timing
The following times are necessary as H/W gate OFF time from the time that
data transmission is completed until transmission processing is completed
(the state changes to the high impedance state). (The transmission rate set
in the Q Series C24 is the object.)
When the transmission rate
is 600 bps or higher : Time for 0 to 1 bits of data to be sent
When the transmission rate
is 50 bps, 300 bps : several ms
Data
External device
Q series C24 Data
3-9 3-9
3 SPECIFICATIONS
MELSEC-Q
POINT
(1) When the external device and the Q series C24 connected in n:1 and m:n configurations
When the send signal of each device is connected as shown below, if the "Output control input" is
turned ON at two or more devices, the relevant devices output (send) data at the same time.
For the external device to transfer data normally,
• "Output control input" must be turned ON only when sending data.
• "Output control input" must be turned OFF when not sending data.
SDA
Send data
SDB
Q series C24
Output control input
RDA
Receive
RDB
data
SDA
Send data
SDB
Output control input Q series C24
RDA
Receive
RDB
data
(2) When the Q series C24 is used, if operation of the two interfaces is linked (see Section 4.5.2 (2)), the
time to send one character becomes the Q series C24 H/W gate OFF time.
(The Q series C24 turns OFF the gate after the one-character send time.)
3 - 10 3 - 10
3 SPECIFICATIONS
MELSEC-Q
3 - 11 3 - 11
3 SPECIFICATIONS
MELSEC-Q
The following table lists dedicated instructions that can be used in the Q series C24.
3 - 12 3 - 12
3 SPECIFICATIONS
MELSEC-Q
The following table lists the utility package function for the Q series C24.
3 - 13 3 - 13
3 SPECIFICATIONS
MELSEC-Q
The following table lists the parameters that are set using the GX Developer.
Parameter setting item Parameter description Set data Reference section
Performs I/O assignment Type
for the Q series C24 and Model name
I/O assignment setting Section 4.5.1
enables the switch settings Points
listed below. Start X/Y
CH1 Transmission setting
Switch 1
CH1 Communication rate setting
Switch 2 CH1 Communication protocol setting
Switch setting CH2 Transmission setting Section 4.5.2
Switch 3
CH2 Communication rate setting
Switch 4 CH2 Communication protocol setting
Switch 5 Station number setting
Interrupt pointer Start No.
Performs setting for CPU side
Interrupt pointer No. of units
Interrupt pointer setting reading reception date with Section 4.5.3
Intelligent Start I/O No.
interrupt programs.
module side Start SI No.
Password settings
Sets the remote password Section 3.3.3 of
Password Model name
Remote password settings and the Q series C24 that User's Manual
active module
performs the check. Start XY (Application)
settings
3 - 14 3 - 14
3 SPECIFICATIONS
MELSEC-Q
3 - 15 3 - 15
3 SPECIFICATIONS
MELSEC-Q
1 The device does not turn on/off by execution of a dedicated instruction when a
function that corresponds to the input signal is used.
2 The device does turn on/off by execution of a dedicated instruction when a function
that corresponds to the input signal is used (from ON to OFF: Data read completed).
3 The mode switching signal (X6/XD) turns ON at mode switching, receive clear,
user frame receive designation or transmission sequence initialization.
While the mode switching signal (X6/XD) is ON, do not issue a communication
request to the target interface.
(The communication processing of the Q series C24 is stopped while the mode
switching signal (X6/XD) is ON.)
4 The Q series C24 ready signal indicates whether or not it is possible to access the
Q series C24 from the PLC CPU.
Use it as a interlock signal for a sequence program.
(It turns on about one second after turning the power ON and reset operation.)
5 Restart the PLC CPU when the watchdog timer error signal is turned on (reset the
power and the CPU module).
6 QJ71C24N-R4 cannot be used. (Related to modem function signal.)
• X10 to X16: For system
• Y10 to Y16: Use prohibited
IMPORTANT
(1) Of the input/output signals to the PLC CPU, the signals marked with "Use
prohibited" must not be output (ON).
If any of the "Use prohibited" signals is output, the PLC system may
malfunction.
(2) When the modem function is not used or the QJ71C24N-R4 is used, X10 to
X16 are used for the system and Y10 to Y16 cannot be used.
POINT
(1) The input/output signals shown in this section are the signals used when a QnA
series serial communication module program is utilized for the Q series C24
(see Section 2 in appendix).
In the QCPU, the on/off of input/output signals to intelligent function modules is
executed with a dedicated instruction.
It is not necessary to turn the signals on/off by the sequence program, except
for the input/output signals shown in the programming of each function
reference page.
(2) When a program for a QnA series serial communication module is also utilized
for the Q series C24, it is recommended to replace the instructions with the
dedicated instructions shown on the corresponding function reference page of
each manual for the Q series C24.
3 - 16 3 - 16
3 SPECIFICATIONS
MELSEC-Q
IMPORTANT
Do not write data in the "System area" of the buffer memory.
If data is written to any of the system areas, the PLC system may malfunction.
Some of the user areas are partially system areas. Care must be taken when
performing read/write to the buffer memory.
3 - 17 3 - 17
3 SPECIFICATIONS
MELSEC-Q
POINT
(1) Use the FROM/TO instructions or other applicable commands to access the
buffer memory shown in this section when a program for a QnA series serial
communication module is utilized for the Q series C24 (see Section 2 in
Appendix).
In QCPU, the access to the buffer memory of an intelligent function module is
executed with a dedicated instruction.
It is not necessary to access directly using the FROM/TO instructions or other
instructions from the sequence program, except when accessing the buffer
memory as shown in the programming on each function reference page.
(2) When a program for a QnA series serial communication module is utilized for
the Q series C24, it is recommended to replace the instructions with the
dedicated instructions shown on the corresponding function reference page of
each manual for the Q series C24.
(3) The following initial settings (changing the default values) for data
communication must be performed by a registration operation using GX
Configurator-SC or by executing the CSET instruction for the sequence
program.
1) Initial settings for communication using the MC protocol
• Setting the unit of data length sent by the on-demand function
Word/byte units designation (addresses 150 (96H), 310 (136H))
• Setting the buffer memory used by the on-demand function
Buffer memory head address designation (addresses 160 (A0H), 320
(140H))
Data length designation (addresses 161 (A1H), 321 (141H))
2) Initial settings for communication using the non procedure/bidirectional
protocols
• Setting the unit of data length to be sent and received
Word/byte units designation (addresses 150 (96H), 310 (136H))
• Setting the transmission area
Transmission buffer memory head address designation (addresses 162
(A2H), 322 (142H))
Transmission buffer memory length designation (addresses 163 (A3H),
323 (143H))
• Setting the reception area
Receive buffer memory head address designation (addresses 166
(A6H), 326 (146H))
Receive buffer memory length designation (addresses 167 (A7H), 327
(147H))
For more details on the registration operation by GX Configurator-SC, see
the explanation of the system settings of the corresponding protocol in
Sections 8.4.5 to 8.4.8.
For more details on the CSET instruction, see Section 16.4 of the User's
Manual (Application).
3 - 18 3 - 18
3 SPECIFICATIONS
MELSEC-Q
3 - 19 3 - 19
3 SPECIFICATIONS
MELSEC-Q
3 - 20 3 - 20
3 SPECIFICATIONS
MELSEC-Q
3 - 21 3 - 21
3 SPECIFICATIONS
MELSEC-Q
3 - 22 3 - 22
3 SPECIFICATIONS
MELSEC-Q
3 - 23 3 - 23
3 SPECIFICATIONS
MELSEC-Q
3 - 24 3 - 24
3 SPECIFICATIONS
MELSEC-Q
3 - 25 3 - 25
3 SPECIFICATIONS
MELSEC-Q
3 - 26 3 - 26
3 SPECIFICATIONS
MELSEC-Q
3 - 27 3 - 27
3 SPECIFICATIONS
MELSEC-Q
3 - 28 3 - 28
3 SPECIFICATIONS
MELSEC-Q
3 - 29 3 - 29
3 SPECIFICATIONS
MELSEC-Q
1 Only QJ71C24N (-R2/R4) is usable. (System area when using QJ71C24 (-R2)
2 The following tables show the areas of block monitoring devices No. 1 to 10 (CH1
side: 8272 to 8361 (2050H to 20A9H), CH2 side: 8528 to 8617 (2150H to 21A9H)),
which are assigned for designating the PLC CPU monitoring function.
3 - 30 3 - 30
3 SPECIFICATIONS
MELSEC-Q
3 Only the QJ71C24N(-R2/R4) whose first 5 digits of the serial No. are 06062 or
later is applicable. (System area for other than the one described on the left)
3 - 31 3 - 31
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
This chapter explains the settings and procedures required before starting a system
that uses the Q series C24.
POINT
(1) When using the Q series C24, please read the safety precautions at the
beginning of this manual.
(2) The installation and setup methods of the Q series C24 are the same as those
for CPU modules.
(3) For module installation and setup, see the user's manual for the PLC CPU
used.
4 The following explains the precautions for handling the Q series C24:
(1) Do not drop the module or subject it to heavy impact since it is made of resin.
(2) Tighten the module terminal and fixing screws within the specified tightening
torque range as follows:
Screw location Tightening torque range
RS-422/485 terminal block terminal screws (M3 screw) 0.42 to 0.58 N · m
RS-422/485 plug-in connector socket terminal screw for
0.20 to 0.25 N · m
QJ71C24N-R4 (M2 screw)
Module fixing screw (normally not required) (M3 screw) ( 1) 0.36 to 0.48 N · m
1 A module can be easily fixed to a base unit using the hooks in the upper part
of the module. However, it is recommended that the module be fixed using
the module mounting screws when it is used in a place subject to vibration or
impact.
4-1 4-1
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
Start
4
Perform various settings with • I/O assignment setting of the Q series C24
GX Developer • Setting of operation mode and transmission specifications for
the Q series C24 and the external device
• See Section 4.5 in this manual.
• ROM/RAM/switch tests of the Q series C24
Perform individual station tests
• Self-loopback test of the Q series C24
with GX Developer
• See Section 4.7 in this manual
Communication using non Communication using Communication using MC protocol Communication using
procedure protocol bidirectional protocol (see the Reference Manual) special functions
(see Chapter 6) (see Chapter 7) see the User's
Manual (Application)
4-2 4-2
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
CH1
RS-422/485
SDA
CH1
2) RS-232 SDB
4) RDA
CH1
2) RS-232 RDB
SG
(FG)
CH2
RS-422/485
SDA
SDA
1
SG SDB
2
SDB 4) RDA
(FG) 3 CH2 RDB
3) 2) RS-232
RDA
4 SG
(FG) 5
(FG)
RDB
6
7
CH2
RS-422
/485 QJ71C24N-R2 QJ71C24N-R4
1 The external diagrams of the QJ71C24 are the same as QJ71C24N (except for the model name).
2 The external diagrams of the QJ71C24-R2 are the same as QJ71C24N-R2 (except for the model
name).
Name Contents
1) Display LED Display LED (For details, see (1).)
RS232 interface for serial communication with external
2) RS-232 interface
devices (D-Sub 9 pin)
RS422/485 interface for serial communication with external
3) RS-422/485 interface
devices (2-piece terminal block)
RS422/485 interface for serial communication with external
4) RS-422/485 interface
devices (2-piece plug-in socket block)
4-3 4-3
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
Compatible protocol
CH LED Display contents On/flashing Off
MC Non-procedural Bidirectional
RUN Normal operation display Normal Faulty or reset
— Valid
ERR Error display ( 1) Error has occurred Normal
NEU Neutral status on the CH1 Waiting for MC command MC command message
Valid Invalid (Off)
( 3) side display ( 2) message to be received being received
CH1 Transmission status
SD Data being transmitted Data not transmitted
display Valid
RD Reception status display Data being received Data not received
NEU Neutral status on the CH2 Waiting for MC command MC command message
Valid Invalid (Off)
( 3) side display ( 2) message to be received being received
Transmission status MC command message
CH2 SD Data being transmitted
display not transmitted
Valid
MC command message
RD Reception status display Data being received
not received
1 This LED comes on when an error occurs at Q series C24 hardware or during data communication.
2 This LED displays the data communication status via MC protocol. (see chapter 10.)
On: Waiting for the command message to be received from the external device.
Off: Processing the command message received from the external device.
3 This LED can be made valid also when "GX Developer connection" (0H) is specified in communication
protocol setting.
4-4 4-4
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
This section explains wiring between the Q series C24 and external device.
As the wiring precautions, external wiring which is resistant to the effects of external
noise is a prerequisite for reliable system operation and full use of the Q series C24
function.
(2) When connecting with an external device using an RS-232 line, use a connector
shell as specified in Section 3.2.1 on the Q series C24 end.
(3) When connecting with an external device using an RS-422/485 cable, be sure to
note the following.
(a) QJ71C24N and QJ71C24
1) Use the RS-422/485 cable recommended in section 3.3.2.
2) The RS-422/485 interface terminal block uses M3 terminal screws.
Use suitable crimp-on terminals for the terminals.
(b) QJ71C24N-R4
1) Use the RS-422/485 cable recommended in section 3.3.2.
Be sure to strip the outer insulation layer by 7 mm before connecting
the cable to the plug-in socket block.
2) When connecting the braided shield wire inside the RS-422/485 cable,
use the plate terminals included with the product. The braided shield
wire can be connected without the plate terminal. Four plate terminals
are included to connect the FG terminals of both stations. (see section
4.4.2.(6).)
3) When connecting the plug-in socket block to the QJ71C24N-R4, be
sure to confirm the layout of the socket block, and then insert it into the
RS-422/485 connector on the QJ71C24N-R4.
QJ71C24N-R4
RUN ERR.
NEU. NEU. 7m
CH1 SD SD CH2
m
RD RD
(0.2
8 in
.)
CH1 SDA
RS-422/485
SDA SDB
SDB
RDA
RDA
RDB RDB
SG
SG
(FG)
CH2 (FG)
RS-422/485
SDA
Braided shield wire
SDB
RDA
RDB
SG
Plate terminal
(FG)
(included with product)
QJ71C24N-R4
(5) See Appendix 5 for the bend radius of the connection cable.
4-5 4-5
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
The following shows the connection precautions and connection examples when using
the Q series C24 RS-232 interface for full-duplex communications.
(b) The connection cable FG signal and shield are connected as follows.
Connection on the Q series C24 side Notes
Connect to the Q series C24 connector Do not short the communication cable FG
Connection cable FG signal signal and the SG signal.
housing
When the FG signal and the SG signal are
Connect to the external device FG terminal connected inside the external device, do not
Connection cable shield
or the Q series C24 connector housing connect the FG signal to the Q series C24.
(c) When normal data communication is not obtained due to external noise,
perform the wiring as follows:
1) Connect the FG terminals on the external device and the Q series C24
using the shield of the connection cable.
2) Signals other than SG should be connected with SG signals in the
twisted pair.
Q series C24 Shield (External device)
FG
To Connector
housing
SD RD
RD SD
DSR DTR
DTR DSR
SG SG
POINT
When using an RS-232 to RS-422 converter to connect the external device and the
Q series C24, use a converter that is compatible with the external device and PLC
CPU system configuration (1:1).
4-6 4-6
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
The CD terminal check setting is set according to the specification of the external
device. When wiring shown above, DTR/DSR control or DC code control may be
performed.
(b) Connection example with an external device not capable of turning on and off
the CD signal (No. 1 pin)
1) Connection example 1
Q series C24 External device
Signal name Pin No. Signal name
CD 1 CD
RD(RXD) 2 RD(RXD)
SD(TXD) 3 SD(TXD)
DTR(ER) 4 DTR(ER)
SG 5 SG
DSR(DR) 6 DSR(DR)
RS(RTS) 7 RS(RTS)
CS(CTS) 8 CS(CTS)
RI(CI) 9
When wiring shown above, DTR/DSR control or DC code control may be performed.
2) Connection example 2
Q series C24 External device
Signal name Pin No. Signal name
CD 1 CD
RD(RXD) 2 RD(RXD)
SD(TXD) 3 SD(TXD)
DTR(ER) 4 DTR(ER)
SG 5 SG
DSR(DR) 6 DSR(DR)
RS(RTS) 7 RS(RTS)
CS(CTS) 8 CS(CTS)
RI(CI) 9
POINT
If the PLC CPU and an external device cannot be communicated, try to perform data
communication as a connection test, using the wiring connection as shown in
Connection example 2.
If data can be communicated using the wiring connection shown in Connection
example 2, rewire after checking the interface specifications on the external device
side.
4-7 4-7
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
The following shows the connection precautions and connection examples when using
the Q series C24 RS-422/485 interface.
(b) Connect the shield of the connection cable to the FG terminal on either of
the connected devices.
If normal data communication is not obtained due to external noise even if
wiring is made as shown above, perform wiring as follows:
1) Connect between the FG of both stations with the shield of the
connection cable.
On the external device side, however, follow the instruction manual of
the external device.
Be sure to use the plate terminals included with the product when
connecting the braided shield wire to the QJ71C24N-R4.
2) Connect the (FG) of the Q series C24 side to the FG terminal at the power
supply module of the station which has the Q series C24 is installed, or to
the FG terminal of the control panel on which the Q series C24 PLC is
installed.
3) Connect nnA and nnB of each signal in the connection cable as a pair.
Q series C24 External device
SDA SDA
RDA
SG SDB RDB
SDB RDA SDA
FG RDB SDB
RDA SG SG
FG (FG) FG
RDB
(FG)
Shield
4-8 4-8
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
(c) Terminal resistor must be set (or connected) for the station of both ends on
the circuit.
Match the Q series C24 to the specifications of the external device and
connect a terminal resistor (packed with the Q series C24) according to this
section.
Connect, or set a terminal resistor at the external device according to the
instruction manual of the external device.
(The terminal resistor to connect to the Q series C24)
• When communications performed using RS-422, "330 1/4 W" resistor is
connected.
• When communications performed using RS-485, "110 1/2 W" resistor is
connected.
How to discriminate between the terminating resistors
330 Ω 110 Ω
Orange Orange Brown Brown Brown Brown
(d) If data cannot be communicated with the external device at all, the polarity of
the external device could be wrong and should be checked again. If the
polarities of the Q series C24 and the external device do not match, reverse
the polarity of each signal on either device side and connect the devices with
the cable; this may enable the data to be communicated.
POINT
(1) For terminal resistor setting/connection described in this section, when the RS-
232 to RS-422 converters or similar device is used at the external device at
both ends of the circuit, a terminal resistor must be set, or connected, at the
converter.
(2) When using the RS-232C to RS-422 converters to connect the external
devices and the Q series C24, use a converter that is compatible with the
external device and PLC CPU system configuration (1:1, 1:n, m:n).
(3) Device connected to the Q series C24 RS-422/485 interface must be
standardized as RS-422 or RS-485, including 1:n and m:n connections.
SG
FG
4-9 4-9
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
(b) External device and Q series C24 with 1:n (multidrop) system configuration
1) Connection example
External device C24 1) C24 2) C24n
RD RD FG FG FG
RS-422/485 RS-422/485
cable cable
Linked R Terminal
operation resistor
2) Connection example 2
FG FG FG FG
R Terminal
resistor
(c) External device and Q series C24 with n:1 (multidrop) system configuration
FG FG FG FG
RS-422/485 RS-422/485 RS-422/485
cable cable cable
R Terminal
resistor
4 - 10 4 - 10
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
(d) External device and Q series C24 with m:n (multidrop) system configuration
1) Connection example 1
RS-232 RS-232
SD SD
RD RD
C24 1) C24 2)
SD SD
RD RD
C24n
FG FG FG
RS-422/485 RS-422/485
cable cable
2) Connection example 2
FG FG FG FG
RS-422/485 RS-422/485 RS-422/485
cable cable cable
R Terminal
resistor
4 - 11 4 - 11
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
This chapter explains various settings via GX Developer that allow the Q series C24 to
perform data communication with external devices.
See Section 3.3.3 of the User's Manual (Application) for how to perform the remote
password setting.
[Setting purpose]
The I/O assignment settings perform the settings for the types of modules to be
mounted on a base unit, the range of input/output signals, and switches of the Q
series C24.
[Startup procedure]
[GX Developer] [PLC parameters] I/O assignment .
For screen display, see the GX Developer Operating Manual.
[Setting screen]
[Display description]
Item name Setting for item Remarks
Type Select "intelli."
Model name Enter the module model name to be mounted.
(Example: QJ71C24N)
Points Select 32 points.
I/O
Start XY Enter the start I/O signal (Hexadecimal) for the target module.
assignment
Switch setting Set the communication rate, transmission specifications,
See Section 4.5.2.
communication protocol, etc.
Detailed setting Select the control PLC of the Q series C24 when a multiple
See QCPU User's Manual
CPU system is employed.
(Multiple CPU System)
Multiple CPU settings Select when using a multiple CPU system.
4 - 12 4 - 12
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
[Setting purpose]
The switch settings for I/O module and intelligent functional module perform the
settings for transmission specifications and communication protocol for
communicate with external devices.
[Setting procedure]
[GX Developer] [PLC parameters] [I/O assignment setting]
Switch setting .
For screen display, see the GX Developer Operating Manual.
[Setting screen]
[Display description]
(1) Switches 1 to 5
Set the transmission specifications and communication protocol of each interface
using the combinations of setting values for each switch with 16 bit binary data
according to the following table.
Switch number Description Remarks
b15 to b8 b7 to b0
Switch 1 See a) and b)
CH1 Communication rate setting CH1 Transmission setting
Switch 2 CH1 communication protocol setting See c)
b15 to b8 b7 to b0
Switch 3 See a) and b)
CH2 Communication rate setting CH2 Transmission setting
Switch 4 CH2 Communication protocol setting See c)
Switch 5 Station number setting See d)
For settings to perform linked operation between two Q series C24 interfaces, see (2).
POINT
When GX Developer and/or the GOT is connected directly to the Q series C24,
switching settings using GX Developer need not be made to perform access to the
QCPU, monitoring and other operations. (If switch settings are not made, operation
is performed in the GX Developer connection mode.)
4 - 13 4 - 13
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
(a) Transmission setting (CH1 side: switch 1 (lower level); CH2 side: switch 3
(lower level))
b7 b6 b5 b4 b3 b2 b1 b0
CH1 side
CH2 side
Bit Description OFF (0) ON (1) Remarks
b0 Operation setting Independent Link Must be set to OFF on CH1
b1 Data bit 7 8 Parity bit is not included
b2 Parity bit NO Yes Vertical parity
Valid only when parity bit is set to
b3 Even/odd parity Odd Even
Yes
b4 Stop bit 1 2 —
b5 Sum check code NO Yes —
b6 Write during RUN Prohibited Allowed —
b7 Setting modifications Prohibited Allowed —
All items listed in the table should be set to OFF for the interfaces for which
"GX Developer connection" is set in the communication protocol setting.
1) Operation setting
• This sets whether to use each of the two Q series C24 interfaces for
independent data communication, or to use the two for linked data
communication.
• The setting and data flow for linked operation is explained in (2).
2) Data bit setting
• This sets the bit length for one character in data communicated with an
external device according to the specifications of the external device.
(When data communication is performed using format 5 of the MC
protocol (for binary code communication), it is necessary to set it to 8
bits when processing the sum check code with the bidirectional
protocol.)
• If 7 bits are set, the data is communicated by ignoring the most
significant bit (8th bit).
3) Parity bit setting
• This sets whether or not a parity bit (vertical parity) is added for one
byte of transmission/receive data, according to the specifications of
the external device.
• The addition of the parity bit to the transmission data and the checking
of the parity bit of receive data are performed by the Q series C24.
4 - 14 4 - 14
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
POINT
(1) A setting change in the connected interface side should be set to Allowed, in
order to register a user frame to the flash ROM from an external device using
the MC protocol.
(2) Setting changes in interfaces on the CH1 and CH2 sides should both be set to
Allowed, in order to register the system setting values and user frames to the
flash ROM from the PLC CPU.
4 - 15 4 - 15
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
(b) Communication rate setting (CH1 side: switch 1 (upper level); CH2 side:
switch 3 (upper level)) 1 2 3
Communication rate Bit position Communication rate Bit position
Remarks
(Unit: bps) b15 to b8 (Unit: bps) b15 to b8
50 0FH 14400 06H
300 00H 19200 07H Try lowering the communication
600 01H 28800 08H rate when data cannot be
1200 02H 38400 09H communicated normally with an
2400 03H 57600 0AH external device due to overrun
4800 04H 115200 0BH errors and framing errors etc.
9600 05H 230400 0CH
1 Transmission speed of 230,400 bps is available for only CH1 of the
QJ71C24N (-R2/R4).
2 When connecting external devices to both of two interfaces, the total of
the communication speed should be 115,200bps or less (230,400 bps
or less if using QJ71C24N (-R2/R4)). When connecting an external
device to either of two interfaces, the maximum of 115,200 bps is
available for the interface (the maximum of 230,400 bps if using
QJ71C24N (-R2/R4)). In this case, set 300 bps for the other interface to
which no external device is connected.
3 Set "00H" to the interface for which "GX Developer connection" is set in
the communication protocol setting. Serial communication module will
operate at the communication speed set on the GX Developer.
(c) Communication protocol setting (CH1 side: switch 2; CH2 side: switch 4)
Set number Description Remarks
GX Developer communication rate and transmission specifications are
0H GX Developer connection
automatically set.
1H Format 1
2H Format 2 For communication with ASCII code in the specified form of an A compatible 1C
3H MC protocol Format 3 frame or QnA compatible 2C/3C/4C frame
4H Format 4
5H Format 5 For communication with binary code in a QnA compatible 4C frame
6H Non procedure protocol For communication using non procedure protocol
7H Bidirectional protocol For communication using bidirectional protocol
Set to the CH1 side when CH1 and CH2 interfaces are used in linked operation
8H For linked operation setting
(operated with the communication protocol of the CH2 side).
9H to DH Setting prohibited —
EH ROM/RAM/switch test For self-diagnosis of the modules
FH Individual station loopback test For checking operation of each interface of the modules
4 - 16 4 - 16
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
(d) Station number setting (switch 5 (common for both CH1 and CH2 sides))
• This setting is for communication using the MC protocol.
• When several the Q series C24s are connected on the same line with
multidrop connection, set the station number designated in the data items
of the transmission frame in each external device to 0 to 31 (0H to 1FH).
This number designates which external device is to be communicated
with the Q series C24.
• Set the station number to 0 when the system configuration of the external
device and the PLC CPU is 1:1.
Q series C24
External device
POINT
If the communication of data with external device is to be started, check the
specifications of the functions to be used and then make the settings and connect
the cables.
Make the following switch settings from the GX Developer if there is to be no
communication (if the cables are not to be connected) at the interface.
• Communication protocol setting : Set between 0H and 7H.
• Transmission setting, communication rate setting: Set all to OFF.
4 - 17 4 - 17
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
(b) Do not use the above settings for the following cases, because linked
operation cannot be performed.
1) When using the QJ71C24N-R2 or QJ71C24-R2.
2) When an external device is not connected to either of the interfaces.
3) When the bidirectional protocol is used for data communication.
4) When communicating data with an external device connected to two
interfaces that are not interacting, using functions set in the
communication protocol settings (MC protocol/non procedure protocol).
5) When communicating data using the modem function.
POINT
When two interfaces are in linked operation, the transmission time for one
character becomes equal to the hardware gate off time of the Q series C24.
4 - 18 4 - 18
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
In linked operation, all data received from one of the two interfaces is
transmitted from the other interface. In this case, exclusive control of the
received data is necessary when data is communicated using the non-
procedure protocol since all the connected stations receive the data.
When data communication is performed using the MC protocol, only
the Q series C24 having the station number designated in the
message performs the process designated by the command.
Furthermore, when data communication is performed using QnA
compatible 2C/3C/4C frames of the MC protocol, the header
information for linked operation is added to messages directed to
other stations linked by multidrop connection.
a Processing performed by the Q series C24 connected to an
external device
• The header information is added to the command messages
received from the external device that are directed to other
stations and sends them to the stations through the other
interface.
• The header information is deleted from the response
messages received from other stations and sends them to the
external device using the other interface.
(The header information is also sent during m:n connection.)
b Operation of the accessed station
The accessed station processes the request contained in the
command message, adds the header information to a response
message, and sends it using the interface that received the
command message.
REMARK
The following describes the header information that is added by the Q series C24 to
a message in linked operation.
1) When communicating with ASCII code (formats 1 to 4)
The following 13/15 character header information is added immediately before
the control code (ENQ/STX/ACK/NAK) at the start of each message (13
characters for formats 1, 3 and 4; 15 characters for format 2).
2) When communicating in binary mode (format 5)
The following 10 byte header information is added immediately before the
control code (DLE + STX) at the start of each message.
"STX" in format 3
(In ASCII code communication) (In binary code communication)
Existence in format 2
Frame ID No. for link
Station No.
Block No.
System data
System data
System data
Frame ID No.
Station No.
E E D S D S
N N L T L T
Q Q E X E X
H L H L H L H - - L H L H L H L H L L H L H L H
4 - 19 4 - 19
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
The following explains the interrupt pointer setting with GX Developer in order to
receive data using an interrupt program.
For the method to receive data using an interrupt program, see User's Manual
(Applications) Chapter 4.
[Setting purpose]
The intelligent function module interrupt pointer sets the information to read the
receive data with an interrupt program of the PLC CPU during communication
using the non procedural/bidirectional protocol.
By performing this setting, an interrupt program starts when data is received from
an external communicating device and the reading of data received by the PLC
CPU becomes possible.
[Startup procedure]
[PLC parameters] [PLC system setting] Interrupt pointer setting .
For display screen, see the GX Developer Operating Manual.
[Setting screen]
[Setting description]
(1) Interrupt pointer start No. on the PLC side
Set the start number (ranging from 50 to 255) of the interrupt pointer (Ixx) for
use in the sequence program.
4 - 20 4 - 20
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
1) Assign control numbers (SI) on the Q series C24 side to the interrupt
pointers (Ixx) used in the sequence program.
2) Set the start SI No. (0) of the interrupt control numbers.
3) The interfaces for data reception corresponding to the interrupt control
numbers are as follows:
SI No. 0: for interface on the CH1 side
SI No. 1: for interface on the CH2 side
4 - 21 4 - 21
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
The settings defined with GX Configurator-SC for operation of the Q series C24 are
described in Chapter 8.
The following concerns the data set from GX Configurator-SC.
1) Data set in the Q series C24 for the use of specific functions
2) Data set in the PLC CPU to communicate information between the Q series C24
and the PLC CPU of the mounting station.
This section explains the "Auto refresh settings" of the data mentioned in 2) above.
[Setting purpose]
The auto refresh settings are defined to automatically store the error and status
information stored in the buffer memory of the Q series C24 in devices
designated by the PLC CPU.
By this setting, the users can see the module error and status information without
accessing the Q series C24.
[Setup procedure]
[GX Developer] [Tools] [Intelligent function utility] [Start] "Intelligent
function module parameter setting module select" Auto refresh .
For display screen, see Section 8.3.
[Setting screen]
4 - 22 4 - 22
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
[Setting items]
Setting item Buffer memory address Reference section
Flash ROM access register/read/delete result 4H
1
CH1/CH2 LED ON status, communication error status ( ) 201H /202H
1 Section 8.6.9
Switch setting error, mode switching error status ( ) 203H
Section 10.1
Number of registered user frame 204H
Flash ROM system parameters write result 220H
Modem function error code 221H
Modem function sequence status 222H
Number of data registrations for connection 223H
Number of data registrations for initialization 226H
Number of notification execution 229H
Data storage area 1 notification execution data No. 22AH
Section 8.6.2
Data storage area 2 notification execution data No. 22EH
Section 3.3 of User’s Manual
Data storage area 3 notification execution data No. 232H
(Application)
Data storage area 4 notification execution data No. 236H
Data storage area 5 notification execution data No. 23AH
Accumulated count of unlock process normal completion 22FBH
Accumulated count of unlock process abnormal completion 22FCH
Accumulated count of lock process based on circuit
22FFH
disconnection
1
CH1/CH2 communication protocol status ( ) 252H/262H Section 4.5.2
1
Transmission status ( ) 253H/263H Section 8.6.3
1
RS-232 control signal status ( ) 254H/264H Section 10.1
1
Transmission sequence status ( ) 255H/265H
On-demand execution result 256H/266H
Sections 8.6.4 to 8.6.6
Data transmission result 257H/267H
Section 10.1
Data reception result 258H/268H
MC protocol transmission error code 25AH/26AH
Receive user frame nth 25BH/26BH Section 8.6.5
Chapter 11 of User’s Manual
User frame being transmitted B6H/156H (Application)
Operation status 2204H/2304H
PLC CPU monitoring Section 8.6.7
Execution result 2205H/2305H
function Chapter 2 of User’s Manual
Number of transmission 2206H/2306H
(Application)
Monitoring condition arrival block No. 2207H/2307H
1 See Section 10.1 for the contents of the buffer memory.
4 - 23 4 - 23
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
(1) Devices
(a) Set the word device of the PLC CPU which stores error and status
information in the setting item field when using the auto refresh function
between the Q series C24 and the PLC CPU.
(c) The device can be set to auto refresh for required information only.
(2) Writing auto refresh settings to QCPU and saving them in a file
(a) Writing auto refresh settings to QCPU
Use online PLC write function of GX Configurator-SC or GX Developer.
POINT
(1) The auto refresh settings are stored in the intelligent function module
parameter.
After the intelligent function module parameters have been written to the CPU
module, it enables the auto refresh setting by turning the power OFF ON or
by resetting the CPU module.
(2) The auto refresh settings cannot be changed from the sequence program.
However it is possible to add a process similar to auto refresh by using the
FROM/TO command of the sequence program.
4 - 24 4 - 24
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
After installing the Q series C24 to the base unit of QCPU, perform an individual station
test first to check the switch setting (see Section 4.5.2) and operation of the Q series
C24.
POINT
(1) When a problem occurs during data communication with an external device,
perform an individual station test as described in this section to check whether
or not there is any problem in the operation of the Q series C24.
(2) In order to avoid problems, set the PLC CPU to STOP status during the
individual station test.
(3) Test both interfaces of the Q series C24 simultaneously in an individual station test.
Alternatively, either one of the interfaces can be tested in an individual station
loopback test.
In that case, ignore the test results on the interface side for which the test is not
performed.
(4) Cable removal and reconnection before and after the individual station
loopback test should be performed with the power to the Q series C24
mounting station turned off.
(5) To restart data communication with an external device after an individual
station test, check the specifications of the devices used before defining
various settings and reconnecting cables.
For the interface that is not used for communication (no cable connection), define
the switch settings in GX Developer as follows (for the setting method, see Section
4.5.2).
• Communication protocol setting: 0H to 7H
• Transmission control settings and communication rate settings: all set to OFF.
(6) If an error occurs even though the correct settings have been made for the Q
series C24 through an individual station test, please consult your nearest
dealer or branch office with a description of the error.
A ROM/RAM/switch test checks the contents of the memory of the Q series C24 and
the switch settings set with GX Developer.
Perform a ROM/RAM/switch test with the procedure described below.
(Procedure 1) Communication protocol setting and transmission setting (see Section 4.5.2)
(1) Set the communication protocol setting on the CH2 side to EH (ROM/RAM/switch test).
Set the communication protocol setting on the CH1 side to the number (1 to 8)
used for data communication with an external device following the test.
(2) Set the transmission settings for the two interfaces to match the specifications
used when communicating data with an external device.
(Procedure 2) Performing ROM/RAM/switch tests
(1) Set the PLC CPU to STOP status.
4 - 25 4 - 25
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
(2) Restart the PLC CPU station or reset the CPU. The test starts automatically in
about one second.
(3) For the Q series C24, the following tests should be performed once.
1) ROM check
Read the ROM data and verify the sum check.
2) RAM check
Write data to RAM, and read and check it.
3) Switch check
Check whether or not each switch is set within the tolerance range and the
operation setting in the transmission settings is set to off.
4) Linked operation setting check (perform this test with the operation setting in
the transmission settings of CH2 set to on)
Check to see that the communication protocol setting on CH1 is set to 8H and
whether the communication rate setting of each channel is within the tolerance
range.
A linked operation setting check is performed when values are set as follows:
• Communication protocol setting on the CH1 side : 8H
• Operation setting in the transmission settings on the CH2 side: bit 8 = ON.
(2) The test is completed normally when the ERR LED turns off.
(3) The test is completed with error when the ERR LED turns on. Check the error
description in one of the following screens.
• The "Monitor/test others" screen of GX Configurator-SC (see Section 8.6.9)
• The buffer memory monitor screen of GX Developer (see the GX Developer
Manual for the operation method)
When checking errors in the buffer memory monitor screen of GX Developer,
monitor the following buffer memory.
Check the error descriptions on the screens by bit-decoding the monitored value
(16-bit integer). Each bit corresponds to the following error description.
Buffer memory monitored
Address CH1 side CH2 side CH1/CH2 side Description when corresponding bit is on Corrective action
Bit location 201H 202H 203H
b0 — — —
b1 SIO — When linked operation Transmission setting error
Review setting value
b2 PRO — setting Protocol setting error
(see Section 4.5.2)
b3 P/S — When independent Transmission setting error
b4 C/N — operation setting Protocol setting error
b5 to b6 — — — —
b7 NEU — Test completed —
b8 to b13 — — —
CH2 ERR — RAM error ( 1)
b14 Setting station Review setting value
— — Out of the setting station number range
number (see Section 4.5.2)
b15 CH1 ERR — ROM error ( 1)
4 - 26 4 - 26
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
4 - 27 4 - 27
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
The individual station loopback test checks the operation of the communication
function of the Q series C24.
Follow the procedure below to perform an individual station loopback test.
(Procedure 1) Connecting cable
(1) Connect cables to two interfaces as follows.
• Connect cables to the RS-232 interface within the connector and install it to the
interface.
• Connect cables to the RS-422/485 interface on a terminal block.
(Procedure 2) Communication protocol setting and transmission setting (see Section 4.5.2)
(1) Set the communication protocol setting to FH (individual station loopback test) for
both interfaces.
(2) Set each transmission setting of the two interfaces according to the transmission
specification for data communication with an external device.
(4) The LED corresponding to a test item flashes when the test starts.
• The CH1 NEU LEDs flash when checking communication with the PLC CPU.
• The SD and RD LEDs of the interface being tested flash when checking the
communication functions of each interface.
4 - 28 4 - 28
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
(2) The test is completed with an error when the ERR LED is lit. Check the error
description on one of the following screens. (The ERR LED is lit upon error
occurrence, and the test is completed.)
• The "Monitor/test others" screen of GX Configurator-SC (see Section 8.6.9)
• The buffer memory monitor screen of GX Developer (see the GX Developer
Manual for operation method)
When checking for errors in the buffer memory monitor screen of GX
Developer, monitor the LED ON status storage area (address CH1: 201H,
CH2: 202H).
Check the error descriptions on the screens by bit-decoding the monitored value
(16-bit integer). Each bit corresponds to the following error description.
Buffer memory monitored
Description when corresponding
Address CH1 side CH2 side Corrective action
bit is on
Bit location 201H 202H
b0 to b3 — — —
Remove errors occurring in the CPU
Error occurrence in the CPU module.
module.
Not enough power supply capacity. Examine the power supply capacity.
Module is not mounted correctly. Reinstall the module properly.
b4 C/N —
Check each module and remove the
Error occurrence in the base unit,
cause of the error.
extension cable, CPU module, or the
Reconnect the cable correctly.
Q series C24.
Reinstall the module correctly.
b5 to b13 — — —
(2) Perform the ending procedure for individual station loopback test
1) Follow the procedure in Section 4.7.1 to perform a ROM/RAM/switch test.
2) Perform the following procedure to end the test and start data communication
with an external device.
• Set the switch settings on GX Developer according to the procedure
specified in Section 4.5.2.
• Turn off the power to the station on which the Q series C24 is installed and
connect the communication cable with the external device.
• Turn on the power to the station on which the Q series C24 is installed.
4 - 29 4 - 29
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
A loopback test performs a communication test using the loopback test function of the
MC protocol, in order to check the connection between the Q series C24 and an
external device, the communication function of each device, and the operation of the
communication program of the external device.
(2) The following shows an example of the settings when performing a loopback test
on the interface on the CH1 side.
• Switch 1: 0544H Transmission Operation setting : Independent operation
setting Data bit : 7 bit
Parity bit : Yes (odd)
Stop bit : 1 bit
Sum check code : No
Write during RUN : Allowed
Setting modification : Prohibited
Communication rate setting : 9600 bps
• Switch 2: 0001H Communication protocol setting : MC protocol (format 1)
• Switch 3: 0000H
• Switch 4: 0000H
• Switch 5: 0000H Station number setting : 0 station
4 - 30 4 - 30
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
PC No.
Message wait
Character length
Command
0 0 F F T T 0 0 5 A B C D E 7 8
(Example)
05H 30H 30H 46H 46H 54H 54H 30H 30H 35H 41H 42H 43H 44H 45H 37H 38H
Character length
Station No.
PC No.
4 - 31 4 - 31
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
This section explains the maintenance and inspection and installing and removing of
the Q series C24.
The Q series C24 has no special inspection items other than below.
For items other than listed below, perform inspection according to the inspection items
listed in the User's Manual of the PLC CPU module in order to always use the system
in the optimal condition.
POINT
Be sure to read through the Safety Precautions in the beginning of this manual
regarding the Q series C24 inspection and maintenance.
4 - 32 4 - 32
4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
MELSEC-Q
Please read 4.1, "Handling Precautions" before mounting or dismounting the module,
and make sure to pay attention to safety and handle the module properly during the
operation.
When replacing the Q series C24 and QCPU, it becomes necessary to register the
following data on the Q series C24 again for the module to be replaced.
• Q series C24: System setting data in the flash ROM
• QCPU: PLC parameters (I/O assignment, switch setting, etc.)
The procedure for replacing a module, including re-registration of data, is as follows.
4 - 33 4 - 33
5 DATA COMMUNICATION USING THE MELSEC COMMUNICATION
PROTOCOL
MELSEC-Q
The MELSEC protocol (MC protocol) is a communication system for the Q series PLCs.
Using this protocol, the external devices can read or write device data and programs for
the PLC CPUs via the Q series C24 or Q series Ethernet interface module.
Any external devices on which application programs can be installed and which can
transmit and receive data in accordance with the MELSEC PLC protocol can
communicate with the PLC CPUs using the MC protocol.
This section describes the main functions for accessing the PLC CPUs using the 5
MC protocol.
(An overview of the data communication functions using the MC protocol is
provided in Section 3.4).
With the exception of the on-demand function described below, the Q series C24
sends and receives data based on commands from the external devices.
Thus, the PLC CPU side does not require sequence programs for data
communication.
5-1 5-1
5 DATA COMMUNICATION USING THE MELSEC COMMUNICATION
PROTOCOL
MELSEC-Q
(5) Sending data from the PLC CPU to the external device
A function for requesting data transmission from the PLC CPU to the external
device is called the on-demand function.
Urgent data that must be forwarded to the external device can be sent as on-
demand data to the external device by starting up from the PLC CPU.
The data communication functions using the MC protocol correspond to the data
communication functions using the dedicated protocol for the conventional products
listed below.
5 • A series computer link module
• QnA series serial communication module
Therefore, the message format and control procedure are the same as when
accessing the PLC using these conventional modules.
The external device side can access the Q series PLC with a program used for
accessing the PLC via a conventional module.
(Example)
Station No.
PC No.
PC No.
Station No.
code
code
Sum check
Sum check
Command
E S E
Message wait
HL H L H L H L H L H L H L
0 0 0 1 QR 0 X 0 0 0 0 4 0 0 2 7 2 0 0 0 1 1 2 3 4 A B C D 9 8
05H 30H 30H 30H 31H 51H 52H 30H 58H 30H 30H 30H 30H 34H 30H 30H 32H 37H 32H 02H 30H 30H 30H 31H31H 32H 33H 34H 41H 42H 43H 44H 03H 39H 38H
POINT
The following manual is available for performing data communication using the MC
protocol.
MELSEC Communication Protocol Reference Manual (sold separately)
5-2 5-2
5 DATA COMMUNICATION USING THE MELSEC COMMUNICATION
PROTOCOL
MELSEC-Q
POINT
To write from the external device to the intelligent function module installed in the
MELSECNET/H remote I/O station during communication using the MC protocol,
set the "Write allow/prohibit during PLC CPU RUN" in the GX Developer to enable.
When the external device accesses a QCPU in a multiple CPU system or redundant
system, it is possible to selectively access either a control or non-control CPU in the
multiple CPU system or a control or standby system CPU or System A or System B
CPU in the redundant system by specifying the target QCPU in "Requested module
I/O No." of the QnA compatible 4C frame for the MC protocol.
Refer to the Reference Manual for details.
Refer to Chapter 2 of this manual for the system configuration.
(Example) When multiple CPU No.1 is specified
Frame ID No.
Command
Sub command
Device code
Head device
PC No.
Station No.
Self-station No.
E
Requested module
Requested module
Number of device
N
Q
station No.
points
I/O No.
H L H L H L H L H — — L H L H L H — — L H — — L H — — — — L H — — L H L
F 8 0 5 0 7 0 7 0 3 E 0 0 0 0 0 0 4 0 1 0 0 0 1 X 0 0 0 0 4 0 0 0 0 5 3 6
05 46 38 30
H H H H 35 30 H H 37 30 H H 33 30 33H 45H 30H 30H 30H 30H 30H 30H 34H 30H 31H 30H 30H 30H 31H 58H 2AH 30H 30H 30H 30H 34H 30H 30H 30H 30H 35H 33H 36H
H H
REMARK
• When using the Q series C24 in a multiple CPU system, it is necessary to specify
the QCPU that controls the Q series C24 (hereinafter referred to as the control
PLC) using GX Developer.
• It is also possible to mount a Q series C24 of function version A in a multiple CPU
system. In this case, it is only possible to access the control PLC (PLC No.1).
• It is only possible to access the control PLC if data is communicated by means of
frames other than the QnA compatible 4C frame.
5-3 5-3
5 DATA COMMUNICATION USING THE MELSEC COMMUNICATION
PROTOCOL
MELSEC-Q
This section explains an overview of the remote password function when a remote
password is set for the Q series C24 mounted to a QCPU.
See Chapter 3 of the User's Manual (Application) for a detailed explanation.
5-4 5-4
5 DATA COMMUNICATION USING THE MELSEC COMMUNICATION
PROTOCOL
MELSEC-Q
REMARK
The remote password should be set to a QCPU using GX Developer in order to use
the remote password function of QCPU.
• Unlocking the remote password is possible only for the QCPU of the local station
with the Q series C24.
It is impossible to unlock the remote password for the QCPU of other stations.
See Section 3.18 of the Reference Manual for the command for unlocking the
remote password.
• When accessing the PLC using GX Developer, the remote password should be
unlocked when starting the online operation.
(3) Q series C24 setting and monitoring function when using the QCPU
remote password function
(a) Modem function system setting by GX Configurator-SC
1) Remote password mismatch notification count designation
Designate the number of times before notification when a remote
password disagreement occurs at the unlock processing by the
user/external device after the line is connected.
The Q series C24 automatically disconnects the line if more remote
password disagreements occur than the number of times designated by
this value.
2) Remote password mismatch notification accumulated count designation
Designate the number of times before notification when remote
password disagreements occur at the unlock processing by the
user/external device after the startup of the Q series C24.
The error signal on the CHn side (XE, XF) and the ERR LED turn on if
remote password disagreements occur more than the number of times
designated by this value (the line is not disconnected).
The user can clear the cumulative value counted by the Q series
C24 at an occurrence of remote password disagreement using either
one of the methods below:
• Set the cumulative number of abnormal completions of unlock
processing to "0" in the modem function monitor/test screen of GX
Configurator-SC.
• Write "0" to the storage area in the buffer memory corresponding
to the Accumulated count of abnormal completions of unlock
processing (address: 8956 (22FCH)).
5-5 5-5
5 DATA COMMUNICATION USING THE MELSEC COMMUNICATION
PROTOCOL
MELSEC-Q
If the external device is a PC running one of the basic operation systems below, it is
possible to create a communication program for the external device without
considering the detailed MC protocol (transmission/reception procedures) using one of
the following separately sold communication support tools.
See Appendix 7 for the overview of MX Component.
5-6 5-6
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
Data communication using the non procedure protocol is a function for sending and
receiving data between a PLC CPU and an external device using the message format
and transmission control procedure specified by the user.
Data can be transferred using the non procedure protocol when it is necessary to
perform data communication using the protocol for external devices such as a
measuring instrument and a bar code reader. In that case, transmission/receive data
processing can be simplified by using the communication functions with the user
frames described in the User's Manual (Application).
This chapter explains the basic transmission and reception methods when performing
data communication using the non procedure protocol.
Follow the procedure described in this chapter to create sequence programs for
sending and receiving data for the PLC CPU.
For details on the additional functions listed below for data communication using the
non procedure protocol, see the separate User's Manuals (Application).
6-1 6-1
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
The following shows the methods for receiving data in any format using the non-
procedure protocol.
There are two methods for receiving data: the "reception via receive complete code"
for receiving variable length messages, and the "reception via received data count" for
receiving fixed length messages. The receive complete code and received data count
used for data reception can be changed to any setting values chosen by the user using
GX Configurator-SC.
Q series C24
PLC CPU
Q25HCPU
Receiving area
MODE.
1) (buffer memory)
RUN. Reception data Receive data
ERR. 10
USER. read request count storage (00H) (0AH) Head data Receive complete code
6 BAT.
BOOT. area
A STX
2) 3) Receive data (41H) (02H) STX A B C D E F G H ETX
INPUT storage area C B
(02H) (41H) (42H) (43H) (44H) (45H) (46H) (47H) (48H) (03H)
(43H) (42H)
instruction
E D
USB
(45H) (44H) Transmission data External device
G F
RS-232 (47H) (46H)
ETX H
(03H) (48H)
1) When data is received from the external device using either "reception via receive
complete code" or "reception via received data count" method, the reception data
read request signal (X3/XA) turns ON.
2) Control data is stored in the device designated with the INPUT instruction.
3) When the INPUT instruction is executed, receive data is read from the reception
area of the buffer memory.
6-2 6-2
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
(b) When the Q series C24 receives the receive complete code data preset in
GX Configurator-SC by the user, it sends a receive data read request to the
sequence program.
The read request from the Q series C24 allows the sequence program to
read the receive data up to the receive complete code received from the
external device.
(c) The receive complete code can be changed to match the specifications of the
external device. An arbitrary 1-character (1-byte) code within the 00H to FFH
range can be designated.
(d) The Q series C24 issues a receive data read request to the PLC CPU as
follows, according to the set value of the receive end code.
1) When receive complete code not changed (Default value: 0D0AH)
(CR+LF is added to the end of the message and sent from the external
device.)
• If LF is received within the time set in the no-reception monitoring time
(timer 0) after CR is received, the Q series C24 stores the receive data
up to CR+LF to the buffer memory receive data storage area and turns
on the read request signal to the PLC CPU.
Timer 0
C set time L
R F
External device
Q series C24
(X3/XA)
6-3 6-3
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
• If the next data (LF, etc.) is not received within the time set in the non
reception monitoring time (timer 0) after CR is received, the Q series
C24 stores the received data up to CR to the buffer memory receive
data storage area and turns on the following signals to the PLC CPU.
When non procedure and non reception monitoring time format is 0:
Reception abnormal detection signal (X4/XB)
When non procedure and non reception monitoring time format is 1:
Reception data read request signal (X3/XA) 1
Timer 0
C set time
External device R
Q series C24 ( 2)
(User defined receive complete code data is added to the end of the
message and sent from the external device).
When the Q series C24 receives the receive complete code data
changed by the user, it stores the receive data up to the receive complete
code to the buffer memory receive area and turned on the read request
signal to the PLC CPU.
External device
Q series C24
(X3/XA)
6-4 6-4
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
(b) When the Q series C24 receives data of the received data count preset in
GX Configurator-SC by the user, it sends a reception data read request to
the sequence program.
When the sequence program receives the read request from the Q series
C24, it reads data up to the received data count received from the external
device.
(c) The received data count default value is set to 511 (words). However, it can
be changed within the size of the receive data storage area depending on
the data contents exchanged with the external device.
POINT
(1) When the receive complete code and received data count are set to GX
Configurator-SC, both become valid.
In this case, if the Q series C24 receives the receive complete code before
data corresponding to the received data count, it outputs (X3/XA: ON) a
reception read request signal to the sequence program.
(2) For details on how to change the receive complete code and received data
count, see Section 8.4.7.
6-5 6-5
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
The following shows the list of the receive area and the receive data for performing
data reception using the non procedure protocol.
to Receive data storage area • Stores the arbitrary data area of the receive data.
7FFH
(Default)
6-6 6-6
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
POINT
(1) The position and size of the receive area in the buffer memory can be changed
with the GX Configurator-SC in accordance with the specifications of the
external device and the receive data length. (See Section 8.4.7.)
(a) When changing the position and size of the receive area in the buffer
memory with GX Configurator-SC, specify as follows:
(b) If the following functions are also used when the position and size of the
receive area in the buffer memory are changed, make sure that the
addresses of the receive area do not overlap with those for the buffer
memory that stores the transmission and reception data to be used by
these functions.
1) MC protocol buffer memory read/write function
2) MC protocol on-demand function
3) Non procedure protocol transmission/receive function
4) Bidirectional protocol transmission/receive function
5) Communication data monitoring function
(2) When sending data from the external device to the Q series C24, one of the
following two adjustments should be made so that the relationship shown
below is maintained.
1) Reduce the transmission data size.
2) Increase the receive area.
Receive data storage area ≥ Size of data sent from the external device
6-7 6-7
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
1) The receive message is stored to the Q series C24 buffer memory (receive
data storage area).
2) The data is stored to the receive data storage area in low address (L) (H),
next address (L) (H) order.
Under the following conditions, when the receive data count is an odd
byte, 00H is stored in the upper byte of the final data storage position:
• When the unit for the received data count is designated in bytes.
• When data reception is performed using the receive complete code.
(Example) When receive arbitrary data area "ABCDEFG123" was stored
(The receive area is the default value.)
Q series C24
CH1
address Buffer memory
600H 5 or 10 Receive data count storage area
601H (B) (A)
42H 41H
602H (D) (C)
Head
44H 43H
603H (F) (E)
OS area Receive data storage area
46H 45H
From external "321GFEDCBA"
604H (1) (G) The receive data is stored in low
device 31H 47H address (L) → (H), next address
605H (3) (2) (L) → (H) order in the order in which
33H 32H it is received.
( 1) 606H
……
1 The OS area of the Q series C24 shown in the above diagram is the
memory (8448 bytes) that temporarily stores the data to be received while a
request for the reading of the receive data is being made to the PLC CPU.
(The user cannot read the receive data in the OS area).
When the sequence program finishes reading the receive data in the
buffer memory in response to the read request, the receive data in the OS
area, and any succeeding receive data, is stored successively in the
receive area of the buffer memory when the next read request is issued.
Also, when the OS area's free space, which stores the receive data, is
reduced to 64 bytes default value or less, a request to discontinue data
reception from the external device is issued by the following transmission
control (the RS signal does not turn OFF):
• When DTR control is set, the DTR signal turns OFF.
• When DC1/DC3 control is set, DC3 is sent.
When there is no more free space in the OS area to store receive data,
an SIO error occurs and the SIO information bit in the communication
error information storage area (address: 201H/202H) in the buffer
memory turns ON. In that case, succeeding receive data is discarded
until a free space becomes available in the OS area.
For more details on the transmission control, see Chapter 7 of the
User's Manual (Application).
6-8 6-8
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
REMARK
(1) Data reception when the receive data storage area is larger than
the receive data length
The following control is performed.
(Example) When the receive area for the CH1 side interface is located at
addresses 600H to 7FFH (default values) and data of 511 words or
less is received by the CH1 side interface.
Complete code
Q series C24
(2) Data reception when the receive data storage area is smaller
than the receive data length
Since the following control is performed, data link processing is required in the
sequence program.
Complete code
Q series C24
X3
Sequence program INPUT INPUT
6-9 6-9
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
(Receive data storage area) > (Data length received from external device)
(Example) When 550 words of data is received through the CH1 interface
in three parts when the CH1 interface receive area consists of
addresses 600H to 7FFH (default value)
External device 511 words 39 words 472 words 78 words 433 words 117 words
Q series C24
Read data....
Read data....
1st 39 words and
1st 511 words
2nd 472 words
6 - 10 6 - 10
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
M0 M1
Processing for normal completion
(receive data is stored)
M1
Processing for abnormal completion
(Reading and discarding received data,
resent request, etc.
(CH1 side)
Data reception
6 - 11 6 - 11
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
4) The device completing the INPUT instruction turns ON when the reading of receive
data is completed.
When the complete device + 1 (abnormal completion signal) turns ON, the error
code is stored in the control data completion status (S1 + 1).
(Program example)
When the Q series C24 I/O signals are from X/Y00 to X/Y1F:
Q series C24
6 - 12 6 - 12
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
POINT
(1) Receive data can also be read using interrupt programs.
For more details on reading receive data with interrupt programs, see Chapter
4 of the User's Manual (Application).
Note that if the reading of data received from the same interface is to be
performed, it is not possible to combine the reading of data received by the
main program and reading of data received by the interrupt program.
Accordingly, use one or the other of the above programs to read the data
received.
(2) The SPBUSY instruction is used to read the execution status when using a
dedicated instruction. (See Chapter 9.)
(4) When the communication data count is set in word units, and if the received
data count is an odd byte when requesting the reading of received data to the
PLC CPU, the receive data count is processed as follows:
Receive data count = Receive data byte count/2 … Fractions following the
decimal point are rounded up
Also, 00H is stored in the higher byte of the final data storage position in the
receive area where receive data is stored.
6 - 13 6 - 13
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
For the data reception by a non procedure protocol, if the transmission of data from a
transmitting device is interrupted due to trouble occurring, it may be necessary for the
data received up to the present time are cleared in the receiving device and for the
data to be received again from the start.
The methods for clearing reception data in the Q Series C24 is shown below. Either
method may be used to clear the reception data as is necessary.
1) Clear the reception data by the dedicated instruction "CSET."
2) Write to/read from the reception data clear request area (address A8H/148H).
(FROM/TO instruction)
3) Clear the reception data by GX Configurator-SC (see Section 8.7).
REMARK
When transmitting data to an external device from the Q Series C24, do not execute
a clear request of the reception data shown in this section.
If a reception data clear request is executed when transmitting data to an external
device, The Q Series C24 stops data transmission and terminates the dedicated
instruction for transmission abnormally. (The transmission completed signal does not
go ON.) If a reception data clear request is executed during data reception, the data
received up to that point are cleared.
6 - 14 6 - 14
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
Abnomal completion
The following page shows an example of a program to clear receive data with the
FROM/TO instruction.
Create a program that contains the contacts (user flags, etc.) indicating the
following statuses in the TO instruction.
• Contact when the CHn reception data read request signal (X3/XA) is OFF
• Contact when the CHn reception abnormal detection signal (X4/XB) is OFF
• Contact indicating that send and receive processes are not currently being
performed
• Contact indicating that reception data clear processing is not currently being
performed
6 - 15 6 - 15
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
Send request
execution disabled
(2)
Dedicated instruction Receive
Q series C24
for sending execution data clear
disabled, too processing
(3)
Buffer memory
address A8H "0" "1" "0"
(1)
PLC CPU TO instruction
(Program) (Write "1" to address A8H)
( 1)
( 1)
( 1)
1 Add the dotted line portion to the sequence program when the function version
A Q Series C24 is used. (Carry out communications when M19 is ON.)
6 - 16 6 - 16
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
This section explains how to detect errors that may occur when receiving data from the
external device.
The following items are considered as the primary causes of errors that may occur
during data reception.
Cause of reception error Reference section
A transmission error occurred due to noise. —
A timeout for the no-reception monitoring (timer 0) occurred. User's Manual Chapter 6
Received data that could not be converted using the ASCII-BIN conversion. (Application) Chapter 13
Received data larger than the size that could be stored in the OS area of the Q series C24. Section 6.1.2
(b) How to turn off the ERR LED and clear the error code (see Section 10.1.2.)
1) To turn off only the ERR LED, write "1" to the LED OFF request area
(addresses 0H/1H) in the buffer memory.
2) To turn off the ERR LED and clear the error code, turn ON the ERR LED
OFF request output signal (YE/YF).
(Example) To perform the ERR LED OFF and the error code clear on the
CH1 side
INPUT instruction
Completion device + 1
6 - 17 6 - 17
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
6 - 18 6 - 18
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
Q series C24
PLC CPU
Receive area
Q25HCPU
Reception (buffer memory) Reception error causing data
MODE.
RUN.
abnormal Receive data
ERR.
count storage 3 Receive
USER.
detection (00H) (03H) Head data complete code
BAT.
BOOT.
area
Receive data A STX
(41H) (02H) STX A B C D E F G H ETX
storage area
INPUT C B (02H) (41H) (42H) (43H) (44H) (45H) (46H) (47H) (48H) (03H)
(43H) (42H)
instruction
E D
USB
(45H) (44H) Transmission data External device
RS-232
Reception abnormal
detection data
Data reception
When the data from "G" to in the reception message shown in the figure above is
received normally, the data is stored in the Q series C24 OS area.
The receive data stored in the OS area will be read to the PLC CPU in the
succeeding read operation.
6 - 19 6 - 19
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
The following default values have been set for the received data count and receive
complete code that are used for data reception with the non procedure protocol.
If it is necessary to change the following default settings, change the settings on the
GX Configurator-SC "Non procedure system setting" screen according to the
specifications of the external device (see Sections 8.4.5 and 8.4.7).
Default Buffer memory address where
Setting data Allowable range Remarks
value the setting value is stored
Received data Less than the size of the Unit is in accordance with the
511 (1FFH) A4H/144H
count receive data storage area word/byte units designation
0000H to 00FFH When any code is set
Receive 0D0AH
A5H/145H When there is no receive
complete code (CR, LF) FFFFH
complete code
REMARK
Other than through the setting using GX Configurator-SC or the TO instruction at the
startup of the Q series C24, the received data count and receive complete code
setting values can be changed even after data communication has started if the
timing is as shown in the chart below.
The following describes the procedure for changing setting values for data reception
via the non procedure protocol after the start of data communication, and for the
resumption of data reception processing. Specifically, the module restrictions are
explained, along with the timing and procedure for changing the setting values.
POINT
When the reception abnormal detection signal (X4/XB) turns ON, read the error
code from the buffer memory below, and then check the type of error and take
corrective action based on the information found in Chapter 10.
• Data reception result storage area (addresses 258H/268H)
6 - 20 6 - 20
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
(Program example: I/O signals for the Q series C24 are from X/Y00 to X/Y1F)
Read request
1) 2)
Reads receive data count.
( 1)
2)
Reads the data that is equal to the receive
data count.
3)
Change the setting value for the received
data count as needed.
4)
Change the setting value for the receive
complete code as needed.
5)
Turns ON the read complete signal.
6 - 21 6 - 21
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
This section explains data transmission from the PLC CPU to the external device.
The following shows how to send data in any format using the non procedure protocol.
PLC CPU
Transmission data
STX A B C D E F G H ETX
(02H) (41H) (42H) (43H) (44H) (45H) (46H) (47H) (48H) (03H)
Q series C24
Transmission area
Transmission (buffer memory)
data count 10
designation
(00H) (0AH)
area
A STX
Transmission (41H) (02H)
data C B
designation (43H) (42H)
1) 2) area E D
OUTPUT instruction (45H) (44H) 3)
G F Transmission data
(47H) (46H) ETX H A STX
ETX H (03H) (48H) (41H) (03H)
(03H) (48H)
External device
Transmission instruction
OUTPUT instruction
completion device
1) Transmission data is stored in the device designated with the OUTPUT instruction.
2) Control data is stored in the device designated with the OUTPUT instruction.
3) When the OUTPUT instruction is executed, the Q series C24 sends the amount of
data designated by the transmission data count from the transmission data area to
the external device in ascending order of the transmission data area addresses.
6 - 22 6 - 22
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
6.2.2 Arrangement and contents of the transmission area and the transmission data
This section explains the arrangement and contents of the transmission area and the
transmission data for performing data transmission using the non procedure protocol.
6 - 23 6 - 23
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
POINT
(1) The position and size of the transmission area in the buffer memory can be
changed with GX Configurator-SC in accordance with the specifications of the
external device and the received data length. (See Sections 8.4.5 and 8.4.7.)
(a) When changing the position and size of the transmission area in the buffer
memory with GX Configurator-SC, specify as follows:
(b) If the following functions are also used when the position and size of the
transmission area in the buffer memory are changed, make sure that the
addresses of the transmission area do not overlap with those for the
buffer memory that stores the transmission and receive data to be used
by these functions.
1) MC protocol buffer memory read/write function
2) MC protocol on-demand function
3) Non procedure protocol transmission/receive function
4) Bidirectional protocol transmission/receive function
5) Communication data monitoring function
(2) Set the size of data per data transmission from the PLC CPU to the external
device so that it is smaller than the size of the transmission data's designated
area in the buffer memory.
(Transmission data designation area) ≥ (Size of arbitrary data portion to be sent
from the PLC CPU)
To transmit data whose size is larger than the transmission data designation area,
increase the transmission area, or divide the transmission data before sending.
6 - 24 6 - 24
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
CH1 side
address
Buffer memory
1)
400H
5 or 10 Transmission data count storage area
In accordance with the word/byte units designation
401H (B) (A) Word units....5
41H Bytes units....10
42H
402H (D) (C)
44H 43H
(E) 2)
403H (F)
Transmission data designation area
46H 45H
Sequentially store the transmission data to low address (L) → (H), next
404H (1) (G) address (L) → (H), in the order of transmission.
31H 47H
Transmission
instruction (In case of the CH1 side)
G.OUTPUT Un D0 D11 M0
M0 M1
M1
Processing for abnormal completion
(retransmission, etc.)
6 - 25 6 - 25
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
Transmission instruction 2)
3)
OUTPUT instruction OUTPUT
4)
OUTPUT instruction complete device
ON when transmission
OUTPUT instruction complete device + 1 abnormal completion
(normal completion/abnormal
1 scan
completion)
Transmitting data
6 - 26 6 - 26
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
(Program example)
When Q series C24 I/O signals are from X/Y00 to X/Y1F:
Q series C24
D11 (4241H)
to Transmission data to
D15 (0A0DH)
POINT
(1) The SPBUSY instruction is used to read the execution status when using a
dedicated instruction. (See Chapter 9.)
(2) More than one OUTPUT instruction cannot be executed simultaneously.
Execute the next OUTPUT instruction only after the execution of the first
OUTPUT instruction is completed.
6 - 27 6 - 27
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
This section explains how to detect errors that may occur when sending data to the
external device.
The following items are considered as the primary causes of errors that may occur
during data transmission.
Cause of reception error Reference section
User's Manual
A timeout occurred for the transmission monitoring time (timer 2) Section 6.3
(Application)
Designated number of transmission data was larger than the size that could be stored in the
Section 6.2.2
transmission area
(b) How to turn off the ERR LED and clear the error code (see Section 10.1.2)
1) To turn off only the ERR LED, write a "1" to the LED OFF request area
(addresses 0H/1H) in the buffer memory.
2) To turn off the ERR LED and clear the error code, turn ON the ERR LED
OFF request output signal (YE/YF).
(Example) To perform the ERR LED OFF and the error code clear on the
CH1 side
OUTPUT instruction
Complete device + 1
6 - 28 6 - 28
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
POINT
When a transmission error occurs, the PLC CPU may not transmit all the
designated data.
It is recommended that data communications be performed by establishing a user
arbitrary communication procedure that can check normal transmission by
reception of a response to data transmission.
6 - 29 6 - 29
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
The following describes the precautions to be taken during non procedure protocol
data communications.
1) When the power is turned on, the Reset switch on the CPU panel is
operated, or the Q series C24 mode is switched
2) When the receive data was cleared.
3) When the CD signal was turned off when data communications were
performed by setting CD terminal check enable during full-duplex
communications through the RS-232 interface.
(Example)
Station Station
STX Space Data length CR LF
No. 0 No. 2 (BIN data) Data
(02H) (20H) (32H) (32H) (0DH) (0AH)
6 - 30 6 - 30
6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
MELSEC-Q
6 - 31 6 - 31
7 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL
MELSEC-Q
This chapter explains the basic transmission and reception methods when performing
data communication using the bidirectional protocol.
Follow the procedure described in this chapter to create sequence programs for
sending and receiving data for the PLC CPU.
Regarding the additional functions listed below for data communication using the
bidirectional protocol, see the separate User's Manuals (Application)
7-1 7-1
7 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL
MELSEC-Q
This section explains the data reception from the external device.
The following shows how to receive data sent from the external device using the
bidirectional protocol. Since the size of each message received is recognized using the
"data length" information contained in the message, messages of any size can be sent
from the external device.
2) Arbitrary data
Read request (When normal) 1)
7
Contents CH1/CH2 Control Timing
7-2 7-2
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
1) When the control code ENQ is received, the Q series C24 starts data reception
processing.
When the data specified by the data length is received, the Q series C24 ends the
reception processing of that data.
If "Sum check" is set with GX Developer, the Q series C24 checks whether the
message is normal or abnormal using the sum check code received immediately
after the message and the sum check code calculated by internal processing.
If "No sum check" is set with GX Developer, messages are not checked using
the sum check codes.
2) If the message has normally been received, the reception data read request signal
(X3/XA) turns ON.
If an error has been detected when receiving the message, the Q series C24
sends an abnormal end response (NAK message) to the external device.
The reception data read request will not be sent to the PLC CPU.
(The reception abnormal detection signal (X4/XB) does not come on.)
3) Control data is stored in the device designated with the BIDIN instruction and then
the BIDIN instruction is executed.
Receive data is read from the receive area of the buffer memory.
4) When the BIDIN instruction has been executed, the Q series C24 sends a normal
end response (ACK message) to the external device.
7-3 7-3
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
7.1.2 Arrangement and contents of the receive area and the receive data
This section shows the arrangement and contents of the receive area and the receive
data for performing data reception using the bidirectional protocol.
7-4 7-4
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
POINT
(1) The position and size of the receive area in the buffer memory can be changed
with GX Configurator-SC in accordance with the specifications of the external
device and the received data length. (See Sections 8.4.5 and 8.4.7.)
(a) When changing the position and size of the receive area in the buffer
memory with GX Configurator-SC, specify as follows:
1) Receive buffer memory head address designation
Designate the starting address for the area to be used as the receive
area in the user definable area of the buffer memory (address: 400H to
1AFFH, 2600H to 3FFFH).
2) Receive buffer memory length designation
Designate by addresses the length of the area (0001H to 1A00H) to be
used as the receive area in the user definable area of the buffer
memory (address: 400H to 1AFFH, 2600H to 3FFFH).
(b) If the following functions are also used when the position and size of the
receive area in the buffer memory are changed, make sure that the
addresses of the receive area do not overlap with those for the buffer
memory that stores the transmission and reception data to be used by
these functions.
1) MC protocol buffer memory read/write function
2) MC protocol on-demand function
3) Non procedure protocol transmission/receive function
4) Bidirectional protocol transmission/receive function
5) Communication data monitoring function
(2) When sending data to the Q series C24 from the external device, one of the
following two adjustments should be made so that the relationship shown
below is maintained.
1) Reduce the send data size.
2) Increase the receive area.
(Receive data storage area) ≥ (Size of data portion sent from the external device)
7-5 7-5
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
1) The receive message is stored to the Q series C24 buffer memory (receive
data storage area).
2) The data is stored to the receive data storage area in low address (L) (H),
next address (L) (H) order.
If the received data is "ABCDEFG123", it will be stored as shown below (for
the CH1 side):
Q series C24
Receive area
(buffer memory) Receive data (response message)
Receive 5
(00H) (05H) Data Sum
data count length A B C D E F G 1 2 3
B A check
storage area (42H) (41H) ENQ (0005H) code
D C L H L H
(44H) (43H) 05H 00H 41H 42H 43H 44H 45H 46H 47H 31H 32H 33H 47H 02H
Receive F E
data storage (46H) (45H)
1 G
area (31H) (47H) Transmission data (response message)
3 2
(33H) (32H)
ACK
06H External device
(Normal completion)
When the data length unit is in bytes, 00H is stored in the higher byte of the
last data storage position in the receive area when the data length of the
message is an even byte.
1) For data communication from the external device to the Q series C24
the Q series C24 checks and processes the control code received.
It cannot be read from the sequence program.
2) For data communication from the Q series C24 to the external device
The control code to be transmitted is added by the Q series C24.
7-6 7-6
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
1) For data communication from the external device to the Q series C24
The Q series C24 checks the length of the data received.
When the reception is normal, the Q series C24 stores the receive data
in the receive data storage area of the Q series C24 buffer memory,
assigning the first byte as the lower byte (L).
2) For data communication from the Q series C24 to the external device
The length of the transmission data is the number of the transmission
data designated by the sequence program using the BIDOUT
instruction.
The Q series C24 sends this value as is from the lower byte (L).
1) For data communication from the external device to the Q series C24
If the receive data portion is normal, the Q series C24 takes the codes
as is and stores them in the receive data storage area in sequence,
beginning with the youngest address.
The storage size is in accordance with the data length in the message
(See item (b) above) and the word/byte units designation in GX
Configurator-SC.
2) For data communication from the Q series C24 to the external device
The transmission data portion is the number of the transmission data
designated by the sequence program using the BIDOUT instruction.
The Q series C24 sends the transmission data using the existing codes
until the transmission data count is reached in accordance with the
word/byte units designation in GX Configurator-SC to the transmission
data designation area.
7-7 7-7
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
1) For data communication from the external device to the Q series C24
The Q series C24 checks and processes the sum check code received.
It cannot be read from the sequence program.
When "No sum check" is specified, once a data portion of message
corresponding to the data length is received, the succeeding data
received will be ignored up to the control code that follows (See (a)).
The following example shows the contents of a sum check code in the
message.
2) For data communication from the Q series C24 to the external device
The sum check code to be transmitted is calculated and added by the Q
series C24. When "No sum check" is specified, no sum check code is
transmitted.
(Example) The following shows the sum check code when "ABCDEFGHIJ " and the numeric value 100 are sent as data
(when the unit is in bytes).
Arbitrary data
Data
E
N Data 100 Sum
Q length A B C D E F G H I J check
(000CH) (0064H) code
External device side
L H L H L H
05H 0CH 00H 41H 42H 43H 44H 45H 46H 47H 48H 49H 4AH 64H 00H 27H 03H
Q series C24
0CH + 00H + 41H + 42H + 43H + 44H + 45H + 46H +
47H + 48H + 49H + 4AH + 64H + 00H
03H 27H
(L) (H)
7-8 7-8
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
1) For data communication from the external device to the Q series C24
For error codes from the external device, transmit the codes specified by
the user.
The error codes (0022H to 005FH) that are not used by the Q series C24
can be used.
The Q series C24 stores the received error codes as a completion status
in the control code for the BIDOUT instruction.
They are also stored in the data transmission result storage area in the
buffer memory (address: 257H).
2) For data communication from the Q series C24 to the external device
The error codes are added by the Q series C24.
When an error code is transmitted, the Q series C24 writes the same
error code in the data reception result storage area of the buffer memory
(address: 258H).
7-9 7-9
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
G.BIDIN Un D0 D10 M0
M0 M1
2)
Reception data read (X3)
request signal
3)
BIDIN instruction BIDIN
4)
BIDIN instruction complete device
One scan
7 - 10 7 - 10
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
(Program example)
When Q series C24 I/O signals are from X/Y00 to X/Y1F:
Q series C24
7 - 11 7 - 11
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
POINT
(1) Receive data can also be read using interrupt programs.
For more details on reading receive data with interrupt programs, see Chapter
4 of the User's Manual (Application).
Note that if the reading of data received from the same interface is to be
performed, it is not possible to combine the reading of data received by the
main program and reading of data received by the interrupt program.
Accordingly, use one or the other of the above programs to read the data
received.
(2) The SPBUSY instruction is used to read the execution status when using a
dedicated instruction. (See Chapter 9.)
(4) If the communication data count is set in byte units and the receive data count
is an odd byte when requesting the reading of receive data to the PLC CPU,
00H is stored in the higher byte of the final data storage position in the receive
data storage area.
7 - 12 7 - 12
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
This section explains how to detect errors that may occur when receiving data from the
external device.
The following items are considered as the primary causes of errors that may occur
during data reception.
Cause of reception error Reference section
A transmission error occurred because of noise. —
A timeout occurred for the no-reception monitoring time (timer 0). Section 6.1
User's Manual
A timeout occurred for the transmission monitoring time (timer 2) Section 6.2
(Application)
Data that could not be converted with the ASCII-BIN conversion was detected. Chapter 13
Received the data length that was too long to store in the receiving area. Section 7.1.2
Simultaneous transmissions occurred. Section 7.3
(b) How to turn off the ERR LED and clear the error code (see Section 10.1.2)
1) To turn off only the ERR LED, write a "1" to the LED OFF request area
(addresses 0H/1H) in the buffer memory.
2) To turn off the ERR LED and clear the error code, turn ON the ERR LED
OFF request output signal (YE/YF).
(Example) To perform the ERR LED OFF and the error code clear on
the CH1 side
Read command
7 - 13 7 - 13
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
7 - 14 7 - 14
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
This section explains data transmission from the PLC CPU to the external device.
The following shows the method of sending data to the external device through data
communication using the bidirectional protocol.
4)
(When normal)
ACK
5)
Send instruction
BIDOUT instruction
completion device
1) Data such as control data and transmission data are stored in the device designated
with the BIDOUT instruction and then the BIDOUT instruction is executed.
2) The transmission data count and transmission data are written into the
transmission area of the buffer memory.
3) The Q series C24 sends data by adding the control code ENQ at the beginning of
the data.
When "Sum check" is designated with GX Developer, the Q series C24 adds
the sum check code calculated by internal processing to the end of the
message and then transmits the message.
When "No sum check" is designated with GX Developer, no sum check code is
sent.
4) A response for the data transmission (for normal completion: ACK message; for
abnormal completion: NAK message) is received.
5) The execution of the BIDOUT instruction completes with the transmission
processing completion of the Q series C24.
7 - 15 7 - 15
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
7.2.2 Arrangement and contents of the transmission area and the transmission data
This section explains the arrangement and contents of the transmission area and the
transmission data for performing data transmission using the bidirectional protocol.
For details on the contents of transmission data, see Section 7.1.2 (3).
to
designation area • Transmission data
5FFH The transmission data designated with the
BIDOUT instruction is written and then sent.
(Default)
7 - 16 7 - 16
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
POINT
(1) The position and size of the transmission area in the buffer memory can be
changed with GX Configurator-SC in accordance with the specifications of the
external device and the transmission data length. (See Section 8.4.5.)
(a) When changing the position and size of the transmission area in the buffer
memory with GX Configurator-SC, designate as follows:
(b) If the following functions are also used when the position and size of the
transmission area in the buffer memory are changed, make sure that the
addresses of the transmission area do not overlap with those for the
buffer memory that stores the transmission and receive data to be used
by these functions.
1) MC protocol buffer memory read/write function
2) MC protocol on-demand function
3) Non procedure protocol transmission/receive function
4) Bidirectional protocol transmission/receive function
5) Communication data monitoring function
(2) Set the size of data per data transmission from the PLC CPU to the external
device to be smaller than the size of the transmission data designation area in
the buffer memory.
(Transmission data designation area) ≥ (Size of data portion to be sent from the PLC CPU)
To transmit data whose size is larger than the transmission data designation area,
increase the transmission area, or divide the transmission data before sending.
7 - 17 7 - 17
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
Q series C24
Transmission area
(buffer memory) Transmission data (response message)
Transmission 5
(00H) (05H) Sum Data
data count 3 2 1 G F E D C B A length
B A check
designation area (42H) (41H) code (0005H) ENQ
D C H L H L
(44H) (43H) 02H 47H 33H 32H 31H 47H 46H 45H 44H 43H 42H 41H 00H 05H
Transmission F E
data designation (46H) (45H)
1 G
area (31H) (47H) Receive data (response message)
3 2
(33H) (32H)
ACK
06H External device
(Normal completion)
7 - 18 7 - 18
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
G.BIDOUT Un D0 D11 M0
M0 M1
M1
Processing for abnormal completion
(retransmission, etc.)
Transmission instruction 2)
3)
BIDOUT instruction BIDOUT
4)
BIDOUT instruction complete device
ON when transmission
BIDOUT instruction complete device + 1 abnormal completion
(Normal completion/abnormal completion)
1 scan
7 - 19 7 - 19
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
(Program example)
When Q series C24 I/O signals are from X/Y00 to X/Y1F:
7 - 20 7 - 20
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
Q series C24
to
D11 (4241H) Transmission data designation area
to Transmission data to 5FFH
D15 (0A0DH)
D11 (4241H)
to Transmission data to
D15 (0A0DH)
POINT
(1) The SPBUSY instruction is used to read the execution status when using a
dedicated instruction. (See Chapter 9.)
7 - 21 7 - 21
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
This section explains how to detect errors that may occur when sending data to the
external device.
The following items are considered as the primary causes of errors that may occur
during data transmission.
Cause of transmission error Reference section
A transmission error occurred because of noise. —
A timeout occurred for the no-reception monitoring time (timer 0). Section 6.1
A timeout occurred for the response monitoring time (timer 1). User's Manual Section 6.2
A timeout occurred for the transmission monitoring time (timer 2) (Application) Section 6.3
Data that could not be converted with the ASCII-BIN conversion was detected. Chapter 13
Designated the transmission data count that exceeded the transmission area size. Section 7.2.2
Simultaneous transmissions occurred. Section 7.3
(b) How to turn off the ERR LED and clear the error code (see Section 10.1.2)
1) To turn off only the ERR LED, write a "1" to the LED OFF request area
(addresses 0H/1H) in the buffer memory.
2) To turn off the ERR LED and clear the error code, turn ON the ERR LED
OFF request output signal (YE/YF).
(Example) To perform the ERR LED OFF and the error code clear on
the CH1 side:
Read command
7 - 22 7 - 22
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
7 - 23 7 - 23
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
This section explains the processing when simultaneous transmissions occur in full-
duplex communication.
This section explains the processing performed by the Q series C24 when the external
device and the Q series C24 transmit at the same time during data communications
using the bidirectional protocol.
Since the external device and the Q series C24 do not transmit at the same time
during half-duplex communications (see User's Manual (Application) Chapter 8), this
section does not have to be read.
When an external device and the Q series C24 transmit at the same time, the Q series
C24 processing depends on the setting of "Simultaneous transmission data valid/invalid
designation" with GX Configurator-SC.
The GX Configurator-SC setting value, "Simultaneous transmission data valid/invalid
designation" is stored in the following areas of the buffer memory.
Simultaneous transmission data valid/invalid designation area (addresses: 9BH/13BH)
The Q series C24 communication data processing for each setting is described in
Section 7.3.2.
Setting contents Value set to buffer memory Q series C24 processing contents
with GX Configurator-SC (Address 9BH/13BH) Message transmit processing Message receive processing
Waits to receive the response message Transmits a response message (2)-2)
(1)-2) while checking time-out after data after data reception (2)-1) is complete.
transmission (1)-1) is complete. Posts the receive data and receive
Transmission data: Valid
0000H Posts normal end or abnormal end result to the PLC CPU through the
Receive data: Valid
according to whether or not the PLC buffer memory.
CPU received a response message
through the buffer memory.
Posts a simultaneous transmission error Transmits a response message (2)-2)
to the PLC CPU through the buffer after data reception (2)-1) is complete.
Transmission data: Invalid
0100H memory after data transmission (1)-1). Posts the receive data and receive
Receive data: Valid
Does not wait for a response massage result to the PLC CPU through the
(1)-2) in reply to data transmission (1)-1). buffer memory.
Waits to receive the response message Ignores data reception (2)-1) and
(1)-2) while checking time-out after data discards the received data.
transmission (1)-1) is complete. Does not transmit a response
Transmission data: Valid
0001H Posts normal end or abnormal end message (2)-2).
Receive data: Invalid
according to whether or not the PLC Does not inform the PLC CPU that
CPU received a response message data was received.
through the buffer memory.
Posts a simultaneous transmission error Ignored data reception (2)-1) and
to the PLC CPU through the buffer discards the receive data.
Transmission data: Invalid memory after data transmission (1)-1). Does not transmit a response
0101H
Receive data: Invalid Does not wait to a response massage message (2)-2).
(1)-2) in reply to data transmission (1)-1). Does not inform the PLC CPU that
data was received.
( )-m) is the number showing the correspondence with the messages in the illustration shown in Section 7.3.2.
7 - 24 7 - 24
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
Examples of the Q series C24 communication data processing for various settings of
"Simultaneous transmission data valid/invalid designation" by GX Configurator-SC are
explained.
2)-1 1)-2
E A
N Arbitrary data Sum check C
External device Q code K
Q series C24 E A
Arbitrary data Sum check Time check C
N
code (timer 1) K
Q
1)-1 2)-2
POINT
When the entire message of 2)-1 was received while transmitting the message of
1)-1 in the illustration.
• The Q series C24 outputs the receive data read request signal of 2)-1 to the PLC
CPU after transmitting all 1)-1. (Turns on the X3/XA.)
2)-1
E
N Arbitrary data Sum check
External device code Ignores the receive
Q
data of 1)-1.
1)-1 2)-2
1)-1 1)-2
E A
N Sum check C
Arbitrary data
External device Q code K
1)-1
7 - 25 7 - 25
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
2)-1
E
N Arbitrary data Sum check
External device Q code Ignores the receive
data of 1)-1.
1)-1
REMARK
Time-check timer 1 (response monitoring time) shown in the illustration is described
in Section 6.2 of User's Manual (Application).
POINT
When the transmission control (see Chapter 9 of User's Manual (Application)) is
performed, and the simultaneous transmission data valid/invalid designation sets
that the receive data is valid and transmission data is valid, the Q series C24
performs message transmission and message reception processing as described
below.
During message transmission processing, time check by timer 1 (response
monitoring time) is performed.
7 - 26 7 - 26
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
The following shows the precautions when performing data communications using the
bidirectional protocol.
(1) When the transmission sequence is in the initial status, it indicates that data
transmission and reception processing has not been started.
The Q series C24 transmission sequence is initialized in the following cases.
• The power is turned on, the CPU is reset.
• When operating, or the mode is switched.
• When a response message (ACK, NAK, etc.) was received in reply to data
transmission.
• When a response message (ACK, NAK, etc.) was transmitted in reply to data
reception.
• When the CD signal was turned off during data communications using Check
CD terminal in full-duplex communications through the RS-232 interface.
(2) As a data transmission procedure, data transmission from the external device or
the Q series C24 should be performed after an response for the immediately
preceding data transmission has been received.
(3) The external device and PLC CPU must agree so that the units of the data length
(word count/byte count) in the message to be transmitted and received is the same.
The PLC CPU units can be set using the GX Configurator-SC word/byte units
designation.
Make the length of the data area in the message to be transmitted and received
the size of the Q series C24 buffer memory transmission data designation area
and receive data storage area, or less.
7 - 27 7 - 27
7 DATA COMMUNICATIONS USING BIDIRECTIONAL PROTOCOL
MELSEC-Q
POINT
(1) Perform error processing according to the error code received immediately
after the NAK message at the device that received NAK as the response
message after data transmission.
Chapter 10 shows the error codes that are transmitted from the Q series C24.
(2) If the Q series C24 receives an NAK response while transmitting data to an
external device, it completes data transmission, then reads the NAK, perform
abnormal completion.
(3) If the Q series C24 detects an error while receiving data, it ignores the receive
data corresponding to the data length.
If the data length is abnormal, the Q series C24 ignores all the data up to the
receive message head data (ENQ, etc.) received thereafter.
7 - 28 7 - 28
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
8-1 8-1
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
8-2 8-2
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
See "Method of installing the MELSOFT Series" attached with the utility package
regarding the install and uninstall operation for the utility package.
(3) About display screen errors while using the intelligent function
module utility
There may be cases in which the screen will not properly display while the
intelligent function module utility is being used, due to a lack of system resources.
If this occurs, close the intelligent function module utility first and then GX
Developer (program, comments, etc.) and other applications. Then, restart GX
Developer and the intelligent function module utility.
8-3 8-3
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
For example, if multiple intelligent function modules are installed in a remote I/O
station, set the GX Configurator so that the number of parameter settings of all
the intelligent function modules does not exceed the maximum number of
parameter settings. The total number of parameter settings is calculated
separately for the initial setting and for the automatic refresh setting.
The number of parameter settings that can be set for one module in the GX
Configurator-SC is as shown below.
Object Module Initial setting Automatic refresh setting
QJ71C24N 0 (not used) 46 (Maximum number of settings)
QJ71C24N-R2 0 (not used) 47 (Maximum number of settings)
QJ71C24N-R4 0 (not used) 46 (Maximum number of settings)
QJ71C24 0 (not used) 46 (Maximum number of settings)
QJ71C24-R2 0 (not used) 47 (Maximum number of settings)
8-4 8-4
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
8-5 8-5
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
GX Developer screen
POINT
The following settings must be performed before starting
the intelligent function module utility:
• Set the project using the GX Developer
• Set "QCPU (Q mode)" for the PC series.
POINT
The various setting values to be registered in the Q series C24's
flash ROM can be saved in a file of the PC via offline operation.
Use online operation to write system setting values to the Q series
C24. See Sections 8.4.1 through 8.4.10
8-6 8-6
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
Monitor/test screen
POINT
(1) When the setting operation is complete in each system setting screen, register
the system setting data in the flash ROM, then restart the PLC CPU resume
data transmission.
(2) With the Q series C24, monitoring, testing, and reading/writing of setting
values can be performed via online operation.
8-7 8-7
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
REMARK
The following diagram illustrates the overview of a procedure in which the GX
Configurator-SC is used to change the system setting values of the Q series C24
and save the new values to a file or write them to the Q series C24's flash ROM.
Start
Do you wish to NO
change the setting values via Go to 1) setting via online operation
offline operation?
Display the system setting sub-screen Select in the [Flash ROM setting] screen.
for changing the setting values. See Section 8.4.
NO Have you
changed all the applicable
setting values?
YES
I End
¹—
8-8 8-8
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
1) (Online operation)
YES
Is the original data saved?
NO
Is the data saved in a file?
NO
YES
Read the data from the file. Read the data from the module's flash ROM.
Set the flash ROM write allow/prohibit Select in the [Monitor] screen.
designation to "allowed". See Section 8.4.12.
YES
Do you wish
to write the new setting YES
Reset the CPU.
values to the module's
NO
IEnd
¹—
8-9 8-9
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
8.3.2 Starting the intelligent function module utility (displaying the [select parameter setting
module] screen)
[Purpose]
Start the intelligent function module utility from the GX Developer, and display the
module selection screen for the intelligent function module utility parameter setting.
The screens that perform system setting, auto refresh setting, and
monitoring/testing for the Q series C24 can be started from this module selection
screen.
POINT
To start the Intelligent function module utility, a project created with the GX
Developer whose PLC series is set as "QCPU (Q mode)" is required.
[Startup procedure]
[Tools] [Intelligent function module utility] [Start]
[Setting screen]
• Start I/O No.
Enter the start I/O number for the applicable the Q series C24
using a hexadecimal expression.
• Module type
Select [Serial communication module].
• Module model name
Select the module model name of the applicable the Q series
C24.
• Intelligent function module parameter setting module
The modules for which parameters are set with the intelligent
function module utility are displayed.
Select the target module of your operation.
It is not necessary to select [Intelligent function module,
select parameter setting module] to perform monitor/test
operation.
[Explanation of items]
8 - 10 8 - 10
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
8 - 11 8 - 11
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
POINT
(1) Saving the intelligent function module parameter files
Since files cannot be saved using the GX Developer project save operation,
save the files on the module selection screen for parameter setting described
above.
(2) Reading from and writing to PLC operations for the intelligent function module
parameters using GX Developer
(a) After the intelligent function module parameters are saved in a file, they
can be read from and written into the PLC.
(b) Set the target PLC using the GX Developer [Online] [Transfer setup].
Only use the control PLC for the Q series C24 to write the intelligent
function module parameters for a multiple CPU system to the PLC.
(c) Use the GX Developer for PLC reading or PLC writing the intelligent
function module parameters at the remote I/O station.
GX Configurator-SC can not be used.
(3) Checking for the required utility
The head I/O is displayed in the Intelligent function module utility setting
screen, but a " " may be displayed for the model name.
This means that either the required utility is not installed or that the utility
cannot be started from the GX Developer.
Check for the required utility in [Tools] - [Intelligent function utility] - [Utility
list...] in GX Developer, and set it.
8 - 12 8 - 12
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
This section explains how to perform the common operations in the data setting, auto
refresh setting and monitor/test screens.
Ctrl Used in conjunction with the mouse to select multiple cells in the selection test.
Back
space Deletes the character where the cursor is positioned.
Page
up Moves the cursor one page up.
Page
Down Moves the cursor one page down.
Make text file : Creates a text file (TXT format) under the specified
file name and saves to it the contents currently
displayed on the screen.
Start monitor : Starts monitoring of the current value field.
8 - 13 8 - 13
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
File save : Saves all system setting data for the Q series C24
to the designated file (extension: UMD).
File read : Reads all system setting data for the Q series C24
from the designated file (extension: UMD).
Close : Closes the currently displayed screen and returns
to the previously displayed screen.
End setup : Saves/writes the system setting data, closes the
current screen, and returns to the previously
displayed screen.
With offline operation, only [File save] and [File
read] are enabled.
POINT
(1) When the setting operation is complete in each system setting screen, register
the system setting data in the flash ROM, then restart the PLC CPU to resume
data transmission.
(2) If two or more intelligent function module utility package are running, perform
each operation after selecting the target utility package from the task bar and
making it active.
(3) When the menu screen for system registration to flash ROM (see Section 8.4) is
closed, all the system setting data will be cleared. Before closing the screen, write
the data to the module (enabled only via online operation) or save it to a file.
(b) Steps 1) to 3) shown in Figure 8.1 are performed using the following operations.
1) Operating from GX Developer.
[Project] [Open existing project] / [Save project] / [Save project as]
2) Operating from the utility parameter setting module selection screen.
[File] [File read] / [File save]
3) Operating from the GX Developer.
[Online] [Read from PLC / [Write to PLC] "Intelligent function
module parameters"
Or, operate from the utility parameter setting module selection screen.
[Online] [Read from PLC] / [Write to PLC]
8 - 14 8 - 14
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
4) This operation can be performed from the [Flash ROM setting] screen or
[Monitor/test] screen.
[Flash ROM setting] screen [File read]/[File save]
[Monitor/test] screen [File read]/[File save]
5) This operation can be performed from the [Monitor/Test] screen of the
utility.
[Monitor/test] screen [Read from module]/[Write to module]
GX Developer/
GX Configurator-SC Disk
Project Project
1)
A A
2)
Personal computer
B B
4)
QCPU 3) QJ71C24
5)
Q25HCPU QJ71C24
RS-232
A
B
CH.2
SDA
1
2
SDB
USB (FG) 3
RDA
4
(FG)
5
RS-232 RDB
6
RS-422
7
/485
Figure 8.1 Correlation chart for data created by the utility package
8 - 15 8 - 15
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Purpose]
Display the menu screen for flash ROM registration, which is used to change the
initial values set in the Q series C24's buffer memory.
[Startup procedure]
• Online operation
Startup from Intelligent function module utility
(GX Developer Version 4 or later)
[Online] [Monitor/test] "Select monitor/test module" Monitor/test
[Monitor] screen
Startup from the system monitor (GX Developer Version 6 or later).
[GX Developer] [Diagnostics] [System Monitor] "Select the Q series
C24 by installation status" Diagnostics... [Monitor] screen
• Offline operation
[Tools] Flash ROM setting [Flash ROM setting] screen
[Setting screen]
Screen displayed during online operation ( 1) Screen displayed during offline operation
8 - 16 8 - 16
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Setting Items]
The following table shows the selection menus for system setting/registration to
be displayed:
Function Section Remarks
User frame registration Section 8.4.1
Data for modem initialization registration Section 8.4.2
Data for modem connection registration Section 8.4.3
Can be used via online
Modem function system setting Section 8.4.4
operation.
Transmission control and others system setting Section 8.4.5
MC protocol system setting Section 8.4.6
Can be used via offline
Non procedure system setting Section 8.4.7
operation.
Bidirectional system setting Section 8.4.8
PLC CPU monitoring system setting Section 8.4.9
Transmission user frame No. designation system setting Section 8.4.10
Resetting buffer memory/flash ROM setting values to default values Section 8.4.11 Can be used only via online
Flash ROM write allow/prohibit setting Section 8.4.12 operation.
POINT
(1) The User's Manual (Basic) and GX Configurator-SC's Help function provide
the code list. Use this list as a reference.
(2) The values set in the respective setting screens explained in Section 8.4 can
be written to the Q series C24 module (via online operation only) or saved to a
file.
(3) Perform the following operations in advance to enable the registration of
setting values in the flash ROM:
(a) Switch setting using the GX Developer (see Section 4.5.2)
Set "Setting change" under [Transmission settings] to "Enable" for both
the CH1 and CH2 sides.
(b) Setting using GX Configurator-SC (see Section 8.4.12)
Set the flash ROM write allow/prohibit designation to "Allowed".
(4) Some system setting screens have a pair of screens: one for CH1 and the
other for CH2. Please note that the explanations given in Section 8.4.1 and
thereafter apply to the online operations performed in the CH1 screens.
The setting items are the same between CH1 and CH2, but different buffer
memory addresses are used to store the setting values. The respective
addresses are indicated as follows where applicable.
(Left side: address for the CH1 side, right side: address for the CH2 side)
Setting value storage buffer Reference section containing detailed
Setting item
memory address explanation
DTR/DC control Chapter 7 of
93H/133H
designation User's Manual (Application)
(5) When a multiple CPU system is employed, GX Configurator-SC should be
connected to the control PLC of the Q series C24, and the system setting data
register in the flash ROM.
It is not possible to set target PLC to multiple CPU setting of "Transfer setup"
of GX Developer and register the system setting data in the flash ROM.
8 - 17 8 - 17
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Purpose]
Register the user frame used in the following functions:
• On-demand function using the MC protocol.
• Data transmission/receive function using the non procedure protocol.
[Startup procedure]
• Online operation
[Monitor] screen User frame
• Offline operation
[Flash ROM setting] screen User frame
[Setting screen]
[Setting item]
Setting value storage Reference section containing
Setting item
buffer memory address detailed explanation
Chapter 9 of
User frame 1 to 200 —
User's Manual (Application)
REMARK
Use \ + code to specify hexadecimal numbers in the control code registration field if
QSCU is used for registering a user frame.
(Example) To register the 5 bytes of data, STX (02H), "C24," and ETX (03H), specify
the following:
\02C24\03
8 - 18 8 - 18
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Purpose]
Register the data for initializing the modem connected to the Q series C24.
[Startup procedure]
• Online operation
[Monitor] screen Data for user modem initialization
• Offline operation
[Flash ROM setting] screen Data for user modem initialization
[Setting screen]
[Setting item]
Setting value storage Reference section containing
Setting item
buffer memory address detailed explanation
Data for user initialization 1 to 30
User control data Chapter 3 of
—
Data for user initialization 1 to 30 User's Manual (Application)
Initialization command
REMARK
Use \\ code to specify a field to register "\" if GX Configurator-SC is used for data for
modem initialization.
(Example) To register the \Q2 of data: \\Q2
8 - 19 8 - 19
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Purpose]
For data communication and notification using the modem function, register the
data for connection with external devices.
[Startup procedure]
• Online operation
[Monitor] screen Data for modem connection
• Offline operation
[Flash ROM setting] screen Data for modem connection
[Setting screen]
[Setting items]
Setting value storage Reference section containing
Setting item
buffer memory address detailed explanation
Pager receiver designation
Telephone number
Data for modem External line dialing
Chapter 3 of
connection Line types —
User's Manual (Application)
1 to 30 Wait time for message transmission units: s
Message
Comment
8 - 20 8 - 20
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Purpose]
For data communication using the modem function, register system setting
values.
[Startup procedure]
• Online operation
[Monitor] screen Modem function system setting
• Offline operation
[Flash ROM setting] screen Modem function system setting
[Setting screen]
[Setting items]
Setting value storage buffer Reference section containing detailed
Setting item memory address explanation
Modem connection channel designation 2EH
Notification execution designation 2FH
Number of connection retries designation 30H
Connection retry interval designation units: s 31H
Initialization/connection timeout time designation units: s 32H
Number of initialization retries designation 33H
Data No. for initialization designation 34H
Data No. for connection designation 35H
GX Developer connection designation 36H
No-communication interval time designation units: min 37H Chapter 3 of
RS · CS control yes/no designation 38H User's Manual (Application)
Modem initialization time DR signal valid/invalid designation 2008H
Wait time of notification units: s 200AH
Circuit disconnect wait time (PLC CPU watch use) units: s 200EH
Remote password mismatch notification count designation 200CH
Remote password mismatch notification accumulated count designation 200DH
Auto modem initialization designation 2007H
Callback function designation 2001H
Callback denial notification accumulated count designation 2002H
Data No. for callback designation 1 to 10 2101H to 210AH
8 - 21 8 - 21
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Purpose]
For data communication with external devices, register system setting values for
the transmission control method, monitoring time, and buffer memory
assignment.
[Startup procedure]
• Online operation
[Monitor] screen CH Transmission control system setting
• Offline operation
[Flash ROM setting] screen CH Transmission control system setting
[Setting screen]
8 - 22 8 - 22
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Setting items]
Setting value storage Reference section containing
Setting item
buffer memory address detailed explanation
DTR/DSR (ER/DR), DC control designation 93H/133H
Chapter 7 of
DC1/DC3 (Xon/Xoff) code designation 94H/134H
User's Manual (Application)
DC2/DC4 code designation 95H/135H
Communication system designation 98H/138H Section 3.2 of
CD terminal check designation 97H/137H User's Manual (Basic)
Half-duplex communications control designation
99H/139H
Simultaneous transmission priority/non-priority designation Chapter 8 of
Half-duplex communications control designation User's Manual (Application)
9AH/13AH
Retransmission time transmission method designation
No-reception monitoring time (timer 0) designation 9CH/13CH
Chapter 6 of
Response monitoring time (timer 1) designation 9DH/13DH
User's Manual (Application)
Transmission monitoring time (timer 2) designation 9EH/13EH
Chapter 5 of
Word/byte units designation 96H/136H
User's Manual (Application)
RTS (RS) designation 92H/132H … b0 Section 3.2.1 of
DTR (ER) designation 92H/132H … b2 User's Manual (Basic)
Transmission control start free area 2012H/2112H Chapter 7 of
Transmission control end free area 2013H/2113H User's Manual (Application)
Send/Recv data monitoring designation 2018H/2118H
Action for buffer full 2019H/2119H … b0
Chapter 16 of
Stop by Timer 0 error 2019H/2119H … b2
User's Manual (Application)
Monitor buffer head address 201AH/211AH
Monitor buffer size 201BH/211BH
Transmission buffer memory head address designation A2H/142H
Transmission buffer memory length designation A3H/143H Chapters 6 and 7 of
Receive buffer memory head address designation A6H/146H User's Manual (Basic)
Receive buffer memory length designation A7H/147H
Transmission transparent code designation 1st 11FH/1BFH
2030H to 2038H/ Chapter 12 of
Transmission transparent code designation 2nd to 10th
2130H to 2138H User's Manual (Application)
Receive transparent code designation 120H/1C0H
Chapter 13 of
ASCII-BIN conversion designation 121H/1C1H
User's Manual (Application)
Chapter 4 of
Receive interrupt-issued designation 2010H/2110H
User's Manual (Application)
8 - 23 8 - 23
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Purpose]
For data transmission using the MC protocol, register system setting values.
[Startup procedure]
• Online operation
[Monitor] screen CH MC protocol system setting
• Offline operation
[Flash ROM setting] screen CH MC protocol system setting
[Setting screen]
[Setting items]
Setting value storage Reference section containing
Setting item
buffer memory address detailed explanation
8 - 24 8 - 24
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Purpose]
For data transmission using the non procedure protocol, register system setting
values.
[Startup procedure]
• Online operation
[Monitor] screen CH Non procedure system setting
• Offline operation
[Flash ROM setting] screen CH Non procedure system setting
[Setting screen]
[Setting items]
Setting value storage Reference section containing
Setting item
buffer memory address detailed explanation
Received data count designation A4H/144H Chapter 6 of
Receive complete code designation A5H/145H User's Manual (Basic)
Receive user User frame use enable/disable designation ADH/14DH
frame First frame No. designation 1st to 4th AEH to B1H/14EH to 151H
designation Last frame No. designation 1st to 4th B2H to B5H/152H to 155H
2020H to 2023H/
User frame receive format designation 1st to 4th
2120H to 2123H Chapters 9 and 11 of
2024H to 2027H/ User's Manual (Application)
Exclusive format-1 received data count 1st to 4th
2124H to 2127H
Transmission CR/LF output designation B7H/157H
user frame Output head pointer designation B8H/158H
designation Output count designation B9H/159H
Chapters 6 of
Timeout at No-protocol 2014H/2114H
User's Manual (Application)
8 - 25 8 - 25
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Purpose]
For data transmission using the bidirectional protocol, register system setting
values.
[Startup procedure]
• Online operation
[Monitor] screen CH Bidirectional system setting
• Offline operation
[Flash ROM setting] screen CH Bidirectional system setting
[Setting screen]
[Setting item]
Setting value storage Reference section containing
Setting item
buffer memory address detailed explanation
Section 7.3 of
Simultaneously transmission data valid/invalid designation 9BH/13BH
User's Manual (Basic)
8 - 26 8 - 26
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Purpose]
Register system setting values to use the PLC CPU monitoring function.
[Startup procedure]
• Online operation
[Monitor] screen CH Monitoring system setting
• Offline operation
[Flash ROM setting] screen CH Monitoring system setting
[Setting screen]
8 - 27 8 - 27
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Setting items]
Setting value storage Reference section containing
Setting item
buffer memory address detailed explanation
Cycle time units designation 2040H/2140H
Cycle time designation 2041H/2141H
PLC CPU monitoring function designation 2042H/2142H
PLC CPU monitoring transmission measure designation 2043H/2143H
Transmission pointer 2044H/2144H
Constant cycle
Output count designation 2045H/2145H
transmission
Data No. for connection designation 2046H/2146H
Number of registered word blocks designation 204DH/214DH
Number of registered bit blocks designation 204EH/214EH
PLC CPU abnormal monitoring designation 204FH/214FH
No. n block monitoring device 2050H/2150H to
Monitoring device designation 20A1H/21A1H
2051H-2052H/2151H-
Head device No. designation 2152H to 20A1H-20A2H/
21A1H-21A2H
2053H/2153H to Chapter 2 of
Read point designation
20A3H/21A3H User's Manual (Application)
Condition agreement transmission 2054H/2154H to
Monitoring condition designation 20A4H/21A4H
2055H/2155H to
Monitoring condition value designation
20A5H/21A5H
2056H/2156H to
Transmission pointer designation
20A6H/21A6H
2057H/2157H to
Number of output designation
20A7H/21A7H
2058H/2158H to
Data No. for connection designation
20A8H/21A8H
PLC PCU abnormal monitoring designation
Condition agreement transmission 20E6H/21E6H
Transmission pointer
Output count designation 20E7H/21E7H
Data No. for connection designation 20E8H/21E8H
8 - 28 8 - 28
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Purpose]
Register the output frame number to transmit data with the non procedure
protocol using the user frame.
[Startup procedure]
• Online operation
[Monitor] screen CH Output frame system setting
• Offline operation
[Flash ROM setting] screen CH Output frame system setting
[Setting screen]
[Setting item]
Setting value storage Reference section containing
Setting item
buffer memory address detailed explanation
BAH to 11DH/ Chapter 11 of
Output frame No. designation 1st to 100th
15AH to 1BDH User's Manual (Application)
8 - 29 8 - 29
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
8.4.11 Resetting the buffer memory/flash ROM setting values to the default values
This section explains how to reset the values set in the buffer memory/flash ROM to
their default values.
[Startup procedure]
[Online] [Monitor/test] "Select monitor/Test module" Monitor/test
[Monitor] screen
[Operating procedure]
(Procedure 1) In the [Monitor] screen, select [Default request] for [System setting default].
(Procedure 2) Click on Execute test .
The setting values in the buffer memory will return to their default values.
(Procedure 3) Change the setting of [Flash ROM write allow/prohibit] to "Allowed."
(Procedure 4) In the [Monitor] screen, select [Write request] for [System setting write].
(Procedure 5) Click on Execute test .
The setting values in the flash ROM will return to their default values.
This section explains the settings to allow or prohibit writing to the flash ROM.
[Startup procedure]
[Online] [Monitor/test] "Select monitor/Test module" Monitor/test
[Monitor] screen
[Operating procedure]
(Procedure 1) In the [Monitor] screen, select [Flash ROM write allow/prohibit] and set "Allowed"
or "Prohibited."
(Procedure 2) Click on Execute test .
[Flash ROM write allow/prohibit] will be set to "Allowed" or "Prohibited,"
accordingly.
8 - 30 8 - 30
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
The Auto Refresh Settings are used to automatically store the error information and
status information currently stored in the Q series C24's buffer memory in the device
specified by the PLC CPU.
For details, see Section 4.6.
8 - 31 8 - 31
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
8.6 Monitor/Test
[Purpose]
The displayed menu screen is used to perform various operations, including the
monitoring of the Q series C24's operating status and setting values and the
testing of its output signals. The monitor/test operations can be performed only
via online operation.
[Startup procedure]
Startup from Intelligent function module utility
(GX Developer Version 4 or later)
[Online] [Monitor/test] "Select monitor/Test module" Monitor/test
[Monitor] screen
Startup from the system monitor (GX Developer Version 6 or later).
[GX Developer] [Diagnostics] [System Monitor] "Select the Q series
C24 by installation status" Diagnostics... [Monitor] screen
[Monitor/test screen]
[Monitor/test items]
The following selection menus for monitor/test operation will be displayed.
Reference section containing
Function
explanation
ERR. occurrence
ERR. clear request Section 8.6.10
(Communication error information, error code information)
X · Y monitor/test Section 8.6.1
Modem function monitor/test Section 8.6.2
Transmission control and others monitor/test Section 8.6.3
MC protocol monitor Section 8.6.4
Non procedure monitor/test Section 8.6.5
Bidirectional monitor Section 8.6.6
PLC CPU monitoring monitor Section 8.6.7
Transmission user frame No. designation monitor Section 8.6.8
Monitor/test others Section 8.6.9
System setting default, system setting write Section 8.4.11
Flash ROM write allow/prohibit designation Section 8.4.12
8 - 32 8 - 32
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
8.6.1 X · Y monitor/test
[Purpose]
Perform the monitoring of I/O signals and testing of output signals.
[Startup procedure]
[Monitor] screen X · Y monitor/test
[Monitor/test screen]
[Monitor/test items]
Setting value storage Reference section containing
Monitor/test items
buffer memory address detailed explanation
X00: CH1 Transmission normal completion —
X01: CH1 Transmission abnormal completion —
X02: CH1 Transmission processing in progress —
X03: CH1 Reception data read request —
X04: CH1 Reception abnormal detection —
X06: CH1 Mode switching —
X0E: CH1 ERR. Occurrence —
Section 3.8.
X1A: CH1 Global signal —
X07: CH2 Transmission normal completion —
X08: CH2 Transmission abnormal completion —
to to
Y18: Flash ROM write request —
Y19: Flash ROM system setting request —
Y1C: System setting default request —
8 - 33 8 - 33
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Monitor/test screen]
[Monitor/test items]
Setting value storage Reference section containing
Monitor/test items
buffer memory address detailed explanation
Modem function error code 221H
Modem function sequence status 222H
Number of data registration for connection 223H
Number of data registrations for initialization 226H
Number of notification execution 229H
Data storage area 1 notification execution data No. 22AH
Data storage area 2 notification execution data No. 22EH
Data storage area 3 notification execution data No. 232H
Data storage area 4 notification execution data No. 236H Section 3.3 of
Data storage area 5 notification execution data No. 23AH User's Manual (Application)
X10: Modem initialization completion —
X11: Dial in progress —
X12: Connection in progress —
X13: Initialization/connection abnormal completion —
X14: Modem disconnection completion —
X15: Notification normal completion —
X16: Notification abnormal completion —
Y10: Modem initialization request —
8 - 34 8 - 34
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
8 - 35 8 - 35
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Test Items]
The following accumulated count of times counter values can be cleared to "0" by
the select test function.
Setting value storage Reference section containing
Test items
buffer memory address detailed explanation
Accumulated count of unlock process normal completion 22FBH
Accumulated count of unlock process abnormal completion 22FCH
Accumulated count of lock process based on circuit disconnection 22FFH
Callback permit accumulated count 22F0H Section 3.3 of
Callback denial accumulated count 22F1H User's Manual (Application)
Auto (callback) connection permit accumulated count 22F2H
Auto (callback) connection denial accumulated count 22F3H
Accumulated count of callback receive procedure cancel 22F4H
[Operation procedure]
(Step 1) Display the "Modem function monitor/test" screen.
(Step 2) Click the setting value area of the item to be cleared to "0."
(Step 3) Click the " Execute test ."
The counter value of the selected item becomes "0."
8 - 36 8 - 36
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Purpose]
Monitor the RS-232 signal status and the various setting values for data
communication.
[Startup procedure]
[Monitor] screen CH Transmission control monitor/test
[Monitor/test screen]
[Monitor/test items]
Setting value storage Reference section containing
Monitor/test items
buffer memory address detailed explanation
RTS (RS) 254H/264H … b0
DSR (DR) 254H/264H … b1
RS-232 control DTR (ER) 254H/264H … b2 Section 4.4.1 of
signal status CD 254H/264H … b3 User's Manual (Basic)
CS (CTS) 254H/264H … b4
RI (CI) 254H/264H … b5
Communication protocol status 252H/262H
Operation setting 253H/263H … b0
Data bit 253H/263H … b1
Parity bit enable/disable 253H/263H … b2
Section 4.5.2 of
Transmission Even/odd parity 253H/263H … b3
User's Manual (Basic)
status Stop bit 253H/263H … b4
Sum check code 253H/263H … b6
Write during RUM 253H/263H … b6
Setting modification 253H/263H … b7
8 - 37 8 - 37
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
8 - 38 8 - 38
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Purpose]
Monitor the status and setting values of the data communication using the MC
protocol.
[Startup procedure]
[Monitor] screen CH MC protocol monitor
[Monitor screen]
8 - 39 8 - 39
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Monitor items]
Setting value storage Reference section containing
Monitor items
buffer memory address detailed explanation
Transmission sequence status 255H/265H
On-demand execution result 256H/266H
Data transmission result 257H/267H
Data reception result 258H/268H
MC protocol transmission error code 25AH/26AH Chapter 10 of
X00: CH1 Transmission normal completion — User's Manual (Basic)
X01: CH1 Transmission abnormal completion —
X02: CH1 Transmission processing in progress — Sections 3.10 and 3.11 of
X1A: CH1 Global signal — Reference Manual
Y00: CH1 Transmission request —
On-demand Buffer memory head address designation A0H/140H
function
Data length designation A1H/141H
designation
First frame No. designation 1st A9H/149H
On-demand user
First frame No. designation 2nd AAH/14AH Chapter 10 of
frame
Last frame No. designation 1st ABH/14BH User's Manual (Application)
designation
Last frame No. designation 2nd ACH/14CH
Chapter 6 of
Message wait time designation units: 10 ms 11EH/1BEH
User's Manual (Application)
8 - 40 8 - 40
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Purpose]
Monitor the status and setting values of the data transmission using the non
procedure protocol. The test operation for the receive data clear is explained in
Section 8.7.
[Startup procedure]
[Monitor] screen CH Non procedure monitor/test
[Monitor/test screen]
8 - 41 8 - 41
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Monitor/test items]
Setting value storage Reference section containing
Monitor/test items
buffer memory address detailed explanation
Data transmission result 257H/267H Chapter 10 of
Data reception result 258H/268H User's Manual (Basic)
Receive user frame nth 25BH/26BH Chapter 11 of
User frame being transmitted B6H/156H User's Manual (Application)
X00: CH1 Transmission normal completion —
X01: CH1 Transmission abnormal completion —
X02: CH1 Transmission processing in progress —
Chapter 6 of
X03: CH1 Reception data read request —
User's Manual (Basic)
X04: CH1 Reception abnormal detection —
Y00: CH1 Transmission request —
Y01: CH1 Reception data read completion —
Received data count designation A4H/144H Chapter 6 of
Receive complete code designation A5H/145H User's Manual (Basic)
Receive user User frame use enable/disable designation ADH/14DH
frame First frame No. designation 1st to 4th AEH to B1H/14EH to 151H
designation Last frame No. designation 1st to 4th B2H to B5H/152H to 155H
2020H to 2023H/
User frame receive format designation 1st to 4th
2120H to 2123H Chapter 9 of
2024H to 2027H/ User's Manual (Application)
Exclusive format-1 received data count 1st to 4th
2124H to 2127H
Transmission CR/LF output designation B7H/157H
user frame Output head pointer designation B8H/158H
designation Output count designation B9H/159H
Chapter 6 of
Timeout at No-protocol 2014H/2114H
User's Manual (Application)
Chapter 6 of
Receive data clear request A8H/148H
User's Manual (Basic)
8 - 42 8 - 42
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Purpose]
Monitor the status and setting values of the data transmission using the
bidirectional protocol.
[Startup procedure]
[Monitor] screen CH Bidirectional monitor
[Monitor screen]
[Monitor items]
Setting value storage Reference section containing
Monitor items
buffer memory address detailed explanation
Data transmission result 257H/267H Chapter 10 of
Data reception result 258H/268H User's Manual (Basic)
X00: CH1 Transmission normal completion —
X01: CH1 Transmission abnormal completion —
X02: CH1 Transmission processing in progress — Chapter 7 of
X03: CH1 Reception data read request — User's Manual (Basic)
Y00: CH1 Transmission request —
Y01: CH1 Reception data read completion —
Section 7.3 of
Simultaneously transmission data valid/invalid designation 9BH/13BH
User's Manual (Basic)
8 - 43 8 - 43
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Purpose]
Monitor the operating status and setting values of the PLC CPU monitoring
function.
[Startup procedure]
[Monitor] screen CH Monitoring monitor
[Monitor screen]
8 - 44 8 - 44
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Monitor items]
Setting value storage Reference section containing
Monitor items
buffer memory address detailed explanation
PLC CPU Operation status 2204H/2304H
monitoring Execution result 2205H/2305H
function Number of transmission 2206H/2306H
Monitoring condition arrival block No. 2207H/2307H
Cycle time units designation 2040H/2140H
Cycle time designation 2041H/2141H
PLC CPU monitoring function designation 2042H/2142H
PLC CPU monitoring transmission measure designation 2043H/2143H
Transmission pointer 2044H/2144H
Constant cycle
Output count designation 2045H/2145H
transmission
Data No. for connection designation 2046H/2146H
Number of registered word blocks designation 204DH/214DH
Number of registered bit blocks designation 204EH/214EH
PLC CPU abnormal monitoring designation 204FH/214FH
No. n block monitoring device 2050H/2150H to
Monitoring device designation 20A1H/21A1H
2051H-2052H/
2151H-2152H to
Head device No. designation Chapter 2 of
20A1H-20A2H/
User's Manual (Application)
21A1H-21A2H
2053H/2153H to
Read point designation
20A3H/21A3H
Condition agreement transmission 2054H/2154H to
Monitoring condition designation 20A4H/21A4H
2055H/2155H to
Monitoring condition value designation
20A5H/21A5H
2056H/2156H to
Transmission pointer designation
20A6H/21A6H
2057H/2157H to
Output count designation
20A7H/21A7H
2058H/2158H to
Data No. for connection designation
20A8H/21A8H
PLC PCU abnormal monitoring designation
Condition agreement transmission 20E6H/21E6H
Transmission pointer
Number of output designation 20E7H/21E7H
Data No. for connection designation 20E8H/21E8H
8 - 45 8 - 45
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Purpose]
Monitor the setting value of output frame number used when transmitting data
with the non procedure protocol using the user frame.
[Startup procedure]
[Monitor] screen CH Output frame monitor
[Monitor screen]
[Monitor item]
Setting value storage Reference section containing
Monitor item
buffer memory address detailed explanation
BAH to 11DH/ Chapters 9 through 11 of
Output frame No. designation 1st to 100th
15AH to 1BDH User's Manual (Application)
8 - 46 8 - 46
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Purpose]
Monitor the result of access to the flash ROM, the data communication status of
each interface, and the result of the intelligent function module switch settings
using GX Developer.
[Startup procedure]
[Monitor] screen Monitor/test others
[Monitor/test screen]
8 - 47 8 - 47
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
[Monitor/test items]
Setting value storage Reference section containing
Monitor/test items
buffer memory address detailed explanation
Flash ROM access register/read/delete result 4H
Station No. (Switch setting) 200H
Station No. (Instruction setting) 24FH
SD WAIT status 201H … b0
SIO status 201H … b1
PRO. status 201H … b2
P/S status 201H … b3
CH1 C/N status 201H … b4
NAK status 201H … b5
ACK. status 201H … b6
NEU. LED status 201H … b7
ERR. LED status 202H … b15
Communication error clear request for CH1 and to turn LED off 0H
SD WAIT status 202H … b0
SIO status 202H … b1
PRO. status 202H … b2
P/S status 202H … b3 Chapter 10 of
CH2 C/N status 202H … b4 User's Manual (Basic)
NAK status 202H … b5
ACK. status 202H … b6
NEU. LED status 202H … b7
ERR. LED status 202H … b14
Communication error clear request for CH2 and to turn LED off 1H
CH1 Communication protocol setting No. error 203H … b0
CH1 Transmission speed setting error 203H … b1
CH1 Mode switching error of setting change prohibit time 203H … b3
CH2 Communication protocol setting No. error 203H … b4
CH2 Transmission speed setting error 203H … b5
CH2 Mode switching error of setting change prohibit time 203H … b7
Station No. out of range error 203H … b14
Linked operation setting error 203H … b15
Number of registered user frame 204H
Number of registered default registration frames 21EH
Flash ROM system parameters write result 220H
8 - 48 8 - 48
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
8.6.10 Display LED off and communication error information/error code initialization
This section explains how to turn off the display LEDs of the Q series C24 and initialize
its communication error information and error codes.
[Operation procedure]
8 - 49 8 - 49
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
(2) Communication error clear request for CH and to turn LED off on
Monitor/test others screen
This is used to turn off the CH LED of the Q series C24 and to initialize (clear)
the communication error information.
The CH LED on status and communication error information can be confirmed
on the Monitor/test others screen.
[Operation procedure]
8 - 50 8 - 50
8 UTILITY PACKAGE (GX Configurator-SC)
MELSEC-Q
This section explains how to clear the received data using the non procedure protocol.
By using this function, the receive data can be cleared from GX Configurator-SC while
the communication with the non procedure protocol is still in progress, without resetting
the PLC CPU or turning off the power.
[Operation procedure]
(Procedure 1) Display the [Non procedure monitor/test] screen. (See Section 8.6.5.)
(Procedure 2) Set [Clear request issued] for "Receive data clear request".
(Procedure 3) Click on Execute test .
The received data will be cleared.
POINT
Clear the received data when transmission/reception are not in progress with the
external device.
Executing a receive data clear while the data transmission is in progress causes
the Q series C24 to stop the data transmission abruptly, resulting in an abnormal
completion of the dedicated transmission instruction. (The transmission completion
signal will not be lit.)
When the receive data clear is executed while the data reception is in progress, the
data received up to that point will be cleared.
8 - 51 8 - 51
9 DEDICATED INSTRUCTIONS
MELSEC-Q
9 DEDICATED INSTRUCTIONS
Dedicated instructions are used to simplify programming when using intelligent function
module functions.
This chapter describes the dedicated instructions for the Q series C24, which is part of
the functions of the QCPU (in Q mode) explained in this manual.
The following table lists the dedicated instructions explained in this chapter.
Dedicated Explanation
Application Description of function
instruction page
Sends data using the on-demand function of the MC
On-demand function transmission ONDEMAND Section 9.2
protocol.
Non procedure protocol OUTPUT Sends data for the specified data count. Section 9.3
communication INPUT Reads received data. Section 9.4
Bidirectional protocol BIDOUT Sends data for the designated data count. Section 9.5
communication BIDIN Reads received data. Section 9.6
Reads the status of data transmission/reception via a
Communication status confirmation SPBUSY Section 9.7
dedicated instruction.
Perform the receive data clear without stopping the
Receive data clear CSET transmission processing during the non procedure Section 9.8
protocol.
POINT
(1) The user should not change data values (control data, request data, etc.)
designated by a dedicated instruction until the execution of the dedicated
instruction is completed.
(2) Dedicated instructions for the Q series C24 are executed based on the current
setting values stored in the buffer memory when the module is started.
When it is necessary to change a setting value, change the value by GX
Configurator-SC before starting up the module.
Alternatively, a setting value can be changed via the sequence program using
a CSET instruction before starting up the PLC CPU (See the User's Manual
(Application)).
9
1) Area of buffer memory assigned as applicable functions for dedicated
instructions.
2) Setting values for data communication
• Word/byte units designation
• Receive complete code
• Received data count
etc.
9-1 9-1
9 DEDICATED INSTRUCTIONS
MELSEC-Q
The ONDEAMAND instruction transmission data using the on-demand function of the
MC protocol.
Applicable device
MELSECNET/H,
Set Internal device
MELSECNET/10 Special module
data (System, user) File register Index register Zn Constant Others
Direct J \ U \G
Bit Word Bit Word
(S1) — —
(S2) — —
(D) —
[Instruction [Executing
code] condition]
Command
ONDEMAND G.ONDEMAND Un (S1) (S2) (D)
Command
GP.ONDEMAND Un (S1) (S2) (D)
ONDEMAND
The file register per local device and program cannot be used as the set data.
Control data
3
Device Item Set data Setting range Set by
• Set transmission channel
(S1) + 0 Transmission channel 1: Channel 1 (CH1 side) 1, 2 User
2: Channel 2 (CH2 side)
• Result read by an ONDEMAND instruction is stored.
(S1) + 1 Transmission result 0: Normal — System
9 Other than 0: Error code 1
2
(S1) + 2 Transmission data count • Set the transmission data count. 1 or more User
1 For error codes relating to abnormal completion, see Chapter 10 of the User's
Manual (Basic).
2 When setting "Word/byte units designation" by GX Configurator-SC, set the number
of bytes when bytes are designated and set the number of words when words are
designated.
3 The settings are done by either of the following:
• User: Data set by the user before executing the ONDEMAND instructions.
• System: The PLC CPU stores the execution result of the ONDEMAND instructions.
9-2 9-2
9 DEDICATED INSTRUCTIONS
MELSEC-Q
Function
(1) Data stored in the device designated in (S2) and succeeding devices are sent
according to the control data of the device designated in (S1) and succeeding
devices, via the on-demand function of the MC protocol of the module designated in
Un.
QCPU Q series C24 Channel to be
used is set by
b15 to b0 the control data.
(S2)+ 0 Send
+1 Channel 1
+2
Send
Channel 2
(a) Completion device : Turns on at the END processing of the scan where
the ONDEMAND instruction is completed, and turns
off at the next END processing.
9-3 9-3
9 DEDICATED INSTRUCTIONS
MELSEC-Q
Error
(1) When a dedicated instruction is completed abnormally, the abnormal completion
signal, (D)+1, turns on and the error code is stored in the transmission result
(S1)+1.
In case of operation errors, the error flag (SM0) turns on and the error code is
stored in the SD0.
See one of the following manuals according to the error code, and check and
correct the error.
<Error code>
4FFFH or less : QCPU(Q Mode) User's Manual
(Hardware Design, Maintenance and Inspection)
7000H or more: Section 10.2 of the User's Manual (Basic)
Program example
A program that sends data stored in D10 to D11 using an on-demand transmission
When input/output signals of the Q series C24 are from X/Y00 to X/Y1F
Normal completion
Abnormal completion
POINT
(1) The status of communication via dedicated instructions can be read by an
SPBUSY instruction.
(2) Designate the storage capacity of transmission data (stored in D10 to D11 in
the program example above) and data length (stored in D2 in the program
example above) within the range of the buffer memory the user has assigned
for an on-demand function.
9-4 9-4
9 DEDICATED INSTRUCTIONS
MELSEC-Q
This instruction transmission data in any message format specified by the user using
the non procedure protocol.
Applicable device
MELSECNET/H,
Set Internal device
MELSECNET/10 Special module
data (System, user) File register Index register Zn Constant Others
Direct J \ U \G
Bit Word Bit Word
(S1) — —
(S2) — —
(D) —
[Instruction [Executing
code] condition] Command
OUTPUT G.OUTPUT Un (S1) (S2) (D)
Command
GP.OUTPUT Un (S1) (S2) (D)
OUTPUT
The file register per local device and program cannot be used as the set data.
Control data
Device Item Set data Setting range Set by 3
• Set transmission channel
(S1) + 0 Transmission channel 1: Channel 1 (CH1 side) 1, 2 User
2: Channel 2 (CH2 side)
• Transmission result by an OUTPUT instruction
are stored.
(S1) + 1 Transmission result 0: Normal — System
Other than 0: Error code 1
Transmission data 2
(S1) + 2 • Set the transmission data count. 1 or more User
count
1 For error codes relating to abnormal completion, see Chapter 10 of the User's
Manual (Basic).
2 When setting "Word/byte units designation" by GX Configurator-SC, set the number
of bytes when bytes are designated and set the number of words when words are
designated and set the number of words when words are selected as the unit types.
3 The settings are done by either of the following:
• User: Data set by the user before executing the OUTPUT instructions.
• System: The PLC CPU stores the execution result of the OUTPUT instructions.
9-5 9-5
9 DEDICATED INSTRUCTIONS
MELSEC-Q
Function
(1) Data stored in the device designated in (S2) and succeeding devices are sent
according to the control data of the device designated in (S1) and succeeding
devices, via the non procedure protocol of the module specified in Un.
QCPU Q series C24 Channel to be
used is set by
b15 to b0 the control data.
(S2) + 0 Send
+1 Channel 1
+2
Send
Channel 2
(a) Completion device: Turns on at the END processing of the scan where the
OUTPUT instruction is completed, and turns off at the
next END processing.
9-6 9-6
9 DEDICATED INSTRUCTIONS
MELSEC-Q
Error
(1) When a dedicated instruction is completed abnormally, the abnormal completion
signal, (D)+1, turns on and the error code is stored in the transmission result
(S1)+1.
In case of operation errors, the error flag (SM0) turns on and the error code is
stored in the SD0.
See one of the following manuals according to the error code, and check and
correct the error.
<Error code>
4FFFH or less : QCPU(Q Mode) User's Manual
(Hardware Design, Maintenance and Inspection)
7000H or more: Section 10.2 of the User's Manual (Basic)
Program example
The following example shows a program that sends any data stored in D11 to D15
using the non procedure protocol.
When input/output signals of the Q series C24 are from X/Y00 to X/Y1F:
9-7 9-7
9 DEDICATED INSTRUCTIONS
MELSEC-Q
This instruction receives data in any message format specified by the user using the
non procedure protocol.
Applicable device
MELSECNET/H,
Set Internal device
MELSECNET/10 Special module
data (System, user) File register Index register Zn Constant Others
Direct J \ U \G
Bit Word Bit Word
(S) — —
(D1) — —
(D2) —
[Instruction [Executing
code] condition]
Command
INPUT G.INPUT Un (S) (D1) (D2)
The file register per local device and program cannot be used as the set data.
Control data
Device Item Set data Setting range Set by 3
• Set receive channel
(S) + 0 Receive channel 1: Channel 1 (CH1 side) 1, 2 User
2: Channel 2 (CH2 side)
• Reception result by an INPUT instruction are
stored.
(S) + 1 Reception result — System
0: Normal
Other than 0: Error code 1
2
(S) + 2 Receive data count • Receive data count is stored. 0 or more System
Allowable number of • Set the allowable number of words for received
(S) + 3 1 or more User
receive data data that can be stored in (D1).
POINT
(1) The command of G.INPUT cannot be converted into pulse.
(2) G.INPUT should be executed while the read request of the input/output signal
is turned on.
9-8 9-8
9 DEDICATED INSTRUCTIONS
MELSEC-Q
1 For error codes relating to abnormal completion, see Chapter 10 of the User's
Manual (Basic).
2 When setting "Word/byte units designation" by GX Configurator-SC, set the number
of bytes when bytes are designated and set the number of words when words are
designated.
3 The settings are done by either of the following:
• User: Data set by the user before executing the INPUT instructions.
• System: The PLC CPU stores the execution result of the INPUT instructions.
Function
(1) The function stores in the device designated in (D1) and succeeding devices the data
received with the non procedure protocol of the module designated in Un, according
to the control data of the device designated in (S) and succeeding devices.
(3) In case of reading the receive data to the same interface, it cannot be used along
with BUFRCVS instruction (for interrupt programs).
(a) Completion device: Turns on at the END processing of the scan where the
INPUT instruction is completed, and turns off at the next
END processing.
9-9 9-9
9 DEDICATED INSTRUCTIONS
MELSEC-Q
Error
(1) When a dedicated instruction is completed abnormally, the abnormal completion
signal (D2)+1, turns on and the error code is stored in the transmission result
(S1)+1.
In case of operation errors, the error flag (SM0) turns on and the error code is
stored in SD0.
See one of the following manuals according to the error code, and check and
correct the error.
<Error code>
4FFFH or less : QCPU(Q Mode) User's Manual
(Hardware Design, Maintenance and Inspection)
7000H or more: Section 10.2 of the User's Manual (Basic)
Program example
The following example shows a program that stores data received via the non-
procedure protocol in D10 and later.
When the input/output signals of the Q series C24 are from X/Y00 to X/Y1F:
9 - 10 9 - 10
9 DEDICATED INSTRUCTIONS
MELSEC-Q
[Instruction [Executing
code] condition]
Command
BIDOUT G.BIDOUT Un (S1) (S2) (D)
Command
GP.BIDOUT Un (S1) (S2) (D)
BIDOUT
The file register per local device and program cannot be used as the set data.
Control data
Device Item Set data Setting range Set by 3
• Set transmission channel
(S1) + 0 Transmission channel 1: Channel 1 (CH1 side) 1, 2 User
2: Channel 2 (CH2 side)
• Transmission result by a BIDOUT instruction
are stored.
(S1) + 1 Transmission result — System
0: Normal
Other than 0: Error code 1
Transmission data 2
(S1) + 2 • Set the transmission data count. 1 or more User
count
1 For error codes relating to abnormal completion, see Chapter 10 of the User's
Manual (Basic).
2 When setting "Word/byte units designation" by GX Configurator-SC, set the number
of bytes when bytes are designated and set the number of words when words are
designated.
3 The settings are done by either of the following:
• User: Data set by the user before executing the BIDOUT instructions.
• System: The PLC CPU stores the execution result of the BIDOUT instructions.
9 - 11 9 - 11
9 DEDICATED INSTRUCTIONS
MELSEC-Q
Function
(1) The function sends data stored in the device designated in (S2) and succeeding
devices according to the control data of the device designated in (S1) and
succeeding devices, via the bidirectional protocol of the module designated in Un.
Error
(1) When a dedicated instruction is completed abnormally, the abnormal completion
signal (D)+1, turns on and the error code is stored in the transmission result (S1)+1.
In case of operation errors, the error flag (SM0) turns on and the error code is
stored in SD0.
See one of the following manuals according to the error code, and check and
correct the error.
<Error code>
4FFFH or less : QCPU(Q Mode) User's Manual
(Hardware Design, Maintenance and Inspection)
7000H or more: Section 10.2 of the User's Manual (Basic)
9 - 12 9 - 12
9 DEDICATED INSTRUCTIONS
MELSEC-Q
Program example
The following example shows a program that sends any data stored in D11 to D15
using the bidirectional protocol.
When the input/output signals of the Q series C24 are from X/Y00 to X/Y1F:
9 - 13 9 - 13
9 DEDICATED INSTRUCTIONS
MELSEC-Q
[Instruction [Executing
code] condition]
Command
BIDIN G.BIDIN Un (S) (D1) (D2)
Command
GP.BIDIN Un (S) (D1) (D2)
BIDIN
The file register per local device and program cannot be used as the set data.
Control data
Device Item Set data Setting range Set by 2
• Set receive channel
(S) + 0 Receive channel 1: Channel 1 (CH1 side) 1, 2 User
2: Channel 2 (CH2 side)
• Reception result by a BIDIN instruction are
(S) + 1 Reception result stored. — System
0: Normal
1
(S) + 2 Receive data count • The number of data received is stored. 1 or more System
Allowable number of • Set the allowable number of words for received
(S) + 3 1 or more User
receive data data that can be stored in (D1).
POINT
(1) The command of G (P).BIDIN cannot be converted into pulse.
(2) G (P).BIDIN should be executed while the read request of the input/output
signal is turned on.
9 - 14 9 - 14
9 DEDICATED INSTRUCTIONS
MELSEC-Q
Function
(1) The function stores in the device designated in (D1) and succeeding devices the data
received via the bidirectional protocol of the module designated in Un, according to
the control data of the device designated in (S) and succeeding devices.
(3) It cannot be used along with BUFRCVS instruction (for interrupt programs).
(4) Whether a BIDIN instruction was completed normally can be checked by the
completion device ((D2)) or status display device at completion ((D2)+1).
(a) Completion device: Turns on at the END processing of the scan where the
BIDIN instruction is completed normally, and turns off at
the next END processing.
(b) Status display device at completion: Does not change when left off.
BIDIN
instruction
ON
9 - 15 9 - 15
9 DEDICATED INSTRUCTIONS
MELSEC-Q
Error
(1) In case of operation errors, the error flag (SM0) turns on and the error code is
stored in SD0.
See one of the following manuals according to the error code, and check and
correct the error.
<Error code>
4FFFH or less : QCPU(Q Mode) User's Manual
(Hardware Design, Maintenance and Inspection)
Program example
The following example shows a program that receives any data using the bidirectional
protocol and stores that data in D10 or later.
The input/output signals of the Q series C24 are from X/Y00 to X/Y1F:
9 - 16 9 - 16
9 DEDICATED INSTRUCTIONS
MELSEC-Q
This instruction reads the status of data transmission and reception executed with
dedicated instructions.
Applicable device
MELSECNET/H,
Set Internal device
MELSECNET/10 Special module
data (System, user) File register Index register Zn Constant Others
Direct J \ U \G
Bit Word Bit Word
(D) —
[Instruction [Executing
code] condition]
Command
SPBUSY G.SPBUSY Un (D)
Command
GP.SPBUSY Un (D)
SPBUSY
Function
(1) The function reads the execution status of a dedicated instruction directed to a
module designated by the start I/O signal, and stores it in the device designated
by (D) or later.
(2) The execution status is stored in (D) in the form of "1" at the corresponding bit
when the processing of each instruction is started, and "0" when the processing is
completed.
The processing of each instruction is completed when the completion flag of each
instruction is turned from on to off.
b15 to b4 b3b2b1 b0
(D) + 0
Stores the execution status of ONDEMAND, OUTPUT, PRR, and BIDOUT instructions directed to channel 1.
Stores the execution status of INPUT and BIDIN instructions directed to channel 1.
Stores the execution status of ONDEMAND, OUTPUT, PRR, and BIDOUT instructions directed to channel 2.
Stores the execution status of INPUT and BIDIN instructions directed to channel 2.
Stores the execution status of GETE and PUTE instructions.
(D) + 1 0 (Always stores "0".)
(3) The SPBUSY instruction is executed for every scan while the read command is
ON, if the system is executing during ON. And, the instruction will be executed for
a single scan when the read command rises from OFF to ON, if the system is
starting up.
9 - 17 9 - 17
9 DEDICATED INSTRUCTIONS
MELSEC-Q
Error
(1) In case of operation errors, the error flag (SM0) turns on and the error code is
stored in SD0.
See one of the following manuals according to the error code, and check and
correct the error.
<Error code>
4FFFH or less : QCPU(Q Mode) User's Manual
(Hardware Design, Maintenance and Inspection)
7000H or more: Section 10.2 of the User's Manual (Basic)
Program example
A program that reads the communication status of a target module.
When input/output signals of the Q series C24 are from X/Y00 to X/Y1F
9 - 18 9 - 18
9 DEDICATED INSTRUCTIONS
MELSEC-Q
Applicable device
MELSECNET/H,
Set Internal device
MELSECNET/10 Special module
data (System, user) File register Index register Zn Constant Others
Direct J \ U \G
Bit Word Bit Word
(S1) — — K, H —
(S2) — —
(D1) — —
(D2) —
Each of file registers for local device and program cannot be used as the setting data.
Control data
Device Item Set data Setting range Set by
(S2) + 0 Execution type Select 0. 0 User
The execution result at the completion of the instruction
is stored.
(S2) + 1 Complete status — System
0: Normal
Other than 0: Abnormal (error code)
Specify the request.
(S2) + 2 Request type 4 User
4: Receive data clear request
(S2) + 3
to For system — — System
(S2) + 111
REMARK
(1) See the "Error" explanation on the following page for details on errors caused by
wrong data specifications by the user.
(2) The setting sides are partitioned as follows:
• User: Data set by the user before executing the dedicated instruction.
• System: The PLC CPU stores the execution result of the dedicated instruction.
9 - 19 9 - 19
9 DEDICATED INSTRUCTIONS
MELSEC-Q
Function
(1) This function clears reception data in the OS area. It does not clear the user data
reception area in the buffer memory.
(2) If the CSET instruction is executed while the read request (X03/X0A) or reception
abnormal detection signal (X04/X0B) is turned on, the CSET instruction is kept
waiting until the signal is turned off.
(3) The status of the CSET instruction, whether it is being executed or completed
normally/abnormally, can be checked by the complete device (D2) specified by
the setting data.
(a) Complete device ((D2) + 0)
This device turns on at the End processing of the scan at which the CSET
instruction is completed and turns off at the next End processing.
Complete device
Error
(1) If the dedicated instruction is abnormally completed, the error flag (SM0) turns on
and the error code is stored in SD0.
See the following manuals according to the error code, and check/take action
according to the error.
<Error code>
4FFFH or less : QCPU User's Manual
(Hardware Design, Maintenance and Inspection)
7000H or more: Section 10.2 of the User's Manual (Basic)
9 - 20 9 - 20
9 DEDICATED INSTRUCTIONS
MELSEC-Q
Program example
This is an example of a program that clears reception data on the Q series C24 side.
It is assumed that the input/output signals of the Q series C24 are X/Y00 to X/Y1F.
Abnomal completion
9 - 21 9 - 21
10 TROUBLESHOOTING
MELSEC-Q
10 TROUBLESHOOTING
This chapter explains the definitions of errors that may occur during data
communication between the Q series C24 and external devices, and the corrective
actions.
10.1.1 Checking the LED ON status, communications error status, and switch setting status
of the serial communication module
This section explains how to check the status of communication between the Q series
C24 and external devices, the transmission status of the Q series C24, and the switch
setting status of the Q series C24.
When a communication problem occurs, check the error status using one of the
following procedures:
(1) Checking the module status and error codes in the detailed module
information screen of the GX Developer diagnostic functions
[Startup procedure]
GX Developer [Diagnostics] [System monitor]
Module's Detailed Information
10
10 - 1 10 - 1
10 TROUBLESHOOTING
MELSEC-Q
[Displays]
• Module
The following information is displayed:
Module name : The name of the module installed
I/O Address : The start input/output signal (number) of the target
module
Implementation Position: The slot position where the module is mounted
Product information : Product information
The last character of the product information
indicates the function version of the module.
(Example) If the last character is "B," it means
that the module is of function
version B.
• Unit access (Module access)
Displays access permissions when the Ready signal (X1E) is turned on and
the WDT error signal (X1F) is turned off.
• Status of I/O Address Verify
Displays whether or not the module for which the user set the parameters
matches the module installed.
• Remote password setting status
Displays the setting status of the remote password.
• Present Error
Displays the error code of the latest error occurrence.
• Error Display
Displays the error codes for any errors that have occurred in any of the
functions being used.
• Error details, corrective action
Displays the error details and corrective action for the error code selected in
Error Display.
10
10 - 2 10 - 2
10 TROUBLESHOOTING
MELSEC-Q
[Displays]
1) H/W LED Information Right side (Left side: CH1 information/
Right side: CH2 information)
Displays the transmission status and the communications error status
of the Q series C24.
(Displays 201H/202H of the buffer memory.)
b15 to b8 b7 b6 b5 b4 b3 b2 b1 b0
Buffer memory address 201H 1/0 1/0 1/0 1/0 1/0 1/0 1/0 1/0 (Information of CH1 side)
10 - 3 10 - 3
10 TROUBLESHOOTING
MELSEC-Q
10 - 4 10 - 4
10 TROUBLESHOOTING
MELSEC-Q
(b) The initial status of the LED ON and communications error indicates the
status when the Q series C24 starts up by turning on the power or resetting
the PLC CPU.
(c) Each of the communications error status, C/N to SIO, CH1 ERR. and CH2
ERR., turns on when an error occurs, and keeps its on-status even after the
communication returns to normal.
The PLC CPU can check the aforementioned LED ON status and
communications error status, and initialize any error information using
read/write to the buffer memory of the Q series C24 and input/output signals.
Initialize the error information according to Section 10.1.2.
(e) SD WAIT turns on when data cannot be sent to the external device by the
transmission control of the Q series C24 (waiting for data transmission).
• When transmission cannot be started.
• When a transmission pause request is received during data transmission.
(DSR signal is off, reception by DC3)
SD WAIT turns off when transmission becomes possible and data
transmission is started/resumed.
10 - 5 10 - 5
10 TROUBLESHOOTING
MELSEC-Q
This section explains the ERR. LED ON factors and the error code initialization (clear)
for the Q series C24.
(2) Turning off the ERR. LED and initializing the error codes by GX
Configurator-SC (Refer to Section 8.6.10)
(a) When turning off the ERR. LED and initializing the error codes
By making the CH ERR. clear request on the "Monitor/Test" screen, the
ERR. LED of the Q series C24 turns off and the stored error codes are
initialized.
(b) When initializing the communication error information
By making the Communication error clear request for CH and to turn LED
off on the "Monitor/test others" screen, the LEDs (ERR., NEU.) of the Q
series C24 turn off and the communication error information is initialized.
(3) Turning off the ERR. LED and initializing the error codes by
sequence program
(a) Input signals used to notify of error occurrences and output signals used to
initialize the error code
I/O signal Name of status information Description/function
XE Error occurrence on CH1 side Turns on upon error occurrence in CH1 interface.
Input signal
XF Error occurrence on CH2 side Turns on upon error occurrence in CH2 interface.
YE CH1 Error information initialization request Turns on when initializing error code of interface on CH1 side.
Output signal
YF CH2 Error information initialization request Turns on when initializing error code of interface on CH2 side.
10 - 6 10 - 6
10 TROUBLESHOOTING
MELSEC-Q
POINT
(1) Initialization requests are valid only when write operation is performed.
The initialization requests clear all data in the LED ON and communication
error information storage area (201H to 202H) at the same time.
Furthermore, when initialization of error information on the CH1 and CH2 sides
is requested, XE and XF also turn off.
(2) Data written to the buffer memory address 0H to 1H is cleared after initialization
processing.
(3) If errors persist even after completion of the initialization processing, the
corresponding communication error information is stored again and the
corresponding bit in the LED ON and communications error status storage
area (201H to 202H) turns on (1).
10 - 7 10 - 7
10 TROUBLESHOOTING
MELSEC-Q
(c) Examples of programs that initialize displayed LED and communication error
information
The following shows examples of a program that reads error codes when
errors described in (1) above occur in an interface on the CH1 side and
initializes the displayed LED and communication error information.
Incorporate the necessary part of the program.
(Input/output signals X/Y00 to X/Y1F of the Q series C24)
Check the error codes and take corrective action according to Section 10.2.
Check the error codes and take corrective action according to Section 10.2.
REMARK
When data is communicated using the MC protocol, the displayed ERR. LED may
not be turned on if the Q series C24 sends an NAK message to the external device
in response to the command message.
Error codes (see Section 10.2) corresponding to the error content when the NAK
message is sent back to the external device are stored in the following areas. (when
communicating with an A compatible 1C frame, the error codes differ from the
transmission error code.)
When checking error codes transmitted by the PLC CPU, incorporate the following
program (in case of the interface on the CH1 side).
Read command
Reads transmission error codes from address 25AH.
Check the error codes and take corrective action according to Section 10.2.
10 - 8 10 - 8
10 TROUBLESHOOTING
MELSEC-Q
This section explains how to read the control signal status stored in the buffer memory
during communication using RS-232 interface.
When GX Configurator-SC is used, check the status using the "Transmission control
and others monitor/test" screen (see Section 8.6.3).
When a transmission problem occurs, read operation is executed to check the signal
on/off status of the RS-232 interface.
(1) RS-232 control signal status storage area (address: 254H, 264H)
The status of the RS-232 signals is stored in buffer memory addresses 254H and
264H as follows:
b15 to b6 b5 b4 b3 b2 b1 b0
Buffer memory address 254H 0 1/0 1/0 1/0 1/0 1/0 1/0 (Information on CH1 side)
264H 0 1/0 1/0 1/0 1/0 1/0 1/0 (Information on CH2 side)
1 : ON RS
0 : OFF
DSR
DTR
CD
System area for QJ71C24 (-R2) CS
RI
REMARK
(1) For more details on signals for RS-232, see Section 3.2.1.
(2) Signals output from the Q series C24 side (RTS and DTR) are controlled by the
operating system (OS) of the Q series C24.
They cannot be directly controlled by the sequence program.
(3) There is a maximum delay of 100 ms in signal status stored in the buffer
memory above.
(2) Example of a program that reads from RS-232 control signal status
storage area
The following shows an example of a program that reads the RS-232 control
signal status.
(input/output signals X/Y00 to X/Y1F of the Q series C24)
b15 to b6 b5 b4 b3 b2 b1 b0
D0 0 0 0 1 1 1 DTR signal: ON, DSR signal: ON, RTS signal: ON
D1 0 0 1 1 1 0 CD signal: ON, DTR signal: ON, DSR signal: ON
10 - 9 10 - 9
10 TROUBLESHOOTING
MELSEC-Q
This section explains how to read the current status of the data communication using
the MC protocol stored in the buffer memory.
When GX Configurator-SC is used, check the status using the "MC protocol monitor"
screen (see Section 8.6.4).
When a transmission problem occurs, read operation is executed to check the status
of the data communication using the MC protocol.
(1) Transmission sequence status storage area (address: 255H and 265H)
The status of data communication using the MC protocol is stored as a numerical
value in buffer memory addresses 255H and 265H.
b15 to b0
Buffer memory address 255H 0 to 9 (Information on the CH1 side)
265H 0 to 9 (Information on the CH2 side)
The following shows the correspondence between the numerical values in the
transmission sequence status storage area and the data communication status.
Request from an external device
number HL
E Message wait
Station
External N
device Q
ACK
or
NAK
Request
Q series C24 to CPU
Response
from
CPU
"6" "1"..."6" is repeated afterward.
Stored 0 1 3 4 5 6
value 2 Values 7 to 9 are stored when "mode switching" or "initialization
of transmission sequence" is performed.
REMARK
When the target interface is not set to use the MC protocol, "0" is stored in the
transmission sequence status storage area.
b15 to b0
The CH1 side is waiting to receive a command message,
D0 0 and is using non procedure or bidirectional protocol.
D1 4 CH2 is accessing the PLC CPU upon reception of a
command message.
10 - 10 10 - 10
10 TROUBLESHOOTING
MELSEC-Q
This section explains how to read the switch setting status of the Q series C24.
When GX Configurator-SC is used, check the status in the "Monitor/test others" screen
(see Section 8.6.9).
REMARK
(1) The switch settings can be changed when the mode is switched or when the
UINI instruction is executed. (The station No. setting can be changed only when
the UINI instruction is executed.)
For the mode switching, refer to Chapter 15 of the User's Manual (Application).
For the UINI instruction, refer to Chapter 17 of the User's Manual (Application).
(2) For the switch settings, refer to Section 4.5.
261H 0 0 0 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 (Information on the CH2 side)
10 - 11 10 - 11
10 TROUBLESHOOTING
MELSEC-Q
(2) Example of a program that reads from the setting status storage
area
The following shows an example of a program that reads the setting of various
switches of the Q series C24 from the setting status storage area.
For details on XE and XF of the input/output signals used in the program, see
Section 10.1.2 (3).
(input/output signals X/Y00 to X/Y1F of the Q series C24)
b15b14b13b12 b11b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0
D0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 Error description (1: Communication protocol number setting error)
D1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Setting station number of the Q series C24 (0).
D2 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 1 Communication protocol setting number (9).
CH1 side
D3 0 0 0 0 0 1 0 1 0 0 0 0 1 0 1 0 (transmission setting description)
D4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 Communication protocol setting number (1).
CH2 side
D5 0 0 0 0 0 1 0 1 0 1 1 0 1 0 1 0 (transmission setting description)
Displays communication protocol number setting error status on the CH1 side
10 - 12 10 - 12
10 TROUBLESHOOTING
MELSEC-Q
This section explains how to read the current operation status of the Q series C24.
When GX Configurator-SC is used, check the status in the "Transmission control and
others monitor/test" screen (see Section 8.6.3).
REMARK
• The status of the switch settings by GX Developer can be checked by performing
read operations as described in Section 10.1.5.
• Refer to Section 4.5 for the switch settings.
263H 0 0 0 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 (Information on the CH2 side)
10 - 13 10 - 13
10 TROUBLESHOOTING
MELSEC-Q
(2) Example of a program that reads from the current setting status
storage area
The following shows an example of a program that reads from the switch setting
status storage area for current operation of the Q series C24.
For details regarding XE and XF of the input/output signals used in the program,
see Section 10.1.2 (3).
(input/output signals X/Y00 to X/Y1F of the Q series C24)
While the CH1 side is set to the non procedure protocol and the CH2 side is set to the MC protocol (format 1),
this indicates the communication rate setting error on the CH1 side.
10 - 14 10 - 14
10 TROUBLESHOOTING
MELSEC-Q
The following shows the error codes, error contents, and corrective action for errors
that are generated during communication between the Q series C24 and an external
device.
The signal name in the following table indicates the CH side LED on status or
communication error status that is stored into buffer memory address 201H/202H when
an error occurs.
The CH side LED on status and communication error status can be confirmed by GX
Developer's System monitor or GX Configurator-SC. (Refer to Section 10.1.1.)
For errors without a corresponding signal name entered to errors generated with the
MC protocol communication, “NAK” comes on.
The following shows the error codes, error contents, and corrective action for errors
generated during communication using MC protocol (excluding A compatible 1C
frame), non procedure protocol, and bidirectional protocol.
(" " in the table is the error code when the target CPU is not a Q/QnACPU.)
Protocol
Error code
Signal Non
(Hexa- Error Error Contents Corrective action Bidire-
name MC Proce-
decimal) ctional
dure
• See Troubleshooting of the
3E8H
QCPU (Q mode) maintenance
to — (Error detected by the CPU) —
and inspection user's manual
3FFFH
and take corrective action.
• See Appendix of the QCPU (Q
4000H mode) maintenance and
to — (Error detected by the CPU) — inspection user's manual
4FFFH (details) and take corrective
action.
7101H
System error • The OS of the Q series C24 detected some error. — ( 1)
7102H
• Make the watchdog timer (timer
1) time longer.
7103H PLC access error • Cannot communicate with the Q series C24 CPU. C/N • Check if the CPU can
communicate in communication
protocol No. "F".
7104H
to System error • The OS of the Q series C24 detected some error. — ( 1)
7116H
• Number of request points exceeds the range for the
command.
• A word device was designated in a bit units • Check and correct the external
7140H Request data error command. PRO device transmit message and
• The last device No. exceeds the range. restart data communications.
Given device last No. > Designated head device
No. + Designated number of points
7141H System error • The OS of the Q series C24 detected some error. — ( 1)
• Check and correct the external
• A device that cannot be designated by the given
7142H Device name error PRO device transmit message and
command was designated.
restart data communications.
• Check and correct the external
7143H Device No. error • The head device No. is out of range. PRO device transmit message and
restart data communications.
Monitor data write • Monitoring was requested before the device to be • Write the device to be monitored
7144H PRO
error monitored was written. before issuing a monitor request.
Monitor PLC No. • The written PLC No. and PLC No. in the monitor
7145H C/N • Rewrite the monitor data.
error request are different.
Monitor CPU model • The written CPU model name and the CPU monitor
7146H C/N • Rewrite the monitor data.
name error name in the monitor request are different.
Written number of • Check and correct the external
• The written number of monitoring points exceeds
7147H monitoring points PRO device transmit message and
the designated range.
overrun error restart data communications.
10 - 15 10 - 15
10 TROUBLESHOOTING
MELSEC-Q
Protocol
Error code
Signal Non
(Hexa- Error Error Contents name Corrective action Bidire-
MC Proce-
decimal) ctional
dure
• A nonexistent extension file register block No. was
designated. • Correct the designated block
Extension R block
7148H • A block No. being used as an extension comment PRO No. and restart data
No. error
area, sampling trace area, or status latch area was communications.
designated.
7149H System error • The OS of the Q series C24 detected some error. — ( 1)
• Change the setting to "Enable
• A write command was designated when "Disable
Cannot execute a write during RUN" and restart
write during RUN" was set.
714AH command during C/N data communications.
• Parameter or sequence program was written during
RUN • Stop the CPU and restart data
RUN.
communications.
714BH
to System error • The OS of the Q series C24 detected some error. — ( 1)
714DH
• Check and correct the other
Monitor network • The written monitor network No. and the monitor station access valid module No.
714EH C/N
No. error request network No. are different. in the network parameters.
• Rewrite the monitor data.
7150H System error • The OS of the Q series C24 detected some error. — ( 1)
• Check and correct the external
PLC No. • A PLC No. other than "FF" or "0 to 64(00H to 40H)"
7151H C/N device transmit message and
designation error was designated.
restart data communications.
7152H System error • The OS of the Q series C24 detected some error. — ( 1)
• Review the transmission
message.
• The received message length has exceeded the CHn
7153H Frame length error • Correct the message format so
allowable range. ERR.
the number of access points is
within the allowable range.
7154H System error • The OS of the Q series C24 detected some error. — ( 1)
• Write the device to be monitored
Unwritten monitor • Monitoring was requested before monitor data was
7155H PRO before issuing a monitor
data error written.
request.
7156H System error • The OS of the Q series C24 detected some error. — ( 1)
• If there is an error in the CPU,
7160H PLC access error • CPU model name cannot be confirmed. C/N remove the CPU error and
restart data communications.
7161H
to System error • The OS of the Q series C24 detected some error. — ( 1)
7163H
• Check the transmission
message/request from the
• Either the request or the device designation method
7164H Request error external device, make the
is wrong.
necessary corrections, and send
again.
7166H System error • The OS of the Q series C24 detected some error. — ( 1)
• Change the setting to "Enable
• A write command was designated when "Disable
7167H Cannot execute a C/N write during RUN" and restart
write during RUN" was set.
command during data communications.
RUN • A command that cannot be executed during RUN • Stop the CPU and restart data
7168H C/N
was designated. communications.
• If there is an error in the CPU,
7169H CPU error • Cannot communicate normally with the CPU. C/N remove the CPU error and
restart data communications.
716AH
to System error • The OS of the Q series C24 detected some error. — ( 1)
716CH
• Monitor data was not written using QnA compatible
716DH PRO
Monitor data write 2C/3C/4C frame.
• Rewrite monitor data.
error • Monitor data was not written using A compatible 1C
716EH PRO
frame.
10 - 16 10 - 16
10 TROUBLESHOOTING
MELSEC-Q
Protocol
Error code
Signal Non
(Hexa- Error Error Contents Corrective action Bidire-
name MC Proce-
decimal) ctional
dure
• A nonexistent device was designated. • Check and correct the external
716FH Device error • Device that cannot be specified by the PRO device transmit message and
corresponding command was designated. restart data communications.
10 - 17 10 - 17
10 TROUBLESHOOTING
MELSEC-Q
Protocol
Error code
Signal Non
(Hexa- Error Error Contents Corrective action Bidire-
name MC Proce-
decimal) ctional
dure
• Change the write destination to
User frame an unwritten frame No.
7E52H • A written frame No. overwrite request was issued. PRO
overwrite error • When overwriting, delete the
given No. beforehand.
• A nonexistent command was designated in a
• Check and correct the external
User frame access subcommand.
7E53H PRO device transmit message and
data error • Byte count exceeding the number of bytes that can
restart data communications.
be requested was designated.
• Flash ROM write allow/prohibit designation from GX
• Set to ON at GX Configurator-
Modification Configurator-SC is set to OFF.
7E54H PRO SC.
allowed error • At the switch setting on GX Developer, modification
• Set to ON at GX Developer.
allowed switch was set to OFF.
• Check and correct the external
User frame data
7E55H • There is an error in the user frame variable data. PRO device transmit message and
error
restart data communications.
7E56H System error • The OS of the Q series C24 detected some error. — ( 1)
• Re-execute the write operation.
Flash ROM write
7E57H • Cannot write to Flash ROM normally. PRO If the error is generated again,
error
replace the module.
• Check and correct the contents
of the external device transmit
• There was an error in the mode No. or transmission
Mode modification message and restart data
7E58H specification designated contents when changing PRO
error communications.
the mode.
• Recheck the switch setting on
the Q series C24.
• Review the program.
Flash ROM write • Rewrite the flash ROM area
7E59H count over limit • Flash ROM written 1,000 times — (address: 2401H) of the buffer
error memory to 0 and restart data
communications.
I/O number error
• Correct the I/O number of the
7E5F H on requested • I/O number of requested module is incorrect. —
module to which data is sent.
module
Device monitoring • Cancel the PLC CPU monitoring
• PLC CPU monitoring registration was performed
7E60 H duplicate — and perform the PLC CPU
twice.
registration error monitoring registration again.
Cycle time units • Correct the setting value of the
7E61 H • Setting value of cycle time units is out of range. —
range error cycle time units.
PLC CPU
• Setting value of PLC CPU monitoring function is out • Correct the setting value of the
7E62 H monitoring function —
of range. PLC CPU monitoring function.
error
Transmission
• Setting of transmission measure of the PLC CPU • Correct the setting value of the
7E63 H measure setting —
monitoring is incorrect. transmission measure.
error
Registration point • Correct the setting value of the
7E64 H • Registration point (word/bit) is out of range. —
range error registration point (word/byte)
PLC CPU abnormal
• Setting value of the PLC CPU abnormal monitoring • Correct the setting value of the
7E65 H monitoring number —
is out of range. PLC CPU abnormal monitoring.
error
Monitoring
• Setting value of transmission condition is out of • Correct the setting value of the
7E66 H condition error of —
range. transmission condition.
monitoring device
CPU abnormal • Correct the setting value (fixed
• Setting value (fixed value) of CPU abnormal
7E67 H monitoring setting — value) of the CPU abnormal
monitoring is out of range.
value error monitoring.
Transmission • Correct the setting value of the
condition range • Setting value of transmission condition (condition transmission condition
7E68H —
error of monitoring agreement transmission) is out of range. (condition agreement
device transmission).
CPU abnormal • Correct the setting value (fixed
• Setting value (fixed value) of CPU abnormal
7E69H monitoring setting — value) of the CPU abnormal
monitoring is out of range.
value error monitoring.
10 - 18 10 - 18
10 TROUBLESHOOTING
MELSEC-Q
Protocol
Error code
Signal Non
(Hexa- Error Error Contents Corrective action Bidire-
name MC Proce-
decimal) ctional
dure
Monitoring device • Correct the setting value of the
7E6AH read point range • Read point of monitoring device is out of range. — read point of the monitoring
error device.
7E6BH CPU abnormal — • Correct the setting value (fixed
• Setting value (fixed value) of CPU abnormal
7E6CH monitoring setting — value) of the CPU abnormal
monitoring is out of range.
7E6DH value error — monitoring.
7E6EH System error • The OS of the Q series C24 detected some error. — ( 1)
Modem connection • Correct the CH to which
7E6FH • Modem is connected to an incorrect channel. —
error notification is sent.
• If there is an error in the CPU,
• The communication with the CPU could not be
7E70H CPU error C/N eliminate the error on the CPU
performed normally.
side and communicate again.
7E81H
to
7E8EH System error • The OS of the Q series C24 detected some error. — ( 1)
7EC1H
7EC2H
Double send • A send request was performed while another send • Interlock (handshake) the send
7EC3H
request error request was being processed. requests.
• Make the transmission data
count smaller than the transmit
buffer size.
Transmission data
• Make the non procedure
count error • Data larger than the transmit buffer size was
protocol transmit buffer size
7EC4H Transmission/ transmitted.
larger.
receipt buffer • Transmission/receipt buffer settings out of range.
• Designate the first address and
setting error
size of transmission/receipt
buffer in the free area range of
the user.
• When writing to Flash ROM, set
• Write to Flash ROM was requested when the setting
Flash ROM access switch shown left of the given
7EC5H modification enable/disable switch in the GX
error interface to ON and restart the
Developer was set to OFF.
Q series C24.
• Check the read/write request
Flash ROM access • There is an error in the Flash ROM read/write
7EC6H data and designate the correct
error request contents.
data.
7F00H System error • The OS of the Q series C24 detected some error. — ( 1)
• Increase the transmission time
• The next data was received before processing of the
by performing handshake with
previous data was completed.
7F01H Buffer full error the external device, etc.
• Multiple requests was simultaneously issued for one • Perform handshake with the
channel. request source external device.
7F02H
to System error • The OS of the Q series C24 detected some error. — ( 1)
7F06H
• Check and correct the external
• An ASCII code that cannot be converted to binary
device transmit message and
code was received.
restart data communications.
ASCII BIN
7F20 H PRO • When communicating using
conversion error • An odd number of bytes of data was received during
ASCII BIN conversion,
data communications using ASCII BIN
always transmit the data in even
conversion. number bytes units.
• There is an error in the command (frame) part. • Check and correct the external
Receive header
7F21 H PRO device transmit message and
area error • An ASCII code that cannot be converted to binary
restart data communications.
code was received.
• Check and correct the external
• A nonexistent command or device was designated.
7F22 H Command error PRO device transmit message and
• The remote password length is wrong.
restart data communications.
• Check and correct the external
MC protocol • There is no data (ETX, CR-LF, etc.) following the
7F23 H PRO device transmit message and
message error character area, or designation was incorrect.
restart data communications.
10 - 19 10 - 19
10 TROUBLESHOOTING
MELSEC-Q
Protocol
Error code
Signal Non
(Hexa- Error Error Contents Corrective action Bidire-
name MC Proce-
decimal) ctional
dure
• The sum check calculated by the Q series C24 and • Recheck the external device
7F24 H Sum check error P/S
the received sum check are not the same. sum check.
• Correct the "data length" that is
transmitted from the external
device.
• The length of the received data exceeds the receive CHn • Change the "word/byte units"
7F25 H Data length error
area size. ERR. set by the Q series C24 to byte
units.
• Increase the receiving area of
the Q series C24.
• Perform the communication
• Another command was received before an unlock CHn
7F26 H Command error after the unlock processing is
processing while the remote password is registered. ERR.
normally completed.
7F30H System error • The OS of the Q series C24 detected some error. — ( 1)
• Process by agreement with the
external device.
• When necessary, change the
Simultaneous • The Q series C24 and an external device started
7F31H simultaneous transmission data
transmission error transmitting simultaneously. valid/invalid designation setting
by GX Configurator-SC. (buffer
memory addresses 9BH/13BH)
7F32H System error • The OS of the Q series C24 detected some error. — ( 1)
• Check if data was dropped from
• No reception watchdog timer (timer 0) time-out the receive data.
7F40H PRO
occurred. • Check if DTR control, etc.
interrupted reception.
• Check the status of the
Time-out error • Response watchdog timer (timer 1) time-out message transmission
7F41H
occurred. destination and restart data
communications, as required.
• Transmit watchdog timer (timer 2) time-out • Check if DTR control, etc.
7F42H
occurred. interrupted transmission.
7F50H
to
7F54H
System error • The OS of the Q series C24 detected some error. — ( 1)
7F60H
to
7F66H
• Decrease the data transmission
rate and restart data
communications.
• Check whether a temporary stop
• The Q series C24 received the next data before it has occurred in the station in
7F67H Overrun error SIO
completed receive processing of the previous data. which the Q series C24 is
installed. (For the QCPU this can
be checked using special register
SD1005.) If a temporary stop has
occurred, remove its cause.
• Match the Q series C24 and
external device settings.
• Clear the error information
according to the error
information initialization request
(YE/YF).
• Data does not match the stop bit setting. In addition, when
• A malfunction occurred in the network because the communicating data with the
power source of the partner station was on or off. non procedure protocol, execute
7F68H Framing error SIO
• Noise occurs in the network. the INPUT instruction, and read
• When the multidrop was connected, data was and discard the unnecessary
transmitted simultaneously by multiple devices. data.
• Measure the noise.
• When connecting the multidrop,
remove the interlock so that
data will not be transmitted
simultaneously by multiple
devices.
10 - 20 10 - 20
10 TROUBLESHOOTING
MELSEC-Q
Protocol
Error code
Signal Non
(Hexa- Error Error Contents Corrective action Bidire-
name MC Proce-
decimal) ctional
dure
• Match the Q series C24 and
external device settings.
• Clear the error information
according to the error
information initialization request
(YE/YF).
• Data does not match the parity bit setting. In addition, when
• A malfunction occurred in the network because the communicating data with the
power source of the partner station was on or off. non procedure protocol, execute
7F69H Parity error P/S
• Noise occurs in the network. the INPUT instruction, and read
• When the multidrop was connected, data was and discard the unnecessary
transmitted simultaneously by multiple devices. data.
• Measure the noise.
• When connecting the multidrop,
remove the interlock so that
data will not be transmitted
simultaneously by multiple
devices.
• Use DTR and DC control and
perform data communications
so that the buffer does not
become full. (Perform RS ⋅ CS
• OS receive buffer overflowed and receive data was
7F6AH Buffer full error SIO control when the modem
skipped. function is used.)
• If the Read Request signal was
turned ON, execute read
immediately.
• Recheck the CD signal control
of the external device.
CD signal control • Data was received when CD signal is OFF when CHn
7F6BH (Send while the CD signal is ON.)
error "CD terminal check enabled" was designated. ERR.
• Set "no CD terminal checking"
and perform communication.
• Transmit data after line
• Data cannot be sent because the line is not CHn connection processing on the
7F6CH Transmission error
connected. ERR. interface side that uses the
modem function.
7F91H
to
7F96H
7F98H
to
7F9AH
7F9DH
7F9EH
7FA0H
to
7FA3H
7FA8H
7FAAH
System error • The OS of the Q series C24 detected some error. — ( 1)
to
7FADH
7FAFH
to
7FB2H
7FB5H
7FB6H
7FB8H
to
7FBCH
7FC0H
to
7FC4H
10 - 21 10 - 21
10 TROUBLESHOOTING
MELSEC-Q
Protocol
Error code
Signal Non
(Hexa- Error Error Contents Corrective action Bidire-
name MC Proce-
decimal) ctional
dure
7FC9H
to System error • The OS of the Q series C24 detected some error. ( 1)
7FCFH
• Check the remote password and
7FE6H • Remote passwords do not match.
communicate again.
• A remote password processing
• The remote password is not registered. command is not necessary
• The remote password processing command was when a remote password is not
registered.
received on the interface side where the modem
CHn • Perform a remote password
7FE7H function is not used.
Processing ERR. unlock processing through GX
• The GX Developer connection is selected in the Developer. Alternatively, change
disabled
communication protocol setting on the the communication protocol
corresponding CH. setting of the corresponding CH
to the MC protocol.
• Clear the storage area of the
• The number of remote password disagreements
CHn cumulative number of abnormal
7FE8H exceeded the value designated at the address
ERR. completions of unlock processing
200D H. (address: 22FC H) to 0.
• Write CPU to the parameter and
• There is an error in the switch setting by the GX CHn
7FEFH Switch setting error reboot after correcting the
Developer ERR. setting value for the switch.
Dedicated
instructions • Do not use dedicated
7FF0H • Executed dedicated instructions simultaneously.
simultaneous instructions simultaneously.
execution error
• Setting value is incorrect. • Correct the setting value in the
7FF1H Control data error
• Setting value is out of range. control data.
Communication
• Instruction cannot be executed with the current • Correct the setting value of the
7FF2H protocol setting
communication protocol. communication protocol.
error
7FF3H
to System error • The OS of the Q series C24 detected some error. — ( 1)
7FF4H
Processing
canceled due to
• The processing was canceled due to mode • Do not execute mode
mode
7FF5H switching or receive data clear executed during the switching/receive data clear
switching/transmiss
processing. during any processing.
ion sequence
initialization
• Multiple external devices must
Simultaneous • Multiple external devices accessed a remote station not access a remote station on
7FF7H
access error on the same network at the same time. the same network at the same
time.
7FF8H
System error • The OS of the Q series C24 detected some error. — ( 1)
7FFFH
• Take corrective action by
B000H
referring to the CC-Link
to • Errors detected by the CC-Link module —
Master/Local Module User's
BFFFH Manual.
C000H • Take corrective action by
to • Errors detected by the Ethernet module — referring to the Ethernet
CFFFH Interface Module User's Manual.
• Take corrective action by referring
F000H
• Errors detected by the MELSECNET/H, to MELSECNET/H,
to
MELSECNET/10 network system MELSECNET/10 network system
FFFFH reference manual.
10 - 22 10 - 22
10 TROUBLESHOOTING
MELSEC-Q
10 - 23 10 - 23
10 TROUBLESHOOTING
MELSEC-Q
The following table lists the error code, error contents, and corrective action for errors
generated during A compatible 1C frame communications.
Protocol
Error code
Signal Non
(Hexa- Error Error Contents Corrective action Bidire-
name MC Proce-
decimal) ctional
dure
• Change the setting to "Enable
• A write command was designated when "Disable
write during RUN" and restart
Disable during write during RUN" was set.
00H C/N data communications.
RUN • Parameter or sequence program was written during
• Stop the CPU and restart data
RUN.
communications.
• Match the Q series C24 and
01H Parity error • The data does not match the parity bit setting. P/S
external device settings.
• The sum check calculated by the Q series C24 and • Check the external device sum
02H Sum check error P/S
the transmitted sum check are not the same. check.
• Check and correct the external
• Received message that is different from the control
03H Protocol error PRO device transmit message and
procedure with the communication protocol setting.
restart data communications.
• Match the Q series C24 and
04H Framing error • The data does not match the stop bit setting. SIO
external device settings.
• The next data was received before the Q series C24 • Decrease the transmission rate
05H Overrun error SIO
received all the preceding data. and restart data communications.
• Designation method error in part of a message.
• A command that does not exist was designated.
Character area • Check and correct the external
06H • The number of processing points is outside the PRO
error device transmit message and
range for the command.
restart data transmission.
• A device that does not exist was designated.
07H Character error • Received data that cannot be used. PRO
• Replace the CPU with a CPU that
• The CPU cannot communicate with the Q series
08H PLC access error C/N can communicate with the Q
C24.
series C24.
• Check and correct the external
• The PLC No. is not "FF", or a station No. set in the
10H PLC No. error C/N device transmit message and
network parameters.
restart data communications.
• Send again.
• An error was detected upon access to the PLC
11H Mode error — • Conduct individual station recovery
CPU.
test and check the Q series C24.
Special function • Check and correct the external
• A special function module does not exist at the
12H module designation C/N device transmit message and
specified position.
error restart data communications.
• Check the error and take
Special function • An error was detected upon access to a special corrective action according to the
21H C/N
module bus error function module at the specified position. manual of the corresponding
module.
42H Other errors See POINT .
POINT
• If an error occurs during A compatible 1C frame communications, the Q series C24
adds a 2-character error code (00H to 10H, 42H) to the "NAK" code and returns the
"NAK" code to the external device and stores the error code (equivalent to QnA
compatible 2C/3C/4C frame error code) to buffer memory address 25AH (CH1) or
26AH (CH2).
The exact error contents can be checked by reading the value stored to the
buffer memory.
See Section 10.2.1 for a detailed description of the error codes.
10 - 24 10 - 24
10 TROUBLESHOOTING
MELSEC-Q
The following describes the error codes, contents and corrective actions for errors
(including errors at the abnormal completion) that may occur while the Q series C24
modem function is used.
The error codes for the modem function are stored in the modem function error code
storage area (address : 221H(545)) of the buffer memory.
The reference pages listed in the table below are found in the User's Manual
(Application).
Error code
Signal
(Hexa- Error Error Contents Corrective action Reference section
name
decimal)
There is an error in the designation of the notification Set 0 to 1 to the notification execution
7FD0H
execution. designation.
There is an error in the designation of the number of Set the number of connection retries in
7FD1H
connection retries. the range of 1 to 5.
There is an error in the designation of the connection Set the connection retry interval in the
7FD2H Section 3.3.6
retry interval. range of 90 to 300 (s).
Modern There is an error in the initialization/connection time- Set the initialization/connection time- out
7FD3H CHn
function out designation. in the range of 1 to 60 (s).
ERR.
error There is an error in the designation of the number of Set the number of initialization retries in
7FD4H
initialization retries. the range of 1 to 5.
There is an error in the designation of the data Designate the registered data number for Section 3.3.6
7FD5H
number for initialization. initialization, or 0. Section 3.4.5
7FD6H Recheck the pager receiver designation.
There is an error in the data for connection designated
Recheck the dialing number of the Section 3.4.4
7FD7H by the data number for connection.
external line.
7FD8H System error The OS of the Q series C24 detected some error. ( 1)
After the modem has been initialized,
External destination is connected to network or connect to the network if the external Section 3.4.6
7FD9H
modem has not been initialized. destination is not connected to the Section 3.4.7
network or report it.
There is an error in the designation of the data number Designate a registered number for the Section 3.3.6
7FDAH
for connection. data for connection. Section 3.4.6
There is an error in the designation of the GX Set 0 to 1 to the GX Developer
7FDBH Section 3.3.6
Developer connection. connection designation.
Recheck the waiting time for the
There is an error in the data for connection designated
7FDCH notification-message part of the message Section 3.4.4
by the data number for connection.
transmission.
• Recheck the telephone number in the
CHn data for connection.
Modern ERR. • Check if the destination is ready for a Section 3.3.6
7FDDH function A connection time-out error occurred. connection. Section 3.4.3
error • Recheck the set value of the Section 3.4.4
connection time-out.
• Recheck the initialization command.
• Check if there is any problem with the
modem/TA by seeing the operation
manual of the modem/TA.
Connection to the modem/TA was unsuccessful, or • Connect the modem/TA to the Q series
7FDEH —
the modem/TA is not connected. C24.
• Check the connection cable by seeing
the operation manual of the
modem/TA.
7FDFH Modem connection channel number is not designated.
Set 1 to 2 to the modem connection
Designated value of modem connection channel is Section 3.3.6
7FE0H channel designation.
incorrect.
10 - 25 10 - 25
10 TROUBLESHOOTING
MELSEC-Q
Error code
Signal
(Hexa- Error Error Contents Corrective action Reference section
name
decimal)
• Recheck the user frame number.
• Designate the registered user frame Section 3.4.3
There is an error in the designation of the user frame
number. Section 3.4.4
number.
• Register the designated data for Section 3.4.5
initialization.
• Designate the output head pointer in
7FE1H the range of 1 to 100.
• Designate the position (n-th position)
There is an error in the designation of the output head where the data for initialization number
pointer. is designated.
• Designate the data for initialization
Section 3.4.5
number at the designated position
(n-th position).
Designate a registered data for
There is an error in the designation of the output frame initialization number within the range of
7FE2H Modern
number. CHn the designated number of outputs from
function
ERR. the location of the output head pointer.
error
• Designate the data for initialization in
There is an error in the designation of the number of the range of 1 to 78. Section 3.4.3
7FE3H
registered data bytes. • Designate 80 for the data for Section 3.4.4
connection.
• Recheck the message length of the
7FE4H There is an error in the data for connection. Section 3.4.4
message for notification.
There is an error in the designation of the no- • Designate the no-communication
7FE5H Section 3.3.6
communication interval time. interval time in the range of 0 to 120.
• Clear the storage area of the
The number of remote password mismatch exceeded Accumulated count of unlock process
7FE8H Section 3.3.3
the value designated at the address 200DH. abnormal completion (address: 22FCH)
to 0.
• Clear the storage area of the callback
Callback denial exceeded the value designated at the
7FE9H denial accumulated count (address: Section 3.3.4
address 2002H
22F1H) to 0.
10 - 26 10 - 26
10 TROUBLESHOOTING
MELSEC-Q
1 If an error occurs while performing data exchange using the modem function
described in User's Manual (Application) Chapter 3, first check the following items
and confirm whether or not the error is caused by the modem/TA connection.
If an error relating to the modem function is occurring, perform necessary
corrective actions for each cause according to the reference sections given below:
• Check the ON/OFF status of current I/O signals of the Q series C24.
• Check the storage status for error codes related to the modem function. (See
Sections 10.2.3.)
• Check the ON/OFF status of the DR terminal of the modem/TA. (See the
manual for the modem/TA.)
10 - 27 10 - 27
10 TROUBLESHOOTING
MELSEC-Q
REMARK
The following are precautionary notes when exchanging data with an external device
via one of the Q series C24 interfaces.
(1) When the power supply to the Q series C24 or external device is started, the
remote device that is connected may generate a reception error.
(2) If the remote device that is connected starts up while data is being transmitted,
the remote device side will generate a reception error.
(3) When the Q series C24 error LED lights up because a reception error has
occurred, turn off the light if necessary in accordance with Section 10.1.
Also, if a reception error has occurred on the external device side, handle the
error by seeing to the operating manual for the external device.
Handle the occurrence of a reception error on the Q series C24 side using
the following corrective actions.
• When communicating with the MC protocol
The Q series C24 will disregard the received data or returns a response
message indicating an abnormal termination if it detects a reception error
after receiving the head data of the command message in the set format.
If the reception error is detected before the head data of the command
message in the set format is received, the received data will be
disregarded.
10 - 28 10 - 28
10 TROUBLESHOOTING
MELSEC-Q
Bidirectional
procedure
Non
Symptom Cause Corrective action MC
10 - 29 10 - 29
10 TROUBLESHOOTING
MELSEC-Q
10.3.2 Troubleshooting when "RD" LED does not blink even though an external device is
transmitting a message
Bidirectional
procedure
Non
Symptom Cause Corrective action MC
10 - 30 10 - 30
10 TROUBLESHOOTING
MELSEC-Q
10.3.3 Troubleshooting when the Q series C24 does not return a response message even
though an external device transmitted a message and the "RD" LED blinked
Bidirectional
procedure
Non
Symptom Cause Corrective action MC
10 - 31 10 - 31
10 TROUBLESHOOTING
MELSEC-Q
10.3.4 Troubleshooting when an external device transmitted a message and "RD" LED
blinked, but the Read Request signal was not turned ON
Bidirectiona
procedure
Non
Symptom Cause Corrective action MC
10 - 32 10 - 32
10 TROUBLESHOOTING
MELSEC-Q
Bidirectional
procedure
Non
Symptom Cause Corrective action MC
procedure
Non
Symptom Cause Corrective action MC
10 - 33 10 - 33
10 TROUBLESHOOTING
MELSEC-Q
Bidirectional
procedure
Non
Symptom Cause Corrective action MC
• An error was generated • Check the error contents from the state of SB
on the MELSECNET/ H, and SW related to the MELSECNET/H,
MELSECNET/10. MELSECNET/10 with the GX Developer
• The local station CPU monitor, etc. and perform the checks and take
on the MELSECNET/H, the corrective action described in the
MELSECNET/10 MELSECNET/H, MELSECNET/10 reference
generated an error. manual.
• Module installation • Change the transmit message designation data.
address designation
• Communication error
during communications
signal "C/N" turned on.
with intelligent function
module is incorrect.
• A command that cannot • Stop the CPU and restart data communications.
be transmitted during • Set the "Enable/disable write during RUN"
RUN (sequence switch to "Enable" by command.
program, parameters,
etc.) was transmitted, or
"Disable write during
RUN" is set.
Bidirectional
procedure
Non
Symptom Cause Corrective action MC
• Data does not match the • Check the Q series C24 and external device
parity bit setting. data format and match the settings.
• Sum check codes do not • Check if the sum check code transmitted from
match. the external device is correct. (Recalculate)
• When CH1 and CH2 are • When using CH1 and CH2 independently, check
used in the linked mode, that the Q series C24 is not in the linked mode.
• Communication error the cable is not • When using CH1 and CH2 in the linked mode,
signal "P/S" turned on. connected to one of the also connect the cable to both of the interfaces.
interface. Note
• If the cable is not connected to one of the
interfaces when CH1 and CH2 are used in
the linked mode, noise may enter and the
data may be destroyed and "Data cannot be
decoded" or "Communications error cause"
may occur.
10 - 34 10 - 34
10 TROUBLESHOOTING
MELSEC-Q
Bidirectional
procedure
Non
Symptom Cause Corrective action MC
10 - 35 10 - 35
10 TROUBLESHOOTING
MELSEC-Q
Bidirectional
procedure
Non
Symptom Cause Corrective action MC
• Data does not match the • Check if the Q series C24 and external device
stop bit setting. settings are the same.
• Transmission rate is too • Decrease the transmission rate and restart data
fast and the next data is communications.
transmitted before the Q
series C24 completes
processing of the
receive data.
• Data larger than the • Use DTR and DC control and interrupt
receive buffer size was transmission before the buffer becomes full.
received. Perform RS and CS control when the modem
function is used.
• Increase the transmission interval and provide
an ample PLC CPU read processing time.
Note
10 - 36 10 - 36
10 TROUBLESHOOTING
MELSEC-Q
10.3.10 Troubleshooting when communication error "CH1 ERR.", "CH2 ERR." generate
Bidirectional
procedure
Non
Symptom Cause Corrective action MC
• There is an error in the • Read the error code from the buffer memory
communication protocol and check the error contents and change the
or transmission setting. switch setting to the correct setting.
• There is an error in the • Read the error code from the buffer memory
on-line mode switching and check the error contents and correct the
designation. designation contents.
• On-demand execution • Read the error code from the buffer memory
generated an error. and check the error contents and correct the
designation contents.
• The Q series C24 • Read the error code from the buffer memory
detected an error while and take the corrective action corresponding to
transmitting data. the error contents.
• The Q series C24 • Read the error code from the buffer memory
detected an error while and take the corrective action corresponding to
receiving data. the error contents.
• "ERR." LED turned on. Note
• When the "ERR." LED is turned on, the error code is stored to the following buffer memory.
Data receive error 258H 268H Data receive result storage area
Modern function error 221H Modern function error code storage area
MC protocol
025AH 026AH MC protocol transmission error code
transmission error
Monitoring device error 2205H 2305H PLC CPU monitoring function execution result
10 - 37 10 - 37
10 TROUBLESHOOTING
MELSEC-Q
Bidirectional
procedure
Non
Symptom Cause Corrective action MC
• With a multidrop link, two or • Connect the external devices and the Q series C24 in a
more devices transmitted 1:1 configuration and perform a communications test.
data at the same time. Since data is transmitted simultaneously from two or
more devices with a multidrop link when normal
communications among all the devices is possible,
interlock the external devices so that they do not
transmit simultaneously.
• The signal cable wiring
connection is faulty. • Replace the cable, or make the connections firm.
• When "Check CD terminal" • Change the wiring so that the CD signal remains ON all
• Communications are
is set, the CD signal is the time, or change the setting to "Do not check CD
intermittently established
turned on/off repeatedly. terminal".
and lost.
• When half-duplex
( 1) • Control the external device so that the ON/OFF timing
communications is selected,
of each signal is matched.
the ON/OFF timing of each
See Chapter 8 of User's Manual (Application).
signal is not matched.
• Requested processing of the
next transmission before the
processing of the current
transmission is completed. • Make sure to obtain handshake in the sequence
• Requested processing of the program.
next reception before the
processing of the current
reception is completed.
1 The following explains how to take corrective actions when a normal exit response
message cannot be received upon sending of a command message.
1) When a response message of abnormal end is received
When an external device sent a command message and received an
abnormal end response message, take corrective action with the error
according to the error code in the response message (see Section 10.2).
2) When response messages cannot be received
Change the setting value for the response monitoring time (timer 1, default
value is 5 seconds).
(See Section 6.2 of the User's Manual (Application).)
If response messages still cannot be received after changing the setting value,
check the communication protocol setting of the corresponding interface, the
ON status of the displayed LED, and the connection cable.
3) When the first part of a response message cannot be received
Increase the setting value of the message wait time (the default value is 0 ms).
(See Section 6.4 of the User's Manual (Application).)
If response messages still cannot be received after increasing the setting value,
it is necessary to reduce the processing time from the end of transmission
processing to the start of reception processing on the external device side.
10 - 38 10 - 38
10 TROUBLESHOOTING
MELSEC-Q
10.3.12 Troubleshooting when data that cannot be decoded is transmitted and received
Bidirectional
procedure
Non
Symptom Cause Corrective action MC
• With a multidrop link, • Connect the external devices and the Q series
two or more devices C24 in a 1:1 configuration and perform a
transmitted data at the communications test.
same time. Since data is transmitted simultaneously from
two or more devices with a multidrop link when
normal data communications among all the
devices is possible, interlock the external devices
so that they do not transmit simultaneously.
• Data does not match the • Match the Q series C24 and external device
parity bit setting. parity bit settings.
Note
• If the setting of one side is data bit length 7
bits and with parity and the setting of the
• Data does not match the
other side is data length 8 bits and without
parity bit setting.
parity, the number of transmission/receive
• Data that cannot be
bits will be the same and the data will sent
decoded was
and receive without generating an error.
transmitted and
• Transmission rate • Match the Q series C24 and external device
received
settings do not match. transmission rates.
• With a multidrop link, the • Check if the terminal resistor (110 or 330
terminal resistor is not in case of the Q series C24) is connected to the
connected correctly. stations at both ends of the link.
• When CH1 and CH2 are • When using CH1 and CH2 independently,
used to the linked mode, check that the Q series C24 is not in the linked
there is an interface mode.
without cable • When using CH1 and CH2 in the linked mode,
connection. also connect the cable to both of the interfaces.
Note
• If the cable is not connected to one of the
interfaces when CH1 and CH2 are used in
the linked mode, noise may enter and destroy
the data and "Data cannot be decoded" or
"Communication error cause" may occur.
10 - 39 10 - 39
10 TROUBLESHOOTING
MELSEC-Q
10.3.13 Troubleshooting when it is unclear whether the communication error cause is in the
Q series C24 or an external device
Bidirectional
procedure
Non
Symptom Cause Corrective action MC
10 - 40 10 - 40
10 TROUBLESHOOTING
MELSEC-Q
Non
Bidirection
Symptom Cause Corrective action MC procedure
al protocol
protocol
• Check the error code and execute
• A modem initialization error occurs.
processing accordingly.
• Auto modem initialization • Modem connection channel designation is • Set Modem connection channel
cannot be executed. not performed. designation.
• There is an error in the switch settings in the • Review the switch settings. Set it to match
GX Developer. the local station modem and the TA.
• Set the communication protocol to MC
• Communication protocol setting is incorrect.
• Data cannot be protocol, format 5.
communicated with GX • Transmission setting does not match the
• Review the transmission setting.
Developer supporting the Q external device.
series C24. • Communication rate does not match the
• Review the communication rate setting.
external device.
• The product is not supported by the GX
• Confirm the GX Developer’s S/W version.
Developer.
• Check the GX Developer’s connection
• The GX Developer does not
• There was an error in the GX Developer system.
receive the callback signals
connection system. • Set the connection system on “callback
from the Q Series C24.
reception waiting” and connect.
• There is an error in the GX Developer side’s • Set the modem’s settings on "Auto
modem settings. Reception."
• Check the GX Developer’s connection
• There s an error in the GX Developer’s
• Callback connections from system.
connection system.
the GX Developer are • Correct the Q Series C24’s settings.
refused by the Q Series • Check the telephone No.
• There is an error in the connection system’s
C24. • Change the telephone No. to the data for
telephone No.
callback.
• There is an error in the Q Series C24 • Set the callback function designation on the
• When performing Auto setting value. setting 1 to 3.
(callback: during fixed/ • Check the GX Developer’s connection
• There is an error in the GX Developer’s
during designated number) system.
connection system.
from the GX Developer, • Check the Q Series C24’s settings.
connection to the Q Series • Check the telephone No.
• There is an error in the telephone No. of the
C24 is refused. • Change the telephone No. to the data for
connection system.
callback.
• Adjust each of the timer values for the
• It is possible to connect • The timer value for the status of the modem callback function on the GX Developer side.
from the GX Developer, but used or the line is short. (Line callback cancel wait time, callback
callback from the Q Series delay time)
C24 cannot be performed. • There is a problem with the modem • Check the modem’s specifications and
specifications or settings. settings.
10 - 41 10 - 41
10 TROUBLESHOOTING
MELSEC-Q
10.3.15 Troubleshooting when data cannot be communicated with the ISDN sub-address
Non
Bidirection
Circumstance Cause Corrective action MC procedure
al protocol
protocol
• Sub-address is incorrect. • Review the sub-address.
• Data cannot be • Modem does not support ISDN sub- • Use modem that supports ISDN sub-
communicated with ISDN address. address.
sub-address • Sub-address is incorrectly partitioned. • Review how to partition the sub-address
using the TA manual.
10.3.16 Troubleshooting when constant cycle transmission does not operate normally
Non
Bidirection
Circumstance Cause Corrective action MC procedure
al protocol
protocol
• Does not operate in the • The setting value of the constant cycle • Review the constant cycle transmission
cycle time designated in the transmission is incorrect. setting.
constant cycle transmission • The cycle time is affected by some causes. • Remove the causes or designate the cycle
setting time anticipating the causes.
10.3.17 Troubleshooting when condition agreement transmission does not operate normally
Non
Bidirection
Circumstance Cause Corrective action MC procedure
al protocol
protocol
• Does not operate in the • The setting value of the condition • Review the condition agreement
cycle time designated in agreement transmission is incorrect. transmission setting.
condition agreement • The cycle time is affected by some causes. • Remove the causes or designate the cycle
transmission setting time anticipating the causes.
Non
Bidirection
Circumstance Cause Corrective action MC procedure
al protocol
protocol
• Interrupt issuance was not designated. • Designate interrupt issuance.
• Receiving by instruction other than • Use BUFRCVS instruction to receive
BUFRCVS. interrupt data.
• Cannot receive data with
• "Parameter setting" - "PC system setting" - • Review "Parameter setting" - "PS system
the interrupt program
or "Interrupt pointer setting" are not set on setting" - "Interrupt pointer setting" on the
the PLC CPU side, or the settings are PLC CPU side
incorrect.
Non
Bidirection
Circumstance Cause Corrective action MC procedure
al protocol
protocol
• Flash ROM overwrite allow/prohibit was not • Set Flash ROM overwrite allow/prohibit to
• Cannot write data to Flash set to allow. allow.
ROM • Setting change was not set to allow in the • Set setting change to allow in the switch
switch settings by GX Developer. setting by GX Developer.
10 - 42 10 - 42
10 TROUBLESHOOTING
MELSEC-Q
Non
Bidirection
Circumstance Cause Corrective action MC procedure
al protocol
protocol
• A communication error has occurred. • Check the error and remove the cause
according to Section 10.1.1.
• "ERR" LED is lit
• Switch settings of the Q series C24 are • Review the switch settings of the Q series
incorrect. C24.
10 - 43 10 - 43
APPENDIX
MELSEC-Q
APPENDIX
The Q series C24 of function version B has several functions that have been added or
changed from the conventional product (function version A).
This chapter explains a comparison of the functions of Q series C24/GX Configurator-
SC accompanied by the change/addition of functions, and explains how to utilize
programs created for function version A as well as how to incorporate function version
B modules into the existing system.
App. - 1 App. - 1
APPENDIX
MELSEC-Q
Q series C24
(function version)
Function QJ71C24N QJ71C24
App. (-R2/R4) (-R2)
B B A
Communication using bidirectional protocol
Data transmission/reception in any format
Data reception by interrupt programs
ASCII data transmission/reception by ASCII-BIN conversion
Data transmission/reception by specifying transparent code
Specification of Receive transparent code
Specification of Transmission transparent 1st ( 3)
Multiple specification of Transmission transparent 2nd to 10th
Registration of user frame for data communication
Registration of changeable data (added 05H, 0BH, 11H, and 17H)
Registration of changeable data (added 04H and 0AH)
Registration of changeable data (added E5H and EBH) ( 1)
Communication via public network, etc. (modem function)
Callback ( 4)
( 1)
DC code control (including Xon/Xoff control)
Transmission control
DTR/DSR (ER/DR) control
Mode switching
Switch to GX Developer connection mode
Independent/linked operation of each interface
Support for 230400 bps
Data transmission/reception at low speed (transmission speed: 50 bps)
Control of RS and DTR signal states
Data communication monitoring time
Non procedure and non reception monitoring time format designation
Transmission control start/end free area designation
Communication data monitoring function
UINI instruction ( 1)
Monitoring/testing of initial settings and setting values with utility package
Startup from the system monitor ( 5)
Addition to the setting items (See (2)) —
GX Developer and GOT connection
Simultaneous connection of GX Developer and GOT to the Q series C24 ( 6)
Support for multiple CPU system
Communication with non-control CPU using the MC protocol
Communication with QnA compatible 4C frame (ASCII code) Formats 1 to 4
Communication with QnA compatible 4C frame (binary code) Format 5
Multiple CPU setting using GX Developer (I/O assignment, switch setting, interrupt pointer setting, etc.)
: Usable
: Usable (Model serial no. [production date] limited)
: Usable
App. - 2 App. - 2
APPENDIX
MELSEC-Q
1 There is a limitation in the production date of the Q series C24 that contains
functions that are usable.
For version verification, see section 2.6.
2 The data reception using format-0 refers to the method of receiving data by user
frame, which was supported in the Q series C24 of function version A.
3 The Q series C24 of function version A is capable of setting one pair of
transparent code and additional code per interface for both transmission and
reception.
4 This function can be used when connecting with GX Developer.
5 This function is available in GX Developer Version 6 or later.
6 GX Developer can only be connected to the CH1 side in case of the Q series C24
of function version A.
It is not possible to connect both GX Developer and the GOT to the two interfaces
at the same time.
App. - 3 App. - 3
APPENDIX
MELSEC-Q
Appendix 1.2 Precautions when Updating the Module from Function Version A to B
This section explains how to utilize programs created for the Q series C24 of function
version A for the Q series C24 of function version B and how to incorporate function
version B into the existing system.
App. - 5 App. - 5
APPENDIX
MELSEC-Q
This section explains a comparison of the functions of the Q series C24 and QnA/A
series modules, and explains how to utilize programs created for A series modules as
well as how to install the Q series C24 into the existing system.
QnA/A modules refer to the following products.
Model name Product name
QC24N AJ71QC24N (-R2,R4), A1SJ71QC24N (-R2)
QC24 AJ71QC24 (-R2,R4), A1SJ71QC24 (-R2)
UC24, C24-S8 AJ71UC24, A1SJ71UC24 (-R2,R4,PRF), AJ71C24-S8
Appendix 2.1 Functional Comparison with the Q series C24 and the QnA/A Series Modules
The following shows a functional comparison between the Q series C24 and the
QnA/A series modules.
The symbol in the model name columns indicates that the corresponding functions
are compatible between the applicable models (for more information, see the manual
for each module).
Indicates functions that have been added to or modified from the QnA/A
series modules.
Function Q series C24 QC24N QC24 UC24 C24-S8
Communication using MC protocol —
Communication in QnA compatible 3C frame
Communication in QnA compatible 4C frame Communication
Communication in QnA compatible 2C frame with ASCII code
Communication in A compatible 1C frame
Communication
Communication in QnA compatible 4C frame
with binary code
Read/write of QCPU device memory —
Batch read/write of device memory ( 5)
( 1) ( 1)
Excluding multiple block batch read/write.
Multiple block batch read/write ( 5) ( 2) ( 2)
Accessing other stations (via network/data link) ( 3)
Arbitrary data
Transmission from the PLC CPU (on-demand)
Using user frame
Communication with m:n connection between the PLC CPU and
external devices
Communication using non procedure protocol —
Transmitted/received with arbitrary format
Transmitted/received with user frame ( 4)
Transmitted/received with ASCII-BIN conversion
Transmitted/received with transparent code designation
Communication using bidirectional protocol —
Transmitted/received with arbitrary format
Transmitted/received with ASCII-BIN conversion
Transmitted/received with transparent code designation
App. - 6 App. - 6
APPENDIX
MELSEC-Q
3 Access to other stations cannot be performed via data link system (MELSECNET(II), MELSECNET/B).
4 Transmission is only possible using the printer function.
5 When the Q series C24 is used, it is possible to read/write a maximum of 960 words (in case of QC24(N), it
is possible to read/write a maximum of 480 words.)
6 230400 bps can be used via CH1 of QJ71C24N (-R2/R4) only.
The maximum transmission speed of QJ71C24 (-R2) is 115200 bps.
App. - 7 App. - 7
APPENDIX
MELSEC-Q
Appendix 2.2 Using Programs Designed for the QC24 (N) and Installing the Q Series C24
into Existing Systems
This section explains how to use programs designed for serial communication modules
in the QnA series and the installation of the Q series C24 into an existing system.
POINT
When using the Q series C24, make sure to set the operation mode, station
number, and transmission specifications with the following parameter setting
screen of GX Developer.
• "Intelligent function module switch setting" screen
The Q series C24 does not have the setting switches to set the operation mode,
station number, and transmission specification that are available in the serial
communication modules for QnA series.
The data communication between the QnACPU and external devices as well as other
QnACPU which has been performed by QC24(N) can also be performed by the Q
series C24.
The following explains how to use programs designed for QC24(N) during data
communication using the Q series C24.
(1) The communication programs directed to the QC24(N) on the external device side
and the communication programs on the QnACPU (self-station) side to which the
QC24(N) is mounted can be used for the Q series C24.
However, note the following points.
• There is no function that allows data communication with other station's PLC
CPUs by a data link instruction.
Delete the part of data communication program by data link instructions.
• When using a new function, create a new program.
(2) Make sure to check operation when using communication programs for QC24(N)
on the external device side and the QnACPU (self-station) side.
(3) The notes during data communication by RS-422/485 interface also apply to the Q
series C24.
• Take measures against data error reception on the external device side (see
Section 3.3.3).
• Operation of RS-422/485 interface on the PLC side.
App. - 8 App. - 8
APPENDIX
MELSEC-Q
The following explains the Installation of the Q series C24 on an existing system.
POINT
The functional use is the same, except for the functions added by the Q series C24
to the conventional module. However, with the introduction of high-speed QCPUs,
there may be cases in which communication cannot be performed normally when a
PLC module in the QnA series is replaced by a Q series PLC. When a module is
changed to a Q series PLC module, make sure to perform an operation check.
App. - 9 App. - 9
APPENDIX
MELSEC-Q
Appendix 2.3 Using Programs Designed for the Computer Link Module and Installing the Q
Series C24 into Existing Systems
This section describes how to use programs created for A series computer link
modules and installing the Q series C24 into an existing system.
POINT
When using the Q series C24, make sure to set the operation mode, station
number, and transmission specifications with the following parameter setting
screen of GX Developer.
• "Intelligent function module switch setting" screen
The Q series C24 does not have the setting switches to set the operation mode,
station number, and transmission specification that are available in the computer
link module for A series.
Appendix 2.3.1 Using programs designed for the computer link module
The data communication between the PLC CPU and external device as well as other
PLC CPU that has been performed by A series computer link modules (hereinafter
abbreviated as UC24/C24-S8) can also be performed using the Q series C24.
However, UC24/C24-S8 and the Q series C24 have major differences in the following
points.
For PLC CPU side, create a new program according to the explanation in the section
of the function used.
(Differences between UC24/C24-S8 and the Q series C24)
• Initial setting items and the setting method of addresses and special application
areas of the buffer memory
• Input/output signals for handshake
• Dedicated instructions of the PLC CPU
App. - 10 App. - 10
APPENDIX
MELSEC-Q
1) The program for data transmission on the PLC CPU side is different
from when UC24/C24-S8 is used.
Create a new program on the PLC CPU side according to Section 3.11
in the Reference Manual.
2) Data to be sent to the external device is identical to when the UC24/C24-
S8 is used.
App. - 11 App. - 11
APPENDIX
MELSEC-Q
3) When data is received by a reception end code, the external device side
must send the end code data (the default is CR+LF (code: 0DH and 0AH)
at the end of the data sent to the PLC CPU side.
Once any end code is registered, data can be transmitted in the same
way as for the UC24/C24-S8.
4) The external device side can receive data from the Q series C24 in the
same ways as UC24.
(5) Others
1) The Q series C24 has other functions that are equivalent to those of
UC24/C24-S8, which are not mentioned above.
2) Check functions and specifications in this manual and the manuals listed
below, and use the applicable functions.
• User's Manual (Application)
• Reference Manual
App. - 12 App. - 12
APPENDIX
MELSEC-Q
This section shows the notes when installing the Q series C24 into an existing system
that uses UC24/C24-S8.
POINT
Since performances and response speeds are different between the Q series C24
and the UC24/C24-S8, communication may not be performed normally when a
PLC module in the A series is replaced by a Q series PLC.
When a module is changed to a Q series PLC module, make sure to check
operation.
App. - 13 App. - 13
APPENDIX
MELSEC-Q
Transmission command
Output instruction
complete device
[Calculation example]
Estimate the time required to process the Output instruction when
transmitting 100 bytes of data using the non procedure protocol with the
QJ71C24N. (Unit: ms)
• Scan time : 10 ms
• Data length : 10 bits (1 start bit, 8 data bits, 1 stop bit, no parity
bit)
• Communication rate : 19200 bps
10 + (10/19200 1000 + 0.07) 100 + 3.0 72.08 (ms)
App. - 14 App. - 14
APPENDIX
MELSEC-Q
Input instruction
complete device
(DX3)
Reception data
External device side
2ms ( 2)
[Calculation example]
Estimate the time required to process the Input instruction when receiving
100 bytes of data using the non procedure protocol with the QJ71C24N.
(Unit: ms)
• Scan time : 10 ms
10 + 0.09 100 + 7.0 26.00 (ms)
2 When only using CH1 of the Q series C24 and when processing only
30 bytes of data received, the time until the reception data read request
(X3) comes on is displayed after the Q series C24 receives data from
the network.
App. - 15 App. - 15
APPENDIX
MELSEC-Q
App. - 16 App. - 16
APPENDIX
MELSEC-Q
MSD 0 1 2 3 4 5 6 7
LSD 000 001 010 011 100 101 110 111
0 0000 NUL DLE SP 0 @ P ‚ p
1 0001 SOH DC1 ! 1 A Q a q
2 0010 STX DC2 " 2 B R b r
3 0011 ETX DC3 # 3 C S c s
4 0100 EOT DC4 $ 4 D T d t
5 0101 ENQ NAK % 5 E U e u
6 0110 ACK SYN & 6 F V f v
7 0111 BEL ETB / 7 G W g w
8 1000 BS CAN ( 8 H X h x
9 1001 HT EM ) 9 I Y i y
A 1010 LF SUB * : J Z j z
B 1011 VT ESC + ; K [ k {
C 1100 FF FS , < L \ l |
D 1101 CR GS = M ] m }
E 1110 SO RS . > N n ~
F 1111 SI US / ? O o DEL
App. - 17 App. - 17
APPENDIX
MELSEC-Q
CH1
RS-232
98 (3.86)
R2
( 2)
SDA
1
SDB
3
RDA
(FG) 5
R1 6
( 1) r1 RDB
7
( 3) CH2
RS-422
/485
App. - 18 App. - 18
APPENDIX
MELSEC-Q
98 (3.86)
CH1
RS-232
R2
( 1)
CH2
RS-232
QJ71C24N-R2
(3) QJ71C24N-R4
QJ71C24N-R4
RUN ERR.
NEU. NEU.
CH1 SD SD CH2
RD RD
CH1
RS-422/485
SDA
SDB
R3
98 (3.86)
RDA
( 1) RDB
SG
r2 (FG)
( 2)
CH2
RS-422/485
SDA
SDB
RDA
RDB
SG
(FG)
QJ71C24N-R4
App. - 19 App. - 19
APPENDIX
MELSEC-Q
App. - 20 App. - 20
APPENDIX
MELSEC-Q
Q series C24 side RS232 signal RS422 signal External device side
CD 1 1 FG SW1 SW2 FG
2
2 2 RDA
RD TXD 1 OFF 1 OFF TX 15
3 3 R
SD RXD RDB
2 ON 2 OFF 6
4 4 SDA
DTR RTS RX 19
3 OFF 3 OFF SDB
5 5
SG CTS
4 ON 4 OFF 3 DSRA
6 20
DSR DTR RTS 16 R
5 OFF 5 OFF DSRB
7 6
RS DSR
6 ON 6 OFF 7 DTRA
8 8
CS CD CTS 20 DTRB
9 7 7 OFF 7 OFF 1 or 14
RI SG SG RTSA
8 ON RTSB
CTSA
CTSB
SG
• The CD terminal check setting should be set to "No check" according to the explanation in Section 3.2.1 (1).
• DC code control or DTR/DSR control becomes possible for transmission control.
(Connection example 2)
(KS-1/KS-10P)
Q series C24 side RS232 signal RS485 signal External device side
CD 1 1 FG 1 FG
FG SW1 SW2
2 2 (+) 19
RD RD 1 ON 1 ON DATA
RDA
OUT 25 R
3 3 RDB
SD SD 2 ON
(-)
(+) 15
4 4 SDA
DTR CS DATA
17
3 OFF IN
SDB
5 5 (-)
SG RS (+) 14
4 OFF DSRA
6 6 CONT
DSR ER OUT 16 R
5 ON (-) DSRB
7 7
RS SG (+) 21
6 ON CONT DTRA
8 8 IN 23
CS CD (-) DTRB
9 9 7 ON 7
RI DR SG RTSA
8 ON RTSB
CTSA
CTSB
SG
• The CD terminal check setting should be set to "No check" according to the explanation in Section 3.2.1 (1).
• DC code control or DTR/DSR control becomes possible for transmission control.
App. - 21 App. - 21
APPENDIX
MELSEC-Q
(Connection example 3)
(KS-485)
Q series C24 side RS232 signal RS485 signal External device side
1 1 FG
CD 1 FG SW1 SG
2 2 2
RD RD 1 ON TRD+ SDA
3 3 TRD- 3 SDB
SD SD 2 ON
FG 9 RDA
4 5
DTR CS R
3 ON RDB
5 6
SG ER
4 OFF SG
6 7
DSR SG
7 20 5 OFF
RS DR
8 24 6 OFF
CS TC
9 25 7 ON
RI CNT
8 ON
(Connection example 4)
(KS-485)
External device side RS232 signal RS485 signal Q series C24 side
1 FG
FG 1 FG SW1 SG
2 2
SD RD 1 ON TRD+ SDA
3 TRD- 3 SDB
RD SD 2 ON 9 When connecting
5 FG RDA
RS CS R with other stations
3 ON RDB
6
CS ER
4 OFF SG
7
DSR SG
20 5 OFF
SG DR
24 6 OFF
CD TC These switches should
25 7 OFF be ON when the KS-485
DTR CNT
is at the terminal of the
8 OFF • Data communication can be made
line. in half-duplex communication.
• Transmission control cannot be used.
App. - 22 App. - 22
APPENDIX
MELSEC-Q
This section provides the overview of the functions provided by MX Component and
explains the procedure up to creation of applications.
See Operating Manual and Programming Manual of MX Component for the details.
MELSECNET/H communication
Ethernet communication
GOT
App. - 23 App. - 23
APPENDIX
MELSEC-Q
App. - 24 App. - 24
APPENDIX
MELSEC-Q
App. - 25 App. - 25
APPENDIX
MELSEC-Q
This section explains the procedure for creating programs and sample programs using
MX Component.
↓
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) Use the functions provided by the software to write a
program that reads the device data.
Completed
App. - 26 App. - 26
APPENDIX
MELSEC-Q
Command1
' Connect to the communication line.
Command2
' Read the device data.
Command3
' Cut the communication line.
2) Program example
App. - 27 App. - 27
APPENDIX
MELSEC-Q
®
(b) When Visual C++ is used
//
// 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. - 28 App. - 28
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. - 29 App. - 29
APPENDIX
MELSEC-Q
When performing data communications with non procedure protocol, use the receive
data clear request shown in 6.1.4. and display the sequence program example if
clearing the receive data from external device. (If the Q series C24 input/output signal
is X/Y000 to X/Y01F.)
The following I/O signals (X) and internal relays (M) are used in the program.
App. - 30 App. - 30
APPENDIX
MELSEC-Q
POINT
When a function version A for the Q Series C24 is used, add the partial circuit
(shown with 1) shown in the program example in Section 6.1.4 (3).
(Communications are possible when M19 is ON.)
App. - 31 App. - 31
APPENDIX
MELSEC-Q
Appendix 9 Program Examples for Using Q Series C24 at MELSECNET/H Remote I/O
Station
QJ71LP21-25
Remote master station
( 2)
GX Developer
Control target
QJ72lP25-25
Remote I/O station
(Station No.1)
QJ71C24N( 1)
1 It is assumed that the QJ71C24N is mounted on Slot 0 of the base unit and
the starting I/O No. is "0".
2 Set the network parameters of the remote master station as shown below.
1) Network type : MNET/H (Remote master)
2) Starting I/O No. : 0000H
3) Network No. :1
4) Total stations :1
5) Mode : Online
6) Network range assignment (XY setting)
7) Refresh parameters
App. - 32 App. - 32
APPENDIX
MELSEC-Q
(2) Program example for interlocking the remote master station and
remote I/O station
Interlocks should be applied to the programs according to the link status of the
remote master station (host station) and remote I/O station (other station).
The following example shows an interlock in the communication program that
uses the link status (SB47, SB49) of the remote master station and the link status
(SW70 bit 0, SW74 bit 0, SW78 bit 0) of the remote I/O station (Station No. 1).
Reason: This way the control is not stopped even if the network detects an
instantaneous error due to a faulty cable condition and noise
interference.
Also, the multipliers of 4 and 3 should only be considered as a
guideline.
In the following program example, data are read from or written to the buffer memory of
the Q series C24 using the REMFR/REMTO instruction.
POINT
Use GX Configurator-SC to change the default value of the buffer memory. Using
GX Configurator-SC, save the new setting value to the flash ROM of the Q series
C24. (Refer to Chapter 8.)
Abnormal completion of
REMTO instruction
App. - 34 App. - 34
APPENDIX
MELSEC-Q
The following program example sends on-demand data using the REMFR/REMTO
instruction and I/O signals.
For the on-demand function, refer to Section 3.11 of the Reference Manual and
Chapter 10 of the User's Manual (Application).
App. - 35 App. - 35
APPENDIX
MELSEC-Q
App. - 36 App. - 36
APPENDIX
MELSEC-Q
The following program example receives data under the nonprocedural protocol (or
bidirectional protocol) using the REMFR instruction and I/O signals.
Refer to Chapter 6 for the communication using the nonprocedural protocol.
Refer to Chapter 7 for the communication using the bidirectional protocol.
Refer to Chapter 11 of the User's Manual (Application) for data communication using
the user frames.
App. - 37 App. - 37
APPENDIX
MELSEC-Q
Abnormal completion of
REMFR instruction
<Read of received data>
Reads data as many as the
received data count from the
communication area of the buffer
memory to D1.
Normal reception completion
REMARK
When data reception is executed by the bidirectional protocol, the area enclosed by
the dotted line shown above must be removed.
Set the intelligent function module switches as indicated below. (Refer to Section
4.5.2.)
Switch No. Setting value
Switch 1 07C0H
Switch 2 0007H
App. - 38 App. - 38
APPENDIX
MELSEC-Q
The following program example sends data under the nonprocedural protocol (or
bidirectional protocol) using the REMFR/REMTO instruction and I/O signals.
Refer to Chapter 6 for the communication using the nonprocedural protocol, and to
Chapter 7 for the communication using the bidirectional protocol.
App. - 39 App. - 39
APPENDIX
MELSEC-Q
Abnormal completion of
transmission
App. - 40 App. - 40
APPENDIX
MELSEC-Q
The following program example uses the receive data clear request area of the buffer
memory.
Refer to Section 6.1.4 for received data clear.
App. - 41 App. - 41
APPENDIX
MELSEC-Q
Timer start
Resets the communication ( 1)
disable flag.
1 When using the Q series C24 of function version A, add the areas enclosed
by the dotted lines to the sequence program. (Make communication when
M19 is ON.)
App. - 42 App. - 42
APPENDIX
MELSEC-Q
The following program example sends data by the user frames using the
REMFR/REMTO instruction and I/O signals.
Refer to Section 11.4 of the User's Manual (Application) for the transmission using the
user frames.
App. - 43 App. - 43
APPENDIX
MELSEC-Q
App. - 44 App. - 44
APPENDIX
MELSEC-Q
App. - 45 App. - 45
APPENDIX
MELSEC-Q
The following program example performs initial setting using the REMTO instruction.
Execute this program when changing the default values of the Q series C24 buffer
memory.
Refer to Chapter 8 when changing the default values of the Q series C24 buffer
memory using GX Configurator-SC.
App. - 46 App. - 46
APPENDIX
MELSEC-Q
REMARK
When changing the default values of the following buffer memory areas, refer to
above (2) Program example to perform programming.
• DTR/DSR (ER/DR), DC control designation
• DC1/DC3 (Xon/Xoff) code designation
• DC2/DC4 code designation
• CD terminal check designation (for RS-232)
• Communication system designation (for RS-232)
• Simultaneous transmission priority/non-priority designation
• Retransmission time transmission method designation
• Simultaneously transmission data valid/invalid designation
• No-reception monitoring time (timer 0) designation
App. - 47 App. - 47
APPENDIX
MELSEC-Q
The following program example registers a user frame to the flash ROM of the Q
series C24 using the REMFR/REMTO instruction and I/O signals.
Refer to Section 9.4 of the User's Manual (Application) for the registration of the user
frame.
POINT
It is recommended to use GX Configurator-SC when registering a user frame to the
flash ROM of the Q series C24. (Refer to Chapter 8.)
App. - 48 App. - 48
APPENDIX
MELSEC-Q
App. - 49 App. - 49
APPENDIX
MELSEC-Q
The following program example reads a user frame registered to the flash ROM of the
Q series C24 using the REMFR/REMTO instruction and I/O signals.
Refer to Section 9.4 of the User's Manual (Application) for details.
POINT
It is recommended to use GX Configurator-SC when reading a user frame
registered to the flash ROM of the Q series C24. (Refer to Chapter 8.)
App. - 50 App. - 50
APPENDIX
MELSEC-Q
App. - 51 App. - 51
APPENDIX
MELSEC-Q
The following program example deletes a user frame registered to the flash ROM of
the Q series C24 using the REMFR/REMTO instruction and I/O signals.
Refer to Section 9.4 of the User's Manual (Application) for details.
POINT
It is recommended to use GX Configurator-SC when deleting a user frame
registered to the flash ROM of the Q series C24. (Refer to Chapter 8.)
App. - 52 App. - 52
APPENDIX
MELSEC-Q
App. - 53 App. - 53
APPENDIX
MELSEC-Q
Appendix 9.12 When changing the communication protocol and transmission setting
This section provides a program example that changes the communication protocol
and transmission setting using the REMFR/REMTO instructions and I/O signals.
(When the module is used on a MELSECNET/H remote I/O station, the station No.
cannot be changed because the UINI instruction is unavailable.)
For changing the communication protocol and transmission setting, refer to Chapter 15
of the User's Manual (Application).
App. - 54 App. - 54
APPENDIX
MELSEC-Q
App. - 55 App. - 55
APPENDIX
MELSEC-Q
App. - 56 App. - 56
APPENDIX
MELSEC-Q
The following sheet is for recording parameter setting values set by GX Developer.
Use as many copies as needed.
In order to review the setting values of the utility package (GX Configurator-SC),
print out the content of the file generated by the "Make text file" function of GX
Configurator-SC which can be used as the setting value recording sheet.
[Module No. ]
Recording sheet 1 (Intelligent function module interrupt pointer setting)
GX Developer Set data
Data item name
setting screen Setting value Remarks
Intelligent Interrupt pointer start No.
CPU side Input format: Decimal
function module Interrupt pointer No. of modules 2 (fixed)
interrupt pointer Intelligent Start I/O number Input format: Hexadecimal
setting module side Start SI number 0 (fixed) Input format: Decimal
H
Switch 2 CH1 Communication protocol setting =
CH2 Communication rate setting CH2 Transmission setting
b15 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0
Switch 3
H
Switch 4 CH2 Communication protocol setting =
Switch 5 Station number setting =
Check the setting values in the next page and record them.
App. - 57 App. - 57
APPENDIX
MELSEC-Q
(GX Developer "Intelligent function module switch setting" setting values recording check
sheet)
(1) Transmission setting (Enter "0" or "1" in the bit position field)
b7 b6 b5 b4 b3 b2 b1 b0
CH1 side
CH2 side
Bit Description OFF (0) ON (1) Remarks
Always set to OFF on
b0 Operation setting Independent Linked
CH1 side.
b1 Data bit 7 8 Do not include parity bit.
b2 Parity bit No Yes Vertical parity
Valid only when parity
b3 Odd/even parity Odd Even
bit is set to Yes.
b4 Stop bit 1 2 —
b5 Sum check code No Yes —
b6 Write during RUN Prohibit Allow —
b7 Setting modification Prohibit Allow —
(2) Communication rate setting (Enter check marks in the CH1 and
CH2 fields)
CH1 CH2 Setting value Communication speed (unit: bps)
FH 50
0H 300
1H 600
2H 1200
3H 2400
4H 4800
5H 9600
6H 14400
7H 19200
8H 28800
9H 38400
AH 57600
BH 115200
CH 230400
(3) Communication protocol setting (Enter check marks in the CH1 and
CH2 fields)
CH1 CH2 Setting value Setting data
0H GX Developer connection
1H Format 1
2H Format 2
3H MC protocol Format 3
4H Format 4
5H Format 5
6H Non procedure protocol
7H Bidirectional protocol
8H For linked operation setting
9H to DH Setting prohibited
EH ROM/RAM/Switch test
FH Individual station recovery test
App. - 58 App. - 58
INDEX
Ind
[A] [F]
Applicable modules ..................................... 2-1 Full-duplex communications ......................7-24
ASCII-code table ...................................App-17 Function lists of the Q series C24..............3-11
Auto refresh .............................................. 4-22 Functions available with utility package ......8-2
[B] [G]
BIDIN.......................................................... 9-14 GX Configurator-SC....................A-20, 2-2, 8-1
Bidirectional protocol ................................... 7-1 GX Configurator-SC function list ...............3-13
BIDOUT ..................................................... 9-11 GX Developer..................................... A-20, 2-2
[H]
[C] H/W gate OFF time ......................................3-9
C/N ........................................................... 10-33 How to detect reception error
CH1.ERR, CH2.ERR............................... 10-37 (bidirectional)..............................................7-13
Checking the function version................... 2-12 How to detect reception error
Checking the LED ON status, (non procedure)..........................................6-17
communications error status ..................... 10-1 How to detect transmission errors
Checking the software version (bidirectional)..............................................7-22
(GX Configurator-SC)................................ 2-13 How to detect transmission errors
Communication protocol setting................ 4-16 (non procedure)..........................................6-28
Communication rate .................................. 4-16 How to read the setting status of
Communication support tool .................App-23 switches....................................................10-11
Communication system............................... 3-1
Computer link module ...........................App-10 [I]
Connecting the RS-232 interface................ 4-6 I/O assignment settings .............................4-12
Connecting the RS-422/485 interface ........ 4-8 Individual station loopback test..................4-28
Comparison of the function .....................App-1 Individual station test..................................4-25
CSET (Receive data clear) ..............6-14, 9-19 Initializing error information .......................10-6
INPUT...........................................................9-8
[D] Installing utility package ...............................8-3
Data bit....................................................... 4-14 Interrupt pointer ..........................................4-20
Data communication functions.................... 2-5
Data format .................................................. 3-1 [L]
Data reception by receive complete code .. 6-3 LEDs displayed ............................................4-4
Dedicated instruction list ............................. 9-1 Linked operation.........................................4-17
Dedicated instructions ................................. 9-1 List of applications and assignments of
the buffer memory......................................3-17
[E] List of input/output signals for the
ERR. LED .................................................. 10-6 PLC CPU....................................................3-15
Error code table ....................................... 10-15
Explanation of utility package operation ..... 8-6
External dimensions ..............................App-18
Index - 1 Index - 1
[M] [S]
m:n ............................................................... 2-4 Serial communication module .....................1-1
Ind Monitor/test ................................................ 8-32 Setting and procedures prior to operation...4-1
Multiple CPU system ............................ 1-7, 5-3 Setting for GX Developer...........................4-12
Simultaneous transmissions......................7-24
[N] SIO............................................................10-36
n:1 ................................................................ 2-3 SPBUSY.....................................................9-17
NAK.......................................................... 10-33 Starting the utility........................................8-10
Non procedure protocol............................... 6-1 Station number setting ...............................4-17
Sum check code.........................................4-15
[O] Switch setting .............................................4-13
ONDEMAND................................................ 9-2 System configuration ...................................2-3
Operation mode....................................... 10-13 System registration to flash ROM..............8-16
OUTPUT ...................................................... 9-5
[T]
[P] Transmission area (bidirectional) ..............7-16
P/S ........................................................... 10-34 Transmission area (non procedure) ..........6-23
Parity bit ..................................................... 4-14 Transmission data (bidirectional)...............7-18
Part names and functions .......................... 4-3 Transmission data (non procedure) ..........6-25
PRO. ........................................................ 10-35 Transmission methods (bidirectional)........7-15
Processing time .....................................App-14 Transmission methods (non procedure) ...6-22
Transmission setting ..................................4-14
[Q] Transmission specification...........................3-1
QnA/A series module ..............................App-6 Troubleshooting .........................................10-1
[R] [U]
Reading the data communication Uninstalling utility package ..........................8-3
status........................................................ 10-10 Utility package ..............................................8-1
Reading the RS-232 control signal
status.......................................................... 10-9 [1]
Reading the signal status (RS-232).......... 10-9 1:1 system configuration..............................2-3
Receive area (bidirectional) ........................ 7-4 1:n.................................................................2-4
Receive area (non procedure) .................... 6-6
Receive complete code setting ................. 6-20
Receive data (bidirectional)......................... 7-6
Receive data (non procedure) .................... 6-8
Receive data clear (bidirectional).............. 7-14
Receive data clear (non procedure) ......... 6-14
Received data count.................................. 6-20
Receiving methods (bidirectional)............... 7-6
Receiving methods (non procedure)........... 6-8
ROM/RAM/switch tests ............................. 4-25
RS-232 interface specification .................... 3-3
RS-422/485 interface specification ............. 3-6
"RUN" LED............................................... 10-29
Remote password check...................... 1-9, 5-4
Index - 2 Index - 2
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.
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.
VS-VIEW
Copyright (c) 2001 ComponentOne LLC
VS-FlexGrid Pro
Copyright (c) 2000 VideoSoft Corporation
SPREAD
Copyright (c) 1996 FarPoint Technologies, Inc.
MITSUBISHI ELECTRIC
MITSUBISHI ELECTRIC EUROPE GEVA AUSTRIA UAB UTU POWEL LITHUANIA CSC Automation UKRAINE
EUROPE B.V. Wiener Straße 89 Savanoriu Pr. 187 15, M. Raskova St., Fl. 10, Off. 1010
German Branch AT-2500 Baden LT-2053 Vilnius UA-02002 Kiev
Gothaer Straße 8 Phone: +43 (0)2252 / 85 55 20 Phone: +370 (0)52323-101 Phone: +380 (0)44 / 238 83 16
D-40880 Ratingen Fax: +43 (0)2252 / 488 60 Fax: +370 (0)52322-980 Fax: +380 (0)44 / 238 83 17
Phone: +49 (0)2102 486-0 e mail: [email protected] e mail: [email protected] e mail: [email protected]
Fax: +49 (0)2102 486-1120 TEHNIKON BELARUS Intehsis Srl MOLDOVA
e mail: [email protected] Oktjabrskaya 16/5, Ap 704 Cuza-Voda 36/1-81
MITSUBISHI ELECTRIC FRANCE BY-220030 Minsk MD-2061 Chisinau EURASIAN REPRESENTATIVE
EUROPE B.V. Phone: +375 (0)17 / 2104626 Phone: +373 (0)2 / 562 263
French Branch Fax: +375 (0)17 / 2275830 Fax: +373 (0)2 / 562 263 CONSYS RUSSIA
25, Boulevard des Bouvets e mail: [email protected] e mail: [email protected] Promyshlennaya St. 42
F-92741 Nanterre Cedex Getronics b.v. BELGIUM Getronics b.v. NETHERLANDS RU-198099 St Petersburg
Phone: +33 1 55 68 55 68 Control Systems Control Systems Phone: +7 812 / 325 36 53
Fax: +33 1 55 68 56 85 Pontbeeklaan 43 Donauweg 2 B Fax: +7 812 / 325 36 53
e mail: [email protected] BE-1731 Asse-Zellik NL-1043 AJ Amsterdam e mail: [email protected]
MITSUBISHI ELECTRIC IRELAND Phone: +32 (0)2 / 467 17 51 Phone: +31 (0)20 / 587 6700 ELEKTROSTYLE RUSSIA
EUROPE B.V. Fax: +32 (0)2 / 467 17 45 Fax: +31 (0)20 / 587 6839 ul. Garschina 11
Irish Branch e mail: [email protected] e mail: [email protected] RU-140070 Moscow Oblast
Westgate Business Park, Ballymount TELECON CO. BULGARIA Motion Control NETHERLANDS Phone: +7 095/ 557 9756
IRL-Dublin 24 4, A. Ljapchev Blvd. Automation b.v. Fax: +7 095/ 746 8880
Phone: +353 (0) 1 / 419 88 00 BG-1756 Sofia Markenweg 5 e mail: [email protected]
Fax: +353 (0) 1 / 419 88 90 Phone: +359 (0)2 / 97 44 058 NL-7051 HS Varsseveld
e mail: [email protected] ELEKTROSTYLE RUSSIA
Fax: +359 (0)2 / 97 44 061 Phone: +31 (0)315 / 257 260 Krasnij Prospekt 220-1, Office 312
MITSUBISHI ELECTRIC . ITALY e mail: — Fax: +31 (0)315 / 257 269 RU-630049 Novosibirsk
EUROPE B.V INEA CR d.o.o. CROATIA e mail: — Phone: +7 3832 / 10 66 18
Italian Branch Losinjska 4 a Beijer Electronics AS NORWAY Fax: +7 3832 / 10 66 26
Via Paracelso 12 HR-10000 Zagreb Teglverksveien 1 e mail: [email protected]
I-20041 Agrate Brianza (MI) Phone: +385 (0) 1 / 36 940-01 NO-3002 Drammen
Phone: +39 039 60 53 1 ICOS RUSSIA
Fax: +385 (0) 1 / 36 940-03 Phone: +47 (0)32 / 24 30 00 Ryazanskij Prospekt, 8A, Office 100
Fax: +39 039 60 53 312 e mail: [email protected] Fax: +47 (0)32 / 84 85 77
e mail: [email protected] RU-109428 Moscow
AutoCont CZECH REPUBLIC e mail: [email protected] Phone: +7 095 / 232 0207
MITSUBISHI ELECTRIC SPAIN Control Systems s.r.o. MPL Technology Sp. z o.o. POLAND Fax: +7 095 / 232 0327
EUROPE B.V. Nemocnicni 12 ul. Sliczna 36 e mail: [email protected]
Spanish Branch CZ-70200 Ostrava 2 PL-31-444 Kraków
Carretera de Rubí 76-80 SMENA RUSSIA
Phone: +420 59 / 6152 111 Phone: +48 (0)12 / 632 28 85 Polzunova 7
E-08190 Sant Cugat del Vallés Fax: +420 59 / 6152 562 Fax: +48 (0)12 / 632 47 82
Phone: +34 9 3 565 3131 RU-630051 Novosibirsk
e mail: [email protected] e mail: [email protected] Phone: +7 095 / 416 4321
Fax: +34 9 3 589 2948
e mail: [email protected] louis poulsen DENMARK Sirius Trading & Services srl ROMANIA Fax: +7 095 / 416 4321
industri & automation Str. Biharia Nr. 67-77 e mail: [email protected]
MITSUBISHI ELECTRIC UK Geminivej 32 RO-013981 Bucuresti 1
EUROPE B.V. SSMP Rosgidromontazh Ltd RUSSIA
DK-2670 Greve Phone: +40 (0) 21 / 201 1146 23, Lesoparkovaya Str.
UK Branch Phone: +45 (0)43 / 95 95 95 Fax: +40 (0) 21 / 201 1148
Travellers Lane RU-344041 Rostov On Don
Fax: +45 (0)43 / 95 95 91 e mail: [email protected] Phone: +7 8632 / 36 00 22
GB-Hatfield Herts. AL10 8 XB e mail: [email protected]
Phone: +44 (0) 1707 / 27 61 00 ACP Autocomp a.s. SLOVAKIA Fax: +7 8632 / 36 00 26
Fax: +44 (0) 1707 / 27 86 95 UTU Elektrotehnika AS ESTONIA Chalupkova 7 e mail: —
e mail: [email protected] Pärnu mnt.160i SK-81109 Bratislava STC Drive Technique RUSSIA
EE-10621 Tallinn Phone: +421 (02)5292-2254 Poslannikov per., 9, str.1
MITSUBISHI ELECTRIC JAPAN Phone: +372 (0)6 / 51 72 80 Fax: +421 (02)5292-2248
CORPORATION RU-107005 Moscow
Fax: +372 (0)6 / 51 72 88 e mail: [email protected] Phone: +7 095 / 786 21 00
Office Tower “Z” 14 F e mail: [email protected]
8-12,1 chome, Harumi Chuo-Ku INEA d.o.o. SLOVENIA Fax: +7 095 / 786 21 01
Tokyo 104-6212 UTU POWEL OY FINLAND Stegne 11 e mail: [email protected]
Phone: +81 3 622 160 60 Box 236 SI-1000 Ljubljana
Fax: +81 3 622 160 75 FIN-28101 Pori Phone: +386 (0)1 513 8100
Phone: +358 (0)2 / 550 800 Fax: +386 (0)1 513 8170 MIDDLE EAST REPRESENTATIVE
MITSUBISHI ELECTRIC USA Fax: +358 (0)2 / 550 8841 e mail: [email protected]
AUTOMATION e mail: [email protected]
500 Corporate Woods Parkway Beijer Electronics AB SWEDEN SHERF Motion Techn. Ltd ISRAEL
Vernon Hills, IL 60061 UTECO A.B.E.E. GREECE Box 426 Rehov Hamerkava 19
Phone: +1 847 478 21 00 5, Mavrogenous Str. S-20124 Malmö IL-58851 Holon
Fax: +1 847 478 22 83 GR-18542 Piraeus Phone: +46 (0)40 / 35 86 00 Phone: +972 (0)3 / 559 54 62
Phone: +302 (0)10 / 42 10 050 Fax: +46 (0)40 / 35 86 02 Fax: +972 (0)3 / 556 01 82
Fax: +302 (0)10 / 42 12 033 e mail: [email protected] e mail: —
e mail: [email protected] ECONOTEC AG SWITZERLAND
Meltrade Automatika Kft. HUNGARY Postfach 282
55, Harmat St. CH-8309 Nürensdorf AFRICAN REPRESENTATIVE
HU-1105 Budapest Phone: +41 (0)1 / 838 48 11
Phone: +36 (0)1 / 2605 602 Fax: +41 (0)1 / 838 48 12 CBI Ltd SOUTH AFRICA
Fax: +36 (0)1 / 2605 602 e mail: [email protected] Private Bag 2016
e mail: [email protected] GTS TURKEY ZA-1600 Isando
SIA POWEL LATVIA Darülaceze Cad. No. 43A KAT: 2 Phone: +27 (0)11 / 928 2000
Lienes iela 28 TR-80270 Okmeydani-Istanbul Fax: +27 (0)11 / 392 2354
LV-1009 Riga Phone: +90 (0)212 / 320 1640 e mail: [email protected]
Phone: +371 784 2280 Fax: +90 (0)212 / 320 1649
Fax: +371 784 2281 e mail: [email protected]
e mail: [email protected]