Mitsubishi QJ71C24/-R2 User`s manual

MELSEC-Q/L Serial Communication Module
User's Manual (Application)
-QJ71C24N
-QJ71C24N-R2
-QJ71C24N-R4
-QJ71C24
-QJ71C24-R2
-LJ71C24
-LJ71C24-R2
SAFETY PRECAUTIONS
(Read these precautions before using this product.)
Before using this product, please read this manual and the relevant manuals carefully and pay full attention
to safety to handle the product correctly.
The precautions given in this manual are concerned with this product only. For the safety precautions of the
programmable controller system, refer to the user's manual for the CPU module used.
In this manual, the safety precautions are classified into two levels: "
WARNING" and "
CAUTION".
WARNING
Indicates that incorrect handling may cause hazardous conditions,
resulting in death or severe injury.
CAUTION
Indicates that incorrect handling may cause hazardous conditions,
resulting in minor or moderate injury or property damage.
Under some circumstances, failure to observe the precautions given under "
CAUTION" may lead to
serious consequences.
Observe the precautions of both levels because they are important for personal and system safety.
Make sure that the end users read this manual and then keep the manual in a safe place for future
reference.
1
When using the MELSEC-Q series serial communication module
[Design Precautions]
WARNING
● For the operation status of each station at communication error in each station, refer to the respective
manual for each station.
Incorrect output or malfunction due to a communication failure may result in an accident.
● 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 programmable controller system, install a call circuit with a lamp display or
buzzer sound.
● When connecting a peripheral with the CPU module or connecting an external device, such as a
personal computer, with an intelligent function module to modify data of a running programmable
controller, configure an interlock circuit in the program to ensure that the entire system will always
operate safely. For other forms of control (such as program modification or operating status change)
of a running programmable controller, read the relevant manuals carefully and ensure that the
operation is safe before proceeding. Especially, when a remote programmable controller is controlled
by an external device, immediate action cannot be taken if a problem occurs in the programmable
controller due to a communication failure. To prevent this, configure an interlock circuit in the program,
and determine corrective actions to be taken between the external device and CPU module in case of
a communication failure.
● Do not write any data to the "system area" of the buffer memory in the intelligent function module.
Also, do not use any "use prohibited" signals as an output signal from the programmable controller
CPU to the intelligent function module.
Doing so may cause malfunction of the programmable controller system.
2
[Design Precautions]
CAUTION
● Do not install the control lines or communication cables together with the main circuit lines or power
cables.
Keep a distance of 100mm or more between them.
Failure to do so may result in malfunction due to noise.
● 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 programmable
controller CPU.
If the power supply for the module loading station is turned off or the programmable controller 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 Precautions]
CAUTION
● Use the programmable controller in an environment that meets the general specifications in the user's
manual for the CPU module used.
Failure to do so may result in electric shock, fire, malfunction, or damage to or deterioration of the
product.
● To mount the module, while pressing the module mounting lever located in the lower part of the
module, fully insert the module fixing projection(s) into the hole(s) in the base unit and press the
module until it snaps into place.
Incorrect interconnection may cause malfunction, failure, or drop of the module.
When using the programmable controller in an environment of frequent vibrations, fix the module with
a screw.
● Tighten the screws within the specified torque range.
Undertightening can cause drop of the screw, short circuit, or malfunction.
Overtightening can damage the screw and/or module, resulting in drop, short circuit, or malfunction.
● Shut off the external power supply (all phases) used in the system before mounting or removing a
module.
Failure to do so may result in damage to the product.
● Do not directly touch any conductive parts and electronic components of the module.
Doing so can cause malfunction or failure of the module.
3
[Wiring Precautions]
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.
Incomplete connections may cause short circuit, fire, or malfunction.
● Securely connect the connector to the module.
● Place the cables in a duct or clamp them.
If not, dangling cable may swing or inadvertently be pulled, resulting in damage to the module or
cables or malfunction due to poor contact.
● Check the interface type and correctly connect the cable. Incorrect wiring (connecting the cable to an
incorrect interface) may cause failure of the module and external device.
● Tighten the terminal screws within the specified torque range.
Undertightening the terminal screws can cause short circuit or malfunction.
Overtightening can damage the screw and/or module, resulting in drop, short circuit, or malfunction.
● When disconnecting the cable from the module, do not pull the cable by the cable part.
For the cable with connector, hold the connector by hand and pull it out.
For the cable connected to the terminal block, loosen the terminal block screws. Failure to do so may
result in malfunction and damage to the module or cable.
● Prevent foreign matter such as dust or wire chips from entering the module.
Such foreign matter can cause a fire, failure, or malfunction.
● A protective film is attached to the top of the module to prevent foreign matter, such as wire chips,
from entering the module during wiring.
Do not remove the film during wiring.
Remove it for heat dissipation before system operation.
4
[Startup and Maintenance Precautions]
CAUTION
● Do not disassemble or modify the modules. Doing so may cause failure, malfunction, injury, or a fire.
● Shut off the external power supply (all phases) used in the system before mounting or removing a
module.
Failure to do so may cause the module to fail or malfunction.
● After the first use of the product, do not mount/remove the module to/from the base unit, and the
terminal block to/from the module more than 50 times (IEC 61131-2 compliant) respectively.
Exceeding the limit may cause malfunction.
● Do not touch any terminal while power is on.
Doing so may cause malfunction.
● Shut off the external power supply (all phases) used in the system before cleaning the module or
retightening the terminal screws or module fixing screws.
Failure to do so may cause the module to fail or malfunction.
Undertightening can cause drop of the screw, short circuit, or malfunction.
Overtightening can damage the screw and/or module, resulting in drop, short circuit, or malfunction.
● Before handling the module, touch a conducting object such as a grounded metal to discharge the
static electricity from the human body.
Failure to do so may cause the module to fail or malfunction.
[Operating Precautions]
CAUTION
● When changing data and operating status, and modifying program of the running programmable
controller from an external device such as a personal computer connected to an intelligent function
module, read relevant manuals carefully and ensure the safety before operation.
Failure to perform correct operations to change data, program, or the status may result in system
malfunction, machine damage, or an accident.
[Disposal Precautions]
CAUTION
● When disposing of this product, treat it as industrial waste.
5
When using the MELSEC-L series serial communication module
[Design Precautions]
WARNING
● For the operation status of each station at communication error in each station, refer to the respective
manual for each station.
Incorrect output or malfunction due to a communication failure may result in an accident.
● When connecting a peripheral with the CPU module or connecting an external device, such as a
personal computer, with an intelligent function module to modify data of a running programmable
controller, configure an interlock circuit in the program to ensure that the entire system will always
operate safely.
For other forms of control (such as program modification or operating status change) of a running
programmable controller, read the relevant manuals carefully and ensure that the operation is safe
before proceeding.
Especially, when a remote programmable controller is controlled by an external device, immediate
action cannot be taken if a problem occurs in the programmable controller due to a communication
failure.
To prevent this, configure an interlock circuit in the program, and determine corrective actions to be
taken between the external device and CPU module in case of a communication failure.
● Do not write any data to the "system area" of the buffer memory in the intelligent function module.
Also, do not use any "use prohibited" signals as an output signal from the CPU module to the
intelligent function module.
Doing so may cause malfunction of the programmable controller system.
[Design Precautions]
CAUTION
● Do not install the control lines or communication cables together with the main circuit lines or power
cables.
Keep a distance of 100mm or more between them.
Failure to do so may result in malfunction due to noise.
[Installation Precautions]
WARNING
● Shut off the external power supply (all phases) used in the system before mounting or removing a
module.
Failure to do so may result in electric shock or cause the module to fail or malfunction.
6
[Installation Precautions]
CAUTION
● Use the programmable controller in an environment that meets the general specifications in the
MELSEC-L CPU Module User's Manual (Hardware Design, Maintenance and Inspection).
Failure to do so may result in electric shock, fire, malfunction, or damage to or deterioration of the
product.
● To interconnect modules, engage the respective connectors and securely lock the module joint levers.
Incorrect interconnection may cause malfunction, failure, or drop of the module.
● Do not directly touch any conductive parts and electronic components of the module.
Doing so can cause malfunction or failure of the module.
[Wiring Precautions]
WARNING
● Shut off the external power supply (all phases) used in the system before wiring.
Failure to do so may result in electric shock or cause the module to fail or malfunction.
● After installation and wiring, attach the included terminal cover to the module before turning it on for
operation.
Failure to do so may result in electric shock.
7
[Wiring Precautions]
CAUTION
● Use applicable solderless terminals and tighten them within the specified torque range.
If any spade solderless terminal is used, it may be disconnected when a terminal block screw
comes loose, resulting in failure.
● Connectors for external devices must be crimped or pressed with the tool specified by the
manufacturer, or must be correctly soldered.
Incomplete connections may cause short circuit, fire, or malfunction.
● Securely connect the connector to the module.
● Place the cables in a duct or clamp them.
If not, dangling cable may swing or inadvertently be pulled, resulting in damage to the module or
cables or malfunction due to poor contact.
● Check the interface type and correctly connect the cable. Incorrect wiring (connecting the cable to
an incorrect interface) may cause failure of the module and external device.
● Tighten the terminal block screws within the specified torque range.
Undertightening can cause short circuit, fire, or malfunction.
Overtightening can damage the screw and/or module, resulting in drop, short circuit, fire, or
malfunction.
● When disconnecting the cable from the module, do not pull the cable by the cable part.
For the cable with connector, hold the connector part of the cable.
For the cable connected to the terminal block, loosen the terminal screw.
Failure to do so may result in malfunction and damage to the module or cable.
● Prevent foreign matter such as dust or wire chips from entering the module.
Such foreign matter can cause a fire, failure, or malfunction.
● A protective film is attached to the top of the module to prevent foreign matter, such as wire chips,
from entering the module during wiring.
Do not remove the film during wiring.
Remove it for heat dissipation before system operation.
8
[Startup and Maintenance Precautions]
WARNING
● Do not touch any terminal while power is on. Doing so will cause electric shock or malfunction.
● Shut off the external power supply (all phases) used in the system before cleaning the module or
retightening the terminal block screws.
Failure to do so may result in electric shock.
[Startup and Maintenance Precautions]
CAUTION
● Do not disassemble or modify the modules. Doing so may cause failure, malfunction, injury, or a fire.
● Shut off the external power supply (all phases) used in the system before mounting or removing a
module.
Failure to do so may cause the module to fail or malfunction.
● Tighten the terminal block screws within the specified torque range.
Undertightening can cause drop of the component or wire, short circuit, or malfunction.
Overtightening can damage the screw and/or module, resulting in drop, short circuit, or malfunction.
● After the first use of the product (module, display unit, and terminal block), the number of
connections/disconnections is limited to 50 times (in accordance with IEC 61131-2).
Exceeding the limit may cause malfunction.
● Before handling the module, touch a conducting object such as a grounded metal to discharge the
static electricity from the human body.
Failure to do so may cause the module to fail or malfunction.
9
[Operating Precautions]
CAUTION
● When changing data and operating status, and modifying program of the running programmable
controller from an external device such as a personal computer connected to an intelligent function
module, read relevant manuals carefully and ensure the safety before operation.
Incorrect data change, program modification, and status control may cause malfunction of the system,
mechanical damage, or accidents.
● While set values in the buffer memory are being registered to the flash ROM in the module, do not
turn off the power to the module and do not reset the CPU module.
Doing so will affect the flash ROM data, and setting to the buffer memory and registration to the flash
ROM need to be performed again. Also, this may cause failure and malfunction of the module.
[Disposal Precautions]
CAUTION
● When disposing of this product, treat it as industrial waste.
10
CONDITIONS OF USE FOR THE PRODUCT
(1) Mitsubishi programmable controller ("the PRODUCT") shall be used in conditions;
i) where any problem, fault or failure occurring in the PRODUCT, if any, shall not lead to any major or serious accident;
and
ii) where the backup and fail-safe function are systematically or automatically provided outside of the PRODUCT for the
case of any problem, fault or failure occurring in the PRODUCT.
(2) The PRODUCT has been designed and manufactured for the purpose of being used in general industries.
MITSUBISHI SHALL HAVE NO RESPONSIBILITY OR LIABILITY (INCLUDING, BUT NOT LIMITED TO ANY AND ALL
RESPONSIBILITY OR LIABILITY BASED ON CONTRACT, WARRANTY, TORT, PRODUCT LIABILITY) FOR ANY
INJURY OR DEATH TO PERSONS OR LOSS OR DAMAGE TO PROPERTY CAUSED BY the PRODUCT THAT ARE
OPERATED OR USED IN APPLICATION NOT INTENDED OR EXCLUDED BY INSTRUCTIONS, PRECAUTIONS, OR
WARNING CONTAINED IN MITSUBISHI'S USER, INSTRUCTION AND/OR SAFETY MANUALS, TECHNICAL
BULLETINS AND GUIDELINES FOR the PRODUCT.
("Prohibited Application")
Prohibited Applications include, but not limited to, the use of the PRODUCT in;
• Nuclear Power Plants and any other power plants operated by Power companies, and/or any other cases in which the
public could be affected if any problem or fault occurs in the PRODUCT.
• Railway companies or Public service purposes, and/or any other cases in which establishment of a special quality
assurance system is required by the Purchaser or End User.
• Aircraft or Aerospace, Medical applications, Train equipment, transport equipment such as Elevator and Escalator,
Incineration and Fuel devices, Vehicles, Manned transportation, Equipment for Recreation and Amusement, and
Safety devices, handling of Nuclear or Hazardous Materials or Chemicals, Mining and Drilling, and/or other
applications where there is a significant risk of injury to the public or property.
Notwithstanding the above, restrictions Mitsubishi may in its sole discretion, authorize use of the PRODUCT in one or
more of the Prohibited Applications, provided that the usage of the PRODUCT is limited only for the specific
applications agreed to by Mitsubishi and provided further that no special quality assurance or fail-safe, redundant or
other safety features which exceed the general specifications of the PRODUCTs are required. For details, please
contact the Mitsubishi representative in your region.
11
INTRODUCTION
Thank you for purchasing the Mitsubishi MELSEC-Q or -L series programmable controllers.
This manual explains the functions and programming required to use the serial communication module.
Before using this product, please read this manual and the relevant manuals carefully and develop familiarity with the
functions and performance of the MELSEC-Q or -L series programmable controller to handle the product correctly.
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.
Please make sure that the end users read this manual.
● To use LJ71C24 and LJ71C24-R2 serial communication modules
When reading the manual, substitute the contents in the table with the following descriptions in the explanations.
Description in manual
After substitution
Q series C24
L series C24
QCPU
LCPU
QCPU station
LCPU station
Q/QnACPU
Q/L/QnACPU
The specifications of MELSEC-L series and MELSEC-Q series are partially different.
Before using the equipment, please refer to the following to gain familiarity with the different in specifications.
 Page 411, Appendix 1
Remark
● The program examples shown in this manual are the examples in which the serial communication module is assigned to
the I/O No. X/Y00 to X/Y1F unless otherwise specified. For the assignment of I/O No., refer to the user's manual (function
explanation, program fundamentals) for the CPU module used.
● This manual explains operations by using GX Configurator-SC.
12
COMPLIANCE WITH EMC AND LOW VOLTAGE
DIRECTIVES
(1) Method of ensuring compliance
To ensure that Mitsubishi programmable controllers maintain EMC and Low Voltage Directives when incorporated
into other machinery or equipment, certain measures may be necessary. Please refer to one of the following
manuals.
• QCPU User's Manual (Hardware Design, Maintenance and Inspection)
• Safety Guidelines
(This manual is included with the CPU module or base unit.)
The CE mark on the side of the programmable controller indicates compliance with EMC and Low Voltage
Directives.
(2) Additional measures
No additional measures are necessary for compliance of this product with the EMC and Low Voltage Directives.
13
CONTENTS
CONTENTS
SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
CONDITIONS OF USE FOR THE PRODUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
COMPLIANCE WITH EMC AND LOW VOLTAGE DIRECTIVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
RELEVANT MANUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
MANUAL'S USE AND STRUCTURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
GENERIC TERMS AND ABBREVIATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
CHAPTER 1 OVERVIEW
1.1
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.2
Functions Added/Changed for the QJ71C24N (-R2/R4) and QJ71C24 (-R2) . . . . . . . . . . . . . 33
CHAPTER 2 USING THE PROGRAMMABLE CONTROLLER CPU MONITORING
FUNCTION
2.1
2.2
2.3
2.4
3.1
3.2
3.3
34
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
About the Programmable Controller CPU Monitoring Function . . . . . . . . . . . . . . . . . . . . . . . . 36
2.2.1
Data registration for using the programmable controller CPU monitoring function . . . . . . . . .36
2.2.2
Programmable controller CPU monitoring information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
2.2.3
Timing for programmable controller CPU monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
2.2.4
Timings of transmission and notification of monitoring results to the external device . . . . . . .41
2.2.5
Transmission methods of monitoring results and transmission data to the external device . .44
2.2.6
Execution sequence for using the programmable controller CPU monitoring function . . . . . .57
Settings for Using the Programmable Controller CPU Monitoring Function . . . . . . . . . . . . . . . 58
2.3.1
System setting items for the programmable controller CPU monitoring function. . . . . . . . . . .58
2.3.2
How to register and cancel the programmable controller CPU monitoring function. . . . . . . . .64
Precautionary Notes for Using the Programmable Controller CPU Monitoring Function . . . . . 67
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
14
27
69
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
3.1.1
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
3.1.2
Function list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
3.1.3
Comparisons with related devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
3.2.1
System configuration when performing data communication with an external device . . . . . . .76
3.2.2
System configuration when using the notification function. . . . . . . . . . . . . . . . . . . . . . . . . . . .78
3.2.3
System configuration when connecting GX Developer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
3.2.4
Precautions for system configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
3.3.1
Transmission specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
3.3.2
Specification of connectable modems/TAs (terminal adapters) . . . . . . . . . . . . . . . . . . . . . . . .83
3.3.3
Compatibility with the QCPU remote password function . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86
3.3.4
Compatibility with the callback function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92
3.3.5
List of I/O signals for the modem function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102
3.3.6
Buffer memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
3.3.7
Precautions when using the modem function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120
3.4
Start-up of the Modem Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
3.4.1
3.5
Start-up procedures when communicating data with external devices . . . . . . . . . . . . . . . . .126
3.4.2
Initial settings of the serial communication module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131
3.4.3
Register/read/delete of the initialization data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134
3.4.4
Register/read/delete of the data for connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139
3.4.5
Initialization of modem/TA (terminal adapter). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144
3.4.6
Line connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148
3.4.7
Data communication and notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154
3.4.8
Line disconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161
Sample Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
3.5.1
Sample program for data communication-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165
3.5.2
Sample program for data communication-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171
3.5.3
Sample program for notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180
CHAPTER 4 RECEIVING DATA WITH AN INTERRUPT PROGRAM
184
4.1
Settings for Receiving Data Using an Interrupt Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
4.2
Interrupt Program Startup Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
4.3
Reception Control Method Using an Interrupt Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
4.4
Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
4.4.1
Program example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188
4.4.2
Precautions when receiving data with an interrupt program . . . . . . . . . . . . . . . . . . . . . . . . .190
CHAPTER 5 CHANGING SEND AND RECEIVE DATA LENGTH UNITS
TO BYTE UNITS (WORD/BYTES UNITS SETTING)
192
CHAPTER 6 CHANGING THE DATA COMMUNICATIONS MONITORING TIMES
194
6.1
No-reception Monitoring Time (timer 0) Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
6.2
Response Monitoring Time (timer 1) Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
6.3
Transmission Monitoring Time (timer 2) Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
6.4
Message Wait Time Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
CHAPTER 7 DATA COMMUNICATIONS USING DC CODE TRANSMISSION
CONTROL
203
7.1
Control Contents of DTR/DSR (ER/DR) Signal Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
7.2
Control Contents of DC Code Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
7.3
Precautions when Using the Transmission Control Functions . . . . . . . . . . . . . . . . . . . . . . . . 210
CHAPTER 8 DATA COMMUNICATIONS USING HALF-DUPLEX
COMMUNICATIONS
212
8.1
Half-duplex Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
8.2
Data Transmission and Reception Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
8.3
Changing the Communication System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
8.4
Connector Connections for Half-duplex Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
8.5
Half-duplex Communications Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
15
CHAPTER 9 CONTENTS AND REGISTRATION OF THE USER FRAMES
FOR DATA COMMUNICATION
9.1
220
User Frame Types and Contents During Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
9.1.1
User frames to be registered and used by the user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221
9.1.2
Default registration frame (read only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .230
9.2
Transmission/Reception Processing Using User Frame Register Data . . . . . . . . . . . . . . . . . 231
9.3
Precautions when Registering, Reading, Deleting and Using User Frames . . . . . . . . . . . . . 235
9.4
Register/Read/Delete User Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
9.4.1
Registering user frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240
9.4.2
Reading user frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241
9.4.3
Deleting user frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242
CHAPTER 10 ON-DEMAND DATA COMMUNICATIONS USING USER FRAMES
243
10.1
User Frame Data Communications Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
10.2
User Frame Types and Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
10.3
User Frame On-Demand Data Transmission and Buffer Memory Used . . . . . . . . . . . . . . . . 244
10.4
On-Demand Function Control Procedure During User Frame Use . . . . . . . . . . . . . . . . . . . . 246
10.4.1 Data communication using the ASCII code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246
10.4.2 Data communications using the binary code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248
10.5
Example of an On-Demand Data Transmission Program Using User Frames. . . . . . . . . . . . 250
CHAPTER 11 DATA COMMUNICATIONS USING USER FRAMES
11.1
11.2
11.3
252
Overview of Data Communication Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Data Reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
11.2.1
About reception data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254
11.2.2
Timing for start/completion of data reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .262
11.2.3
Receive procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266
11.2.4
User frame setting for reception. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267
Receive Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
11.3.1
Sequence program example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273
11.3.2
Application example for data reception using a combination that specifies the first frame
11.3.3
Application example for data reception using a combination that does not specify
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278
the first frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284
11.4
11.5
Data Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
11.4.1
Send data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286
11.4.2
Transmission procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .288
11.4.3
Settings for transmission user frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289
Transmission Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
CHAPTER 12 TRANSPARENT CODES AND ADDITIONAL CODES
16
296
12.1
Handling the Transparent Code and Additional Code Data . . . . . . . . . . . . . . . . . . . . . . . . . . 296
12.2
Registering Transparent Codes and Additional Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
12.3
Handling Transparent Codes and Additional Codes during Non Procedure Protocol Data
Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
12.4
Example of Data Communication Using the Non Procedure Protocol . . . . . . . . . . . . . . . . . . 304
12.4.1 Example of data reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .305
12.4.2 Example of data transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .307
12.5
Handling Transparent Codes and Additional Codes During Bidirectional Protocol Data
Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
12.6
Example of Data Communication Using the Bidirectional Protocol . . . . . . . . . . . . . . . . . . . . 313
12.6.1 Example of data reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314
12.6.2 Example of data transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .317
CHAPTER 13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION) 319
13.1
ASCII-BIN Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
13.2
Settings for ASCII-BIN Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
13.3
Performing ASCII-BIN Conversion for Data Communicated via Non Procedure Protocol . . . 321
13.4
Example of Data Communication Using the Non Procedure Protocol . . . . . . . . . . . . . . . . . . 323
13.4.1 Example of data reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .324
13.4.2 Example of data transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327
13.5
Performing ASCII-BIN Conversion for Data Communicated via the Bidirectional Protocol . . 329
13.6
Example of Data Communication Using the Bidirectional Protocol . . . . . . . . . . . . . . . . . . . . 331
13.6.1 Example of data reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .332
13.6.2 Example of data transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .333
CHAPTER 14 DATA COMMUNICATIONS USING EXTERNAL DEVICE AND
PROGRAMMABLE CONTROLLER CPU M : N CONFIGURATION
14.1
14.2
334
Data Communications Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
External Devices Interlock Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
14.2.1 Maximum communications time per external device station . . . . . . . . . . . . . . . . . . . . . . . . .336
14.2.2 Message structure when communicating data between external devices . . . . . . . . . . . . . . .337
14.3
Examples of Procedure for Data Communications with the Programmable Controller CPU
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
14.3.1 Sequential data communications between external devices and the programmable
controller CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .339
14.3.2 Data communications between programmable controller CPU and external devices
by designating a master station and slave stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .342
CHAPTER 15 SWITCHING THE MODE AFTER STARTING
15.1
345
Mode Switching Operation and Contents that can be Changed. . . . . . . . . . . . . . . . . . . . . . . 347
15.1.1 Settings that can be changed with mode switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .347
15.1.2 Operation for mode switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .348
15.2
Mode Switching Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
15.3
I/O Signals for Handshake with Programmable Controller CPU and Buffer Memory . . . . . . . 350
15.4
Switching the Mode from the Programmable Controller CPU . . . . . . . . . . . . . . . . . . . . . . . . 354
15.4.1 Mode switching procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .354
15.4.2 Mode switching sample program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .355
17
15.5
Switching the Mode from an External Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
15.5.1 Mode switching procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .356
15.5.2 Mode switching sample program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .357
CHAPTER 16 USING COMMUNICATION DATA MONITORING FUNCTION
16.1
358
Communication Data Monitoring Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
16.1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .358
16.1.2 Communication data monitoring operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .359
16.2
Communication Data Monitoring Function Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
16.3
Communication Data Monitoring Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
CHAPTER 17 DEDICATED INSTRUCTIONS
369
17.1
Dedicated Instruction List and Available Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
17.2
Z.BUFRCVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
17.2.1 Setting data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .371
17.2.2 Receive data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .371
17.2.3 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .372
17.2.4 Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .372
17.2.5 Precaution when using the BUFRCVS instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .373
17.2.6 Program example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .374
17.3
ZP.CSET (Programmable Controller CPU Monitoring Register/Cancel) . . . . . . . . . . . . . . . . 375
17.3.1 Setting data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .375
17.3.2 Control data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .376
17.3.3 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .379
17.3.4 Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .381
17.3.5 Program example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .382
17.4
ZP.CSET (Initial Settings) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
17.4.1 Setting data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .384
17.4.2 Control data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .385
17.4.3 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .386
17.4.4 Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .388
17.4.5 Program example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .388
17.5
G(P).GETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
17.5.1 Setting data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .389
17.5.2 Control data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .390
17.5.3 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .390
17.5.4 Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .392
17.5.5 Program example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .392
17.6
G(P).PRR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
17.6.1 Setting data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .393
17.6.2 Control data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .394
17.6.3 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395
17.6.4 Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .396
17.6.5 Program example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .397
17.7
G(P).PUTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
17.7.1 Setting data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .398
18
17.7.2 Control data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .398
17.7.3 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .399
17.7.4 Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .401
17.7.5 Program example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .401
17.8
ZP.UINI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
17.8.1 Setting data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .402
17.8.2 Control data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .402
17.8.3 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .405
17.8.4 Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .406
17.8.5 Program example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .407
17.8.6 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .409
APPENDIX
411
Appendix 1 Specification Comparison between the Q Series C24 and L series C24 . . . . . . . . . . . 411
INDEX
413
REVISIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
WARRANTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
19
RELEVANT MANUALS
The specifications and usage of special functions can be checked in this manual.
In addition, use the following manuals according to their intended use.
Manual name
Manual number
(Model code)
Q Corresponding Serial Communication Module User's Manual (Basic)
Overview of the module, applicable system configuration, specifications, procedures prior to operations, basic methods for
communicating with the external device, maintenance and inspection, and troubleshooting of the Q series serial communication
module.
(Sold separately)
SH-080006
(13JL86)
MELSEC-L Serial Communication Module User's Manual (Basic)
Overview of the module, applicable system configuration, specifications, procedures prior to operations, basic methods for
communicating with the external device, maintenance and inspection, and troubleshooting of the MELSEC-L serial communication
module.
(Sold separately)
SH-080894ENG
(13JZ40)
MELSEC Communication Protocol Reference Manual
Information on how the external device reads data from and writes data to the programmable controller CPU through
communication using the MC protocol by utilizing the serial communication module or Ethernet interface module.
(Sold separately)
SH-080008
(13JF89)
GX Configurator-SC Version 2 Operating Manual (Protocol FB support function)
Features and usage of the protocol FB support function that supports creation of the data communication program of the serial
communication module and how to set parameters.
(Sold separately)
SH-080393E
(13JU46)
GX Configurator-SC Version 2 Operating Manual (Pre-defined protocol support function)
The pre-defined protocol support function and usage of the serial communication module, and the protocol setting method.
(Sold separately)
SH-080850ENG
(13JU66)
20
MANUAL'S USE AND STRUCTURE
(1) How to use this manual
This manual describes the use of special functions for the Q series C24 (QJ71C24N, QJ71C24N-R2, QJ71C24NR4, QJ71C24, QJ71C24-R2), with each chapter covering a specific function.
Please read this manual and use the contents below as a reference.
(a) To read an overview of special functions
An overview of the major special functions is described in Chapter 1.
(b) To use the function that monitors errors in the programmable controller CPU
• Chapter 2 describes the programmable controller CPU monitoring function, which monitors the
programmable controller CPU status and devices and automatically sends status information to the other
communicating device upon occurrence of an error.
• For how to register/cancel the programmable controller CPU monitoring from the external device using the
MC protocol, refer to the MELSEC Communication Protocol Reference Manual.
(c) To use the data communication function for the exchange of data with an external
device at a remote location
Chapter 3 describes the specifications, procedures and other items regarding communication using the modem
function in order to exchange of data with an external device at a remote location.
(d) To use the function for reading received data from the external device using an
interrupt program in order to reduce the scan time
Chapter 4 describes the programming for execution of a receiving program only when data from the external
device is received.
(e) To use the function for monitoring the data communication time with the external
device
Chapter 6 describes the function that monitors the data communication time with the external device, along
with the reception-interval time and the response-reception time for transmission.
(f) To use the transmission control function to control data transmission/reception with
the external device
Chapter 7 describes the DTR/DSR control and the DC code function to control the data communication with the
external device.
(g) To use the function for simplifying the data communication program with the
registration data when preregistering the fixed-format section of the communication
message
Chapters 9 to 11 describe the data transmission/reception function with user frames in which the fixed-format
section of the communication message has been preregistered.
21
(h) To use the function that performs the data communication in ASCII code with the
external device
Chapter 13 describes the handling of binary code on the programmable controller CPU and ASCII-BIN
conversion function for communicating ASCII code data for an external device.
(i) To use dedicated instructions
Chapter 17 describes the dedicated instructions that are used to execute the functions explained in this
manual.
(2) Structure of this manual
This manual describes how to perform the initial settings to execute special functions by using GX Developer and
the utility package for the Q series C24 (GX Configurator-SC).
For details on the usage of GX Developer and GX Configurator-SC, refer to the Q Corresponding Serial
Communication Module User's Manual (Basic).
22
GENERIC TERMS AND ABBREVIATIONS
In this manual, the following generic terms and abbreviations are used to explain the serial communication module and
data communication devices, unless otherwise specified. Specific names or model names are provided when it is
necessary to explicitly identify the model being discussed.
(1) Generic terms and abbreviations for modules
Term
Q series C24 (C24)
Description
Generic term for QJ71C24N, QJ71C24N-R2, QJ71C24N-R4, QJ71C24 and QJ71C24-R2 serial communication
modules.
(Indicated as "C24" in diagrams)
L series C24
Generic term for LJ71C24 and LJ71C24-R2
QC24
Generic term for AJ71QC24, AJ71QC24-R2, AJ71QC24-R4, A1SJ71QC24, and A1SJ71QC24-R2
QC24N
Generic term for AJ71QC24N, AJ71QC24N-R2, AJ71QC24N-R4, A1SJ71QC24N1, A1SJ71QC24N1-R2,
A1SJ71QC24N, and A1SJ71QC24N-R2
QC24(N)
Generic term for QC24 and QC24N
Generic term for the modules below.
Q series
Serial communication module
UC24
A series computer link module
QJ71C24N, QJ71C24N-R2, QJ71C24N-R4, QJ71C24, QJ71C24-R2
L series
LJ71C24, LJ71C24-R2
QnA series
AJ71QC24, AJ71QC24-R2, AJ71QC24-R4, A1SJ71QC24, A1SJ71QC24-R2,
AJ71QC24N, AJ71QC24N-R2, AJ71QC24N-R4, A1SJ71QC24N1,
A1SJ71QC24N1-R2, A1SJ71QC24N, A1SJ71QC24N-R2
Generic term for AJ71UC24, A1SJ71UC24-R2, A1SJ71UC24-R4, A1SJ71UC24-PRF, A1SJ71C24-R2,
A1SJ71C24-R4, A1SJ71C24-PRF, A2CCPUC24, and A2CCPUC24-PRF
Generic term for Q00JCPU, Q00UJCPU, Q00CPU, Q00UCPU, Q01CPU, Q01UCPU, Q02CPU,
Q02HCPU, Q02PHCPU, Q02UCPU, Q03UDCPU, Q03UDECPU, Q03UDVCPU, Q04UDHCPU,
Q04UDEHCPU, Q04UDVCPU, Q06HCPU, Q06PHCPU, Q06UDHCPU, Q06UDEHCPU,
QCPU
Q06UDVCPU, Q10UDHCPU, Q10UDEHCPU, Q12HCPU, Q12PHCPU, Q12PRHCPU,
Q13UDHCPU, Q13UDEHCPU, Q13UDVCPU, Q20UDHCPU, Q20UDEHCPU, Q25HCPU,
Q25PHCPU, Q25PRHCPU, Q26UDHCPU, Q26UDEHCPU, Q26UDVCPU, Q50UDEHCPU, and
Q100UDEHCPU
LCPU
QnACPU
Generic term for L02CPU, L02CPU-P, L26CPU-BT, and L26CPU-PBT
Generic term for Q2ACPU, Q2ACPU-S1, Q2ASCPU, Q2ASCPU-S1, Q2ASHCPU, Q2ASHCPUS1, Q3ACPU, Q4ACPU, and Q4ARCPU
Q/QnACPU
Generic term for QCPU and QnACPU
Ethernet module
Q series E71 (E71)
Generic term for QJ71E71-100, QJ71E71-B5 and QJ71E71-B2 Ethernet interface modules
(Indicated as "E71" in diagrams)
23
(2) Abbreviations for dedicated instructions
Term
BIDIN
Description
Abbreviation for G.BIDIN or GP.BIDIN.
BIDOUT
Abbreviation for G.BIDOUT or GP.BIDOUT.
BUFRCVS
Abbreviation for Z.BUFRCVS.
CPRTCL
Abbreviation for G.CPRTCL or GP.CPRTCL
CSET
Abbreviation for ZP.CSET.
GETE
Abbreviation for G.GETE or GP.GETE.
INPUT
Abbreviation for G.INPUT.
ONDEMAND
Abbreviation for G.ONDEMAND or GP.ONDEMAND.
OUTPUT
Abbreviation for G.OUTPUT or GP.OUTPUT.
PRR
Abbreviation for G.PRR or GP.PRR.
PUTE
Abbreviation for G.PUTE or GP.PUTE.
SPBUSY
Abbreviation for G.SPBUSY or GP.SPBUSY.
UINI
Abbreviation for ZP.UINI.
(3) Generic terms and abbreviations for the manuals
Term
Description
User's Manual (Basic)
Q Corresponding Serial Communication Module User's Manual (Basic)
MELSEC-L Serial Communication Module User's Manual (Basic)
Operating Manual
(Protocol FB support function)
GX Configurator-SC Version 2 Operating Manual (Protocol FB support function)
Operating Manual
(Pre-defined protocol support function)
GX Configurator-SC Version 2 Operating Manual (Pre-defined protocol support function)
(4) Others
Term
Description
Data communication function
Generic term for MC protocol, pre-defined protocol, nonprocedural protocol, bidirectional protocol
QCPU station
Generic term for the programmable controller installed QCPU
LCPU station
Generic term for the programmable controller installed LCPU
24
TERMS
The following table lists the definitions and descriptions of terminology used in this manual.
Term
Description
A compatible 1C frame
(Formats 1 to 4)
One of the message formats for the serial communication modules, which is used to perform ASCII data communication by
MC protocol.
This is the same message format as the one used when communicating using the protocol for the A series computer link
modules.
Device memory read/write operations for the QCPU are allowed within the device range of the AnACPU.
Bidirectional protocol
A communication procedure for the serial communication modules, with which any data communication is available
between the programmable controller CPU and the other device.
Buffer memory
Memory of the intelligent function modules/special function modules, which is used for storing data sent to or received from
the programmable controller CPU (setting values, monitor values, etc.)
Device
A memory of the programmable controller CPU used for storing data
GX Configurator-SC
Setting and monitoring tool for the serial communication module (MELSOFT product)
GX Developer
A programming tool for designing, debugging and maintenance (MELSOFT product)
Independent operation
Operation of each of the two interfaces on the serial communication module when data communication is performed with
other devices using the specified protocols respectively.
Intelligent function module
MELSEC-Q/L series modules with functions other than I/O functions such as A/D and D/A conversion module
Linked operation
Operation of each of the two interfaces on the serial communication module that are connected to external devices and
linked one another in order to communicate data to/from the external devices.
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 pre-defined protocol or
the bidirectional protocol is not allowed.)
MELSEC communication
protocol
(MC protocol)
A communication procedure for the Q series C24 or the Ethernet interface modules, and a communication method for
accessing a programmable controller CPU from an external device.
(This is called the MC protocol in this manual.)
There are two communication types; one uses ASCII code data and the other uses binary code data.
Message send function
(Printer function)
This function registers character data (messages) to be sent to external devices (mainly printers) to the serial
communication module as a user frame in advance, and sends the registered data for multiple user frames using the non
procedure protocol.
Multidrop connection
A name of the connection when multiple external devices or other C24s are connected on a 1:n or m:n basis using the
serial communication module's RS-422/485 interface.
MX Component
Active X control library for serial communication (MELSOFT product)
Non procedure protocol
A communication procedure and one of the data communication functions for communicating any data between the
programmable controller CPU and the other device.
Packet
Data string used for communication using pre-defined protocol with external devices
Pre-defined protocol
One of the data communication functions available for the QJ71C24N(-R2/R4) and LJ71C24(-R2). In data communication
between the QJ71C24N(-R2/R4) or LJ71C24(-R2) and an external device, data can be sent or received by using a protocol
for the external device.
This must be set in GX Configurator-SC (Pre-defined protocol support function).
Pre-defined protocol support
function
This function can be used in GX Configurator-SC (Pre-defined protocol support function).
The functional overview of the pre-defined protocol support function is indicated below.
• Protocol setting according to the opposite device
• The writing and reading of protocol setting data to QJ71C24N(-R2/R4) and LJ71C24(-R2) flash ROM
• Debugging support function
QnA compatible 2C frame
(Formats 1 to 4)
One of the message formats for the serial communication modules, which is used to perform ASCII data communication by
MC protocol.
This is the same message format as the communication frame using the protocol for the QnA series serial communication
modules.
• QnA compatible 2C frame (Formats 1 to 4): QnA simplified frame (Formats 1 to 4)
QnA compatible 3C frame
(Formats 1 to 4)
QnA compatible 4C frame
(Formats 1 to 4)
One of the message formats for the serial communication modules, which is used to perform ASCII data communication by
MC protocol.
This is the same message format as the communication frame using the protocol for the QnA series serial communication
modules.
• QnA compatible 3C frame (Formats 1 to 4): QnA frame (Formats 1 to 4)
• QnA compatible 4C frame (Formats 1 to 4): QnA extension frame (Formats 1 to 4)
25
Term
QnA compatible 4C frame
(Format 5)
Description
One of the message formats for the serial communication modules, which is used to perform ASCII data communication by
MC protocol.
This is the same message format as the communication frame using the protocol for the QnA series serial communication
modules.
• QnA compatible 4C frame (Format 5): QnA extension frame (Format 5)
Special function module
MELSEC-QnA/A series modules with functions other than I/O functions such as A/D and D/A conversion module
User frame
Data name when the fixed format portion of messages to be sent or received between a serial communication module and
an external device is registered in the module and used for sending and receiving data. (The contents of a user frame data
should conform to the specifications of the external device.)
The data array of the head and tail sections of a message (transmission control code, serial communication module station
No., sum check, fixed data, etc.) to be sent and received is registered in the serial communication module before use.
User frame is used in MC protocol on-demand functions and data communication functions which use the non procedure
protocol.
26
CHAPTER 1 OVERVIEW
CHAPTER 1
1.1
OVERVIEW
1
Overview
This manual explains special functions of the MELSEC-Q/L series C24.
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.
This chapter provides an overview of these special functions.
The primary special functions of the Q series C24 and a functional overview are indicated below.
(1) Monitoring the programmable controller CPU ( Page 34, CHAPTER 2)
(a) The local station programmable controller CPU can be monitored at time intervals
set by the user without a sequence program.
• The following information can be registered as items to be monitored. (Monitoring a device for the local
station programmable controller CPU)
• A numeric value stored in a word device
• The ON/OFF status of a bit device (Monitoring the status of the local station programmable controller
CPU)
• Monitoring the status of the local station programmable controller CPU
• For the results of the programmable controller CPU monitoring, the following monitored information can be
transmitted/notified.
• Transmission of information on the device to be monitored and status of the programmable controller CPU
• Notification of notification messages (character string data) registered for connecting the modem function
when using with the modem function together
• The user can select one of the following as transmission timing for the programmable controller CPU
monitoring results to the external device.
• Transmission/notification each time the programmable controller CPU is monitored. (Constant cycle
transmission)
• Transmission/notification when the information read from the programmable controller CPU agrees with
conditions set by the user. (Condition agreement transmission)
27
1.1 Overview
(Monitoring information obtained through combined use of the modem function can also be transmitted.)
(b) The programmable controller CPU monitoring function can be used in
communication using MC protocol or non procedure protocol.
(c) Using the programmable controller CPU monitoring function makes it possible to do
the following:
• Sends device data without using a sequence program
• Simplifies the device monitor procedure
• Sends the programmable controller CPU error information
Q25HCPU
MELSEC
POWER
MODE
QJ71C24
CH1.
External device
CH2.
RUN
ERR.
CH1.
USER
BAT.
BOOT
RS-232
CPU error
information
Monitoring
device information
PULL
USB
Abnormal detection
RS-232
MITSUBISHI
Error
occurrence
(2) Communicating with the external device at a remote location via a modem
( Page 69, CHAPTER 3)
(a) Connecting a modem or TA (terminal adapter) to the RS-232 interface facilitates
communication via a public line/private line/digital line (ISDN), such as data
communication with a device at a remote location (listed below) and calling a pager
device.
• Data communication using the MC protocol
• Data sending and receiving using the non procedure protocol
• Data communication using the bidirectional protocol
• Programmable controller access using the GX Developer
(b) Initialization of a modem or TA, line connection (dialing), and line disconnection are
performed by the programmable controller CPU.
28
CHAPTER 1 OVERVIEW
(c) When a remote password is set in the QCPU with the GX Developer, the following
access from the external device to QCPU using the Q series C24 modem function
1
can be performed by executing the unlock processing to the remote password. *1
• Data communication using the MC protocol
• Accessing the programmable controller using the GX Developer
*1
The remote password function is a QCPU function designed to prevent improper access to the QCPU by users. The
QCPU remote password function can be used by setting a remote password in the QCPU with GX Developer.
Q series C24
Modem/TA (*1)
Modem/TA (*1)
External device
RS-232
Pager receiver
*1 TA is an abbreviation for Terminal Adapter.
(3) Receiving data with an interrupt program ( Page 184, CHAPTER 4)
(a) In data communication between the Q series C24 and the external device, an
functions.
• Data reception during communication using the non procedure protocol
• Data reception during communication using the bidirectional protocol
(b) Receiving data using an interrupt program expedites data reception by the
programmable controller CPU.
Data
transmission
Q series C24
Receive
Interrupt issued
Main program
Programmable
controller CPU
Main program
Interrupt
program executed
FEND
SM400
I
BUFRCVS
29
1.1 Overview
interrupt program can be used to receive data for the following data communication
(4) Controlling data communication in accordance with the external device (
Page 203, CHAPTER 7)
(a) The Q series C24 controls data communication with the external device by turning
ON/OFF the DTR/DSR signal and sending/receiving the DC code.
(b) DTR/DSR signal control
Using the ER (DTR) and DR (DSR) signals, the external device is notified of whether or not data
communication can be performed.
(c) DC code control
By sending/receiving the DC1 and DC3 code data, the external device is notified of whether or not data can be
received. By enclosing the user data with the DC2 and DC4 code data, the external device is notified of the
valid transmission data range.
External
device side
Programmable
controller CPU
side
(Interruption)
(Restart)...From the succeeding data
Data 1-2
Data 1-1
Data 2-1
Data 2-2
(Interruption)
(Restart)... From the
succeeding
data
ER(DTR) signal
DR(DSR) signal
Programmable
controller CPU
side
Data 1-1
D
C
3
D
C
3
Data 2-1
D
C
1
(Restart)...From the succeeding data
(Interruption)
External
device side
Data 1-2
D
C
1
Data 2-2
(Interruption)
(Restart)... From the succeeding data
(5) Converting binary code data to ASCII code data to communicate with the
external device specification ( Page 319, CHAPTER 13)
(a) Binary code data that is processed by the programmable controller CPU can be
converted to ASCII code data for communication.
(b) ASCII-BIN conversion is performed by the Q series C24 according to user settings.
External
device
Q series C24
Buffer memory
H
L
1234H
30
L
H
34H 12H
(34H)
Converts
(12H)
Does not convert
Head data
L
(3)
H
(4)
(1)
(2)
33H 34H 31H 32H
CHAPTER 1 OVERVIEW
1
(6) Sending/receiving data in a message format tailored to the external device
( Page 220, CHAPTER 9 to Page 252, CHAPTER 11)
(a) By preregistering the data arrangement (user frames) of the messages to be sent
and received by the external device, to the Q series C24, the following data
communications can be performed using registered frames.
• MC protocol: Data transmission from the programmable controller CPU to the external device using the
on-demand function
• Non procedure protocol: Data communication between the programmable controller CPU and the external
device
(b) For example, multiple first frames and last frames (called user frames) with the
definition shown in the diagram below can be preregistered in the Q series C24.
When sending data to the external device, the data that is arranged as shown in the
diagram below can be sent by designating the preregistered user frame numbers
and arbitrary data. When receiving data from the external device, by setting the
preregistered user frame numbers for reception at the startup of the Q series C24,
the arbitrary data section can be read to the programmable controller CPU when the
Arbitrary data
CR
LF
Last frame
• Before sending data, the Q series C24 adds the first frame and last frame to arbitrary data. When data is
received, the arbitrary data section is stored in the buffer memory as receive data.
(c) User frames and various setting values for data communication with the external
device can be preregistered to the Q series C24 flash ROM.
31
1.1 Overview
First frame
Self-station
number
Destination
station number
ENQ
Password
message with the registered content is received.
The following table lists which special functions are available for the main data communication functions of the
Q series C24.
Main data communication functions
Special functions
Reference
section
MC protocol
Nonprocedural
protocol
Bidirectional
protocol
Pre-defined
protocol
Monitoring of the programmable controller CPU using the
programmable controller CPU monitoring function




Page 34,
CHAPTER 2
Data communication to a remote location using the
modem function




Page 69,
CHAPTER 3
Reading received data using an interrupt program




Page 184,
CHAPTER 4
Changing the unit of the data length for communication
data




Page 192,
CHAPTER 5
Changing the monitoring time for data communication




Page 194,
CHAPTER 6
Transmission control for data communication
• DC code control (Including Xon/Xoff control)
• DTR/DSR (ER/DR) control




Page 203,
CHAPTER 7
Data communication using half-duplex communication




Page 212,
CHAPTER 8




Page 220,
CHAPTER 9




Page 243,
CHAPTER 10




Page 252,
CHAPTER 11
Data communication using the transparent code




Page 296,
CHAPTER 12
Communication using ASCII code data by ASCII-BIN
conversion




Page 319,
CHAPTER 13
Data communication with multiple external devices using
a multi-drop connection (m:n connection)




Page 334,
CHAPTER 14
Changing the interface mode after starting data
communication (Changes to communication protocol and
transmission specifications)




Page 345,
CHAPTER 15
Registration
Data communication using user
frames
Transmission,
reception
: Available, : Not available
32
CHAPTER 1 OVERVIEW
1.2
Functions Added/Changed for the QJ71C24N (-R2/R4)
and QJ71C24 (-R2)
1
For the function versions, serial numbers, and software versions of the QJ71C24N(-R2/R4) or QJ71C24(-R2) with the
added or changed functions, refer to the following.
 Q Corresponding Serial Communication Module User's Manual (Basic)
1.2 Functions Added/Changed for the QJ71C24N (-R2/R4) and QJ71C24 (-R2)
33
CHAPTER 2
USING THE PROGRAMMABLE
CONTROLLER CPU MONITORING
FUNCTION
This chapter explains the programmable controller CPU monitoring function with which the Q series C24 monitors the
programmable controller CPU based on the monitoring information reregistered by the user.
2.1
Overview
The following explains an overview of the programmable controller CPU monitoring function:
(1) Transmission without using a sequence program
(a) The programmable controller CPU monitoring function enables the Q series C24 to
monitor the local station's programmable controller CPU at time intervals set by the
user by reregistering data to be used for the programmable controller CPU
monitoring function. Data transmission and notification to the external device is
possible by communication using the MC or non procedure protocol without using a
sequence program.
(b) The following monitoring information selected by the user can be sent or notified to
the external device as the programmable controller CPU monitoring results.
Item
Monitoring result
Data
transmission
Local station programmable
controller CPU device (information
on the device to be monitored)
Without the modem
function
Combined use of the
modem function
(modem
communication)




Numeric value stored in a word device
ON/OFF status for a bit device
Status of modules of the local station programmable controller CPU
Notification
Notification message registered in data for connection (character string data)
(c) Two separate timings--constant cycle transmission and condition agreement
transmission--are used to transmit and notify the programmable controller CPU
monitoring results to the external device.
• In the constant cycle transmission, transmission and notification are performed each time the programmable
controller CPU is monitored.
• In the condition agreement transmission, transmission and notification are performed when the information
read from the programmable controller CPU satisfies the user-defined conditions and an error is detected in
the programmable controller CPU.
34
CHAPTER 2 USING THE PROGRAMMABLE CONTROLLER CPU MONITORING FUNCTION
(2) Simplifying the device monitoring procedure
When device monitoring is performed by communication using the MC protocol, the external device must
repeatedly perform monitor request transmission and monitor data reception processing after it executes monitor
registration.
2
By designating the constant cycle transmission for the programmable controller CPU monitoring function, the
device data can be monitored without performing the monitor request reception processing.
(3) Notification of an error in the programmable controller CPU
In the condition agreement transmission and notification, error information can be sent to the external device
without a sequence program whenever a programmable controller CPU error occurs.
Q25HCPU
MELSEC
POWER
MODE
RUN
ERR.
USER
BAT.
BOOT
QJ71C24
CH1.
External device
CH2.
CH1.
RS-232
CPU error
information
Monitoring device
information
PULL
USB
RS-232
Abnormal detection
MITSUBISHI
Error
occurrence
2.1 Overview
35
2.2
About the Programmable Controller CPU Monitoring
Function
This section explains the programmable controller CPU monitoring function.
2.2.1
Data registration for using the programmable controller CPU
monitoring function
The following explains the data registration by the user to use the programmable controller CPU monitoring function.
(1) Programmable controller CPU monitor registration for the Q series C24 that is
required to use the programmable controller CPU monitoring function is
described in the following sections.
(a) Registration using the Q series C24 dedicated utility package (GX Configurator-SC)
(b) Registration using the programmable controller CPU monitoring registration
command (0630) for communication with the MC protocol ( MELSEC
Communication Protocol Reference Manual)
(c) Registration using the programmable controller CPU "CSET" instruction ( Page
369, CHAPTER 17)
(2) When this function is used with the modem function and data is transmitted or
a notification message is notified as a programmable controller CPU
monitoring result, register the connection data for the modem function on the
"PLC CPU monitoring system setting" screen of GX Configurator-SC.
(3) By registering the data for using the above programmable controller CPU
monitoring function, the Q series C24 begins monitoring the programmable
controller CPU.
36
CHAPTER 2 USING THE PROGRAMMABLE CONTROLLER CPU MONITORING FUNCTION
2.2.2
Programmable controller CPU monitoring information
This section explains the monitoring target information used to execute the programmable controller CPU monitoring
2
function.
(1) The following information can be registered as the target of the programmable
controller CPU monitoring function.
(a) Device monitoring for the local station's programmable controller CPU
• Monitoring of the numeric values stored in the word device
• Monitoring of the bit device ON/OFF status
(b) Monitoring of the local station's programmable controller CPU status
(2) In monitoring word and bit devices, a maximum total device point value of 960
(equivalent to a maximum of 15360 bits for only bit devices), or a total of 10
blocks when any continuous device range comprises one block, can be
registered. Since monitoring of the local station's programmable controller
CPU status will also be registered as a one-block portion, up to 11 blocks can
be registered.
11  (Number of word device blocks registered + number of bit device blocks registered) + CPU status monitoring
(1 block)
960 points  (Total number of all word device block points (1 point = 1 word) + total number of all bit device block
(3) With device monitoring of the blocks for which the word and bit devices are
registered, the head device of each block becomes the monitoring target.
For a block in which 10 points of word devices from D100 to D109 are registered
Monitoring target: Numeric value stored in D100
Data transmitted: Numeric values stored in D100 to D109
For a block in which two points of bit devices from M100 to M131 are registered
Monitoring target: ON/OFF status of M100
Data transmitted: ON/OFF status of M100 to M131
37
2.2 About the Programmable Controller CPU Monitoring Function
points(1 point = 16 bits))
(4) The word and bit devices that can be designated as the monitoring targets and
the device codes that are used to register the monitoring devices are listed in
the table below. Register the devices using the device ranges existing in the
programmable controller CPU.
Classification
Internal system
Device
Device type
Bit

Special relay

Special register
Device code
ASCII
Binary
SM
91H
SD
A9H
Input

X*
9CH
Output

Y*
9DH
Internal relay

M*
90H
Latch relay

L*
92H
Annunciator

F*
93H
Edge relay

V*
94H
Link relay

Device range (Default)
0 to 2047
0 to 1FFFH
0 to 8191
0 to 2047
B*
A0H
Data register

D*
A8H
0 to 12287
Link register

W*
B4H
0 to 1FFFH
C1H
Timer
Contact

TS
Coil

TC
C0H
TN
C2H

Current value
Internal user
Retentive timer
Contact

SS
C7H
Coil

SC
C6H

Current value
Counter
SN
C8H
Contact

CS
C4H
Coil

CC
C3H
CN
C5H

Current value
Link special relay


Link special register
SB
A1H
SW
B5H
0 to 1FFFH
0 to 2047
0 to 1023
0 to 7FFH
Step relay

S*
98H
Direct input

DX
A2H
Direct output

DY
A3H

Z*
CCH
0 to 15

R*
AFH
0 to 32767

ZR
B0H
0 to FE7FFH
Index register
Register
Word
File register
0 to 8191
0 to 1FFFH
● Designating a non-existent device code will result in an error.
● When the device range in the parameter setting has been changed, the new device range can be set as the
programmable controller CPU's monitoring target.
38
CHAPTER 2 USING THE PROGRAMMABLE CONTROLLER CPU MONITORING FUNCTION
2.2.3
Timing for programmable controller CPU monitoring
The following explains the timing for programmable controller CPU monitoring when the programmable controller CPU
2
monitoring function is executed.
(1) Programmable controller CPU monitoring using the Q series C24 is performed
continuously at cycle time intervals registered by the user.
(2) Values from 1 to 65535 (unit: 100ms/s/min) can be registered as the cycle time.
Use the following expressions as a reference when registering the cycle time.
(a) When sending device data or the programmable controller CPU status
Cycle time designation > K + sequence scan time + processing time + data transmission time
(b) When notifying through combined use of the modem function*1
(when notifying)
Cycle time designation > K + sequence scan time + processing time
+ data transmission time + data transmission delay time of the modem
+ modem connection and disconnection time
(when sending data)
Cycle time designation > K + sequence scan time + processing time
+ data transmission time + data transmission delay time of the modem
+ modem connection and disconnection time + circuit disconnection wait time
When modem initialization has not been performed, the modem initialization time will be added. (We recommend that
the modem initialization be performed in advance.)
The items that appear in the above expressions are explained below:
• K: 60ms constant (internal processing time of the Q series C24)
• Processing time: Processing time for the "Multiple block batch read word unit command 0406"
For 1 point: 11.3ms
For 480 points: 23.4ms
For 960 points: 36.2ms
• Data transmission time = 1 / transmission rate  bit count for one byte portion during transmission  byte
count for transmission data
• Bit count for one byte portion during transmission = 1 + data bit count + parity bit + stop bit count
(parity bit = 1, no parity bit = 0)
• Data transmission delay time by the modem: Depends on the modem specifications, line specifications and
line status.
• Modem connection and disconnection time: Depends on the modem specifications, line specifications and
line status.
• Modem initialization time: Depends on the modem specifications.
39
2.2 About the Programmable Controller CPU Monitoring Function
*1
(3) To monitor the programmable controller CPU, the Q series C24 reads
monitoring information (device information, programmable controller CPU
status information) from the programmable controller CPU at time intervals set
by the user.
● Since the Q series C24 reads the monitoring information (device data, programmable controller CPU status) at the time
of the next programmable controller CPU END process after the cycle time elapses, make the cycle time as long as
possible.
● The following should be considered if the cycle time is short.
• The scan time of the programmable controller CPU is longer and the number of scan cycles has increased.
• The increase in the processing time of the Q Series C24 programmable controller CPU monitoring function has
increased causing an increase in the processing time of other data communication functions.
• The load on the external device has increased.
40
CHAPTER 2 USING THE PROGRAMMABLE CONTROLLER CPU MONITORING FUNCTION
2.2.4
Timings of transmission and notification of monitoring results
to the external device
The following explains the timings for the transmission and notification of the programmable controller CPU monitoring
2
results.
There are two transmission methods for transmitting and notifying the monitoring results of the local station
programmable controller CPU to the external device. These include constant cycle transmission and condition
agreement transmission. One of these methods must be selected by the user during programmable controller CPU
monitoring registration.
(1) Constant cycle transmission
The monitoring results are transmitted and notified each time monitoring information is read from the
programmable controller CPU.
(Timing to transmit data)
Monitoring information
Constant cycle
transmission
One-block
portion
…
One-block
portion
External device
Cycle time
Sequence program
END
END
END
(2) Condition agreement transmission
(a) For device monitoring, the monitoring conditions registered by the user (conditions
for sending monitoring results), the monitoring condition values and the monitoring
information read from the programmable controller CPU are compared. The
monitoring results are sent or notified when there is a block where the monitoring
conditions match.
For programmable controller CPU status monitoring, the monitoring results are sent or notified only once when
an error is detected for the first time from the status information read from the programmable controller CPU.
(This corresponds to the edge triggered transmission noted below.)
41
2.2 About the Programmable Controller CPU Monitoring Function
END
(b) Two transmission methods of the monitoring results are available for the condition
agreement transmission for device monitoring. These include edge triggered
transmission and level triggered transmission.
• Edge triggered transmission
The monitoring conditions registered by the user (conditions for sending monitoring results), the monitoring
condition values and the monitoring information read from the programmable controller CPU are compared.
The monitoring results are sent or notified only once when an agreement of the monitoring conditions is
detected for the first time.
After that, when the monitoring information read from the programmable controller CPU does not match the
monitoring conditions and then it matches the monitoring conditions once again, the monitoring results are sent
or notified.
• Level triggered transmission
The monitoring conditions registered by the user (conditions for sending monitoring results), the monitoring
condition values and the monitoring information read from the programmable controller CPU are compared.
While the monitoring conditions agree, the monitoring results are sent or notified at each cycle time.
(Timing to transmit data)
Monitoring information
Condition agreement
transmission
One-block
portion
One-block
portion
…
External device
Cycle time
Sequence program
(conditions matched/not
matched)
Matched
END
Not matched
Matched
END
END
(c) In the condition agreement transmission for device monitoring, the head device for
each block is the monitoring target for condition monitoring of each block device.
For the condition agreement transmission, the monitoring conditions that can be designated for the device to
be registered by the user and the registration values when designating the monitoring condition are listed in the
table below.
Register the monitoring conditions for the head device of each block using the following table.
Valid designated
device
Registration value
Monitoring condition (item to be judged)
For edge triggered
transmissions
For level triggered
transmissions
Device value or status = device monitoring condition value or status
0001H
0101H
Device value or status  device monitoring condition value or status
0002H
0102H
0003H
0103H
Monitoring device  monitoring condition value
Unsigned
Signed
42
Monitoring device < monitoring condition value
0004H
0104H
Monitoring device  monitoring condition value
0005H
0105H
Monitoring device > monitoring condition value
0006H
0106H
Monitoring device  monitoring condition value
0007H
0107H
Monitoring device < monitoring condition value
0008H
0108H
Monitoring device  monitoring condition value
0009H
0109H
Monitoring device > monitoring condition value
000AH
010AH
Bit
Word



CHAPTER 2 USING THE PROGRAMMABLE CONTROLLER CPU MONITORING FUNCTION
(d) In device monitoring, register the monitoring condition value or status when the Q
series C24 judges that the numeric value/status of the monitoring device for
condition agreement transmission (head device of each block) agrees with the
2
condition using the registration values listed below.
Type of monitoring device
Monitoring condition value or status
Registration value
OFF
0000H
Bit device
Word device
ON
0001H
Numerical value
0000H to FFFFH
When M0 = ON is the condition agreement
Monitoring condition registration value: 0001H
Registration value for the monitoring condition value or status: 0001H
When D0 > 100 (signed) is the condition agreement
Monitoring condition registration value: 000AH
Registration value for the monitoring condition value or status: 100(64H)
Remark
In status monitoring for the programmable controller CPU, the monitoring conditions and condition values for condition
agreement transmission are not registered.
Instead, it is registered as whether or not programmable controller CPU status monitoring will be performed.
Monitoring results in condition agreement transmission are sent or notified only once when an error is detected by the status
information read from the programmable controller CPU for the first time.
2.2 About the Programmable Controller CPU Monitoring Function
43
2.2.5
Transmission methods of monitoring results and
transmission data to the external device
The following explain the method of transmitting the programmable controller CPU monitoring results and data to the
external device.
(1) Data transmission to the external device while performing communication
using the MC protocol
(a) The same format as for the messages sent with the on-demand function is used to
transmit data, except that the on-demand data section is replaced with the device
information and programmable controller CPU status information. The data is sent
as explained in Page 44, Section 2.2.5 (1) (c) and Page 45, Section 2.2.5 (1) (d). (
MELSEC Communication Protocol Reference Manual)
When the interface that is to use the modem function is set in the MC protocol, connection processing and
disconnection processing to the modem are performed when the programmable controller CPU monitoring
results are transmitted.
Data transmission by MC protocol with modem function (condition agreement transmission)
Dial
Registration information
for programmable controller
CPU monitoring
Disconnection
Cycle time
External device
Sequence program
(conditions matched/
not match)
END
END
END
Matched
Not matched
Matched
(b) When the transmission of on-demand data using user frames is designated, the
same format as for sending on-demand data using user frames is used to transmit
data, except that the on-demand data section is replaced with the device information
and programmable controller CPU status information. The data is sent as explained
in Page 44, Section 2.2.5 (1) (c) and Page 45, Section 2.2.5 (1) (d) below.
See the following explanatory items for data reception by the external device side.
• Device information, programmable controller CPU status information arrangement:  MELSEC
Communication Protocol Reference Manual
• Arrangement of data in the user frame section to be sent:  Page 243, CHAPTER 10
(c) When sending the monitoring results as data during constant cycle transmission,
the entire block portion of the monitoring target device information and
programmable controller CPU status information is transmitted in batch mode.
44
CHAPTER 2 USING THE PROGRAMMABLE CONTROLLER CPU MONITORING FUNCTION
(d) When sending the monitoring results as data during condition agreement
transmission, head data (header) and end data (footer) for the on-demand function
are added to the device information for a block with matched monitoring conditions
and the programmable controller CPU status information upon the occurrence of an
2
error. The header and footer are added to each clock, and then the monitoring result
data is transmitted.
Results are sent in the following order: The programmable controller CPU status information, the device
information registered in the word block and then the device information registered in the bit block.
When there is communication using the MC protocol form 1) to 4), all of the device monitoring head device number will be
converted to hexadecimal ASCII data and sent. (The same conversion is performed during either constant cycle
transmission or condition agreement transmission.)
2.2 About the Programmable Controller CPU Monitoring Function
45
(2) Data transmission to the external device while performing communication
using the non procedure protocol
(a) The device information and CPU information are sent by the word/byte unit
designations.
When the communication data ASCII-BIN conversion is designated, it is converted to ASCII code data and
sent. (Examples are shown in Page 48, Section 2.2.5 (2) (f)).
• When the word/byte unit designation is word
The device information and CPU information are each sent in one-word segments in a (H) (L) sequence.
• When the word/byte unit designation is byte
The device information and CPU information are each sent in one-word segments in a (L) (H) sequence.
When the interface that is to use the modem function is set in the non procedure protocol, connection
processing and disconnection processing to the modem are performed when the programmable controller CPU
monitoring results are transmitted.
Data transmission by non procedure protocol with modem function (condition agreement transmission)
Monitoring information
Dial
1 block
…
1 block
Disconnection
Cycle time
External device
Sequence program
(conditions matched/
not matched)
END
END
END
Matched
Not matched
Matched
(b) When sending monitoring results as data during constant cycle transmission, the
device information of two or more user frame No. and programmable controller CPU
status information that have been currently designated for the constant cycle
transmission by the Q series C24.
(c) When sending the monitoring results as data during condition agreement
transmission, the device information of two or more user frame No. and
programmable controller CPU status information that have been currently
designated by the Q series C24 for the condition agreement transmission of the
block where the monitoring conditions match are transmitted in batch mode.
When the monitoring conditions of two or more block match, the device information and programmable
controller CPU status information are transmitted for each block.
When there is an ASCII-BIN conversion of communication data using non procedure protocol, all of the device monitoring
head device number will be converted to hexadecimal ASCII data and sent. (The same conversion is performed during
either constant cycle transmission or condition agreement transmission.)
46
CHAPTER 2 USING THE PROGRAMMABLE CONTROLLER CPU MONITORING FUNCTION
(d) The user frame numbers that can be designated for data transmission of
programmable controller CPU monitoring results are listed below.
• 1H to 3E7H (Default registration frame numbers)
2
• 3E8H to 4AFH (Frame numbers registered by the user in the flash ROM)
• 8001H to 801FH (Frame numbers registered by the user in the buffer memory)
• B001H to B01FH (Dedicated frame numbers for this function listed in Page 47, Section 2.2.5 (2) (e) below)
For details on how to designate user frame numbers, see Transmission using user frames in Page 252,
CHAPTER 11.
(e) For instructing to transmit the device information and programmable controller CPU
status information when sending monitoring results as data, use the following
dedicated user frame numbers.
Valid function
Frame number
Information to be transmitted
B001H
Number 1
B002H
Number 2
B003H
Number 3
B004H
Number 4
B005H
B006H
Device information for the block registered
in number n
Number 5
Number 6
B007H
Number 7
B008H
Number 8
B009H
Number 9
B00AH
Number 10
Programmable controller CPU status information (CPU abnormal
monitoring data)
B080H
Number of blocks sent
B081H
Monitoring result information for all blocks
B082H
Monitoring result information for blocks satisfying the conditions
Condition agreement
transmission








2.2 About the Programmable Controller CPU Monitoring Function
B061H
Constant cycle
transmission
47
(f) Device information and programmable controller CPU status information are sent
using the data arrangement shown below.
The ASCII-BIN conversion designation is designated in buffer memory address 121H/1C1H.
Note that when the user frame has been designated by setting to on the value for bit 14, which indicates the
user frame No., there will be ASCII-BIN conversion of corresponding send data. It will be sent as binary data.
( Page 321, Section 13.3)
• When user frame numbers B001H to B00AH are designated (example of a one-block portion)
• When word device data (W100 to W103, (4 points)) is sent
When the word/byte unit designation is word unit, the device data will be sent in a (H)  (L) sequence.
The number of registered points is the number of points in word units.
(When ASCII-BIN conversion is not performed)
The total number of bytes for the device data section is the number of device points  2.
L
H
L
H
L
H
L
H
H
L
L
H
L
H
L
(W)
Device data
Number of
registered points
Device code
Monitoring head
device
When the word/byte unit designation is word
Device data
Number of
registered points
Device code
Monitoring head
device
When the word/byte unit designation is byte
H
H
L
L
H
H
L
L
00H 01H 00H B4H 04H 00H 00H 00H 01H 00H 02H 00H 03H 00H
00H 01H 00H B4H 04H 00H 00H 00H 00H 01H 00H 02H 00H 03H
W100
W100
W101
W102
W103
W101
W102
(When ASCII-BIN conversion is performed)
The total number of bytes for the device data section is the number of device points  4.
H
L
H
W
*
0
0
0
1
0
L
H
0
0
0
0
Device data
Device code
Monitoring head
device
Number of
registered points
When the word/byte unit designation is byte
L
L
4
0
0
0
H
L
0
0
1
0
H
L
0
0
H
2
0
0
L
0
H
3
0
0
57H 2AH 30H 30H 30H 31H 30H 30H 30H 30H 30H 34H 30H 30H 30H 30H 30H 31H 30H 30H 30H 32H 30H 30H 30H 33H 30H 30H
W100
48
H
(W)
W101
W102
W103
W103
CHAPTER 2 USING THE PROGRAMMABLE CONTROLLER CPU MONITORING FUNCTION
H
L
H
W
*
0
0
0
1
0
L
H
0
0
0
0
2
Device data
Device code
Monitoring head
device
Number of
registered points
When the word/byte unit designation is word
L
H
4
0
0
0
L
H
0
0
0
0
L
H
1
0
0
0
L
H
2
0
L
0
0
3
57H 2AH 30H 30H 30H 31H 30H 30H 30H 30H 30H 34H 30H 30H 30H 30H 30H 30H 30H 31H 30H 30H 30H 32H 30H 30H 30H 33H
W100
W101
W102
W103
• When data for bit device (M16 to M175, (10 point)) is sent
When the word/byte unit designation is word unit, the device data will be sent in a (H)  (L) sequence.
The number of registered points is the number of points in word units.
2.2 About the Programmable Controller CPU Monitoring Function
49
(When ASCII-BIN conversion is not performed)
The total number of bytes for the device data section is the number of device points  2.
L
H
L
H
L
H
L
L
H
L
H
H
Device data
Device data
Device code
Monitoring
head device
H
Number of
registered points
When the word/byte unit designation is word
Device data
Device data
Number of
registered points
Monitoring
head device
Device code
When the word/byte unit designation is byte
L
H
10H 00H 00H 90H 0AH 00H 30H 11H
3
12H 34H
0
1
10H 00H 00H 90H 0AH 00H 11H 30H
1
34H 12H
1
0 0 1 1 0 0 0 0 0 0 0 1 0 0 0 1
MMMMMMMMMMMMMMMM
2 2 2 2 1 1 1 1 3 3 2 2 2 2 2 2
3 2 1 0 9 8 7 6 1 0 9 8 7 6 5 4
1
The total number of bytes for the device data section is the number of device points  4.
L
H
M
*
0
0
0
0
1
L
H
0
0
0
0
L
L
A
3
0
Device data
Device data
Device code
Monitoring head
device
Number of
registered points
When the word/byte unit designation is byte
H
1
H
L
1
1
4DH 2AH 30H 30H 30H 30H 31H 30H 30H 30H 30H 41H 33H 30H 31H 31H
3
0
M
2
3
0
M
2
2
1
M
2
0
0
M
1
9
0
M
1
8
1
0
M
1
7
0
M
1
6
3
4
31H 32H 33H 34H
0
1
M
2
1
H
2
0
M
3
1
0
M
3
0
0
M
2
9
1
1
M
2
8
0
M
2
7
0
M
2
6
0
M
2
5
1
M
2
4
L
H
M
*
0
0
0
0
1
L
H
0
0
0
0
L
H
A
1
1
Device data
Device data
Device code
Monitoring head
device
Number of
registered points
When the word/byte unit designation is word
H
3
0
0 0 0 1 0 0 0 1 0 0 1 1 0 0 0 0
MMMMMMMMMMMMMMMM
3 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1
1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6
(When ASCII-BIN conversion is performed)
3
L
H
0
3
4DH 2AH 30H 30H 30H 30H 31H 30H 30H 30H 30H 41H 31H 31H 33H 30H
1
0
M
3
1
50
L
(M)
(M)
0
M
3
0
0
M
2
9
0
M
2
7
0
M
2
6
0
M
2
5
3
1
M
2
4
1
2
33H 34H 31H 32H
1
1
M
2
8
L
4
0
M
2
3
0
M
2
2
1
M
2
1
0
1
M
2
0
0
M
1
9
0
M
1
8
0
M
1
7
0
M
1
6
CHAPTER 2 USING THE PROGRAMMABLE CONTROLLER CPU MONITORING FUNCTION
• When user frame No. B061H is designated
Programmable controller CPU status information (for one block) is sent as the following data:
Item
when communicating with
ASCII code
when communicating with
binary code
"01"
01H
"0001"
0001H
"000000"
000000H
"0000"
0000H
Device code
Number of registered points
Monitoring head device
During normal operation
Device data
Module warning occurring
"0001"
0001H
Module error/module system error occurring
"0002"
0002H
Remarks
2
All fixed value
(When ASCII-BIN conversion is not performed)
The total number of bytes for the device data section is the number of device points  2.
H
L
H
L
L
H
L
01H 00H 00H 00H 01H 00H 01H 00H
L
H
Device data
Monitoring head
device
Device code
H
Number of
registered points
When the word/byte unit designation is word
Device data
Device code
Monitoring head
device
Number of
registered points
When the word/byte unit designation is byte
H
L
01H 00H 00H 00H 01H 00H 00H 01H
(When ASCII-BIN conversion is performed)
The total number of bytes for the device data section is the number of device points  4.
L
H
1
0
0
0
0
0
L
H
0
0
0
0
L
L
1
0
1
0
H
H
L
H
0
0
1
0
30H 31H 30H 30H 30H 30H 30H 30H 30H 30H 30H 31H 30H 31H 30H 30H
0
0
0
0
L
H
0
0
0
0
Device data
Number of
registered points
Monitoring head
device
Device code
Device data
Monitoring head
device
Device code
H
0
When the word/byte unit designation is word
2.2 About the Programmable Controller CPU Monitoring Function
Number of
registered points
When the word/byte unit designation is byte
L
H
1
0
L
0
0
1
30H 31H 30H 30H 30H 30H 30H 30H 30H 30H 30H 31H 30H 30H 30H 31H
• When user frame No. B080H is designated
The transmission block count will be sent as follows:
Number of registered word blocks: 2 (D0 to D3 (4 points), W100 to W107 (8 points))
Number of registered bit blocks: 1 (M0 to M31 (2 points))
02H 01H 00H
Number of registered
bit blocks
CPU abnormal
monitoring
When ASCII-BIN conversion is performed
Number of registered
word blocks
CPU abnormal monitoring
Number of registered bit blocks
Number of registered word blocks
When ASCII-BIN conversion is not performed
H
L
H
L
H
L
0
2
0
1
0
0
30H 32H 30H 31H 30H 30H
51
• When user frame No. B081H is designated
Information on monitoring results for all blocks are sent as follows:
Results are sent in the following order: the device information registered in the word block, the device
information registered in the bit block and then programmable controller CPU status information.
Number of registered word blocks: 1 (W100 to W103 (4 points))
Number of registered bit blocks: 1 (M0 to M15 (1 point))
Perform CPU status monitoring: 1 (1 point)
(When ASCII-BIN conversion is not performed)
The total number of bytes for the device data section is the number of device points  2.
L
H
L
H
L
H
L
H
L
H
L
H
L
H
(W)
L
H
L
H
L
H
L
Device data
Number of
registered points
Device code
Monitoring head
device
Device data
Number of
registered points
Device code
Monitoring head
device
Device data
Number of
registered points
Device code
Monitoring head
device
When the word/byte unit designation is byte
H
L
H
(M)
00H 01H 00H B4H 04H 00H 00H 00H 01H 00H 02H 00H 03H 00H 00H 00H 00H 90H 01H 00H 30H 11H 00H 00H 00H 01H 01H 00H 00H 00H
W100
W101
W102
W103
3
0
M
0
7
0
1
0 1 1 0 0 0 0 0 0 0
MMMMMMMMMM
0 0 0 0 0 0 0 1 1 1
6 5 4 3 2 1 0 5 4 3
1
1 0 0 0 1
MMMMM
1 1 1 0 0
2 1 0 9 8
L
H
L
H
H
L
H
L
H
L
H
L
(W)
L
H
L
H
H
L
L
L
H
H
Device data
Number of
registered points
Device code
Monitoring head
device
Device data
Number of
registered points
Device code
Monitoring head
device
Device data
Number of
registered points
Device code
Monitoring head
device
When the word/byte unit designation is word
H
L
(M)
00H 01H 00H B4H 04H 00H 00H 00H 00H 01H 00H 02H 00H 03H 00H 00H 00H 90H 01H 00H 11H 30H 00H 00H 00H 01H 01H 00H 00H 00H
W100
W101
W102
W103
1
0
M
1
5
52
1
3
0
0 0 1 0 0 0 0 0 0 1 1 0 0 0 0
MMMMMMMMMMMMMMM
1 1 1 1 1 0 0 0 0 0 0 0 0 0 0
4 3 2 1 0 9 8 7 6 5 4 3 2 1 0
CHAPTER 2 USING THE PROGRAMMABLE CONTROLLER CPU MONITORING FUNCTION
(When ASCII-BIN conversion is performed)
The total number of bytes for the device data section is the number of device points  4.
H
L
H
W
*
0
0
0
1
0
L
H
0
0
0
0
L
L
4
0
0
0
H
L
0
0
1
0
H
L
0
0
2
0
H
L
0
0
3
0
H
H
L
H
0
M
*
0
0
0
0
2
0
L
H
0
0
0
0
Device data
Number of
registered points
Monitoring
head device
Device code
Device data
Number of
registered points
Monitoring
head device
Device code
When the word/byte unit designation is byte
L
L
1
3
H
0
1
1
57H2AH30H 30H 30H 31H 30H 30H 30H 30H 30H 34H 30H 30H 30H 30H 30H 31H 30H 30H 30H 32H 30H 30H 30H 33H 30H 30H4DH 2AH 30H 30H 30H 30H 30H 30H 30H 30H 30H 31H 33H 30H 31H 31H
W100
W101
W103
W102
H
L
H
0
1
0
0
0
0
0
L
H
0
0
0
0
Device data
Device code
Monitoring head
device
Number of
registered points
3
L
L
1
0
1
0
1
0 0 1 1 0 0 0 0 0 0 0 1 0 0 0 1
MMMMMMMMMMMMM MMM
0 0 0 0 0 0 0 0 1 1 1 1 1 1 0 0
7 8 5 4 3 2 1 0 5 4 3 2 1 0 9 8
H
0
0
0
30H 31H 30H 30H 30H 30H 30H 30H 30H 30H 30H 31H 30H 30H 30H 30H
H
L
H
W
*
0
0
0
1
0
L
H
0
0
0
0
L
H
4
0
0
0
L
H
0
0
0
0
L
H
1
0
0
0
L
H
2
0
0
0
L
H
L
H
3
M
*
0
0
0
0
0
L
H
0
0
0
0
Device data
Number of
registered points
Monitoring
head device
Device code
Device data
Number of
registered points
Monitoring
head device
Device code
When the word/byte unit designation is word
L
H
1
1
L
1
3
0
W100
W101
W102
W103
H
L
H
0
1
0
0
0
0
0
L
H
0
0
0
0
Device data
Device code
Monitoring head
device
Number of
registered points
1
L
H
1
0
1
3
0
00 0 10 0 0 1 0 0 1 1 0 0 0 0
MMMMMMMMMMMMMMMM
1 11 11 1 0 0 0 0 0 0 0 0 0 0
5 43 21 0 9 8 7 6 5 4 3 2 1 0
L
0
0
0
30H 31H 30H 30H 30H 30H 30H 30H 30H 30H 30H 31H 30H 30H 30H 30H
• When user frame No. B082H is designated
Information on the monitoring results for the condition agreement blocks are sent for each block.
Transmission is performed in the following order: the programmable controller CPU status information, then the
device information registered in the word block, and then the device information registered in the bit block.
Number of registered word blocks: 2 (D0 to D3 (4 points), W100 to W103 (4 points))
Number of registered bit blocks: 1 (M0 to M15 (1 point))
When the condition satisfied monitoring device is W100 = 0 and M0  ON
53
2.2 About the Programmable Controller CPU Monitoring Function
57H2AH30H 30H 30H 31H 30H 30H 30H 30H 30H 34H 30H 30H 30H 30H 30H 30H 30H31H 30H 30H 30H 32H 30H 30H 30H 33H 4DH 2AH 30H 30H 30H 30H 30H 30H 30H 30H 30H 31H 31H 31H 33H 30H
(When ASCII-BIN conversion is not performed)
The total number of bytes for the device data section is the number of device points  2.
When the word/byte unit designation is byte
L
H
L
H
L
H
L
H
L
H
L
H
L
H
(W)
L
H
Device data
Number of
registered points
Device code
Monitoring head
device
For M0 to M15 block data
Device data
Number of
registered points
Device code
Monitoring head
device
For W100 to W103 block data
L
H
(M)
00H 01H 00H B4H 04H 00H 00H 00H 01H 00H 02H 00H 03H 00H
W100
W102
W101
00H 00H 00H 90H 01H 00H 30H 11H
W103
3
0
1
1
0 0 1 1 0 0 0 0 0 0 0 1 0 0 0 1
MMMMMMMMMMMMMMMM
0 0 0 0 0 0 0 0 1 1 1 1 1 1 0 0
7 6 5 4 3 2 1 0 5 4 3 2 1 0 9 8
When the word/byte unit designation is word
L
H
L
H
H
L
H
L
H
L
H
L
(W)
L
H
L
H
Device data
Number of
registered points
Device code
Monitoring head
device
For M0 to M15 block data
Device data
Number of
registered points
Device code
Monitoring head
device
For W100 to W103 block data
H
L
(M)
00H 01H 00H B4H 04H 00H 00H 00H 00H 01H 00H 02H 00H 03H
W100
W101
W102
00H 00H 00H 90H 01H 00H 11H 30H
W103
1
1
3
0
0 0 0 1 0 0 0 1 0 0 1 1 0 0 0 0
MMMMMMMMMMMMMMMM
1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0
5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0
54
CHAPTER 2 USING THE PROGRAMMABLE CONTROLLER CPU MONITORING FUNCTION
(When ASCII-BIN conversion is performed)
The total number of bytes for the device data section is the number of device points  4.
When the word/byte unit designation is byte
For W100 to W103 block data
For M0 to M15 block data
H
L
H
W
*
0
0
0
1
0
L
H
0
0
0
0
L
L
4
0
0
0
H
L
0
0
1
0
H
L
0
0
2
0
H
L
0
0
3
0
H
H
L
H
0
M
*
0
57H2AH30H 30H 30H 31H 30H 30H 30H 30H 30H 34H30H 30H 30H 30H 30H 31H 30H 30H 30H 32H 30H 30H 30H 33H 30H 30H
W100
W101
W102
0
0
0
0
L
H
0
0
0
0
Device data
Number of
registered points
Monitoring head
device
Device code
Device data
Number of
registered points
Device code
Monitoring head
device
2
L
L
1
3
H
0
1
1
4DH 2AH 30H 30H 30H 30H 30H 30H30H 30H 30H 31H 33H 30H 31H31H
W103
3
1
0
1
0 0 1 1 0 0 0 0 0 0 0 1 0 0 0 1
MMMMMMMMMMMMMMMM
0 0 0 0 0 0 0 0 1 1 1 1 1 1 0 0
7 6 5 4 3 2 1 0 5 4 3 2 1 0 9 8
When the word/byte unit designation is word
H
L
H
W
*
0
0
0
1
0
L
H
0
0
0
0
H
0
0
0
L
H
0
0
0
0
L
H
1
0
0
0
L
H
2
0
0
0
L
H
L
H
3
M
*
0
57H2AH30H 30H 30H 31H 30H 30H 30H 30H 30H 34H30H 30H 30H 30H 30H 30H 30H 31H 30H 30H 30H 32H 30H 30H 30H 33H
W101
W102
0
0
0
L
H
0
0
0
0
Device data
L
H
1
1
L
1
3
0
4DH 2AH 30H 30H 30H 30H 30H 30H30H 30H 30H 31H 33H 30H 31H 31H
W103
1
1
3
0
0 0 1 1 0 0 0 0 0 0 0 1 0 0 0 1
MMMMMMMMMMMMMMMM
1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0
5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0
55
2.2 About the Programmable Controller CPU Monitoring Function
W100
0
Number of
registered points
Device code
Device data
L
4
Monitoring head
device
For M0 to M15 block data
Number of
registered points
Device code
Monitoring head
device
For W100 to W103 block data
(3) Notification to the interface side using the modem function
(a) The notification message (text string data) contained in the user registered data for
connecting the modem function is conveyed using the modem function.
The device information and the CPU status information read from the programmable controller CPU are not
sent to the external device in the notification message.
Include the device information and the CPU status information by which the programmable controller CPU
status can be checked in the preregistered notification message.
(b) The method for message notification is functionally the same as the notification
using the modem function described in Page 69, CHAPTER 3.
The difference is that notification is performed with Y14 OFF when using the modem, whereas for notification
using programmable controller CPU monitoring, notification is performed for whenever the programmable
controller CPU error is detected or the designated device status is matched with the monitoring conditions.
( Page 41, Section 2.2.4)
(c) During constant-cycle transmission, a notification message for one connection data
registered for notifying constant-cycle transmission is sent.
(d) During condition agreement transmission, a notification message for connection
data registered in the block where the monitoring conditions match is sent in block
units.
When there are multiple blocks where the monitoring conditions match, notification is performed at the "Wait
time of notification" interval (notification interval) set by the user for use with the modem function. The
programmable controller CPU monitoring stops until notification has been performed to all blocks where the
monitoring conditions match.
● When performing message notification using the programmable controller CPU monitoring function, set the
corresponding interface side as the target of the modem function.
● When setting data for the programmable controller CPU monitoring function with GX Configurator-SC, programmable
controller CPU monitoring begins immediately when the Q series C24 starts up.
56
CHAPTER 2 USING THE PROGRAMMABLE CONTROLLER CPU MONITORING FUNCTION
2.2.6
Execution sequence for using the programmable controller
CPU monitoring function
2
The following explains the execution sequence for using the programmable controller CPU monitoring function.
(1) When transmitting the monitoring results through data
transmission/notification messages using the modem function, perform the
following settings in order to use the modem function.
Setting item
Reference section
Initial setting by GX Configurator-SC
Page 131, Section 3.4.2
Registration of data No. for initialization and data No. for connection
Page 134, Section 3.4.3, Page 139, Section 3.4.4
Initialization of the Q series C24 modem/TA
Page 144, Section 3.4.5
(2) Register programmable controller CPU monitoring for the Q series C24 using
one of the methods described in Page 36, Section 2.2.1.
(3) By registering programmable controller CPU monitoring, the Q series C24
monitors the local station's programmable controller CPU regardless of the
RUN/STOP status and sends the monitoring information to the external device.
(a) When registering with communication using the MC protocol
( MELSEC Communication Protocol Reference Manual)
(b) When registering with the programmable controller CPU's "CSET" instruction (
Page 203, CHAPTER 7)
To cancel when using GX Configurator-SC, change the programmable controller CPU to the STOP status, redo
the settings, and then restart the QCPU.
57
2.2 About the Programmable Controller CPU Monitoring Function
(4) When reregistering programmable controller CPU monitoring in order to
change the registration data for the programmable controller CPU monitoring,
reregister after canceling the programmable controller CPU monitoring.
2.3
Settings for Using the Programmable Controller CPU
Monitoring Function
This section describes system settings required for constant cycle transmission and condition agreement transmission.
2.3.1
System setting items for the programmable controller CPU
monitoring function
The following explains system setting items for the programmable controller CPU monitoring function.
● Register transmission user frames by GX Configurator-SC, after checking the specifications and setting methods
explained in Page 220, CHAPTER 9 and Page 252, CHAPTER 11 of this manual.
● Register connection data for the modem function by GX Configurator-SC, after checking the specifications described in
Page 139, Section 3.4.4 of this manual.
(1) Setting items and requirement when performing communication using the MC
protocol
Constant cycle transmission
Setting item
Data
transmission
Notification
*1
Condition agreement
transmission
Data
transmission
Reference section
*1
Notification
Cycle time units


Page 61, Section 2.3.1 (3) (a)
Cycle time


Page 61, Section 2.3.1 (3) (b)
PLC CPU monitoring function
PLC CPU monitoring transmission measure
Transmission pointer
Constant cycle
transmission
Output count
Data No. for connection
58
 (1H: Constant cycle)
 (Data)

(Notification)




 (2H: Condition agreement)
Page 61, Section 2.3.1 (3) (c)

(Notification)
Page 61, Section 2.3.1 (3) (b)
 (Data)


Page 38, Section 2.2.2 (4)
Page 288, Section 11.4.2
Page 56, Section 2.2.5 (3)
Page 139, Section 3.4.4
CHAPTER 2 USING THE PROGRAMMABLE CONTROLLER CPU MONITORING FUNCTION
Constant cycle transmission
Setting item
Data
transmission
Notification*1
Condition agreement
transmission
Data
transmission
Reference section
Notification*1
Number of registered word blocks
Page 61, Section 2.3.1 (3) (e)
Number of registered bit blocks
PLC CPU abnormal monitoring

Monitoring device
2
Page 61, Section 2.3.1 (3) (f)
Head device No.


Page 62, Section 2.3.1 (3) (g)
Read point
Monitoring
condition
No. n block
monitoring device
Condition
agreement
transmission
Monitoring
condition value
Page 62, Section 2.3.1 (3) (i)

Transmission
pointer
Output count
Data No. for
connection
PLC CPU abnormal monitoring
designation
Condition agreement transmission
Page 62, Section 2.3.1 (3) (h)


Page 63, Section 2.3.1 (4)
Page 288, Section 11.4.2


Page 56, Section 2.2.5 (3)
Page 139, Section 3.4.4


Page 63, Section 2.3.1 (4)
Page 288, Section 11.4.2


Page 56, Section 2.2.5 (3)
Page 139, Section 3.4.4

Transmission
pointer
Output count
Data No. for
connection
: Setting required, : Setting not required
*1
Cannot be used for the LJ71C24(-R2).
While using the notification function, the device information and the CPU status information cannot be transmitted.
2.3 Settings for Using the Programmable Controller CPU Monitoring Function
59
(2) Setting items and requirement when performing communication using the non
procedure protocol
Constant cycle transmission
Setting item
Data
transmission
Notification
Condition agreement
transmission
Data
transmission
Reference section
Notification
Cycle time units


Page 61, Section 2.3.1 (3) (a)
Cycle time


Page 61, Section 2.3.1 (3) (b)
 (1H: Constant cycle)
 (2H: Condition agreement)
Page 61, Section 2.3.1 (3) (c)

(Notification)
Page 61, Section 2.3.1 (3) (d)
PLC CPU monitoring function
PLC CPU monitoring transmission measure
Transmission pointer
Constant cycle
transmission
Output count
 (Data)

(Notification)


 (Data)

Data No. for connection


Page 63, Section 2.3.1 (4)
Page 288, Section 11.4.2
Page 56, Section 2.2.5 (3)
Page 139, Section 3.4.4

Number of registered word blocks
Page 61, Section 2.3.1 (3) (e)
Number of registered bit blocks
PLC CPU abnormal monitoring
Page 61, Section 2.3.1 (3) (f)

Monitoring device
Head device No.


Page 62, Section 2.3.1 (3) (g)
Read point
Monitoring
condition
No. n block
monitoring device
Condition
agreement
transmission
Monitoring
condition value
Page 62, Section 2.3.1 (3) (i)

Transmission
pointer
Output count
Data No. for
connection
PLC CPU abnormal monitoring
designation
Condition agreement transmission
Page 62, Section 2.3.1 (3) (h)
Transmission
pointer


Page 63, Section 2.3.1 (4)
Page 288, Section 11.4.2


Page 56, Section 2.2.5 (3)
Page 139, Section 3.4.4


Page 63, Section 2.3.1 (4)
Page 288, Section 11.4.2


Page 56, Section 2.2.5 (3)
Page 139, Section 3.4.4

Output count
Data No. for
connection
: Setting required, : Setting not required
While using the notification function, the device information and the CPU status information cannot be transmitted.
60
CHAPTER 2 USING THE PROGRAMMABLE CONTROLLER CPU MONITORING FUNCTION
(3) Contents of setting items
The data items to be set using GX Configurator-SC to use the programmable controller CPU monitoring function
and the setting contents are explained below.
2
(a) Cycle time units
• Designates the unit for cycle time ( Page 61, Section 2.3.1 (3) (b)) for reading information from the
programmable controller CPU using the programmable controller CPU monitoring function.
• The cycle time units and the cycle time designated using this unit can also be used as the transmission time
interval for constant cycle communication.
(b) Cycle time
Designates the time for one cycle when reading information from the programmable controller CPU in order to
perform programmable controller CPU monitoring.
(c) Programmable controller CPU monitoring function
Designates the timing (constant cycle transmission or condition agreement transmission) when
sending/notifying information on the programmable controller CPU monitoring results (device information/CPU
status information) to the external device.
• The time interval designated in data items of Page 61, Section 2.3.1 (3) (a) and Page 61, Section 2.3.1 (3)
(b) for reading information from the programmable controller CPU can also be used as the transmission time
interval for constant cycle communication.
• The conditions for condition agreement transmission are designated using data items of Page 62, Section
2.3.1 (3) (h) and Page 62, Section 2.3.1 (3) (i).
(d) Programmable controller CPU monitoring transmission measure
Designates the means by which the programmable controller CPU monitoring results are conveyed to the
• Data transmission
The device information and the programmable controller CPU status information are sent as the monitoring
results.
• Notification
Notification message is sent as the monitoring results.
(e) Number of registered word blocks, number of registered bit blocks
Designates the number of word device blocks (number of registered word blocks) and the number of bit device
blocks (number of registered bit blocks) registered in the Q series C24 as the target when performing device
data monitoring or transmission.
(f) CPU abnormal monitoring
Designates whether or not the Q series C24 monitors abnormality of the local station programmable controller
CPU (status monitoring) in the programmable controller CPU monitoring.
61
2.3 Settings for Using the Programmable Controller CPU Monitoring Function
external device.
(g) Monitoring device, head device No., read point (Number of registered points)
When performing device data monitoring or transmission, designate the device range for each block for the
number of blocks designated by number of registered word blocks and number of registered bit blocks (
Page 61, Section 2.3.1 (3) (e)).*1
*1
The target of device data monitoring for condition agreement transmission is the head device for each block.
Word device designated block: Head word device (for one word)
Bit device designated block: Head bit device (for one bit)
• The monitored device is the item that indicates the target device of the corresponding block and designated
with the codes listed in Page 38, Section 2.2.2 (4).
• The head device is the data that designates the head of the target device range for the corresponding block.
• The read point is the item that indicates the target device range for the corresponding block which designate
points from the head device No. The bit device designates points in word units (1 point = 16 bits)
• The methods for designating these data are the same as the designation methods used when reading from
or writing to the device memory, which are described in the MELSEC Communication Protocol Reference
Manual.
Remark
When the user performs the programmable controller CPU monitoring registration, the device will designate either a decimal
or hexadecimal device No. The read points (registration points) are designated as hexadecimal.
However, if this is done by either MC protocol communication (form 1) to 4)) or non procedure protocol communication,
when ASCII-BIN conversion of the communication data has been designated, the head device No. for all devices to be sent
to external devices as the monitoring results will be converted to hexadecimal ASCII data and sent.
(h) Monitoring condition
When condition agreement transmission is designated with the programmable controller CPU monitoring
function ( Page 61, Section 2.3.1 (3) (c)), designate the conditions for transmitting information for the
monitoring condition value ( Page 62, Section 2.3.1 (3) (i)).
(i) Monitoring condition value
When condition agreement transmission is designated with the programmable controller CPU monitoring
function ( Page 61, Section 2.3.1 (3) (c)), this item designates the status/numeric value of the monitoring
condition ( Page 62, Section 2.3.1 (3) (h)).
• When the monitoring device is a word device: Designate the monitoring condition value with a numeric value
• When the monitoring device is a bit device: Designate the monitoring condition with a numeric value (1/0)
corresponding to ON/OFF.
62
CHAPTER 2 USING THE PROGRAMMABLE CONTROLLER CPU MONITORING FUNCTION
(4) Setting items for sending monitoring results
The following is an example of setting items and data transmission when sending the monitoring results of the
programmable controller CPU monitoring function execution to the external device using the non procedure
2
protocol.
This example shows a case in which the D0 to D3 device information and user frame data are sent by the
edge trigger method using a condition of D0 = 0.
Perform the settings on the "PLC CPU monitoring system setting" screen and the "###" screen of GX
Configurator-SC.
• PLC CPU monitoring system setting
Setting item
Setting data
Cycle time units
Remarks
min
Cycle time
3
PLC CPU monitoring function
Condition agreement
PLC CPU monitoring transmission measure
Data transmission
Number of registered word blocks
1
Number of registered bit blocks
0
PLC CPU abnormal monitoring
0
Monitoring device
D
Head device No.
0
Read point
4
No. 1 block monitoring device
Edge =
Monitoring condition
value
0
Transmission pointer
49
Output count
3
2.3 Settings for Using the Programmable Controller CPU Monitoring Function
Condition agreement
transmission
Monitoring condition
Settings other than those
listed at left are not required
• Setting the transmission user frames
Transmission frame No. designation 46th
User frame number
Transmission frame No. designation 47th
User frame number
Transmission frame No. designation 48th
User frame number
Transmission frame No. designation 49th
User frame number (02H)
Set the user frame data (STX)
Transmission frame No. designation 50th
User frame number (B001H)
Set the first block (from D0 to D3)
Transmission frame No. designation 51st
User frame number (03H)
Set the user frame data (ETX)
Transmission frame No. designation 52nd
User frame number
Transmission frame No. designation 53rd
User frame number
Transmission frame No. designation 54th
User frame number
Transmission frame No. designation 55th
User frame number
Transmission frame No. designation 56th
User frame number
Transmission frame No. designation 57th
User frame number
Device
data
(D2)
Device
data
(D1)
Device
data
(D0)
Monitoring
head
device
Device
data
(D3)
Device code
ETX
Number of
registered
points
Data sent when the condition D = 0 is satisfied
ETX
External device
63
2.3.2
How to register and cancel the programmable controller CPU
monitoring function
The following describes the method for registering and canceling the programmable controller CPU monitoring
function from the programmable controller CPU.
● For details on the method for registering and canceling the programmable controller CPU monitoring function with GX
Configurator-SC, refer to the Q Corresponding Serial Communication Module User's Manual (Basic).
● For details on the method for registering or canceling the programmable controller CPU monitoring with a command of
MC protocol, refer to the MELSEC Communication Protocol Reference Manual.
(When registering or canceling from the programmable controller CPU)
For details on the CSET command, see Page 375, Section 17.3.
Registering
programmable controller
CPU monitoring
Create control code data from D0
ZP.CSET
M0
"Un" K1 D0 D200 M0
M1
Processing for normal completion
M1
Processing for abnormal completion
Sequence program
CSET instruction
Scan
END
processing
Scan
END
processing
Scan
END
processing
Instruction
execution
Completion device
Completion device +1
Programmable controller CPU
At abnormal completion
Setting processing
(1) Stores the data for programmable controller CPU monitoring registration in
the device that designates the control data for the CSET instruction.
(2) Executes the CSET instruction.
At the end of the scan in which the CSET instruction was completed, the completion device (M0) designated by
(D2) turns ON and then turns OFF at the next END processing.
(3) When there is an error, (D2)+1 turns ON and the error code in stored in the
completion status (S2)+1.
64
CHAPTER 2 USING THE PROGRAMMABLE CONTROLLER CPU MONITORING FUNCTION
(a) Example of a program for performing programmable controller CPU monitoring
registration
This example shows a program that registers programmable controller CPU monitoring for the CH1 side
interface.
This registration is for transmitting the contents of M0 to M15 and D100 to D109 to the external device using
2
constant cycle transmission (cycle time is 3 min).
Converts registration command to pulses
Sets execution type
Sets request type (programmable controller CPU
monitoring registration)
Sets cycle time unit to minutes
Sets cycle time to 3 (min)
Sets the monitoring function to constant cycle
transmission
Sets the means of transmission to data
transmission
Sets the output head pointer
Sets the transmission count of the user frame
Sets data set complete flag -1
Sets the number of registered word blocks to 1
Sets the number of registered bit blocks to 1
2.3 Settings for Using the Programmable Controller CPU Monitoring Function
Registers the devices for D100 to D109
as the first block
Registers the devices for M0 to M15
as the second block
Sets data setting complete flag -2
Executes programmable controller CPU
monitoring registration
Normal completion
Abnormal completion
65
(b) Example of a program for executing programmable controller CPU monitoring
cancellation
This example shows a program that cancels programmable controller CPU monitoring for the CH1 side
interface.
Sets pulse command
Executes programmable controller
CPU monitoring registration reset
Normal completion
Abnormal completion
66
CHAPTER 2 USING THE PROGRAMMABLE CONTROLLER CPU MONITORING FUNCTION
2.4
Precautionary Notes for Using the Programmable
Controller CPU Monitoring Function
2
(1) The cycle time will be affected by the following factors.
Keep these in mind when setting the cycle time.
(a) When the programmable controller CPU is accessed by a module other than the Q
series C24.
(b) When a data communication function other than the programmable controller CPU
monitoring function is used.
(c) When transmission stops by DTR/DSR control.
(2) Both the constant cycle transmission and the condition agreement
transmission cannot be designated together for the same interface.
(3) Only the local station's programmable controller CPU can be the target for the
programmable controller CPU monitoring function.
(a) Perform the new programmable controller CPU monitoring registration after
canceling the programmable controller CPU monitoring.
(b) If the new programmable controller CPU monitoring registration is performed
without canceling the programmable controller CPU monitoring, an error will occur.
Also, for programmable controller CPU monitoring registration using GX Configurator-SC, perform the
registration after placing the programmable controller CPU in the STOP status, and then restart QCPU.
(5) While the programmable controller CPU monitoring function is in operation,
even if an error occurs with transmission/notification of the programmable
controller CPU monitoring results or reading of data from the programmable
controller CPU, the programmable controller CPU monitoring function
operation will not stop.
(6) The programmable controller CPU monitoring function can only be used when
the system configuration is 1:1.
67
2.4 Precautionary Notes for Using the Programmable Controller CPU Monitoring Function
(4) A new programmable controller CPU monitoring registration cannot be
performed while the programmable controller CPU monitoring function is in
operation.
(7) The following describes how the Q series C24 operates when the
programmable controller CPU monitoring result information cannot be sent to
the external device due to line disconnection or other reasons.
Even if an error occurs while the programmable controller CPU monitoring function is in operation, the ERR LED
does not light up. (This is the same as when using the on-demand function of the MC protocol.)
(a) When the setting for the transmission monitoring time designation (timer 2) is an
infinite wait (0H)
• Reading of monitoring data from the programmable controller CPU stops until the transmission of monitoring
data completes.
• When transmission resumes, reading of monitoring data from the programmable controller CPU resumes
and monitoring data and information are transmitted.
(b) When the setting for the transmission monitoring time designation (timer 2) is other
than an infinite wait (0H)
• A transmission timeout error occurs, monitoring information read from the programmable controller CPU,
and transmission of monitoring information resumes.
• The error code is stored in the programmable controller CPU monitoring function error code storage area
(address: 2205H).
(8) When device data for the programmable controller CPU cannot be read
because of a programmable controller CPU error (hardware failure, etc.), the
error code is stored in the programmable controller CPU monitoring function
error code storage area and the Q series C24 performs the monitoring
processing based on previously read data.
(9) When the monitoring information is transmitted as data using the modem
function, a modem connection error will occur if a modem connection is
requested for the following reasons.
• A connection request by Y11
• A notification-issued request by Y14
If possible, provide a dedicated Q series C24 for using the programmable controller CPU monitoring function.
When using both the programmable controller CPU monitoring function and data communication function with a
single Q series C24 and one of the above modem connection errors occurs, re-execute a connection request in
consideration of the transmission timing set by the user for the programmable controller CPU monitoring function.
68
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
CHAPTER 3
COMMUNICATIONS BY THE MODEM
FUNCTION
This chapter explains the overview and how to use the modem function, which can be used for data communication
with remote external devices and paging pager terminals.
3.1
3
Overview
The overview of the modem function is described below:
(1) The modem function easily performs data transmission/reception to remote
devices via public lines/office telephone systems/digital lines (ISDN) by
connecting a modem or TA (terminal adapter) to the Q series C24's RS-232
interface.
(a) Communicating arbitrary data with an external device
(b) Call pager receiver (beeper) to notify the programmable controller system
maintenance information.
(3) Once the line is connected, data communication with the external device via
public line/office telephone system/digital line, or a call to pager receiver can
be made.
Q series C24
Modem/TA (*1)
Modem/TA (*1)
External device
RS-232
Pager receiver
*1 TA: terminal adapter
69
3.1 Overview
(2) Initialization of the modem or TA, line connection (dialing), and line
disconnection are performed using the programmable controller CPU.
3.1.1
Features
The following explains the features of the modem function.
(1) Interface that can use the modem function
(a) The modem function can be used with the Q series C24 using an RS-232 interface.
(b) For the QJ71C24(N)-R2 and LJ71C24-R2, the modem function can be used for only
one of the two RS-232 interfaces.
Through the other interface of the Q series C24, direct data communication with an external device can be
performed using MC protocol, non procedure protocol or bidirectional protocol (independent operation).
QJ71C24-R2
CH1.
CH2.
CH1.
CH2.
Communication using
the modem function
Communication without using
the modem function
(2) Initialization, line connection and disconnection of the modem or TA
(a) The following set values for line connection can be used by storing to the Q series
C24 Flash ROM in multiple sets.
• Modem/TA initialization data (AT command)
User setup: 30 sets (78 bytes/set); default value: 13 sets
• Connection data
User setup: 30 sets (80 bytes/set)
(Telephone number of the connection destination and display message to the pager receiver.)
(b) By registering the above data to the Q series C24 ahead of time, the modem/TA
(terminal adapter) initialization, line connection (dialing), and line disconnection can
be performed with ease.
(c) When the no-communication interval time (1 min to 120 min) is set, the Q series C24
disconnects the line when a no-communication condition has occurred for the set
period of time following the line connection.
70
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(3) Communication between a remote external device and programmable
controller CPU
(a) Data communication can be performed via full-duplex communication.
(b) From the external device to the programmable controller CPU, communication
using the MC protocol, non procedure protocol and bidirectional protocol can be
3
performed.
(c) From the programmable controller CPU to the external device, communication
using the MC protocol (transmission by the on-demand dedicated-protocol function
only), the non procedure protocol and bidirectional protocol can be performed.
3.1 Overview
71
(4) Notification to the pager receiver
(a) In order to notify to the pager receiver of the programmable controller system
maintenance information, the Q series C24 performs calling and message
transmission according to the user-designated connection data when the output
signal from programmable controller CPU is turned from ON to OFF.
(b) Because Q series C24 notification processing is performed while the output signals
from programmable controller CPU are turned OFF from ON, dedicated notification
can be performed when the programmable controller CPU enters the STOP state due
to an error, etc.
QJ71C24-R2
Q25HCPU
MODE
RUN
CH1.
CH2.
ERR.
USER
BAT.
Notification
BOOT
Modem
CH1.
USB
CH2.
RS-232
Out of material
detection
Notification-issued
request Y14
Notification execution
direction
Data number for
connection
0
1
0
n
(5) Communication from GX Developer
(a) Access from GX Developer to the remote programmable controller CPU can be
made. (read and write from/to the device data and sequence program)
(b) The QCPU can be accessed after reconnection from the Q Series C24 side using the
callback function.*1
GX Developer
QJ71C24-R2
Q25HCPU
MODE
RUN
CH1.
CH2.
ERR.
USER
BAT.
BOOT
Public line
Modem
CH1.
RS-232
cable
USB
RS-232
*1
72
CH2.
Modem
RS-232
cable
Transmission costs after line connection by callback from the Q Series C24 side are borne by the Q Series C24 side.
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(6) Remote password check
If the remote password check has been set for the Q series C24 installed in the QCPU, the Q series C24
executes a remote password check when the programmable controller is accessed from an external device using
the Q series C24 modem function.
The following is an overview of the QCPU remote password function. For more details, see Page 86, Section
3.3.3.
3
(a) Remote password function
The remote password function allows / prohibits access to the QCPU from an external device via the following
modules.
• Q series C24
• Ethernet module
• Built-in CPU of Ethernet port
*1
In the case of the Ethernet module, the remote password function can be used for data communications connections
with an external device. For details, see the User's Manual (Basic) for the Ethernet module.
(b) Station where the remote password and remote password check are set
• In the case of a programmable controller system with one QCPU station
GX Developer parameter setting
⋅ Remote password
⋅ Module subject to the remote
password check
QCPU
External device
access source
Q series C24
Public line
Remote
password
check
Remote
password
Modem
Modem
Communication executing the
remote password check
• In the case of a programmable controller system consisted of multiple QCPU stations
Set in the QCPU station which is the entrance of the programmable controller system as viewed from the
external device (the local station QCPU in the diagram below).*1
Set in the local station to allow/prohibit access to
the network System 1 from the external device.
Remote
password
Remote
password
check
(Local station)
QCPU
Ethernet
module
Q series C24
Public line
Modem
Modem
External device
access source
Ethernet
(Relay station) QCPU
Ethernet
module
Ethernet
module
QCPU
Ethernet
module
(Access station)
Ethernet
Not set in the relay station or access station. (*)
Network System 1
*1
When set in a station other than the QCPU which is the entrance of the programmable controller system (relay station or
access station in the above diagram), access to other stations beyond the set station is prohibited.
73
3.1 Overview
⋅ Communication using MC protocol
⋅ Communication using the GX Developer
3.1.2
Function list
The following lists the overview of the modem function:
Function
Overview
Modem/TA initialization
Initializes the modem/TA using the user-designated initialization data (AT command). (Auto initialization of the modem / TA is
possible.)
Line connection (dialing)
Dials the partner telephone number according to the user-designated connection data and enables data communication after
establishing the line connection.
When the modem/TA is not initialized, performs initialization.
Performs communication with an external device using the MC protocol, non procedure protocol
or bidirectional protocol.
Data communication
Performs communication with the partner Q series C24-installed station by modem/TA
connection using non procedure protocol or bidirectional protocol. (Station-to-station
communication)
Enables the communication between GX Developer and programmable controller via Q series
C24.
Communication method:
full-duplex communication
Synchronization method:
start-stop synchronous
system (asynchronous)
Notification
Calls and transmits messages to the pager receiver.
Line disconnection
Forcefully disconnects the line from the connected destination device.
Flash ROM reading, writing
(registration) and deletion
Reads, writes (registers) and deletes the initialization data (AT command) and data for connection from/to the Flash ROM in the
Q series C24 according to the request from programmable controller CPU.
Remote password check
Allows the Q series C24 to execute the remote password check set in the QCPU when there is communication from the
external device to the Q series C24 using MC protocol or the programmable controller is accessed using GX Developer.
Callback
After line connection from GX Developer, access to the QCPU from GX Developer is made possible through line reconnection
from the Q Series C24 (callback). Transmission costs after line connection from the Q Series C24 side are borne by the Q
Series C24 side.
74
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
3.1.3
Comparisons with related devices
The following lists the comparison with the related products which supports data communication with the
programmable controller using the modem and public line, etc., similarly to the communication performed via the
modem function.
Communication function name
QJ71C24N(-R2/R4),
QJ71C24(-R2) (function
version)
B
Modem/TA initialization
Q6TEL (for
QnACPU/ACPU)
A6TEL (for
ACPU)
*1




(Performed on the external device side)
MC protocol



Nonprocedural protocol



Bidirectional protocol



Communication between Q series C24 and other products




Remote communication from GX Developer








Communication between
same products (such as
C24-C24)
Remote communication from GX Developer (Callback
function)



GX Configurator-SC
Line connection (dialing)


Remote communication from peripheral device for GPPQ




Remote communication from peripheral device for GPPA




Notification






Pager receiver
Remote password check




Sequence program




GX Developer




GPPQ




GPPA




GX Configurator-SC




Number of connectable modems/TAs
1
Transmission type
Connectable lines
(Performed on the external device side)
3.1 Overview
Data setting (data for
modem initialization, data
for connection)
*2

Line disconnection
Pulse/tone
Analog 2-line method




Analog 4-line method




Digital line (ISDN)




: enable, : disable
*1
*2
3
A

Sequence program
QC24N (modem
function)
Modem initialization is executed automatically when the Q Series C24 starts up.
Prior to data communication, the Q series C24 checks whether the remote password specified by the user and the
remote password set in the QCPU agree or not. If they agree, it allows access to the specified station.
75
3.2
System Configuration
This section describes system configurations when the modem function is used to call a pager receiver or to perform
data communication with an external device via public lines.
3.2.1
System configuration when performing data communication
with an external device
The following describes the system configuration examples used when performing data communication between the
external device and programmable controller using the Q series C24's MC protocol/non procedure
protocol/bidirectional protocol.
(1) Connection example with an external device*1*2
External device
QJ71C24-R2
Q25HCPU
MODE
RUN
CH1.
CH2.
ERR.
USER
BAT.
BOOT
Modem
CH1.
Public line
RS-232
cable
USB
Modem
RS-232
cable
CH2.
RS-232
(2) Connection example with a Q series C24*1*2
QJ71C24-R2
Q25HCPU
QJ71C24-R2
Q25HCPU
MODE
RUN
CH1.
MODE
RUN
CH2.
ERR.
USER
BAT.
BOOT
ERR.
USER
BAT.
BOOT
Public line
RS-232
cable
RS-232
76
CH2.
CH1.
Modem
CH1.
USB
CH1.
Modem
USB
RS-232
cable
RS-232
CH2.
CH2.
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(3) Connection example with a Q series C24 via cellular phone*1
MODE
RUN
CH1.
MODE
RUN
CH2.
CH2.
USER
BAT.
USER
BAT.
BOOT
BOOT
Public line
Modem
CH1.
RS-232
cable
RS-232
CH1.
ERR.
ERR.
USB
QJ71C24-R2
Q25HCPU
QJ71C24-R2
Q25HCPU
CH1.
3
Cellular
Phone
USB
CH2.
CH2.
RS-232
Cellular phone
connection adapter
*1
*2
The public line is compatible with the office telephone system as well.
The digital line (ISDN) can replace the public line.
When connecting via a digital line, a TA (terminal adapter) and a DSU (digital service module) are used instead of a
modem.
3.2 System Configuration
77
3.2.2
System configuration when using the notification function
The following describes the system configuration example when calling the pager receiver by the notification
function.*1
QJ71C24-R2
Q25HCPU
MODE
RUN
CH1.
CH2.
ERR.
USER
BAT.
BOOT
Public line
Modem
CH1.
RS-232
cable
USB
CH2.
RS-232
*1
78
The public line is compatible with the office telephone system as well.
Pager receiver
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
3.2.3
System configuration when connecting GX Developer
The following describes the system configuration when GX Developer performs data communication with a remote
station programmable controller via Q series C24.*1*2
GX Developer
QJ71C24-R2
Q25HCPU
MODE
RUN
CH1.
3
CH2.
ERR.
USER
BAT.
BOOT
Public line
Modem
CH1.
RS-232
cable
USB
RS-232
*1
*2
CH2.
Modem
RS-232
cable
The public line is compatible with the office telephone system as well.
Set items as below for "Transfer Setup" screen using GX Developer.
• PC side I/F: Serial
• PLC side I/F: C24
• Telephone line connection (Q/A6TEL, C24): Data for line connection
Set the other items corresponding to the access destination station.
For how to display the "Transfer Setup" screen, refer to manuals for GX Developer.
When GX Developer is connected, perform the settings and operations described in Page 120, Section 3.3.7 to prevent a
line to the modem from disconnecting even if communication between the GX Developer and programmable controller is
interrupted.
3.2 System Configuration
79
3.2.4
Precautions for system configurations
The following describes the precautionary items when configuring the system to perform data communication with an
external device or call a pager receiver via public line, an office telephone system or digital line (ISDN) using the Q
series C24 modem function.
(1) Usable Q series C24 interface
(a) The modem function can be used for the RS-232 interface only.
(b) For the QJ71C24(N)-R2 and LJ71C24-R2, the modem function can only be used for
only one of the two RS-232 interfaces.
(c) Interactive data communication via two interface of Q series C24 (linked operation)
is not possible.
(2) Connectable modem/TA
(a) Only the modems/TA indicated in Page 83, Section 3.3.2 can be used for the Q series
C24 RS-232 interface using the modem function.
(3) Number of connectable modems/TA's
(a) Only one modem/TA can be connected to the Q series C24 RS-232 interface that
uses the modem function.
(4) Modem/TA connection cables
(a) The RS-232 cable supplied with the modem/TA or the designated modem/TA cable
can be used for connection between the Q series C24 and modem/TA.
(b) For the RS-232 interface of the Q series C24, a D-sub 9-pin connector (female) is
used. For the connection cable of the Q series C24 side, refer to the User's Manual
(Basic).
(5) Modem/TA installation
(a) Install the modem/TA according to the modem/TA manual. When installed in an area
in which a lot of noises exists, malfunctions may occur.
(b) In order to prevent the effects of noise and power surges, do not connect near or tie
the cable together with a main circuit line, high-voltage line or load line other than
for the programmable controller with the modem/TA connection cable.
80
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(6) Connectable lines
(a) The connections can be made with the following lines.
Perform connection tests beforehand and confirm that connection is possible.
• Public line or office telephone system of analog two-line method
• Digital line (ISDN)
3
(b) It is not possible to connect to call-waiting lines, in order to avoid data errors or
automatic line disconnection due to the call-waiting interrupt tone.
(c) Avoid connections with party-line telephones to avoid interrupted calls during
communication.
(d) If an alert sound is sent at fixed intervals from the communication machine to
prevent long-term calls, data may experience errors.
It is recommended to check the normality/abnormality of data reception between devices, and perform
transmission-retry processing when an abnormality is detected.
(e) See the modem/TA manual regarding the connection from a modem to public
line/office telephone system, or from a TA (terminal adapter) to a digital line.
(7) Communication system
Communication via the modem function is performed using full-duplex communication.
Connections cannot be made devices designed for half-duplex communication.
(a) Data communication with external devices and notification to a pager receiver are
performed using the public line or electric wave transmitted from the electric wave
transmission base.
There might occur a condition in which correct data communication or notification cannot be carried out due to
an error from the system's setup environment, electric-wave transmission status, error in the partner device,
etc. Perform connection tests beforehand and confirm that connection is possible.
(b) In notification processing via electric-wave transmission, errors from the pager
receiver cannot be detected. Setup a separate call circuit with a lamp display or
buzzer to ensure the safety of the programmable controller system.
81
3.2 System Configuration
(8) Data communication and notification to external devices
3.3
Specifications
This section explains the transmission specification on the Q series C24 side, connectable modems/TA's (terminal
adapter), I/O signals related to the modem function, and buffer memory for the usage of the modem function.
3.3.1
Transmission specifications
The transmission specifications on the Q series C24 side for use of the modem function are as listed below.
The transmission specifications between Q series C24 and a modem/TA (local station Q series C24) that are not
provided in this table are listed in the User's Manual (Basic).
Item
Modem function
Linked operation between CH1 and CH2 of the Q series C24
Communication method
1
Data bit
7/8
Parity bit
1 (On) / 0 (Off)
Stop bit
1/2
Parity check
Sum check code
Transmission control

On (odd/even selectable) / Off
On / Off
RS/CS control yes/no (selectable)
Nonprocedural protocol
Available
Bidirectional protocol
Available
MC protocol
Pre-defined protocol
Line connection (Q series C24: modem)
82
RS-232
Not available
Asynchronous method
Start bit
*1
Not available
1200, 2400, 4800, 9600, 14400, 19200, 28800, 38400,
57600, 115200 (bps)
Transmission speed*1
Data communication
QJ71C24N-R4
Full-duplex communications
Synchronization method
Error detection
QJ71C24N-R2
QJ71C24-R2
LJ71C24-R2
Available
Interface that can use the modem function
Data format
QJ71C24N
QJ71C24
LJ71C24
Available
Not available
1:1
When the first five digits of the serial No. are 03042 or earlier, the transmission speed cannot be set to 115200 bps for
connection between the Q series C24 and GX Developer via a modem.
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
3.3.2
Specification of connectable modems/TAs (terminal adapters)
The following table lists the specification of modems/TAs that can be connected to the Q series C24 side when the
modem function is used.
(1) Specification and precautions for the connectable modems
3
(a) Modem specification
Specifications
When using the
subscriber's telephone
line/office telephone system
Item
Connection line
Analog 2-line
Initialization
Telephone line
Communication
standard
Modem-to-modem
communication
specification
ITU-T
V.34/V.32bis/V.32/V.22bis/V.22/V.21/V.fc
ITU-T
V.42 compliant
Data
MNP
Class 5 compliant
compression*1
ITU-T
DR signal control

V.42bis compliant

Mode switching required
9-pin (female) D sub
Only the DR (DSR) signal must be able to turn on
Compatible with the Q series C24 specification
 User's Manual (Basic)
*2
 Page 82, Section 3.3.1,
 User's Manual (Basic)
The following are the functions of the modem itself that become available by issuing the AT commands to the modem.
See the modem manual for details.
 Error correction
• When a noise occurs on the line, scrambled data may appear due to interrupted communication data. The error
correction function is intended to suppress effects from such noises.
• If an error such as scrambled data is detected by the error correction, the modem retries the transmission. When
the number of retries has exceeded the modem's limit, the modem determines that communication cannot be
performed in that environment and disconnects the line.
• Both modems must support the MNP4 or V.42 protocol.
 Data compression
• This function compresses data to be sent prior to transmission, and inflates the compressed data upon reception,
then forwards to the terminal.
• The data compression is effective for the execution speed at a maximum of 200% for the MNP5 and 300% for the
V.42bis.
• Both modems must support the MNP5 or V.42bis protocol.
 Flow control (RS/CS control)
When communication between a modem and terminal is faster than between two modems, the flow control is performed
in the following order:
• The modem transmits data to the partner by storing the data from the terminal in the modem buffer.
• When the buffer in the modem becomes almost full, the modem outputs a data-transmission temporary stop
request (CS (CTS) signal = OFF) to the terminal. The terminal then stops data transmission to the modem when
the data-transmission temporary stop request (CS (CTS) signal = OFF) is received. Even while the terminal
pauses data transmission, the modem continues to send data to the partner.
• When a free space is present in the modem buffer, the modem outputs the data-transmission resume request (CS
(CTS) signal = ON) to the terminal. The terminal then resumes data transmission to the modem when the datatransmission resume request (CS (CTS) signal = ON) is received.
Modems that turn on the CD (DCD) signal simultaneously cannot be used.
83
3.3 Specifications
*2
 Page 80, Section 3.2.4
regarding the restrictions
212A/103
Other
*1
A line compatible with NTT communication protocol
Class 4 and 10 compliant
Q series C24-side
connector (RS-232)

Page 134, Section 3.4.3
Bell
ANS-ORG mode switch
Remarks
Hayes AT command compatible
MNP
Error correction*1
Q series C24-to modem
communication
specification
When using a manual line
connection/cellular phone
(b) Precautions for selecting a modem
• When using a cellular phone
A modem with the error correction function of MNP class-10 is recommended. However, note that
communication may not be established depending on the line condition.
• Modem setting
• Set the modem on the Q series C24 side as shown below:
Setting item
Setting range
Communication rate
Depends on the modem in use*1
Modem command
Hayes AT command
SI/SO control
None
Communication method
No procedure
Data bit
Data format
Stop bit
Match the Q series C24*2*3
Parity bit
*1
*2
*3
When using different modems, the slower communication rate will be in effect.
Some modems may transmit one character as 10 bits.
Check the modem specifications when setting the Q series C24 transmission specifications.
Some modems may switch the communication rate following the start of data communication.
Since the Q series C24 cannot switch the communication rate, set the modem side so that its communication rate does
not switch.
• When using a modem whose DR terminal (signal) is set by a switch, set the DR-terminal (modem output)
switch level to high. When using a modem requiring DR terminal setting with software, write the command
that turns on the DR (DSR) signal into the data for initialization. Set the "Modem initialization time DR
signal valid/invalid designation" to "Invalid" during modem function system settings with GX ConfiguratorSC.
84
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(2) Specification and precautions for the connectable TA's (terminal adapters)
(a) TA specification
Item
TA-to-TA communication
specification
Q series C24-to-TA
communication
specification
*1
Specifications
Remarks
Connection line
ISDN (INS net 64) equivalent, High-speed digital dedicated line
DSU and TA are required
Initialization
Hayes AT command compatible
Page 134, Section 3.4.3
Communication standard
B-channel line exchange (V.110), D-channel packet exchange
Electrical condition
V.28 compliant
Circuit definition
V.24 compliant
Q series C24-side
connector (RS-232)
9-pin (female) D sub
DR signal control
Only the DR (DSR) signal must be able to turn on
Other
Compatible with the Q series C24 specification
3

 User's Manual (Basic)
*1
 Page 82, Section 3.3.1,
 User's Manual (Basic)
TA's that turn on the CD (DCD) signal simultaneously cannot be used.
Use a TA capable of flow control as described in Page 83, Section 3.3.2 (1) (a) also for the communication between the
TA and terminal. Flow control is a function of the TA itself that becomes available by issuing the AT commands to the
modem. See the TA manual for details.
(b) Precautions for selecting a TA
• Set the TA on the Q series C24 side as listed below:
Setting item
Setting range
Communication rate
Depends on the TA in use
TA command
Hayes AT command
SI/SO control
None
Communication method
No procedure
Stop bit
Match the Q series C24*1*2
Parity bit
*1
*2
Some TAs may transmit one character as 10 bits. Check the TA specifications when setting the Q series C24
transmission specifications.
Some TAs may switch the communication rate following the start of data communication. Since the Q series C24 cannot
switch the communication rate, set the TA side so that its communication rate does not switch.
• When using a TA whose DR terminal (signal) is set by a switch, set the DR-terminal (TA output) switch level
to high. When using a TA requiring DR terminal setting with software, write the command that turns on the
DR (DSR) signal into the data for initialization. Set the "Modem initialization time DR signal valid/invalid
designation" to "Invalid" during modem function system settings with GX Configurator-SC.
85
3.3 Specifications
Data bit
Data format
3.3.3
Compatibility with the QCPU remote password function
This section explains the Q series C24 data communication for the QCPU remote password function.
Refer to Page 70, Section 3.1.1 for an overview of the Q series C24 check function for the QCPU remote password.
● The remote password function is a function that has been added to the QCPU as a means of preventing improper access
(such as destroying a program or data) from an external device. However, this function cannot completely prevent
improper access.
● The user should incorporate his/her own safeguards when it is necessary to protect the security of the programmable
controller system from improper access from an external device.
● The company cannot assume any responsibility for any problems that may arise from system troubles caused by
improper access.
An example of a safeguard on the programmable controller CPU with respect to improper access
One example is shown in Page 105, Section 3.3.6, in which the programmable controller CPU disconnects a line to the
external device when the number of times a "remote password mismatch" is detected exceeds the number set by the
user with regard to the Q series C24 remote password check explained in this section.
(1) Data communication during remote password setting
This section explains the use and setting of the QCPU remote password function and data communication
between the external device and the QCPU when a remote password has been set.
(a) Allowing/prohibiting access to the programmable controller from the external
device
1) Access allow processing (unlock processing)
• To access the specified QCPU, the external device performs the remote password unlock processing with
respect to the Q series C24*1 of the directly connected station (local station) after line connection for the
modem function.
• If the unlock processing has not been performed, the remote password check performed by the Q series
C24*1 that has received a communication request prohibits access to the specified station. ( Page 88,
Section 3.3.3 (2))
• All data communication before the unlock processing is performed will be processed as an error.
*1
The Q series C24 of the QCPU station for which a remote password is set will be indicated.
2) Access processing
• Normal completion of the remote password unlock processing allows the specified station to be accessed.
• Perform communication using MC protocol. (Perform on-line operation when GX Developer is connected.)
3) Access prohibition processing (lock processing)
• When the specified station access is completed, the process for disconnecting the line for the modem
function is performed in order to disable further access.
• When line disconnection is completed, the remote password lock processing is performed automatically.
86
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(When accessing other station QCPU)
(When accessing the local station QCPU)
A station
A station
(*1)
(*1)
1) Unlock processing
1) Unlock processing
Modem
Modem
2) Access
Modem
3) Lock processing (*2)
Remote password Remote password
(Local station)
check
QCPU
Modem
3) Lock processing (*2)
Remote
password
Q series C24
Remote password
check
QCPU
Q series C24
(*3)
3
(Local station)
Ethernet
module
Ethernet
*1 Unlock and lock processing for the local station remote password is possible.
Remote password unlock and lock processing for the relay station
and access station cannot be performed
*2 Lock processing is performed when a line for the modem function is disconnected.
QCPU
Ethernet
module
Ethernet
module
*3 Even if the Ethernet module that transmits a communication request
to other Ethernet is set as a module subject to the remote password check,
unlock and lock processing is not necessary.
(Relay station)
Ethernet
2) Access
QCPU
Ethernet
module
(Access station)
● The remote password unlock and lock processing can be performed only for the Q series C24 of the local station directly
connected to the external device. The remote password unlock and lock processing cannot be performed for the Ethernet
module of the other stations (relay station and access station).
● See Page 121, Section 3.3.7 (8) for what to do when the remote password unlock processing is completed abnormally.
87
3.3 Specifications
● The remote password unlock processing from the external device is performed using dedicated commands for MC
protocol communication.
(2) Remote password check processing performed by the Q series C24
(a) Communication in which a remote password check is performed
1) When the following parameters are set for the Q series C24 installed in the QCPU station, the Q series C24
performs a remote password check for communication requests listed below.
• When a remote password is set in the QCPU
• When the Q series C24 that is communicating data with the external device has been set as a module
subject to the remote password check
2) The Q series C24 performs a remote password check with respect to a communication request to the local
station/other station received from the external device.
3) The Q series C24 does not perform a remote password check for the following communication requests.
• Transmission request from the local station QCPU (such as transmission using non procedure protocol)
• Communication request from the external device (including GX Developer connected to the local station
QCPU) transmitted to other station upon request from the QCPU
Modem
QCPU
Modem
Q series
C24
Remote password
(Local station)
Ethernet module
Path for items subject
to remote password check
Remote password
check
1)
Path for items not subject
to remote password check
2)
(Other station)
3)
3)
GX Developer
QCPU
Remote
password
Remote password
check
(*1)
Ethernet module
*1
In the above diagram, a communication request from the external device cannot be received since the remote password
check setting has been executed.
If the remote password check setting has not been executed, a communication request can be received and data
communication from the external device is possible.
(b) Selecting modules subject to the remote password check
The user can select any Q series C24 to perform the remote password check and set this using QCPU
parameters. (This is set on the GX Developer remote password setting screen.)
88
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(c) Stations that can be accessed when the remote password check is performed
• If the external device performs the remote password unlock processing with respect to the Q series C24 of
the directly connected station (local station) after line connection for the modem function, it can access the
local station QCPU.
• When accessing the programmable controller of another station via the Ethernet module of a relay station or
access station, the following settings determine whether access is allowed/prohibited.
• To prohibit access to other station from an external device using the CC-Link IE Controller Network,
MELSECNET/H or MELSECNET/10 relay communication function of the Ethernet module, place a check
3
mark at the following setting items in the remote password setting for the relay station or access station.
"GX Developer communication port (UDP/IP)*1, dedicated commands, CC IE Control, MNET/10(H) relay
communication port"
*1
Set on the GX Developer remote password setting screen.
• If a check mark is not placed at the above setting items, access to other station will be allowed.
• See the user's manual (Basic) for the Ethernet module for stations that can be accessed when accessing
other station programmable controllers via the Ethernet module. (When reading the manual, substitute the Q
series C24 with the station connected to the external device).
(3) Data communications procedure
This section explains the procedure when the external device performs data communication via the Q series C24
in which the remote password check is performed.
(a) Initialization of the modem of the Q series C24 side and external device side is
performed at each device sides.
(b) The line is connected from the external device.
the QCPU of the station where the Q series C24 is installed using dedicated
commands for MC protocol communication.*1 (The unlock processing cannot be
performed for the QCPU of other station.)
*1
See Page 121, Section 3.3.7 (8) for what to do when the remote password unlock processing is completed abnormally.
(d) Data communication is performed from the external device using MC protocol.
(e) When data communication using MC protocol is completed, a line for the modem is
disconnected from the external device.
When line disconnection is completed, the remote password lock processing is performed automatically.
Remark
● Refer to the MELSEC Communication Protocol Reference Manual for the unlock processing command for the remote
password.
● When accessing the programmable controller from GX Developer connected to the Q series C24, the remote password
unlock processing is performed when on-line operation begins.
89
3.3 Specifications
(c) The external device performs the remote password unlock (release) processing for
(4) How to set the remote password
On the screen below for setting parameters (remote password) using GX Developer, set the remote password in
the QCPU and specify the Q series C24 that performs the check.
Set the remote password as the following instructions.
[Starting procedure]
"GX Developer"  [Remote password]  "Remote password setting" screen
[Setting screen]
[Setting item]
Item name
Password settings
Password active
module settings
*1
Set data
Enter the remote password to be set in the QCPU
Setting range/choices
*1
4 bytes
Model name
Select the type of module that checks the remote password set in the
QCPU
QJ71C24/CMO
Start XY
Set the head address of the module that checks the remote password
0000H to 0FE0H
Conditions
(No setting required)

Consider the following when setting the remote password.
• Avoid using a character string of simple numbers or letters only.
• Mix numbers, letters and special characters (?, ., !, &, %, etc.).
• Avoid using a character string that represents the user's name or date of birth.
● When using the Q series C24 in a multiple CPU system, write the remote password setting in the control CPU of the Q
series C24.
● After setting the remote password in the QCPU, reboot the QCPU (CPU No. 1 in a multiple CPU system). (Reset/power
reset using the RESET/L.CLR switch) By rebooting the QCPU, the remote password becomes valid.
● The password supported by the QCPU function version A is used to prohibit reading/writing of file data in the QCPU using
GX Developer.
Dual access control can be provided by using the remote password described in this section and password for file
access.
90
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(5) Setting from GX Configurator-SC
When the Q series C24 performs a remote password check for the remote password set in the QCPU, the remote
password check setting as well as the present check results can be monitored with respect to the screen items
listed in the table below.
See Page 105, Section 3.3.6 for an explanation of each area.
GX Configurator-SC setting/monitor screen
"Modem function system setting" screen
"Modem function monitor/test" screen
Setting/monitor items for the remote password check
Buffer memory address
Remote password mismatch notification count designation
8204 (200CH)
Remote password mismatch notification accumulated count designation
8205 (200DH)
Remote password mismatch notification count designation
8204 (200CH)
Remote password mismatch notification accumulated count designation
8205 (200DH)
Accumulated count of unlock process normal completion
8955 (22FBH)
Accumulated count of unlock process abnormal completion
8956 (22FCH)
Accumulated count of lock process based on circuit line disconnection
8959 (22FFH)
3
3.3 Specifications
91
3.3.4
Compatibility with the callback function
The following describes the Q Series C24 callback function that can be used when accessing the QCPU from GX
Developer connected to the Q Series C24.
(1) About the Callback function
(a) What is the Callback function
The callback function is a function that makes it possible to access the QCPU from GX Developer by
reconnection (callback) of the line from the Q Series C24. Transmission costs after line connection from the Q
Series C24 side are borne by the Q Series C24 side.
(b) Settings in order to use the callback function
The callback function can be used by setting it through GX Configurator-SC, then registering it in the Q Series
C24. ( Page 96, Section 3.3.4 (4))
(c) Selecting the callback destination GX Developer
GX Developer that can be called back in accordance with the settings in the Q Series C24 can be selected as
described below.
• If the callback destination GX Developer is fixed (1 module)*1
(Callback connection (during fixed))
Connection can be made to only fixed GX Developer (1 module) registered in the Q Series C24.
• If it is being made possible to change the callback destination GX Developer*1
(Callback connection (during designated number))
It is possible to connect to GX Developer when the callback destination telephone number (Call number) is
specified.
• If the maximum number of callback destination GX Developer is limited to 10 modules*1
(Callback connection (during max. designated number is 10))
Connection is possible with only those pieces of GX Developer (max. 10 modules) with a callback destination
telephone No. registered in the Q Series C24.
*1
A description of the callback operation in 1) to 3) is shown in Page 97, Section 3.3.4 (4) (b).
1) Line Connection
Setting of callback function
designation settings by the
GX Configurator-SC
2) Temporary line disconnection
3) Line connection
Selection of the
connection system
and line connections
4) Access to the QCPU
5) Line disconnection
Modem
Modem
GX Developer
Q Series C24
Processing for the GX Developer
to access the QCPU
Processing by the callback function
92
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(2) Data communications procedure
Here, the procedure for data communications when using the callback function is shown.
(a) Q series C24 side procedure
Carry out procedure of starting the modem function and data communications in accordance with Page 126,
Section 3.4.1.
3
• Set the callback function by GX Configurator-SC. ( Page 96, Section 3.3.4 (4))
• Initialize the Q Series C24 side modem. ( Page 126, Section 3.4)
• The modem's initialization completed signal (X10) goes On when modem initialization is completed. Wait
for the line connection from GX Developer.*1*2
*1
*2
Select the connection system (connect way) from GX Developer, then make line connection.
When the Q Series C24 callback processing is completed normally, the line connection signal (X12) is in the ON state.
See the GX Developer's Operating Manual for details of the line connection screen from the GX Developer when using the
callback function.
(3) Cautions during data communications
(a) Set the GX Developer side modem which the Q Series C24 is to reconnect to
(callback) on "with Auto Reception". (With Auto Reception: This setting enables line
connection from the external device.)
(b) When a request is issued for a line connection from another GX Developer during a
the Q Series C24 executes a callback operation for the latter connection request.
The Q Series C24 terminates callback processing to GX Developer that it received a connection request from
earlier.
93
3.3 Specifications
temporary line disconnection from the GX Developer side by callback processing,
(c) If you are making a line connection to the GX Developer by the following connection
system, select "callback reception waiting" as the connection system for GX
Developer that the Q Series C24 is reconnecting to (callback) and make the
connection.
• Callback request (during fixed/during designated number)
In the case of line connections with "Callback request (during designated number)" as the connection
system.
Setting of callback function
designation settings by the
GX Configurator-SC
Select "Callback request (during designation number)",
input the telephone No. 2) and make the line connection.
Callback request
(during designated number)
GX Developer
Telephone No. 1)
Modem
Modem
Select "Callback reception waiting"
and make the line connection.
Registration in the Q Series C24
Callback data No. 1
Telephone No. 1)
Callback data No. 2
Telephone No. 2)
Callback data No. 3
Telephone No. 3)
to
to
Callback data No. 10
Telephone No. 10)
Line connection
GX Developer
Telephone No. 2)
Modem
"Callback
reception waiting"
(d) If callback processing was not executed normally, an error message screen is
displayed on the GX Developer side. Perform the processing operation
(reconnection operation, etc.) corresponding to the displayed message.
The operating state on the Q Series C24 side can be confirmed by the following items in the GX ConfiguratorSC monitor/test screen.
GX Configurator-SC Monitor / test screen
XY monitor/test
Modem function monitor/test
94
Monitor item
Buffer memory address
X10: Modem initialization
completion

X12: Connection in progress

Modem function sequence status
222H
Reference
Page 102, Section 3.3.5
Page 105, Section 3.3.6
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(e) Set the settings related to the callback function in the following areas of GX
Developer.
[Starting procedure]
GX Developer  [Tools]  [Options]  [TEL]
• Line callback cancel wait time (Setting range: 1 to 180 s. (Default: 90 s.))
This specifies the waiting time after sending a response to a callback request from the Q Series C24, until the
3
line is disconnected from GX Developer.
If the line is not disconnected from GX Developer within the specified time in this area, the Q Series C24
forcibly disconnects the line, terminating callback processing.
• Callback delay time (Setting range: 1 to 999s. (Default: 20s.))
This specifies the time from the temporary line disconnect on the GX Developer side until the Q Series C24
reconnects (callback).
Refer to the Q Corresponding Serial Communication Module User's Manual (Basic) for the symptoms, causes, and actions
of problems that may occur during access from GX Developer to the QCPU when using the callback function.
3.3 Specifications
95
(4) Setting and monitoring by GX Configurator-SC for use of the callback function
(a) Setting, monitoring / test items
Carry out setting, monitoring and testing of the callback function using the following GX Configurator-SC
screen.
• Setting items through the "Modem function system setting" screen
This shows the callback function setting items.
See Page 105, Section 3.3.6 for the modem function setting items, including the following items.
Setting item
Setting value
Setting
possible /
impossible
Description
GX Developer connection designation
Connect
●
Be sure so specify "Connect" when using the callback
function.
Callback function designation
Settings 1 to 6
( Page 97,
Section 3.3.4 (4)
(b))
●
Select according to the callback operation.
Callback denial notification accumulated count
designation
0 to 65535

Specify the accumulated count value informed to the
user.
Data No. for Callback designation 1 to 10
BB8H to 801FH
●
Specify the connection data No. See Page 139,
Section 3.4.4 for setting values.
●: Must be set, : Set as necessary
• Monitoring / Testing through the "modem function monitor / test" screen
This shows the callback function monitoring and testing.
See Page 105, Section 3.3.6 for monitoring and testing of the modem function, including the following items.
Callback function monitoring / test items
96
Buffer memory address
Callback permit accumulated count
8944 (22F0H)
Callback denial accumulated count
8945 (22F1H)
Auto (callback) connection permit accumulated count
8946 (22F2H)
Auto (callback) connection denial accumulated count
8947 (22F3H)
Accumulated count of callback receive procedure cancel
8948 (22F4H)
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(b) Callback function designation and callback operation outline
Here the setting values for "Callback function designation" items in the "Modem function system setting" screen
and an outline of the corresponding Q Series C24 callback operation are explained.
Setting values for "Callback function designation" items.
If you desire to set the connection
system on "auto" and carry out
line connection
If you set the connection system
on "auto" and do not carry out
line connection
Auto (0H)*1

2) If the callback destination GX Developer is fixed (1 module)
(Callback connection (during fixed))
Setting 1 (9H)*1*2
Setting 4 (1H)*1
3) If it is being made possible to change the callback destination GX Developer
(Callback connection (during designated number))
Setting 2 (BH)*1*2
Setting 5 (3H)*1
4) If the maximum number of callback destination GX Developer is limited to 10
modules
(Callback connection (during max. designated number is 10))
Setting 3 (FH)*1*2
Setting 6 (7H)*1
Function
1) If the callback function is not used
*1
*2
3
Values in parentheses are values when the set values are stored in buffer memory (Address: 2001H).
If the connection system is set on "Auto (Callback: during fixed/Callback: during designated number)" and line
connection is executed, (Setting 1 to Setting 3) are explained in 5).
1) If the callback function is not used (Auto (0H) (Default Value)
• Select this if the callback function is not being used.
• Data communications becomes possible after line connection from GX Developer.
2) If the callback destination GX Developer is fixed (1 module) (Setting 1 (9H) or setting 4 (1H))
• Select this if the Q Series C24 fixes the telephone No. (1 module) of the GX Developer side that is being
called back.
• The Q Series C24 executes callback to the GX Developer side using connection data set in the following
data No. 1 for callback, shown below. At this time, the external line dialing, line types and telephone
• Set callback data No. 1 in the "Modem function system settings" screen.
If line connections are being made with "Callback connection (during fixed)" as the connection system
1) Line Connection
(Callback connection (during fixed))
Setting of callback function
designation settings by the
GX Configurator-SC
2) Temporary line disconnection
Selection of the
connection system
and line connections
3) Line connection to Telephone No. 1
4) Access to the QCPU
5) Line disconnection
Modem
Modem
GX Developer
Registration in the Q Series C24
Callback data No. 1
Telephone No. 1)
Processing for the GX Developer
to access the QCPU
Callback data No. 2
Telephone No. 2)
Processing by the callback function
Callback data No. 3
Telephone No. 3)
to
to
Callback data No. 10
Telephone No. 10)
Not used
97
3.3 Specifications
number in the connection data become valid.
3) If it is being made possible to change the callback destination GX Developer (Setting 2 (BH) or Setting 5
(3H))
• Select the callback destination telephone No. if it is being specified at the time when line connections are
being made from the initial GX Developer side.
• The Q Series C24 calls back GX Developer with the callback destination telephone No. received from the
GX Developer side. At this time, the external line dialing, line types and the connection data set in the
following callback data No. 1 are used.
• If the callback destination is not specified when line connections are made from the initial GX Developer
side, the connection data set in the following callback data No. 1 are used to call back the GX Developer
side. At this time, the external line dialing, line types and telephone number in the connection data become
valid.
• Set callback data No. 1 in the "Modem function system settings" screen.
If line connections are being made with "Callback connection (during designated number)" as the
connection system
Input the telephone No. 1)
for the callback destination
telephone No. and make line
connections.
Setting of callback function
designation settings by the
GX Configurator-SC
Line Connection
(Callback connection
(during designated number))
GX Developer
telephone No. 1)
Modem
Callback
Modem
Line Connection
(Callback connection
(during designated number))
Input the telephone No. n)
for the callback destination
telephone No. and make line
connections.
Registration in the Q Series C24
98
Callback data No. 1
Telephone No. 1)
Callback data No. 2
Telephone No. 2)
Callback data No. 3
Telephone No. 3)
to
to
Callback data No. 10
Telephone No. 10)
Callback
Not used
Modem
GX Developer
telephone No. n)
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
4) If the maximum number of callback destination GX Developer is limited to 10 modules (Setting 3 (FH) or
Setting 6 (7H))
• Select GX Developer to be called back if the Q Series C24 limits the callback destination to a maximum of
10 modules.
• Specify the callback destination telephone No. when making line connection from the initial GX Developer
side.
• If the Q Series C24 checks the callback destination telephone No. received from the GX Developer side
and it is a telephone No. that is registered in the Q Series C24, callback is executed. If a telephone No.
that is not registered in the Q Series C24 is received from the GX Developer side, the Q Series C24
3
disconnects the line and does not execute callback.
• Data for checking the callback destination telephone No. by the Q Series C24 are registered in callback
Data No. 1 to 10. Set the data registered in callback data No. 1 to 10 in the "Modem function system
setting" screen.
If line connections are being made with "Callback connection (during designated number)" as the
connection system
Input the telephone No. 1)
for the callback destination
telephone No. and make line
connections.
Set the Callback function designation by
the GX Configurator-SC.
* Check the received telephone No. If it is
registered, make the line connection.
Line Connection
(Callback connection
(during designated number))
GX Developer
telephone No. 1)
Modem
Callback
Modem
Input the telephone No. 2)
for the callback destination
telephone No. and make line
connections.
Registration in the Q Series C24
Callback data No. 1
Telephone No. 1)
Callback data No. 2
Telephone No. 2)
Callback data No. 3
Telephone No. 3)
to
to
Callback data No. 10
Telephone No. 10)
Callback
Modem
GX Developer
telephone No. 2)
99
3.3 Specifications
Line Connection
(Callback connection
(during designated number))
5) If line connections from GX Developer are made with "Auto (Callback: during fixed/Callback: during
designated number)" as the connection system (Setting 1 (9H) to Setting 3 (FH))
• When accessing the QCPU from GX Developer, select whether to use the callback function to make line
connections or to make line connections without using the callback function.
• If the following is selected for the GX Developer connection system and line connections made, it is possible
to access the QCPU from the GX Developer by that method only on that occasion.*3
●Auto (callback: during fixed)
●Auto (callback: during designated number)
*3
The procedure is the same as when accessing the QCPU by selecting "Auto" for the connection system and making line
connections.
• If line connections are made with the callback destination GX Developer limited to a maximum of 10 modules
set, (setting 3 (FH)), select "Auto (Callback: during designated number)" as the connection system and
specify the telephone No. The Q Series C24 checks the telephone No. received from the GX Developer side
and if it is registered in the Q Series C24, the line connection status is held and it becomes possible to
access the QCPU from GX Developer. If a telephone No. is received from GX Developer that is not
registered in the Q Series C24, the Q Series C24 disconnects the line.
• Data for checking the callback destination telephone No. by the Q Series C24 are registered in callback Data
No. 1 to 10. Set the data registered in callback data No. 1 to 10 in the "Modem function system setting"
screen.
If line connections are being made with "Auto (Callback: during designated number)" as the connection
system
1) Line Connection
(Auto (callback: during designated number))
Setting of callback function
designation settings by the
GX Configurator-SC
Selection of the
connection system
and line connections
2) Temporary line disconnection
3) Line connection
4) Access to the QCPU
5) Line disconnection
Modem
Modem
GX Developer
telephone No. 1)
Registration in the Q Series C24
100
Callback data No. 1
Telephone No. 1)
Callback data No. 2
Telephone No. 2)
Callback data No. 3
Telephone No. 3)
to
to
Callback data No. 10
Telephone No. 10)
Processing for the GX Developer
to access the QCPU
Processing by the callback function
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
Remark
I If the GX Configurator-SC's "Callback function designation" setting is performed in the Q Series C24, line connections to
GX Developer are possible by the connection system listed below.
The correspondence between the GX Configurator-SC "Callback function designation" setting items and the GX Developer
connection system setting items is listed.
Q Series C24 Side Callback function specification
3
GX Developer connection system*1
1)
2)
3)
4)
5)
6)
7)
8)
9)
Auto









Setting 1: Auto/Callback connection (during fixed)









Setting 2: Auto/Callback connection (during designated number)









Setting 3: Auto/Callback connection (during max. designated
number is 10)









Setting 4: Callback connection (during fixed)









Setting 5: Callback connection (during designated number)









Setting 6: Callback connection (during max. designated number is
10)









: Connection possible
*1
101
3.3 Specifications
This shows the GX Developer connection system. See the GX Developer Operating Manual for details about line
connection from GX Developer.
1) Auto
2) Auto (callback: during fixed)
3) Auto (callback: during designated number)
4) Callback connection (during fixed)
5) Callback connection (during designated number)
6) Callback request (during fixed)
7) Callback request (during designated number)
8) Callback reception waiting
9) Manual
3.3.5
List of I/O signals for the modem function
The I/O signals with the programmable controller CPU for the modem function are described.
Refer to the User's Manual (Basic) for the other I/O signals.
(1) I/O signal list
102
Device
number
Signal description
Device
number
X0
CH1 Transmission normal completion, ON: Normal
completion
Y0
CH1 Transmission request, ON: Requesting
transmission
X1
CH1 Transmission abnormal completion, ON:
Abnormal completion
Y1
CH1 Reception data read completion, ON: Data
read completed
X2
CH1 Transmission processing, ON: Transmission in
progress
Y2
CH1 Mode switching request, ON: Requesting
switch
X3
CH1 Reception data read request, ON: Requesting
read
Y3
X4
CH1 Reception abnormal detection, ON: Abnormal
detection
Y4
X5
(Use prohibited)
Y5
X6
CH1 Mode switching, ON: Switching
Y6
X7
CH2 Transmission normal completion, ON: Normal
completion
Y7
CH2 Transmission request, ON: Requesting
transmission
X8
CH2 Transmission abnormal completion, ON:
Abnormal completion
Y8
CH2 Reception data read completion, ON: Data
read completed
X9
CH2 Transmission processing, ON: Transmission in
progress
Y9
CH2 Mode switching request, ON: Requesting
switch
XA
CH2 Reception data read request, ON: Requesting
read
YA
XB
CH2 Abnormal reception detection, ON: Abnormal
detection
YB
XC
(Use prohibited)
YC
XD
CH2 Mode switching, ON: Switching
YD
XE
CH1 ERR occurrence, ON: Error occurring
YE
CH1 ERR. information clear request, ON:
Requesting error clear
XF
CH2 ERR occurrence, ON: Error occurring
YF
CH2 ERR. information clear request, ON:
Requesting error clear
Signal description
(Use prohibited)
(Use prohibited)
X10*1*3
Modem initialization completion, ON: Initialization
completed
Y10*1*3
Modem initialization request (standby request), ON:
Requesting initialization
X11*1*3
Dialing, ON: Dial in progress
Y11*1*3
Connection request, ON: Requesting connection
X12*1*3
Connection, ON: Connection in progress
Y12*1*3
Modem disconnection request, ON: Requesting
disconnection
X13*1*3
Initialization/connection abnormal completion, ON:
Initialization/connection abnormal completed
X14*1*3
Modem disconnection completion, ON:
Disconnection completed
Y13
Y14*1*2*3
(Use prohibited)
Notification-issued request, OFF: Requesting
notification issuance
X15*1*2*3
Notification normal completion, ON: Normal
completion
Y15
X16*1*2*3
Notification abnormal completion, ON: Abnormal
completion
Y16
X17
Flash ROM read completion, ON: Completed
Y17
X18
Flash ROM write completion, ON: Completed
Y18
Flash ROM write request, ON: Requesting
X19
Flash ROM system setting write completion, ON:
Completed
Y19
Flash ROM system setting write request, ON:
Requesting
X1A
CH1 Global signal, ON: Output directed
Y1A
X1B
CH2 Global signal, ON: Output directed
Y1B
(Use prohibited)
Flash ROM read request, ON: Requesting
(Use prohibited)
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
Device
number
*1
*2
*3
Signal description
Device
number
X1C
System setting default completion, ON: Completed
Y1C
X1D
Pre-defined protocol ready, ON: Ready
Y1D
X1E
Q series C24 ready, ON: Accessible
Y1E
X1F
Watchdog timer error (WDT error)
ON: Module error occurred
OFF: Module being normally operated
Y1F
Signal description
System setting default request, ON: Requesting
(Use prohibited)
Cannot be used for the QJ71C24N-R4. (Signal for the modem function.)
Cannot be used for the LJ71C24(-R2).
Signal for the modem function.
3
● Of the input/output signals to the programmable controller CPU, the signals marked with "Use prohibited" must not be
output (ON). If any of the "Use prohibited" signals is output, the programmable controller system may malfunction.
● 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.
3.3 Specifications
103
(2) Function and description of each I/O signal
I/O signal
Signal name
Function/description
X10
Modem initialization
completion
Indicates normal completion of the Q series C24's initialization of the modem/TA
connected to itself according to the initialization data designated.
X11
Dial in progress
Indicates that the Q series C24 is dialing (connection processing) the partner side
according to the data for connection designated.
Reference
Page 144, Section
3.4.5
Page 148, Section
3.4.6
X12
Connection in progress
• Indicates normal completion of the line-connection processing from or to the partner
side.
• When this signal is on, data communication with the destination is possible
(notification is not possible).
X13
Initialization/connection
abnormal completion
• Indicates abnormal completion of the modem/TA initialization or line connection
processing (dialing) to the destination.
• Check the cause of the abnormal completion in the modem error code storage area
(address: 221H) and remove the cause.
X14
Modem disconnection
completion
Indicates that the line for data communication with the destination has been
disconnected.
X15
Notification normal
completion
Indicates the normal completion when performing the notification processing to the
destination.
X16
Notification abnormal
completion
• Indicates abnormal completion when the notification processing is performed with the
destination.
• Check the cause of the abnormal completion in the modem error code storage area
(address: 221H) and remove the cause.
Y10
Modem initialization request
(standby request)
• Indicates the initialization request to the modem connected to the local station Q
series C24.
• Turn on the initialization-request signal after designating the initialization data to the
buffer memory when it is not set with GX Configurator-SC.
Page 144, Section
3.4.5
Y11
Connection request
• Indicates the connection request (dialing) to enable data communication with the
destination.
• Turn on the connection request signal after designating the data for connection to the
buffer memory when it is not set with GX Configurator-SC.
• If the modem/TA connected to the local station is not initialized, the Q series C24side modem is initialized as well prior to dialing, according to the initialization data
designated.
Page 148, Section
3.4.6
Y12
Modem disconnection
request
Y14
Notification-issued request
Indicates a line-disconnection request from the partner side upon completion of data
communication.
• Indicates the notification request to the partner side.
• Turns on before completing the Q series C24-side modem/TA initialization is
complete.
• Turns off the notification-issued request signal after designating the data for
connection in the buffer memory when it is not set with GX Configurator-SC.
Page 144, Section
3.4.5, Page 148,
Section 3.4.6
Page 161, Section
3.4.8
Page 154, Section
3.4.7
Page 161, Section
3.4.8
Page 154, Section
3.4.7
The descriptions hereafter show an example in which I/O numbers of the Q series C24 are assigned to X/Y00 to X/Y1F.
104
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
3.3.6
Buffer memory
The buffer memory that can be used with the modem function is described.
Refer to the User's Manual (Basic) for the buffer memory not related to the modem function.
The writing and reading of setting values to and from the buffer memory are performed using the special utility package ("GX
Configurator-SC") of the Q series C24.
This section provides supplementary explanations on setting values used to perform settings and monitoring with GX
Configurator-SC.
3
(1) Buffer memory list
Address Dec. (Hex.)
CH1
Application
Name
CH2
0 (0H)
1 (1H)
For LED and
communication
error clear
2 (2H)
Communication error clear request for CH2 and to turn LED
off
0
Non
Bi
RW
Register/read/delete result storage
0
RW

Number of data bytes registration designation
6 to 45 (6H to 2DH)
User frame
46 (2EH)
Modem connection channel directions
0: None, 1: CH1, 2: CH2
47 (2FH)
Notification execution designation*2
0: Does not execute, 1: Execute
48 (30H)
Number of connection retries designation
1 to 5: Number of retries
49 (31H)
Connection retry interval designation
90 to 300: Connection retry interval (unit: s)
180
50 (32H)
Initialization/connection timeout designation
1 to 60: Time out (unit: s)
60
51 (33H)
Number of initialization retries designation
1 to 5: Number of retries
3
52 (34H)
Data number for initialization designation
0H: Sends initialization data designated by the transmission
user frame designation area
7D0H to 801FH: Data No. for initialization
0
3.3 Specifications
For modem
functions
designation-1*3
54 (36H)
MC
Frame No. direction
For Flash ROM
access
5 (5H)
53 (35H)
Correspondence
protocol
Register/read/delete directions
3 (3H)
4 (4H)
Communication error clear request for CH1 and to turn LED
off
Default
value
3
7D0H
(2000)
RW
Data number for connection designation
BB8H to 801FH: Data number for connection
[When using Q series C24]
GX Developer connection designation
0: Does not connect, 1: Connects
0
[When using L series C24]
MELSOFT connection designation
0: Does not connect, 1: Connects
55 (37H)
No-communication interval time designation
0: Waits infinitely
1 to 120: Non-communication interval time (Line disconnection
wait time)
(Unit: min)
30
56 (38H)
RS/CS control yes/no designation
0: Does not control, 1: Controls
1
105
Address Dec. (Hex.)
CH1
Application
CH2
57 to 127 (39H to 7FH)
(Use prohibited)
128 (80H)
For programmable
controller CPU
information clear*1
129 to 143 (81H to 8FH)
Transmission specification designation after switching
304 (130H)
305 (131H)
For specifying
mode switching
146 (92H)
306 (132H)
Signal setting*1
183 (B7H)
343 (157H)
184 (B8H)
344 (158H)
185 (B9H)
345 (159H)
186 to 285
(BAH to 11DH)
346 to 445
(15AH to 1BDH)
544 (220H)
Correspondence
protocol
MC
Non
Switching mode number designation
RS and DTR signal status designation
0
RW
0005H
RW
CR/LF output designation
Transmission user
frame
Output head pointer designation
Output count designation
0

RW
Transmission frame No. designation (A maximum of 100
frames can be designated.)
Flash ROM system parameters write result
0
RW
545 (221H)
Modem function error code
0: Normal completion
1 or more: Abnormal completion (error code)
0
RW
546 (222H)
Modem function sequence status
0: Idle status
1: Waiting for initialization
2: Initializing modem
3: Standby in progress
4: Checking password
5: Communication in progress
6: Notification in progress (Valid for Q series C24 only, not for
L series C24.)
7: Modem disconnection
8: Callback Request reception waiting
9: Callback Modem disconnect waiting
10: Callback Delay time waiting
11: Callback Reconnecting
12: Callback Rechecking password
0
Flash ROM
For modem
function
confirmation*3
547 (223H)
548 to 549 (224H to 225H)
550 (226H)
551 to 552 (227H to 228H)
Bi
Programmable controller CPU information clear request
0000H: No request
4C43H: Requested
System area
145 (91H)
Default
value
System area
(Use prohibited)
144 (90H)
106
Name
R
Number of data registrations for connection
0: No registration, 1 or more: Number of registration
Data registration status for connection (for conformation of
registration No.)
0: No registration, 1: Registered
• Bits for registration number are 0 (ON)/1 (OFF)
Registration number BB8H (3000): Address 224H (b0) to
Registration number BD5H (3029): Address 225H (b13)
Number of data registrations for initialization
0: No registration, 1 to 30: The number of registrations
Data registration status for initialization
0: No registration, 1: Registered
• Bits for registration number are 0 (ON)/1 (OFF)
Registration number 9C4H (2500): Address 227H (b0) to
Registration number 9E1H (2529): Address 228H (b13)
The values
vary
depending
on the
registration
status

CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
Address Dec. (Hex.)
CH1
Application
Name
CH2
Number of notification executions
0: Not executed, 1 or more: Number of executions
553 (229H)
554 (22AH)
555 to 557 (22BH to 22DH)
:
Notification status
confirmation*2*3
Data
storage
area 1
(Use prohibited)
3072 to 6911 (C00H to 1AFFH)
For user
6912 to 6952 (1B00H to 1B28H)
(For registration No. 8001H)
For user
8192 (2000H)
registration*3
*3
(Use prohibited)
System
designation
8193 (2001H)
For callback
function*3
8194 (2002H)
8195 to 8198 (2003H to 2006H)
0
(Use prohibited)
Bi
R
R
3

0
Notification execution data number
0: No notification execution
BB8H or more: Notification executed
(Notification executions number)
R
0

System area
User free area (3840 words)
• Application is determined by the user.
0
User registration area (Registration No. 8001H to 801FH)
The user registration area has the following combined uses,
with data written by the user according to the purpose of use
by the TO instruction, etc.
See each explanation item concerning the configuration of
each area, the data written, etc.
0
If data communications is being carried out by user
registration frame
• User frame ( Page 220, CHAPTER 9)
If data communications is being carried out by the modem
function
• Initialization Data ( Page 134, Section 3.4.3)
• Connection Data ( Page 139, Section 3.4.4)
0
RW

RW

RW
System area
Flash ROM writing allow/prohibit designation
0: Write prohibited, 1: Write allowed
0
Callback function designation
0H: Auto
1H: Callback connection (during fixed) (Setting 4)
3H: Callback connection (during designated number) (Setting
5)
7H: Callback connection (during max. designated number is
10)
(Setting 6)
9H: Auto/Callback connection (during fixed) (Setting 1)
BH: Auto/Callback connection (during designated number)
(Setting 2)
FH: Auto/Callback connection (during max. designated
number is 10) (Setting 3)
0
Callback denial notification accumulated count designation
0H: Not specified
1H to FFFFH: Notification accumulated number count
1
3.3 Specifications
8183 to 8191 (1FF7H to 1FFFH)
Non
System area (Use prohibited)
574 to 590 (23EH to 24EH)
8142 to 8182 (1FCEH to 1FF6H)
(For registration No. 801FH)
MC
System area (Use prohibited)
571 to 573 (23BH to 23DH)

Correspondence
protocol
Notification execution data number
0: No notification execution
BB8H or more: Notification executed
(Notification executions number)
:
Data
storage
area 5
570 (23AH)
Default
value
RW
RW

System area
107
Address Dec. (Hex.)
CH1
Application
Name
CH2
Default
value
8199 (2007H)
Auto modem initialization designation
0: No auto initialization, 1: Auto initialization
0
8200 (2008H)
Modem initialization time DR (DSR) signal valid/invalid
designation
0: DR signal is not ignored., 1: DR signal is ignored.
1
Complete signal handling designation for modem function
0: Does not turn ON/OFF from X13 to X16
1: Turns ON/OFF from X13 to X16
1
Wait time of notification*2
0H: No waiting time
1H to FFFFH: Wait time of notification (Notification interval
time)
(Unit: s)
10
For modem
function
8201 (2009H)
designation-2*3
8202 (200AH)
8203 (200BH)
(Use prohibited)
8204 (200CH)
For remote
password
8205 (200DH)
8207 (200FH)
8449 to 8458 (2101H to 210AH)
Remote password mismatch notification count designation
0H: No designation
1H to FFFFH: Count for notification
0
designation - 3*3
(Use prohibited)
System area
function*3
Data No. for callback designation 1 to 10
0BB8H to 0BD5H, 8001H to 801FH: Data number for callback
8944 (22F0H)
Callback permit accumulated count
0 or more: Accumulated count
8945 (22F1H)
Callback denial accumulated count
0 or more: Accumulated count
For callback
8946 (22F2H)
function*3
Auto (callback) connection permit accumulated count
0 or more: Accumulated count
8947 (22F3H)
Auto (callback) connection denial accumulated count
0 or more: Accumulated count
8948 (22F4H)
Accumulated count of callback receive procedure cancel
0 or more: Accumulated count
8949 to 8954 (22F5H to 22FAH)
(Use prohibited)
8955 (22FBH)
For remote
password
8956 (22FCH)
function*3
8957 to 8958 (22FDH to 22FEH)
(Use prohibited)
For remote
password
8959 (22FFH)
function*3
9216 (2400H)
(Use prohibited)
9728 to 16383 (2600H to 3FFFH)
*1
*2
*3
108
For user*1
Bi
RW

RW
Circuit disconnect wait time (programmable controller CPU
watch use)
0000H to FFFH: Wait time (Unit: s)
For callback
Non
0
1
For modem
function
8206 (200EH)
MC
System area
Remote password mismatch notification accumulated count
designation
0H: No designation
1H to FFFFH: Notification accumulated number count
function*3
Correspondence
protocol

RW
0
RW

0
RW

0
RW

0
RW

System area
Accumulated count of unlock process normal completion
0 or greater: Accumulated count of normal completion
Accumulated count of unlock process abnormal completion
0 or greater: Accumulated count of abnormal completion
System area
Accumulated count of lock process based on circuit line
disconnection
0 or greater: Accumulated count of lock process based on
circuit line disconnection
System area
User free area 2 (6656 words)
(Communication data monitoring function default buffer)
• Application is determined by the user.
Only the QJ71C24N (-R2/R4) are usable. (System area when using QJ71C24 (-R2))
Only the Q series C24 is usable. (System area when using the L series C24)
Buffer memory areas that can be used with the modem function
0
RW
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
Do not write data in the system area of the buffer memory.
If data is written in the system area, the programmable controller system may operate abnormally.
There is also a partial system area in the user's area. Be careful when reading and writing from and to the buffer memory.
3
3.3 Specifications
109
(2) Details of the buffer memory (for modern function)
(a) Modem connection channel designation area (address 46 (2EH))
The interface on the Q series C24 side to which a modem/TA is connected is designated.
(b) Notification execution designation area (address 47 (2FH))
Whether or not to perform notification (message transmission) to the pager receiver during the fall of the
notification-issued request signal Y14 is designated.
(c) Number of connection retries designation area (address 48 (30H))
• Designates the number of retries for the notification/connection request when the connection could not be
made to the partner device by the notification request/connection request.
• The default value is recommended to use for the number of connection retries.
(d) Connection retry interval designation area (address 49 (31H))
• Designates the interval time of the retry processing for the notification/connection request when the
connection could not be made to the partner device by the notification request/connection request.
• The default value is recommended to use for the connection retry interval.
(e) Initialization/connection timeout time designation area (address 50 (32H))
• The following wait times are designated.
• Wait time until the modem/TA initialization is complete.
• Wait time per wait when the connection could not be made to the destination by the notification/connection
request.
• The default value is recommended to use for the initialization/connection retry timeout.*1
*1
Shown below is the relationship of the number of connection retries designation, connection retry interval designation
and the time for initialization/connection timeout time designation used for the notification/connection request to the
partner device.
• Number of connection retries: 3 times
• Connection retry interval: 180s
• Initialization/connection retry timeout: 60s
Notification
60 s
Notification abnormal
completion signal
X16
Notification-issued
request signal
Y14
Q series C24 ready
signal
X1E
180 s
(1st retry)
(2nd retry)
(3rd retry)
Notification
Notification
Notification
60 s
180 s
60 s
180 s
60 s
(f) Number of initialization retries designation area (address 51 (33H))
The number of retries when the initialization per the initialization request to the modem on to the Q series C24
side has failed.
110
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(g) Data number for initialization designation area (address 52 (34H))
• The registration number for the initialization data transmitted with the initialization request to the modem on
the Q series C24 side is designated. The registration number for the Q series C24 is used.
• For details on the designation using GX Configurator-SC, refer to Q Corresponding Serial Communication
Module User's Manual (Basic).
An example of designations using the program is shown in Page 144, Section 3.4.5.
3
(h) Data number for connection designation area (address 53 (35H))
• Designates the registration number of the data for connection used by the Q series C24 for the connection
processing to the partner device in order to perform data communication/notification. The registration
number for the Q series C24 is used.
• For details on the designation using GX Configurator-SC, refer to Q Corresponding Serial Communication
Module User's Manual (Basic).
An example of designations using the program is shown in Page 148, Section 3.4.6.
(i) GX Developer connection designation area (address 54 (36H))
• Whether to access the programmable controller from GX Developer by connecting the Q series C24 and GX
Developer using the Q series C24 modem function is designated.
• When connecting the Q series C24 and GX Developer using the Q series C24 modem function, select "PLC
side I/F = via telephone line connection (Q/A6TEL, C24)" in the "Transfer Setup" screen of GX Developer.
(When connecting direct shown in Page 79, Section 3.2.3). When this GX Developer designation is
performed, designate "1" in this area on the Q series C24 side.
(j) No-communication interval time designation area (address 55 (37H))
• Designates the wait time until the line is closed when the data communication has ceased with the
destination device after the line connection.
performed with the destination device for a designated time. The connection in progress signal (X12) and the
modem initialization completion signal (X10) turn off and the modem disconnection completion signal (X14)
turns on when the line disconnection processing is performed.
(k) RS/CS control yes/no designation area (address 56 (38H))
• Designates whether to use the RS/CS signals for controls to notify local station-side data reception capability
to the partner side during data transmission between the Q series C24 and modem/TA.
• This setting is for the interface designated by the modem connection channel indicated in Page 110, Section
3.3.6 (2) (a). The control of the other interface that does not use the modem function is performed by the
settings in the buffer memory DTR/DSR and DC control designation area (address: 93H/133H).
111
3.3 Specifications
• The Q series C24 automatically performs the line disconnection processing when no data communication is
Remark
The overview of the RS/CS controls are described.
1) When transmitting data
● The Q series C24 detects the modem/TA data reception capability from on/off of the CS (CTS) signal.
● When the CS (CTS) signal is on, data transmission from the Q series C24 starts or continues. When the CS (CTS) signal
is off, data transmission from the Q series C24 is interrupted.
2) When receiving data
● The Q series C24 side reception capability is notified to the modem/TA by the on/off of the RS (RTS) signal.
● When the RS (RTS) signal is on, the Q series C24 can receive data. Start/continue data transmission from the modem/TA
to the Q series C24. When the RS (RTS) signal is off, the Q series C24 cannot receive data. Cancel data transmission
from the modem/TA to the Q series C24.
● The on/off of the RS (RTS) signal is controlled by the following conditions of the Q series C24:
• OFF  ON control of the RS (RTS) signal: Performed when the OS area for reception data storage in the Q series
C24 becomes 64 bytes (default) or less.
• OFF  ON control of the RS (RTS) signal: Performed when the OS area for reception data storage in the Q series
C24 becomes 263 bytes (default) or more.
(l) Modem function error code storage area (address 545 (221H))
• Stores the error code when an error occurs during the modem function or abnormal signal (such as the
initialization/connection abnormal completion signal X13) turns on.
• Refer to the User's Manual (Basic) for the error codes.
(m) Modem function sequence status storage area (address 546 (222H))
• The current status during use of the modem function is stored as a number.
• See Page 126, Section 3.4.1 for storage values for the modem function sequence status when using the
modem.
(n) Number of data registrations for connection storage area (address 547 (223H))
• Stores in Flash ROM the number of registered data for connection used by the Q series C24 for the
connection processing with the partner device in order to perform data communication/notification. The
number of registrations is the number of data for connection registered to the Flash ROM by the user.
• The registration of data for connection is described in Page 139, Section 3.4.4.
112
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(o) Data registration status for connection storage area (address 548 to 549 (224H to
225H))
• Stores in Flash ROM registration status of data for connection used by the Q series C24 in the connection
processing with the partner device in order to perform data communication/notification.
• The registration status of each data for connection with registration numbers of No.BB8H to BD5H (3000 to
3029) is indicated in the corresponding bit in the range shown in the figure below.
3
Registration status of data for connection number BB8H (3000)
Registration status of data for connection number BC7H (3015)
Buffer memory address
b15
b14
0
0
b13
b12
to
b2
b1
b0
548 (224H)
549 (225H)
Registration status of data for connection number BD5H (3029)
Registration status of data for connection number BC8H (3016)
0 (OFF): No registration
1 (ON): Registration exists
(p) Number of data registrations for initialization storage area (address 550 (226H))
• Stores in Flash ROM the number of data registrations for initialization, sent to the modem on the Q series
C24 side with the initialization request. The number of registrations indicates the number of data for
initialization registered to the Flash ROM by the user.
(q) Data registration status for initialization storage area (address 551 to 552 (227H to
• Stores in Flash ROM registration status for initialization of data for initialization transmitted with the
initialization request to the modem on the Q series C24 side.
• The registration status of each data for initialization with registration numbers of No.9C4H to 9E1H (2500 to
2529) is indicated in the corresponding bit in the range shown in the figure below.
• The registration of data for initialization is described in Page 134, Section 3.4.3.
Registration status of the data for initialization number 9C4H (2500)
Registration status of the data for initialization number 9D3H (2515)
b15
Buffer memory address
b14
552 (228H)
b13
b12
to
b2
b1
b0
to
551 (227H)
0
0
to
Registration status of the data for initialization number 9E1H (2529)
Registration status of the data for connection number 9D4H (2516)
0(OFF): No registration
1(ON): Registration exists
113
3.3 Specifications
228H))
(r) Number of notification execution storage area (address 553 (229H))
• Stores the number of execution of the Q series C24 notification (message transmission) processing for the
pager receiver.
• The storage value when the number of notification execution exceeds 32767 remains at 32767.
• The value for this area can be changed by the user in the range of 0 to 32767. When the storage value is
changed by the user, the number of execution is stored according to the changed value.
(s) For notification execution data storage: Notification execution data number storage
area (address 554, 558... (22AH, 22EH...))
• Stores the registration number of the data for connection used in the Q series C24 notification (message
transmission) processing to the pager receiver as log information.
• The latest five data is stored in order at the corresponding areas (data 1, data 2, ....). (The latest information
is stored in the data 1 notification execution data number storage area.) The old notification execution data
number other than the latest five are deleted in order.
b15
Buffer memory address
b0
to
554(22AH)
0H, BB8H to BD5H, 8001H to 801FH (Data 1)
570(23AH)
0H, BB8H to BD5H, 8001H to 801FH (Data 1)
0: Notification not executed
BB8H or more: Notification executed
(execution number)
* BB8H to BD5H (3000 to 3029)
(t) For user registration frame registration: Number of bytes in registration data
designation area (address 6912, 6953... (1B00H, 1B29H...))
• The initialization data or data for connection can be stored into the buffer memory as well as the Q series
C24's Flash ROM.
Data type
Initialization data
Data for connection
Registration destination
Data registered by the OS
Flash ROM
Registration number (Decimal (hexadecimal))
2000 to 2013 (7D0H to 7DDH)
User-registered data
2500 to 2529 (9C4H to 9E1H)
Buffer memory
(All registered by user)
-32767 to -32737 (8001H to 801FH)
Flash ROM
(All registered by user)
3000 to 3029 (BB8H to BD5H)
Buffer memory
(All registered by user)
-32767 to -32737 (8001H to 801FH)
A registration number for the initialization data or the data for connection to the buffer memory is in the range of
-32767 to -32737 (8001H to 801FH), and determined by the used area.
• In this area, the number of bytes for the initialization data or data for connection (for 1 data) to be registered
to the buffer memory is designated.
• The registration of data for initialization is described in Page 134, Section 3.4.3. The registration of data for
connection is described in Page 139, Section 3.4.4.
b15
Buffer memory address
to
6912 (1B00H)
0 to 78/80
8142 (1FCEH)
0 to 78/80
b0
(Number of bytes)
0: No registration data
1 to 78: Registration data exists (for initialization)
80: Registration data exists (for connection)
114
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(u) For user frame registration: User frame designation area (address 6913 to 6952,
6954 to 6993... (1B01H to 1B28H, 1B2AH to 1B51H...))
• When registering the initialization data or data for connection to the buffer memory, the number of
registration data bytes (for 1 data) is designated.
• The registration of data for initialization is described in Page 134, Section 3.4.3. The registration of data for
connection is described in Page 139, Section 3.4.4.
3
Buffer memory address
6913 (1B01H)
to
6952 (1B28H)
Data for initialization or data for connection
8143 (1FCFH)
to
8182 (1FF6H)
Data for initialization or data for connection
(Area for registration number 8001H)
(Area for registration number 801FH)
(v) Auto modem initialization designation area (Address 8199 (2007H)
• This designates whether the Q Series C24 side modem is initialized automatically or not.
• Registration of this area is done through the GX Configurator-SC. The modem is initialized automatically
when the Q Series C24 starts up after the QCPU restarts.
(w) DR (DSR) signal valid/invalid designation area during modem initialization (address
8200 (2008H))
Set this setting to "DR signal valid."*1
*1
(x) Modem function completed signal handling designation area (address 8201 (2009H))
Set this setting to "turn ON/OFF X13 to X16" (default value).
(y) Wait time of notification designation area (address 8202 (200AH))
• Designates the waiting time from the moment the present notification is executed until the next notification is
executed (Unit: s), when performing more than one notification continuously. (Unit: s)
• Designates wait time of notification after checking the time required during debugging.
(z) Circuit disconnect wait time designation area (programmable controller CPU watch
use) (address 8206 (200EH))
• When sending data using the programmable controller CPU monitoring function, designates the time it takes
to complete data transmission from the local station side modem to the external device after data
transmission from the Q series C24 (wait time until the circuit is disconnected).
• Specify the circuit disconnect wait time to match the specifications of the modem that is being used.
115
3.3 Specifications
This setting is used to designate how the DR (DSR) signal is treated when only modem initialization is performed.
Following the completion of modem initialization, data is sent according to the status of the DR (DSR) signal.
(3) Details of buffer memory (for the remote password function)
Each of the areas described below is valid when the Q series C24 performs the remote password check.
(a) Remote password mismatch notification count designation area (address 8204
(200CH))
• Use 0 to FFFFH to designate the count that will be the notification timing to the QCPU when a remote
password mismatch occurs during the user/external device unlock processing after the modem line has
been connected.
• It cannot confirm the accumulated number of times a remote password mismatch occurred up to the present
after the line connection.
(b) Remote password mismatch notification accumulated count designation area
(address 8205 (200DH))
• Use 0 to FFFFH to designate the accumulated count that will be the notification timing to the QCPU when a
remote password mismatch occurs during the user/external device unlock processing after the Q series C24
has been started up.
• The accumulated number of times up to the present a remote password mismatch occurred (accumulated
count value in the Q series C24) after starting up can be checked in the area where the accumulated count
of unlock process abnormal completion is stored (address 8956 (22FCH)).
(c) Storage area for accumulated count of unlock process normal completion (address
8955 (22FBH))
The accumulated number of times the remote password unlock process has been completed normally is
stored.
(d) Storage area for accumulated count of unlock process abnormal completion
(address 8956 (22FCH))
The accumulated number of times the remote password unlock process has been completed abnormally is
stored.
(e) Storage area for accumulated count of lock process based on circuit line
disconnection (address 8959 (22FFH))
The accumulated number of times the Q series C24 has automatically performed the lock process due to a
modem line disconnection is stored.
Each of the accumulated count values stored in Page 116, Section 3.3.6 (3) (c) to Page 116, Section 3.3.6 (3) (e) above are
further explained below:
● The user can clear the values using either of the following:
• Set the accumulated count to "0" using the GX Configurator-SC modem function monitor/test screen.
• Write "0" to the applicable area of the buffer memory.
● The accumulated count will be stored as 0H  1H  2H... FFFFH  0H  1H ...
116
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(4) Details of buffer memory (for the callback function)
The areas shown below are valid if the Q Series C24 uses the callback function.
(a) Callback function designation area (Address 8193 (2001H))
• If communications are done by connecting to the GX Developer via a modem, specify whether the callback
function is to be used or not. Also specify the callback operation in the case that the callback function is
used.
• This specification becomes valid if "Connection" is entered in the GX Developer connection designation area
3
(Address 54 (36H).
• Show the setting value (the value stored in this area) in the GX Configurator-SC and show the corresponding
Q Series C24's callback operation. This becomes invalid if any setting values other than those shown below
are specified, and the callback function does not operate.
• When the callback function is not to be used: Auto (0H)
• When the callback function is to be used: Setting 1 (9H) to setting 6 (7H)
Setting 1 (9H): Auto/Callback connection (during fixed)
Setting 2 (BH): Auto/Callback connection (during designation number)
Setting 3 (FH): Auto/Callback connection (during max. designation number is 10))
Setting 4 (1H): Callback connection (during fixed)
Setting 5 (3H): Callback connection (during designation number)
Setting 6 (7H): Callback connection (during max. designation number is 10))
(b) Callback denial notification accumulated count designation area (Address 8194
(2002H))
• Use 0 to FFFFH to designate the accumulated count that will be the notification timing to the QCPU when a
denial of the callback occurs during access from GX Developer after the Q series C24 has been started up.
value in the Q series C24) after starting up can be checked in the area where the accumulated count of
denial of the callback is stored (address 8945 (22F1H)).
117
3.3 Specifications
• The accumulated number of times up to the present a denial of the callback occurred (accumulated count
(c) Data No. for Callback designation area (Addresses 8449 to 8458 (2101H to 210AH))
• This specifies the connection data registration No. where the callback destination GX Developer side's
telephone No. is registered. Connection data are data that have been registered in the Q Series C24's flash
ROM or buffer memory. See Page 139, Section 3.4.4 for connection data registration.
• In the following case, the connection data telephone No. specified in callback data No. 1 becomes the
callback destination.*1
• If the callback destination GX Developer is fixed (1 module)
*1
The external line dialing, line types and telephone number in the connection data become valid.
• In the following cases, when the callback destination telephone No. from the GX Developer is specified and
connection made, callback is performed using the external line dialing and line types in the connection data
for the registration No. specified in callback data No. 1.
• If it is being made possible to change callback destination GX Developer
• If the maximum number of callback destination GX Developer is limited to 10 modules
• If the callback destination GX Developer is limited to a maximum of 10 modules, specify the connection data
registration No. that specify the callback destination telephone No. for a maximum of 10 modules.
• The external line dialing, line types and telephone number in callback data No. 1 become valid.
• The telephone No. only becomes valid in callback data No. 2 to 10. The external line dialing and line types
in the connection data for callback data No. 1 are used for these.
• If "0H" is specified in this specification, the callback data No. after that become "unspecified."
If callback data No. 4 is specified as "0H," the callback data No. 4 to 10 registrations become invalid.
(d) Callback permit accumulated count storage area (Address 8944 (22F0H))
The accumulated count value when the Q Series C24 executed callback is stored here.
(e) Callback denial accumulated count storage area (Address 8945 (22F1H))
The accumulated count value for callbacks which the Q Series C24 did not executed due to callback error
detection is stored here.
(f) Auto (callback) connection permit accumulated count storage area (Address 8946
(22F2H))
The accumulated count value for normal line connections from GX Developer by the connection system listed
below is stored here.
• Auto (callback: during fixed)
• Auto (callback: during designated number)
(g) Auto (callback) connection denial accumulated count storage area (Address 8947
(22F3H))
The accumulated count value for line connections from GX Developer by the connection system shown below
that were not connected normally is stored here.
• Auto (callback: during fixed)
• Auto (callback: during designated number)
118
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(h) Accumulated count of callback receive procedure cancel storage area (Address
8948 (22F4H))
The accumulated count value for the number of callback procedures that were terminated from the initial GX
Developer by the Q Series C24 when a line connection request by another GX Developer was executed during
temporary line disconnect from the GX Developer side through callback specification is stored here.*1
*1
The Q Series C24 performs the callback operation with respect to the latest connection request.
3
Each of the accumulated count values stored in Page 118, Section 3.3.6 (4) (d) to Page 119, Section 3.3.6 (4) (h) above are
further explained below:
● The user can clear the values using either of the following:
• Set the accumulated count to "0" using the GX Configurator-SC modem function monitor/test screen.
• Write "0" to the applicable area of the buffer memory.
● The accumulated count will be stored as 0H  1H  2H... FFFFH  0H  1H ...
3.3 Specifications
119
3.3.7
Precautions when using the modem function
Precautions when using the modem function to perform data communication with an external device via public line or
call to the pager receiver are described.
(1) Line connection and disconnection
When performing data communication with an external device, it must be predetermined which station is to
perform the line connection (dialing) and disconnection processing with the partner device as well as the timings.
(2) Reception data before connection completion
Before the connection processing to the modem is completed the reception data other than modem commands is
ignored (read and disposed) at the interface that uses the modem function.
The Q series C24 will ignore the data even when an MC protocol command message is received.
(3) Transmission control
Delays may occur in transmission controls to notify the data reception capability at the local station to the partner
device.
In order not to have a state in which the partner device cannot receive the transmission data, the amount of
transmission/reception data and intervals should be determined beforehand.
When transmission/reception data in the non procedure protocol, the procedure must also be predetermined.
(4) Priority of data communication and notification
After line connection is established, the data transmission/reception processing with the partner device is
performed in the order of the processing request occurrence.
At the same time, when the line disconnect processing or data transmission reception (including data
transmission processing, reception processing and Flash ROM access processing) occurs, the line disconnect
processing has the priority.
(5) Data communication time
The data transmission/reception time after line connection has been established with the partner device is the
total time of the transmission time between the Q series C24 and modem/TA, between modem and TA, and
between modem/TA and partner device.
When communicating via the MC protocol, the transmission time (such as T0 and T3) indicated in the MELSEC
Communication Protocol Reference Manual must include the transmission time between the Q series C24-side
modem/TA and the destination device.
120
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(6) Initial Settings
The connection data used for modem functions can be registered as follows using setting procedures.
Set the telephone number and message within the permissible number of registration characters for modem/TA.
• If registered using GX Configurator-SC
• Comments can be set to a maximum of 254 bytes. (These are not used for control.)
• Telephone numbers can be set to a maximum of 62 bytes.
3
• Messages can be set to a maximum of 254 bytes.
• If registered from the programmable controller CPU (sequence program)
• Comments cannot be set.
• Telephone numbers can be set to a maximum of 18 bytes.
• Messages can be set to a maximum of 30 bytes.
(7) Programmable controller CPU monitoring function
See Page 67, Section 2.4 for precautions when transmitting monitoring results using the modem function.
(8) Remote password check
(a) How to unlock the remote password
• When the Q series C24 has been set as a module subject to the remote password check with the QCPU
parameter, a remote password unlock processing must be performed from the external device after line
connection before starting data communication.
• The unlock processing for the QCPU remote password is performed as follows:
• When communicating using MC protocol
Perform the unlock processing from the external device using dedicated commands.
Perform the unlock processing on the GX Developer screen when access begins.
(b) When the remote password unlock processing is completed abnormally
• Repeat the unlock processing after checking the remote password set in the QCPU.
• Start with the line connect processing again if the Q series C24 line connect signal (X12) turns OFF due to
the unlock processing abnormal completion.
• The user should clear the accumulated count stored in the following buffer memory before repeating the line
connect processing if the Q series C24 CHn side ERR occurrence signal (XE/XF) turns ON and the ERR
LED lights up due to the unlock processing abnormal completion.
(Applicable buffer memory)
Storage area for accumulated count of unlock process abnormal completion accumulated: Address 8756
(22FCH)
(How to clear) Cleared by the user using one of the following:
• Set the accumulated count to "0" using the GX Configurator-SC modem function monitor/test screen.
• Write "0" to the applicable area of the buffer memory.
121
3.3 Specifications
• When accessing the programmable controller from GX Developer
(c) When the number of times remote password mismatch occurs is large
• When the number of times notification of a remote password mismatch is received exceeds the number of
times specified in buffer memory address 8204 (200CH), the Q Series C24 disconnects the line
automatically. (The connection signal (X12) turns OFF.) After confirming the remote password registered in
the QCPU and the remote password specified in the external device execute line connection again.
• When the number of times notification of a remote password mismatch is received exceeds the accumulated
count value (buffer memory address 8205 (200DH)), the Q Series C24 executes the following processing.
(The line and modem are not disconnected.)
(when communicating using MC protocol)
• An error code (7FE8H) is stored in the buffer memory's MC protocol transmission error code storage area
(address 602/618 (25AH/26AH).
• The CHn side error occurrence signal (XE/XF) turns ON and the ERR LED lights up.
(When communicating using GX Developer)
• An error code (7FE8H) is stored in the buffer memory's modem function error code storage area (address
545 (221H).
• The CHn side error occurrence signal (XE/XF) turns ON and the ERR LED lights up.
• The accumulated number of times up to the present a remote password mismatch occurred (accumulated
count value in the Q series C24) can be checked in the area where the accumulated count of unlock process
abnormal completion is stored (address 8956 (22FCH)).
• The user should clear the accumulated number of times up to the present a remote password mismatch
occurred using one of the following methods.
• Set the accumulated count of unlock processing abnormal completion to "0" on the GX Configurator-SC's
modem function monitor/test screen.
• Write "0" in the buffer memory area where the accumulated count of unlock process abnormal completion
is stored (address 8956 (22FCH)).
If the CHn side ERR occurrence signal (XE/XF) for the Q series C24 turns ON and the ERR LED lights up, this could indicate
improper access from the external device.
See also an example of measures taken on the programmable controller CPU side described in Page 124, Section 3.3.7
(12).
Remark
Refer to the User's Manual (Basic) for the method for turning off the Q Series C24's ERR LED when it lights up.
122
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(9) Number of modules for which the remote password check can be set
A maximum of eight modules can be registered with remote passwords in the QCPU.*1
To set the remote password in a module, use the GX Developer remote password setting screen.
*1
The remote password modules are as follows:
• Q series C24
• Q series Ethernet module
• Built-in CPU of Ethernet port
3
(10)Callback function
(a) When the number of callback processing denials exceeds callback denial
notification accumulated count (buffer memory address 8194 (2002H), the following
processing is executed each time the Q Series C24 issues another refusal.
• An error code (7FE9H) is stored in the buffer memory's modem function error code storage area (address
545 (221H).
• The CHn side error occurrence signal (XE/XF) turns ON and the ERR LED lights up.
(b) When the number of callback processing refusals exceeds callback denial
notification accumulated count, after performing the following checks and clearing
processing, make the line connection again from GX Developer.
• Check the setting contents of the callback function set in the Q Series C24.
• Check the setting contents of the callback function set in GX Developer.
• The user should clear the accumulated counts stored in the following buffer memory areas.
(Applicable buffer memory)
Callback denial accumulated count: Address 8945 (22F1H)
• Set the accumulated count to "0" using the GX Configurator-SC modem function monitor/test screen.
• Write "0" to the applicable area of the buffer memory.
Remark
Refer to the User's Manual (Basic) for the method for turning off the Q Series C24's ERR LED when it lights up.
(11)Preventing a line disconnect when GX Developer is connected
Perform the following settings and operations to prevent a line to the modem from disconnecting even if
communication between GX Developer and programmable controller is interrupted.
(a) Initial setting by GX Configurator-SC
• Setting screen: Modem function system setting screen
• Setting item: No-communication interval time designation
• Setting value: 0 (infinite wait)
(b) Operation using GX Developer
Always perform the line disconnect operation when the GX Developer on-line operation is completed after the
line to the Q series C24 side is connected.
123
3.3 Specifications
(How to clear) Cleared by the user using one of the following:
(12)An example of what to do on the programmable controller CPU side for
improper access from the external device
The following is an example of performing, on the programmable controller CPU side, the line disconnect
processing with respect to the opposite device and prohibiting receive via a modem when the number of "remote
password mismatch" detected by the Q series C24 remote password check function exceeds the number set by
the user.
• The user should determine the count and accumulated count of notification given when a remote password
mismatch occurs during the unlock processing from the external device with respect to the remote password
set in the QCPU. ( Page 116, Section 3.3.6 (3) (a),  Page 116, Section 3.3.6 (3) (b))
• In the GX Configurator-SC system settings, in order for the Q series C24 to operate, set the count
determined above in the following item on the "Modem function system setting" screen and register this to
the Q series C24.
• Set in the item "Remote password mismatch notification count."
• Set in the item "Remote password mismatch notification accumulated count."
• In addition to initialization commands used in normal modem initialization, specify "No automatic receive"
and additionally register the modem initialization command for this step to the Q series C24. (No automatic
receive: This is the setting to prohibit line connection from the opposite device.) Use the "Modem function
initialization data" screen to set.
• Constantly monitor the rise (OFF  ON) of the ERR occurrence signal (XE or XF) when connecting the line
to the opposite device using the modem function after the system begins operating.
• Monitor the following buffer memory when the ERR occurrence signal turns ON.
• Storage area for MC protocol transmission error codes (address: 602 (25AH))
• Perform the line disconnect processing with respect to the opposite device when the error code stored in the
above buffer memory is 7FE8H. (Use the modem disconnection request signal (Y12).)
• After the above line disconnect processing is completed, specify the modem initialization command for which
"No automatic receive" has been specified and perform modem initialization only. ( Page 154, Section
3.4.7)
• Describe the above occurrence to the system manager and take necessary measures.
124
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
When the number of times a remote password mismatch occurred exceeds the notification accumulated
count setting value during the remote password unlock processing in communication using MC protocol
with the Q series C24 CH1 side interface used.
Access enabled flag is turned ON
Register initialization data for "No automatic
receive" to the buffer memory
3
CH1 side ERR occurrence is detected
Read the CH1-side error code
If the error code indicates that
the accumulated count of remote password
mismatch is exceeded, the modem
disconnect request signal is set
Modem disconnection completed
When the modem disconnection completed
signal turns OFF, the No. for the modem
initialization data (for "No automatic receive")
is specified and initialization requested
The modem initialization data setting flag is
set
The modem initialization normal completion
flag is set
Error code is read if the modem initialization
completes abnormally
The modem initialization ERR occurrence
flag is set
The modem initialization request signal is
reset
The unlock processing accumulated count is
cleared
The modem initialization processing normal
completion flag is set
An instruction from the user resets the flag
125
3.3 Specifications
The modem initialization request signal is
reset
3.4
Start-up of the Modem Function
This section explains the start-up procedures, processing methods and programming when the modem function of the
Q series C24 is to be used.
3.4.1
Start-up procedures when communicating data with external
devices
This section shows the procedure for starting the modem function and up to the point when data communications is
started.
(1) Procedure up to initialization of the Q Series C24's modem / TA
This initializes the modem / TA connected to the Q Series C24 in order to use the modem function. It becomes
possible to carry out all kinds of communications when the modem / TA is initialized.
Start
⋅ Determine the configuration of the system.
⋅ Verify the Q series C24 specifications.
…
*1
Unit test of the Q series C24
…
*2
* After the unit test, turn off the power
supply to the Q series C24 loading station.
Connecting the Q series C24 and modem/TA
… After setting the modem/TA switch, connect it with
the included RS-232 cable or any designated cables.
⋅ Supplying power to the modem/TA
⋅ Supplying power to the Q series C24 loading station
… Supply power from the modem/TA side.
Setting and registration with GX Developer
⋅ Switch setting of Q series C24
Transmission setting
… (Other than operation setting (OFF)
should be set according to the modem/TA.)
⋅ Installation to the base unit
⋅ Supplying power to the Q series C24 loading station
Parameter setting
of the Q series C24
to QCPU
Communication protocol setting (set accordingly)
Station number setting (0 to 31)
See User's Manual (Basic)
Registration to QCPU (Write to PLC)
Initial setting
of Q series C24
(Setting with
GX Configuration-SC)
Initial setting of Q series C24
…
*3
Registration of the data for initialization
…
*4
Registration of connection data
…
*5
…
*6
Initialization of the modem/TA
(modem function system setting)
(2) For data communication
126
(3) For notification
(4) Access from GX Developer to QCPU
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
*1
*2
*3
*4
*5
*6
 Page 76, Section 3.2,  Page 82, Section 3.3,  User's manual (Basic)
 User's Manual (Basic)
 Page 131, Section 3.4.2,  User's Manual (Basic) for settings of the modem function.
 Page 134, Section 3.4.3,  User's Manual (Basic)
 Page 139, Section 3.4.4,  User's Manual (Basic)
 Page 144, Section 3.4.5,  User's Manual (Basic)
3
3.4 Start-up of the Modem Function
127
(2) Procedure when executing data communications
indicates processing
performed by the user.
Line connection waiting side
Line connection side
Q Series C24
Perform the processing up to the
modem/TA initialization by the
procedure in (1).
Modem
Modem
Q Series C24
or
External device
Perform the processing up to the
modem/TA initialization by the
procedure in (1).
0
1
Modem initialization
Modem initialization
2
Modem initialization
Modem initialization completed signal
(X10)=ON
Line connection wait state
Modem initialization completion
signal (X10 = ON)
Line connection *1
3
Execute line connection.
Line connection request signal (Y11)=ON
Line connection completed
Line connect signal (X12)=ON
Line connection completed
Line connect signal (X12)=ON
Execute data communications.
Execute data communications.
Remote password unlock processing
5
* If MC protocol communications are carried
out with the external device, when a remote
password is set in the QCPU, unlock the
remote password.
Data
communications *2
Line disconnection *3
The line is disconnected after
data communications are
completed.
Line disconnect request signal (Y12)=ON
Line disconnection completed
Line disconnect signal (X14)=ON
Line connect signal (X12)=OFF
Modem initialization completed signal (X10)=OFF
Line disconnection completed
Line connect signal (X12)=OFF
Remote password lock processing
Line connection wait state
Modem initialization completed
signal (X10)=ON
If data communications is to be
executed again, carry out
communications after line
connection from the external
device.
*1
*2
*3
128
3
* By completing the line disconnection,
lock processing of the remote password
is executed automatically.
If data communications are to be
executed again, start the
procedure from the modem
initialization.
* Shows the value stored for the modem function
sequence status (Address 546 (221H)).
Page 148, Section 3.4.6
Page 154, Section 3.4.7
Page 161, Section 3.4.8
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(3) If notification is made
Pager receiver
Modem
indicates processing
performed by the user.
Q Series C24 (Line connection side)
0
1
(1) Perform the processing up to
the point where the modem/TA is
initialized by the procedure in (1).
3
Modem initialization
2
3
Line connection
normally completed.
Notification data
reception.
Line connection
Modem initialization completed signal
(X10)=ON.
Make notification
Notification-issued request signal (Y14)=OFF.
Line connection normally completed
Connection in progress signal (X12)=ON
Notification *1
6
Line disconnect
Line disconnect
completed.
3
Line disconnect completed
Notification-issued request (Y14)=ON
Modem initialization completion signal
(X10)=ON
* Shows the value stored for the modem function
sequence status (address 546 (221H))
*1
Page 154, Section 3.4.7
3.4 Start-up of the Modem Function
129
(4) If accessing the QCPU from GX Developer
Q Series C24
Perform the processing up to the
point where the modem/TA is
initialized by the procedure in (1).
Modem
Modem
0
indicates processing
performed by the user.
GX Developer (Line connection side)
Initialize the personal computer
side modem.
1
Registration of the modem connected
to the personal computer
Registration complete
Modem initialization
2
Line connection wait state
Modem initialization completed
signal (X10) = ON
Execute line connection.
Line connection
3
Connect to the line after setting the
necessary items in the line connection screen.
Line connection normal response
Line connection normal response
Connection in progress signal
(X12)=ON
Password check (for the system)
Normal response
4
Remote password check *1
* When setting the remote password in
the QCPU, the remote password input
dialog box is displayed.
If the callback function is used *2
Access to the QCPU
5
Access to the QCPU.
Execute line disconnect.
Line Disconnect
Line disconnect response
Connection in progress signal
(X12)=OFF
Line connection wait state
Modem initialization completion
signal (X10)=ON
*1
*2
130
Line disconnect processing by
the line disconnect screen.
Line disconnect response.
3
* Shows the value stored for the modem function sequence status
(address 546 (221H))
Page 86, Section 3.3.3
Page 92, Section 3.3.4
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
3.4.2
Initial settings of the serial communication module
This section explains the initial settings of the Q series C24 when data communicating with external device, remotely
notifying a pager receiver and accessing from GX Developer using the modem function.
(1) Switch settings by GX Developer
3
Switch setting by GX Developer
Data
communication
Notification
GX Developer access
(For connection to
MELSOFT products)
Remarks
Communication protocol setting
1 to 7
1 to 7
5

Operation setting
OFF (Independent operation)
Data bit setting
Parity/non-parity setting
(Set according to modem/ TA on local
station)
Even/odd parity setting
Transmission
specifications
Sum check enable/disable
setting
(Set accordingto
system
specification)
Write during RUN enable
/disable setting
Setting modification enable
/disable setting
OFF
OFF = Non-parity, ON = Parity
OFF = Odd, ON = Even
OFF
OFF = 1 bit, ON = 2 bits
OFF/ON
ON
OFF = Disabled, ON = Enabled
OFF/ON
ON
OFF = Disabled, ON = Enabled
OFF/ON
OFF/ON
OFF = Disabled, ON = Enabled
(Set according to modem/TA on local station)*1
Transmission rate setting
Station number setting
*1
OFF = 7 bit, ON = 8 bits
OFF
Stop bit setting
Communication
rate
Setting data
Set both CH1 and CH2 OFF
ON
(bps)

00 to 31
When the first five digits of the serial No. are 03042 or earlier, the transmission speed cannot be set to 115200 bps for
connection between the Q series C24 and GX Developer via a modem.
This gives an example of the switch setting when the modem function is used to connect GX Developer to the Q series C24
CH1 side and the programmable controller is accessed. Perform the switch setting similar to this example also when
performing data communication or notification.
[Starting procedure]
"GX Developer"  "PLC parameter"  "I/O assignment"  Switch setting
[Setting example]
Bit
Switch No.
Switch 1
Description
Setting value
Position
Specified
value
b0
OFF
Operation setting
Independent
b1
ON
Data bit
8 bits
b2
OFF
Parity bit
No
b3
OFF
b4
OFF
CH1
transmissi
on setting
Odd/even parity
Odd
Stop bit
1 bit
b5
ON
Sum check code
Yes
b6
ON
Write during RUN
Allowed
b7
ON
Setting modification
Enable

b8 to b15
CH1 communication rate setting
07E2
19200bps
Switch 2

CH1 communication protocol setting
5
0005
Switch 5

Station number setting
0th station
0000
131
3.4 Start-up of the Modem Function
Remark
(2) Initial settings by GX Configurator-SC (set in the setting screen for modem
function system)
(a) Perform initial settings on the interface side that use the modem function as
described in Page 105, Section 3.3.6:
The following table shows the default settings in the "Modem function system setting" screen and whether
setting is possible or impossible in each type of communications.
Notification
GX Developer
(For connection
to MELSOFT
products)
Buffer memory
address
●
●
46 (2EH)

●

47 (2FH)



48 (30H)
Connection retry interval designation (unit: s)



49 (31H)
Initialization/connection timeout time designation (unit: s)



50 (32H)
Number of initialization retries designation



51 (33H)
●
●
●
52 (34H)
Data communications
(MC non procedure,
bidirectional)
Modem connection channel designation
●
Notification execution designation
Number of connection retries
"Modem function system setting" screen setting items
Data No. for initialization designation
*1
*1
●
●

53 (35H)
GX Developer connection designation


●
54 (36H)
Data No. for connection designation
*3



55 (37H)
RS/CS control yes/no designation



56 (38H)
Modem initialization time DR signal valid/invalid designation*2



8200 (2008H)
No-communication interval time designation (Unit: m)
Wait time of notification (Unit: s)



8202 (200AH)
Circuit disconnect wait time (PLC CPU watch use) (Unit: s)



8206 (200EH)
Remote password mismatch notification count designation



8204 (200CH)
Remote password mismatch notification accumulated count
designation



8205 (200DH)
8199 (2007H)
Auto modem initialization designation



Callback function designation



8193 (2001H)
Callback denial notification accumulated count designation



8194 (2002H)
Data No. for Callback designation 1 to 10



8449 to 8458
(2101H to 210AH)
●: Required item, : Setting possible, : Setting not required
*1
*2
*3
For details on how to register the data No. for initialization, see Page 134, Section 3.4.3.
For details on how to register the data No. for connection, see Page 139, Section 3.4.4.
The "Modem initialization time DR signal valid/invalid designation" designates whether the status of the DR (DSR) signal
output is valid or invalid at the startup of the Q series C24. When the DR (DSR) signal = ON is output from the modem,
register "valid" for this item. When the DR (DSR) signal = ON is not output from the modem, register "invalid" for this
item.
Even if the programmable controller CPU on the Q series C24 loading station (local station) becomes STOP status
under the following circumstances, the line (telephone) with the partner devices will be left connected.
In order to prevent the line from being left connected when the line is not in use, be sure to make the appropriate
settings.
• When the programmable controller CPU is stopped when the connected signal (X12) is at the ON status. This
occurs because the program write after remote stop is enabled.
• When the programmable controller CPU performs an error stop during self-diagnosis, etc.
When setting the No-communication interval time as infinite wait (set value = 0), be sure to perform line disconnection
processing after the data has been communicated.
If the line is left connected for long periods of time without performing line disconnection after data has been communicated,
not only will telephone bills be applied, but it may violate electronic communication business laws.
132
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(b) All transmissions using the modem function are transmitted in full-duplex.
Leave the following initial settings for the interface side that uses the modem function as default.
(Default value)
• CD terminal check: Not checked
• Communication method: full-duplex communication
(c) The processes that correspond to the following output signals may not be aborted.
Output signal
Y10
Requesting process name
3
Initialization request (standby request)
Y11
Connection request
Y12
Disconnection request
Y14
Notification-issued request
It is recommended to leave the following initial settings for the modem functions as default. (Upon error, it will
end due to time out.)
(Default value)
• Number of connection retries: 3 times
• Connection retry interval: 180s
• Initialization/connection time out: 60s
Also perform the settings for a remote password check described in Page 116, Section 3.3.6 (3) (a) and Page 116, Section
3.3.6 (3) (b) when a remote password check is executed with respect to the remote password set in the QCPU.
3.4 Start-up of the Modem Function
133
3.4.3
Register/read/delete of the initialization data
The section explains the register/read/delete of the data for initialization such as initialization commands for the
modem/TA connected to the Q series C24 side for data communication with the external device, pager receiver
notification and accessing from GX Developer using the modem functions.
(1) Registration destination of the data for initialization
• The data for initialization may be used by registering to the Q series C24 Flash ROM or buffer memory.
• The buffer memory may register the data for connection shown in Page 139, Section 3.4.4 and will register
the data for initialization or data for connection in the designated area.
• It is recommended that the data for initialization during the debug process is stored in the buffer memory.
The registration data in the buffer memory will be erased after starting up the Q series C24 loading station
again. It is necessary to register the data for initialization in the buffer memory after each start-up of the Q
series C24.
• It is recommended to store the data for initialization to the Flash ROM after completing the debug process.
By registering it to the Flash ROM, the registration process of the data for initialization will be unnecessary
thereafter.
(2) Types of data for initialization
• There are data for initialization that are registered in the Flash ROM of the Q series C24 upon shipping and
data for initialization that are set by the user.
• The number of times registered/number of possible registrations are shown in the chart below.
(3) Data for initialization registration number
• The registration numbers shown in the table below are used by the memory of the registration destination.
• The registration number of the data for initialization is determined by the area of registration.
Registration
data
Data for
initialization
data
Registration destination
Flash ROM
Buffer memory
Registration number (Decimal (hexadecimal))
Number of
registrations
Data registered by the OS
2000 to 2013 (7D0H to 7DDH)
13
Data registered by the user
2500 to 2529 (9C4H to 9E1H)
30
(All are set by the user)
-32767 to -32737 (8001H to 801FH)
31
(4) Precautions during the registration of data for initialization
• The maximum size of the initialization commands that may be registered as one data for initialization is 78
bytes.
• Do not include CR/LF (data code: 0DH/0AH) in the data for initialization to be registered to the Q series C24.
The CR/LF is output at the end of the AT command by the Q series C24 when processing initialization
(automatically added).
• The registration status of the data for initialization stored in the Flash ROM may be checked in "data
registration for modem initialization" screen for GX Configurator-SC or the buffer memory (address: 226H to
228H (550 to 552). When newly registering, register by designating an unregistered number. When
designating a registration number that has already been registered, first delete the registration data in the
preoccupied registration number prior to registration.
• When connecting the Q series C24 to an external device using a cellular phone and a modem, set the
transmission rate supported by the cellular communication module on the modem side.
134
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(5) Registration contents at shipment
• The data for initialization registered in the Flash ROM of the Q series C24 are listed below:
Registration number
Hexadecimal
Initialization command
Decimal
7D0H
2000
ATQ0V1E1X1\J0\Q2\V2\N3S0=1
7D1H
2001
ATQ0V1E1X1\Q2\V2\N3S0=1
7D2H
2002
ATQ0V1E1X1&K3\N3S0=1
7D3H
2003
ATQ0V1E1X1&H1&R2&A3&D2S0=1
7D4H
2004
ATQ0V1E1X1\J0\Q2\N3S0=1
7D5H
2005
ATE1Q0V1&C1&D2&H1&I0&R2&S0S0=1
7D6H
2006
ATE1Q0V1&C1&D2&K3&S0S0=1
7D7H
2007
ATE1Q0V1&C1&D2&K3&S1S0=1
7D8H
2008
ATE1Q0V1&C1&D2&K3&S0S0=1
7D9H
2009
ATE1Q0V1&C1&D1\Q2&S0S0=1
7DAH
2010
ATE1Q0V1&C1&D2\Q3&S0S0=1
7DCH
2012
AT&S0S0=1
7DDH
2013
ATX1&S0S0=1
3
• If initialization commands other than listed above are needed, the data for initialization needs to be
registered to the Flash ROM or the buffer memory of the Q series C24.
Remark
● Perform the following setting in respect to the modem/TA connected to the Q series C24 side.
For settings other than listed below, perform the setting as designated by the modem/TA.
Setting contents
Setting command example
AT
Display the result code (or, return the result code).
Qn
Set the result code as a word.
Vn
Perform character echo.
En
Dial tone and busy tone detection + X1
Set register 0 at 2
The modem and the serial speed are not equal.
3.4 Start-up of the Modem Function

Xn
Sr=n
\Jn
Control RTS/CTS.
\Qn
Control DSR.
&Sn
Control DTR.
&Dn
Enable extension result code (display MNP class).
\Vn
MNP mode/normal mode auto selection
\N3
● The following shows an specification example of the transmission rate supported by the cellular communication module
using the modem initialization command, when connecting the Q series C24 to an external device using a cellular phone
and a modem. (Transmission rate = 9600bps is set)
For the details, see the manual of the modem used.
(Setting example for the initialization command of the registration No.7D3H)
ATQ0V1E1X1&H1&R2&A3&D0S0=1&N6
(Setting example for the initialization command of the registration No.7D4H)
ATQ0V1E1X1\J0\Q2\N3&D0+MS=, 9600, 9600S0=1
135
(6) Procedures for register/read/delete of the initialization data
(a) For the flash ROM in the Q series C24
Register/read/delete operations are executed on the GX Configurator-SC's "Data registration for modem
initialization" screen.*1
*1
The factory setting of initialization data stored in the Flash ROM of the Q series C24 cannot be deleted.
(Registration example)
Remark
Use \\ code to specify a field to register "\" if GX Configurator-SC is used for data for modem initialization.
To register the \Q2 of data: \\Q2
136
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(b) For the buffer memory of the Q series C24
• The initialization data write (registration) and read operations are performed by designating an applicable
area that corresponds to registration numbers 8001H to 801FH for the user frame registration area
(addresses: 1B00H to 1FF6H). When deleting the initialization data, write "0" to the number of registration
data bytes designation area.
• The table below shows an overview of the buffer memory used in the write, read, and delete operations of
the initialization data as well as the designated values for each area. For more details, see Page 220,
3
CHAPTER 9. (Use the table by replacing the user frame with the initialization data.)
Address
Hexadecimal
1B00H
Name
Designated/stored value
Decimal
6912
1B01H
6913
1B02H
6914


1B28H
6952
1B29H
6953
6954
1B2BH
6955


1B51H
6993
1FCEH
8142
1FCFH
8143
1FD0H
8144


1FF6H
8182
Registration
number
8002H
Registration
number
801FH
User controlled data
Any data used by the user to manage the registration
data (manufacturer code, control number, etc.)
Initialization
command
Data code for the initialization command for registration
Registration data byte
number designation
0: When deleting
1 to 78: Number of bytes in the registration data
(Only for the initialization command section)
User controlled data
Any data used by the user to manage the registration
data (manufacturer code, control number, etc.)
Initialization
command
Data code for the initialization command for registration
Registration data byte
number designation
0: When deleting
1 to 78: Number of bytes in the registration data
(Only for the initialization command section)
User controlled data
Any data used by the user to manage the registration
data (manufacturer code, control number, etc.)
Initialization
command
Data code for the initialization command for registration
Write
Read


(Read
processing
not
required)
Delete





(Read
processing
not
required)




(Read
processing
not
required)

• The contents of the data to be written into the designated area that corresponds to registration numbers
8001H to 801FH are the same as those for the Flash ROM.
137
3.4 Start-up of the Modem Function
1B2AH
Registration
number
8001H
Registration data byte
number designation
0: When deleting
1 to 78: Number of bytes in the registration data
(Only for the initialization command section)
Specification required
()/not required ()
• The following shows an example of a sequence program used to write the initialization data (registration).
• Example of writing the initialization data to the area having registration number 8001H
X1E: Q series C24 ready signal
X1F: WDT error signal
Turns the ready flag ON
Data registration for initialization
instruction
Sets the number of registration
data bytes
Sets the user control data
(control number)
Sets the AT command for initialization
Sets the AT command for initialization
to the buffer memory
Sets the initialization completed flag
Data register
(Item name)
(Address)
Buffer memory
Area for registration
No. 8001H
Number of registration data bytes
D0
30
1B00H
30
User control data
D1
1
1B01H
1
D2
Initialization command
to
D13
command
to
1B0DH
to
1B28H
138
Data for
1B02H
Initialization
Initialization
command
initialization
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
3.4.4
Register/read/delete of the data for connection
This section explains the registration/reading/deletion of data for connection such as the telephone number of the
partner device and notification messages that are used for communicating data with external devices, notify pager
receivers and accessing from GX Developer using the modem functions.
3
(1) Registration destination of data for connection
• The data for connection can be used by registering to the Q series C24's Flash ROM or buffer memory.
• The buffer memory can register the data for initialization shown in Page 134, Section 3.4.3. The data for
initialization or data for connection will be registered in the applicable area.
• It is recommended to store the data for connection during the debug process in the buffer memory. The
registration data in the buffer memory will be erased after the starting up the Q series C24 loading station
again. It is necessary to register the data for connection in the buffer memory after each start-up of the Q
series C24.
• It is recommended to store the data for connection to the Flash ROM after completing the debug process. By
registering it to the Flash ROM, the registration process of the data for connection will be unnecessary
thereafter.
(2) Types of data for connection
• All data for connection are registered and used as defined by the user.
• The number of possible registrations are shown in the table below.
(3) Data for connection registration number
• The registration numbers shown in the table below are used by the memory of the registration destination.
Registration
data
Data for
connection
Registration destination
Flash ROM
Buffer memory
(All are set by user)
Registration number (Decimal (hexadecimal))
Number of
registrations
3000 to 3029 (BB8H to BD5H)
30
-32767 to -32737 (8001H to 801FH)
31
(4) Precautions during the registration of data for connection
• The maximum size of data that can be registered as one data for connection is 80 bytes. Do not deviate from
the following data sizes for the following items:
• Message area for notification = 36 bytes, data-for-connection area = 44 bytes
• Designate the messages for notification accordingly with the display designation of the partner devices.
• The registration status of the data for initialization stored in the Flash ROM can be checked in "data
registration for modem connection" screen for GX Configurator-SC or the buffer memory (address: 223H to
225H (547 to 549) When newly registering, register by designating an unregistered number. When
designating a registration number that has already been registered, first delete the registration data in the
preoccupied registration number prior to registration.
139
3.4 Start-up of the Modem Function
• The registration number of the data-for-connection is determined by the area of registration.
(5) Procedures for register/read/delete of the data for connection
(a) For the flash ROM in the Q series C24
Register/read/delete operations are executed on the GX Configurator-SC's "Data for modem connection"
screen.
Set the required items with the table below.
"Data for modem connection" screen setting item
Pager receiver designation
Data for modem
connection 1 to
30
Data communications
(MC non procedure,
bidirectional)
Notification
GX Developer (For
connection to MELSOFT
products)

●

Telephone number
●
●
● (for callback)
External line dialing


 (for callback)
Line types


 (for callback)
Wait time for message transmission unit: s



Message



Comment



●: Required item, : Setting possible, : Setting not required
(Registration example) Setting example to perform data communication
140
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(b) For the buffer memory of the Q series C24
• The connection data write (registration) and read operations are performed by designating an applicable
area that corresponds to registration numbers 8001H to 801FH for the user frame registration area
(addresses: 1B00H to 1FF6H). When deleting the connection data, write "0" to the number of registration
data bytes designation area.
• The table below shows an overview of the buffer memory used in the write, read, and delete operations of
the connection data as well as the designated values for each area are. For more details, see Page 220,
CHAPTER 9. (Use the table by replacing the user frame with the connection data.)
Address
Hexadecimal
1B00H
Name
Specification required
()/not required ()
Designated/stored value
Decimal
6912
1B01H
6913


1B28H
6952
1B29H
6953
1B2AH
6954


1B51H
6993
1FCEH
8142
1FCFH
8143


1FF6H
8182
Registration
number
8001H
Registration
number
8002H
Registration
number
801FH
Registration data byte
number designation
0: When deleting
80: Number of registration data bytes
Connection data
Notification message for connection data to be
registered, and connection data
Registration data byte
number designation
0: When deleting
80: Number of registration data bytes
Connection data
Notification message for connection data to be
registered, and connection data
Registration data byte
number designation
0: When deleting
80: Number of registration data bytes
Connection data
Notification message for connection data to be
registered, and connection data
Write
Read
Delete



(Read
processing
not
required)



(Read
processing
not
required)

(Read
processing
not
required)





numbers 8001H to 801FH) in the buffer memory that is used for the register, read and delete operations of
the connection data, as well as the designated values and stored values.
Data for connection
(H)
(L)
Connection data area (44 bytes)
Pager receiver designation (2)
Telephone number (18)
External line dialing (2)
Line types (2)
(Open) (20)
Wait time for Message transmission (2)
Message (30)
Message length (2)
(Open) (2)
(Data name (number of bytes))
141
3.4 Start-up of the Modem Function
• The following shows the data arrangement of the connection area data (area corresponding to registration
Message area for notification (36 bytes)
3
(Data for connection area): 44 bytes
Designated/stored value and contents
Number of
bytes
Data type
Whether or not notification is performed, and the notification target module are designated.
0: No notification
3: Notification performed
• In the case of 3 above, the wait time for message transmission in the notification message
must be designated.
2
Binary
• The other party's phone number used to establish line connection when communicating
data or performing notification is designated.
• When phone number is less than 18 characters, a space (code: 20H) must be entered for
the remainder.
18
ASCII
Data name
Pager receiver
designation
Telephone number
External line dialing
number
The external-line access number on Q series C24 side when performing data
communication/notification to the partner device is designated.
0 to 9, 10 (*), 11 (#): External-line access number on the Q series C24 side
255: No external-line access number required on the Q series C24 side
2
Binary
Line types
The line type used to perform data communication/notification with the partner device is
designated.
0: Pulse
1: Tone
2: ISDN
2
Binary
(Open)
Designate "0".
20
Binary
Number of
bytes
Data type
(Notifying message area): 36 bytes (Designated when performing notification)
Data name
Designated/stored value and contents
Wait time for message
transmission
The wait time after line connection until message transmission is designated.
(Unit: s)
0 to 255: Wait time
• Valid when the pager receiver designation in data connection is "3".
2
Binary
Message
Designate the notification message according to the display specification on the other party's
device.
30
Binary
Message length
The number of designated message bytes shown above is designated.
0: No message designation
1 to 30: Number of message bytes
2
Binary
(Open)
Designate "0".
2
Binary
142
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
• An example of a sequence program used for writing (registering) of data for connection is shown below.
• Example of writing data for connection to the registration number 8002H area
X1E: ready signal
X1F: WDT error signal
Turns the ready flag ON
Connection data registration
command
Set the number of registration
data bytes
3
Clear the data storage device
for connection
Set the pager receiver designation
(Notification is not executed)
Set the telephone number
to be connected
Set the external line dialing
number (0)
Sets the line type to tone
Writes the connection data
in the buffer memory
Sets the connection data
registration completion flag
(Item name)
Data register
(Address)
Buffer memory
Area for registration
No. 8002H
Number of registration
data bytes
D0
to
(Connection data)
1B3FH
D23
D40
80
1B2AH
(Connection data)
D22
to
1B29H
3.4 Start-up of the Modem Function
D1
to
Data for connection
80
1B40H
(Data for notification)
to
(Data for notification)
1B51H
143
3.4.5
Initialization of modem/TA (terminal adapter)
This section explains the initialization of the modem/TA connected to the Q series C24, used for communicating data
with the external device, performing notifications to pager receivers and accessing from GX Developer using the
modem function.
(1) Requirements for initialization
Perform the following setting and registration:
• The initial settings for the Q series C24 as shown in Page 134, Section 3.4.3
• The data for initialization registration shown in Page 134, Section 3.4.3, when initializing the modem/TA with
the data for initialization set by the user.
Remark
It is possible to initialize and connect at the same time by performing the connection process by designating the data for
initialization and data for connection. ( Page 148, Section 3.4.6)
(2) Registering initialization data using GX Configurator-SC (Settings on the
modem function system setting screen)
The number of the initialization data used to initialize the modem connected to the Q series C24 is registered on
the GX Configurator-SC's "Modem function system setting" screen.
The following explains the number designated by the "Initialization data number" item on the GX ConfiguratorSC's "modem function system setting" screen and the related buffer memory when the initialization data number
= 0 is designated.
Buffer memory used
The number of data for initialization used and buffer memory designated value
Address (CH1/CH2)
Name
Hexadecimal
Decimal
When number used = 1
When number used = 2 or more
7D0H to 801FH:
Data number for initialization
designation
34H
52
User frame being transmitted
number
B6H/156H
182/338
CR/LF output designation
B7H/157H
183/339
0 (default value)
Output head pointer
designation
B8H/158H
184/340
1 to 100 (See 1))
Output count designation
B9H/159H
185/341
Transmission
frame
number
designation
First
BAH/15AH
186/342
Second
BBH/15BH
187/343



Hundredth
11DH/1BDH
285/445
*1
0H
Data for initialization registration number*1
(During initialization, the data registration
number currently being sent is stored.)
(Unused)
1 to 100 (See 2))
7D0H to 801FH:
Data for initialization registration number*1
The data for initialization registration number to be used is designated.
7D0H to 7DDH (2000 to 2013): Data registered by the OS
9C4H to 9E1H (2500 to 2529): Data registered in the Flash ROM by the user
8001H to 801FH (-32767 to -32737): Data registered to the buffer memory by the user
1) Output head pointer designation area (address: 184/344 (B8H/158H)): Designate the location of the head
position (n-th unit) in the transmission frame number designation area to which the registration number of the
data for initialization to be sent is written.
• 1: Transmitted form the first unit to 100: Transmitted from the 100th unit
144
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
2) Output count designation area (address: 185/345 (B9H/159H)): The number of data for initialization units to be
transmitted starting from the location set by the output head pointer designation area is designated here.
• 1: Transmitted form the first unit to 100: Transmitted from the 100th unit
(3) Precautions during modem/TA initialization
If the DSR signal from the modem/ TA goes OFF when modem/TA initialization is completed (X10 goes ON), the
Q Series C24 executes initialization processing automatically in accordance with the following.
3
• If the auto modem initialization is specified
Modem / TA initialization processing is executed in the initialization / connection timeout time interval while the
DSR signal is OFF without relation to the ON/OFF status of the modem initialization request signal Y10.
• If the auto modem initialization is not specified
The modem / TA initialization processing is executed when the DSR signal restarts without relation to the
ON/OFF status of the modem initialization request signal Y10.
(4) If modem / TA initialization is executed automatically (Set by the GX
Configurator-SC)
By having the GX Configurator-SC perform the settings for automatic modem initialization, modem initialization is
executed automatically when the Q Series C24 starts up.
The modem initialization completion signal (X10) goes ON.
(a) Settings for auto initialization of the modem / TA
Select "auto initialize" for the auto modem initialization designation in the GX Configurator-SC's "Modem
function system setting" screen.
(b) Cautions when initializing the modem / TA automatically
processing.
• The initialization / connection abnormal completion signal (X13) does not go ON.
• An error code is stored in the buffer memory's modem function error code storage area (Address: 545
(221H)).
• Modem initialization is retried automatically using the initialization / connection timeout time stored in the
buffer memory (address: 50 (32H), and is repeated until initialization is completed normally.*1
*1
When modem initialization is not completed normally, the user should perform the following, and restart the station
where the Q Series C24 is installed.
Check the set initialization data No.
Check the registered contents of the initialization data corresponding to the set initialization data No. (If they are
abnormal, correct them and register them again.)
Check if the modem's power is turned on.
• When the line is disconnected from the Q Series C24 side (using Y12), the initialization completion signal
(X10) goes off together with the connection in progress signal (X12). When connecting to the line again, do
so after first initializing the modem.
When the line to the Q Series C24 is disconnected from the external device side, the Q Series C24's initialization completion
signal (X10) does not go OFF.
When desiring to disable reception by the Q Series C24 side's modem, execute line disconnect by the modem disconnection
request signal (Y12).
145
3.4 Start-up of the Modem Function
• If the modem's initialization processing is completed abnormally, the Q Series C24 executes the following
(5) If the modem/TA is initialized by a sequence program
(a) I/O signals used in initialization
The initialization request signal (Y10), initialization complete signal (X10) and initialization/connection abnormal
complete signal (X13) are used.
When initializing the modem connected to CH1 of the Q series C24 using two set of data for initialization
(registration numbers 8001H and 8002H) that are registered in the buffer memory
Address
B6H
Buffer memory
Frame number being
transmitted
(Designated value)
0
0
B8H
CR/LF output designation
Output head pointer
designation
B9H
Number of outputs
2
B7H
3
BAH
1st unit
BBH
2nd unit
9C5H
BCH
3rd unit
8001H
BDH
Transmission
frame
number
9C4H
4th unit
8002H
BEH
5th unit
9D0H
BFH
6th unit
9D1H
…… Out of the transmission frame numbers, from which one
the transmission will be initiated is designated.
…… Out of the transmission frame numbers, the number of units to be transmitted
is designated.
…… Data for initialization registration number is designated.
* The Q series C24 will transmit the data for initialization in the designated order.
Must be designated prior to the
modem initialization request.
Initialization request
Y10
Initialization completion
X10
Initialization/connection
abnormal completion
X13
(Normal completion)
(Abnormal completion)
After the designated number of initialization retries
have been executed
Initialization data
Registration No.8002
Initialization data
Registration No.8001
Q series C24
Modem
146
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(b) Modem/TA initialization program example
An example of the modem/TA initialization program on the Q series C24 side by the programmable controller
CPU is shown below.*1
*1
When the initialization data has been registered from GX Configurator-SC or from the programmable controller CPU.
X12: Connection in progress signal
X1E: Ready signal
X1F: WDT error signal
M0: Accessible flag
M1: Data registration complete flag
for initialization
M30: Initialization enabled flag
3
Turns the ready flag ON
Turns the modem initialization enabled
flag ON
Modem initialization command
Sets the initialization request signal
Sets the initialization request flag
Sets the initialization completed flag
Reads the error code at initialization
abnormal completion
Resets the flag with the clear command
3.4 Start-up of the Modem Function
147
3.4.6
Line connection
This section explains the connection (dialing) with the partner devices for the purpose of data communication with
external devices using the modem functions.
In case of notification to a pager receiver, the line is connected while the notification is being processed. The
connection processing such as a connection request (Y11) to I/O signal is, therefore, unnecessary.*1
*1
The data for connection indicated in this section should be set to perform the notification processing
(1) Requirements for connection
Complete the following settings and registrations in advance.
• The initial settings for the Q series C24 as shown in Page 131, Section 3.4.2
• The registration of the data for initialization as shown in Page 134, Section 3.4.3
• The registration of the data for connection as shown in Page 139, Section 3.4.4
• The initialization of the modem/TA connected to the Q series C24 side as shown in Page 144, Section 3.4.5
• In addition, both the initialization and line connection can be conducted simultaneously by designating the
data for initialization and data for connection to perform connection processing. For the data setting for
initialization to perform initialization and line connection simultaneously, see Page 131, Section 3.4.2,
Page 144, Section 3.4.5. Explanation on the above-mentioned setting is omitted in this section.
(2) Registering the data for connection using GX Configurator-SC (Settings on the
modem function system setting screen)
The number of the data for connection that is used for line connection in order to perform data communication
with the external device is registered on the GX Configurator-SC's "Modem function system setting" screen.
The following explains the number designated by the "Connection data number" item on the GX ConfiguratorSC's "Modem function system setting" screen.
• When line connecting from the Q series C24 side*1
• Data number for connection designation area (address: 35H (53))
The data for connection registration number is designated.
BB8H to BD5H (3000 to 3029): Data registered to the Flash ROM by the user
8001H to 801FH (-32767 to -32737): Data registered to the buffer memory by the user
*1
The addresses shown in parentheses below indicate the addresses of the buffer memory where the setting values for
this item on the "Modem function system setting" screen are stored.
• When line connecting from the external device
Since the line connection processing is not necessary on the Q series C24 side, connecting data registration for
line connection and data number setting for connection are not needed.
148
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(3) I/O signals used in line connection
Connection request signal (Y11), dial in progress signal (X11), connection in progress signal (X12) and
initialization/connection abnormal completion signal (X13) are used.
When performing the line connection from the Q series C24 side only following the completion of
initialization
Buffer memory for
connection
Address: 35H (53)
3
0
3000
Normal completion
Connection
request
Y11
Initialization
completion
Y10
Dial in progress
X11
Connection in
progress
X12
(ON)
RS-232 CD terminal
Result code
receive *
* Set "Display a result code using
the AT command" in the local station
side modem.
3.4 Start-up of the Modem Function
Dial
Abnormal completion
Connection
request
Y11
Initialization
completion
Y10
Dial in progress
X11
Connection in
progress
X12
(ON)
(OFF)
Initialization/
X13
connection
abnormal completion
RS-232 CD terminal
(OFF)
Dial
Dial
Dial
Dial
(Dialing)
Retry (In case of three times)
* Connection channel and retry operation are performed using the buffer memory setting.
149
When performing the initialization and the line connection from the Q series C24 side simultaneously
Buffer memory for
initialization
*1
Buffer memory for
connection
Address: 35H (53)
0
3000
Normal completion
Connection
request
Y11
Initialization
completion
X10
Dial in progress
X11
Connection in
progress
X12
RS-232 CD terminal
* Set "Display a result code
using the AT command" in
the local station side modem.
Y11
Initialization
completion
X10
Dial in progress
X11
Connection in
progress
X12
Dial
Result code
receive *
*1
Abnormal completion
Connection
request
Modem
initialization
(OFF)
Initialization/
X13
connection
abnormal completion
RS-232 CD terminal
(OFF)
Modem
initialization
Dialing
*1
Dial
Dial
Dial
Dial
Retry (In case of three times)
* Connection channel and retry operation are performed using the buffer memory setting.
*1
150
Page 144, Section 3.4.5
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
When initiating the line connection from the partner device after the completion of initialization
Buffer memory for
connection
Address: 35H (53)
0
Connection
request
Y11
Initialization
completion
X10
Dial in progress
X11
3
(OFF)
(ON)
(OFF)
(Normal connection)
Connection in
progress
X12
(Normal connection)
RS-232 CD terminal
Reception
* Set "Display a result code
using the AT command" in
the local station side modem.
Unlock processing for
the remote password
Result code
receive *
Password
(for system)
Response
Communication only
when connected with
GX Developer
Remote
password
Response
Communication using MC protocol
When connecting to the GX Developer
● Abnormal processing when the partner device initiate the line connection is left entirely to the partner device. There is no
method on the Q series C24 side to check a line connection error occurrence at the partner device.
● When a remote password check is performed for the QCPU, normal completion of the unlock processing allows access
to data communication/ programmable controller thereafter.
(4) Precautions during the line connection
• Prior to data communication with external devices, determine when and which station will perform the line
connection (dialing) and line disconnection processing to the external device.
• Use the following method to perform the unlock processing for the QCPU remote password from the
opposite device.
• During communication using MC protocol, transmit the dedicated command to the Q series C24 side.
• When accessing the programmable controller using the GX Developer, perform the unlock processing on
the GX Developer screen when access begins. See Page 121, Section 3.3.7 (8) for what to do when the
unlock processing is completed abnormally.
• When reconnecting the line after disconnection, allow several seconds for the modem before turning on the
Connection request (Y11). If it (Y11) is turned on immediately after line disconnection, the modem may not
accept the first connection request, resulting in connection failure, and the user may be forced to wait for the
retry time to elapse.
151
3.4 Start-up of the Modem Function
● The connection channel on the Q series C24 side is set in the "modem function system setting" screen of GX
Configurator-SC.
(5) Line connection program example
An example of a line connection program is shown below.
(a) Example of initiating line connection from the Q series C24 side following the
initialization completion
When the data for connection has been registered from GX Configurator-SC or from the programmable
controller CPU.
X10: Initialization complete signal
X1E: Ready signal
X1F: WDT error signal
M0: Accessible flag
M2: Data registration complete flag
for connection*1
M3: Initialization complete flag
M40: Connectable flag
Turns the ready flag ON
Turns the line connectable
flag ON
• Data for initialization registration
• Data for connection registration
• Modem/TA initialization
*2
Line connection command
Sets connection request signals
When the connection in progress
signal ON (normal completion),
sets the connection complete flag
Reads the error code at connection
abnormal completion
Resets the flag with the clear
command
*1
*2
152
Page 139, Section 3.4.4
 Page 134, Section 3.4.3,  Page 139, Section 3.4.4,  Page 144, Section 3.4.5
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(b) Example of simultaneous execution of initialization and line connection from the Q
series C24 side
When the initialization and connection data have been registered from GX Configurator-SC or from the
programmable controller CPU
X10: Initialization complete signal
X1E: Ready signal
X1F: WDT error signal
M0: Accessible flag
M1: Data registration complete flag
for initialization
M2: Data registration complete flag
for connection*1
M3: Initialization complete flag
M40: Connectable flag
3
Turns the ready flag ON
Turns the line connectable
flag ON
• Data for initialization registration
• Data for connection registration
*2
Line connection command
Sets connection request signals
When the connection in progress
signal ON (normal completion),
sets the connection complete flag
Resets the flag with the clear
command
*1
*2
Page 139, Section 3.4.4
Page 134, Section 3.4.3, Page 139, Section 3.4.4
Remark
When the line connection is initiated from the partner device, neither registration, setting nor connection processing is
necessary.
As shown in example of Page 149, Section 3.4.6 (3), data communication is possible if the connection in progress signal
(X12) turns ON after the completion of Q series C24 modem/TA initialization.
For an example of the modem/TA program for initialization, see Page 144, Section 3.4.5.
153
3.4 Start-up of the Modem Function
Reads the error code at
connection abnormal completion
3.4.7
Data communication and notification
This section explains the cautions for data communication with the partner device using modem function and
procedures for notification to pager receivers.
(1) Requirements for data communication and notification
(a) When communicating data with external devices
Perform the appropriate processing up to line connection or modem/TA initialization, depending on whether or
not the line connection is initiated from the Q series C24 side.
After line connection, data communication can be performed using an MC protocol/non procedure
protocol/bidirectional protocol in full-duplex communication.
• When line connecting from the Q series C24 side
Processing up to line connection as shown in Page 148, Section 3.4.6.
• When line connecting from the external device
Processing up to the initialization of the modem/TA as shown in Page 144, Section 3.4.5.
(b) When notifying to pager receivers
Perform processing up to the initialization of the modem/TA as shown in Page 144, Section 3.4.5.*1
*1
In notification to pager receiver, since the line connection is performed during notification processing, line connection
processing is unnecessary. However, be sure to register data for connection.
(2) Buffer memory used and I/O signals
(a) When communicating data with the external device
Only buffer memory and I/O signals the user uses for data communication (MC protocol/non procedure
protocol/bidirectional protocol). Communicate data using the connection in progress signal (X12)ON as the
interlock signal.
X12
Program for data communication
There is no I/O signal or buffer memory for modem functions used in data communication.
Initialization
request
Y10
Initialization
completion
X10
Connection
request
Y11
Connection in
progress
X12
(ON)
(ON)
(ON)
RS-232 CD terminal
* Set "Display a result code
using the AT command" in
the local station side modem.
154
Initialization
Dial
Result code
receive *
Data communication is possible
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
Remark
This section explains the general procedure for non procedure protocol/bidirectional protocol (executed in full-duplex
communication) data communication using the modem function between the programmable controller CPU with Q series
C24 installed.
Station A
MODE
RUN
CH1.
3
Station B
QJ71C24-R2
Q25HCPU
QJ71C24-R2
Q25HCPU
MODE
RUN
CH2.
ERR.
ERR.
USER
BAT.
USER
BAT.
CH1.
CH2.
BOOT
BOOT
Public line
Modem
CH1.
RS-232
cable
USB
CH1.
Modem
CH2.
RS-232
cable
RS-232
USB
CH2.
RS-232
(General Procedure)
1) Perform initial setting for Q series C24 at both station A and station B.
2) Perform modem/TA initialization in station B.
3) Perform modem/TA initialization and line connection in station A.
4) Communicate data using the non procedure protocol/bidirectional protocol.
5) In order to end the communication, disconnect line from station A that initiated the line connection.
3.4 Start-up of the Modem Function
155
Station A
(connection request side)
Connection
request
Y11
Initialization
completion
X10
Connection in
progress
X12
Disconnection
request
Y12
Disconnection
completion
X14
Connection
Communication
Disconnection
RS-232 CD terminal
Station B
(connection reception side)
Initialization
completion
X10
Connection in
progress
X12
Disconnection
request
Y12
(OFF)
Disconnection
completion
X14
(OFF)
(ON)
RS-232 CD terminal
* It is possible to disconnect line from Station B, as well.
156
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(b) When notifying to pager receiver
• Initial setting by GX Configurator-SC
Register the data number registration area for connection below in the "Modem function system setting"
screen.
BB8H to BD5H (3000 to 3029): Data registered to the Flash ROM by the user
8001H to 801FH (-32767 to -32737): Data registered to the buffer memory by the user
• I/O signal
Use notification-issued request signal (Y14), notification normal complete signal (X15), notification abnormal
3
complete signal (X16).
When normal completion
Buffer memory for Q series C24 initial setting
Notification execution
0
designation area
(Address: 2FH (47))
……
1
Buffer memory for notification
Data number for
connection designation area
(Address: 35H (53))
0
3000
Modem function error code
storage area
(Address: 221H (545))
0
Notification execution data
storage area
(Address: 22AH (554))
0
3000
……
3.4 Start-up of the Modem Function
Initialization
completion
X10
Connection in
progress
X12
(ON)
Notification
X15
normal completion
X16
Notification
abnormal completion
Notificationissued request
(OFF)
Y14
RS-232 CD terminal
(OFF)
Dial
Notification
Disconnection
157
When abnormal completion
Buffer memory for Q series C24 initial setting
Notification execution
designation area
0
(Address: 2FH (47))
……
1
Buffer memory for notification
Data number designation
area for connection
(Address: 35H (53))
0
3000
Modem function error code
storage area
(Address: 221H (545))
0
(Error code)
Notification execution data
storage area
(Address: 22AH (554))
……
0
Initialization
completion
X10
(ON)
Connection in
progress
X12
(OFF)
Notification
X15
normal completion
(OFF)
X16
Notification
abnormal completion
Notificationissued request
Y14
RS-232 CD terminal
(OFF)
Dial
Dial
Dial
Dial
(Dialing)
Retry (In the case of three times)
* Retry processing is conducted according to the values for the connection retry number
to initialization/connection timeout registered in the initial setting for GX Configurator-SC.
158
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(3) Precautions for performing data communication and notification
(a) When communicating data with the external device
• When setting the no-communication interval time to infinite wait (set value=0) in the initial setting of Q series
C24, be sure to perform line disconnection after the completion of data communication.
• Only the no procedure protocol/bidirectional protocol data communication can be performed in the
programmable controller CPU with Q series C24 installed.
• The Q series C24 automatically performs line disconnection processing if no data exchange is performed
3
during the no-communication interval time. The connection in progress signal (X12) and the modem
initialization completion signal (X10) turn off and the modem disconnection completion signal (X14) turns on
when the line disconnection processing is performed.
(b) When notifying to pager receivers
• Turn on the notification-issued request signal (Y14) before the Q series C24 modem/TA initialization is
completed.
• Notification processing is conducted when the notification-issued request signal (Y14) turns from ON to OFF
after the completion of modem/TA initialization. Therefore, notification processing is conducted when the
programmable controller CPU of the station with Q series C24 installed is in stop status, or the
programmable controller CPU stops due to error, since the notification-issued request signal (Y14) is turned
off in either case. Write the data number for connection in the initial setting for GX Configurator-SC.
• When the notification-issued request signal (Y14) is turned OFF from ON before initialization of the Q series
C24 modem/TA, the processing will end abnormally.
• When the notification-issued request signal (Y14) is turned OFF from ON during initialization of the Q series
C24 modem/TA, notification processing will be conducted after the completion of the modem/TA initialization.
• Notification processing is completed in the order of line connection, message transmission, and line
Therefore, even if the power to the notification destination equipment is off, the notification processing will
end normally as long as the above processing is completed.
• When the notification-issued request signal (Y14=ON) is turned ON before notification processing is
complete, some messages may not be sent.
Turn on the notification-issued request signal (Y14) before the initialization processing of the Q series C24 modem/TA is
completed, and turn it off after the initialization complete signal (X10) is turned ON (notification request).
159
3.4 Start-up of the Modem Function
disconnection from Q series C24 for the transmission station of the radio wave to the notification destination.
(4) Program for notification example
An example of program for notification is shown below.*1
*1
When the initialization and connection data have been registered from GX Configurator-SC or from the programmable
controller CPU
X10: Initialization complete signal
X1E: Ready signal
X1F: WDT error signal
M0: Accessible flag
M2: Data registration complete flag for
connection*2
M3: Initialization complete flag
M40: Notification enable flag
Turns the ready flag ON
Turns the notification enable
flag ON
• Data for initialization registration
• Data for connection registration
*3
Sets the notification-issued
request signal
• Modem/TA initialization
*4
Notification command
Resets the notification-issued
request signal (notification-issued)
Sets the notification-issued
request flag
Sets the flag at notification
normal completion
Reads the error code at
notification completion
Resets the flag with the clear
command
*2
*3
*4
160
Page 139, Section 3.4.4
Page 134, Section 3.4.3, Page 139, Section 3.4.4
Page 144, Section 3.4.5
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
3.4.8
Line disconnection
This section explains the line disconnection upon communication completion when communicating data with the
external device using the modem functions.
In case of notification to pager receivers, since the line will be disconnected at the end of the notification processing,
the disconnection processing such as I/O signal disconnection request (Y12) is unnecessary.
3
(1) I/O signal used
Uses modem disconnection request signal (Y12) and modem disconnection completion signal (X14).
Host station
Communication
Initialization
completion
X10
Connection in
progress
X12
Disconnection
Modem
Y12
disconnection request
Modem disconnection
completion
X14
RS-232 CD terminal
External station
(Q series C24)
X10
Connection in
progress
X12
(ON)
Modem
Y12
disconnection request
(OFF)
Modem disconnection
completion
X14
(OFF)
3.4 Start-up of the Modem Function
Initialization
completion
RS-232 CD terminal
This is the procedure to take in order to turn off the initialization complete signal (X10).
* In the case of Q series C24, when the line is disconnected from the external device,
the initialization complete signal (X10) at the local station is not turned OFF.
161
● Line disconnection processing can be conducted from either device as long as the connection is in progress.
● The line disconnection processing disconnects the line connection with the external device as well as the connection with
the Q series C24 modem.
● Even when an error occurs during the line disconnection, the disconnection processing will be forced.
● If data communication is to be resumed after line disconnection, either one of the following processing will be initiated
depending on the initialization complete signal (X10).
• If the initialization complete signal is OFF: Start from the initialization of the modem/TA.
• If the initialization complete signal is ON: Start from the line connection with the external device.
Remark
There is no buffer memory for line disconnection processing.
(2) Precautions during the line disconnection
• Prior to data communication with external devices, determine when and which station will perform the line
connection (dialing) and line disconnection processing to the external device.
• If the line is disconnected during data transmission, transmission processing will be performed depending on
the signal status of the Q series C24 RS-232 interface.
• If the line is disconnected during data reception, data reception will be disabled. This may cause an error
occurrence such as a reception time out.
• If the data communication is not performed during the designated noncommunication interval time, the Q
series C24 automatically disconnects line. When the line is disconnected, the connection in progress signal
(X12) and the modem initialization completion signal (X10) turn off and the modem disconnection completion
signal (X14) turns on. To turn off the modem disconnection completion signal (X14), turn on the modem
disconnection request signal (Y12) and keep it for a second after the modem disconnection completion
signal (X14) turns on.
162
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(3) Program example for line disconnection
A program example for line disconnection is shown below.
X0: Normal transmission completion signal
X1: Abnormal transmission completion signal
X3: Reception data read request signal
X4: Abnormal reception detection signal
X10: Initialization complete signal
X12: Connection signal
X1E: Ready signal
X1F: WDT error signal
Registration of data for initialization
Registration of data for connection
Modem/TA initialization
Line connection
Data communication
Y0: Transmission request signal
Y1: Reception data read complete signal
M0: Accessible flag
M50: Data communication enable flag
M70: Line disconnection enable flag
3
*1
Ready flag is ON
Data communication enable flag is ON
The line disconnection enable flag is
ON
Line disconnection command
Modem disconnection request signal
is set
When the modem disconnection
completion signal is ON, the error
code is read
Line disconnection completion flag
is set upon normal completion
Performs error handling when D105 is
other than 0 (error code)
Modem disconnection request signal
is reset
When any connection signal or
completion signal is ON, the modem
disconnection request signal is set
To turn OFF the modem disconnection
completion (X14), a second is required
after the modem disconnection request
(Y12) is ON.
When the modem disconnection
completion signal is ON, the request
signal is reset
When the modem disconnection
completion signal is OFF, the line
disconnection request signal is reset
*1
 Page 134, Section 3.4.3,  Page 139, Section 3.4.4,  Page 144, Section 3.4.5,  Page 148, Section
3.4.6,  Page 154, Section 3.4.7
163
3.4 Start-up of the Modem Function
Line disconnection processing
(Line disconnection from external
device)
Various request signals are reset
3.5
Sample Programs
This section shows sample programs to test the connection with the remote station's programmable controller CPU to
which Q series C24 is installed.
Each program contains a minimum set of processing necessary for performing a exchange test.
Modify the data for initialization and data for connection to match each system environment. When adding errorhandling procedures, add them separately by seeing the explanation in this chapter.
The uses of major devices that are used in these sample programs are listed below.
Application of device (comment list)
Device
Application
Device
Application
Device
Application
X3
Reception data read request
Y64
Line connection completion
M100
Initialization request execution
X4
Reception abnormal detection
Y66
Notification completion
M101
Connection request execution
Notification execution
X10
Initialization completion
Y67
Line disconnection completion
M102
Transmission execution in progress
X11
Dial in progress

M103
Reception data read execution in
progress
X12
Connection in progress
M0
Q series C24 accessible
X13
Initialization/connection
abnormal completion
M1
Initialization data registration
completion
X14
Modem disconnection
completion
M2
Data registration completion for
connection

X15
Notification normal completion
M3
Initialization completion
D0
Number of registration data bytes


SM400

Always ON

X16
Notification abnormal completion
M4
Line connection completion
D1
Control number designation
Receiver designation
X1E
Q series C24 ready
M6
Notification completion
D2
Initialization command/telephone
number
X1F
WDT error
M7
Line disconnection completion
D11
External line dialing number, etc.
X20
Initialization command
M10
Convert the registration
command into pulse
D12
Line type, etc.
X21
Line connection command
M20
Convert the registration
command into pulse
D23
Wait time for message transmission
X22
Data communication command
M30
Initialization enabled
D24
Message
X23
Line disconnection command
M31
Convert the initialization
command into pulse
D39
Message length
X24
Notification command
M40
Connectable
D50
Number of transmission data
M41
Convert the connection
command into pulse
D51
Transmission data


Y10
Initialization request
M50
Data communication enabled
D60
Number of reception data
Y11
Connection request
M51
Transmission enabled
D61
Reception data
Y12
Modem disconnection request
M52
Convert the transmission
command into pulse
D100
Initialization error code
Y14
Notification-issued request
M60
Convert the notification
command into pulse
D101
Line connection error code
Y60
Q series C24 accessible
M70
Line disconnection enabled
D102
Notification error code
Y61
Initialization data registration
completion
M71
Convert the line disconnection
command into pulse
D103
Data transmission error code
Y62
Data registration completion for
connection
M80
Line disconnection (request)
occurrence
D104
Data reception error code
Y63
Initialization completion
M91
Reception processing in
progress flag
D105
Line disconnection error code
M92
Transmission processing in
progress flag

164



CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
3.5.1
Sample program for data communication-1
(1) Sample program system configuration
The configuration of a system using this sample program is shown below.
1) Line connection
3
2) Communications by the non-procedure protocol
3) Line disconnection
Modem
Modem
QJ71C24-R2 2)
QJ71C24-R2 1)
(2) Connection request station side (QJ71C24-R2 1)) sample program
The modem connected to the CH1 side interface is initialized, the line is connected, data are transmitted by the
non-procedure protocol and the line is disconnected through commands from the user.
Perform the following settings before running this program.
(a) GX Developer switch settings ( Page 131, Section 3.4.2)
Switch No.
Setting value
Switch 1
07E2
Switch 2
0006
Switch 5
0000
3.5 Sample Programs
(b) Settings by GX Configurator-SC ( Page 131, Section 3.4.2)
Perform the following settings in each setting screen.
Use the default settings in screens and setting items other than those listed below.
• Modem function system settings
"Modem function system setting" screen setting items
Setting value
Modem connection channel designation
1CH
Data No. for initialization designation
07D5
Data No. for connection designation
0BB8
• Modem connection data registration
"Data for modem connection" screen setting item
Data for modem connection 1
(H0BB8)
*1
Telephone number*1
Setting value
0123456789
Specify the external party's telephone No.
165
<Status confirmation>
Access possible
Modem initialization, line connection
possible
Data communications possible
Data transmission possible
Line disconnect possible
<Modem initialization, line connection processing>
Conversion of modem initialization,
line connection commands to pulses
<Data transmission processing (non procedure protocol)>
Modem initialization, line connection
processing to sub routine
Conversion of data communications
(transmission) commands to pulses
<Data reception processing (non procedure protocol)>
To the data transmission processing
sub routine
Setting of the receive data reading
request
<Line disconnect processing>
To the data reception processing rub
routine
Conversion of line disconnect
commands to pulses
Conversion of turning connected
signals OFF to pulses
To the line disconnect processing sub
routine
166
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
[Modem initialization, line connection processing]
Set the connection request signal
With the initialization completed signal ON
and the connected signal ON, reset
the request signal
With the initialization/connection
abnormally completed signal ON,
read the error code and reset
the request signal
3
[Data transmission processing]
Set the transmission data
Set the transmission channel on CH1
Set the transmission data count
Execute the transmission request
Transmission normally completed
Transmission abnormally completed
Set the data reception channel on CH1
Execute reading of receive data
Reading of receive data normally
completed
Reading of receive data abnormally
completed
167
3.5 Sample Programs
[Data reception processing]
[Line disconnection processing]
Modem disconnection request signal is set
When the modem disconnection completion
signal is ON, the error code is read
When the normal completion signal is ON,
the line disconnection completion flag is set
Modem disconnection request signal is reset
168
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
(3) Sample program for a connection receiving station side (QJ71C24-R2 2))
After the connection in progress signal (x12) = ON, data communications are carried out by the non procedure
protocol through a command from the user.
Perform the following settings before running this program.
(a) GX Developer switch settings ( Page 131, Section 3.4.2)
Switch No.
Setting value
Switch 1
07E2
Switch 2
0006
Switch 5
0000
3
(b) Settings by GX Configurator-SC ( Page 131, Section 3.4.2)
Perform the following settings in each setting screen.
Use the default settings in screens and setting items other than those listed below.
• Modem function system settings
"Modem function system setting" screen setting items
Modem connection channel designation
Setting value
1CH
Data No. for initialization designation
07D5
Auto modem initialization designation
Auto initialize
3.5 Sample Programs
169
<Status confirmation>
Access possible
Data transmission possible
<Data transmission processing (non procedure protocol)>
Set the transmission data
Set the transmission channel
on CH1
Set the transmission data count
Execute transmission request
Transmission normally completed
Transmission abnormally completed
<Data reception processing (non procedure protocol)>
Set the data reception channel
on CH1
Execute reading of receive data
Reading of receive data normally
completed
Reading of receive data abnormally
completed
170
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
3.5.2
Sample program for data communication-2
(1) Sample program on the connection request station side
Initialization for the modem connected to CH1 interface, line connection, data communication by the non
procedure protocol and line disconnection are executed by commands from the user.
3
Before executing this program, perform the following settings (changing the default values) on the GX
Configurator-SC's "Modem function system setting/registration" screen and register them in the Q series C24.
(Settings other than the items shown below are not required.)
Settings on the GX Configurator-SC's "Modem function system setting" screen
Setting item
Modem connection channel designation
Setting value
CH1
No-communication interval time designation
2 (min)
Data No. for initialization designation
8001H
Data No. for connection designation
8002H
Remark
Registration of the modem's initialization data and line connection data, modem initialization, line connection, data
communications by the non procedure protocol and line disconnection are all performed by the sequence program.
3.5 Sample Programs
171
Accessible flag is turned ON
Modem initialization enabled flag is
turned ON
Line connectable flag with the remote
station is turned ON
Exchangeable flag with the partner
station is turned ON
Data transmission enabled flag
to the partner station turned ON
Line disconnection enabled flag
with the partner station is turned ON
To the data registration processing
for initialization subroutine
To the data registration processing
for connection subroutine
Convert the initialization command
into pulse
Various complete flags after the modem
initialization processing is reset
To the modem initialization processing
subroutine
Convert the line connection command
into pulse
Various complete flags after the line
connection processing is reset
To the line connection processing
subroutine
Convert the data communication
(transmission) command into pulse
To the data transmission processing
subroutine
Convert the reception data read request
into pulse
To the reception data read processing
subroutine
Convert the line disconnection command
into pulse
(Line disconnection from local station)
Line disconnection complete flag is reset
To the line disconnection processing
subroutine
Convert the connection in progress signal
OFF into pulse
(Line disconnection from partner side)
172
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
Convert the reset command of various
request signal into pulse
To the various request signal and
the complete signal OFF subroutine
Output the various complete flag status
(LED display)
P1
3
Data registration processing for initialization
subroutine
• Set the number of bytes of
the registration data
• Set the user control data (control number)
• Set the initialization command
• Write the data for initialization
(Data No. 8001H)
(Registration to buffer memory)
• Data registration complete flag
for initialization is set
P2
Data registration processing for connection
subroutine
• Set the number of bytes of
the registration data
• Clear the data storage device
for connection
• Set the pager receiver designation
(Notification is not executed)
• Set the telephone number
• Set the space to the remainder of
the telephone number designation area
• Set the external line dialing number (0)
3.5 Sample Programs
• Set the line type (tone)
• Write the data for connection
(Data No.8002H)
(Registration to buffer memory)
• Data registration complete flag
for connection set
P3
Modem initialization processing subroutine
• Set the initialization request signal
• Initialization request execution flag is set
• When the initialization complete
signal ON, the initialization complete flag
is set and the request signal is reset
• When the initialization/connection
abnormal complete signal ON,
the error code is read and the request
signal is reset
173
P4
Line connection processing subroutine
• Connection request signal is set
• Connection request execution flag is set
• When the connection in progress
signal ON, the connection complete flag
is set and the request signal is reset
• When the initialization/connection
abnormal complete signal ON, the error
code is read and request signal is reset
P51
Data communication processing subroutine
(Non procedure protocol, transmission)
• Set the transmission data
• Sets the transmission channel to CH1
• Set the number of transmission data
• Sets the transmitting flag
• Executes the transmission request
• Transmission request execution flag is
set
• Transmission normal completion
• Transmission abnormal completion
P52
Data reception processing subroutine
• Sets the data reception channel to CH1
• Reception data read execution flag is
set
• Executes the reception data reading
174
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
· Received data read normally
completed
· Received data read abnormally
completed
3
Line disconnection processing subroutine
(Line disconnection from local station)
· Modem disconnection request signal
is set
· When the modem disconnection
completion signal is ON, the error code
is read
· When the normal completion signal is
ON, the line disconnection completion
flag is set
· Modem disconnection request signal
is reset
Subroutine resetting various request
signals and completion signals
· Various request signals are reset
· To turn OFF the modem disconnection
completion signal, a second is required
after the modem disconnection request
signal is ON.
· When the initialization complete signal
is OFF and the modem disconnection
completion signal is ON, the request
signal is reset
· When the related signals are OFF,
the flag is reset
175
3.5 Sample Programs
· When any completion signal is ON,
the modem disconnection request
signal is set
(2) Sample program on the connection reception station side
The modem initialization and data communication by the non procedure protocol are executed by commands
from the user.
Before executing this program, perform the following settings (changing the default values) on the GX
Configurator-SC's "Modem function system setting" screen and register them in the Q series C24.
(Settings other than the items shown below are not required.)
Settings on the GX Configurator-SC's "Modem function system setting/registration" screen
Setting item
Modem connection channel designation
176
Setting value
CH1
No-communication interval time designation
2 (min)
Data No. for initialization designation
8001H
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
Accessible flag is turned ON
Modem initialization enabled flag is
turned ON
Exchangeable flag with the partner
station is turned ON
Data transmission enabled flag to
the partner station turned ON
To the data registration processing
for initialization subroutine
3
Convert the initialization command
into pulse
Various complete flags after the modem
initialization processing is reset
To the modem initialization processing
subroutine
Convert the data communication
(transmission) command into pulse
To the data transmission processing
subroutine
Convert the reception data read request
into pulse
To the various request signal and
the complete signal reset subroutine
Output the various complete flag status
(LED display)
177
3.5 Sample Programs
To the reception data read processing
subroutine
Convert the connection in progress
signal OFF into pulse
(Line disconnection from partner side)
Convert the reset command of various
request signal into pulse
P1
Data registration processing for initialization
subroutine
• Sets the number of bytes of the
registration data
• Sets the user control data
(control number)
• Sets the initialization command
• Write the data for initialization
(Data No. 8001H)
(Registration to buffer memory)
• Data registration complete flag
for initialization is set
P3
Modem initialization processing subroutine
• Initialization request signal is set
• Initialization request execution flag is set
• When the initialization complete signal
ON, the initialization complete flag is set
and the request signal is reset
• When the initialization/connection
abnormal complete signal ON, the error
code is read and the request signal is reset
P51
Data communication processing subroutine
(Non procedure protocol, transmission)
• Set the transmission data
• Sets the number of transmission data
(words)
• Transmission request execution flag is set
• Transmission request execution
• Transmission request normal completion
• Transmission request abnormal completion
178
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
Data reception processing subroutine
• Sets the data reception channel to
CH1
• Sets the data setting completion flag
for reading the receive data
• Executes the receive data reading
• Receive data read execution flag
is set
3
• Receive data normal completion
• Receive data abnormal completion
Resets subroutine of various request
signal and complete signal
• Various request signal is reset
• When any complete signal ON, the
modem disconnection request signal is
set
• To turn OFF the modem disconnection
completion signal, a second is required
after the modem disconnection request
signal is ON.
179
3.5 Sample Programs
• When the initialization complete signal
OFF and the modem disconnection
complete signal ON, the request signal
is reset
• When the relation various signal OFF,
the flag is reset
3.5.3
Sample program for notification
Modem initialization and notification are executed by commands from the user.
Before executing this program, perform the following settings (changing the default values) on the GX ConfiguratorSC's "Modem function system setting" screen and register them in the Q series C24.
(Settings other than the items shown below are not required.)
Settings on the GX Configurator-SC's "Modem function system setting/registration" screen
Setting item
Modem connection channel designation
Notification execution designation
Setting value
CH1
Perform notification
No-communication interval time designation
2 (min)
Data No. for initialization designation
8001H
Data No. for connection designation
8002H
Remark
Registration of the modem's initialization data and line connection data, modem initialization, line connection and
notifications are all performed by the sequence program.
180
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
Accessible flag is turned ON
Modem initialization enabled flag is turned ON
Line connectable flag with the remote station is
turned ON
To the data registration processing for initialization
subroutine
To the data registration processing for connection
subroutine
Converts the initialization command into pulse
3
Various complete flags after the modem
initialization processing is reset
To the modem initialization processing subroutine
Converts the notification command into pulse
To the notification processing subroutine
When the reset command, the complete flag is
reset
Output the various complete flag status
(LED display)
P1
Data registration processing for initialization
subroutine
• Sets the number of bytes of the registration data
• Sets the user control data (control number)
• Sets the initialization command
181
3.5 Sample Programs
• Write the data for initialization (Data No.8001H)
(Registration to buffer memory)
• Data registration complete flag for initialization is
set
P2
Data registration processing for connection
subroutine
• Set the number of bytes of the registration
data
• Clear the data storage device for connection
• Set the pager receiver designation
(Notification is executed)
• Set the telephone number
• Set the space to the remainder of
the telephone number designation area
• Set the external line dialing number (0)
• Set the line type (tone)
• Set the waiting time for the message
transmission
• Set the message
• Set the message length
• Write the data for connection
(Data No. 8002H)
(Registration to buffer memory)
• Data registration complete flag
for connection is set
• Notification-issued request signal is set
(Initial status)
P3
Modem initialization processing subroutine
• Initialization request signal is set
• Initialization request execution flag is set
• When the initialization complete signal ON,
the initialization complete flag is set
and the request signal is reset
• When the initialization/connection abnormal
complete signal ON, the error code is read
and the request signal is reset
P6
Notification processing subroutine
• Notification-issued request signal is reset
(Issue request)
• Notification execution flag is set
• When the notification normal complete
signal ON, the notification complete flag is
set and the request signal is set (Initial status)
• When the notification abnormal complete
signal ON, the error code is read
and the request signal is set (Initial status)
182
CHAPTER 3 COMMUNICATIONS BY THE MODEM FUNCTION
Memo
3
3.5 Sample Programs
183
CHAPTER 4
RECEIVING DATA WITH AN
INTERRUPT PROGRAM
In data communication between the Q series C24 and the external device, an interrupt program can be used to receive
data for the following data communication functions.
• Data reception during communication using the non procedure protocol
• Data reception during communication using the bidirectional protocol
This chapter explains a case in which data reception using the following data communication functions is performed
with an interrupt program.
External device
Data transmission
Q series C24
Receive
Interrupt-issued
Main program
Programmable
controller CPU
Main program
Interrupt program
execution
FEND
SM400
I
BUFRCVS
Receiving data with an interrupt program expedites data reception by the programmable controller CPU.
184
CHAPTER 4 RECEIVING DATA WITH AN INTERRUPT PROGRAM
4.1
Settings for Receiving Data Using an Interrupt Program
The following explains the settings for performing data reception with an interrupt program during communication using
the non procedure protocol or bidirectional protocol.
(1) Setting by GX Developer
The following settings are performed with the interrupt pointer No. of module screen.
• The interrupt pointer number and quantity (quantity is fixed at 2) for the programmable controller CPU used
for the Q series C24.
• Assigning correspondence between the programmable controller CPU interrupt pointer number and the Q
4
series C24 control number (fixed at 0).
(2) Setting by GX Configurator-SC
Perform the following settings in the transmission control and other system setting screens.
• Specify "Interrupt-issued" in Receive interrupt-issued designation.
To start the interrupt program, the settings of the "Interrupt pointer No. of module" in GX Developer and the "System setting"
in GX Configurator-SC are required.
4.1 Settings for Receiving Data Using an Interrupt Program
185
4.2
Interrupt Program Startup Timing
The following explains the startup timing for interrupt program when performing data reception with an interrupt
program during communication using the non procedure protocol or bidirectional protocol.
(1) The startup timing is the same for communication using either the non
procedure protocol or bidirectional protocol.
(2) Receive data from the external device is stored in the reception area of the
buffer memory. When the next input signal rises, the interrupt program is
started.
Input signal name
186
CH1
CH2
CHn reception data read request signal
X3
XA
CHn reception abnormal detection signal
X4
XB
CHAPTER 4 RECEIVING DATA WITH AN INTERRUPT PROGRAM
4.3
Reception Control Method Using an Interrupt Program
The following explains the reception control method when receiving data with an interrupt program during
communication using the non procedure protocol or bidirectional protocol.
<Data reception using the dedicated instruction,
BUFRCVS instruction (interrupt program)>
FEND
4
SM400
I50
Z.BUFRCVS
"U0"
K1
Control data
D200
⋅ [D200]: Word count for stored receive data
⋅ [D201]: Receive data
IRET
5)
2)
Main program execution
Interrupt program execution
BUFRCVS instruction
3)
X3
Reception abnormal
detection signal
X4
1)
4)
Buffer memory
reception area
Reception using bidirectional
protocol
Data reception
Response
transmission
1) When data is received from the external device, the receive data is stored in the buffer memory and the reception
data read request signal turns ON.
2) The main program stops executing and the interrupt program starts.
3) The data reception dedicated instruction, BUFRCVS, for the interrupt program is executed and data is received.*1
4) When execution of the BUFRCVS instruction is complete, the reception data read request signal turns OFF.
5) When execution of the interrupt program is finished, execution of the main program restarts.
*1
When the reading of receive data using the BUFRCVS instruction is finished, the following processes are performed.
At normal completion: Programmable controller CPU error flag (SM0) turns OFF.
At abnormal completion: Programmable controller CPU error flag (SM0) turns ON.
The error code is stored in the programmable controller CPU error code (SD0).
For more details on the programmable controller CPU error flag (SM0) and error codes (SD0), see the programmable
controller CPU Manual.
187
4.3 Reception Control Method Using an Interrupt Program
Reception data read
request signal
4.4
Programming
This section explains the programming when data reception is performed with an interrupt program during
communication using the non procedure protocol or bidirectional protocol.
4.4.1
Program example
The following shows a program example for receiving data using an interrupt program.
(Program condition)
• Interrupt pointer setting with GX Developer
• PLC side: Interrupt pointer Start No. = 50, Interrupt pointer No. of module = 2 (fixed)*1
*1
CH1 side interrupt pointer = I50, CH2 side interrupt pointer = I51
• Intelli. module side: Start I/O No. = 0, Start SI No. = 0 (fixed)
• Interrupt program start enable/disable setting with GX Configurator-SC
• CH1 side: Issues interrupt (performs communication via the non procedure protocol.)
• CH2 side: Does not issue interrupt
(Program example)
When the Q series C24 I/O signals are X/Y00 to X/Y1F
Interrupt program enabled
For CH1 side
Normal reception
Abnormal reception
Sets the flag for confirming
normal reception/abnormal
reception in the main program
* Resets by the main program
Reception interrupt program executed
Receives data and stores it
in D200 and succeeding addresses
D200
: No. of receive data
From D201: Receive data
188
CHAPTER 4 RECEIVING DATA WITH AN INTERRUPT PROGRAM
Data register
Buffer memory
D200
D201
Reception area
No. of receive data
Receive data
D2nn
4
● When data reception is performed with an interrupt program, the dedicated BUFRCVS instruction is used regardless of
whether the communication uses the non procedure protocol or bidirectional protocol. For more details on the BUFRCVS
instruction, see Page 371, Section 17.2.
● Create a program that enables/disables interrupts during execution of the main program in order to start the interrupt
program. Use the EI, DI, and IMASK instructions.
4.4 Programming
189
4.4.2
Precautions when receiving data with an interrupt program
The following shows the precautionary notes when receiving data with an interrupt program.
(1) Create an interrupt program for data reception for each interface.
(2) Use GX Configurator-SC to set whether or not the interrupt program is started.
Whether or not the interrupt program is started can also be set with direct
writing to the buffer memory. However, if it is specified during data reception,
the interrupt program will not start.
(3) Do not use the INPUT and BIDIN instructions during execution of the interrupt
program. Always use the BUFRCVS instruction to receive data.
(4) Do not turn the reception data read completion signal (Y1/Y8) ON/OFF during
execution of the interrupt program.
(5) Use always ON (SM400) or direct input signal (DX3, DX4) as the contact signal
when executing the BUFRCVS instruction. ( Page 371, Section 17.2)
190
CHAPTER 4 RECEIVING DATA WITH AN INTERRUPT PROGRAM
(6) After the power supply turns from OFF to ON or the programmable controller
CPU is reset, data cannot be received because the interrupt program is
invalidated during the initial processing of the programmable controller CPU.
For asynchronous data communication with the Q series C24 from the external
device without communication procedure setting, read the data as shown in
the following program.
When the input/output signals of the Q series C24 are X/Y00 to X/Y1F
4
After RUN, 1 scan only INPUT
instruction execution
Normal completion processing
Abnormal completion processing
CH1 error information is
initialized
Received interrupt program
execution
4.4 Programming
191
CHAPTER 5
CHANGING SEND AND RECEIVE
DATA LENGTH UNITS TO BYTE
UNITS (WORD/BYTES UNITS
SETTING)
The word units are used for the data length (count) of the amount of data sent/received using the following data
communication functions in data communication between the Q series C24 and the external device.
This chapter explains how to change the units (word to byte, byte to word) of the data length (count) sent/received with
the following data communication functions.
The data length units can be set for each Q series C24 interface. The Q series C24 controls the number of data to be
transmitted to the external unit and the number of data when it requests the programmable controller CPU to read the
data received from the external device according to the units set by the user.
(1) Data communication functions and buffer memory related to data length units
The following lists the data communications functions and buffer memory related to the data length units.
(The buffer memory addresses in the table are the default value.)
Data communications function
MC protocol
Nonprocedural
protocol
Bidirectional
protocol
Name of buffer memory related to data length units
(Address CH1, CH2)
On-demand function
On-demand data length designation area (A1H, 141H)
Data transmit
function
Send data count storage area (400H, 800H)
Data receive function
Received data count designation area (A4H, 144H)
Receive data count storage area (600H, A00H)
Data transmit
function
Send data count storage area (400H, 800H)
Data receive function
Receive data count storage area (600H, A00H)
Reference manual
( MELSEC Communication
Protocol Reference Manual)
 User's manual (Basic)
 User's manual (Basic)
(2) How to change the units of the data length (count)
The units of the data length (count) can be changed using one of the following procedures.
• Changing via GX Configurator-SC: The units can be changed on the GX Configurator-SC's system setting
screen.
• Changing via the programmable controller CPU: The units can be changed with the CSET instruction.
Change the units of the data length (count) according to the explanation in Page 384, Section 17.4 of this
manual.
192
CHAPTER 5 CHANGING SEND AND RECEIVE DATA LENGTH UNITS TO BYTE UNITS (WORD/BYTES UNITS SETTING)
Memo
5
193
CHAPTER 6
CHANGING THE DATA
COMMUNICATIONS MONITORING
TIMES
The monitoring times are timers used by the Q series C24 to monitor the receiving interval time between each byte
when receiving data from the external device, the programmable controller CPU processing time, and the time it takes
to transmit to the external device.
The monitoring times can be set for each interface. The Q series C24 uses the monitoring time set by the user to
control data transmission to and reception from the external device.
Set the monitoring times to match the specifications of the external device.
The Q series C24 monitoring times are listed below.
Protocol that can monitor the time
Monitoring time
Q series C24 default value
MC
Non
procedure
Bidirectional






5s



Transmission monitoring time (timer 2)
3min



Message wait time
0ms



No-reception monitoring
time (timer 0)
Format 0
Format 1
0 byte (Infinite wait)
Response monitoring time (timer 1)
Remarks
Transmission time for the set
number of bytes (depends on the
transmission rate)
For bidirectional protocol, this is
valid for transmission only.

No wait time
Data communications using an MC protocol
Command message
First data
1 byte
Last data
External
device
First data
Last data
Programmable
controller CPU
Response message
Q series C24
ready to receive
data state
Timer 0 monitoring time
Timer 0 elapsed time reset
Timer 1 monitoring time
Timer 2 monitoring time
Message wait time
Timer 1 elapsed time reset
194
H/W gate OFF time
Timer 2 elapsed time reset
CHAPTER 6 CHANGING THE DATA COMMUNICATIONS MONITORING TIMES
6.1
No-reception Monitoring Time (timer 0) Setting
The no-reception monitoring time (timer 0) is the time for clearing the Q series C24 state when the Q series C24 is
placed into the data receive wait state by trouble in the external device.
The Q series C24 monitors the reception interval in byte units at the start of data reception from the external device
and ends monitoring when the preset last data is received and repeats this operation.
The following explains the no-reception monitoring time (timer 0) operation.
1 byte
External
device
Data 1
Data 2
Data n-1
Data n
Programmable
controller CPU
Data receive interval
(depends on the transmission rate, etc.)
Monitoring
time
Elapsed time reset
6
● One byte is always handled as 12 bits in the no-reception monitoring time (timer 0), regardless of the transmission
setting.
● If the non-reception monitoring time (timer 0) was changed in the sequence program, execute any of the following to
enable the changed value.
• Mode switching ( Page 345, CHAPTER 15)
• UINI instruction ( Page 369, CHAPTER 17)
• Programmable controller CPU information clear ( User's Manual (Basic).)
Monitors the receive interval in byte units and returns the elapsed time to 0 each time one byte is received.
At time-out, the Q series C24 performs the following processing.
(a) Data communication using MC protocol
• Stores the error code to the MC protocol transmission error code storage area (buffer memory addresses
25AH, 26AH) for the target interface.
• Transmits a NAK message to the external device and enters the command message receive wait state.
(b) Data communications using non procedure protocol (Format 0)
• Data communications not using user frames
• Passes the receive data up to time-out to the Q series C24.
• Stores the error code to the data receive result storage area (buffer memory addresses 258H, 268H) for
the target interface and turns on the reception abnormal detection signal (X4, XB) and waits to receive the
next data.
Receiving according to the received complete code (Received complete code: CR + LF (0D0AH))
When the LF is not received within the set time for timer 0 after reception of the CR, the abnormal
reception detection signal to the programmable controller CPU turns ON and the received data at the CR
is stored in the received data storage area of the buffer memory.
195
6.1 No-reception Monitoring Time (timer 0) Setting
(1) Q series C24 operation by no reception monitoring time (timer 0)
CR
External device
Timer 0
Set time
(*1)
Q series C24
Abnormal reception detection signal
(X4/XB)
*1 CR is treated as 1 byte of data included in the message.
• Data communications using user frames
• When designating the last frame, an arbitrary part of data in the area starting from the start of the reception
of the current message until time-out is read into the Q series C24, and the data in the last frame area is
ignored (deleted).
• Stores the error code to the data receive result storage area (buffer memory addresses 258H, 268H) for
the target interface and turns on the reception abnormal detection signal (X4, XB) and waits to receive the
next data.
(c) Data communications using non procedure protocol (Format 1)
The reception monitoring format 1 of the no-reception monitoring time (timer 0) is used for receiving a message
for which the receive complete code and receive data count has not been preset. This occurs when the noreception monitoring time (timer 0) runs out on the non procedure protocol.
• Data is received by the Q series C24 until the time is out, the receive data read request signal (X3, XA) turns
ON, and the following data reception waiting condition occurs.
When receiving using the receive data count (Receive data count: 4 bytes)
After 3 bytes of data is received, the 3-byte data is stored in the received data storage area of the buffer
memory by the time out (timer 0) and the receive data read request signal to the programmable controller
CPU turns ON.
External device
A
B
C
Timer 0
Set time
Q series C24
Receive data read request signal
(X3/XA)
(d) Data communications using bidirectional protocol
• Ignores (deletes) the receive data from the start of reception of the current message to time-out.
• Stores the error code to the data receive result storage area (buffer memory addresses 258H, 268H) for the
target interface.
• When the receive data complete, transmits a NAK message to the external device and waits to receive the
next data.
196
CHAPTER 6 CHANGING THE DATA COMMUNICATIONS MONITORING TIMES
(2) Changing the no-reception monitoring time (timer 0)
(a) Changing the no-reception monitoring time (timer 0)
The no-reception monitoring time (timer 0) is designated by the number of transmitted characters (byte count)
corresponding to the data communication rate set in the interface, and then it is registered on the GX
Configurator-SC's "Transmission control and others system setting" screen.
Adjust or set the value based on the specifications of the external device.
(b) No-reception monitoring time format specification in non procedure protocol
(Format 0/Format 1)
The no-reception monitoring time format in non procedure protocol is specified to use the no-reception
monitoring time (timer 0) by the non procedure protocol and is registered on the "Non procedure system
setting" screen.
Remark
• When changing the no-reception monitoring time (timer 0)
Find the result using the following expression and set the number of bytes or greater for the no-reception monitoring time
(timer 0).
No-reception monitoring time (timer 0) = 1 +
6
Td × Vbps
12000
(Round up fractions below decimal point.)
Td: Maximum delay time for external device output processing (ms)
Vbps: Transmission rate (bps)
Calculation of no-reception monitoring time (timer 0)
No-reception monitoring time (timer 0) = 1 +
50 × 9600
= 41 bytes
12000
In this case, actual monitoring time is as follows:
41 bytes  12*1  9600  1000 = 51.25ms
*1
Number of transmit bits per byte (Fixed)
• When exchanging data with the external device through the Q series C24 RS-422/485 interface and changing the
no-reception monitoring time (timer 0)
Find the result using the following expression and set the number of bytes or greater for the no-reception monitoring time
(timer 0).
No-reception monitoring time (timer 0) = 1 +
(Td + T1) × Vbps
12000
(Round up fractions below decimal point.)
Td: Maximum delay time for external device output processing (ms)
T1: External device side H/W gate OFF time (ms)
Vbps: Transmission rate (bps)
197
6.1 No-reception Monitoring Time (timer 0) Setting
• Transmission rate (Vbps): 9600bps
• Maximum delay time for external device output processing (Td): 50ms
6.2
Response Monitoring Time (timer 1) Setting
The response monitoring time (timer 1) clears the receive wait state of the device that receives the response message
when trouble in the device that received the message does not return a response message (result) to the external
device.
When the Q series C24 receives a message from the external device, it monitors the programmable controller CPU
processing time up to the start of transmission of the response message to the external device.
When a message was received, it monitors the external device processing time up to the start of reception of the
response message from the external device.
The following describes the response monitoring time (timer 1) operation.
External device
Message
Programmable
controller CPU
Response message
Response message
Message
Monitoring time
Monitoring time
Elapsed time reset
Elapsed time reset
• If on-demand data is transmitted before a response message during data communications using a MC
protocol, the time up to the start of transmission of the on-demand data is monitored.
External
device
Programmable
controller CPU
Command message
On-demand data
Response message
Monitoring time
Elapsed time reset
(1) Q series C24 operation by response monitoring time (timer 1)
(a) When response monitoring time (timer 1) set to 0ms
After receiving a message, the Q series C24 does not monitor the time up to the start of transmission of a
response message to the external device, but waits infinitely.
After transmitting a message, the Q series C24 does not monitor the time up to the start of reception of the
response message from the external device, but waits infinitely.
(b) When response monitoring time (timer 1) is set to 100ms or longer
After receiving a message, the Q series C24 monitors the time up to the start of transmission of a response
message to the external device and returns the elapsed time to 0 at the start of transmission.
After transmitting a message, the Q series C24 monitors the time up to the start of reception of the response
message from the external device and returns the elapsed time to 0 at the start of reception.
At time-out, the Q series C24 performs the following processing.
• Data communications using a MC protocol
• Stores the error code to the MC protocol transmit error code storage area (buffer memory addresses
25AH, 26AH) for the target interface.
• Transmits a response message (NAK message) to the external device and waits to receive the next
command message.
• Data communications using bidirectional protocol
• Stores the error code to the data transmission result storage area (buffer memory addresses 257H, 267H)
for the target interface and performs transmission processing abnormal completion.
• While waiting to transmit a response message, the Q series C24 does not check the response monitoring
time.
198
CHAPTER 6 CHANGING THE DATA COMMUNICATIONS MONITORING TIMES
(2) Changing the response monitoring time (timer 1)
The response monitoring time (timer 1) is registered on the GX Configurator-SC's "Transmission control and
others system setting" screen.
For data communication using the MC protocol, set the response monitoring time so that it is longer than the
message wait time.*1
*1
The message wait time is designated at the following locations.
• A compatible 1C frame: Designate in a command message
• QnA compatible 2C/3C/4C frame: GX Configurator-SC "MC protocol system setting" screen
When changing the response monitoring time (timer 1) default value (5 s), observe the following precautions.
(1) Data communications using an MC protocol
In any of the following cases make the default value the message wait time described in Page 202, Section 6.4, or longer.
● When designating the monitor conditions with the following functions, set the maximum time matched to system
operation.
• Word units random read ( MELSEC Communication Protocol Reference Manual)
• Device memory monitor ( MELSEC Communication Protocol Reference Manual)
6
● Access other than (a) above
• When accessing a station connected (including multidrop link) to an external device, set the following value, or
longer.
Response monitoring time >= Maximum number of scans required to process the command used  connected station scan
time
• When accessing another station over a network system, set the default value to infinity or the following time, or
longer.
Response monitoring time >= Maximum number of scans required to process the command used  communications time
When setting the default value to infinity, check the external device response wait time and initialize the Q series C24
transmission sequence when time-out is generated. ( MELSEC Communication Protocol Reference Manual)
6.2 Response Monitoring Time (timer 1) Setting
Refer to the MELSEC Communication Protocol Reference Manual for the maximum number of scans and the
communication time required by processing.
(2) Data communications using bidirectional protocol
Set the default value to the following time, or longer.
(Sequence scan time  2) + 100ms
199
6.3
Transmission Monitoring Time (timer 2) Setting
The transmission monitoring time (timer 2) clears the wait state when the Q series C24 that is to transmit a message or
response message (result) has entered the transmission end wait state due to trouble in the external device.
When the Q series C24 transmits a message, it monitors the wait time up to the end of transmission of the message.
When the Q series C24 received a message from the external device, it monitors the wait time up to the end of
transmission of the response message.
The following explains the transmission monitoring time (timer 2) operation.
External
device
Programmable
controller CPU
Message
Response message
Message
Response message
Monitoring
time
Monitoring
time
Elapsed time reset
• If on-demand data is transmitted before a response message during data communications using an MC
protocol, each time is monitored.
External
device
Programmable
controller CPU
Command message
On-demand data
Response message
Monitoring
time
Monitoring
time
Elapsed time reset
(1) Q series C24 operation by transmission monitoring time (timer 2)
(a) When transmission monitoring time (timer 2) is set to 0ms
The time until transmission of the message or response message is not monitored. If the Q series C24 cannot
transmit, it waits infinitely.
(b) When transmission monitoring time (timer 2) is set to 100ms or longer
Monitors the time from completion of message or response message transmission preparations to the end of
transmission and returns the elapsed time to 0 at the end of transmission.
At time-out, the Q series C24 performs the following processing.
• Data communications using MC protocol
• While waiting for the end of transmission of the response message, the Q series C24 stores the error code
to the data transmission result storage area (buffer memory addresses 257H, 267H) for the target
interface. The Q series C24 enters the state in which it waits to receive the next command message
without sending a response message (NAK message) to the external device.
• During on-demand data transmission, the Q series C24 stores the error code to the on-demand execution
result storage area (buffer memory addresses 256H, 266H) for the target interface.
• If transmission was terminated midway in either of the cases above, the Q series C24 does not transmit
the remaining data.
200
CHAPTER 6 CHANGING THE DATA COMMUNICATIONS MONITORING TIMES
• Data communications using non procedure protocol or bidirectional protocol
• While waiting for the end of transmission of a message, the Q series C24 stores the error code to the data
transmission result storage area (buffer memory addresses 257H, 267H) for the target interface and
performs transmission processing abnormal completion. If message transmission was terminated midway,
the Q series C24 does not transmit the remaining data.
• If waiting for the end of transmission of a response message, the Q series C24 stores the error code to the
data receive result storage area (buffer memory addresses 258H, 268H) for the target device and turns on
the reception abnormal detection signal (X4, XB).*1 When the receive data read complete, the Q series
C24 turns off the reception abnormal detection signal (X4, XB) and waits to receive the next command. If
transmission of the response message was terminated midway, the Q series C24 does not transmit the
remaining data.
*1
When communicating using bidirectional protocol, it stores the error code in the data receive result storage area for the
target interface. (The reception abnormal detection signal does not turn on.)
(2) Changing the transmission monitoring time (timer 2)
The transmission monitoring time (timer 2) is registered on the GX Configurator-SC's "Transmission control and
6
others system setting" screen.
The transmission monitoring time (timer 2) monitors the transmission termination time when the following states are
generated.
• When DTR/DSR signal control is used and the DR (DSR) signal is turned off ( Page 204, Section 7.1)
• When DC1/DC3 receive control is used and DC3 is received ( Page 206, Section 7.2)
• When the RS-232 interface CS (CTS) signal is turned off ( User's manual (Basic))
Criteria when changing the transmission monitoring time (time 2) setting
Find the transmission monitoring time (timer 2) time from the maximum delay time of external device message receive
processing or response message transmission processing and the transmission time/byte (t) and change the set value.
• Number of bytes transmitted/second (n) = Transmission rate/number of transmit bits/byte
• Transmission time/byte (t) = 1000 (ms)/number of bytes transmitted/s (n)
• Transmission monitoring time (timer 2) = (Maximum external device processing delay time) + (transmission
time/byte (t)  transmit byte count)100ms units truncated
Under the following conditions, the transmission monitoring time (timer 2) is set to 300ms
• Transmission rate: 9600 bps
• Number of transmit bits/byte: 11 (start bit: 1, data bits: 8, stop bits: 2)
• Maximum processing delay time: 200ms
• Transmit byte count: 3 bytes
201
6.3 Transmission Monitoring Time (timer 2) Setting
Remark
6.4
Message Wait Time Setting
The message wait time is used during data communications using a MC protocol.
It is the time for an external device that cannot receive the data immediately after it has been transmitted.
When the Q series C24 transmits a response message in reply to a command message received from the external
device, transmission of the response message is delayed by the message wait time, or longer.
The following explains the message wait time operation for data communications using QnA compatible 2C/3C/4C
frame. (For A compatible 1C frames, the message wait time is designated in the command message.)
External
device
Programmable
controller CPU
Command message
Response message
Message wait time
(1) Q series C24 operation by message wait time
• When message wait time is 0ms
If a response message can be transmitted, the Q series C24 immediately transmits the response message. A
transmission wait time is not set.
• When the message wait time is 10ms or longer
If a response message can be transmitted, and the message wait time after reception of the command message
has elapsed, the Q series C24 transmits the response message.
(2) Changing the transmission wait time
The transmission wait time is registered on the GX Configurator-SC's "MC protocol system setting" screen
● If the external device that must wait a certain time before it can receive a response message after a command message
was transmitted, set the message wait time as explained above. Especially, for data communications with an external
device connected to the Q series C24 RS-422/485 interface, set the message wait time to the external device hardware
gate OFF time or longer.
● The message wait time described here is the time for data communications using QnA compatible 2C/3C/4C frame.
202
CHAPTER 7 DATA COMMUNICATIONS USING DC CODE TRANSMISSION CONTROL
CHAPTER 7
DATA COMMUNICATIONS USING DC
CODE TRANSMISSION CONTROL
The transmission control function controls (termination, restart) the transmission and reception of data between the Q
series C24 and external device by turning transmission control signals on and off, or by transmitting and receiving DC
codes (DC1, DC2, DC3, DC4), or informs the range of validity for the data to the external device.
The transmission control function can be set for each Q series C24 interface. The Q series C24 uses the transmission
control function set by the user to control data communications with external devices.
Set the transmission control function to match the specifications of the external device.
The table below lists the Q series C24 transmission control functions.
Transmission control
function
Kind of control
Interface that can be
controlled
232
422/485


(Ignored)
DTR control
DTR/DSR signal control*1
DSR control
RS/CS signal control*2
CD signal
control*2
DC code control*1
DC2/DC4
transmission control
DC2/DC4 reception
control
Remarks
MC
Non
procedure
Bidirectional






Cannot be used simultaneously
with DC control.
One is selected.





Normal control.





The cable wiring depends on
whether or not control is used.
With half-duplex communications,
control is necessary.












DC1/DC3
transmission control
DC1/DC3 reception
control
Protocol that can be controlled


Cannot be used simultaneously
with DTR/DSR signal control.
One is selected.
: Possible (transmission control used), : Invalid
*1
*2
When using full-duplex communications with bidirectional protocol data communications, refer to the User's Manual
(Basic).
Refer to the User's Manual (Basic) and check Q series C24 operation according to the RS (RTS) signal and CS (CTS)
signal control contents and CD terminal check designation.
When the Q series C24 is started, DTR/DSR signal control and RS/CS signal control are enabled.
203
7
7.1
Control Contents of DTR/DSR (ER/DR) Signal Control
This control uses the RS-232 interface DTR/DSR signals to inform the external device whether or not the local station
is ready to receive data.
The Q series C24 uses the ER (DTR) signal to inform the external device whether or not the local station is ready to
receive data and uses the DR (DSR) signal to check if the external device is ready to receive data.
(Terminate)
External device
(Restart)...Continue
Data 1-2
Data 1-1
Data 1-2
Programmable
controller CPU
Data 2-2
(Terminate) (Restart)...Continue
ER(DTR) signal
DR(DSR) signal
(1) Q series C24 DTR control
(a) Q series C24 DTR control
The Q series C24 uses the ER (DTR) signal to inform the external device whether or not it is ready to receive
data.
The data transmitted from the external device by non procedure protocol is stored to the buffer memory receive
data storage area through the OS area. ( User's manual (Basic))
For the following conditions, the receive data is temporarily stored to the OS area and is transferred to the
receive data storage area when the present receive data read processing is complete.
• Receive data size exceeds the size of the buffer memory area when "receive data storage area < receive
data length data" was received.
• The data was received before the sequence program read the previously received data.
The Q series C24 turns the ER (DTR) signal on/off as listed below, depending on the size of the vacant OS
area.
• Vacant area 64 bytes (default) or less: Off
• Vacant area 263 bytes (default) or more: On
ON
ER(DTR) signal
OFF
ON
OFF
ON: Ready to receive
OFF: Not ready to receive
Receive preparations
complete
Q series C24
(OS area)
Q series C24
(OS area)
(Data storage)
8448
bytes
(Data storage)
Vacant area
8448
bytes
64 bytes
or less
(default)
Vacant area
263 bytes
or more
(default)
After read complete from
sequence program
204
CHAPTER 7 DATA COMMUNICATIONS USING DC CODE TRANSMISSION CONTROL
(b) Specification of free OS area
The limit of free OS area for data reception under the DTR/DSR (ER/DR) signal control is specified in GX
Configurator-SC's "Transmission control and others system setting". When it reaches the limit, this status is
notified to disable data reception.
The set values must satisfy the following condition.
"Transmission control start free area < Transmission control end free area"
• Transmission control start free area specification (Address: 2012H/2112H)
Specifies an available capacity in the OS area so that the full status is notified to disable the data reception (ER
(DTR) signal is OFF).
• Transmission control start free area: 64 to 4095 (Default: 64)
• Transmission control end free area specification (Address: 2013H/2113H)
Specifies an available capacity in the OS area so that data reception is enabled by notification (ER (DTR)
signal is ON).
• Transmission control end free area: 263 to 4096 (Default: 263)
Remark
● "Receive data clear" described in User's Manual (Basic) clears the data stored in the OS area. (The receive area in the
buffer memory is not cleared.)
● If more data is received when the OS area mentioned above are 0 byte, an SIO error is generated and the data received
until the OS area becomes vacant is ignored. At this time, the SIO signal is turned on. ( User's manual (Basic))
7
(2) Q series C24 DSR control
The Q series C24 uses the DSR signal to detect whether or not the external device is ready to receive data and
to control data transmission to the external device as shown below, depending on whether the DSR is on/off.
• If the DSR signal is OFF, even if there is send data, the Q series C24 does not transmit it to the external
device. When the DSR signal is turned on, the Q series C24 transmits the send data to the external device.
205
7.1 Control Contents of DTR/DSR (ER/DR) Signal Control
• If the DSR signal is ON and there is send data, the Q series C24 transmits it to the external device.
7.2
Control Contents of DC Code Control
This control uses the Q series C24 transmission control data to inform the external device whether or not local station
is ready to receive data and the valid range of the send and receive data.
The four kinds of Q series C24 DC code control shown below are available. These control functions can be used
simultaneously.
(1) DC1/DC3 transmission control, DC1/DC3 reception control
The Q series C24 informs the external device whether or not local station is ready to receive data by transmitting
the DC1 and DC3 signals and checks whether or not the external device is ready to receive data by receiving the
DC1 and DC3 signals.
DC1: Control data that informs the external device that the Q series C24 is ready to receive data
DC3: Control data that informs the external device that the Q series C24 is not ready to receive data
(Terminate)
External device
Programmable
controller CPU
206
(Restart)...Continue
Data 1-2
Data 1-1
D
C
3
D
C
1
D
C
3
Data 2-1
(Terminate)
D
C
1
Data 2-2
(Restart)...Continue
CHAPTER 7 DATA COMMUNICATIONS USING DC CODE TRANSMISSION CONTROL
(a) Q Series C24 DC1/DC3 transmission control and free OS area specification
The control is performed in the same as those described in Page 204, Section 7.1 (1), DTR control. The free
OS area specification are the same as those described in Page 205, Section 7.1 (1) (b).
The Q series C24 transmits DC1 or DC3 to the external device instead of turning the ER (DTR) signal on/off.
For the DC1 and DC3 transmit timing, replace ER (DTR) signal ON/OFF as listed below.
(DTR control) (DC1, DC3 transmission control)
ER (DTR) signal OFF= DC3 transmit: Transmitted when the vacant OS area drops to 64 bytes (default) or less
ER (DTR) signal ON = DC1 transmit: Transmitted when the vacant OS area reaches 263 bytes (default) or
more
External device
Programmable
controller CPU
Data
Data
D
C
3
D
C
1
Remark
● "Receive data clear" described in the User's Manual (Basic) clears the data stored in the OS area.
● If more data is received when the vacant OS area mentioned above is 0 byte, an SIO error is generated and the data
received until the OS area becomes vacant is ignored. At this time, the SIO LED is turned on. ( User's manual
(Basic))
7
(b) Q series C24 DC1/DC3 reception control contents
• When the Q series C24 receives DC3 from the external device, it terminates data transmission. The
sequence program cannot read the received DC3 signal.
• When the Q series C24 receives DC1 from the external device, it restarts data transmission. (The Q series
the received DC1 signal.
D
C
3
External device
Q series C24
Data
D
C
1
Data
• Once DC1 is received, subsequent DC1 are ignored and are removed from the receive data.
● In the DC1/DC3 transmission/reception control, the state of the Q series C24 is as follows at the time of power-on, reset
or mode switching of the CPU, or the UINI instruction execution.
● DC1 is not transmitted to the external device.
• This is the same state as when DC1 was transmitted.
• The same state as when DC1 was received even if DC1 is not received from the external device.
207
7.2 Control Contents of DC Code Control
C24 resumes transmission from the data terminated on DC3 reception.) The sequence program cannot read
(2) DC2/DC4 transmission control, DC2/DC4 reception control
The Q series C24 encloses the send data from the local station in the DC2 and DC4 codes and transmits it to the
external device and processes the data received from an external device enclosed in the DC2 and DC4 codes as
valid data.
DC2: Control data that informs the external device that the data following it is the start of the valid data
DC4: Control data that informs the external device that the data immediately preceding it is the end of the valid
data
External device
DC2
Data
DC4
DC2
Programmable
controller CPU
DC2
Data
Data
DC4
(a) Q series C24 DC2/DC4 transmission control contents
When transmitting data to an external device, the Q series C24 adds the DC2 code to the head of the send
data and the DC4 code to the end of the send data.
D
C
2
D
C
4
Data
E
N
Q
D
C
2
Transmit order
(Non procedure protocol)
Data
Sum check
Programmable
controller CPU
Data length
External device
D
C
4
Transmit order
(Bidirectional protocol)
* The DC2 and DC4 code are also added when MC protocol is used.
(b) Q series C24 DC2/DC4 reception control contents
• When the Q series C24 receives DC2 from the external device, it processes the receive data up to DC4 as
valid data. The sequence program cannot read the received DC2 code.
• When the Q series C24 receives DC4, it ignores the receive data up to immediately before DC2 as invalid
data. The sequence program cannot read the received DC4 code.
(Non procedure protocol)*1
D
C
2
D
C
4
Data
D
C
2
Arbitrary
data
D
C
4
Data
External device
Programmable
controller CPU
Stored to Q series C24
buffer memory or OS area
Ignored by
the Q series C24
Stored to Q series C24
buffer memory or OS area
208
Sum check
code
Character
E
N
Q
Message wait
D
C
2
Command
External
device
PC No.
*1 MC protocol A
compatible 1C frame
format 1
Station No.
• Once DC2 is received, subsequent DC2 are ignored and are removed from the receive data.
D
C
4
CHAPTER 7 DATA COMMUNICATIONS USING DC CODE TRANSMISSION CONTROL
(3) The transmission control method and changing the DC code
Switching between DC code control method and DTR/DSR control as well as changing of the DC code are
registered on the GX Configurator-SC's "Transmission control and others system setting" screen.
7
7.2 Control Contents of DC Code Control
209
7.3
Precautions when Using the Transmission Control
Functions
The following describes the precautions to be observed when using the Q series C24 transmission control functions.
(1) Agreement between external device and programmable controller CPU
The external device and programmable controller CPU must agree to the following.
• Whether or not a transmission control function is to be used. If a control function is used, which control is to
be used for data communications.
• Control timing.
• DC1 to DC4 codes when DC control is performed. (The DC1 to DC4 codes used can be arbitrarily changed.)
(2) Transmission control function usage conditions
• DTR/DSR control and DC code control cannot be used at the same time. Select one of them using the GX
Configurator-SC registration.
• When using DTR/DSR control, connect the Q series C24 ER (DTR) and DR (DSR) signals to the external
device.
(3) Transmission control function setting
Set a transmission control function that can control the target interface.
If a function that cannot control the target interface is set, the set contents are invalid.
(4) Setting of transmission control function during linked operation
When the two Q series C24 interfaces are linked ( User's Manual (Basic)), set the transmission control
function of only the interface that must be controlled.
Set the other interface to "Do not use transmission control function" (set value when directly set to the buffer
memory: 0001H).
(5) DC code control
• DC1/DC3 transmission control and DC1/DC3 reception control are possible when full-duplex
communications is used to communicate data between the Q series C24 and external devices. Do not use
DC1/DC3 control with half-duplex communications.
• The same data as the DC1 to DC4 codes cannot be included in the user data. To handle the same data as a
DC code as user data, do the following.
• Use DTR/DSR control.
• Change the DC code.
• Do not use the transmission control functions.
If the user data received from the external device includes the relevant DC code when DC1/DC3 reception control and
DC2/DC4 reception control are used, the Q series C24 uses the corresponding DC code control.
If the user data transmitted from the programmable controller CPU includes a DC code, it is sent unchanged.
210
CHAPTER 7 DATA COMMUNICATIONS USING DC CODE TRANSMISSION CONTROL
(6) Handling of ER (DTR) and DR (DSR) signals when DTR/DSR control is not used
When the DTR/DSR control function is not used, the Q series C24 handles the ER (DTR) and DR (DSR) signals
as described below.
• Leaves the ER (DTR) signal ON.
• Ignores the DR (DSR) signal ON/OFF state.
7
7.3 Precautions when Using the Transmission Control Functions
211
CHAPTER 8
DATA COMMUNICATIONS USING
HALF-DUPLEX COMMUNICATIONS
For data communications between the Q series C24 and an external device using the RS-232 interface, it is set so that
the Q series C24 and the external device do not transmit data at the same time.
The QJ71C24 (N)-R2 can be set for each interface.
When the Q series C24 is started, full-duplex communications is set. The user can change the communications
method to match the specifications of the external device.
Since half-duplex communications does not have to be set in the following cases, you do not have to read this section.
● When data is only transmitted or receive during non procedure protocol data communications.
● When it is designated in the external device that no data transmission is performed from the external device to the Q
series C24 unless so directed by the Q series C24.
8.1
Half-duplex Communications
The following describes the differences between full-duplex communications and half-duplex communications.
Since the Q series C24 uses the communications method designated by the user to control programmable controller
CPU communications, control by sequence program is unnecessary.
(1) Full-duplex communications
This communication method uses telephone conversation format image to communicate data with the external
device.
The Q series C24 can receive data while transmitting data to the external device.
It can also transmit data while receiving data from the external device.
External device
Data A-1
Programmable
controller CPU
Data A-2
Data B-2
Data B-1
(2) Half-duplex communications
This communications method uses transceiver conversation format image to communicate data with the external
device.
If the Q series C24 receives data from the external device while transmitting data to the external device, it
controls data transmission and reception according to "Simultaneous transmission priority/non-priority
designation".
The Q series C24 does not transmit data while it is receiving data from the external device.
External device
Programmable
controller CPU
212
Data A-2
Data A-1
Data B-1
Data B-2
CHAPTER 8 DATA COMMUNICATIONS USING HALF-DUPLEX COMMUNICATIONS
8.2
Data Transmission and Reception Timing
Half-duplex communications uses the Q series C24 RS-232 interface CD (DCD) and RS (RTS) signals to control
communications.
If the external device can transmit and receive data according to ON/OFF of the Q series C24 RS (RTS) and CD
(DCD) signals as shown below, half-duplex communications is possible.
• RS (RTS) signal: The Q series C24 turns ON/OFF this signal as shown below. When data is transmitted from
the Q series C24, this signal is turned ON. When transmission is complete, this signal is turned OFF.
• CD (DCD) signal: Turn ON/OFF this signal using the external device as shown below. To transmit data from
the external device, turn ON this signal. When transmission is complete, turn OFF this signal.
The following describes the half-duplex communications data transmission and reception timings by Q series C24 CD
(DCD) signal and RS (RTS) signal.
(1) Timing when transmitting data from external device
Transmit data by controlling the Q series C24 CD (DCD) signal according to the "simultaneous transmission
priority/non-priority designation" registered in "Transmission control and others system setting" screen of GX
Configurator-SC.
(a) When Q series C24 is designated "priority"
Terminate data
transmission.
Data A
External device
Programmable
controller CPU
8
Data B
Data C
8.2 Data Transmission and Reception Timing
Since the Q series C24
has priority, it continues
to transmit even if the
CD(DCD) signal is
turned ON.
Data C
SD(TXD) (Send Data)
RS(RTS)
(Send Request)
Retransmission
Data B
Store this data at the
external device.
4)
1)
5)
CS(CTS)
(Send possible)
CD(DCD)
(Data Carrier Detect)
RD(RXD)
(Receive Data)
2)
The Q series C24
ignores the receive
Data A
data. (*1)
3)
Data B
Data B
1) If the RS (RTS) signal is OFF, turn ON the CD (DCD) signal. If the RS (RTS) signal is ON, wait until it is
turned OFF, then turn ON the CD (DCD) signal.
2) Transmit data after turning ON the CD (DCD) signal.
3) After data transmission is complete, turn off the CD (DCD) signal.
4) If the RS (RTS) signal is turned ON during data transmission, terminate data transmission and turn OFF the
CD (DCD) signal and perform data reception processing. (Simultaneous transmission generated)
5) After transmission from the Q series C24 is complete, retransmit all the data terminated at step 4.
*1
Take the following measures between the communicating devices as a countermeasure against ignoring of the receive
data by the Q series C24.
• Transmit and receive a response message in reply to data transmission
• Time-out check of the response message and data transmission due to time-out error (external device side).
213
(b) When Q series C24 is designated "non-priority"
Continue data
transmission.
Data B
Data A
External device
Programmable
controller CPU
Data C-1
SD(TXD) (Send Data)
RS(RTS)
(Send Request)
Data C-2
Data C-1
Since the Q series C24
does not have priority,
when the CD(DCD) signal
is turned ON, it terminates
transmission.
Retransmission
*1
Data C-2
4)
1)
CS(CTS)
(Send Possible)
CD(DCD)
(Data Carrier Detect)
RD(RXD)
(Receive Data)
5)
2)
The Q series C24 stores
the receive data.
Data A
3)
Data B
The contents of steps 4 and 5 below are different from those of Page 213, Section 8.2 (1) (a).
1) If the RS (RTS) signal is OFF, turn ON the CD (DCD) signal. If the RS (RTS) signal is ON, wait until it is
turned OFF, then turn ON the CD (DCD) signal.
2) Transmit data after turning ON the CD (DCD) signal.
3) After data transmission is complete, turn off the CD (DCD) signal.
4) Keep transmitting data from the external device to the Q series C24 even if the RS (RTS) signal is turned ON
during data transmission. (Simultaneous transmission generated)
5) After transmission from the external device is complete, data is transmitted from the Q series C24 to the
external device. ( Page 215, Section 8.2 (2))
*1
For transmission data, see Page 215, Section 8.2 (2).
Remark
When using the DTR/DSR transmission control function described in Page 203, CHAPTER 7, transmit data from the
external device to the Q series C24 as shown below in both cases Page 213, Section 8.2 (1) (a) and Page 214, Section 8.2
(1) (b).
• When the Q series C24 ER (DTR) signal is turned OFF, terminate data transmission.
• When the Q series C24 ER (DTR) signal is turned ON after data transmission is terminated, restart data
transmission (transmit from the terminated data).
214
CHAPTER 8 DATA COMMUNICATIONS USING HALF-DUPLEX COMMUNICATIONS
(2) Timing when data is transmitted from the Q series C24
The Q series C24 RS (RTS) signal is controlled and data is transmitted according to the "simultaneous
transmission priority/non-priority" value registered in "Transmission control and others system setting" screen of
GX Configurator-SC.
(a) When Q series C24 is designated "priority"
Terminate data
transmission
External device
Programmable
controller CPU
Data A
Send
request
SD(TXD) (Send Data)
Retransmission
Data C-1
Data B
Send
request
Time for
transmitting
2 characters
Data A
1)
Data C
3)
Since the Q series C24
has priority, it continues
to transmit even if the
Store this data at the
CD(DCD) signal is
external device.
turned ON.
Data B
2)
RS(RTS)
(Send Request)
5)
CS(CTS)
(Send Possible)
4)
CD(DCD)
(Data Carrier Detect)
CD check
8
Data C
Data C-1
The Q series C24 ignores
the receive data. (*1)
The Q series C24
stores the receive data.
1) When transmitting data, check the Q series C24 CD (DCD) signal. If the CD (DCD) signal is OFF, turn on the
Q series C24 RS (RTS) signal. If the CD (DCD) signal is ON, wait until it is turned OFF, then turn ON the RS
(RTS) signal.
2) Transmit the data after turning ON the RS (RTS) signal.
3) After data transmission is complete, turn off the RS (RTS) signal.
4) Keep transmitting data from the Q series C24 to the external device even if the CD (DCD) signal is turned
ON during data transmission. (Simultaneous transmission generated)
5) After transmission from the Q series C24 is complete, transmit all the data terminated at step 4 from the
external device to the Q series C24.
*1
Take the following measures between the communicating devices as a countermeasure against ignoring of the receive
data by the Q series C24.
• Transmit and receive a response message in reply to data transmission
• Time-out check of the response message and data transmission due to time-out error (external device side).
215
8.2 Data Transmission and Reception Timing
RD(RXD)
(Receive Data)
CD check
CD check
(b) When Q series C24 is designated "non-priority"
Continue data transmission.
Data C
External device
Programmable
controller CPU
Send
request
SD(TXD) (Send Data)
Data B
Data A
Send
request
Time for
transmitting
2 characters
Data A
1)
Data B
Since the Q series C24
does not have priority, when
the CD(DCD) signal is turned ON
it terminates transmission.
3)
Data B
(*2)
Data B
2)
RS(RTS)
(Send Request)
CS(CTS)
(Send Possible)
4)
CD(DCD)
(Data Carrier Detect)
CD check
CD check
CD check
RD(RXD)
(Receive Data)
5)
CD check
Transmission wait time (*1)
Data C
The Q series C24 stores the receive data.
The contents of steps 4 and 5 below are different from those of Page 215, Section 8.2 (2) (a).
1) When transmitting data, check the Q series C24 CD (DCD) signal. If the CD (DCD) signal is off, turn on the
Q series C24 RS (RTS) signal. If the CD (DCD) signal is ON, wait until it is turned OFF, then turn ON the RS
(RTS) signal.
2) Transmit the data after turning ON the RS (RTS) signal.
3) After data transmission is complete, turn off the RS (RTS) signal.
4) If the CD (DCD) signal is turned on during data transmission, terminate data transmission and turn off the RS
(RTS) signal and perform the data receive processing. (Simultaneous transmission generated)
5) After transmission from the external device is complete, transmit the data terminated at step 4 from the
beginning or from the last data transmitted.*2
*1
*2
The data size set to "Simultaneous transmission priority/non-priority" by GX Configurator-SC is not transmitted.
Transmit from the beginning or from the data transmitted immediately before transmission was terminated, according to
the contents set to "Retransmission time transmission method by GX Configurator-SC".
Remark
When using the DTR/DSR transmission control function described in Page 203, CHAPTER 7, transmit data from the Q
series C24 to the external device as shown below in both cases Page 215, Section 8.2 (2) (a) and Page 216, Section 8.2 (2)
(b) above.
• When the Q series C24 DR (DSR) signal is turned OFF, terminate data transmission.
• When the Q series C24 DR (DSR) signal is turned on after data transmission is terminated, restart data
transmission (transmit from the terminated data).
216
CHAPTER 8 DATA COMMUNICATIONS USING HALF-DUPLEX COMMUNICATIONS
8.3
Changing the Communication System
To change the data communication mode from full-duplex communication to half-duplex communication, registration
on the GX Configurator-SC's "Transmission control and others system setting" screen is required.
The following explains setting items for changing the communication system.
(1) RS-232 communication system designation
Designate either full-duplex or half-duplex communication.
(2) Simultaneous transmission priority/non-priority designation
When the Q series C24 and the external device start data transmission simultaneously in half-duplex mode,
designate whether to continue (priority) or stop (non-priority) transmission from the Q series C24.
Designated values "1" to "255" for setting "non-priority" will be the transmission wait time that elapses from when
the resumption of data transmission becomes available until data is actually sent.
(3) Retransmission time transmission method designation
When "half-duplex communication" and "non-priority" are set as indicated above, this setting becomes valid.
When the Q series C24 and the external device begin transmission simultaneously, if the Q series C24 stops and
then restarts transmitting, designate whether the stopped message will be transmitted from the beginning
("resend") or whether transmission will continue after the stopped message ("not resend").
8
(4) RS-232 CD terminal check designation
When using half-duplex communication, set the "CD terminal check designation" to on.
8.3 Changing the Communication System
217
8.4
Connector Connections for Half-duplex
Communications
The following explains the functions of the connector that connects the Q series C24 and external device when halfduplex communications are used.
Connect the Q series C24 and external device based on (1) and (2) below.
(1) Connect the Q series C24 RS (RTS) signal to one of the external device halfduplex communications signals (CS (CTS), DR (DSR), or CD (DCD) signal).
(2) Connect the Q series C24 CD (DCD) signal to one of the external device halfduplex communications signals (RS (RTS) or ER (DTR) signal).
(3) The half-duplex communications described in this section cannot be
performed when an RS-232 and RS-422 converter is used.
(Connection example)
Q series C24
218
Cable connection and
signal direction
External device
Signal name
Pin No.
CD(DCD)
1
CD(DCD)
RD(RXD)
2
RD(RXD)
SD(TXD)
3
SD(TXD)
ER(DTR)
4
ER(DTR)
SG
5
SG
DR(DSR)
6
DR(DSR)
RS(RTS)
7
RS(RTS)
CS(CTS)
8
CS(CTS)
CI(RI)
9
Signal name
CHAPTER 8 DATA COMMUNICATIONS USING HALF-DUPLEX COMMUNICATIONS
8.5
Half-duplex Communications Precautions
The following describes the precautions to be observed when using half-duplex communications.
(1) Half-duplex communications system configuration and functions
Half-duplex communications is possible only with a system that connects the programmable controller CPU and
external device in a 1: 1 configuration.
(Half-duplex communications
can be designated)
(Half-duplex communications
cannot be designated)
External device
External device
RS-232
RS-232
CPU
CPU
QC24
CPU
CPU
RS-422/485
(2) Agreement and confirmation between external device and programmable
controller CPU
Agree and confirm the following items between the external device and the programmable controller CPU.
• Whether or not half-duplex communications can be performed by Q series C24 RS (RTS) signal and CD
8
(DCD) signal.
• Q series C24 RS (RTS) signal and CD (DCD) signal ON/OFF timing.
• RS-232 cable connection method.
(3) Transmission control
When the transmission control functions described in Page 203, CHAPTER 7 are used, DC code control
DC1/DC3 transmission control and DC1/DC3 reception control cannot be used with half-duplex communications.
Therefore, do not designate them.
219
8.5 Half-duplex Communications Precautions
• Q series C24 and external device data transmission timing.
CHAPTER 9
CONTENTS AND REGISTRATION OF
THE USER FRAMES FOR DATA
COMMUNICATION
User frames are used to register some, or all, of the messages exchanged between an external device and the Q
series C24 in advance and use them to check the send data or receive data.
The following functions can use Q series C24 user frames to transmit and receive data.
• MC protocol on-demand function. ( Page 243, CHAPTER 10)
• Non procedure protocol data transmit and receive functions. ( Page 252, CHAPTER 11)
Data can be transmitted and received by registering the corresponding user frames to the Q series C24 in advance to
match the data contents that are transmitted and received between the external device and the Q series C24.
This chapter explains the data that can be registered, the data contents that are transmitted and received, and
registering to the Q series C24 of user frames that can be used in data communications with the external device.
See Page 243, CHAPTER 10 and Page 252, CHAPTER 11 for a description of how each data communications
function uses the user frames.
9.1
User Frame Types and Contents During Communication
This section explains the kinds of user frames handled by the Q series C24 and the data contents that are transmitted
and received.
The following two kinds of user frames are available. Either kind can be used.
User frame *1
User frame
(Generic term)
Default registration frame *2
*1
*2
220
Frame described in  Page 221, Section 9.1.1
Frame described in  Page 230, Section 9.1.2
CHAPTER 9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA COMMUNICATION
9.1.1
User frames to be registered and used by the user
9
The following explains the registered data, data contents that are transmitted and received, and how the Q series C24
handles user frames registered the Q series C24 Flash ROM or buffer memory by the user.
(1) General description
User frames registered by the user are frames that contain arbitrary data that matches the specifications of the
external device. The data contents are selected by the user.
(2) User frame registering
(a) Up to 231 user frames can be registered, read, and deleted at the Q series C24.
• Q series C24 flash ROM
(number that can be registered: Maximum 200, frame No.: 3E8H to 4AFH)
• Q series C24 buffer memory
(number that can be registered: Maximum 31, frame No.: 8001H to 801FH)
(b) Up to 80 bytes (80 en characters) of data can be registered as 1 user frame.
(c) User frames can include data for handling the variable data (sum check code, Q
series C24 station No., etc.) shown in (4) as a part of user frames.
(d) User frames can be overwritten to the Q series C24 buffer memory. (The old
contents are destroyed.)
usage.
• After data communication has started, register the user frames without changes to buffer memory and use.
(Frame No: 3E8H to 4AFH)
• After data communication has started, register the user frames with changes to buffer memory and use.
(Frame No: 8001H to 801FH)
(3) Data that can be registered as user frame
Up to 80 bytes of data can be registered by combining 1 byte of register code 01H to FEH data and 2 bytes of
register code FFH + 00H to FFH + FFH data.
(a) One byte of register code (01H to FEH) data
This is the register code for transmitting and receiving the register code (01H to FEH) data.
(b) Two bytes of register code (FFH + 00H) to (FFH + FFH) data
This is the register code for transmitting and receiving the variable data (Sum check code, Q series C24 station
No., etc.) shown in (4) as part of the user frame.
FFH is the register code of the first byte for handling variable data.
221
9.1 User Frame Types and Contents During Communication
(e) The registration destination for the user frame can be divided into the following
(4) Variable data
"Variable data" is the generic term for the following data.
These variable data can be handled as part of a user frame.
• Sum check code whose objective is an arbitrary range in the transmit and receive messages.
• Horizontal parity code whose objective is a determined range in the transmit and receive messages.
• Two's complement sum check code whose objective is a determined range in the transmit and receive
messages.
• Q series C24 station No.
• One byte data in data transmission (NULL: Code 00H) One byte of arbitrary data in data reception. (Used to
handle an arbitrary byte of data as part of the user frame during receiving check by the Q series C24.)
(a) Variable data designation method
Variable data is designated by combining write code FFH and the data codes shown in the table below.
The sum check code, Q series C24 station No., and other variable data can be handled according to FFH of the
first byte and 00H to FFH of the second byte.
FFH
00H to FFH
2nd byte
1st byte
222
CHAPTER 9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA COMMUNICATION
(b) Variable data designation contents, data contents transmitted and received, and
handling by the Q series C24
9
The table below shows the register codes (FFH+00H) to (FFH + FFH) combinations for handling variable data,
the data contents that are transmitted and received, and how the Q series C24 handles the data.
Combinations other than those listed in the table cannot be registered.
Changeable data
register code
1st byte
2nd byte
00H
FFH
Data contents transmitted and received/Q series C24 handling
Transmission: Transmits the data code 00H (NUL) data (1 byte).
Reception: Skips the given part (1 byte) of the receive user frame. (Skips the check and performs
receive processing.)
01H
Transmits and receives the station No. set in the GX Developer switch setting as 1-byte binary code
data (00H to 1FH).
04H*1
Transmits and receives the horizontal parity code in the calculation range using 1 byte of binary code
data
05H*1
Transmits and receives the horizontal parity code in the calculation range using 2-byte ASCII code
data
0AH*1
Transmits and receives the horizontal parity code in the calculation range using 1 byte of binary code
data
0BH*1
Transmits and receives the horizontal parity code in the calculation range using 2-byte ASCII code
data
11H*1
17H*1
E5H*1
*1
EBH
Transmits and receives the two's complement sum check code in the calculation range.
Transmits and receives the sum check code in the calculation range.*2 (Except the last one frame)
Calculation
range*3
Detailed
explanation
1)

2)
Range 1
3)
Range 2
Range 1
Range 2
4)
Range 3
6)
Range 4
7)
EEH
F0H
Range 1
F3H
F4H
Transmits and receives the sum check code in the calculation range.*2
F6H
5)
Range 2
F7H
F9H
FFH
*1
*2
*3
Transmits and receives the register code FFH data (1 byte).


For usage of the register code, there are restrictions on versions of QJ71C24N(-R2/R4) and QJ71C24(-R2).
Refer to the Q Corresponding Serial Communication Module User's Manual (Basic) for how to check the version.
During data communication using a user frame that handles the last frame, the contents of the "sum check code" set in
the transmission setting using the GX Developer switch setting will be ignored.
Calculation ranges for the register codes
223
9.1 User Frame Types and Contents During Communication
F1H
(Calculation range when transmitting data)
Range 4
Range 3
User frame
(1st)
User frame
(2nd)
User frame
("n-1"th)
User frame
("n"th)
Register
code
FFH
H
Range 1
Range 2
(Calculation range when transmitting data)
(Calculation range when receiving data)
Range 4
Range 3
User frame
(First frame)
Arbitrary data
User frame
(Last frame)
Register
code
FFH
H
Range 1
Range 2
(Calculation range when receiving data)
[Range 1]
• When transmitting: Calculation includes everything from the data following the first frame (first one frame
only when multiple user frames have been specified) to the one immediately before the register code.
(Except the additional code data of the transparent code designation shown in Chapter 12)
• When receiving: Calculation includes everything from the data following the first frame to the one
immediately before the register code. (Except the additional code data of the transparent code designation
shown in Chapter 12)
[Range 2]
• When transmitting/receiving: Calculation includes everything from the head of the message to the one
immediately before the register code. (Except the additional code data of the transparent code designation
shown in Chapter 12)
224
CHAPTER 9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA COMMUNICATION
[Range 3]
• When transmitting: Calculation includes everything from the data following the first frame (user frame (1st)
when multiple frames have been specified) to the frame preceding the last one (user frame ("n"th) when
9
there are multiple frames specified). (Except the additional code data of the transparent code designation
shown in Chapter 12)
• When receiving: Calculation includes everything from the data following the first frame to the frame
preceding the last one. (Except the additional code data of the transparent code designation shown in
Chapter 12)
[Range 4]
• When transmitting/receiving: Calculation includes everything from the head of the message to the frame
preceding the last one. (Except the additional code data of the transparent code designation shown in
Chapter 12)
9.1 User Frame Types and Contents During Communication
225
1) Q series C24 processing corresponding to register codes FFH and 00H
The following uses an example to describe the processing performed by the Q series C24 when it receives a
user frame part corresponding to register codes FFH and 00H.
Assume that a user frame containing the data codes 02H, FFH, 00H, and 3BH was set as receive user frame
No. 3EAH.
• When the Q series C24 receives the 3 bytes of data "STX, arbitrary data (1 byte), ; ", it processes them as
if user frame No. 3EAH was received.
• The Q series C24 does not check the 2 bytes described above.
Receive data
Receive data
code
S
T
X
1
:
A
B
02H 31H 3BH 41H 42H
Check
If the 02H and 3BH data parts match, they are processed as if
user frame No. 3EAH mentioned above was received
2) Transmission/reception data corresponding to register codes FFH and 01H
The Q series C24 transmits and receives the user frame part corresponding to register codes FFH and 01H by
representing the station No. set in the GX Developer switch setting as 1-byte binary data.
See the first frame part shown in the illustration in item 3 for an example.
3) Transmission/reception data corresponding to register codes FFH + 04H, FFH + 05H, FFH + 0AH, and FFH
+ 0BH.
• For FFH + 04H and FFH + 0AH: The horizontal parity code that calculates the range for the
transmission/reception data (message) is expressed as 1 byte of binary data and then transmitted and
received. The difference between FFH + 04H and FFH + 0AH is the difference in the calculation range.
• For FFH + 05H and FFH + 0BH: The horizontal parity code that calculates the range for the
transmission/reception data (message) is expressed as 2-byte ASCII code data and then transmitted and
received from the upper digit. The difference between FFH + 05H and FFH + 0BH is the difference in the
calculation range.
Examples of the transmission and reception data arrangement of the horizontal parity codes are shown below.
(One first frame and one last frame each)
For register code FFH + 04H
User frame
register code
Transmission/
reception data
code
226
02H FFH+01H 3BH
S Station
T No.
X
02H
00H
User frame
(last frame)
Arbitrary data
User frame
(first frame)
;
03H FFH+04H 0DH 0AH
1
2
3
4
E
T
X
3BH 31H 32H 33H 34H 03H
Calculation
range
Horizontal
parity
code
07H
C
L
R
F
0DH 0AH
CHAPTER 9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA COMMUNICATION
9
For register code FFH + 05H
User frame
register code
Transmission/
reception data
code
02H FFH+01H 3BH
S Station
T No.
X
02H
00H
User frame
(last frame)
Arbitrary data
User frame
(first frame)
03H FFH+05H 0DH 0AH
;
1
2
3
E
T
X
4
Horizontal
parity
code
C
L
R
F
3BH 31H 32H 33H 34H 03H 30H 37H 0DH 0AH
Calculation
range
• How to calculate the horizontal parity code
This is a numeric value obtained by calculating the XOR for the subject data and then converting it to ASCII
code.
(In the case of the example)
"1" (31H) 0011 0001
XOR
"2" (32H)
0011 0010 = 0000 0011
XOR
"3" (33H)
0011 0011 = 0011 0000
XOR
0011 0100 = 0000 0100
"4" (34H)
XOR
0000 0011 = 0000 0111
"ETX" (03H)
4) Transmission/reception data corresponding to register codes FFH+11H and FFH+17H
The two's complement sum check code that calculates the subject range for transmission/reception data
(message) is expressed as two-character data in ASCII code, then transmitted and received from the upper
digit.
The difference between (FFH+11H) and (FFH+17H) is the difference between the calculation ranges.
An example of the contents (arrangement) of the transmission and reception of the two's complement sum
check code is shown below.
Arrangement of data transmitted and received with the register code FFH+17H (one first frame and one
last frame)
User frame register code
02H
00H
;
User frame
(last frame)
03H FFH+17H 0DH 0AH
02H FFH+01H 3BH
S Station
T No.
X
Transmission/reception
data code
Arbitrary data
1
2
3
4
E
T
X
Two's complement
sum check code
User frame
(first frame)
C
L
R
F
3BH 31H 32H 33H 34H 03H 46H 36H 0DH 0AH
Calculation range
227
9.1 User Frame Types and Contents During Communication
"0"
"7"
(30H) (37H)
ASCII code
• How to calculate the two's complement sum check code
The lower 1 byte of the value obtained by adding the subject data as binary data is converted to a two's
complement, then converted to a hexadecimal ASCII code.
(In the case of the example)
02H+00H+3BH+31H+32H+33H+34H+03H=10AH
Data in the subject range are added
as binary data (hexadecimal)
00001010
The lower 1 byte of the above numeric value
is expressed as a binary number
11110110
Reversed, then converted to a two's complement
F6H
Converted to a hexadecimal ASCII code
"F"
"6"
(46H) (36H)
5) Transmission/reception data corresponding to register codes FFH+EEH to FFH+F9H
The sum check code that calculates the subject range for transmission/reception data (message) is expressed
as the binary code/ ASCII code data listed below, then transmitted and received.
Register code
Data contents transmitted and received
FFH + EEH or FFH + F4H
The lower 2 bytes of the calculated sum check code are transmitted and received as 2-byte binary
code data.
FFH + F0H or FFH + F6H
The lower byte of the calculated sum check code is transmitted and received as 1-byte binary code
data.
FFH + F1H or FFH + F7H
The lower byte of the calculated sum check code is converted to 2-digit ASCII code, then transmitted
and received.
FFH + F3H or FFH + F9H
The lower 4 bits of the calculated sum check code is converted to 1-digit ASCII code, then transmitted
and received.
An example of the contents (arrangement) of the transmission and reception of the sum check code is given
below.
Arrangement of data transmitted and received (one first frame and one last frame)
Arbitrary data
User frame
(first frame)
User frame register code
02H FFH+01H 3BH
S Station
T No.
X
Transmission/reception
data code
02H
00H
;
User frame
(last frame)
03H FFH+F1H 0DH 0AH
A
E Sum
1 (12ABH) T check
X code
C
L
R
F
3BH 41H 31H ABH 12H 03H 32H 01H 0DH 0AH
Range 1
Range 2
• How to calculate the sum check code and data contents transmitted and received
This is a numeric value obtained by adding data in the above range as binary data.
(In the case of the example [Range 1]) (H) (L)
41H+ 31H + ABH + 12H + 03H = 0132H
Register code
228
Data contents transmitted and received (arrangement)
FFH + EEH
01H and 32H are transmitted and received, beginning from 32H.
FFH + F0H
32H is transmitted and received.
FFH + F1H
"3" and "2" are transmitted and received, beginning from "3."
FFH + F3H
"2" is transmitted and received.
CHAPTER 9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA COMMUNICATION
(In the case of the example [Range 2]) (H) (L)
9
02H + 00H + 3BH + 41H + 31H + ABH + 12H + 03H = 016FH
Register code
Data contents transmitted and received (arrangement)
FFH, F4H
01H and 6FH are transmitted and received, beginning from 6FH.
FFH, F6H
6FH is transmitted and received.
FFH, F7H
"6" and "F" are transmitted and received, beginning from "6".
FFH, F9H
"F" is transmitted and received.
6) Transmission/reception data corresponding to register code FFH+E5H
The sum check code resulted from the calculation of the transmission/reception data (message) codes except
the first one frame and last one frame is expressed as the ASCII code data and transmitted or received.
• How to calculate the sum check code
Lower one byte of the sum check value calculated is converted into 2-digit ASCII code data, and used for data
transfer.
Arrangement of data when received
User frame
(First frame)
User frame
(Last frame)
Arbitrary data
User frame register
code
02H
S
T
X
Transmission/
reception data code
02H
03H FFH+E5H
Station
No.
E Sum
T check
X code
Read data
0
1
1
7
30H
31H
31H
37H
7
0
37H 30H
03H
3
0
33H
30H
Calculation range
7) Transmission/reception data corresponding to register code FFH+EBH
The sum check code resulted from the calculation of the transmission/reception data (message) codes,
including the first one frame and excluding the last one frame, is expressed as the ASCII code data and
transmitted or received.
• How to calculate the sum check code
Lower one byte of the sum check value calculated is converted into 2-digit ASCII code data, and used for data
transfer.
Arrangement of data when received
User frame
(First frame)
User frame
(Last frame)
Arbitrary data
User frame register
code
02H
S
T
X
03H FFH+EBH
Station
No.
0
Transmission/
reception data code
02H
30H
E
T
X
Read data
1
1
7
31H
31H
37H
7
0
37H 30H
03H
Sum
check
code
3
2
33H
32H
Calculation range
02H+30H+31H+31H+37H+37H+30H
=132H
229
9.1 User Frame Types and Contents During Communication
30H+31H+31H+37H+37H+30H
=130H
9.1.2
Default registration frame (read only)
This frame is registered to the Q series C24 in advance and can be used in the same way as the other user frames.
(1) Overview
The default registration frame is registered in the OS ROM of the Q series C24. The following table lists one-byte
data (codes: 01H to FEH) to a maximum of five-byte data, which is registered in the frames and can be used for
read-only (frame numbers: 1H to 3E7H).
Each of these frames is treated as an user frame.
(2) Default registration frame write data and data contents that are transmitted
and received
The following lists the codes of the register data and the data contents that are transmitted and received.
Default registration frame No.
(Hexadecimal (decimal))
Register data code (1st byte to nth
byte)
1H (1)
01H
2H (2)
02H


FEH (254)
FEH
Registered bytes
count
Frame byte
count
Data contents transmitted and
received
data contents
(Data codes shown at the left)
1
1
STX

(Data codes shown at the left)
FFH (255)

100H (256)
00H
1

101H (257)
FFH
1
102H (258)
0DH, 0AH
103H (259)
10H, 02H
104H (260)
10H, 03H
1
(For variable data designation)
NUL
(Data codes shown at the left)
CR, LF
2
2
DLE, STX
DLE, ETX
105H (261)
00H, FEH
2
2
(Data codes shown at the left)
106H (262)
00H, 00H, FEH
3
3
(Data codes shown at the left)
107H (263)
03H, FFH, F1H
3
2
ETX, Sum check code*1
108H (264)
03H, FFH, F1H, 0DH, 0AH
5
4
ETX, sum check code, CR, LF*1
(None)



2
1
109H (265)

10DH (269)
10EH (270)
FFH, EEH
110H (272)
FFH, F0H
111H (273)
FFH, F1H
113H (275)
FFH, F3H
114H (276)
FFH, F4H
116H (278)
FFH, F6H
117H (279)
FFH, F7H
119H (281)
FFH, F9H
11FH (287)
FFH, FFH
Sum check code*1
Register code FFH data (1 byte)
120H (288)

(None)



3E7H (999)
*1
230
The combination of FFH,
H in the register code is used to handle variable data (sum check code, Q series C24
station No., etc.) as part of the user frame. The data contents that are transmitted and received and the byte count
depend on the code combined with register code FFH. See Page 221, Section 9.1.1 (1) for the register code
combinations that can be handled as variable data and the data contents that are transmitted and received.
CHAPTER 9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA COMMUNICATION
9.2
Transmission/Reception Processing Using User Frame
Register Data
9
The following explains how the Q series C24 transmits and receives using user frame register data.
The Q series C24 checks the transmission/reception of following data, using registered data.
(1) Transmission
(a) If user frame transmission is designated, the user frame is converted, or not
converted, from ASCII to BIN data and transmitted, depending on the data
communications protocol, ASCII-BIN conversion designation, and user frame No.
designation, based on the following data as the send data of the given part.
• Register data code 01H to FEH 1-byte data register part
Q series C24 transmission is based on the register code (01H to FEH) data.
Register the data codes 03H, 0DH, 0AH as user frame No. 3E8H: When user frame No. 3E8H is
designated during data transmission, if ASCII-BIN conversion is disabled, the Q series C24 transmits the
data codes 03H, 0DH, 0AH (ETX, CR, LF) as the send data of the given user frame part. If ASCII-BIN
conversion is enabled, the Q series C24 converts each of the data above to 2-character ASCII code data
and transmits.
Part that designated user frame
No. 3E8H (Added by the Q series C24)
A
B
1
to
2
41H 42H 31H 32H
C
L
R
F
(When ASII-BIN conversion disabled)
(89ABH)
ABH 89H 03H 0DH 0AH
• Register data code FFH + 00H to FFH 2-byte data register part
The Q series C24 transmission is based on the variable data corresponding to the combination of the register
codes FFH and 00H to FFH.
For example, if sum check code is registered, the Q series C24 will calculate and transmit the sum check code.
If the Q series C24 station No. is registered, the station No. set in the Q series C24 is transmitted.
Register the data codes 03H, FFH, F0H, 0DH, 0AH as user frame No. 3E9H: If ASCII-BIN conversion is
disabled, the Q series C24 transmits the calculated sum check code as the send data of that user frame
part. If ASCII-BIN conversion is enabled, the Q series C24 converts the calculated sum check code to 2
characters/byte ASCII code data and transmits.
Part that designated user frame
Data designated by sequence
program
A
B
1
2
41H 42H 31H 32H
to
(89ABH)
E
T
X
Sum check
code
No. 3E9H (Added by the Q series C24)
C
L
R
F
(When ASII-BIN conversion disabled)
ABH 89H 03H 12H 0DH 0AH
Calculated by the Q series C24
231
9.2 Transmission/Reception Processing Using User Frame Register Data
E
T
X
Data designated by sequence
program
Remark
With a multidrop link, the user frame includes data that identifies which station transmitted the message to the external
device to facilitate generation of arbitrary send data.
External
device
Data that identifies the transmitting station
to the external device
S
L
T 1 A ; A B C 1 2 3 ; C
R F
X
When message transmitted from the station
No.1 Q series C24
Arbitrary data
"ABC123" … Data designated to the station
No.1 Q series C24 send data
designation area.
User frame
CPU C24
(0)
CPU C24
(1)
CPU C24
(5)
( ): Station No.
Data when transmitting
a frame written to eachQ
series C24 for transmission
S
T 0 A ;
X
S
T 1 A ;
X
S
T 5 A ;
X
C L
; R F
C L
; R F
C L
; R F
C24: Q series C24, QC24(N)
232
CHAPTER 9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA COMMUNICATION
9
(2) Reception
(a) When setting for reception by user frame is performed, and the first frame is set, the
Q series C24 receives the message when it receives data with the same contents as
the designated first frame.
If the last frame is set, when the Q series C24 receives data with the same contents as the designated last
frame, it sends a reception data read request to the programmable controller CPU.
(b) The following describes the Q series C24 receive processing using register data.
• Register data code 01H to FEH 1-byte data register part
The Q series C24 receives and checks if the received data is data of the same code (01H to FEH) as the
registered code.
Register the data codes 03H, 0DH, and 0AH as user frame No. 3E8H: When user frame No. 3E8H is set
as data receive, the Q series C24 receives and checks data codes 03H, 0DH, 0AH (ETX, CR, LF) as the
receive data of that user frame part.
E
T
X
Arbitrary data area
Programmable
controller CPU
Q series C24
Buffer memory
4241H
A
B
1
2
3
4
(1234H)
L
R
F
(89ABH)
41H 42H 31H 32H 33H 34H 34H 12H ABH 89H 03H 0DH 0AH
(Receive data
storage area)
Reception data
read request
C
When the Q series C24 receives the data,
it performs a Reception data read request
to the programmable controller CPU
89ABH
The Q series C24 receives and checks if the received data is variable data corresponding to the combination of
the register codes FFH and 00H to FFH.
For example, if a sum check code is registered, the Q series C24 calculates the sum check code from the
receive data and checks if it is the same as the received sum check code. If the two codes are not the same,
the Q series C24 performs error processing.
If the Q series C24 station No. is registered, the Q series C24 checks if the received station No. is the same as
the station No. set in the Q series C24. If the station Nos. are not the same, the Q series C24 processes the
data as if normal data was received instead of an user frame.
Register the data codes 03H, FFH, F0H, 0DH, 0AH as user frame No. 3E9H: When user frame No. 3E9H
is set as a data receive frame, the Q series C24 calculates, receives, and checks the sum check code as
the receive data of that user frame part.
(c) The Q series C24 removes the user frame data from the received message.
(The programmable controller CPU cannot read this data.)
233
9.2 Transmission/Reception Processing Using User Frame Register Data
• Register data code FFH + 00H to FFH 2-byte data register part
Remark
With a multidrop link, if the receive user frame inherent to each Q series C24 is connected to the link in advance, the Q
series C24 of a given station will store only the arbitrary data area of the message transmitted by the external device to the
receive data storage area.
External
device
Data used by the external device
to indicate the transmission destination
S
Arbitrary
C L
T 5 A ; data area ; R F
X
CPU C24
(0)
CPU C24
(1)
Received by the station No.5 Q series C24.
CPU C24
(5)
(First frame)
S
T 0 A ;
X
S
T 1 A ;
X
S
T 5 A ;
X
(Last frame)
C L
; R F
C L
; R F
C L
; R F
Data when a receive
frame is received at
each Q series C24
( ): Station No.
C24: Q series C24, QC24(N)
234
CHAPTER 9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA COMMUNICATION
9.3
Precautions when Registering, Reading, Deleting and
Using User Frames
9
The following shows the precautions which should be observed when registering user frames and using registered
user frames to transmit data to and receive data correctly from the external device.
(1) Precautions when registering, reading or deleting user frames
(a) User frames can be registered using one of the following methods. However, an
user frame to be registered to the flash ROM could be registered by the utility
package (GX Configurator-SC) dedicated to the Q series C24 as much as possible.
• Registering via the utility package (GX Configurator-SC) for the Q series C24.
• Registering with the dedicated instruction "PUTE" from the programmable controller CPU.
• Registering from an external device with command "1610" through communication using the MC protocol.
(b) The following settings are required when registering or deleting user frames.
• Switch setting using GX Developer: Set the setting modification to Enable in the transmission setting.
• Settings via GX Configurator-SC: Set the flash ROM write allow/prohibit setting to Allow on the monitor/test
screen.
• To set from the programmable controller CPU, write "1" in the following buffer memory at the startup of the
Q series C24 (when the ready signal rises). Flash ROM write allow/prohibit designation area (address:
2000H)
(c) To register, read or delete user frames from the programmable controller CPU,
external device.
(d) An user frame having only a sum check code as changeable data cannot be
registered.
To register a sum check code, add arbitrary data.
(e) Register a receive user frame in the Q series C24 flash ROM.
(f) The changeable data (05H to F9H) can be specified at only one place in the last
frame.
235
9.3 Precautions when Registering, Reading, Deleting and Using User Frames
perform the operation while there is no data communication in progress with the
(2) Precautions when using user frames
(a) To send/receive data using the user frames, it is necessary to set the user frame
number to be used in the buffer memory prior to data transmission/reception
(receive user frames must be set at the startup of the Q series C24).
The user frame number to be used can be set from the programmable controller CPU. However, please try to
register frames using the utility package (GX Configurator-SC) of the Q series C24.
(b) Set the receive user frame number by the programmable controller CPU to show the
procedure to receive data.
Receive user frame data by performing the following operations sequentially.
• If an user frame used in data reception was registered from programmable controller CPU, restart
programmable controller CPU.
• When starting the Q series C24, set the receive user frame No. to the buffer memory and write [1] to buffer
memory user frame use enable/disable designation area (addresses: ADH/14DH).*1
• After the value of the buffer memory user frame use enable/disable designation area changes to [2], start
receiving data.*1
• Check if the data from the external device was received normally.
*1
For details, refer to Page 252, CHAPTER 11.
(c) If the Q series C24 receives additional code data while receiving data with the non
procedure protocol, it does not assume that the last byte of data is the following
control data.
• Data received as user frame first frame, last frame ( Page 220, Section 9.1,  Page 231, Section 9.2)
• Receive complete code data
Therefore, do not set a user frame containing data receive additional code data as a non procedure protocol
receive user frame.
(d) The arbitrary data area of a message received from an external device cannot
include data with the same contents (same code) as the last frame.
User frame
(first frame)
Arbitrary
dat area
User frame
(last frame)
(e) In the following cases, set the data bit length of the transmission specification to 8
bits.
(It is set in the "transmission setting" of switch setting by GX Developer on the Q series C24 side.)
• When transmitting and receiving the sum check code of the variable data as binary data (Write code: FFH,
EEH/FFH, F0H/FFH, F4H/FFH, F6H)
• When transmitting and receiving a user frame containing data codes 80H to FFH
236
CHAPTER 9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA COMMUNICATION
9.4
Register/Read/Delete User Frames
9
The following explains registering, reading, and deleting user frames in the Q series C24 flash ROM or buffer memory.
When registering, reading and deleting the user frames in the flash ROM, try to register them using the utility package (GX
Configurator-SC) of the Q series C24.
This section explains how to register, read, or delete user frames from the programmable controller CPU.
(1) Type of user frames
Type
Default registration
frames
Data
communication
function
User frame No.
Registration destination
1H to 3E7H
(1 to 999)
ROM for the Q series C24 OS
3E8H to 4AFH*2
User frame
*1
Read enabled
Q series C24 flash ROM
(100 to 1199)*3
8001H to 801FH
Register/read/delete
enabled
Q series C24 buffer memory
(Addresses: 1B00H to 1FF6H)
(-32767 to -32737)*1
User frame for the programmable
controller CPU monitoring function
Remarks
B001 to B00AH, B061H,
B080H to B082H
Register/read/delete
disabled
ROM for the Q series C24 OS
*2
*3
(2) Devices that can register/read/delete user frames
Device that can register/read/delete
Type
User frame No.
Programmable controller
CPU
Register
Default registration frames
User frame
1H to 3E7H

3E8H to 4AFH

8001H to 801FH
User frame for the programmable
controller CPU monitoring function
Read
B001 to B00AH,
B061H,
B080H to B082H
 (FROM/TO)
Delete
External device
GX Configurator-SC
Register
Read
Delete




Register
Read
Delete




Conduct registering, reading, and deletion of the user frame from the sequence program when data communication is not
being conducted with external device.
237
9.4 Register/Read/Delete User Frames
Data contained in user frames used for registering and reading is arranged in the same way as data in user frames used
for registering in or reading to the flash ROM.
Use the arrangement described in this section as a reference, and register and read user frames. User frames can also
be registered in the buffer memory, but the user frame for the fixed format section should be registered in the flash ROM
whenever possible.
A user frame cannot be overwritten for registration. To reregister a user frame having the same number, first delete the
current user frame and then reregister.
Check the registration status of the user frame number from GX Configurator-SC.
(3) Buffer memory to use
Processing
Address
(Hexadecimal
(decimal))
Name
Stored value
2H (2)
Register/read/delete direction
0: No request
1: Register request
2: Read request
3: Delete request
3H (3)
Frame No. direction
0: No frame No.
1000 to 1199 (3E8H to 4AFH)
: Register/read/delete frame No.
4H (4)
Register/read/delete result storage
0: Normal completion
One or higher: Abnormal completion (error
code)
Write data byte count designation
( Page 238, Section 9.4 (3) (a))
0: Delete
1 to 80 (1H to C8H)
: Register data byte count
Flash ROM
access
5H (5)
Regist
er
Read
Delete












6H (6)

User frame
( Page 239, Section 9.4 (3) (b))
Data code of frame to be registered/deleted
Number of registered user frame storage
0: Not registered to Flash ROM
1 to 200 (1H to C8H)
: Number registered to Flash ROM
User frame registration status storage
( Page 239, Section 9.4 (3) (c))
(For registration No. check)
0: Given range not registered
One or higher: Registration status
2DH (45)
204H (516)
205H (517)

21DH (541)
Number of registered default registration frames storage (OS
ROM)
21EH (542)
1B00H (6912)
1B01H (6913)

n: Registration count ( Page 230,
Section 9.1.2)
Register data byte count designation
Registration
No.8001H
User frame storage
*40 words
1B28H (6952)
Register data byte count designation
1B29H (6953)
1B2AH (6954)

Registration
No.8002H
User frame storage
*40 words
1B51H (6993)
1B52H (6994)

to
(Register data byte count designation: 
Page 238, Section 9.4 (3) (a))
1 to 80 (1H to C8H)
: Register data byte count
(User frame storage.  Page 239,
Section 9.4 (3) (b))
Register frame data code
1FCDH (8141)
1FCEH (8142)
1FCFH (8143)

Register data byte count designation
Registration
No.80F1H
1FF6H (8182)
User frame storage
*40 words
* Register area for 31 frames
Read/write from programmable controller CPU
: Always performed, : Performed as required, : Unnecessary
(a) Registration data byte count designation area (Addresses: 5H, 1B00H, 1B29H,...,
1FCEH)
• Indicates the total number of bytes of register data of the user frame to be registered/read.
• Flash ROM access: During the register operation, the user registers the total number of bytes of register
data. During the read operation, the total number of bytes of registered data is stored.
• Buffer memory access: During the register operation, the user registers the total number of bytes of
register data.
238
CHAPTER 9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA COMMUNICATION
(b) User frame storage area (Addresses: 6H to 2DH, 1B01H to 1B28H, 1B2AH to
9
1B51H,...1FCFH to 1FF6H)
• During the register operation, the user sequentially stores the register data of the user frame to be
registered in (L) (H) order, beginning from the head area of the given area range.
• During the read operation, the register data of the registered user frame is stored with the same contents
as when registering.
Contents stored to user frame storage area when a user frame to transmit and receive ETX, sum check
code, CR, and LF (register codes: 03H, FFH, F1H, 0DH, 0AH) is registered to the Flash ROM.
Buffer memory
(H) (L)
Address
6H
7H
8H
Head data
FFH to 03H
0DH to F1H
00H to 0AH
Last data
(Part corresponding to write frame above)
(Data contents transmitted and received)
User frame
(first frame)
User frame register
code
Transmission/reception
data corresponding to
register code
Transmission/reception
data code
02H FFH,01H
S
T Station
X No.
02H
00H
Arbitrary data
3BH
;
User frame
(last frame)
03H FFH,F1H 0DH 0AH
E
A
1 (12ABH) T
X
Sum
check
code
C
L
R
F
3BH 41H 31H ABH 12H 03H 32H 01H 0DH 0AH
Sum check code
calculation range
The Q series C24 calculates
the programmable controller CPU
checksum.
• The registration status of user frames to the Flash ROM is stored as the values shown below.
• The contents of each area that indicates the registration status are shown below. The contents of the area
are indicated in one user frame No./1 bit form.
User frame No. 1015 (3F9H)
registration status
(H) Buffer memory
to
b8 b7
Address b15
0: Not registered 205H 0 0 0 0 0 0 1 1 0 0 0
1: Registered
206H 0 0 0 0 0 0 1 1 0 0 0
211H
User frame No. 1000 (3E8H)
registration status
(L)
to
b0
0 1 1 1 1 to 030FH
0 0 0 1 1 to 0303H
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 to 0000H
User frame No. 1199 (4AFH) registration
status (Subsequent bits are spares)
239
9.4 Register/Read/Delete User Frames
(c) User frame registration status storage area (Addresses: 205H to 21DH)
9.4.1
Registering user frames
The following shows an example of a sequence program when registering user frames in the Q series C24 flash ROM.
For details on the PUTE instruction, see Page 398, Section 17.7.
(When the Q series C24 I/O signals are X/Y80 to X/Y9F)
Data set for the program example are as follows:
Setting item
User frame No.
Registration data (10 bytes)
Setting data
3E8H
Binary
46H,39H,30H,30H,30H,30H,46H,46H,30H,30H
ASCII
F90000FF00
Registration request
Sets the registration request
Sets the frame number to be
registered
Sets the number of registration
data bytes
Sets the registration data
for the frame to be registered
in D4 to D8
Sets the flash ROM write allow
Executes user frame registration
Normal completion
Abnormal completion
● When registering a user frame in the flash ROM, to designate an user frame number that has already been registered,
delete the previously registered number and then reregister.
● The user should manage the number of total bytes for registered data.
● To check unregistered user frames, read the buffer memory (addresses: 205H to 21DH) indicated in Page 238, Section
9.4 (3).
● The SPBUSY instruction can be used to read the communication status by the dedicated instruction.
240
CHAPTER 9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA COMMUNICATION
9.4.2
Reading user frames
9
The following shows an example of a sequence program when reading user frames registered in the Q series C24
flash ROM.
For details on the GETE instruction, see Page 389, Section 17.5.
(When the Q series C24 I/O signals are X/Y80 to X/Y9F)
Read request
Sets the frame No. to be read
Sets the allowable number of data
to be read
Clears the device in which to store
the read user frame data
Executes user frame reading
Normal completion
Abnormal completion
● When an unregistered user frame number is designated, the operation will complete abnormally.
● When the total bytes of data registered in the frame to be read is unknown, read 40 words (80 bytes) by the dedicated
instruction.
9.4 Register/Read/Delete User Frames
● The SPBUSY instruction can be used to read the communication status by the dedicated instruction.
241
9.4.3
Deleting user frames
The following shows an example of a sequence program when deleting user frames registered in the Q series C24
flash ROM.
For details on the PUTE instruction, see Page 398, Section 17.7.
(When the Q series C24 I/O signals are X/Y80 to X/Y9F)
Deletes request
Sets the delete request
Sets the No. of the user frame to
be deleted
Sets a dummy number for
the allowable number of deletions
Set the flash ROM write allow.
Executes user frame deletion
Normal completion
Abnormal completion
● When an unregistered user frame number is designated, the operation will complete abnormally.
● The SPBUSY instruction can be used to read the communication status by the dedicated instruction.
242
CHAPTER 10 ON-DEMAND DATA COMMUNICATIONS USING USER FRAMES
CHAPTER 10 ON-DEMAND DATA
COMMUNICATIONS USING USER
FRAMES
10
During communications between external device and programmable controller CPU using the MC protocol, ondemand data can be transmitted from the programmable controller CPU to the external device by on-demand function
using user frames.
This chapter explains the transmission of the data specified by the programmable controller CPU using a message
format other than the message formats (A compatible 1C frame formats 1 to 4, QnA compatible 4C frame format 5)
described in the MELSEC Communication Protocol Reference Manual.
10.1
User Frame Data Communications Function
The user frame data communications transmits and receives the first and last parts of a message in the format
selected by the user during data communications between programmable controller CPU and external device via the
Q series C24.
By using the function described in this chapter, on-demand data shown below can be transmitted from the Q series
C24 to an external device.
(Transmitting in QnA compatible 3C frame format 1)
character
area B
Sum check code
Send data
Local station
No.
PC No.
Network No.
Station No.
H L H L H L H L H L
E
T
X
As shown in the left, the user can sort the data
except for the "Send data" portion.
H L
Transmitted by user frame.
User frame data communications can be carried out by registering (registered by the data code) the message format to
be transmitted by the external device and the message format to be received by the external device according to the
specifications of the external device to the Q series C24 as user frames.
For the illustration above, the Q series C24 transmits the on-demand data as described below.
• User frame sum check code: Calculates the sum check code according to the contents registered in
advance by the user and transmits the result as ASCII code or binary code data.
• Other than user frame sum check code: Transmits data of the code registered in advance by the user. (No
conversion)
• Send data (character area B): This is the data that the sequence program requested for a transmission with
on-demand instruction. The same contents and list as when transmitted without using a user frame
described in the MELSEC Communication Protocol Reference Manual are transmitted by communication
protocol by GX Developer switch setting and word/byte designation.
243
10.1 User Frame Data Communications Function
S
T
X
Frame identification No.
On-demand data
10.2
User Frame Types and Registration
Data communications using user frames can be performed by registering the user frames to the Q series C24 from an
external device and the programmable controller CPU.
Page 220, CHAPTER 9 explains the types of user frames and the data that can be used.
To register a user frame from the programmable controller CPU, refer to Page 220, CHAPTER 9.
To register a user frame from an external device, first refer to Page 220, CHAPTER 9 and check the precautions, etc.,
then register the user frame with the function described in the MELSEC Communication Protocol Reference Manual.
10.3
User Frame On-Demand Data Transmission and Buffer
Memory Used
This section describes user frame on-demand data transmission processing and the on-demand data list by user
frame setting to the Q series C24 buffer memory.
(1) Transmission of on-demand data using user frames
The following describes the transmission of on-demand data using user frames.
• Programmable controller CPU processing
• Before issuing a transmission request to the Q series C24, set the No. of the user frame registered in the
Q series C24 to the buffer memory shown in the table below.
• Except for the above, the programmable controller CPU execution procedure and control procedure are
the same as transmitting on-demand data without user frames described in the MELSEC Communication
Protocol Reference Manual.
• External device processing
• When the external device receives the user frame transmitted by the Q series C24 as the first frame,
receive it as on-demand data.
(2) Buffer memory used and on-demand data list
• Buffer memory used
During on-demand data transmission by user frame, the user frame to be transmitted is designated in the buffer
memories shown below.
Address
CH1
A9H(169)
149H(329)
AAH(170)
14AH(330)
ABH(171)
14BH(331)
ACH(172)
14CH(332)
*1
244
Name
CH2
First frame No.
designation
On-demand user
frame designation
Last frame No.
designation
Description
(1st)
Designates the No. of the user frame that is transmitted as the first
frame.
0H: Do not transmit
(2nd)
Others: Transmit*1
(Other than 0 is always designated for the 1st frame. When
designating the 1st frame, the 2nd frame can also be designated.)
(1st)
Designates the No. of the user frame to be transmitted as the last
frame.
0H: Do not transmit
(2nd)
Others: Transmit*1
(When designating the 1st frame, the 2nd frame can also be
designated.)
Designates the registration No. (shown below) of the user frame to be transmitted from among the user frames
registered in the Q series C24.
1H to 3E7H (1 to 999): Default registration frame
3E8H to 4AFH (1000 to 1199): User frame (registered in flash ROM)
8001H to 801FH (-32767 to -32737): User frame (registered in buffer memory)
CHAPTER 10 ON-DEMAND DATA COMMUNICATIONS USING USER FRAMES
• On-demand data list
The following shows the user frame designation on-demand data list.
On-demand data
User frame
User frame
Send data
User frame
10
User frame
Transmitted when last frame (2nd) designated.
Transmitted when last frame (1st) designated.
On-demand instruction/transmitted when send
data designated in buffer memory.
Transmitted when first frame (2nd) designated.
First frame (1st).
• Only the on-demand data list combinations shown below can be used.
: Designation data
Data name
Combination
First frame (1st)
First frame (2nd)
Send data
Last frame (1st)
Last frame (2nd)
1)





2)





3)





4)





5)





6)





7)





8)





Contents of send data
User frame
First frame (1st)
Last frame (Last frame)
User frame
First frame (2nd)
Last frame (Other than last
frame)
*1
Send data
*1
ASCII mode
Binary mode
Codes registered from 00H to
FEH
Transmit the data of the code registered in the Q series C24. (No
conversion)
Combination of codes registered
in FFH and 00H to FFH
Transmit the data according to the user-designated contents, code,
and byte count.
Codes registered from 00H to
FEH
Converts the data code
registered in the Q series C24 to
ASCII data and transmits.
Transmits data code registered in
the Q series C24.
For 10H data, transmits 10H +
10H.
Combination of codes registered
in FFH and 00H to FFH
Converts data of the contents,
code, and byte count designated
by the user to ASCII data and
transmits.
Transmits the data of the
contents, code, and byte count
designated by the user.
For 10H data, transmits 10H +
10H.

Converts the designated send
data to ASCII data and transmits.
Transmits the designated data
unchanged. (No conversion)
For 10H data, transmits 10H +
10H.
Refer to the MELSEC Communication Protocol Reference Manual for details.
245
10.3 User Frame On-Demand Data Transmission and Buffer Memory Used
• The send data for on-demand data transmission by user frame is listed below. (See Page 220, CHAPTER 9 for a
detailed description of user frame.)
10.4
On-Demand Function Control Procedure During User
Frame Use
The following uses examples to explain the control procedure when using the on-demand function to frame to transmit
on-demand data to an external device by user frame.
10.4.1
Data communication using the ASCII code
The following shows the control procedure when performing switch settings via GX Developer and registration via GX
Configurator-SC.
(1) Switch settings by GX Developer
• Set the "Communication protocol setting" to any one of the "MC protocol (formats 1 to 4) ".
• Set the "Station number" to "0".
(2) Registration via GX Configurator-SC
Register as follows when transmitting a user frame, user selected transmission data*1 or a combination of user
frames.
(a) "User frame registration" screen
User frame No.
02H (2)
User frame (Registration code)
02H
3EBH(1003)
F9H, 00H, 00H, FFH, FFH, 00H
401H(1025)
03H, FFH, F1H
Contents of user frame registration
STX to host station No. data code matched to QnA
compatible 3C frame format 1
QnA compatible 3C frame format 1 corresponding
ETX, sum check code data code
(b) "Transmission control and others system setting" screen, "MC protocol system
setting" screen
• Set the "Word/byte units designation" to word units.
• Set the "On-demand user frame designation" items to the following:
• First frame No. 1st: 02H
• First frame No. 2nd: 3EBH
• Last frame No. 1st: 401H
• Last frame No. 2nd: 0H (No specification)
*1
246
Use the ONDEMAND instruction to designate the transmission data to two words (1234H, 5678H).
CHAPTER 10 ON-DEMAND DATA COMMUNICATIONS USING USER FRAMES
[Control procedure]
Added by Q series C24
10
First frame (1st)
External device
First frame (2nd)
Last frame (1st)
User frame
User
frame
Send data
(Data name)
S
T
X
F9H
F
9
00H
0
00H
0
0
FFH,FFH
0
F
F
00H
0
03H FFH,F1H
0
1
2
3
4
5
6
7
8
E
T
X
Sum check
Code
02H
Programmable controller CPU
H
(Example)
User frame registration code
Send data corresponding to
registration code
L
02H 46H 39H 30H 30H 30H 30H 46H 46H 30H 30H 31H 32H 33H 34H 35H 36H 37H 38H 03H 44H 32H
Send data code
ONDEMAND command
ONDEMAND command complete bit
ONDEMAND command abnormal
complete bit
1 scan
10.4 On-Demand Function Control Procedure During User Frame Use
Buffer memory
(Word units)
96H
0
(First address)
A0H
C00H
(Data length)
A1H
2
(1st first frame No.)
A9H
02H
(2nd first frame No.)
AAH
3EBH
(1st last frame No.)
ABH
401H
(2nd last frame No.)
ACH
0H
(Result of execution)
256H
0
C00H
1234H
C01H
5678H
(Send data)
When a transmission error is generated,
other than 0 is stored.
Sequentially transmits the data in 4-bit units, beginning
from the most significant bit.
(CH1 side)
247
10.4.2
Data communications using the binary code
The following shows the control procedure when performing switch settings via GX Developer and registration via GX
Configurator-SC.
(1) Switch settings by GX Developer
• Set the "Communication protocol setting" to "MC protocol (format 5)".
• Set the "Station number" to "0".
(2) Registration via GX Configurator-SC
Register as follows when transmitting a user frame, user selected transmission data*1 or a combination of user
frames.
(a) "User frame registration" screen
User frame No.
User frame (Registration code)
User frame registration contents
3ECH(1004)
02H, FFH, 01H, 3BH
STX + Q series C24 station No. + ;
402H(1026)
03H, FFH, F0H, 0DH, 0AH
ETX + sum check code + CR + LF
Sum check code is designated by a 1 byte binary
code.
(b) "Transmission control and others system setting" screen, "MC protocol system
setting" screen
• Set the "Word/byte units designation" to word units.
• Set the "On-demand user frame designation" items to the following:
• First frame No. 1st: 3ECH
• First frame No. 2nd: 0H (No designation)
• Last frame No. 1st: 402H
• Last frame No. 2nd: 0H (No specification)
*1
248
Use the ONDEMAND instruction to designate the transmission data to two words (1234H, 5678H).
CHAPTER 10 ON-DEMAND DATA COMMUNICATIONS USING USER FRAMES
[Control procedure]
Added by Q series C24
External device
First frame (1st)
10
Last frame (1st)
User frame Send data
User frame
(Data name)
S
T
X
Programmable controller CPU
03H FFH,F0H 0DH 0AH
E
T
X
Sum check
code
Station No.
Q series C24
02H FFH,01H 3BH
C
R
L
F
(Example)
02H
00H
3BH 12H 34H 56H 78H 03H
17H
0DH 0AH
User frame registration code
Send data corresponding to
registration code
Send data code
ONDEMAND command
ONDEMAND command complete bit
ONDEMAND command abnormal
completion bit
1 scan
96H
0
(First address)
A0H
C00H
(Data length)
A1H
2
3ECH
(1st first frame No.)
A9H
(2nd first frame No.)
AAH
0H
(1st last frame No.)
ABH
402H
(2nd last frame No.)
ACH
0H
(Result of execution)
256H
0
C00H
1234H
C01H
5678H
(Send data)
10.4 On-Demand Function Control Procedure During User Frame Use
(Word units)
When a transmission error is generated,
other than 0 is stored.
Sequentially transmits the data in 4-bit units, beginning
from the most significant bit.
(CH1 side)
249
10.5
Example of an On-Demand Data Transmission Program
Using User Frames
The following shows an example of a sequence program when sending on-demand data including user frames.
Perform the following settings via GX Developer and registration using GX Configurator-SC in advance.
(The Q series C24 I/O signals are X/Y00 to X/Y1F and are sent from the CH1 side interface.)
(1) Switch settings by GX Developer
Set the following setting values on the "Intelligent functional module switch setting" screen.
Setting item
Switch 1
Switch 2
Switch 3
Setting value
CH1 Transmission setting
CH1 Communication rate setting
Remarks
Set according to the
external device.
CH1 Communication protocol setting
0001H
CH2 Transmission setting
0000H
CH2 Communication rate setting
0000H
Switch 4
CH2 Communication protocol setting
0001H
Switch 5
Station No. setting
0000H

MC protocol format 1
Not used
Q series C24 station No.
(2) Registration via GX Configurator-SC
• Registering the user frame to be transmitted: To register the user frame data to be transmitted on the "User
frame registration" screen, refer to Page 220, CHAPTER 9.
• Registering the user frame No. to be transmitted and the unit of the data length: Using the screens listed
below, register the user frame No. and the unit of the length of data to be transmitted, which have been
registered on the "User frame registration" screen.
• "Transmission control and others system setting" screen
• "MC protocol system setting" screen
Registration screen
"Transmission control and others system setting"
screen
"MC protocol system setting" screen
Setting item
Word/byte units designation
0000H
Remarks
Word unit
On-demand buffer memory head address designation
0400H

On-demand data length designation
0000H

On-demand user frame
designation
First frame No. designation 1st
0002H
First frame No. designation 2nd
03EBH
Last frame No. designation 1st
0401H
Last frame No. designation 2nd
0000H
Message wait time designation
250
Setting
value
0000H

(No designation)

CHAPTER 10 ON-DEMAND DATA COMMUNICATIONS USING USER FRAMES
(3) Program example
The following program example shows the transmission of on-demand data using the on-demand function.
10
Designate two words of transmission data with the ONDEMAND instruction.
The data for the user frame section of on-demand data to be sent is the registered data for the user frame No.
that was registered with GX Configurator-SC.
On-demand transmission
instruction
Sets the transmission channel
to the CH1 side
Sets the transmission data count
to two words
Sets the transmitting data
in D10 to D11
Resets the normal completion
flag
Resets the abnormal completion
flag
Sets the transmission
preparation completion flag
Executes on-demand
transmission
Normal completion
Abnormal completion
● The SPBUSY instruction can be used to read the communication status by the dedicated instruction.
● For details on the dedicated instructions, refer to the User's Manual (Basic).
● Designate the storage capacity for transmission data (stored in D10 to D11 in the above program example) and data
length (stored in D2 in the above program example) so that they do not exceed the range of buffer memory assigned by
the user for the on-demand function.
251
10.5 Example of an On-Demand Data Transmission Program Using User Frames
Resets the transmission
preparation completion flag
CHAPTER 11
DATA COMMUNICATIONS USING
USER FRAMES
Registering the fixed format portion of the message transmitted/received by the opposite device and the Q series C24
as a user frame beforehand allows data transmission/reception using a user frame.
The use of the user frame to perform data transmission/reception facilitates the creation of transmission data on the
programmable controller CPU side and a simplified sequence program for checking the reception data.
This Chapter explains the data transmission/reception method and procedure when performing data communication
with the Q series C24 non procedure protocol using a user frame.
User frame
Data
transmission
Arbitrary data
Arbitrary data
Q series C24
Data
transmission
Opposite device such as a bar code reader
or ID controller personal computer
User frame
For more details on the "Transparent code" and "ASCII-BIN conversion" used in the explanations of this chapter, see the
chapters listed below.
When using transparent codes or performing data communication using ASCII-BIN conversion, please read the following
chapters, as well.
• When using transparent codes:  Page 296, CHAPTER 12
• When performing data communication using ASCII-BIN conversion:  Page 319, CHAPTER 13
252
CHAPTER 11 DATA COMMUNICATIONS USING USER FRAMES
11.1
Overview of Data Communication Procedure
The following is an overview of the procedure when performing data communication between the opposite device and
programmable controller CPU using a user frame.
Start
11
Switch setting by GX Developer.
Initial setting by GX Configurator-SC
(When only default registration frame used)
(When registering user frames)
• Register to the Q series C24 Flash ROM.
• Register to the Q series C24 buffer memory.
…… *1
(When receiving data)
Set user frame No., etc. to receive user frame
designation area
(addresses ADH to B5H, 14DH to 155H, 2020H
…… *2
to 2027H, 2120H to 2127H) of the Q series
C24 buffer memory
* Must be set by GX Configurator-SC
after debugging is completed.
Start data communications
(Reception)
Designate user frame No. to
transmission user frame designation
area (address B7H to 11DH,157H to 1BDH)
of the Q series C24 buffer memory.
Designate transmission data
(arbitrary data area in transmit message)
to transmit area of the Q series C24
buffer memory.
Read receive data
11.1 Overview of Data Communication Procedure
(Transmission)
…… *3
…… *4
Data transmission
*1
*2
*3
*4
 User's Manual (Basic),  Page 220, CHAPTER 9
Page 267, Section 11.2.4
Page 254, Section 11.2.1, Page 262, Section 11.2.2
Page 286, Section 11.4
253
11.2
Data Reception
In data reception using the user frame, the reception method on the Q series C24 side includes format 0 and format 1.
This section explains data reception for each format.
11.2.1
About reception data
In reception using the user frame, data arranged as indicated below can be received.
User frame
(first frame)
User frame
(first frame)
Arbitrary data
User frame
(last frame)
(1-A)
¨
¨
¨
(1-B)
¨
-
¨
(1-C)
¨
¨
-
(1-D)
¨
¨
-
(1-E)
¨
-
-
(2-A)
-
¨
¨
(2-B)
-
-
¨
Reception
Combination
method
Format-0
With the first
frame (*1)
Format-1
Without the first
frame (*1)
User frame
(last frame)
Arbitrary data
Format-0
Explanation
section
*4
Remarks
For data
reception,
mixed settings
are possible.
*5
*6
¨ : Specified data exists.
(When ASCII-BIN conversion is set to "Disable")
Codes that can
be received
Codes stored to
00H to FFH
(Not stored)
00H to FFH
00H to FFH
receive area *3
(When ASCII-BIN conversion is set to "Enable")
*2
254
Codes that can
be received
Codes stored to
00H to FFH
(Not stored)
30H to 39H,
41H to 46H
receive area *3
0H to 9H,AH to FH
CHAPTER 11 DATA COMMUNICATIONS USING USER FRAMES
*1
*2
*3
*4
*5
*6
User frames for reception
• The user frame for data reception can set up to a maximum of four combinations of the first frame and the last
frame, regardless of whether there is a specification.
• For a combination that specifies the first frame (with the first frame), it is necessary to specify the first frame even
in other combinations.
• For a combination that does not specify the first frame (without the first frame), the first frame cannot be specified
even in other combinations.
• A combination with the first frame and a combination without the first frame cannot be combined.
If data of other than 30H to 39H and 41H to 46H are received as the data code of the arbitrary data area (including the
transparent code data), the Q series C24 ASCII-BIN conversion will generate an error.
Receive data arbitrary data area
When the arbitrary data area is stored to the receive area, and the storage byte count is an odd number of bytes, the
receive data count shown below is stored to the receive data count storage area. (When ASCII-BIN conversion is
enabled, receive data count is the storage byte count when the arbitrary data area is converted to binary code and
stored to the receive area.)
• Word units: Receive data count = Number of bytes stored to receive area  2Fractions are truncated
• Byte units: Receive data count = Number of bytes stored to receive area (00H is stored to the upper byte of the
last data storage location of the receive area.)
When ASCII-BIN conversion enabled, make the arbitrary data area of the receive data an even number of bytes
excluding the additional code.
Page 256, Section 11.2.1 (1)
Page 257, Section 11.2.1 (2)
Page 259, Section 11.2.1 (3)
11
11.2 Data Reception
255
(1) Reception with the first frame (combination 1-A to C) (reception using Format0)
(a) Reception of combination (1-A)
• In this method, any data section of the reception message that can be handled by the programmable
controller CPU side is enclosed by the first frame and the last frame and transmitted from the external
device.
• Any reception data prior to the first frame will be ignored.
• The Q series C24 will begin reception processing when data of the same arrangement as the first frame is
received. When data of the same arrangement as the last frame is received, arbitrary data is stored in the
reception area of the buffer memory and a read request is performed to the programmable controller CPU.
• The received data count initially set in the Q series C24 should be a data count that exceeds the size of the
arbitrary data to be received.
• Reception processing via the receive complete code initially set in the Q series C24 will not be performed.
The reception data for the receive complete code will be treated as arbitrary data.
When data transmitted from a bar code reader is received
STX will be registered in the first frame and ETX registered in the last frame according to the message
format of the bar code reader.
(Data format transmitted from the bar code reader)
S
T
X
Reception
data
Data (arbitrary data)
E
T
X
First frame: STX
Last frame: ETX
02H
03H
: Reception start timing
: Receive complete timing (read timing)
Ignored
Stored in the reception area
(b) Reception of combination (1-B)
• In this method, messages to be received by the programmable controller CPU side are all transmitted from
the external device as fixed format data.
• Any reception data prior to the first frame will be ignored.
• The Q series C24 will begin reception processing when data of the same arrangement as the first frame is
received. When data of the same arrangement as the last frame is received, a read request is performed to
the programmable controller CPU.
• Since there is no arbitrary data, the reception data count will be "0" when a read request is performed to the
programmable controller CPU.
• The received data count initially set in the Q series C24 uses the default value.
A
C
K
Reception
data
C
L
R
F
06H 0DH 0AH
First frame: ACK
Last frame: CR, LF
: Reception start timing
Ignored
256
: Receive complete timing (read timing)
Stored in the reception area
The received data count is "0."
CHAPTER 11 DATA COMMUNICATIONS USING USER FRAMES
(c) Reception of combination (1-C)
• In this method, start of data transmission from the external device to the programmable controller CPU side
is notified by the first frame, after which arbitrary data of a fixed length is repeatedly transmitted from the
external device.
• Any reception data prior to the first frame will be ignored. After the first frame is received, all later reception
data is treated as arbitrary data.
• The Q series C24 will begin reception processing when data of the same arrangement as the first frame is
received. A read request will be repeatedly performed to the programmable controller CPU when arbitrary
11
data equaling the received data count initially set in the Q series C24 is received.
• The received data count initially set in the Q series C24 should be a data count for arbitrary data (fixed
length) transmitted from the external device.
• Reception processing via the receive complete code initially set in the Q series C24 will not be performed.
The reception data for the receive complete code will be treated as arbitrary data.
Reception
data
Arbitrary data
First frame
Equaling the received
data count
Equaling the received
data count
: Reception start timing
: Receive complete timing (read timing)
Ignored
Stored in the
reception area
Stored in the
reception area
(2) Reception with the first frame (combination 1-D, 1-E) (reception using Format1)
transmitted from the external device together with the first frame.
The data length for the arbitrary data in the reception message that can be handled by the programmable
controller CPU side*1 can be specified for each data reception frame combination (up to four combinations).
• Any reception data prior to the first frame will be ignored.
• The Q series C24 will begin reception processing when data of the same arrangement as the first frame is
received. When arbitrary data equaling the exclusive format-1 received data count is received, the arbitrary
data is stored in the reception area of the buffer memory and a read request is performed to the
programmable controller CPU.
• Exclusive format-1 received data count initially set in the Q series C24 should be a data count for arbitrary
data to be received. The received data count initially set in the Q series C24 is not used.
• Reception processing via the receive complete code initially set in the Q series C24 will not be performed.
The reception data for the receive complete code will be treated as arbitrary data.
By specifying a user frame, in which only ACK (06H) is registered, as the first frame and also exclusive
format-1 received data count for arbitrary data as 0 bytes, a read request will be performed to the
programmable controller CPU upon the reception of a 1-byte ACK.
257
11.2 Data Reception
• In this method, arbitrary data of exclusive format-1 received data count initially set in the Q series C24 is
By specifying a user frame, in which only NAK (15H) is registered, as the first frame and also specifying
exclusive format-1 received data count for arbitrary data as 2 bytes, a read request will be performed to
the programmable controller CPU upon the reception of NAK + 2-byte data.
N
A
K
Reception
data
(1234H)
First frame: NAK
15H 34H 12H
Equaling exclusive format-1
receive data count
: Reception start timing
: Receive complete timing (read timing)
Ignored
*1
258
Stored in the reception area
The data length for arbitrary data can be specified as a word/byte count of 0 or greater (the unit depends on word/byte
units designation) for each combination of the first frame and the last frame specifying format-1.
The received data count for data reception using format-1 is referred to as exclusive format-1 received data count.
CHAPTER 11 DATA COMMUNICATIONS USING USER FRAMES
(3) Reception without the first frame (combination 2-A, 2-B) (reception using
Format-0)
(a) Reception of combination (2-A)
• In this method, a user frame is used as the last frame in place of the non procedure protocol data receive
complete code and is transmitted from the external device together with arbitrary data.
11
• Any reception data prior to the last frame are all treated as arbitrary data.
• The Q series C24 will begin reception processing when arbitrary data is received. When data of the same
arrangement as the last frame is received, arbitrary data is stored in the reception area of the buffer memory
and a read request is performed to the programmable controller CPU.
• The received data count initially set in the Q series C24 should be a data count that exceeds the size of the
arbitrary data to be received.
• The Q series C24 performs the following processing with respect to the reception data that is the same as
the receive complete code initially set in the Q series C24.
• When the reception data is included in the arbitrary data: Reception is processed via the receive complete
code.
• When included in the last frame: Reception is not processed via the receive complete code.
By registering ETX + CR + LF as the last frame, a read request is performed to the programmable
controller CPU when the end of the reception data receives a message of ETX + CR+ LF.
Arbitrary data
E
T
X
C
L
R
F
Last frame: ETX, CR, LF
Stored in the reception area
11.2 Data Reception
03H 0DH 0AH
: Reception start timing
: Receive complete timing (read timing)
259
(b) Reception of combination (2-B)
• In this method, a user frame is used as the last frame in place of the non procedure protocol data receive
complete code, and fixed format data is transmitted from the external device.
• Any reception data prior to the last frame are all treated as arbitrary data.
• When data of the same arrangement as the last frame is received, the Q series C24 performs a read request
to the programmable controller CPU.
• Upon the reception of data from this combination that contains no arbitrary data, the reception data count will
be "0" when a read request is performed to the programmable controller CPU.
• The received data count initially set in the Q series C24 uses the default value.
• The Q series C24 performs the following processing with respect to the reception data that is the same as
the receive complete code initially set in the Q series C24.
• When included in the last frame: Reception is not processed via the receive complete code.
By registering ACK + CR + LF as the last frame, a read request is performed to the programmable
controller CPU when the end of the reception data receives a message of ACK + CR + LF.
A
C
K
C
L
R
F
Last frame: ACK, CR, LF
06H 0DH 0AH
: Reception start timing
: Receive complete timing (read timing)
Stored in the reception area
The received data count is "0."
Handling of the Q series C24 receive data
● When an user frame (first frame, last frame) of a code registered in the Q series C24 is received, receive processing by
user frame is performed.
● Of the first frame No. and last frame No. (maximum 4 sets) initialized by the user at the buffer memory receive user frame
designation area, the set No. ( th) of the user frame received from the external device is stored to the receive user
frame storage area.
● If receive transparent code is designated, the data of the additional code included in the arbitrary data area is removed
immediately after reception (before conversion when the receive data is converted from ASCII code to binary code).
260
CHAPTER 11 DATA COMMUNICATIONS USING USER FRAMES
Remark
The following shows the difference in how reception data for each reception method (Format-0 and Format-1) is treated
when data is received using the combination of (first frame + arbitrary data).
● When data is received using Format-0 (combination (1-C))
• The Q series C24 regards all arbitrary data after the first frame as valid data and stores it sequentially in the
reception area.
• A read request is performed to the programmable controller CPU each time arbitrary data equaling the received
data count is received, and this process is repeated.
Reception
data
11
Arbitrary data
First frame
Equaling the received
data count
Equaling the received
data count
: Reception start timing
: Receive complete timing (read timing)
Ignored
Stored in the
reception area
Stored in the
reception area
● When data is received using Format-1 (combination (1-D, 1-E))
• After the first frame is received, the Q series C24 regards all arbitrary data equaling exclusive format-1 received
data count specified for the received first frame combination as valid data and stores it in the reception area. It
then performs a read request to the programmable controller CPU.
• After data equaling exclusive format-1 received data count is received, any data until the next first frame will be
ignored. (Data will not be stored in the reception area.)
Reception
data
First frame
Arbitrary data
Reception
data
Ignored
Stored in the reception area
Arbitrary data
11.2 Data Reception
Equaling exclusive format-1
received data count
First frame
Equaling exclusive format-1
received data count
Ignored
Stored in the reception area
: Reception start timing
: Receive complete timing (read timing)
261
11.2.2
Timing for start/completion of data reception
This section explains the reading of reception data based on the user frame and other factors (such as the receive
complete code and received data count) during data reception using a user frame.
(1) Timing for start/completion of data reception
The following describes the timing for start/completion of the data reception processing with the Q series C24.
• Data reception using a user frame
• Data reception using the receive complete code and received data count initially set in the Q series C24
• Data reception using exclusive format-1 received data count
User frame setting for
reception
Item
Reception
start
When using format-0
(See Page 262, Section 11.2.2 (2) for each
timing.)
With the first frame
When the first frame is received.
Without the first frame
When the first data of arbitrary data is
received.
When using Format-1
(See Page 262, Section 11.2.2 (2) for each
timing.)

When the factor of receive complete (timing of reception data reading to the programmable
controller CPU) is one of the following:
(Depends on prior settings. See Page 262, Section 11.2.2 (2))
Receive
complete

• When the last frame is received.
• When data of the receive complete code is
received. (In the case of a combination
without the first frame)
• When data equaling the received data
count is received.
• When a receive error (time out for the noreception monitoring time (timer 0)) occurs.
• When exclusive format-1 received data
count is specified as 0 and the first frame is
received.
• When exclusive format-1 received data
count is specified as 1 or more and data
equaling this count is received.
• When a receive error (time out for the noreception monitoring time (timer 0)) occurs.
* All arbitrary data received up to the point when one of the above occurs or a receive error is
generated is stored in the reception area.
(2) Timing chart for reception processing using the Q series C24
The following is a timing chart for the reception processing when data reception is performed using the user
frame, which includes the reception processing using the received data count. The numbers in the table indicate
the timing of a reception data read request to the programmable controller CPU.
[Combination with the first frame]

Timing pattern number
Reception data
Combination
Amount of reception data of arbitrary data
Reception
data prior to
the reception
of the first
frame
When receiving
the first frame
Reception data count < Received data count
1-A
1-B
1-C
When
receiving
the last
frame

1-A 1)
Data of the
complete code
is treated as part
of arbitrary data.
1-B

Reception data count  Received data count
1-A 2)
Reception data count = 0
Reception data count  Received data count
Reception start
Reception data count (exclusive format-1 received
data count > 0)
1-E
Reception data count (exclusive format-1 received
data count = 0)

1-C 1)
Delete
Reception data count > Received data count
1-D
262
When
receiving
arbitrary data
in the
reception
message
1-C 2)
1-D
Reception
start
1-E


When receiving
the complete
code (*1)
Data of the
complete code
is treated as part
of arbitrary data.

CHAPTER 11 DATA COMMUNICATIONS USING USER FRAMES
[Combination without the first frame]

Timing pattern number
Reception data
Combination
Amount of reception data of arbitrary data
Reception
data prior to
the reception
of the first
frame
When
receiving the
first frame
Reception data count < Received data count
2-A (*2)
2-B (*2)
Reception data count  Received data count
Reception data count = 0
*1
*2


When receiving
arbitrary data in
the reception
message
When receiving
the last frame
Reception start
2-A 1)
Reception
start

When
receiving the
complete
code (*1)
2-A 3)
2-A 2)
Reception
start
11
2-A 4)
2-B

The reception processing via the receive complete code is not performed when the same data as the receive complete
code has been registered in the last frame.
The data reception interval is not monitored with the no-reception monitoring time (timer 0) when only the last frame is
set.
When a receive error is detected, the Q series C24 stores arbitrary data of the reception data received immediately before
the error in the reception area of the buffer memory, then turns the reception error detection signal (X4) ON.
11.2 Data Reception
263
[Combination with the first frame] Timing patterns for reception start and receive complete (read)
(For data reception with format-0)
Arbitrary data
Equaling the
received data
count
Programmable
controller CPU
side
Last frame
First frame
Arbitrary data
Pattern No. 1-A 2)
Last frame
External device
side
First frame
Pattern No. 1-A 1)
Equaling the
received data
count
External device
side
Last frame
First frame
Pattern No. 1-B
Programmable
controller CPU
side
Pattern No. 1-C 2)
First frame
External device
side
First frame
Pattern No. 1-C 1)
Arbitrary data
Programmable
controller CPU
side
Equaling the
received data
count
Arbitrary data
Equaling the
received data
count
Equaling the
received data
count
(For data reception with format-1)
Programmable
controller CPU
side
Arbitrary data
Reception data
Equaling exclusive format-1
received data count
Ignored
First frame
External device
side
First frame
Pattern No. 1-D
Arbitrary data
Equaling exclusive format-1
received data count
Programmable
controller CPU
side
Reception data
Ignored
First frame
External device
side
First frame
Pattern No. 1-E
: Reception start timing
: Receive complete timing (read timing)
When exclusive format-1
received data count is 0
When data is received using Format-1, the Q series C24 checks again whether the first frame has been received after
receiving data equaling the exclusive format-1 received data count. Reception data during that time is ignored.
264
CHAPTER 11 DATA COMMUNICATIONS USING USER FRAMES
[Combination without the first frame] Timing patterns for reception start and receive complete (read)
Pattern No. 2-A 1)
Arbitrary data
Programmable
controller CPU
side
11
Equaling the received
data count
Programmable
controller CPU
side
Arbitrary data
Equaling the received
data count
Last frame
Arbitrary data
Complete
code
Last frame
Arbitrary data
Pattern No. 2-A 4)
Complete
code
Pattern No. 2-A 3)
External device
side
Last frame
Last frame
Arbitrary data
External device
side
Pattern No. 2-A 2)
Arbitrary data
External device
side
Last frame
Pattern No. 2-B
: Reception start timing
: Receive complete timing (read timing)
Programmable
controller CPU
side
11.2 Data Reception
265
11.2.3
Receive procedure
The following shows the receive procedure when a message, including data with the same arrangement as the
specified user frame, is received and the arbitrary data is read to the programmable controller CPU.
(When the CH1 side interface of the Q series C24 receives data)
Reception data with the user frame
External device
side
User frame
(first frame)
Arbitrary
data area
(*1)
User frame
(last frame)
Programmable
controller CPU
side (*2)
(*1)
Reception data
read request signal
Programmable
controller CPU
side
X3
(*3 2))
INPUT
ON
Completion device
Abnormal
ON completion
Status display device
at completion
Normal
completion
1 scan
(*3 1))
FROM
*1
*2
*3
266
See Page 254, Section 11.2.1 and Page 267, Section 11.2.4 regarding the reading of reception data using a user frame
and the timing of reception data reading to the programmable controller CPU.
Sets the receive user frame registration No., etc. in the "non procedure system setting" screen for GX Configurator-SC.
During debugging, the initial setting value for data reception shall be set prior to data receiving, but after debugging is
completed, it shall be set when the Q series C24 starts up. ( Page 267, Section 11.2.4)
Reading (1) below) for checking which user frame was received by the Q series C24 from the programmable controller
CPU and reading of the receive data (2) below).
1) Reads which of the user frames set in the receiver user frame designation area was received from the receive user
frame storage area (address: 25BH).
2) Reads the arbitrary data area of the receive message from the receive area (default addresses: 600H to 7FFH).
CHAPTER 11 DATA COMMUNICATIONS USING USER FRAMES
11.2.4
User frame setting for reception
(1) About user frame setting for reception
This setting is to receive data from the opposite device using non procedure protocol through the use of a user
frame. Everything is set on the GX Configurator-SC "Non procedure system setting" screen.
The setting items are listed below.
11
[Setting screen] Non procedure system setting screen
Description of setting values
Format-0
Format-1
Received data count designation
Designates the data count that exceeds
the size of the arbitrary data to be
received or the data count of the received
data size.
Receive complete code designation
(Reception of combination with the first frame)
The specified value is invalid.
(Reception of combination without the first frame)
Designates the code for the last data in the reception message for performing a read
request to the programmable controller CPU.
User frame use enable/disable designation
Designates "Enable".
First frame No. designation 1st to 4th
Designates the user frame No.
(0 or 1 or higher).
Designates the user frame No.
(1 or higher).
Last frame No. designation 1st to 4th
Designates the user frame No.
(0 or 1 or higher).
Designates 0H for everything.
User frame receive format designation 1st to 4th
Designates "Format-0".
Designates "Format-1".
The specified value is invalid.
Designates the data count for the arbitrary
data to be received.
Exclusive format-1 received data count 1st to 4th
The specified value is invalid.
(Exclusive format-1 received data count
becomes valid.)
267
11.2 Data Reception
GX Configurator-SC setting items (Non
procedure system setting screen)
(2) Initial settings via GX Configurator-SC ("Non procedure system setting"
screen)
This section explains the buffer memory when setting various setting data for data reception using a user frame in
a sequence program. (Numbers in the parentheses indicate the buffer memory address.)
(a) User frame use enable/disable designation (addresses: ADH/14DH)
Designate "Enable" when using user frames to receive data.
b15
Buffer memory address
to
b0
ADH/14DH
(Default 0H)
Write 1H
0: Do not use.
1: Use.
2: Data communication enable (Q series C24 is set)
• "1" is written in the user frame use enable/disable designation area.
• After the preparation for the data reception using the user frames is completed, "2" is written in the user
frame use enable/disable designation area. (Set by the Q series C24)
• After the value in the user frame use enable/disable designation area is changed from "1" to "2", start
receiving data used by the user frame. Until "2" is written in the user frame use enable/disable designation
area, data transmission is also not available.
(b) First frame No. designation area and last frame No. designation area (addresses:
AEH to B5H/14EH to 155H)
From among the user frames registered in the Q series C24, designate the frame numbers of the user frames
you wish to use in the combination and order of priority as described in (1).
b15
Buffer memory address
to
AEH/14EH
to
to
to
First frame (4th)
B2H/152H
B5H/155H
(Default All 0H)
First frame (1st)
B1H/151H
to
b0
First
combination
Last frame (1st)
to
to
Fourth
combination
Last frame (4th)
Write 0H to 801FH
• 0H (0): No designation
• 1H to 3E7H (1 to 999): Designate the default registration frame (for OS ROM registration).
• 3E8H to 4AFH (1000 to 1199): Designate the user frame (for flash ROM registration).
• 8001H to 801FH (-32767 to -32737): Designate the user frame (for buffer memory registration).
268
CHAPTER 11 DATA COMMUNICATIONS USING USER FRAMES
[How to specify the first frame No. and the last frame No.]
Set the frame numbers using the following setting method.
• For the receive user frames, the first frame and last frame are set as a pair, regardless of whether the
external device transmits these frames.
(If the external device does not transmit either one of the frames, the unsent frame No. is set to "0" (no
setting)).
• A maximum of four combinations of first and last frames can be set for the non procedure protocol. (
11
Page 254, Section 11.2.1)*1
(When specifying the first frame)
*2
• Each frame No. for combinations that specify the first frame and the last frame
• Each frame No. for combinations that specify the first frame but not the last frame
*1
*2
Of the maximum four combinations to be set, if there is a combination that specifies the first frame, specify the first frame
for all other combinations. In addition, set in the following order starting from the first buffer memory (AEH to B5H/14EH
to 155H).
Of the maximum four combinations to be set, if there is a combination that specifies the last frame only without
specifying the first frame, the first frame cannot be specified in any of the combinations. Set the number of the last frame
to be used in order starting from the first area of the buffer memory (AEH to B5H/14EH to 155H).
• When setting more than one combination, the first frame having the registered data in the same
arrangement or the same frame number cannot be designated.
However, the last frame can be designated.
• Use the user frame numbers of the following user frames to set the receive user frames. ( Page 220,
Section 9.1)
• Default registration frame numbers: 1H to 3E7H
• User frame numbers registered in the Q series C24 flash ROM: 3E8H to 4AFH
• User frame numbers registered in the Q series C24 buffer memory: 8001H to 801FH
additional code data shown in Chapter 12 as a user frame for data reception using non procedure protocol.
269
11.2 Data Reception
• Do not specify (set) the frame No. of a user frame that includes the receive transparent code designation
(c) User frame receive format designation (address: 2020H to 2023H/2120H to 2123H)
In data reception using a user frame, specify the reception method for each combination of receive user
frames. This setting is valid in a setting shown in Page 268, Section 11.2.4 (2) (b) when it is set using a
combination that specifies a user frame.
b15
Buffer memory address
2020H/2120H
b0
to
(Default 0H)
Setting for the first combination
Setting for the second combination
to
Setting for the third combination
2023H/2123H
Setting for the fourth combination
0H: Format-0
1H: Format-1
Specify the reception method
For combinations other than those with the first frame only, data reception is performed using Format-0 even if Format-1 is
specified through the above reception method setting.
(d) Exclusive format-1 received data count designation (address: 2024H to 2027H/2124H
to 2127H)
• For a combination specifying Format-1 in the user frame receive format designation, specify the arbitrary
data word/byte count (size for performing a reception data read request to the programmable controller
CPU) when the applicable first frame is received. Specify this for each combination specifying Format-1.
• Specify a size within the size of the storage area for the reception data in the buffer memory.
• The unit for the setting value depends on the setting value given in the word/byte units designation.
b15
Buffer memory address
2024H/2124H
to
b0
(Default
Setting for the second combination
to
Setting for the third combination
2027H/2127H
Setting for the fourth combination
Write 0H to FFFFH
270
0H)
Setting for the first combination
Exclusive format-1
received data count
CHAPTER 11 DATA COMMUNICATIONS USING USER FRAMES
(3) Examples of registering a receive user frame
The following are examples of pre-registering a receive user frame on the CH1 side with the GX Configurator-SC.
(a) When the first frame is specified
In the example, the following three combinations are registered for the receive user frame.
[Setting conditions]
User frame
User frame receive format
designation
Exclusive format-1 received
data count
1st
combination
(First frame + last frame)
Format-0

2nd
combination
(First frame only)
Format-1
0H
3rd
combination
(First frame only)
Format-1
2H
11
Remarks
The received data count
becomes valid.
Exclusive format-1
received data count
becomes valid.
[Setting value]
Setting item
Setting value
Received data count designation
1FFH
Remarks
For Format-0
Receive complete code designation
FFFFH
Set to "No receive
complete code".
Receive user frame designation
User frame use enable/disable designation
Enable
Always specify "Enable".
1st
Receive user frame designation
First frame No. designation
User frame receive format designation
Exclusive format-1 received data count
designation
2nd
3E9H
3rd
3EAH
4th
0H
1st
41DH
2nd
0H
0H: No designation
1H or higher: There is a
designation.
In this setting, only three
combinations become
valid.
3rd
0H
4th
0H
1st
Format-0
2nd
Format-1
3rd
Format-1
Exclusive format-1
received data count
becomes valid.

4th
Format-0
1st
0H
2nd
0H
3rd
2H
4th
0H
The received data count
becomes valid.
For Format-1
271
11.2 Data Reception
Receive user frame designation
Last frame No. designation
3E8H
(b) When the first frame is not specified
In the example, the following three combinations are registered for the receive user frame.
[Setting conditions]
User frame
1st
combination
(Last frame only)
2nd
combination
(Last frame only)
3rd
combination
(Last frame only)
User frame receive format
designation
Exclusive format-1 received
data count
Format-0

Remarks
The received data count
becomes valid.
[Setting value]
Setting item
Setting value
Received data count designation
Remarks
For Format-0
Receive complete code designation
00H
Designate any received
complete code.
Receive user frame designation
User frame use enable/disable designation
Enable
Always specify "Enable".
Receive user frame designation
First frame No. designation
Receive user frame designation
Last frame No. designation
User frame receive format designation
Exclusive format-1 received data count
designation
272
1FFH
1st
0H
2nd
0H
3rd
0H
4th
0H
1st
41DH
2nd
41EH
3rd
41FH
4th
0H
1st
Format-0
2nd
Format-0
3rd
Format-0
4th
Format-0
1st
0H
2nd
0H
3rd
0H
4th
0H
0H: No designation
0H: No designation
1H or higher: There is a
designation.
In this setting, only three
combinations become
valid.
Everything is set to Format0 since the first frame is not
designated.
Setting value for Format-1.
This setting is not required
since everything is set to
Format-0.
CHAPTER 11 DATA COMMUNICATIONS USING USER FRAMES
11.3
Receive Program
This section shows examples of the sequence program to read the reception data stored in the Q series C24 buffer
memory to the programmable controller CPU, when data including the user frame is received.
11.3.1
Sequence program example
11
In the program examples provided in this section, data reception by the user frame is indicated based on the following:
• I/O signals of Q series C24: Install Q series C24 in the position where the I/O signal with QCPU is X/Y00 to
X/Y1F.
• Interface for Q series C24 used for data communications with external device: Use an RS-232 interface on
the CH1 side of Q series C24.
• Intelligent function module switch settings
Bit
Switch No.
Position
Specified
value
Switch 1
Description
Setting value
b0
OFF
Operation setting
b1
ON
Data bit
8 bits
b2
OFF
Parity bit
None
b3
OFF
b4
OFF
b5
OFF
Sum check code
None
b6
OFF
Write during RUN
Prohibited
b7
OFF
Setting modifications
Prohibited
Even/odd parity
Odd
Stop bit
1 bit
Communication rate setting
Switch 2

Communication protocol setting
Switch 5

Station number setting
0702H
(Matched with
the external
device)
19200bps
Nonprocedural protocol
0006H
No. 0 station
0000H
• Buffer memory settings for the examples (For other than below, default values are used.)
• Example in Page 275, Section 11.3.1 (1) shows the GX Configurator-SC setting. For settings, refer to
Page 267, Section 11.2.4.
• Example in Page 276, Section 11.3.1 (2) shows the setting by a sequence program.
Address Dec. (Hex.)
CH1
173 (ADH)
Name
User frame use enable/disable designation
Setting value
1H: Enable
174 (AEH)
First frame No. designation, 1st*1
Example (1): 3E8H
Example (2): 8001H
175 (AFH)
First frame No. designation, 2nd*1
Example (1): 3E9H
Example (2): 8002H
176 (B0H)
First frame No. designation, 3rd*1
6H
177 (B1H)
First frame No. designation, 4th*1
15H
178 (B2H)
Last frame No. designation, 1st*1
Example (1): 41BH
Example (2): 8005H
179 (B3H)
Last frame No. designation, 2nd
0H: None
180 (B4H)
Last frame No. designation, 3rd
0H: None
181 (B5H)
Last frame No. designation, 4th
0H: None
8224 (2020H)
User frame receive format designation, 1st
0H: Format 0
8225 (2021H)
User frame receive format designation, 2nd
1H: Format 1
8226 (2022H)
User frame receive format designation, 3rd
1H: Format 1
273
11.3 Receive Program

b8 to b15
Transmissio
n setting
Independent
Address Dec. (Hex.)
Name
CH1
*1
8227 (2023H)
User frame receive format designation, 4th
1H: Format 1
8229 (2025H)
Exclusive format-1 received data count, 2nd
12 words
8230 (2026H)
Exclusive format-1 received data count, 3rd
0 word
8231 (2027H)
Exclusive format-1 received data count, 4th
2 words
Indicates the settings of the user frame No. to which the first and last frame Nos. are specified in the programs.
User frame No.
Registration code
3E8H/8001H
02H, 51H, 20H, 0AH, 3BH
3E9H/8002H
Registered data
STX, Q, (SP), Station No. of external device, ;
02H, 41H, 3BH
STX, A, ;
6H
06H
ACK
15H
15H
NAK
03H, FFH, F0H
ETX, Sum check code
41BH/8005H
274
Setting value
CHAPTER 11 DATA COMMUNICATIONS USING USER FRAMES
(1) Example of a sequence program when setting is done using the GX
Configurator-SC
For details on the INPUT instruction, refer to the User's Manual (Basic).
<Reads combination No.
\
>
Reads combinations of user
frames received.
11
Sets the reception channel to CH1.
Sets the allowable number of
reception data to 20.
<Reads reception data
>
Executes reception.
Sets the normal completion flag.
Sets the abnormal completion flag.
Q series C24
Address
ADH
AEH
(Sequence program)
Sets the receive user frame
to
B1H
registration No. *1
B2H
Buffer memory
User frame use control designation
(1st)
First frame
No. designation
to
(4th)
(1st)
Last frame
No. designation
Receive user frame
to
B5H
D2
Data receive result
258H Data reception result
D3
Receive data count
D10
Receive data
D0
1st set
to
(4th)
4th set
D1
11.3 Receive Program
25BH Receive user frame (
th set)
D11
Receive data
count storage
600H
601H
Dn
to
Receive area
Receive data storage
7FFH
(Sequence program)
Setting the user frame
receive format, etc.
*1
*1
2020H User frame
receive
to format
2023H designation
2024H Exclusive
format-1
to received data
2027H count designation
(1st)
to
1st set
(4th)
(1st)
to
4th set
(4th)
Page 267, Section 11.2.4
275
(2) Example of a sequence program when setting is not done using the GX
Configurator-SC
For details on the INPUT instruction, refer to the User's Manual (Basic).
<<User frame reception setting>>
<Frame No. 8001H setting
\
>
\
\
\
<Frame No. 8002H setting
\
>
\
\
<Frame No. 8005H setting
\
\
\
*1
276
Page 220, CHAPTER 9
>
User frame registration *1
CHAPTER 11 DATA COMMUNICATIONS USING USER FRAMES
<First frame No. (for reception) designation, 1st to 4th>
\
\
\
\
11
<Last frame No. (for reception) designation, 1st to 4th>
\
\
\
\
<Reception format designation 2 to 3, format-1 specified>
\
\
User frame setting for reception *2
\
<Format-1 received data count designation 2 to 3>
\
\
\
<Set to enable user frame>
11.3 Receive Program
\
<<Wait until data communications are enabled>>
\
<Reception is ready>
<<Start communications after M2 turns ON>>
<Reads combination No.>
\
Reads combination of received
user frames
Sets to CH1 for reception channel
Sets to 20 for No. of allowable
reception data
<Reads reception data>
Executes reception
Sets normal completion flag
Sets abnormal completion flag
*2
Page 267, Section 11.2.4
277
11.3.2
Application example for data reception using a combination
that specifies the first frame
In the description of this program example, conditions for data reception using a user frame are as follows.
(1) The Q series C24 I/O signals
The Q series C24 is installed at QCPU I/O signal addresses X/Y80 to X/Y9F.
(2) Q series C24 interface used in data communications with the external device
The Q series C24 CH1 side RS-232 interface is used.
(3) Data to be registered on the GX Configurator-SC "Transmission control and
other system settings" screen and "Non procedure system settings" screen
used for data communication using a user frame.
Change default values for the items listed in the table below.
Use default values for other items.
Set contents
Buffer memory address to
store registration value
Remarks
Word/byte
96H
Set to either one according to the example.
Yes/No
120H
When Yes, Additional code: 10H (DLE),
Transparent code: 02H (STX)
Do not convert
121H
Select "Do not convert" in the example.
6 to 511
A4H
Set according to the example.
None
A5H
Use
ADH
Yes
AEH to B5H
Format-0/ Format-1
2020H to 2023H
0H to FFFFH
2024H to 2027H
Item
Word/byte units designation
Receive transparent code
designation
ASCII-BIN conversion designation
Received data count
Receive complete code
User frame use enable/disable
designation
First frame No. designation
Last frame No. designation
*1
User frame receive format
designation
Exclusive format-1 received data
count designation
*1

 Page 279, Section 11.3.2 (3) (a) to
 Page 283, Section 11.3.2 (3) (e)
This program example gives the registered contents of the user frame No. specified as the first frame No. and the last
frame No.
[When receiving with a combination that specifies the first frame]
Item
First frame No.
Last frame No.
278
User frame No.
Registration code
Registered data contents
1st
3E8H
02H, 51H, 20H, 0AH, 3BH
STX, Q, (SP),
External device station No.,;
2nd
3E9H
02H, 41H, 3BH
STX, A, ;
3rd
6H
06H
ACK
4th
15H
15H
NAK
1st
41BH
03H, FFH, F0H
ETX, Sum check code
2nd
0H (none)

3rd
0H (none)

4th
0H (none)

CHAPTER 11 DATA COMMUNICATIONS USING USER FRAMES
(a) When receiving with a combination of the first frame, arbitrary data and last frame
(reception using Format-0)
Additional code (Removed by Q series C24.)
Transparent code
D S
L T
E X
When STX handled as
transparent code.
11
10H 02H
External device
02H51H 20H
0AH
0
1
2
C
A B C
R
L E
T
F X
(1234H)
The figure shown below is for word units.
3BH 30H31H 32H33H 02H 41H 42H 43H 34H12H 0DH0AH03H
First frame
(corresponds to
register No. 3E8H)
Programmable
controller CPU
S
3 T
X
Arbitrary data area
Sum check
code
S
T Q
X
External
device
station NO.
Head data
Receive data count
Word units
Receive byte count excluding frame and
additional code (12)/2=6
Byte units
Receive byte count excluding frame and
additional code (12)
EEH
ADH
Last frame
(corresponds to
register No.41BH)
AEH
AFH
Reception data
read request
X83
Programmable
controller CPU
B0H
B1H
INPUT
3E9H
6H
15H
ON
M1
Abnormal
completion
Normal
completion
1 scan
2021H
2022H
2023H
Reception data read request
0H
0H
1H
1H
(2nd = Format-0)
(3rd = Format-1)
(4th = Format-1)
Exclusive format-1
received data count
(1st)
2024H
0H
2025H
0H
(2nd)
2026H
0H
(3rd)
2027H
2H
(4th)
Buffer memory
41BH
User frame use control
designation
First frame No. designation
(1st)
(2nd)
(3rd)
(4th)
Last frame No. designation
(1st)
B3H
(None)
0H
(2nd)
B4H
(None)
0H
(3rd)
B5H
(None)
0H
(4th)
120H
(YES) (NO)
1002H/ 0H
121H
(Disable)
0H
25BH
600H
1H
00H , 06H
601H
(1) (0)
31H , 30H
602H
(3) (2)
33H , 32H
603H
(A) (STX)
41H , 02H
604H
(C) (B)
43H , 42H
605H
(1234H)
12H , 34H
606H
(LF) (CR)
0AH , 0DH
Receive transparent
code designation
ASCII-BIN conversion
designation
2)
Receive user frame
to D0
( th)
3)
to D3
Receive data count
Receive data
(arbitrary data
area)
4)
to D10
or after
Buffer memory
Reads combinations of user frames
received.
Sets to CH1 the reception channel.
Sets the allowable number of reception
data to 6.
Executes reception.
Sets the normal completion flag.
Sets the abnormal completion flag.
279
11.3 Receive Program
2020H
User frame receive
format designation
(1st = Format-0)
(Each 1st designated frame)
M0
ON
Status display device
at completion
3E8H
1)
B2H
Completion device
2H
(b) When receiving with a combination of the first frame and arbitrary data (reception
using Format-0)
Additional code (Removed by Q series C24.)
Transparent code
D
L
E
When STX handled
as transparent code.
S
T
X
Receive data count
Word units
Receive byte count excluding frame and additional code (12)/2=6
Byte units
Receive byte count excluding frame and additional code (12)
10H 02H
Head data
S
T
X
External device
A
;
0
1
2
S
3 T
X
C
L
R
F
A B C
The figure shown below is for word units.
(1234H)
A4H
02H41H 3BH30H 31H 32H 33H 02H 41H 42H 43H 34H 12H0DH0AH
Programmable
controller CPU
First frame
(corresponds to
register No. 3E9H)
ADH
Arbitrary data are
(Received data count)
AEH
AFH
Reception data
read request
X83
Programmable
controller CPU
B0H
B1H
INPUT
3E8H
3E9H
6H
15H
ON
M1
Abnormal
completion
Normal
completion
1 scan
2020H
2021H
2022H
2023H
Reception data read request
0H
0H
1H
1H
User frame receive
format designation
(1st = Format-0)
(2nd = Format-0)
41BH
(None)
0H
(4th)
120H
(YES) (NO)
1002H/ 0H
121H
(Disable)
0H
25BH
600H
2H
00H , 06H
(A) (STX)
41H , 02H
604H
(C) (B)
43H , 42H
(3rd)
605H
(1234H)
12H , 34H
(4th)
606H
(LF) (CR)
0AH , 0DH
0H
2027H
2H
Last frame No. designation
(1st)
B5H
603H
2026H
(4th)
(3rd)
(3) (2)
33H , 32H
(2nd)
(3rd)
B4H
602H
0H
(2nd)
(2nd)
(4th = Format-1)
2025H
First frame No. designation
(1st)
(None)
0H
601H
Exclusive format-1
received data count
designation
(1st)
User frame use control
designation
(None)
0H
(3rd = Format-1)
0H
Received data count
B3H
(1) (0)
31H , 30H
2024H
Buffer memory
(Each 2nd designated frame)
M0
ON
Status display device
at completion
2H
1)
B2H
Completion device
6H
Receive transparent
code designation
ASCII-BIN conversion
designation
2)
Receive user frame
to D0
( th)
Receive data
count
Receive data
(arbitrary data
area)
3)
to D3
4)
to D10
or after
Buffer memory
Reads combinations of user frames
received.
Sets to CH1 the reception channel.
Sets the allowable number of reception
data to 6.
Executes reception.
Sets the normal completion flag.
Sets the abnormal completion flag.
280
CHAPTER 11 DATA COMMUNICATIONS USING USER FRAMES
(c) When receiving with user frame only (reception using Format-0)
Head data
External device
02H51H 20H
0AH
;
E
T
X
3BH 03H
Sum check
code
S
T Q
X
External
device
station No.
(For reception using first frame and last frame combination)
Since there is no arbitrary data area,
the receive data count is [0].
The illustration below is for reception using
first frame and last frame combination.
ADH
03H
AEH
Programmable
controller CPU
First frame
(Correspond to
register No. 3E8H
and 41BH)
Last frame
AFH
B0H
X83
Programmable
controller CPU
Completion device
1)
B1H
B2H
INPUT
ON
M0
ON
Status display device
at completion
M1
Abnormal
completion
Normal
completion
1 scan
(Each 1st designated frame)
Reception data
read request
3E8H
3E9H
User frame use control
designation
First frame No. designation
(1st)
(3rd)
6H
(4th)
15H
41BH
Last frame No. designation
(1st)
(None)
0H
(2nd)
B4H
(None)
0H
(3rd)
B5H
(None)
0H
120H
(YES) (NO)
1002H/ 0H
121H
(Disable)
0H
600H
2020H
2021H
2022H
1H
00H , 00H
0H
0H
1H
1H
(4th)
Receive transparent
code designation
ASCII-BIN conversion
designation
Receive user frame 2)
to D0
( th)
3)
Receive data
to D3
count
User frame receive
format designation
(1st = Format-0)
(2nd = Format-0)
(3rd = Format-1)
(4th = Format-1)
2024H
0H
Exclusive format-1
received data count
(1st)
2025H
0H
(2nd)
2026H
0H
(3rd)
2027H
2H
(4th)
11.3 Receive Program
2023H
11
(2nd)
B3H
25BH
Reception data read request
2H
Buffer memory
Reads combinations of user frames
received.
Sets to CH1 the reception channel.
Sets the allowable number of reception
data to 6.
Executes reception.
Sets the normal completion flag.
Sets the abnormal completion flag.
281
(d) When receiving with first frame only (reception using Format-1)
Head data
A
C
K
Since it is designated to system 1 received data count "0",
the receive data count is [0].
The illustration below is for byte unit.
External device
06H
ADH
Programmable
controller CPU
First frame
(Correspond to
register No. 6H)
AEH
AFH
X83
Programmable
controller CPU
Completion device
B0H
B1H
INPUT
ON
M0
ON
Status display device M1
at completion
Abnormal
completion
Normal
completion
1 scan
(Each 3rd designated frame)
Reception data
read request
1)
B2H
3E8H
3E9H
6H
15H
41BH
User frame use control
designation
First frame No. designation
(1st)
(2nd)
(3rd)
(4th)
Last frame No. designation
(1st)
B3H
(None)
0H
(2nd)
B4H
(None)
0H
(3rd)
B5H
(None)
0H
120H
(YES) (NO)
1002H/ 0H
121H
(Disable)
0H
25BH
600H
2020H
2021H
2022H
2023H
Reception data read request
2H
3H
00H , 00H
0H
(4th)
Receive transparent
code designation
ASCII-BIN conversion
designation
Receive user frame 2)
to D0
( th)
3)
Receive data
to D3
count
User frame receive
format designation
(1st = Format-0)
0H
(2nd = Format-0)
1H
(3rd = Format-1)
1H
(4th = Format-1)
2024H
0H
Exclusive format-1
received data count
(1st)
2025H
0H
(2nd)
2026H
0H
(3rd)
2027H
2H
(4th)
Buffer memory
Reads combinations of user frames
received.
Sets to CH1 the reception channel.
Sets the allowable number of reception
data to 6.
Executes reception.
Sets the normal completion flag.
Sets the abnormal completion flag.
282
CHAPTER 11 DATA COMMUNICATIONS USING USER FRAMES
(e) When receiving with a combination of the first frame and arbitrary data (Exclusive
format-1 dedicated received data count) (reception using Format-1)
Receive data count
Word units
Receive byte count excluding frame and
additional code (2)/2=1
Byte units
Receive byte count excluding frame and
additional code (2)
Head data
N
A
K
(0022)
External device
15H
Programmable
controller CPU
The illustration below is for byte unit.
22H 00H
ADH
Arbitrary data area
AEH
First frame
(Correspond to
register No. 15H)
Programmable
controller CPU
AFH
1)
B0H
B1H
INPUT
ON
M0
ON
Status display device
M1
at completion
Abnormal
completion
Normal completion
1 scan
(Each 4th designated frame)
Reception data read X83
request
Completion device
11
B2H
2H
3E8H
User frame use control
designation
First frame No. designation
(1st)
3E9H
(2nd)
6H
(3rd)
15H
41BH
(4th)
Last frame No. designation
(1st)
B3H
(None)
0H
(2nd)
B4H
(None)
0H
(3rd)
B5H
(None)
0H
120H
121H
25BH
600H
2020H
2021H
2022H
2023H
4H
(4th)
Receive transparent
code designation
ASCII-BIN conversion
designation
Receive user frame 2)
( th)
Receive data count
00H , 02H
(0022H)
00H, 22H
0H
0H
1H
1H
Receive data
4)
(arbitrary data area)
User frame receive
format designation
(1st = Format-0)
to D0
to D3
to D10
(2nd = Format-0)
(3rd = Format-1)
(4th = Format-1)
Exclusive format-1
received data count
(1st)
2024H
0H
2025H
0H
(2nd)
2026H
0H
(3rd)
2H
(4th)
2027H
3)
Buffer memory
Reception data read request
Reads combinations of user frames
received.
Sets CH1 to the reception channel.
Sets the allowable number of reception
data to 6.
Executes reception.
Sets the normal completion flag.
Sets the abnormal completion flag.
283
11.3 Receive Program
601H
(YES) (NO)
1002H/ 0H
(Disable)
0H
11.3.3
Application example for data reception using a combination
that does not specify the first frame
In the description of this program example, conditions for data reception using a user frame are as follows.
(1) The Q series C24 I/O signals
The Q series C24 is installed at QCPU I/O signal addresses X/Y80 to X/Y9F.
(2) Q series C24 interface used in data communications with the external device
The Q series C24 CH1 side RS-232 interface is used.
(3) Data to be registered on the GX Configurator-SC "Transmission control and
other system settings" screen and "Non procedure system settings" screen
used for data communication using a user frame.
Change default values for the items listed in the table below.
Use default values for other items.
Set contents
Buffer memory address to
store registration value
Word/byte
96H
The unit is set to "Word" in the example.
Yes
120H
Additional code: 10H (DLE),
Transparent code: 02H (STX)
Do not convert
121H
Select "Do not convert" in the example.
6 to 511
A4H
Set according to the example.
None
A5H
Use
ADH
First frame No. designation*1
None
AEH to B1H
Last frame No. designation*1
Yes
B2H to B5H
Format-0
2020H to 2023H
0H
2024H to 2027H
Item
Word/byte units designation
Receive transparent code
designation
ASCII-BIN conversion designation
Received data count
Receive complete code
User frame use enable/disable
designation
User frame receive format
designation
Exclusive format-1 received data
count designation
*1
Remarks

Page 285, Section 11.3.3 (3) (a)
Page 285, Section 11.3.3 (3) (a)
Specify Format-0 for a combination that
does not specify the first frame.
This program example gives the registered contents of the user frame No. specified as the first frame No. and the last
frame No.
[When receiving with a combination that does not specify the first frame]
Item
User frame No.
First frame No.
Last frame No.
284
Registered code
Registered data contents
0H (none)

2nd
0H (none)

3rd
0H (none)

4th
0H (none)

1st
1st
419H
2nd
0H (none)
3BH, 04H

;, E0T
3rd
0H (none)

4th
0H (none)

CHAPTER 11 DATA COMMUNICATIONS USING USER FRAMES
(a) When receiving using arbitrary data and last frame combination. (reception using
Format-0)
Additional code (Removed by the Q series C24.)
Transparent code
D S
L T
E X
When STX is handled
as transparent code.
11
Receive data count
Word units
Receive byte count excluding frame and
additional code (12)/2=6
Byte units
Receive byte count excluding frame and
additional code (12)
10H 02H
Head data
0
1
2
S
3 T
X
External device
C
L
R
F
A B C
E
; O
T
(1234H)
The illustration below is for word units.
30H 31H 32H 33H 02H 41H 42H 43H 34H 12H 0DH0AH3BH 04H
Programmable
controller CPU
ADH
Last frame
Arbitrary data area
(Corresponds to register
No.419H)
AEH
AFH
Reception data read
X3
request
Programmable
controller CPU
1)
INPUT
(None)
0H
(None)
0H
B0H
(None)
0H
B1H
(None)
0H
ON
B2H
M0
ON
Abnormal
completion
Status display device
M1
at completion
Normal completion
1 scan
2021H
2022H
2023H
0H
User frame receive
format designation
(1st = Format-0)
(2nd = Format-0)
0H
(3rd = Format-1)
0H
(4th = Format-1)
Exclusive Format-1
received data count
(1st)
0H
2025H
0H
(2nd)
2026H
0H
(3rd)
2027H
0H
(4th)
Buffer memory
(2nd)
(3rd)
(4th)
Last frame No. designation
(1st)
(None)
0H
(2nd)
B4H
(None)
0H
(3rd)
B5H
120H
121H
25BH
601H
2024H
First frame No. designation
(1st)
B3H
600H
0H
419H
User frame use control
designation
602H
603H
604H
605H
606H
(None)
0H
(YES)
1002H
(Disable)
0H
1H
(4th)
Receive transparent
code designation
ASCII-BIN conversion
designation
Receive user frame 2)
(
To D0
th)
3)
00H , 06H
(1) (0)
31H , 30H
(3) (2)
33H , 32H
(A) (STX)
41H , 02H
(C) (B)
43H , 42H
(1234H)
12H , 34H
(LF) (CR)
0AH , 0DH
Receive data count
Receive data
(arbitrary data
area)
To D3
4)
To D10
or after
Buffer memory
Reception data read request
Reads combinations of user frames
received.
Sets CH1 to the reception channel.
Sets the allowable number of reception
data to 6.
Executes reception.
Sets the normal completion flag.
Sets the abnormal completion flag.
285
11.3 Receive Program
2020H
(Each 1st designated frame)
Completion device
2H
11.4
Data Transmission
This section explains the arrangement of the transmission data and transmission procedure when transmitting data
using a user frame.
11.4.1
Send data
The following describes the data list, codes, and handling of the Q series C24 send data during user frame data
transmission.
(1) Send data list
Only the data list combinations shown below are allowed during user frame data transmission.
Arbitrary data area
(Send data designation area data)
User frame (first n frames)
Data name
Combination
User frame
(first n frames)
Arbitrary data area
User frame
(last m frames)
1)
¨
¨
¨
2)
¨
¨
4)
Note
Total 99 frames
¨
3)
User frame (last m frames)
¨
¨
Total 100 frames
¨: Designated data exists
(When ASCII-BIN conversion disabled)
*2
Codes that can
be designated
Codes when
transmitting
Note
00H to FFH
Added by the Q series C24.
00H to FFH
Transmission area data.
(When ASCII-BIN conversion enabled)
Codes that can
be designated
0H to 9H, AH to FH
30H to 39H,
41H to 46H
0H to 9H, AH to FH
30H to 39H,
41H to 46H
*1
*1
*2
286
Codes when
transmitting
Note
Added by the Q series C24.
The codes shown at the left
are 4-bit codes.
Transmission area data.
The codes shown at the left at
are 4-bit codes.
Four bits of 0H to FH data are converted to 30H to 39H and 41H to 46H ASCII data and transmitted as the data codes of
the data to be transmitted (including the transparent code data).
Send data arbitrary data area
• When the send data count designated by the programmable controller CPU during transmission in byte units is an
odd number of bytes, the data of the lower byte of the last send data storage location of the send data storage
area are transmitted.
• When ASCII-BIN conversion is enabled, the data to be transmitted is transmitted as 2 characters/byte.
CHAPTER 11 DATA COMMUNICATIONS USING USER FRAMES
Handling of the Q series C24 send data
● The data of the user frame and the data of the transmission area designated from the programmable controller CPU are
transmitted in the contents and order set in the buffer memory send user frame designation area.
● For the user frame section and arbitrary data section, the data can be sent as ASCII code using the ASCII-BIN
conversion. For more details on the ASCII-BIN conversion, see Page 319, CHAPTER 13.
● If send transparent code is designated, the additional code data is added in front of the transparent code/additional code
in the data of the designated area during transmission and transmitted.
11
11.4 Data Transmission
287
11.4.2
Transmission procedure
The following describes the transmission procedure when a message containing user frames is transmitted to the
external device.
Procedure
External device
User frame
(1st)
Programmable
controller CPU (*1)
User frame
(nth)
Arbitrary data
area
[Transmission
area data]
User frame
(mth)
User frame
(±th)
(*2)
TO
Programmable
controller CPU
PRR
ON
Completion device
ON
Status display device
at completion
(*3)
Abnormal
completion
Normal
completion
1 scan
*1
*2
*3
288
Designates the data of the user frame number to send.
Programmable controller CPU processing
Before issuing a send request to the Q series C24, designate (write) the following data.
• Transmission user frame designation area: User frame No., transmission method and transmission order
registered in the Q series C24
• Transmission area (Buffer memory): User data corresponding to transmit message arbitrary data area
When a transmission data count error or data transmission error is generated, the Q series C24 stores the error code to
the data transmission result storage area and turns on the transmission abnormal end signal (Xn1).
CHAPTER 11 DATA COMMUNICATIONS USING USER FRAMES
11.4.3
Settings for transmission user frames
These settings are required for sending data to an external device via user frames and the non procedure protocol.
These settings are made from the GX Configurator-SC or the programmable controller CPU.
(1) Settings via GX Configurator-SC
11
Perform settings on the following screen to send data using user frames.
• "Non procedure system setting" screen
• "Transmission user frame No. designation system setting" screen
For setting contents on each screen, see Page 289, Section 11.4.3 (2).
(2) Settings via the programmable controller CPU
(a) How to designate and write transmission data when transmitting via user frames
For arbitrary data section when sending a combination of user frames and arbitrary data section, the
transmission data count and transmission data are written in the transmission area (the same as when sending
them in an arbitrary format.)
User frames are registered using the GX Configurator-SC. Or, the user frame registration number to be sent is
written from the programmable controller CPU to the transmission user frame designation area of the buffer
memory as shown in the diagram below.
After executing registration/write, the Q series C24 transmits the designated data in the designated order upon
execution of the PRR instruction.
11.4 Data Transmission
289
Sending data in the following sequence
Sending
sequence
Transmission data type
User frame No.
1
User frame
2H (2)
2
User frame
3E82H (1000)
3
Arbitrary data
4
02H (STX)
8000H (-32768)
User frame
400H (1024)
Address
Buffer memory
B6H 0 or the following frame designation No
To the
external device
Contents of sent/registered data
00H, 3BH (station No., ":")
41H, 42H, 43H, 44H ("ABCD")
03H, FFH, F6H, 0DH, 0AH
(ETX, Sum check, CR, LF)
(Transmission user frame designation area)
…… User frame being transmitted designation No. area
B7H
0
…… CR/LF output designation area
B8H
1
…… Output head pointer designation area
B9H
4
…… Output head pointer designation area
BAH
2H (1st)
BBH
3E8H (2nd)
BCH
8000H (3rd) *1
BDH
400H (4th)
BEH
0H (5th)
BFH
0H (6th)
…… Transmission count designation area
(Transmission area)
2 or 4
400H
401H
42H(B)
,
41H(A)
402H
44H(D)
,
43H(C)
…… Transmission data count (word unit/byte unit)
…… Transmission data
(When the ASCII-BIN conversion is not performed)
S
T
X
User frame
(2nd)
Station No.
1st
Arbitrary data
(;)
(4th)
A
B
C
D
E
T
X
Sum check
User frame
C
L
R
F
* Figure at left is for byte units.
For word units, the optional data section is sent in the sequence "ABCD."
02H 01H 3BH 41H 42H 43H 44H 03H 4BH 0DH 0AH
2H
3E8H
8000H
400H
Corresponding frame No.
*1
290
When sending data that is written in the transmission area, use 8000H as a temporary user frame number. ( Page
291, Section 11.4.3 (2) (b))
CHAPTER 11 DATA COMMUNICATIONS USING USER FRAMES
(b) Transmission user frame designation
The following explains application of the buffer memory to be used when sending data using user frames,
along with the designated and stored values.
• User frame being transmitted storage area (addresses: B6H/156H)
What number of the transmission frame number designation area is being sent is stored in the data
transmission via user frames.
b15
Buffer memory address
0H(
1H to 64H(
to
11
b0
B6H
0H to 64H
(CH1 side)
156H
0H to 64H
(CH2 side)
0) : Not sent
1 to 100) : User frame being transmitted designation No. (nth number)
• CR/LF output designation area (addresses: B7H/157H)
When sending a user frame or arbitrary data that does not contain a CR/LF, designate whether a CR+LF will be
sent each time a user frame or arbitrary data is sent.
b15
Buffer memory address
to
b0
B7H
0 to 1
(CH1 side)
157H
0 to 1
(CH2 side)
0: Do not send
1: Send
• Output head pointer designation area (addresses: B8H /158H)
Write the head position (th number) in the transmission frame No. designation area for writing the registration
number of the user frame to be sent.
to
11.4 Data Transmission
b15
Buffer memory address
b0
B8H
0 to 100
(CH1 side)
158H
0 to 100
(CH2 side)
0 : No designation
1 : Send from the first
to
to
100 : Send from the 100th
Remark
Transmission using a user frame cannot be performed when the value of the output head pointer designation area is "0".
291
• Output count designation area (addresses: B9H/159H)
Write the output count of the user frames to be sent from the position designate in the output head pointer
designation area.
b15
Buffer memory address
to
b0
B9H
0 to 100
(CH1 side)
159H
0 to 100
(CH2 side)
0 : No designation
1 : Transmit 1 frame
to
to
100 : Transmit 100 frames
Remark
The operation is completed normally without data transmission if the value for the output count designation area is "0."
• Transmission frame No. designation area (addresses: BAH to 11DH/15AH to 1BDH)
• Write the user frame No. to be sent in the order in which they are output from the position designated in
the output head pointer designation area.
• When sending data that is written in the transmission area, use 8000H as a temporary user frame number.
• By designating user frame number 8000H, the Q series C24 transmits the data of the transmission data
designation area for the data count designated in the transmission data count designation area.
Buffer memory address
BAH
0H to 801FH(1st)
to
to
11DH
0H to 801FH(100th)
15AH
0H to 801FH(1st)
to
to
1BDH
0H to 801FH(100th)
(CH1 side)
(CH2 side)
Specifies the following user frame No. for the data to be sent.
Note that the No. on the right side of the user frame No. below is the No. used for transmission without ASCII-BIN conversion for
only the data of any frame section when transmission data is converted into ASCII-binary data
and transmitted. See Chapters 12 and 13 for details.
0H : No transmission designation. (No additional transmission is allowed.)
1H to 3E7H/4001H to 43E7H : Transmits the default frame having the designated number.
3E8H to 4AFH/43E8H to 44AFH : Transmits the user frame having the designated number. (For flash ROM registration)
8000H/C000H : Transmits data in the transmission area of the buffer memory.
8001H to 801FH/C001H to C01FH : Transmits the user frame having the designated number. (For buffer memory registration)
The following transmission can be performed by adding 4000H to the registered user frame No. and specifying this number.
• When ASCII-BIN conversion is designated, a specified frame can be sent without the conversion. ( Page 321,
Section 13.3)
• A specified frame can be transmitted without adding the additional code for the send transparent code
designation. ( Page 299, Section 12.3)
292
CHAPTER 11 DATA COMMUNICATIONS USING USER FRAMES
11.5
Transmission Program
The following are examples of a sequence program when the user frame (four) and transmission area data are
transmitted.
In the description of the sample programs, data transmission using user frames is described for the following
11
conditions case:
• The Q series C24 I/O signals: The Q series C24 installed at QCPU I/O signal addresses X/Y80 to X/Y9F.
• The Q series C24 interface used in data communications with the external device: The Q series C24 CH1
RS-232 interface
• Switch setting using GX Developer: Set the following setting values on the "intelligent functional module
switch setting" screen.
Setting item
Setting value
CH1 Transmission setting
Switch 1
CH1 Communication rate setting
CH2 Transmission setting
Switch 3

Set according to the external device.
CH1 Communication protocol
setting
Switch 2
Remarks
CH2 Communication rate setting
0006H
Nonprocedural protocol
0000H
Not used
Switch 4
CH2 Communication protocol
setting
0000H
Switch 5
Station No. setting
0001H
Q series C24 station No.
(used in the user frame)
• Data to be registered on the GX Configurator-SC's "Transmission control and others system setting" screen
and the "Non procedure system settings" screen for data communication via user frames
• Use default settings for other items.
• In example of Page 295, Section 11.5 (2), the transmission frame No. is not registered using the GX
Configurator-SC. (It is registered using a sequence program.)
Item
Word/byte units designation
Set contents
Buffer memory address to
store registration value
Byte
96H
Send transparent code designation
No
11FH
ASCII-BIN conversion designation
Disable
121H
Transmission frame No. designation
1st
3F2H
BAH
Transmission frame No. designation
2nd
3F3H
BBH
Transmission frame No. designation
3rd
8001H
BCH
Transmission frame No. designation
4th
8000H
BDH
Transmission frame No. designation
5th
41BH
BEH
Remarks

Additional code: 10H (DLE),
Transparent code: 02H (STX)

Page 294, Section 11.5 (1)
293
11.5 Transmission Program
• Change the default values for the items listed in the table below.
(1) Sequence program example when setting is done with GX Configurator-SC
For further details on the PRR instruction, see Page 369, CHAPTER 17.
Programmable
controller CPU side
02H 51H
Registration No. of
the corresponding
user frame
0AH
01H
(Total number)
;
T
O
T
A
L
;
(012DH)
3BH 54H4FH 54H 41H 4CH3BH
3F2H
(First specification)
2DH
3F3H
(Second specification)
Transmission area data
(arbitrary data section)
(1234H)
01H
34H
8001H
(Third specification)
(56ABH)
12H
ABH
56H
8000H
(Fourth specification)
Transmission
instruction
Programmable
controller CPU
ON
Abnormal
completion
Status display device
at completion
Normal
completion
One scan
User frame No. being transmitted
B7H
(Do not transmit)
0H
CR/LF output designation
BAH
BBH
BCH
BDH
BEH
BFH
C0H
C1H
C2H
11FH
(Yes) (No)
1002H/ 0DH
Send transparent code designation
121H
(No conversion)
0H
ASCII-BIN conversion designation
401H
402H
41BH
(Fifth specification)
(Not transmitted)
(Sending)
0H/Other than 0H
B9H
400H
37H
(1st)
Output head pointer designation
1H
ON
Completion device
*1
03H
* Four bytes of data in the transmission
area are sent as is.
(4 byte units in the left diagram.)
B6H
B8H
PRR
E
T
X
Sum check
code
Q
Q series C24
Station No.
S
T
X
External device
Station No.
External device side
Transmission area
00H , 04H
(transmission data count designation)
(1234H)
12H , 34H
(transmission data)
(56ABH)
56H , ABH
Buffer memory
C3H
C4H
C5H
C6H
C7H
*1 0002H for word unit
Output count designation
5H
3F2H
Transmission frame No. designation (1st)
3F3H
8001H
8000H
41BH
0H
3F4H
8002H
3F5H
8003H
3F6H
8004H
41BH
0H
(2nd)
(3rd)
(4th)
(5th)
(6th)
(7th)
(8th)
(9th)
(10th)
(11th)
(12th)
(13th)
(14th)
Buffer memory
Transmission instruction
Sets arbitrary transmission data in D1 to D2.
Sets arbitrary transmission data in the
transmission area.
Sets CH1 to the transmission channel.
Sets the output head pointer
Sets the output head count
Executes transmission
Sets normal completion flag.
Sets abnormal completion flag.
294
CHAPTER 11 DATA COMMUNICATIONS USING USER FRAMES
(2) Sequence program example when setting is not done with GX Configurator-SC
The following is the method of data transmission without performing the transmission frame No. designation
using the GX Configurator-SC.
For further details on the PRR instruction, see Page 369, CHAPTER 17.
11
Sets arbitrary transmission data.
Sets the number of transmitted data.
Sets the transmission user frames in D5 to D9.
Sets output frame No. in the buffer memory.
Sets CH1 to the transmission channel.
Sets to no CR/LF output.
Sets the output head pointer.
Sets the output counter.
Executes user frame transmission.
Sets normal completion flag.
Sets abnormal completion flag.
Normal end
Abnormal end
D0 Send data count
(0004H)
D1
(3412H)
D2
Send data
(AB56H)
Send data count
(0004H)
(3412H)
Send data
Transmission frame No.
(AB56H)
D5 Transmission frame No.
(03F2H)
D6
(03F3H)
(03F3H)
D7
(8001H)
(8001H)
D8
(8000H)
(8000H)
D9
(041BH)
(041BH)
D10
(0000H)
D11 Interface No.
(0001H)
Interface No.
D12 Transmission result
(0000H)
Transmission result (other than 0000H)
D13 CR/LF output
(0000H)
CR/LF output
(0000H)
D14 Output head pointer
(0001H)
Output head pointer
(0001H)
D15 Output counter
(0005H)
Output counter
(0005H)
(03F2H)
(0000H)
(0001H)
295
11.5 Transmission Program
Clears the device in which transmission results
are stored.
CHAPTER 12 TRANSPARENT CODES AND
ADDITIONAL CODES
Transparent codes and additional codes are used during data communication with an external device to send/receive
one-byte data for transmission control on the external device side as user data.
Transparent codes and additional codes are handled in data communication using the non procedure or bidirectional
protocol.
• Transparent code: One-byte data for transmission control.
• Additional code: During transmission, one-byte data added preceding the transparent code and additional
code data. During reception, one-byte data deleted (the immediately succeeding one-byte data is processed
for reception).
12.1
Handling the Transparent Code and Additional Code
Data
The following explains how the Q series C24 handles transparent codes and additional codes during data
communication using the non procedure or bidirectional protocol.
The range of additional code data that is added or deleted is explained in Page 299, Section 12.3 and Page 309,
Section 12.5.
(1) During data transmission
Additional code data is added immediately before the transparent code and additional code data set for
transmission.
Buffer memory
Transparent
code
Transparent
code
Additional
code
Send
(2) During data reception
When additional code data set for reception is detected, the additional code data is removed and the immediately
succeeding one-byte data is processed for reception.
Buffer memory
296
Arbitrary
code
Additional
code
Arbitrary
code
Receive
CHAPTER 12 TRANSPARENT CODES AND ADDITIONAL CODES
(3) During data communication using the ASCII-BIN conversion
The handling of transparent codes and additional codes is done for data after ASCII-BIN conversion during
transmission and data immediately before the conversion during reception.
When communicating using an arbitrary format of the non procedure protocol
External
device side
1
2
0
2
3
D
L
E
A
B
C
Receive
31H 32H 30H 32H 33H 10H 41H 42H 43H
Conversion
Send
Arbitrary data section
Delete Additional
Addition code
Buffer memory (transmission area/reception area)
Head data
(H) (L)
(0002H)
00H , 02H
(0212H)
02H , 12H
(BC3AH)
BCH , 3AH
12
Transmission data
count/Receive data
count
Transmission data/
receive data
(The data count is in word units)
(For 41H)
(For 10H)
Transparent code
Additional code
12.1 Handling the Transparent Code and Additional Code Data
297
12.2
Registering Transparent Codes and Additional Codes
To control transparent codes and additional codes for data to be sent/received with the non procedure or bidirectional
protocol, it is necessary to perform settings in the Q series C24 prior to data communication.
The following explains the registration of transparent and additional codes.
(1) For each interface, 10 combinations and one combination of transparent
codes and additional codes can be set for transmission and reception,
respectively.
(2) Transparent and additional codes are registered on the GX Configurator-SC's
"Transmission control and others system setting" screen.
If additional data code is received during data reception, the Q series C24 will not treat the immediately succeeding one-byte
data as the following control data:
● Data received as the first frame and last frame of the user frames
Therefore, do not set the following:
(The code of the data described above cannot be designated as additional codes for data reception.)
• A receive user frame that contains additional code data for data reception
• The same reception complete code as the additional code data for data reception
298
CHAPTER 12 TRANSPARENT CODES AND ADDITIONAL CODES
12.3
Handling Transparent Codes and Additional Codes
during Non Procedure Protocol Data Communication
The following explains the handling of transparent codes and additional codes during non procedure protocol data
communication.
(1) The data designated by the additional code will be added to or deleted from the
data to be transmitted or received.
12
(2) The following shows the range of communication data for which processing of
transparent codes and additional codes is performed.
Applicable range during transmission
Message during
communication using
arbitrary format
Arbitrary data section
Applicable range during reception
Applicable range during transmission
Message during
communication using
user frames
User frame
(first frame)
Arbitrary
data
section
User frame
(last frame)
Applicable range during reception
(a) When an additional code set for reception is detected during data reception, the
additional code data is removed and the immediately succeeding one-byte data is
processed for reception as part of the receive data.
299
12.3 Handling Transparent Codes and Additional Codes during Non Procedure Protocol Data
Communication
The Q series C24 performs the following processing during data transmission and reception:
(b) When transparent code/additional code data set for transmission is detected during
data transmission, the additional code designation data is added immediately
before, and is then transmitted.
During data transmission using user frames, even if a transparent code or additional code has been specified
in the send transparent code designation area, it is possible to transmit data without adding the additional code
data to the user frame portion or arbitrary data.
When sending data without adding the additional code data specified by the send transparent code
designation, specify the user frame No. using the following method.
• Specify the number obtained by adding 4000H to the registered user frame No.
b15 b14 b13
to
b0
Frame No.
0: Conversion enable
1: Conversion disable
0: Frame registered in flash ROM
1: Frame registered in the buffer memory
When sending the data for the section designated by 4001H to 44AFH and C000H to C01FH, data will be sent
without conversion even if "Enable" has been specified in the ASCII-BIN conversion designation area. (
Page 321, Section 13.3)
300
No. of the use frame to be sent
Designation No. when sending data without adding the
additional code specified by the send transparent code
designation.
1H to 3E7H (1 to 999)
4001H to 43E7H (16385 to 17383)
3E8H to 4AFH (1000 to 1199)
43E8H to 44AFH (17384 to 17583)
8000H to 801FH (-32768 to -32737)
C000H to C01FH (-16384 to -16353)
CHAPTER 12 TRANSPARENT CODES AND ADDITIONAL CODES
(3) The following describes the processing steps taken by the Q series C24 when
performing communication with the transparent code designation and the
ASCII-BIN conversion enabled.
(a) Communication using arbitrary format
• Receiving
• If a receive transparent code is designated, the additional code designation data is deleted (removed).
• The arbitrary data section is stored in the reception area of the buffer memory. If the ASCII-BIN conversion
is designated, the data section is stored in the buffer memory after it has been converted to binary code
data.
12
• During reception of an arbitrary data section, if the reception-complete code data or the entire count of
receive data has been stored, a reception-data read is requested of the programmable controller CPU.
• Sending
• The transmission data designated from the programmable controller CPU (arbitrary data section of the
transmission message) is sent. If the ASCII-BIN conversion is designated, the transmission data section is
sent after it has been converted to binary code data.
• If a send transparent code is designated, additional code data is added preceding the transparent
code/additional code data, and is then transmitted.
External
device
Q series C24
(ASCII-BIN conversion designation)
(Transparent code designation)
No
Adding
additional
code
Yes
No
Data
reception
Yes
ASCII-BIN
conversion of
transmission data
Buffer memory
12.3 Handling Transparent Codes and Additional Codes during Non Procedure Protocol Data
Communication
Data
transmission
No
Transmission
area data
Yes
No
Delete
additional
code
Yes
ASCII-BIN
conversion of
arbitrary data
section
Check receive
complete code
and received
data count
Data to be stored
in the reception area
301
When ASCII-BIN conversion is not performed
External
device
Q series C24
(Communicating in an arbitrary format)
Head data
Buffer memory (transmission area/reception area)
D
L
E
Receive
12H 10H 02H 3AH BCH
(For 02H)
(H)
Delete Additional
Addition code
Send
Arbitrary data
section
(L)
(0002H)
00H , 02H
(0212H)
02H , 12H
(BC3AH)
BCH , 3AH
Transmission data
count/Receive data
count
Transmission data/
receive data
(The data count is in word units)
Transparent code
Additional code
(For 10H)
When ASCII-BIN conversion is performed
External
device
(Communicating in an arbitrary format)
2
0
2
3
D
L
E
A
B
C
31H 32H 30H 32H 33H 10H 41H 42H 43H
Receive
Conversion
Send
Arbitrary data section
Delete
Additional
Addition code
Buffer memory (transmission area/reception area)
Head data
1
Q series C24
(H)
(L)
(0002H)
00H , 02H
(0212H)
02H , 12H
(BC3AH)
BCH , 3AH
Transmission data
count/Receive data
count
Transmission data/
receive data
(The data count is in word units)
(For 41H)
(For 10H)
302
Transparent code
Additional code
CHAPTER 12 TRANSPARENT CODES AND ADDITIONAL CODES
(b) Communication using user frames
• Receiving
• Reception check of user frames (first frame, last frame) is performed.
• If a receive transparent code is designated, the additional code designation data is deleted (removed) from
the arbitrary data section.
• If a sum check code is designated in a user frame (last frame), the sum check code is calculated.
• The arbitrary data section is stored in the reception area of the buffer memory. If the ASCII-BIN conversion
is designated, the data section is stored in the buffer memory after it is converted to binary code data.
• During reception of an arbitrary data section, if the reception complete code or the entire count of received
data has been stored, or when a user frame (last frame) has been received, a receive data read is
12
requested of the programmable controller CPU.
• Sending
• The transmission data designated by a user frame or the programmable controller CPU (arbitrary data
section of the transmission message) is sent in the order designated by the user.
• If the ASCII-BIN conversion is designated, the applicable range of data is sent after data is converted to
ASCII code data. Also, if a send transparent code is designated, the applicable range of data is sent after
adding additional code data before the transparent code/additional code data.
External
device
Q series C24
(Transparent code designation) (Sum check code designation)
Data
transmission
Adding
additional
code
Yes
(ASCII-BIN conversion designation)
No
No
Calculating sum
check code using
user frames
Yes
No
ASCII-BIN
conversion of
transmission
data
Buffer memory
Data designated
in the transmission
frame No.
designation area
Yes
No
Data
reception
Check and
delete user
frames
Yes
No
Delete
additional
code
Yes
No
Calculate and check
sum check code
using user frames
Yes
ASCII-BIN
conversion of
arbitrary data
section
Check reception
complete code
and received
data count
Data stored in the
reception area
(Arbitrary data section only)
Explained above is how the Q series C24 processes communication data when enabling and disabling the communication
via the user-frame function, ASCII-BIN conversion function, and/or transparent code-designation communication function.
When communicating data to an external device, use this information as a reference in the selection of a communication
method.
303
12.3 Handling Transparent Codes and Additional Codes during Non Procedure Protocol Data
Communication
For Output count designation
12.4
Example of Data Communication Using the Non
Procedure Protocol
This section shows examples of data communication using the non procedure protocol when the following settings and
registrations are made.
(1) Settings via GX Developer
Perform the following settings on the "Intelligent function module switch setting" screen.
Setting item
Switch 1
Switch 2
Switch 3
CH1 Transmission setting
CH1 Communication rate setting
CH1 Communication protocol setting
CH2 Transmission setting
CH2 Communication rate setting
Setting value
Remarks
Set according to the
external device.

0006H
0000H
Switch 4
CH2 communication protocol setting
0000H
Switch 5
Station No. setting
0000H
Nonprocedural protocol
Not used
Q series C24 station number
(2) Settings via GX Configurator-SC
Register the following on the "Transmission control and others system setting" screen and the "Non procedure
system settings" screen.
For items other than those listed below, the default values are used.
Registration screen
Transmission control and other system
settings
Non procedure system settings
304
Setting item
Setting value
Remarks
Send transparent code designation 1st
combination
1002H
Transparent code: 02H (STX)
Additional code: 10H (DLE)
Send transparent code designation 2nd
combination
1003H
Transparent code: 03H (ETX)
Additional code: 10H (DLE)
Receive transparent code designation
1st combination
1002H
Transparent code: 02H (STX)
Additional code: 10H (DLE)
Received data count designation
0006H

CHAPTER 12 TRANSPARENT CODES AND ADDITIONAL CODES
12.4.1
Example of data reception
The following shows an example of storing receive data in the data register.
(1) Receiving based on the receive complete code
Additional code: 10H (DLE), transparent code: 02H (STX), complete code: 0D0AH (CR + LF)
Additional code (Q series C24 deletes)
Head data
Transparent code
0
External device
1
2
D S N
3 L T U A
E X L
L
C
L
R
F
12
For word unit:
Received byte count excluding additional code (12)/2=6
For byte unit:
Received byte count excluding additional code (12)
B
(1234H)
30H31H 32H 33H 10H 02H 00H 41H 42H 34H 12H 0DH0AH
Programmable
controller CPU
Reception data
read request
X83
Programmable
controller CPU
Received data count
is stored
INPUT
ON
Completion device
The following diagram is for word unit
M0
ON
Status display device M1
at completion
Abnormal
completion
Normal
completion
1 scan
600H
D2
00H , 06H
(1) (0)
31H , 30H
(3) (2)
33H , 32H
601H
602H
(B) (A)
42H , 41H
604H
D11
(3) (2)
33H , 32H
D12
(NULL) (STX)
00H , 02H
(B) (A)
42H, 41H
D13
605H (1234H , 34H)
12H
(LF) (CR)
0AH , 0DH
606H
(0) (0)
31H , 30H
D14
(1234H , 34H)
12H
D15
(LF) (CR)
0AH , 0DH
Buffer memory
Sequence program
device memory
Reception data read request
Sets CH1 to the reception channel
Sets the allowable number of
receive data to 6
Executes reception
Sets the normal completion flag
Sets the abnormal completion flag
When the receive transparent code designation is set to Enable and the ASCII-BIN conversion is set to Disable, the codes
for receivable data and those for receive data that is stored in the buffer memory's reception area are as follows:
Item
Receive transparent code designation
section
Additional code
Transparent
code
Arbitrary data section (including complete code)
Receivable codes
Codes stored in the reception area
01H to FFH
(Delete)
00H to FFH
00H to FFH
00H to FFH
00H to FFH
305
12.4 Example of Data Communication Using the Non Procedure Protocol
603H (NULL) (STX)
00H , 02H
00H , 06H
D10
(2) Receiving based on the completed data count
Additional code: 10H (DLE), transparent code: 02H (STX),
Completed data count: Six words or 12 bytes
Additional code (Q series C24 deletes)
Transparent code
Head data
0
External device side
1
2
D S N
3 L T U
E X L
L
C L
A
For word unit:
Received byte count excluding additional code (12)/2=6
For byte unit:
Received byte count excluding additional code (12)
B
R F
(1234H)
30H 31H 32H 33H 10H 02H 00H 41H 42H 34H12H 0DH0AH
Programmable
controller CPU side
Reception data read
request
X83
Programmable
controller CPU
Received data
count is stored
INPUT
ON
The following diagram is for word unit
Completion device
M0
ON
Status display device
M1
at completion
Abnormal
completion
Normal
completion
600H
D2
00H , 06H
00H , 06H
601H
(1) (0)
31H , 30H
D10
(0) (0)
31H , 30H
602H
(3) (2)
33H , 32H
D11
(3) (2)
33H , 32H
603H
(NULL) (STX)
00H , 02H
D12
(NULL) (STX)
00H , 02H
604H
(B) (A)
42H , 41H
D13
(B) (A)
42H , 41H
605H
(1234H)
12H , 34H
D14
(1234H)
12H , 34H
606H
(LF) (CR)
0AH , 0DH
D15
(LF) (CR)
0AH , 0DH
One scan
Buffer memory
Sequence program
device memory
Reception data read request
Sets CH1 to the reception
channel
Sets the allowable number of
receive data to 6
Executes reception
Sets the normal completion flag
Sets the abnormal completion flag
When the receive transparent code designation is set to Enable and the ASCII-BIN conversion is set to Disable, the codes
for receivable data and those for receive data that is stored in the buffer memory's reception area are as follows:
Item
Receive transparent code designation
section
Additional code
Transparent
code
Arbitrary data section (including complete code)
306
Receivable codes
Codes stored in the reception
area
01H to FFH
(Delete)
00H to FFH
00H to FFH
00H to FFH
00H to FFH
CHAPTER 12 TRANSPARENT CODES AND ADDITIONAL CODES
12.4.2
Example of data transmission
The following shows an example of data transmission.
• Additional code: 10H (DLE), transparent code: 02H (STX)
External device side
Additional code (Q series C24 deletes)
Head data
Transparent code
D S N
0 1 2 3 L T U A B
E X L
L
Programmable
controller CPU side
C L
For word unit:
Received byte count excluding additional code (12)/2=6
For byte unit:
Received byte count excluding additional code (12)
R F
(1234H)
30H 31H 32H 33H 10H 02H 00H 41H 42H 34H 12H 0DH0AH
Transmission
command
X50
Programmable
controller CPU
Completion device
12
OUTPUT
ON
Transmission
data count
M0
Abnormal
completion
ON
Status display device
M1
at completion
Normal
completion
The following diagram
is for word unit
One scan
D3
D11
D12
D13
D14
D15
400H
401H
402H
403H
404H
405H
406H
Sequence program
device memory
00H , 06H
(0) (0)
31H , 30H
(3) (2)
33H , 32H
(NULL) (STX)
00H , 02H
(B) (A)
42H , 41H
(1234H)
12H , 34H
(LF) (CR)
0AH , 0DH
12.4 Example of Data Communication Using the Non Procedure Protocol
Transmission data
D10
00H , 06H
(1) (0)
31H , 30H
(3) (2)
33H , 32H
(NULL) (STX)
00H , 02H
(B) (A)
42H , 41H
(1234H)
12H , 34H
(LF) (CR)
0AH , 0DH
Buffer memory
Transmission instruction
Sets transmission data in D10 to D15
Sets CH1 to the transmission channel
Sets the allowable number of
transmitting data to 6
Executes transmission
Sets normal completion flag
Sets abnormal completion flag
307
• Additional code: 10H (DLE), transparent code: 02H (STX) (1st group), Additional code: 10H (DLE),
transparent code: 03H (ETX) (2nd group)
External device side
Head data
Additional
code
(1st group)
Additional
code
(2nd group)
Transparent
code
(1st group)
Transparent
code
(1st group)
D S N
D E N C L
0 1 2 3 L T U A B L T U
E X L
E X L R F
L
L
Programmable
controller CPU side
For word unit:
Received byte count excluding additional code (12)/2=6
For byte unit:
Received byte count excluding additional code (12)
30H 31H32H 33H 10H 02H 00H 41H 42H 10H 03H 00H 0DH0AH
Transmission
command
X50
Programmable
controller CPU
Completion device
OUTPUT
ON
Transmission
data count
M0
Abnormal
completion
ON
Status display device
M1
at completion
Normal
completion
The following diagram
is for word unit
One scan
Transmission data
D3
00H , 06H
(1) (0)
D10
31H , 30H
(3) (2)
D11
33H , 32H
D12 (NULL) (STX)
00H , 02H
(B) (A)
D13
42H , 41H
D14 (NULL) (ETX)
00H , 03H
D15 (LF) (CR)
0AH , 0DH
Sequence program
device memory
400H
00H , 06H
(0) (0)
31H , 30H
(3) (2)
402H
33H , 32H
403H (NULL) (STX)
00H , 02H
(B) (A)
404H
42H , 41H
405H (NULL) (ETX)
00H , 03H
406H (LF) (CR)
0AH , 0DH
Buffer memory
401H
Transmission instruction
Sets transmission data in D10 to D15
Sets CH1 to the transmission channel
Sets the number of transmitting data to 6
Executes transmission
Sets normal completion flag
Sets abnormal completion flag
308
CHAPTER 12 TRANSPARENT CODES AND ADDITIONAL CODES
12.5
Handling Transparent Codes and Additional Codes
During Bidirectional Protocol Data Communication
The following explains the handling of transparent codes and additional codes during data communication using the
bidirectional protocol.
(1) The additional code designation data will be added to or deleted from the data
that is sent or received.
12
(2) Communication data for which transmission/reception processing of
transparent codes and additional codes is performed includes the message
data length, data section and error code.
Such processing is not performed for the head code (ENQ, ACK, NAK) and sum check code of a message.
*
Transmission sequence
A (When
C normal)
K
External device side
N
A
K
Error
code
L
Data
length
L
Data section
(Designated
transmission data)
H
Sum
check
code
L H
H
* Applicable data range
*
The Q series C24 performs the following processing during data transmission/reception.
(a) When an additional code set for reception is detected during data reception, the
additional code data is removed and the immediately succeeding one-byte data is
processed for reception as part of the receive data.
When transparent code/additional code data set for transmission is detected during transmission of a message
in response to data reception, the additional code designation data is added immediately before, and is then
transmitted.
(b) When transparent code/additional code data set for transmission is detected during
data transmission, the additional code designation data is added immediately
before, and is then transmitted.
When an additional code set for reception is detected while a message is being received in response to data
transmission, the additional code data is removed and the immediately succeeding one-byte data is processed
for reception as part of the receive data.
309
12.5 Handling Transparent Codes and Additional Codes During Bidirectional Protocol Data
Communication
Programmable
controller CPU
side
E
N
Q
(When
abnormal)
(c) Data having an additional code that is added or deleted cannot be included in the
data length, nor will it be used for the sum check code.
When ASCII-BIN conversion is not performed
Additional code
Transparent code
Message
E
N
Q
Data length
Sum
check
code
Data section
(0002H)
D
L
E
L
D
L
E
H
L
Additional code: 10H
Transparent code: 02H
Buffer memory
(H)
(L)
00H , 02H
H
02H , 12H
05H 10H 02H 00H 12H 10H 02H 3AH BCH 0CH 01H
BCH , 3AH
Transmission data count/
Receive data count
Transmission data/
receive data
(3) The following are the processing steps taken by the Q series C24 when
performing communication with the transparent code designation and ASCIIBIN conversion enabled.
Explained above is how the Q series C24 processes communication data, when enabling and disabling the ASCII-BIN
conversion function and/or transparent code designation communication function.
When communicating data to an external device, use this information as a reference in the selection of a communication
method.
(a) Receiving
• If a receive transparent code is designated, the additional code designation data is deleted (removed) from
the arbitrary data section.
• The arbitrary data section is stored in the reception area of the buffer memory. If the ASCII-BIN conversion is
designated, the data section is stored in the buffer memory after it is converted to binary code data.
• When the data section of the designated data length is received, a receive data read is requested of the
programmable controller CPU. If the sum check code is set to Enable in the transmission setting via GX
Developer switch settings, a reception data read is requested of the programmable controller CPU upon
reception of the sum check code.
External
device
Q series C24
(Transparent code designation)
Data
reception
Yes
Deleting
additional code
Response
transmission
Adding
additional code
Yes
(Error code section only)
No
310
(Sum check code setting)
No
No
(Arbitrary data section only)
(ASCII-BIN conversion designation)
No
Buffer memory
Deleting transmission
control code (ENQ)
Adding transmission
control code
(ACK/NAK)
Yes
Calculation and check of
sum check code
Yes
ASCII-BIN conversion of
data length, data section
ASCII-BIN conversion
of error code
Yes
No
Reception area
Reception
result
storage area
CHAPTER 12 TRANSPARENT CODES AND ADDITIONAL CODES
(b) Sending
• The transmission control code data is added to the transmission data designated by the programmable
controller CPU (arbitrary data section of the transmission message), and that transmission data is
transmitted. If ASCII-BIN conversion is designated, the transmission data is sent after it is converted to
ASCII code data.
• If the sum check code is set to Enable in the transmission setting via GX Developer switch settings, the code
will be calculated from the transmission message and added to the transmission message.
• If a send transparent code is designated, additional code data is added preceding the transparent
code/additional code data for the arbitrary data section, and is then sent.
External
device
12
Q series C24
(Transparent code designation)
Data
transmission
(Sum check code setting)
No
(Arbitrary data section only)
Adding
additional code
Response
reception
Yes
No
Buffer memory
Yes
Adding transmission
control code (ENQ)
Deleting
additional code
Deleting transmission
control code
(ACK/NAK)
(Error code section only)
No
(ASCII-BIN conversion designation)
No
Calculation and check of
sum check code
Yes
ASCII-BIN conversion of
transmission data count
and transmission data
Yes
Yes
ASCII-BIN conversion
of error code
Transmission
area
Transmission
result storage
area
No
12.5 Handling Transparent Codes and Additional Codes During Bidirectional Protocol Data
Communication
311
The following example shows the data arrangement when data is sent and received. (The communication
section of the response message is omitted.)
(When the ASCII-BIN conversion is not performed)
External
device
Q series C24
Head data
Buffer memory (transmission area/reception area)
E Data length
N
Q
D
L L H
E
Send
Sum
check
code
Data section
D
L
E
L
H
Receive
05H 10H 02H 00H 12H 10H 02H 3AH BCH 0CH 01H
(H)
(L)
(0002H)
00H , 02H
(0212H)
02H , 12H
(BC3AH)
BCH , 3AH
Delete Additional
Addition code
Arbitrary data section
Transmission data
count/Receive data
count
Transmission data/
receive data
(The data count is in word units)
Additional code
(For 10H)
Transparent code
(For 02H)
(When the ASCII-BIN conversion is performed)
External
device
Q series C24
Head data
Data length
L
0
Data section
H
2
0
0
1
2
0
2
3
D
L
E
Sum
check
code
L
A
B
Send
H
C
05H 30H 32H 30H 30H 31H 32H 30H 32H 33H 10H 41H 42H 43H 80H 02H
Receive
Conversion
E
N
Q
Delete Additional
Addition code
Buffer memory (transmission area/reception area)
Arbitrary data section
(H)
(L)
(0002H)
00H , 02H
(0212H)
02H , 12H
(BC3AH)
BCH , 3AH
Transmission data
count/Receive data
count
Transmission data/
receive data
(The data count is in word units)
(For 41H)
(For 10H)
312
Transparent code
Additional code
CHAPTER 12 TRANSPARENT CODES AND ADDITIONAL CODES
12.6
Example of Data Communication Using the Bidirectional
Protocol
This section shows examples of the bidirectional protocol data communication when the following settings and
registrations are made.
(1) Settings via GX Developer
Perform the following settings on the "Switch setting" screen.
Setting item
Switch 1
Switch 2
Switch 3
CH1 Transmission setting
CH1 Communication rate setting
Setting value
Remarks
Set according to the external
device.

CH1 Communication protocol setting
CH2 Transmission setting
CH2 Communication rate setting
0007H
0000H
Switch 4
CH2 Communication protocol setting
0000H
Switch 5
Station No. setting
0000H
12
Bidirectional protocol
Not used
Q series C24 station number
(2) Settings via GX Configurator-SC
Register the following settings on the "Transmission control and others system setting" screen.
For items other than those listed below, the default values are used.
Registration screen
Setting value
Remarks
Send transparent code designation
1st combination
1002H
Transparent code: 02H (STX)
Additional code: 10H (DLE)
Send transparent code designation
2nd combination
1003H
Transparent code: 03H (ETX)
Additional code: 10H (DLE)
Receive transparent code
designation 1st combination
1002H
Transparent code: 02H (STX)
Additional code: 10H (DLE)
313
12.6 Example of Data Communication Using the Bidirectional Protocol
Transmission control and other
system settings
Setting item
12.6.1
Example of data reception
The following shows an example of storing receive data in the data register.
(1) When the receive transparent code designation is set to Enable and the ASCIIBIN conversion is set to Disable
Additional code: 10H (DLE), transparent code: 02H (STX)
Additional code (the Q series C24 deletes.)
Transparent code
E
N
Q
External device side
Data
length
(0004H)
L
H
Data section
D
L
E
(1102H) A
C
L
R
F
B (1234H)
Sum
check
code
L
H
05H 04H00H 10H 02H 11H 41H 42H 34H 12H 0DH0AHF7H00H
A
C
K
Programmable
controller CPU side
06H
Reception data read X83
request
Programmable
controller CPU
Completion device
Data length (receive data count):
Excluding additional codes
For word unit : 0004H
BIDIN
ON
M0
ON
Status display device M1
at completion
Abnormal
completion
The following diagram is for word unit
Normal completion
Data length
One scan
600H
D3
00H , 04H
601H
D10
(1102H)
11H , 02H
602H
(B) (A)
42H , 41H
D11
(B) (A)
42H , 41H
603H
(1234H)
12H , 34H
D12
(1234H)
12H , 34H
Data section
604H
(LF) (CR)
0AH, 0DH
Buffer memory
D13
Reception data read request
Sets CH1 to the reception
channel
Sets the allowable number of
receive data to 6
Executes reception
Sets the normal completion flag
Sets the abnormal completion flag
314
00H , 04H
(1102H)
11H , 02H
(LF) (CR)
0AH , 0DH
Sequence program
device memory
CHAPTER 12 TRANSPARENT CODES AND ADDITIONAL CODES
● When the receive transparent code designation is set to Enable and ASCII-BIN conversion is set to Disable, the codes for
receivable arbitrary data sections and those for receive data that is stored in the buffer memory's reception area are as
follows:
Item
Receive transparent code designation section
Data length, data section
Additional code
Transparent code
Receivable codes
Codes stored in the reception
area
01H to FFH
(Delete)
00H to FFH
00H to FFH
● When the data length used is in byte units and the data length is an odd byte, 00H will be stored in the upper byte of the
last data-storage position in the reception area.
12
12.6 Example of Data Communication Using the Bidirectional Protocol
315
(2) When the receive transparent code designation is set to Enable and the ASCIIBIN conversion is set to Enable
Additional code: 10H (DLE), transparent code: 02H (STX)
E
N
Q
External device side
Data length
Data section
Sum
check
code
(0004H)
L H
L
H
0 4 0 0 0 2 1 1 4 1 4 2 3 4 1 2 0 D 0 A
05H 30H 34H 30H 30H 30H 32H 31H 31H 34H 31H 34H 32H 33H 34H 31H 32H 30H 44H 30H 41H 02H 04H
Programmable
controller CPU side
A
C
K
Exclude the additional code and set to an even byte.
06H
Reception data read
X83
request
Programmable
controller CPU
BIDIN
ON
Completion device
M0
ON
Status display device
M1
at completion
Abnormal
completion
Normal
completion
One scan
Data length
* Two bytes of receive data are read to
the programmable controller CPU as one-byte data
(excluding the additional code).
Data length (No. of receive data):
Excluding additional code
For word unit;
Byte count after ASCII-BIN conversion (8)/2=4
For byte unit;
Byte count after ASCII-BIN conversion (4)
The following diagram is for word unit
600H
D3
00H , 04H
601H
D10
11H , 02H
602H
D11
42H , 41H
Data section
603H
D12
12H , 34H
604H
D13
0AH , 0DH
Buffer memory
00H , 04H
11H , 02H
42H , 41H
12H , 34H
0AH , 0DH
Sequence program
device memory
Transmission instruction
Sets CH1 to the reception
channel
Sets the allowable number of
receive data to 6
Executes reception
Sets the normal completion flag
Sets the abnormal completion flag
● When the receive transparent code designation is set to Enable and the ASCII-BIN conversion is set to Enable, the codes
for receivable arbitrary data section and those for receive data that is stored in the buffer memory's reception area are as
follows:
Item
Receive transparent code designation section
Data length, data section
316
Receivable codes
Codes stored in the reception
area
Additional code
01H to FFH
(Delete)
Transparent code
30H to 39H
41H to 46H
0H to 9H
AH to FH
CHAPTER 12 TRANSPARENT CODES AND ADDITIONAL CODES
12.6.2
Example of data transmission
The following shows an example of data transmission.
(1) When the send transparent code designation is set to Enable and the ASCIIBIN conversion is set to Disable
Additional code: 10H (DLE), transparent code: 02H (STX) (1st group)
Additional code: 10H (DLE), transparent code: 03H (ETX) (2nd group)
12
A
C
K
Transparent code (2nd group)
External device side
Additional code (2nd group)
06H
E
N
Q
Programmable
controller CPU side
Data
length
(0004H) D
L
L H E
Sum
check
code
Data section
D
L
E
C
L
L H
(0003H)
05H 04H 00H 10H 02H 11H 41H 42H 10H 03H 00H 0DH0AH B4H00H
(1102H) A
B
R
F
Transparent code (1st group)
Additional code (1st group)
Transmission
command
X50
Programmable
controller CPU
Completion device
BIDOUT
ON
M0
ON
Abnormal
completion
Normal
completion
12.6 Example of Data Communication Using the Bidirectional Protocol
Status display device
M1
at completion
Data length (transmission data count):
Excluding additional codes
For word unit: 0004H
For byte unit: 0008H
The following diagram is for word unit
Address
One scan
D3
Transmission
data
00H , 04H
400H
00H , 04H
D10
(1102H)
11H , 02H
401H
(1102H)
11H , 02H
D11
(B) (A)
42H , 41H
402H
(B) (A)
42H , 41H
D12
D13
(0003H)
00H , 03H
(LF) (CR)
0AH , 0DH
Sequence program
device memory
(0003H)
00H , 03H
(LF) (CR)
0AH , 0DH
403H
404H
Buffer memory
Transmission instruction
Sets CH1 to the transmission channel
Sets transmission data count to 4
Sets the transmission data in D10 to D13
Executes transmission
Sets the normal completion flag
Sets the abnormal completion flag
317
(2) When the send transparent code designation is set to Enabled and the ASCIIBIN conversion is set to Enabled
Additional code: 10H (DLE), transparent code: 02H (STX) (1st group)
Additional code: 10H (DLE), transparent code: 03H (ETX) (2nd group)
A
C
K
External device side
06H
E
N
Q
Programmable
controller CPU side
Transmission
command
Programmable
controller CPU
Data length
(0004H)
Data section
Sum
check
code
L H
L
H
0 4 0 0 0 2 1 1 4 1 4 2 0 3 0 0 0 D 0 A
05H 30H 34H 30H 30H 30H 32H 31H 31H 34H 31H 34H 32H 30H 33H 30H 30H 30H 44H 30H 41H FBH03H
X50
BIDOUT
ON
Completion device
M0
ON
Abnormal
completion
Status display device M1
at completion
One scan
Data length (No. of transmission data):
Excluding additional code
For word unit;
Byte count before ASCII-BIN conversion (8)/2=4
For byte unit;
Byte count before ASCII-BIN conversion (8)
The following diagram is for word unit
Normal
completion
Address
D3
D10
D11
Transmission
data
D12
D13
00H , 04H
11H , 02H
42H , 41H
00H , 03H
0AH , 0DH
400H
401H
402H
403H
404H
Sequence program
device memory
00H , 04H
11H , 02H
42H , 41H
00H , 03H
0AH , 0DH
Buffer memory
Transmission instruction
Sets CH1 to the transmission channel
Sets transmission data count to 4
Sets the transmission data in D10 to D13
Executes transmission
Sets normal completion flag
Sets abnormal completion flag
One word of data designated from the programmable controller CPU is converted to four-byte data ("0" to "9", "A" to "F"),
and is then transmitted.
318
CHAPTER 13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION)
CHAPTER 13 COMMUNICATING WITH ASCII CODE
(ASCII-BIN CONVERSION)
This chapter explains the binary-to-ASCII conversion (called ASCII-BIN conversion) in order to send/receive data in
ASCII format to/from an external device.
13.1
ASCII-BIN Conversion
ASCII-BIN conversion is a data conversion function that converts all data communicated between the Q series C24
and an external device to ASCII code data.
The ASCII-BIN conversion of communication data is performed by the Q series C24 according to the user settings.
Programmable
controller CPU
Q series C24
QJ71C24
Q25HCPU
MODE
RUN
ERR.
USER
BAT.
BOOT
External device
With ASCII-BIN conversion
CH2.
CH1.
13
32H 31H
34H 33H
37H 38H
35H 36H
CH1.
1234H
RS-232
Without ASCII-BIN conversion
USB
12H
34H
78H
56H
13.1 ASCII-BIN Conversion
RS-232
5678H
319
13.2
Settings for ASCII-BIN Conversion
In order to convert data to be sent/received via the non procedure protocol and bidirectional protocol from binary code
to ASCII code, it is necessary to make specific settings for the Q series C24 before performing data communication.
The following describes the settings for the ASCII-BIN conversion:
(1) The ASCII-BIN conversion settings can be designated for each interface.
(2) The ASCII-BIN conversion settings are registered in the "Transmission control
and others system setting" screen of GX Configurator-SC.
320
CHAPTER 13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION)
13.3
Performing ASCII-BIN Conversion for Data
Communicated via Non Procedure Protocol
This section explains the ASCII-BIN conversion of data to be communicated using the non procedure protocol.
(1) The following shows the range of transmission/reception data for which ASCIIBIN conversion can be performed.
Applicable data range at transmission
Message at transmission/
reception in arbitrary format
Arbitrary data section
13
Applicable data range at reception
Applicable data range at transmission
Message at transmission/
reception using user frames
Arbitrary
data
section
User frame
(first frame)
User frame
(last frame)
Applicable data range at reception
When sending or receiving data, the Q series C24 processes data as follows:
(a) Out of the data in the applicable data range shown above, the Q series C24 sends
and receives data whose data code is in the range of 30H to 39H ("0" to "9") and 41H
(b) During data reception, the Q series C24 regards the arbitrary data section as ASCII
code data, converting it to binary code data for storage in the buffer memory.
The user frame section is received in the data format corresponding to the registration contents in the Q series
C24. During data transmission, the Q series C24 regards data designated by the programmable controller CPU
(an arbitrary data section in the transmission message) and user-frame sections as binary code data,
converting them into ASCII code data and transmitting them.
External device (When communicated in an arbitrary format)
Buffer memory (transmission area/reception area)
Head data
(H)
1
2
0
2
3
A
B
C
31H 32H 30H 32H 33H 41H 42H 43H Receive
Conversion
Send
Arbitrary data section
(L)
(0002H)
00H , 02H
(0212H)
02H , 12H
(BC3AH)
BCH , 3AH
Transmission data count/
Receive data count
Transmission data/
receive data
(No. of data in word units)
321
13.3 Performing ASCII-BIN Conversion for Data Communicated via Non Procedure Protocol
to 46H ("A" to "F").
• Even if ASCII-BIN conversion is "enabled," it is possible to transmit data without converting the data in any
user frame portion or buffer memory transmission area. When sending data without ASCII-BIN
conversion, specify the user frame No. using the following method.
• Specify the number obtained by adding 4000H to the registered user frame No.
b15 b14 b13
to
b0
Number of frames
0: Conversion enabled
1: Conversion disabled
0: Frame registered in Flash ROM
1: Frame registered in buffer memory
(c) When sending data in the sections designated in 4001H to 44AFH, C000H to C01FH,
the additional codes by transmission transparent code designation will not be
added. ( Page 299, Section 12.3)
User frame No. to be sent
Designated No. when transmitting without ASCII-BIN conversion
1H to 3E7H (1 to 999)
4001H to 43E7H (16385 to 17383)
3E8H to 4AFH (1000 to 1199)
43E8H to 44AFH (17384 to 17583)
8000H to 801FH (-32768 to -32737)
C000H to C01FH (-16384 to -16353)
(2) The processing steps taken by the Q series C24 when communicating with
ASCII-BIN conversion and transparent code designation enabled are explained
in Page 299, Section 12.3.
• Transmission/reception in arbitrary formats
• Transmission/reception using user frames
322
CHAPTER 13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION)
13.4
Example of Data Communication Using the Non
Procedure Protocol
This section shows examples of data communication using the non procedure protocol when the following
settings/registrations are made.
(1) Settings via GX Developer
Perform the following settings on the "Intelligent function module switch setting" screen.
Setting item
Switch 1
Switch 2
Switch 3
CH1 Transmission setting
CH1 Communication rate setting
Setting value
Remarks
Set according to the external device

CH1 Communication protocol setting
0006H
CH2 Transmission setting
0000H
CH2 Communication rate setting
Switch 4
CH2 Communication protocol setting
0000H
Switch 5
Station No. setting
0000H
13
Nonprocedural protocol
Not used
Station number of the Q series C24
(2) Settings via GX Configurator-SC
Register the following items on the "Transmission control and others system setting," "Non procedure system
setting," and "Transmission user frame No. designation system setting" screens.
For items other than those listed below, the default values are used.
Registration screen
"Transmission user frame No. designation system
setting" screen
"Transmission control and others system setting"
screen
Setting value
0003H
Receive complete code designation
0009H
Receive user frame designation
User frame use enable/disable designation
Enable
Receive user frame designation
First frame No. designation 1st
03E8H
Receive user frame designation
First frame No. designation 2nd
03E9H
Receive user frame designation
Last frame No. designation 1st
041BH
Receive user frame designation
Last frame No. designation 2nd
041BH
Transmission user frame designation
Output head pointer designation
0001H
Transmission user frame designation Output count designation
0005H
Transmission frame No. designation 1st
43F2H
Transmission frame No. designation 2nd
43F3H
Transmission frame No. designation 3rd
C001H
Transmission frame No. designation 4th
8000H
Transmission frame No. designation 5th
441BH
ASCII-BIN conversion designation
Enable
13.4 Example of Data Communication Using the Non Procedure Protocol
"Non procedure system setting" screen
Setting item
Received data count designation
323
13.4.1
Example of data reception
The following shows an example of data reception:
(1) Reception using the receive complete code
Complete code: 9H (the code after ASCII-BIN conversion)
Data corresponding
to complete code
Head data
0
1
2
3
4
5
A B C D E 9
External device side
Number of bytes after
ASCII-BIN conversion:
((6)/2=3) when word
units are used,
(6) when byte
units are used
* ⋅ Two bytes of receive data is read to
the programmable controller CPU as
one-byte data.
⋅ Send data from the external device so
that the converted complete code data
is arranged with data having an even
byte number.
30H 31H 32H 33H 34H 35H 41H 42H 43H 44H 45H39H
Set to even byte
Programmable
controller CPU side
Reception data read X83
request
Store data
received count
INPUT
Programmable
controller CPU
ON
Completion device
The diagram below is for when
word units are used.
M0
ON
Abnormal completion
Status display device
M1
at completion
Normal completion
600H
One scan
601H
2)
D2
00H , 03H
D10
23H , 01H
00H , 03H
23H , 01H
3)
602H
603H
D11
ABH , 45H
D12
E9H , CDH
Buffer memory
ABH , 45H
E9H , CDH
Sequence program
device memory
Reception data read request
Sets CH1 to the reception
channel
Sets the allowable number of
receive data to 6
Executes reception
Sets the normal completion flag
Sets the abnormal completion flag
● When ASCII-BIN conversion is enabled, the codes of receivable data and the codes of receive data that is stored in the
reception area of the buffer memory are as follows:
Item
Receivable codes
Codes stored in the reception area
Arbitrary data section (including complete code
section)
30H to 39H, 41H to 46H
0H to 9H, AH to FH
If data codes other than 30H to 39H and 41H to 46H are received for an arbitrary data section, an error occurs after ASCIIBIN conversion processing by the Q series C24.
● To perform ASCII-BIN conversion, the complete code after conversion should be used.
324
CHAPTER 13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION)
(2) Reception based on the received data count
Head data
0
1
2
3
4
5
A B C D E
Number of bytes after
ASCII-BIN conversion:
((6)/2=3) when
word units are used,
(6) when byte units are used
9
External device side
* Two bytes of reception data is read to
the programmable controller CPU as
one-byte data.
30H 31H 32H 33H 34H 35H 41H 42H 43H 44H 45H 39H
Programmable
controller CPU side
Reception data read
request
Set to even byte
X83
Programmable
controller CPU
Store data
received count
INPUT
ON
Completion device
13
The diagram below is for when
word units are used.
M0
ON
Abnormal completion
Status display device
M1
at completion
Normal completion
600H
One scan
601H
602H
603H
2)
D2
00H , 03H
23H , 01H
ABH , 45H
E9H , CDH
D10
3)
D11
D12
Buffer memory
00H , 03H
23H , 01H
ABH , 45H
E9H , CDH
Sequence program
device memory
Reception data read request
Sets CH1 to the reception channel
Executes reception
Sets the normal completion flag
Sets the abnormal completion flag
When the receive transparent code designation is set to Disable and ASCII-BIN conversion is enabled, the codes of
receivable data and the codes of receive data that is stored in the reception area of the buffer memory are as follows:
Item
Arbitrary data section
Receivable codes
Codes stored in the reception area
30H to 39H, 41H to 46H
0H to 9H, AH to FH
If data codes other than 30H to 39H and 41H to 46H are received for an arbitrary data section, an error occurs after ASCIIBIN conversion by the Q series C24.
325
13.4 Example of Data Communication Using the Non Procedure Protocol
Sets the allowable number of receiving data to 6
(3) Example of reception using user frames
Programmable
controller CPU side
02H 51H
00H
0AH 3BH 30H 31H 32H46H 35H 41H 42H 43H 44H 45H 46H 39H 03H
;
0
1
2
First frame
(corresponds to register
number 3E8H)
F
5
A B C D E F
Arbitrary data section
9
E
T
X
Sum
check code
Station No. of
external device
External device side
S
T Q
X
Station No. of
Q series C24
Head data
Number of receive data
Number of bytes after ASCII-BIN conversion of
receive data excluding frames and additional codes:
(6)/2=3 When word units are used,
(6) When byte units are used.
The diagram below is for when word units are used
DEH
ADH
Last frame
(corresponds to
register number
41BH)
AEH
AFH
Reception data read
X83
request
Programmable
controller CPU
B0H
B1H
INPUT
3E8H
M0
ON
Abnormal completion
Status display device
M1
at completion
Normal completion
One scan
B2H
B3H
B4H
B5H
(2nd)
3EAH
(3rd)
(No designation)
0H
(4th)
41BH
Last frame No.
designation
(1st)
41BH
(2nd)
0H
600H
601H
602H
603H
(3rd)
(No designation)
0H
(Designate)
25BH
Reception data read request
(No designation)
120H (No designation)
1002H/ 0H
121H
User frame enable/
disable designation
First frame No.
designation
(1st)
3E9H
ON
(The first designated frame for each)
Completion device
1)
2H
(Convert)
1H
1H
00H , 03H
2FH , 01H
(4th)
Receive transparent
code designation
ASCII-BIN conversion
designation
Receive user
frame ( th)
Number of data
received
To D3
Number of receive
data
(arbitrary data section)
BCH , 5AH
F9H , DEH
Buffer memory
Reads combination of received user
frames
Sets CH1 to the reception channel
Sets the allowable number of receive
data to 6
Executes reception
Sets the normal completion flag
Sets the abnormal completion flag
326
To D0
D10 to
D12
CHAPTER 13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION)
13.4.2
Example of data transmission
The following shows an example of data transmission:
(1) Example of arbitrary data transmission
External device side
Programmable
controller CPU side
Data transmission area
(arbitrary data section)
3
4
1
2
A
B
5
* Eight characters of data
in the transmission area
are sent in two characters
per byte through
ASCII-BIN conversion.
6
33H 34H 31H 32H 41H 42H 35H 36H
Transmission
instruction
Programmable
controller CPU
Completion device
13
X50
OUTPUT
ON
M0
ON
Status display device
at completion
M1
Abnormal
completion
Normal
completion
One scan
121H
00H , 02H
401H
(1234H)
12H , 34H
402H
(56ABH)
56H , ABH
Buffer memory
Transmission instruction
ASCII-BIN conversion designation
Transmission area
(Designation of no. of data sent)
(Transmission data)
* 0004H in byte units
Sets the arbitrary transmission data for D11 to D12
Sets CH1 to the transmission channel
Sets the number of data sent to 2
Execute the transmission
Sets normal completion flag
Sets abnormal completion flag
327
13.4 Example of Data Communication Using the Non Procedure Protocol
400H
(Convert)
1H
(2) Example of transmission by user frame
Programmable
controller CPU side
02H 51H
T
O
T
A
L
;
(012 DH)
2DH
E
T
X
Data in transmission area
(arbitrary data section)
(Total number)
3
4
1
2
A
B
5
6
01H 33H 34H 31H 32H 41H 42H 35H 36H 03H
Corresponds to 3F3H Corresponds to 8001H
(for second designated (for third designated
frame)
frame)
8000H
(for fourth
designated
frame)
B7H
PRR
ON
B8H
M0
ON
Status display device
M1
at completion
One scan
B9H
Abnormal
completion
Normal
completion
A7H
* Eight characters of data
in the transmission area are
sent in two characters
per byte through
ASCII-BIN conversion.
Corresponds to 41BH
(for fifth designated
frame)
B6H
X50
Programmable
controller CPU
Completion device
;
00H 3BH 54H 4FH 54H 41H 4CH3BH
Corresponds to 3F2H
(for first designated frame)
Register No. of
corresponding
user frame
Transmission
instruction
0AH
C24
Sum
check code
Q
Station No.
S
T
X
Station No. of
external device
External device side
BAH
BBH
BCH
BDH
BEH
BFH
121H
400H
(Not sent)(Sending)
User frame No. being transmitted
0H/Other than 0H
(Do not send)
0H
(1st)
1H
5H
3F2H
CR/LF output designation
Output head pointer designation
Output count designation
Transmission frame no. designation (1st)
(2nd)
3F3H
(3rd)
C001H
(4th)
8000H
(5th)
441BH
(6th)
0H
(Convert)
1H
00H , 02H
401H
(1234H)
12H , 34H
402H
(56ABH)
56H , ABH
ASCII-BIN conversion designation
Transmission area
(Designation of no. of data sent)
(Transmission data)
Buffer memory * 0004H in byte units
Transmission instruction
Sets CH1 to the transmission channel
Sets the number of data sent to 2
Sets the arbitrary transmission data for D11 to D12
Sets the arbitrary transmission data for transmission buffer
Executes user frame transmission
Sets normal completion flag
Sets abnormal completion flag
328
CHAPTER 13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION)
13.5
Performing ASCII-BIN Conversion for Data
Communicated via the Bidirectional Protocol
This section explains the ASCII-BIN conversion of data to be communicated using the bidirectional protocol.
(1) The following shows the range of transmission/reception data for which ASCIIBIN conversion can be performed.
Applicable data range at transmission/reception
Message at data transmission/
reception
E
N
Q
(Arbitrary data section)
Data
length
Data section
Sum check
code
13
Applicable data range at transmission/reception
Response message
A
C
K
N
A
K
Error code
When sending or receiving data, the Q series C24 processes data as follows:
(a) Range of ASCII-BIN conversion
The Q series C24 performs the ASCII-BIN conversion for any data section (data length and data section) and
error code in a message.
• At transmission: The Q series C24 converts a transmission data count to 4-digit ASCII code data
(hexadecimal), then sends it beginning with the lowest byte (L).
• At reception: The Q series C24 converts a received data length (4-digit ASCII code data (hexadecimal)) to
2-byte binary code data and stores it in the reception data count storage area.
(c) Conversion of data section
• At transmission: The Q series C24 converts transmission data for one address to 4-digit ASCII code data
(hexadecimal), then sends it beginning with the lowest byte (L).
• At reception: The Q series C24 converts each two characters of a received data section (2-digit ASCII
code data (hexadecimal)) to 1-byte binary code data and stores it in the reception data storage area.
329
13.5 Performing ASCII-BIN Conversion for Data Communicated via the Bidirectional Protocol
(b) Conversion of data length
(d) Conversion of error code
• At transmission: The Q series C24 converts an error code for a detected error to 4-digit ASCII code data
(hexadecimal), then sends it beginning with the lowest byte (L). (For 3412H, it is converted to "3412" and
sent beginning with "12".)
• At reception: The Q series C24 converts the first 2 digits of a received error code (4-digit ASCII code data
(hexadecimal)) to 2-byte binary code data as the lower byte, and stores it in the transmission result
storage area. (For "1234" is received, it is converted to 3412H and stored.)
(e) Treatment of sum check code
The data length and the data section after ASCII-BIN conversion are added together and the lowest two bytes
of the resulting binary code data are treated as a sum check code.
• At transmission: The Q series C24 calculates a sum check code using the data length and data section
after ASCII-BIN conversion, then adds it to the transmission message.
• At reception: The Q series C24 calculates a sum check code using the received data length and data
section prior to ASCII-BIN conversion, then checks the received head of the sum-check code using the
code as a lower byte.
(When word units are used)
E
N
Q
Data length
Message
Data section
(0002)
Buffer memory
(H) (L)
*1
Sum
check
code
00H , 02H
L
H
L
H
0
2
0
0
1
2
3
4
5
A B C
05H 30H 32H 30H 30H 31H 32H 33H 34H 35H 41H 42H 43H 87H 02H
34H , 12H
BCH , 5AH
…… Transmission data
count/Receive data
count
… Transmission data/
receive data
ASCII-BIN conversion
*1 Calculation of sum check code
30H+32H+30H+30H+31H+32H+33H+34H+35H+41H+42H+43H=0287H
(H)(L)
(2) Page 309, Section 12.5 explains how Q series C24 processes data
communicated when ASCII-BIN conversion and transparent code designation
are both enabled.
Q series C24
External device
Head data
(Data
communication)
Arbitrary data section
Buffer memory (transmission area/reception area)
Data section
Sum
check
code
Send
L
H
L
H
0
2
0
0
1
2
0
2
3
A B C
Receive
05H 30H 32H 30H 30H 31H 32H 30H 32H 33H 41H 42H 43H 80H 02H
Starting data
N
A
K
A
C
K
Error code
L
H
4
3
1
2
15H 33H 34H 31H 32H
330
Send
Or
06H
(L)
(0002H)
00H , 02H
(0212H)
02H , 12H
(BC3AH)
BCH , 3AH
…… Transmission
data count/
Receive data
count
… Transmission
data/receive
data
(Communication of
response massage)
Receive
Conversion
Data length
Conversion
(H)
E
N
Q
At normal
completion: 0000H
At abnormal
completion: 1234H
…… Transmission
result/reception
result
CHAPTER 13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION)
13.6
Example of Data Communication Using the Bidirectional
Protocol
This section shows examples of data communication using the bidirectional protocol when the following settings and
registrations are made.
(1) Settings via GX Developer
Perform the following settings on the "Intelligent function module switch setting" screen.
Setting item
Switch 1
Switch 2
Switch 3
Setting value
CH1 Transmission setting
CH1 Communication rate setting
Remarks

Set according to the external device.
CH1 Communication protocol setting
CH2 Transmission setting
CH2 Communication rate setting
0007H
0000H
Switch 4
CH2 Communication protocol setting
0000H
Switch 5
Station No. setting
0000H
13
Bidirectional protocol
Not used
Station number of the Q series C24
(2) Settings via GX Configurator-SC
Register the following items on the "Transmission control and others system setting" screen.
For items other than those listed below, the default values are used.
Setting item
Send transparent code designation
Setting value
1004H
Receive transparent code designation
1004H
ASCII-BIN conversion designation
Convert
13.6 Example of Data Communication Using the Bidirectional Protocol
331
13.6.1
Example of data reception
The following shows an example of data reception when ASCII-BIN conversion is enabled.
When the receive transparent code designation is set to Enable and ASCII-BIN conversion is set to Enable, Additional
code: 10H (DLE), transparent code: 04H (E0T)
E
N
Q
Data length
Sum
check
code
Data section
(0004H)
External device side
L
H
L H
0 4 0 0 1 2 3 4 5 A B C D E F 0 0 D 0 A
05H 30H 34H 30H 30H 31H 32H 33H 34H 35H 41H 42H 43H 44H 45H 46H 30H 30H 44H 30H 41H 6DH04H
Programmable
controller CPU side
A
C
K
Set to even byte except for additional code
06H
1)
Reception data read
X83
request
Programmable
controller CPU
* Two bytes of reception data is read to the programmable
controller CPU as one-byte data (excluding additional code).
BIDIN
Data length (Number of data received): Excluding additional code
Number of bytes after ASCII-BIN conversion: ((8)/2=4)
when word units are used
(8) when byte units are used
ON
Completion device
M0
ON
Abnormal
completion
Status display device
M1
at completion
Normal
completion
One scan
Data length
This diagram is for when word
units are used.
600H
601H
602H
Data section
603H
604H
2)
00H , 04H
D10
34H , 12H
BCH , 5AH
F0H , DEH
0AH , 0DH
Buffer memory
D3
3)
D11
D12
D13
00H , 04H
34H , 12H
BCH , 5AH
F0H , DEH
0AH , 0DH
Sequence program
device memory
Reception data read request
Sets CH1 to the reception channel
Sets the allowable number of receive data to 6
Executes reception
Sets the normal completion flag
Sets the abnormal completion flag
When the receive transparent code designation is set to Enable and ASCII-BIN conversion is set to Enable, the codes of
receivable arbitrary data sections and the codes of receive data that is stored in the reception area of the buffer memory are
as follows:
Item
Sections for which the
reception transparent code
designation is enabled
Data length, data section
332
Receivable codes
Codes stored in the reception area
Additional code
01H to FFH
(Delete)
Transparent code
30H to 39H
41H to 46H
0H to 9H
AH to FH
CHAPTER 13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION)
13.6.2
Example of data transmission
The following shows an example of data transmission when ASCII-BIN conversion is enabled.
When the send transparent code designation is set to Enable and ASCII-BIN conversion is set to Enable, Additional
code: 10H (DLE), transparent code: 04H (E0T)
A
C
K
External device side
06H
E
N
Q
Programmable
controller CPU side
Transmission
instruction
Data length
(0004)
Sum
check
code
Data section
L H
L
H
0 4 0 0 1 2 3 4 5 A B C D E F 0 0 D 0 A
05H 30H 34H 30H 30H 31H 32H 33H 34H 35H 41H 42H 43H 44H 45H 46H 30H 30H 44H 30H 41H 6DH04H
13
X50
Programmable
controller CPU
BIDOUT
Data length (Number of data received): Excluding additional code
Number of bytes after ASCII-BIN conversion: ( (8)/2=4)
when word units are used
(8) when byte units are used
ON
Completion device
M0
ON
Status display device
M1
at completion
Abnormal
completion
Normal
completion
One scan
This diagram is for when word units are used.
Transmission
data
D10
D11
D12
D13
00H , 04H
34H , 12H
BCH , 5AH
F0H , DEH
0AH , 0DH
400H
401H
402H
403H
404H
Sequence program
device memory
00H , 04H
34H , 12H
BCH , 5AH
F0H , DEH
0AH , 0DH
Buffer memory
Transmission instruction
Sets CH1 to the transmission channel
Sets the number of data sent to 4
Sets the arbitrary transmission data to D10 to D13
Executes transmission
Sets normal completion flag
Sets abnormal completion flag
Data for one address (one word) in the buffer memory's transmission area is converted into four-byte ASCII code data ("0" to
"9" and "A" to "F"), and is then transmitted.
333
13.6 Example of Data Communication Using the Bidirectional Protocol
Transmission data
D3
CHAPTER 14 DATA COMMUNICATIONS USING
EXTERNAL DEVICE AND
PROGRAMMABLE CONTROLLER
CPU M : N CONFIGURATION
Always read this chapter when communicating data by using a multidrop link to connect the external devices and
programmable controller CPU in an m: n system configuration. You do not have to read this chapter when using a system
configuration other than
m: n to communicate data.
This section describes the case when data is communicated between external devices and the programmable
controller CPU by connecting multiple external devices (m stations) and multiple Q series C24 (n stations) over a
multidrop link. (The total number of m and n is up to 32 stations.)
With this m : n multidrop link, only MC protocol data communications by command transmission from the external
devices can be performed.
14.1
Data Communications Precautions
(1) When communicating data by using an m: n system configuration, multiple
external devices cannot communicate data with the programmable controller
CPU at the same time.
Interlock the external devices so that the external device can communicate with the programmable controller
CPU in a 1:1 configuration.
See Page 336, Section 14.2 to Page 339, Section 14.3 for the items to be agreed upon and the interlock method
to interlock the external devices.
(2) Communicate data between external devices and the programmable controller
CPU by the following methods only.
• Full-duplex data communications (m : n data communications is impossible with half-duplex data
communications)
• Data communications by command transmission from external device using an MC protocol excluding the
format 3 and format 5 control procedure (Data communications using the format 3 and format 5 control
program and data transmission from sequence program using the on-demand function cannot be
performed.)
334
CHAPTER 14 DATA COMMUNICATIONS USING EXTERNAL DEVICE AND PROGRAMMABLE CONTROLLER CPU M : N
CONFIGURATION
(3) The data transmitted by one external device is received by all the other
external devices, including the external device that transmitted the data. The
send data from a programmable controller CPU is also received by all the
external devices.
Therefore, it may be necessary for devices that received data not addressed to them (judged by station No. in the
message) to ignore the receive data.
At the programmable controller CPU, Q series C24 also ignores the receive data other than that addressed to it.
(4) Connect to multiple external devices and connect the terminating resistor as
described in User's Manual (Basic).
(5) When communicating data by using an m: n system configuration, designate
the following station number at the [Station No.] and [Local station No.] items
in the command message to be transmitted from an external device.
14
(a) When accessing the programmable controller CPU
Item
Communications using QnA compatible 2C/3C/4C frame
Station No.
Communications using A compatible 1C frame
Station No. of Q series C24 to be passed through ( MELSEC Communication Protocol Reference Manual)
Local station No.
Station No. of access source external device*1
Designation unnecessary (No [Local station No.] item)
(b) When accessing another external device (interlock communications)
Item
Communications using QnA compatible 2C/3C/4C frame
Communications using A compatible 1C frame
Local station No.
*1
Station No. of access source external device*1
Designation unnecessary (No [Local station No.] item)
A station No. within the [0] to [31] (00H to 1FH) range not set to the Q series C24 on the programmable controller CPU
side is used as the external device No. in the [Station No.] and [Local station No.] items in the message.
Select and designate the No. of each external device.
The designation method is described in ( MELSEC Communication Protocol Reference Manual).
Station No.: Designates the No. of the transmit destination external device.
Local station No.: Designates the No. of the transmit source external device. (Does not have to be designated when A
compatible 1C frame is used.)
335
14.1 Data Communications Precautions
Station No. of access destination external device*1
Station No.
14.2
External Devices Interlock Conditions
When using a multidrop line to communicate data between external devices and the programmable controller CPU in
an m: n configuration, interlocks must be provided between the external devices so that multiple external devices
cannot communicate data with the programmable controller CPU at the same time.
This section describes the conditions for providing the interlocks between the external devices so that any one of the
external devices can communicate data with the programmable controller CPU.
(Conditions for priority use (obtaining line ownership) of the line from the start to the end of data communications with
the programmable controller CPU.)
14.2.1
Maximum communications time per external device station
This condition determines the maximum time each external device can communicate with the programmable controller
CPU after obtaining line ownership. (Time
in the illustration below.)
This prevents loss of data communications between other external devices and the programmable controller CPU by
shutdown of the external device that obtained line ownership.
Time
External device 1
External device 2
to
External device 5
Start of data communications
Indicates the range within
which the target device
cannot obtain line ownership.
Indicates the range within
which the target device can
obtain line ownership and
can have data communication
with the programmable
controller CPU.
● Make the maximum data communications time per external device station the maximum time of the external device that
requires the most time to communicate data with the programmable controller CPU.
● After system starting, complete data communications from the external device that obtained line ownership and the
programmable controller CPU within the maximum communications time.
(If data communications cannot be completed within this time, initialize the Q series C24 transmission sequence by
transmitting the EOT/CL code to the objective programmable controller CPU within the maximum communications time.
( MELSEC Communication Protocol Reference Manual)
● While an external device and the programmable controller CPU are communicating data, have the other external devices
check for timeout so that they do not transmit data during this time.
336
CHAPTER 14 DATA COMMUNICATIONS USING EXTERNAL DEVICE AND PROGRAMMABLE CONTROLLER CPU M : N
CONFIGURATION
14.2.2
Message structure when communicating data between
external devices
The message structure when communicating data between external devices is determined by any of the following.
This condition is determined to provide interlocks between the external devices so that each of them can exchange
data with the programmable controller CPU in a 1:1 configuration.
(1) When making the message structure the same as that of each control
procedure format frame
(a) Use a number within the [0] to [31] (00H to 1FH) range not set to the Q series C24 on
the programmable controller CPU side as the external device No. in the [Station No.]
and [Local station No.] items in the message.
(b) Select and designate the external device numbers.
14
The designation method is described in the MELSEC Communication Protocol Reference Manual.
• Station No.: Designates the No. of the transmit destination external device.
• Local station No.: Designates the No. of the transmit source external device. (Does not have to be
designated when A compatible 1C frame is used.)
When m : n configuration is 5:27
The values in ( ) are the external device and the Q series C24 station numbers (decimal: hexadecimal)
(28: 1CH)
(31: 1FH)
External
device
External
device
External
device
-1-
-2-
-5-
CPU
C24
CPU
(3: 03H)
C24
CPU
C24
(26: 1AH)
CPU
C24
C24: Q series C24, QC24(N), UC24
PC No.
E
N
Q
Local station
No.
(QnA Compatible 3C frame format 1)
Network No.
C24
(2: 02H)
Station No.
CPU
(1: 01H)
Frame
identification
No.
(0: 00H)
14.2 External Devices Interlock Conditions
(27: 1BH)
H
L
H
L
H
L
H
L
H
L
F
9
1
C
0
0
F
F
1
B
05H 46H 39H 31H 43H 30H 30H 46H 46H 31H 42H
337
(2) When message structure different from that of control procedure format
frames can be used
(a) Change the head data of each message to other arbitrary data.
• When selecting ASCII code format 1, format 2, or format 4, change ENQ (05H).
(b) Arbitrarily list the data following the head data of each message according to the
user specifications.
Command
Message wait
Sum check
code
(;)
Transmission
source station
No.
External device 1
(station No. 1BH)
Transmission
destination
station No.
Head data
Arbitrary contents
(1C)
(1B)
(ZZ)
(2)
(CD)
(:)
Transmission
source station
No.
External device 2
(station No. 1CH)
Transmission
destination
station No.
3BH 31H 43H 31H 42H 5AH 5AH 32H 43H 44H
(1C)
(1B)
3AH
Arbitrary contents
Head data
Correspond the message structure for general reporting to all the other external devices except programmable controller
CPU stations using unused station numbers or a message structure different from the Q series C24 control procedure
format.
338
CHAPTER 14 DATA COMMUNICATIONS USING EXTERNAL DEVICE AND PROGRAMMABLE CONTROLLER CPU M : N
CONFIGURATION
14.3
Examples of Procedure for Data Communications with
the Programmable Controller CPU
The following uses examples to describe the procedure when communicating data with a programmable controller
CPU by interlocking the external devices.
14.3.1
Sequential data communications between external devices
and the programmable controller CPU
The external devices sequentially obtain the line usage right and communicate data with the programmable controller
CPU based on their station No.
14
Time
Station No. 1BH
external device
Transmission to transfer
the line usage right
Response
Station No. 1CH
external device
Data communications
with the programmable
controller CPU
Station No. (m-1)
external device
programmable controller CPU.
: External device that obtained the line usage right
§
1
External device
(Station No.: 1BH)
3
When communicating
data with the station
No. 1H programmable
controller CPU
3
3
External device
External device
External device
(Station No.: 1CH)
(Station No.: 1DH)
(Station No.: 1EH)
2-a)
(Station No.:0H)
CPU
C24
(Station No.:1H)
CPU
C24
(Station No.:2H)
CPU
C24
(Station No.:15H)
CPU
C24
C24: Q series C24, QC24 (N), UC24
339
14.3 Examples of Procedure for Data Communications with the Programmable Controller CPU
The following uses an example to describe the procedure when external devices communicate data with the
1.
When the system starts, the external device with the lowest station No. (1BH) is given the line
usage right.
2.
The external device that obtained the line usage right,
a) When communicating data with the programmable controller CPU, begins processing from step 4 after
communicating data with the programmable controller CPU within the maximum data communications
time from among all the external devices.
b) When not communicating data with the programmable controller CPU, immediately begins processing
from step 4
3.
The external devices that have not obtained the line usage right check the line usage time of the
external device that obtained the line usage right and ignore the receive data not addressed to
their own station.
When the line usage time exceeds the maximum data communications time, each external device
performs the processing of step 7.
: External device that obtained the line usage right
§ (Before 5)
§ (Before 5)
External device
External device
External device
External device
(Station No.: 1BH)
(Station No.: 1CH)
(Station No.: 1DH)
(Station No.: 1EH)
4
5
(Station No.:0H)
C24
CPU
(Station No.:1H)
CPU
C24
6
Data communications with arbitrary
programmable
controller CPU
(Station No.:2H)
CPU
C24
(Station No.:15H)
CPU
C24
C24: Q series C24, QC24 (N), UC24
4.
External devices that communicated data with the programmable controller CPU, or external
devices that do not have to communicate data with the programmable controller CPU, transmit the
data for transferring the line usage right to the external device of the next station No. A message
structure example is shown in Step 5.
When a response message (step 5) is not received from the next external device to which the line usage
right was passed, data transmission for transferring the line usage right to the external device of the next
station No. is repeated until the line usage right is accepted.
340
CHAPTER 14 DATA COMMUNICATIONS USING EXTERNAL DEVICE AND PROGRAMMABLE CONTROLLER CPU M : N
CONFIGURATION
5.
The external device that accepts the line usage right transmits a response message to the external
device that passed it the line usage right.
Message of
4 above
(;)
(1C)
(1B)
(ZZ)
(2)
Sum check
code
Message wait
External device
that transfers line
usage right (1BH)
Command
Transmission
destination
station No.
Transmission
source station
No.
*1
*1 Command "ZZ" is command for
description purposes.
The user should select the command
that transfers/accepts the line usage right.
(CD)
Transmission
destination
station No.
Transmission
source station
No.
3BH 31H 43H 31H 42H 5AH 5AH 32H 43H 44H
External device
passed line usage
right (1CH)
(:)
(1C)
(1B)
3AH 31H 43H 31H 42H
Message of 5
6.
14
The external device that accepted the line usage right by transmitting a response message
performs processing beginning from step 2.
When line usage time of the external device that currently has the line usage right exceeds the
maximum data communications time.
a) The external device of the next station No. transmits all external devices general report data and
obtains the line usage right and performs step 2.
(1F)
(1C)
Sum check
code
(;)
(ZZ)
(0)
(0A)
*1 Station No. for all external
devices general report.
*2 See *1 of step 5.
3BH 31H 46H 31H 43H 5AH 5AH 30H 30H 41H
b) The other external devices check if all external devices general report data was received. If the data
was received, the external device performs step 3.
If the data was not received, the next external device transmits all external devices general report data
and obtains the line usage right and performs step 2. The other external devices perform step 7-b).
341
14.3 Examples of Procedure for Data Communications with the Programmable Controller CPU
External device
that obtains the
line usage right
(1CH)
Message wait
*2
Command
*1
Transmission
designation
station No.
Transmission
source
station No.
7.
14.3.2
Data communications between programmable controller CPU
and external devices by designating a master station and
slave stations
One of the external devices is made the master station and the other external devices communicate data with the
programmable controller CPU after obtaining permission from the master station.
TIme
Permission
granted
response
Master station
external device
Communications
request
General report to
start and end data Communications
communications
request
between master
station and
Permission
programmable
granted
controller CPU
response
Communications
complete report
Communications
request
Slave station
external device 1
Communications
complete report
Response
Response
Permission
granted
response
Slave station
external device 2
Start
End
Data communications with programmable controller CPU
Slave station
external device m-1
Data communications
with programmable
controller CPU
The following uses an example to describe the procedure when external devices communicate data with the
programmable controller CPU.
In this example, after the start of data communications between external devices and the programmable controller
CPU, the external devices perform a maximum data communications time time-out check. Slave station external
devices that are not communicating data with the programmable controller CPU check if the external device that
completed data communications with the programmable controller CPU transmitted a communications complete
report.
In the following descriptions, the external device with the lowest station No. (1BH) is assumed to be the master station
and the other external devices are assumed to be slave stations.
: External device that obtained the line usage right
§ (Before 2)
Master station
§ (after 2)
External device
External device
External device
External device
(Station No.: 1BH)
(Station No.: 1CH)
(Station No.: 1DH)
(Station No.: 1EH)
2
1
(Station No.: 0H)
CPU
C24
(Station No.: 1H)
CPU
C24
(Station No.: 2H)
CPU
C24
(Station No.: 15H)
CPU
C24
C24: Q series C24, QC24 (N), UC24
342
CHAPTER 14 DATA COMMUNICATIONS USING EXTERNAL DEVICE AND PROGRAMMABLE CONTROLLER CPU M : N
CONFIGURATION
1.
A slave station that wants to communicate data with the programmable controller CPU sends a
communications request to the master station to obtain the line usage right. A message structure
example is shown in step 2.
2.
The master station transmits a permission granted response to the slave station that issued the
communications request.
Massage of 1
Transmission
source station
No.
Command
Message wait
Sum check
code
(;)
Transmission
destination
station No.
External device of
slave station that
wants to obtain the
line usage right
(1CH)
*1
(1B)
(1C)
(ZX)
(2)
(CB)
*1 Command "ZX" is a communications request
command for description purpose.
The user should select the command that
requests communications.
Permission granted/
permission not granted
(:)
Transmission
source station
No.
Master station
external device
(1BH)
Transmission
destination
station No.
3BH 31H 42H 31H 43H 5AH 58H 32H 43H 42H
(1B)
(1C)
(Y)
3AH 31H 42H 31H 43H 59H
14
Massage of 2
: External device that obtained the line usage right
§ (After 6)
§ (Before 6)
4
Mater station
4
4
External device
External device
External device
External device
(Station No.: 1BH)
(Station No.: 1CH)
(Station No.: 1DH)
(Station No.: 1EH)
6
5
(Station No.: 0H)
C24
(Station No.: 2H)
CPU
C24
(Station No.: 15H)
CPU
C24
C24: Q series C24, QC24 (N), UC24
3.
After communicating data with the programmable controller CPU within the maximum data
communications time from among the external devices, the slave station that received the
"permission granted" response goes to step 5.
4.
The master station that transmitted the "permission granted" response and the slave stations that
did not obtain line usage right check the line usage time of the slave station that obtained the line
usage right and ignore receive data other than that addressed to their local station.
When the line usage time exceeds the maximum data communications time, each external device
performs the processing of step 7.
5.
After data communications are complete, the slave station that exchanged data with the
programmable controller CPU transmits a communications complete report to the master station.
A message structure example is shown in step 6.
Slave stations that do not communicate data with the programmable controller CPU check if a
communications complete report was transmitted and do not communicate data with the master station
during that time.
343
14.3 Examples of Procedure for Data Communications with the Programmable Controller CPU
C24
CPU
(Station No.: 1H)
CPU
3
6.
The master station that received the communications complete report transmits a response to the
slave station that transmitted the communications complete report.
(1B)
(1C)
(ZY)
(2)
Sum check
code
Message wait
Transmission
destination
station No.
Transmission
source station
No.
(;)
Command
*1
Massage of 5
External device of
slave station to
perform the
communications
complete report
(1CH)
*1 Command "ZY" is a communications complete
report command for description purpose.
The user should select the communications
complete report command.
(CC)
Transmission
destination
station No.
Transmission
source station
No.
3BH 31H 42H 31H 43H 5AH 59H 32H 43H 43H
Master station
external device
(1BH)
(:)
(1B)
(1C)
3AH 31H 42H 31H 43H
Massage of 6
7.
After completion of step 6 above, or when the line usage time of the slave station that obtained the
line usage right exceeds the maximum data communications time:
a) The master station waits for a communications request from a slave station.
When the master station receives a communication request, it performs processing from step 2.
b) The slave stations do not communicate data with the master station until data communications with the
programmable controller CPU are necessary.
When data communications with the programmable controller CPU becomes necessary, that slave station
performs processing from step 1.
8.
When the master station itself wants to exchange data with the programmable controller CPU and
a slave stations does not have the line usage right, it transmits all external devices except
programmable controller CPU a general report data and obtains the line usage right before
communicating data with the programmable controller CPU.
After data communications with the programmable controller CPU are complete, the master station
transmits all external devices general report data to inform the slave stations that data communications
with the programmable controller CPU are complete.
During this time, the slave stations do not communicate data with the master station until master station
data communications are complete.
(1B)
Sum check
code
(1F)
Message wait
(;)
Command
External device of
master station that
obtained the line
usage right (1BH)
*2
Transmission
destination
station No.
Transmission
source station
No.
*1
(ZX)
(0)
(07)
3BH 31H 46H 31H 42H 5AH 58H 30H 30H 37H
(1B)
Sum check
code
(1F)
Message wait
(;)
Command
External device of
master station that
transmits
communications
complete report
(1BH)
*2
Transmission
destination
station No.
Transmission
source station
No.
*1
(ZY)
(0)
(08)
3BH 31H 46H 31H 42H 5AH 59H 30H 30H 38H
344
*1 Station No. for all external devices general report.
*2 Commands "ZX" and "ZY" are commands for description purposes.
The user should select the command when the master station
communicates data with slave stations.
CHAPTER 15 SWITCHING THE MODE AFTER STARTING
CHAPTER 15 SWITCHING THE MODE AFTER
STARTING
This function forcefully switches the current communication protocol and transmission specifications of the designated
interface from an external device and the programmable controller CPU after the Q series C24 starts.
When the Q series C24 starts, it begins operation with the setting values of the GX Developer switch setting.
The mode switching function is used to change the communication protocol of the specified interface and transmission
specifications and continue data communications without restarting the QCPU. (When using the dedicated instruction (UINI
instruction) for mode switching, refer to Page 402, Section 17.8.)
(1) Mode switching from external device
(a) If the communication protocol of the interface connecting the external device is MC
protocol, mode switching can be performed.
(b) The communication protocol can be changed from the MC protocol as shown below.
MC protocol
(Formats 1 to 5)
Non procedure protocol
GX Developer connection
(Format switching)
Bidirectional protocol
Pre-defined protocol
(c) The transmission specifications set by the GX Developer switch setting can be
changed.
345
15
(2) Mode switching from programmable controller CPU
(a) Regardless of the current communication protocol of the connected interface, the
external device can perform mode switching from the sequence program.
(b) The communication protocol can be changed from the sequence program as shown
below.
MC protocol
(Formats 1 to 5)
Non procedure protocol
GX Developer connection
(Format switching)
Bidirectional protocol
Pre-defined protocol
(c) The transmission specifications set by the GX Developer switch setting can be
changed.
When using the mode switching function, set the setting change of the communication setting to "enable" in the GX
Developer switch setting.
( User's manual (Basic))
346
CHAPTER 15 SWITCHING THE MODE AFTER STARTING
15.1
Mode Switching Operation and Contents that can be
Changed
This section describes the set contents that can be changed with mode switching and the operation of Q series C24
after mode switching.
15.1.1
Settings that can be changed with mode switching
The following describes the settings that can be changed with mode switching.
(1) Switching the communication protocol
(a) The communication protocol setting of each interface can be switched.
(b) The communication protocol after the mode switching is specified by the switching
mode No. designation area of the buffer memory (address: 90H, 130H).
15
(2) Changing the transmission specifications
(a) The transmission setting of each interface can be switched.
(b) The transmission setting after the mode switching is specified by the transmission
specification after switching designation area of the buffer memory (address: 91H,
Mode switching allows the user to change the settings corresponding to communication protocol and transmission switch
settings of the GX developer.
347
15.1 Mode Switching Operation and Contents that can be Changed
131H).
15.1.2
Operation for mode switching
The following describes the Q series C24 operation for mode switching.
(1) Processing currently in execution
(a) If there is a mode switching request, mode switching immediately starts.
(b) If one of the following processing was being performed when a mode switching
request was issued, that processing is terminated.
• Data communications using an MC protocol
• Command message receive processing and response message or on-demand data transmission
processing are all terminated.
• The transmission complete end signal for an on-demand data transmission request is not turned on.
• Data communications using non procedure, bidirectional, or pre-defined protocol
• Data and response message transmit and receive processing are all terminated.
• All the input signals from the programmable controller CPU related to transmit and receive processing are
turned off.
• If the receive data from the external device was being stored to the Q series C24, the receive data up to
that point is ignored and the data is processed with the current receive data count as [0].
(2) Modification of buffer memory stored value
(a) Special applications area (addresses: 252H to 253H, 262H to 263H)
The communication protocol status and transmission specifications after mode switching is complete are
stored.
The values stored to areas other than the above are not changed. The contents before switching are
preserved.
(b) User free area (addresses: 400H to 1AFFH, 2600H to 3FFFH)
The stored values are not changed. The contents before mode switching are preserved.
348
CHAPTER 15 SWITCHING THE MODE AFTER STARTING
15.2
Mode Switching Precautions
(1) Set-up between the external device and the programmable controller CPU
Make the following setting for the external device and the programmable controller CPU so that mode switching
is not performed during data communications.
(a) Which side is to switch the mode, the programmable controller CPU or external
device
(b) Timing for each mode switching pattern
(For mode switching patterns,  Page 345, CHAPTER 15.)
(c) Interlocking of all connected devices in the case of mode switching
• Method and message structure when all the connected stations are informed of the mode switching
execution
• Method and message structure when all the connected stations are informed of the mode switching
completion
• Device No. and meaning of the value when a programmable controller CPU word device is used
15
(2) Mode switching from external device
(a) Once the mode has been changed to a mode other than MC protocol (Formats 1 to
5), it cannot be changed from the external device.
In this case, change the mode on the programmable controller CPU.
device is available for mode switching from the external device
( MELSEC Communication Protocol Reference Manual)
It is not available for other Q series C24 stations connected over a network system.
It is recommended to switch the mode on the programmable controller CPU side.
(3) Data communications after mode switching
The Q series C24 requires approximately 400 ms as processing time of mode switching only.
While the mode switching is being executed, the setting values cannot be stored into the buffer memory special
applications area and data cannot be transmitted between the Q series C24 and the external device.
Approx. 400 ms
Mode switching
processing
Mode switching signal
X6/XD
(4) Linked operation mode switching
Do not switch the mode when two interfaces of the Q series C24 are in linked operation. Also, do not switch the
mode for linked operation.
349
15.2 Mode Switching Precautions
(b) Only the Q series C24 (including multidrop link stations) connected to an external
15.3
I/O Signals for Handshake with Programmable
Controller CPU and Buffer Memory
This section describes the I/O signals for handshake and the buffer memories used when mode switching is
performed.
(1) I/O signals for handshake with programmable controller CPU
I/O signal
Item
Mode
switching
CH1
CH2
X6
XD
Signal name
Device turned
ON/OFF
CPU
Mode switching in
progress
Timing
C24

Complete
(Switching)
Y2
Y9
Mode switching
request

Remark
The following signals can also be used as I/O signals, in addition to the above.
Refer to User's Manual (Basic) for the programmable controller CPU I/O signals.
• Q series C24 ready signal (X1E): Turned ON when the Q series C24 can be accessed from the programmable
controller CPU
• Watchdog timer error signal (X1F): Turned ON when the Q series C24 does not operate normally
• CH1 ERR. signal (XE): Turned ON when the CH1 ERR. has occurred
• CH2 ERR. signal (XF): Turned ON when the CH2 ERR. has occurred
(2) Buffer memory
Address (Decimal
(hexadecimal))
CH1
Name
144 (90H)
304 (130H)
For specifying mode
switching
145 (91H)
305 (131H)
515 (203H)
350
Setting value/Stored value
CH2
For confirming mode
switching and switch
setting
Switching mode No. designation
( Page 351, Section 15.3 (2)
(a))
0001H: MC protocol (Format 1)

0007H: Bidirectional protocol
0009H: Pre-defined protocol
00FFH: GX Developer connection
Transmission specification setting
after switching
( Page 351, Section 15.3 (2)
(b))
0000H: Matched to the settings at the GX Developer
8000H to 8FFFH: Matched to the settings of this area
Switch setting error, mode switching
error condition
0: Normal
Other than 0: Switch setting error, mode switching error
( User's manual (Basic))
CHAPTER 15 SWITCHING THE MODE AFTER STARTING
(a) Switching mode No. designation area (addresses: 90H, 130H)
Write the desired mode No. (0001H to 0007H, 00FFH).
b15
b0
to
Buffer memory address 90H/130H
(Default 0000H)
0001H: MC protocol (Format 1)
0002H: MC protocol (Format 2)
0003H: MC protocol (Format 3)
0004H: MC protocol (Format 4)
0005H: MC protocol (Format 5)
0006H: Non procedural protocol
0007H: Bi-directional protocol
0009H: Pre-defined protocol
00FFH: GX Developer connection *1
*1
The communication protocol is specified as "00H" when the GX Developer connection mode is set using the GX
Developer switch setting.
(b) Switching transmission specifications designation area (address: 91H, 131H)
• Designates the transmission specifications after mode switching.
• When the transmission specifications are returned to the contents set in GX Developer, [0000H] is written
to this area.
• When setting arbitrary transmission specifications (other than the contents set in GX Developer), the value
corresponding to ON/OFF of the relevant bit in the table listed below is written. Relevant bit 1 (ON)/0
15
(OFF) is designated the same as transmission setting of GX Developer.
15.3 I/O Signals for Handshake with Programmable Controller CPU and Buffer Memory
351
[For the Q series C24]
b 15
to
b8 b7 b6 b5 b4 b3 b2 b1 b0
0
80H to 8FH
CH1 side *1
CH2 side *1
80H to 8FH
Description
Bit
b0
*1
*2
Operation setting
OFF(0)
ON(1)
Independent
Link
Remarks
Be sure to set the CH1 side
to OFF(0).
b1
Data bit
7
8
b2
Parity bit
NO
Yes
Vertical parity
b3
Even/odd parity
Odd
Even
Valid only when parity bit is
set to Yes.
Parity bit is not included.
b4
Stop bit
1
2
b5
Sum check code
NO
Yes
b6
Write during RUN
Prohibited
Allowed
b7
Setting modifications
Prohibited
Allowed
Bit
Description
Set value
Remarks
b8
to
b15
Communication
speed
80H to 8FH
Refer to *2
All items in the table should be set to OFF for the interface which "GX Developer connection" is set in the switching
mode number designation. The Q series C24 operates with the values set in GX Developer.
Transmission setting
GX Developer side setting
Operation setting
Independent
Data bit
8
Parity bit
Yes
Even/odd parity
Odd
Stop bit
1
Sum check code
Yes
Write during RUN
Allowed
Setting modifications
Allowed/Prohibited
The setting value of the communication speed.
Communication
speed
(Unit: bps)
Bit position
Bit position
b15 to b8
Communication
speed
(Unit: bps)
Remarks
b15 to b8
50
50bps
14400
86H
300
80H
19200
87H
600
81H
28800
88H
1200
82H
38400
89H
2400
83H
57600
8AH
4800
84H
115200
8BH
9600
85H
230400
8CH
Slow down the communication speed when
data cannot be communicated normally due
to overrun error, framing error, etc. in
communication with external devices.
• Transmission speed of 230400 bps is available for only CH1 of the QJ71C24N (-R2/R4) and LJ71C24(R2).
• When connecting external devices to both of two interfaces, the total of the communication speed should
be 115200 bps of less (230400 bps or less the QJ71C24N (-R2/R4)). When connecting an external device
to either of two interfaces, the maximum of 115200 bps is available for the interface (a maximum of
230400 bps for the QJ71C24N (-R2/R4) or LJ71C24(-R2)). In this case, set 300 bps for the other interface
to which no external device is connected.
• Set "80H" to the interface for which "GX Developer connection" is set in the switching mode number
designation. The communication speed set on the GX Developer is applied.
352
CHAPTER 15 SWITCHING THE MODE AFTER STARTING
Remark
The programmable controller CPU must also be aware of the following I/O signals for handshake and buffer memories when
the mode is switched from an external device.
• Mode switching in progress signal (X6/XD)
• Switch setting error, mode switching error storage area (address: 203H)
15
15.3 I/O Signals for Handshake with Programmable Controller CPU and Buffer Memory
353
15.4
Switching the Mode from the Programmable Controller
CPU
This section shows how the Q series C24 mode is switched from the programmable controller CPU.
15.4.1
Mode switching procedure
The following explains the procedure for switching the Q series C24 mode from the programmable controller CPU.
*1
Mode switching request
Y2/Y9
Mode switching in progress
X6/XD
Approx. 400 ms
CH
ERR. communication error
XE/XF
X1E
Q series C24 ready
Mode switching area
(address 90H to 91H/130H to 131H)
TO
Switch setting error,
mode switching error storage area
(address 203H)
FROM
(Only when normal)
Buffer memory special applications area
Data communications initialization
setting areas described in
User's Manual (Basic)
Addresses 93H to 121H/133H to 1C1H
*1
*2
*3
354
*2
TO
Data
communications
possible
Default value change
(Performed only when necessary)
*3
Data communications impossible
Data communicationspossible
Inform in advance all the connected device that data communications by mode switching cannot be performed.
When XE and XF were turned on, check the error contents as described in the User's Manual (Basic) and take the
corresponding action.
• Checking of mode switching designation contents for buffer memory mode switching area and writing of mode
switching designation contents within the range that can be designated.
• Re-execution of mode switching
After checking that mode switching was completed normally, inform all the connected devices that data communications
are possible and restart data communications.
To check the Q series C24 mode (communication protocol, transmission specifications) after switching, read the buffer
memories (addresses: 252H to 253H, 262H to 263H) described in the User's Manual (Basic).
CHAPTER 15 SWITCHING THE MODE AFTER STARTING
15.4.2
Mode switching sample program
The following shows a sample sequence program that switches the CH1 interface mode.
(The Q series C24 I/O signals X/Y00 to X/Y1F)
Changes the operation mode to MC protocol
format 1
Mode
Reception Transmission Reception
Abnormal
switching processing processing
read request reception
instruction
detection
Sets the transmission specifications
Writes the mode switching designation
contents to the buffer memory
Sets the mode switching request
Resets the mode switching error signal
Reads the mode switching request contents
Mode switching complete
Modification of the setting values of the buffer memory
special applications area
Changes the setting value of
the communication protocol according to
the communication specification
Mode switching complete reset
15
Error processing (LED OFF, error code clear)
Mode switching request clear by clear
command
15.4 Switching the Mode from the Programmable Controller CPU
355
15.5
Switching the Mode from an External Device
This section shows how the Q series C24 mode is switched from an external device.
15.5.1
Mode switching procedure
The following explains the procedure for switching the Q series C24 mode from an external device.
*1
External device
Mode switching
command
message
*5
Mode switching
response
message
Programmable
controller CPU
(Normal end)
Approx. 400 ms
Mode switching in progress
X6/XD
*2
CH
ERR. communication error
Q series C24 ready
XE/XF
X1E
*3
Switch setting error, mode switching
error storage area (address 203H)
FROM
(Only when normal)
*3
Buffer memory special applications area
Data communications initialization
setting area described in
User's Manual (Basic).
Addresses 93H to 121H/133H to 1C1H
*1
*2
*3
*4
*5
TO
Data
communications
possible
default value modification
(Performed only when necessary)
*4
Data communications impossible
Data communicationspossible
Inform in advance all the connected devices that data communications by mode switching cannot be performed.
When XE and XF were turned on, check the error contents as described in the User's Manual (Basic) and take the
corresponding action.
• Checking of mode switching designation contents for buffer memory mode switching area and writing of mode
switching designation contents within the range that can be designated.
• Re-execution of mode switching
When the mode was switched from an external device, after mode switching is complete, read and write the buffer
memory special applications area shown below from the programmable controller CPU.
• Switch setting error, mode switching error storage area (address: 203H)
• Data communications initialization setting areas (addresses: 93H to 121H /133H to 1C1H) described in the User's
Manual (Basic).
After checking that mode switching was completed normally, inform all the connected devices that data communications
are possible and restart data communications.
For the message format, refer to MELSEC Communication Protocol Reference Manual.
Remark
To check the Q series C24 mode (communication protocol, transmission specifications) after switching, read the buffer
memories (addresses: 252H to 253H, 262H to 263H) described in the User's Manual (Basic).
(To check the external device, read the buffer memory with the MC protocol buffer memory read function.)
356
CHAPTER 15 SWITCHING THE MODE AFTER STARTING
15.5.2
Mode switching sample program
The following shows a programmable controller CPU sample sequence program that switches the CH1 interface mode
from an external device.
(The Q series C24 I/O signals X/Y00 to X/Y1F)
Reads the mode switching error
contents.
Mode switching complete.
Remodification of setting value of buffer memory special
applications area
Changes the setting value of
the communication protocol according
to the communication specification.
Mode switching complete reset.
Error processing (LED OFF, error code clear)
15
15.5 Switching the Mode from an External Device
357
CHAPTER 16 USING COMMUNICATION DATA
MONITORING FUNCTION
The following describes the QJ71C24N (-R2/R4) and LJ71C24(-R2) communication data monitoring functions.
16.1
Communication Data Monitoring Function
16.1.1
Overview
Communication data monitoring function is a function to monitor communication data between the QJ71C24N (R2/R4) or LJ71C24(-R2) and an external device on communication lines.
The system startup time can be reduced by analyzing the communication data on the communication lines when
debugging the system.
The following two methods are for the communication data monitoring.
(1) Communication data monitoring by the sequence program (Explained in this
section)
Monitoring is performed by the monitor start instruction written in the communication data monitoring specification
area of the buffer memory.
(2) Communication data monitoring by GX Configurator-SC
The debugging support function of the GX Configurator-SC protocol FB support in used for monitoring (circuit
trace).
See the Operating Manual (Protocol FB support function) for the debugging support function of the GX
Configurator-SC protocol FB support.
This section describes the communication data monitoring by the sequence program.
358
CHAPTER 16 USING COMMUNICATION DATA MONITORING FUNCTION
16.1.2
Communication data monitoring operation
The following describes the communication data monitoring operation.
● When using the communication data monitoring function, the total transmission speed of the two interfaces should not
exceed 115200 bps.
● The communication data monitoring function is effective when the communication protocol is assigned to 0H to 9H.
(1) Monitor start
(a) Monitor start instruction "0001H" is written in the communication data monitoring
specification area (Address: 2018H/2118H). (Set by user)
(b) By the monitor start instruction, the monitor data pointer/monitor data size area are
cleared to 0 and "0002H" is written in the communication data monitoring
specification area which starts monitoring.*1 (Q series C24 is set.)
(c) When a monitor setting error occurs, "100FH" is written in the communication data
monitoring specification area. (Q series C24 is set.)
Check the monitor buffer head address and the monitor buffer size setting range and perform monitoring again.
*1
16
Monitor data area (Default address: 2602H to 32FFH/3302H to 3FFFH) is not cleared to 0.
16.1 Communication Data Monitoring Function
359
(2) During monitoring
(a) After monitoring starts, data of reception, transmission, receiving error, and signal
change are stored from the head address of the monitor data area in the order of
occurrence.
(b) When the monitoring data exceeds the capacity of the monitor data area, monitoring
is continued by writing new data over the oldest data.
However, monitoring may automatically stop according to the settings of the monitor option area (Address:
2019H/2119H). ( Page 363, Section 16.2 (2) (a))
(CH1)
2600H
Buffer memory
2601H
0CFEH
0003H
Monitor data pointer storage area
Monitor data size storage area
2602H
+0
2603H
+1
2604H
2605H
+2
Oldest data
+3
2606H
Monitor data area
to
32FFH
(Default value)
(c) Each data is stored in the monitor data area using the following timing.
Data classification
When receiving data
Transmitted data
When transmitting data
Receiving error data
When detecting receiving errors
RS-232
line
360
Data storage timing
Received data
RS (RTS), ER (DTR) signals
When changing the RS (RTS), ER (DTR) signals
CS (CTS), DR (DSR), CD
(DCD) signals
When signal changes are detected during the periodic processing (Operation interval: 1 to
19ms) as well as for the above timing (Monitoring is not performed during the periodic
processing)
CHAPTER 16 USING COMMUNICATION DATA MONITORING FUNCTION
(3) Monitor stop
Monitoring stops if any of the following conditions is satisfied.
(a) Monitor stop by user instructions
Monitoring stops if "0000H" is written in the communication data monitoring specification area of the buffer
memory. (Set by the user)
(b) Monitor stop by the system when the monitor data area is full
• The full stop specification (bit 0) of the monitor option specification area of the buffer memory is set to
"ON".
• When the monitor data area is full (monitor buffer size), monitoring is automatically stopped and "1002H"
is written in the communication data monitoring specification area. (Set by the Q series C24)
(c) Monitor stop by the system when the timer 0 error occurs
• The timer 0 error stop specification (bit 2) of the monitor option specification area of the buffer memory is
set to "ON".
• When the timer 0 error (error code 7F40H) occurs, monitoring is automatically stopped and "1002H" is
written in the communication data monitoring specification area. (Set by the Q series C24)*1
*1
Part of the data immediately after the occurrence of a timer 0 error may be entered in the monitor data area.
16
16.1 Communication Data Monitoring Function
361
16.2
Communication Data Monitoring Function Settings
Settings for the communication data monitoring function can be configured on the "Transmission control and other
system setting" screen of GX Configurator-SC or in the sequence program.
(1) GX Configurator-SC setting for the communication data monitoring function
The setting items for the communication data monitoring function are listed below.
See Page 363, Section 16.2 (2) in this section for setting details.
[Transmission control and other system setting screen]
[Setting items]
Setting items
Setting values
Send/Receive data monitoring designation
No monitoring/Monitor stop,
Monitor start
Item details
Select "monitor start" for constant monitoring.
Action for buffer full
Continue/Stop
Select "stop" to stop monitoring when the monitor data area is full.
Stop by Timer 0 error
Continue/Stop
Select "stop" to stop monitoring when a timer 0 error occurs.
Monitor buffer head address
Monitor buffer size
362
0400H to 1AFDH, 2600H to 3FFDH
0003H to 1A00H
Enter a value to change the monitor buffer address.
(Default address: 2600H/3300H)
Enter a value the monitor buffer size.
(Default: 0D00H)
CHAPTER 16 USING COMMUNICATION DATA MONITORING FUNCTION
(2) Buffer memory for communication data monitoring function
(a) Communication data monitoring specification area (Address: 2018H/2118H)
Set start/stop of the communication data monitoring.
See Page 359, Section 16.1.2 for communication data monitoring setting operation.
to
b15
b0
(Default: 0000H)
Buffer memory address 2018H/2118H
Set the monitor start/stop.
0000H: No monitor/Monitor stop
0001H: Monitor start
0002H: Monitoring (Set by Q series C24)
1002H: Monitor stop (Set by Q series C24)
100FH: Monitor setting error (Set by Q series C24)
(b) Monitor option specification area (Address: 2019H/2119H)
Specify the options of the communication data monitoring function.
b15
Buffer memory address
2019H/2119H
to
b3 b2
0
1/0
b1 b0
0 1/0 (Default: 0000H)
Action for buffer full
0H: OFF
1H: ON
16
Stop by timer 0 error
0H: OFF
1H: ON
• When action for buffer full is OFF: When the monitoring data exceeds the capacity of the monitor data
area, monitoring continues by writing the new data over the oldest data.
• When action for buffer full is ON: When the monitor data area is full (monitor buffer size), monitoring is
automatically stopped and "1002H" is written in the communication data monitoring specification area.
(Set by the Q series C24)
• Stop by timer 0 error (bit 2)
• When the stop by timer 0 error is OFF: Monitoring continues even if the timer 0 error (error code 7F40H)
occurs.
• When the stop by timer 0 error is ON: When the timer 0 error (error code 7F40H) occurs, monitoring is
automatically stopped and "1002H" is written in the communication data monitoring specification area.
(Set by the Q series C24)
(c) Monitor buffer head address specification area (Address: 201AH/211AH)
Specify the head address of the storage area (monitor data area) for the monitor data within the range of the
user's free area of the buffer memory.
Setting range: 0400H to 1AFDH, 2600H to 3FFDH (Default: 2600H/3300H)
(d) Monitor buffer size specification area (Address: 201BH/211BH)
Set the size of the monitor data area.
Setting range: 0003H to 1A00H (Default: 0D00H)
363
16.2 Communication Data Monitoring Function Settings
• Action for buffer full (bit 0)
(e) Monitor data pointer storage area (Address: according to monitor buffer head
address setting (Default: 2600H/3300H))
• The oldest data position of the monitor data area is stored using the offset value from the head address of
the monitor data area.
• 0 to (monitor buffer size specification (Default: 0D00H) -3): oldest data position
• When the monitoring data exceeds the monitor buffer size, the new data is written over the oldest data. (Ring
buffer type) The oldest data position of the monitor data area can be confirmed from this area.
"2611H" becomes the oldest data when "000FH" is the monitor data pointer using "2602H" as the head
address of the monitor data area.
Monitor data pointer
storage area
+0
+1
+2
+3
+4
+5
+6
+7
+8
+9
+A
+B
+C
+D
+E
+F
Monitor data size
storage area
Oldest data in the
monitor data area
(f) Monitor data size area (Address: according to the monitor buffer head address
setting (Default: 2601H/3301H))
The number of monitor data stored in the monitor data area is stored.
0 to (monitor buffer size specification (Default: 0D00H) -2): Number of monitor data
364
CHAPTER 16 USING COMMUNICATION DATA MONITORING FUNCTION
(g) The monitor data area (Default addresses: 2602H to 32FFH /3302H to 3FFFH)
The monitor data are stored in one-word units as shown in the configuration below.
See Page 366, Section 16.3 for an example of the communication data monitoring.
b15
b14
b13
b12
b11
b10
b9
b8
b7
b6
b5
b4
b3
b2
0
0
0
0
*
CD
CS
DR
(DCD) (CTS) (DSR)
Received data
Whe n receiving data
0
0
0
1
*
CD
CS
DR
(DCD) (CTS) (DSR)
Transmitted data
When transmitting data
0
0
1
0
*
CD
CS
DR
(DCD) (CTS) (DSR)
0
0
1
1
*
CD
CS
DR
(DCD) (CTS) (DSR)
*
CD
CS
DR
(DCD) (CTS) (DSR)
0
FE
0
b1
b0
RS
ER
(RTS) (DTR)
When the RS(RTS)/ER(DTR)
signal is changed
OVR
When a reception error occurs
PE
(*1)
0
1
0
0
Signal condition (b8 to b11)
Data classification
(b12 to b15)
* System area
0: When receiving data
1: When transmitting data
2: When the RS(RTS)/ER(DTR)
signal is changed
3: When a reception error occurs
4: When detecting a CD(DCD) to
DR(DSR) signal change
0
When detecting a CD(DCD) to
DR(DSR) signal change
*1 FE: Framing error
OVR: Overrun error
PE: Parity error
16
16.2 Communication Data Monitoring Function Settings
365
16.3
Communication Data Monitoring Example
The following is an example of the data monitoring of nonprocedural protocol communication.
(1) System configuration
The system configuration for the sample program is as shown below.
The CH used for operation of this sample program is CH1 only.
CH1: Transmission channel
CH2: Reception channel
GX Developer
QJ71C24N-R2
(2) Program condition
This is a program to monitor transmitted data from CH1 of the QJ71C24N-R2 with user instructions.
(a) GX Developer switch setting
Switch number
Setting value
Switch 1
07C2
Switch 2
0006
Switch 3
07C2
Switch 4
0006
Switch 5
0000
(b) Devices used by the user
• Monitor start instruction signal: X20
• Monitor option specification signal: X21
• Monitor stop instruction signal: X22
• During monitor start instructions: M20
• During monitoring: M21
• During monitor stop instructions: M22
• Communication data monitoring specification area storage condition: D300
• Monitor option specification area storage condition: D301
366
CHAPTER 16 USING COMMUNICATION DATA MONITORING FUNCTION
(c) Sample program
<Monitor start (X20 is ON)>
Monitor data area is cleared to 0
Monitor start being instructed
Monitoring (0002H)
Monitor setting error (100FH)
<Monitor option (X21 is ON)>
During monitor stop (1002H)
<Monitor stop (X22 is ON)>
Monitor stop being instructed
16
Monitor stop (0000H)
16.3 Communication Data Monitoring Example
367
(3) Confirming monitor data by GX Developer
The monitor data area for CH1 (Address: 2602H to 32FFH) is monitored on the buffer memory batch monitoring
screen of GX Developer.
See Page 365, Section 16.2 (2) (g) for the data configuration of the monitor data area.
The following data are sent from CH1 using non procedure protocol.
Transmitted data; "ABCDEFGH" + 0D0AH (five-word)
b15
b14
b13
b12
b11
b10
b9
b8
b7
b6
b5
b4
b3
b2
b1
b0
0
0
0
1
0
0
1
1
0
1
0
0
0
0
0
1
* System area
368
*
CD CS DR
(DCD)(CTS) (DSR)
Data transmission
When transmitting data
CHAPTER 17 DEDICATED INSTRUCTIONS
CHAPTER 17 DEDICATED INSTRUCTIONS
17
Dedicated instructions are used to simplify programming when using the intelligent functional module functions.
Among the dedicated instructions for the QJ71C24N(-R2/R4) and QJ71C24(-R2) explained in this manual, this chapter
focuses on the instructions that can be used for QCPU.
There are restrictions on the function version and the serial number of the QJ71C24N(-R2/R4) and QJ71C24(-R2) that
can use the dedicated instructions.
For details, refer to the Q Corresponding Serial Communication Module User's Manual (Basic).
17.1
Dedicated Instruction List and Available Devices
(1) Dedicated instruction list
The following table lists the dedicated instructions explained in this chapter.
Application
Dedicated
instruction
The programmable controller CPU
monitoring function
Receives data by an interrupt program during data communication via the
non procedure protocol or bidirectional protocol.
Page 371, Section
17.2
PRR*1
Employs user frames to perform data communication via the non procedure
protocol according to the contents defined in the transmission user frame
designation area.
Page 393, Section
17.6
Sets the units (word/byte) of transmission/reception data count.
Page 384, Section
17.4
Registers/cancels programmable controller CPU monitoring in order to use
the programmable controller CPU monitoring functions.
Page 375, Section
17.3
PUTE
Registers a user frame.
Page 398, Section
17.7
GETE
Reads a user frame.
Page 389, Section
17.5
Mode switching
UINI
Changes the mode, transmission specifications and host station No. of the Q
series C24.
Page 402, Section
17.8
CSET
The user should not change data (control data, request data, etc.) designated by a dedicated instruction until the execution
of that instruction is completed.
*1
To change the following values preset in the buffer memory for use of dedicated instructions, use GX Configurator-SC or
execute the CSET instruction (Initial setting) before starting data exchange. ( Page 384, Section 17.4)
• Word/byte units designation (address: 96H/136H)
• Transmission buffer memory head address designation (address: A2H/142H)
• Transmission buffer memory length designation (address: A3H/143H)
• Receive buffer memory head address designation (address: A6H/146H)
• Receive buffer memory length designation (address: A7H/147H)
The dedicated instructions are executed based on the values preset in the buffer memory at module startup or those that
have been changed by the CSET instruction (Initial setting).
369
17.1 Dedicated Instruction List and Available Devices
Registration/reading of user frames to
Flash ROM
Reference section
BUFRCVS*1
Data transmission/reception
Setting the units of communication
data count
Functional description
(2) Available devices
The following devices are available for the dedicated instructions:
Internal devices
*1
Word
Bit
X, Y, M, L, F, V, B
*1
*2
370
T, ST, C, D, W
File register
Constant*2
R, ZR
K, H
Word device bit designation can be used as bit data. Word device bit designation is done by designating [Word
device.Bit No.]
(Designation of bit numbers is done in hexadecimal.)
For example, bit 10 of D0 is designated as [D0.A].
However, there can be no bit designation for timers (T), retentive timers (ST) and counters (C).
Available devices are given in each of the Constant field.
CHAPTER 17 DEDICATED INSTRUCTIONS
17.2
Z.BUFRCVS
17
This instruction is used to receive data by an interrupt program through non procedure or bidirectional protocol
communication.
Applicable device
Setting
data
Internal device
Bit
Word
File register
(S)


(D)


Bit
Word
Intelligent function
module device U\G
Index register
Zn
Constant
K, H
Others




[Executing
condition]
[Instruction
code]
Link direct device J\
[Instruction format]
Z.BUFRCVS
Z.BUFRCVS
"Un"
(S)
(D)
*1
*1
17.2.1
If the host station is a Basic model QCPU (function version B or later), Universal model QCPU, or LCPU, " " (double
quotation) of the first argument can be omitted.
Setting data
Setting data
Description
Start I/O signal of the module
(00 to FE: The 2 upper digits of an input/output signal expressed in 3-digit.)
"Un"/Un
(S)
Reception channel number
1: Channel 1 (CH1 side)
2: Channel 2 (CH2 side)
(D)
Head number of the devices that store receive data
* Receive data is read from the reception area of the buffer memory.
Setting range
Set by
Data type
0 to FEH
User
String/BIN-16 bit
1, 2
User
Device name
17.2 Z.BUFRCVS

System
The file registers of each of the local device and the program cannot be used as the setting data.
17.2.2
Receive data
Device
Item
(D)+0
Receive data length
(D)+1

(D)+n
Receive data
*1
Setting data
Stores the number of data read from the receive data count storage area.
*1(0
or higher).
Stores data read from the receive data count storage area in sequence,
starting from the lowest-numbered address.
Setting range
Set by

System

System
According to the "Word/byte units designation" by GX Configurator-SC, the number of bytes is stored when byte is
designated and the number of words is stored when word is designated.
Remark
● For information about errors caused by incorrect data designated by the user, refer to "Errors" described later.
When a reception error occurs, the error code can be read from the data reception result storage area (address:
258H/268H) in the buffer memory.
● The "Set by" column indicates the following:
• User: Data set by the user before executing the dedicated instruction.
• System: The programmable controller CPU stores execution results of the dedicated instruction.
371
17.2.3
Functions
(1) This instruction stores data received from an external device to a designated
device.
(2) This instruction can identify the address of the reception area in the buffer
memory and read relevant receive data.
(3) When this instruction is executed, reception is completed and the reception
data read request signal (X3/XA) or the reception abnormal detection signal
(X4/XB) is turned off automatically.
It is not necessary to turn on the reception data read completion signal (Y1/Y8) when receive data is read by this
instruction.
(4) The BUFRCVS instruction is used by an interrupt program and its processing
is completed in one scan.
[Operation when the BUFRCVS instruction is being executed]
Scan
END processing
Sequence program
Interrupt program
BUFRCVS instruction
Instruction execution
Data reception
17.2.4
Receive data storage
Errors
(1) When the dedicated instruction is completed abnormally, the error flag (SM0)
turns on and the error code is stored in SD0.
See the following manuals regarding the error code, and check the errors and take corrective actions.
<Error codes>
4FFFH or less: User's manual (hardware design, maintenance and inspection) for the CPU module used
7000H or higher: User's Manual (Basic)
372
CHAPTER 17 DEDICATED INSTRUCTIONS
17.2.5
Precaution when using the BUFRCVS instruction
17
(1) Use the BUFRCVS instruction when receiving data via an interrupt program.
(2) Simultaneous execution of dedicated instructions
The following table lists the handling for when executing another instruction during execution of the BUFRCVS
instruction or executing the BUFRCVS instruction during execution of another instruction in the same channel.
Instruction*1
OUTPUT
PRR
Availability of
simultaneous
execution
Handling of simultaneous execution


INPUT

BIDOUT


BIDIN
INPUT instruction and BUFRCVS instruction cannot be used at the same time.
(However, simultaneous execution is available when channels to be used are not the same.)

BIDIN instruction and BUFRCVS instruction cannot be used at the same time.
(However, simultaneous execution is available when channels to be used are not the same.)
CSET
PUTE
GETE

BUFRCVS

SPBUSY
UINI
: Available, : Not available
*1
(3) The device storing data received via the BUFRCVS instruction must have an
area that is large enough to store the maximum size of data received from the
external device.
If an area large enough to store the maximum size of data received from the external device is not secured, the
data following the storage device will be overwritten.
373
17.2 Z.BUFRCVS
Because the dedicated instructions listed below use a different communication protocol from that for the BUFRCVS
instruction, they are not used in the same channel.
• ONDEMAND
• CPRTCL
17.2.6
Program example
An interrupt program that reads receive data.
(Setting)
• Interrupt pointer setting with GX Developer
Item
Description
PLC side:
Interrupt pointer Start No. = 50, Interrupt pointer No. of module = 2
(fixed)
• CH1 side interrupt pointer = I50, CH2 side interrupt pointer = I51
Intelli. module side:
Start I/O No. = 0, Start SI No. = 0 (fixed)
• Interrupt program start enable/disable setting with GX Configurator-SC
• CH1 side: Issues interrupt (performs communication via the non procedure protocol.)
• CH2 side: Does not issue interrupt
When the input/output signals of the Q series C24 are X/Y00 to X/Y1F
<Interrupt program enabled
>
In case of CH1 side
<Normal reception
>
<Abnormal reception
>
Sets the checking flag for normal
reception/abnormal reception via
the main program.
* Resets on the main program side
<Reception interrupt program execution>
Receives data and stores
in D200 and later.
D200: Receive data count
D201 and later: Receive data
374
CHAPTER 17 DEDICATED INSTRUCTIONS
17.3
ZP.CSET (Programmable Controller CPU Monitoring
Register/Cancel)
17
With this instruction, monitoring of the programmable controller CPU can be registered or cancelled.
Applicable device
Setting
data
Internal device
Bit
File register
Word
Link direct device
J\
Bit
Word
Intelligent function
module device
U\G
(S1)


(S2)



(D1)



(D2)



[Instruction
code]
[Executing
condition]
Index register
Zn

Constant
K, H
Others


[Instruction format]
ZP.CSET
ZP.CSET
"Un"
(S1)
(S2)
(D1)
(D2)
*1
*1
If the host station is a Basic model QCPU (function version B or later), Universal model QCPU, or LCPU, " " (double
quotation) of the first argument can be omitted.
17.3.1
Setting data
Setting data
Data type
Start I/O signal of the module
(00 to FE: The 2 upper digits of an input/output signal expressed in 3-digit.)
User
String/BIN-16 bit
(S1)
Channel No. for sending the monitoring result
1: Channel 1 (CH1 side)
2: Channel 2 (CH2 side)
User
BIN-16 bit
(S2)
Head number of the devices that store control data
(D1)
Dummy
(D2)
Head bit device number of the local station that turns ON for one scan upon instruction
completion.
(D2)+1 also turns ON if the instruction execution completes abnormally.
User, System
Device name

Device name
System
Bit
The file registers of each of the local device and the program cannot be used as the setting data.
375
17.3 ZP.CSET (Programmable Controller CPU Monitoring Register/Cancel)
Set by
"Un"/Un
Description
17.3.2
Control data
(1) Registering the programmable controller CPU monitoring
Device
Setting range
Set by
(S2)+0
Execution type
Item
Designate 0.
0
User
(S2)+1
Completion status
Stores the result of execution upon completion of an instruction.
0: Normal
Other than 0: Error code

System
(S2)+2
Request type
Designate the request content.
2: Registers programmable controller CPU monitoring.
2
(S2)+3
Cycle time units
Designate the unit of cycle time.
0: 100ms
1: s
2: min
(S2)+4
Cycle time
Designate the cycle time.
1H to FFFFH: Cycle time
(S2)+5
Programmable controller CPU monitoring
function
Designate the monitoring function.
1: Constant cycle transmission
2: Condition agreement transmission
(S2)+6
Programmable controller CPU monitoring
transmission measure
(S2)+7
User frame output head pointer
Setting data
Designate the transmission measure.
0: Data transmission (device data, CPU abnormal information)
0 to 2
1H to FFFFH
1, 2
0, 1
1: Notification*1
Designate the head pointer of the table setting the user frame
numbers for constant cycle transmission.
0: No designation (at condition agreement transmission and
0, 1 to 100
notification*1)
1 to 100: Head pointer
(S2)+8
Constant
cycle
transmission
User frame transmission count
Designate the user frame transmission (output) counts for
constant cycle transmission.
0: No designation (at condition agreement transmission and
0, 1 to 100
notification*1)
1 to 100: Transmission count
Designate the data No. for connecting the modem function when
(S2)+9
User
Modem connection data No.
sending notifications in constant cycle transmission.*2
0: No designation (at data transmission and condition agreement
transmission)
BB8H to BD5H: Data No. for connection (flash ROM)
8001H to 801FH: Data No. for connection (buffer memory)
0,
BB8H to
BD5H,
8001H to
801FH
(S2)+10
Registered word blocks count
Designate the number of blocks of a word device to be monitored.
0 to 10
(S2)+11
Registered bit blocks count
Designate the number of blocks of a bit device to be monitored.
0 to 10
(S2)+12
Programmable controller CPU abnormal
monitoring
(Programmable controller CPU status
monitoring)
Designate whether or not to execute abnormal monitoring for the
programmable controller CPU.
0: Do not monitor.
1: Monitor.
0, 1
(S2)+13
Programmable
controller CPU
monitoring setting
Designate the code of a device to be monitored.
0: Do not monitor device.
Other than 0: Device code.
376
Device code
Page 38,
Section 2.2.2
(4)
CHAPTER 17 DEDICATED INSTRUCTIONS
Device
Item
(S2)+14
(S2)+15
(S2)+16
Setting data
Setting range
Monitoring head device
Designate the head number of the monitoring device in this block.
0 or more
Registration points
Designate the registration points (read points) for this block.
0: Do not monitor device.
0: Do not monitor device.
• For a bit device, designate the points in word units.
(S2)+17
Monitoring
condition
Designate the monitoring condition for this block.
0: No designation (at constant cycle transmission)
1 or more: Monitoring condition
(S2)+18
Monitoring
condition
value
Designate the monitoring condition value for this block.
0 or more: Monitoring condition
• Designate 0 for constant cycle transmission.
(S2)+19
User frame
output head
pointer
1st
(first block)
Condition
agreement
transmission
(S2)+20
User frame
transmission
count
Designate the head pointer of the table designating the user
frame number for condition agreement transmission for this block.
0: No designation (at constant cycle transmission and
(S2)+21
(S2)+22 to
(S2)+102
Programmable controller CPU monitoring setting
2nd to 10th
(2nd to 10th block)
0, 1 or more
Page 37,
Section 2.2.2
(2)
0, 1 to 100
Designate the user frame transmission (output) count in condition
agreement transmission for this block.
0: No designation (at constant cycle transmission and
0, 1 to 100
notification*1)
1 to 100: Transmission count
block.*3
0: No designation (at data transmission and constant cycle
transmission)
BB8H to BD5H: Data No. for connection (flash ROM)
8001H to 801FH: Data No. for connection (buffer memory)
The same arrangement as the first programmable controller CPU
monitoring setting item.
0,
BB8H to
BD5H,
8001H to
801FH
0
(S2)+106
Designate the fixed value when the CPU status monitoring is
performed.
(S2)+107
0
1
5
(S2)+108
(S2)+109
17.3 ZP.CSET (Programmable Controller CPU Monitoring Register/Cancel)
1
(S2)+104
Fixed value
User

(S2)+103
(S2)+105
17
notification*1)
1 to 100: Head pointer
Designate the data No. for connecting the modem function when
sending notifications in condition agreement transmission for this
Modem
connection
data No.
Set by
1
CPU status
monitoring setting
(Abnormal
monitoring) 11th
(11th block)
(S2)+110
Condition
agreement
transmission
User frame
output head
pointer
User frame
transmission
count
Designate the head pointer of the table designating the user
frame number for condition agreement transmission for this block.
0: No designation (at constant cycle transmission and
Designate the user frame transmission (output) count in condition
agreement transmission for this block.
0: No designation (at constant cycle transmission and
(S2)+111
*1
*2
*3
0, 1 to 100
notification*1)
1 to 100: Transmission count
Designate the data No. for connecting the modem function when
sending notifications in condition agreement transmission for this
Modem
connection
data No.
0, 1 to 100
notification*1)
1 to 100: Head pointer
block.*3
0: No designation (at data transmission and constant cycle
transmission)
BB8H to BD5H: Data No. for connection (flash ROM)
8001H to 801FH: Data No. for connection (buffer memory)
0,
BB8H to
BD5H,
8001H to
801FH
For the LJ71C24(-R2), notification function cannot be used.
For the LJ71C24(-R2), use the modem function to designate the data No. for connecting when executing the constant
cycle transmission.
For the LJ71C24(-R2), use this block to designate the data No. for connecting when executing the condition agreement
transmission.
377
(2) Canceling the programmable controller CPU monitoring
Device
(S2)+0
Item
Setting data
Setting range
Set by
Execution type
Designate 0H.
0
User
(S2)+1
Completion status
Stores the result of execution upon completion of an instruction.
0: Normal
Other than 0: Error code

System
(S2)+2
Request type
Designate the request content.
3: Cancels the programmable controller CPU monitoring.
3
User
For system
Use prohibited
(including for any other purposes such as for programs)

System
(S2)+3

(S2)+111
Remark
● For information about errors caused by incorrect data designated by the user, see the description in "Errors".
● The "Set by" column indicates the following:
• User: Data set by the user before executing the dedicated instruction.
• System: The programmable controller CPU stores execution results of the dedicated instruction.
378
CHAPTER 17 DEDICATED INSTRUCTIONS
17.3.3
Functions
17
(1) To register the programmable controller CPU monitoring, this instruction
registers data necessary for the Q series C24 to execute the programmable
controller CPU monitoring function.
When the data registration to execute the programmable controller CPU monitoring function is completed
normally, the Q series C24 begins monitoring the programmable controller CPU and transmitting monitoring
results to an external device.
(2) To cancel the programmable controller CPU monitoring, this instruction ends
the Q series C24's monitoring operation of the programmable controller CPU.
When canceling of the programmable controller CPU monitoring is completed normally, the Q series C24
terminates the operation of the programmable controller CPU monitoring function.
(3) A maximum of 10 blocks can be designated for a word device or bit device to
monitor the device memory.
To register the device memory to monitor, designate the word device blocks for the registered word blocks, then
designate the bit device blocks for the registered bit blocks.
(4) Before sending the programmable controller CPU monitoring results to the
external device, the user frame and user frame number should be registered
with GX Configurator-SC in advance.
(6) Whether the CSET instruction is being executed or has been completed
normally/abnormally can be checked by the completion device (D2)
designated as a setting data.
(a) Completion device ((D2) + 0)
Turns on at the END processing of the scan where the CSET instruction is completed, and turns off at the next
END processing.
(b) Completion device ((D2) + 1)
Turns on and off depending on the completion status of the CSET instruction.
• Normal completion: Stays off and does not change.
• Abnormal completion: Turns on at the END processing of the scan where the CSET instruction is
completed, and turns off at the next END processing.
379
17.3 ZP.CSET (Programmable Controller CPU Monitoring Register/Cancel)
(5) To register the programmable controller CPU monitoring once again, cancel
the programmable controller CPU monitoring before registration.
(7) When the programmable controller CPU monitoring registration is performed,
the corresponding interface data communication protocol setting is only
designated when non procedure protocol is used for the following data for
designation in the control data.
• User frame output head pointer for constant cycle sending/ batch conditions sending.
• User frame transmission count for constant cycle sending/ batch conditions sending.
When the communication protocol setting for the corresponding interface is MC protocol, there is no need to
designate the user frame output head pointer and the user frame transmission count.
(It is ignored when being designated.)
(8) Simultaneous execution of dedicated instructions
The following table lists the handling for when executing another instruction during execution of the CSET
instruction or executing the CSET instruction during execution of another instruction in the same channel.
Availability of
simultaneous
execution
Instruction*1
ONDEMAND

OUTPUT
PRR
INPUT
(the right column)
CSET

Handling of simultaneous execution
• Dedicated instructions simultaneous execution error (7FF0H) occurs in the dedicated instruction attempted
later.
(However, simultaneous execution is available when channels to be used are not the same.)
[When instructions are executed in order of INPUT  CSET]
• Dedicated instructions simultaneous execution error (7FF0H) occurs in the CSET instruction.
(However, simultaneous execution is available when channels to be used are not the same.)
[When instructions are executed in order of CSET  INPUT]
• Simultaneous execution is available.
• The next instruction will be ignored until the active instruction has been completed.
(However, simultaneous execution is available when channels to be used are not the same.)
PUTE
GETE

BUFRCVS

SPBUSY

UINI
• Dedicated instructions simultaneous execution error (7FF0H) occurs in the dedicated instruction attempted
later.
: Available, : Not available
*1
Because the dedicated instructions listed below use a different communication protocol from that for the CSET
instruction (programmable controller CPU Monitoring Register/Cancel), they are not used in the same channel.
• BIDOUT, BIDIN
• CPRTCL
If the dedicated instructions above are used in the same channel with the CSET instruction, the communication protocol
setting error (7FF2H) occurs.
[Operation when a CSET instruction is being executed]
Sequence program
CSET instruction
Scan
END
processing
Scan
END
processing
Scan
Instruction execution
Completion device
Abnormal completion
Completion device + 1
Q series C24
380
Setting processing
END
processing
CHAPTER 17 DEDICATED INSTRUCTIONS
17.3.4
Errors
17
(1) When the dedicated instruction is completed abnormally, the error flag (SM0)
turns on and the error code is stored in SD0.
See the following manuals regarding the error code, and check the errors and take corrective actions.
<Error codes>
4FFFH or less: User's manual (hardware design, maintenance and inspection) for the CPU module used
7000H or higher: User's Manual (Basic)
(2) The programmable controller CPU monitoring setting (control data (S2) + 13 to
(S2) + 102) is not checked when the CSET instruction is executed, but when
the designated cycle time elapses.
In the case the monitoring data registered from the Q series C24 is not sent after the CSET instruction is
completed normally and the designated cycle time elapses, check the programmable controller CPU monitoring
function execution result (buffer memory 2205H/2305H) to check the errors, and take corrective actions.
17.3 ZP.CSET (Programmable Controller CPU Monitoring Register/Cancel)
381
17.3.5
Program example
(1) A program that registers the programmable controller CPU monitoring
The following example shows how to register the programmable controller CPU monitoring and send the
monitoring results from the interface on the CH1 side.*1
*1
The following registration is done to send the contents of M0 to M15 and D100 to D109 to the external device on a
constant cycle (cycle time is 3 min).
When the input/output signals of the Q series C24 are X/Y00 to X/Y1F
Converts registration command to pulses
Sets execution type
Sets request type (programmable controller CPU
monitoring registration)
Sets cycle time unit to minutes
Sets cycle time to 3 (minutes)
Sets the monitoring function to constant cycle transmission
Sets the means of transmission to data transmission
Sets the output head pointer
Sets the transmission count of the user frame
Sets data set complete flag -1
Sets the number of registered word blocks to 1
Sets the number of registered bit blocks to 1
Registers the devices for D100 to D109 as the first block
Registers the devices for M0 to M15 as the second block
Sets data setting complete flag -2
Executes programmable controller CPU
monitoring registration
Normal completion
Abnormal completion
382
CHAPTER 17 DEDICATED INSTRUCTIONS
17
(2) A program that cancels the programmable controller CPU monitoring
This following example shows how to cancel the programmable controller CPU monitoring for the interface on
CH1 side.
When the input/output signals of the Q series C24 are X/Y00 to X/Y1F
Instruction pulse set
Execute canceling the programmable
controller CPU monitoring
Normal completion
Abnormal completion
17.3 ZP.CSET (Programmable Controller CPU Monitoring Register/Cancel)
383
17.4
ZP.CSET (Initial Settings)
With this instruction, the unit of transmission/reception data (word/byte) and data communication areas can be set.
Applicable device
Setting
data
Internal device
Bit
File register
Word
Link direct device
J\
Bit
Word
Intelligent function
module device
U\G
(S1)


(S2)



(D1)



(D2)



[Instruction
code]
[Executing
condition]
Index register Zn

Constan
t K, H
Others


[Instruction format]
ZP.CSET
ZP.CSET
"Un"
(S1)
(S2)
(D1)
(D2)
*1
*1
17.4.1
If the host station is a Basic model QCPU (function version B or later), Universal model QCPU, or LCPU, " " (double
quotation) of the first argument can be omitted.
Setting data
Setting data
Set by
Data type
Start I/O signal of the module
(00 to FE: The 2 upper digits of an input/output signal expressed in 3-digit.)
User
String/BIN-16
bit
(S1)
Channel No. for sending the monitoring result
1: Channel 1 (CH1 side)
2: Channel 2 (CH2 side)
User
BIN-16 bit
(S2)
Head number of the devices that store control data
User, System
Device name

Device name
System
Bit
"Un"/Un
Description
(D1)
Dummy
(D2)
Head bit device number of the local station that turns ON for one scan upon instruction
completion.
(D2)+1 also turns ON if the instruction execution completes abnormally.
The file registers of each of the local device and the program cannot be used as the setting data.
384
CHAPTER 17 DEDICATED INSTRUCTIONS
17.4.2
Control data
Device
17
Setting range
Set by
Execution type
Designate 0.
0
User
(S2)+1
Completion status
Stores the result of execution upon completion of an
instruction.
0: Normal
Other than 0: Error code

System
(S2)+2
Request type
Designate the request content.
1: Setting of word/byte units and buffer memory assignment
change
1
(S2)+3
Word/byte units designation
Designate the units of transmission/reception data count.
0: Current setting value
1: Word units
2: Byte units
(S2)+4
On-demand function buffer
memory head address
Designate the head address of the buffer memory used with
the on-demand function.
0H: Use the current setting value
400H to 1AFFH, 2600H to 3FFFH: Head address
0H,
400H to 1AFFH,
2600H to 3FFFH
(S2)+5
On-demand function buffer
memory size
Designate the size (word number) of the buffer memory used
with the on-demand function.
0H: Use the current setting value
1H to 1A00H: Size
0H,
1H to 1A00H
Transmission area head address
Designate the head address of the transmission area used
with the non procedure /bidirectional protocol.
0H: Use the current setting value
400H to 1AFFH, 2600H to 3FFFH: Head address
0H,
400H to 1AFFH,
2600H to 3FFFH
Transmission area size
Designate the size (word number) of the transmission area
used with the non procedure /bidirectional protocol.
0H: Use the current setting value
1H to 1A00H: Size
• The head transmission area (1 word) is used as a
transmission data count designation area.
0H,
1H to 1A00H
Reception area head address
Designate the head address of the reception area used with
the non procedure /bidirectional protocol.
0H: Use the current setting value
400H to 1AFFH, 2600H to 3FFFH: Head address
0H,
400H to 1AFFH,
2600H to 3FFFH
Reception area size
Designate the size (word number) of the reception area used
with the non procedure /bidirectional protocol.
0H: Use the current setting value
1H to 1A00H: Size
• The head reception area (1 word) is used as a reception
data count storage area.
0H,
1H to 1A00H
For system
Use prohibited
(including for any other purposes such as for programs)
(S2)+0
(S2)+6
(S2)+7
(S2)+9
(S2)+10

(S2)+111
Setting data
User
0, 1, 2

User
17.4 ZP.CSET (Initial Settings)
(S2)+8
Item
System
Remark
● For information about errors caused by incorrect designated by the user, refer to "Errors" described later in this section.
● The "Set by" column indicates the following:
• User: Data set by the user before executing the dedicated instruction.
• System: The programmable controller CPU stores execution results of the dedicated instruction.
385
17.4.3
Functions
(1) This instruction changes the current values of the settings below to
transmit/receive data using the following communication protocols:
• Data count unit (word/byte) of the data to be transmitted/received
• Transmission area in the buffer memory used by the on-demand function of the MC protocol
• Transmission and reception areas in the buffer memory used with the non-procedure protocol
• Transmission and reception areas in the buffer memory used with the bidirectional protocol
(2) To change the above setting values from the programmable controller CPU,
execute the CSET instruction.
The CSET instruction must be executed before starting any data communication (execute it before the first scan).
Once data communication begins, the CSET instructions cannot be executed (the setting values cannot be
changed).
More than one CSET instruction cannot be executed simultaneously to perform the initial settings.
(3) Simultaneous execution of dedicated instructions
The following table shows the handling for when executing another instruction during execution of the CSET
instruction or executing the CSET instruction during execution of another instruction in the same channel.
Instruction
Availability of
simultaneous
execution
Handling of simultaneous execution
ONDEMAND
OUTPUT
PRR

BIDOUT
• Dedicated instructions simultaneous execution error (7FF0H) occurs in the dedicated instruction attempted
later.
(However, simultaneous execution is available when channels to be used are not the same.)
BIDIN
INPUT
(the right column)
CSET

[When instructions are executed in order of INPUT  CSET]
• Dedicated instructions simultaneous execution error (7FF0H) occurs in the CSET instruction.
(However, simultaneous execution is available when channels to be used are not the same.)
[When instructions are executed in order of CSET  INPUT]
• Simultaneous execution is available.
• The next instruction will be ignored until the active instruction has been completed.
(However, simultaneous execution is available when channels to be used are not the same.)
PUTE
GETE
BUFRCVS


SPBUSY
UINI

• Dedicated instructions simultaneous execution error (7FF0H) occurs in the dedicated instruction attempted
later.
: Available, : Not available
386
CHAPTER 17 DEDICATED INSTRUCTIONS
17
(4) Whether the CSET instruction is being executed or has been completed
normally/abnormally can be checked by the completion device (D2)
designated as a setting data.
(a) Completion device ((D2) + 0)
Turns on at the END processing of the scan where the CSET instruction is completed, and turns off at the next
END processing.
(b) Completion device ((D2) + 1)
Turns on and off depending on the completion status of the CSET instruction.
• Normal completion: Stays off and does not change.
• Abnormal completion: Turns on at the END processing of the scan where the CSET instruction is
completed, and turns off at the next END processing.
[Operation when the CSET instruction is being executed]
Sequence program
CSET instruction
Scan
END
processing
Scan
END
processing
Scan
END
processing
Instruction execution
Completion device
Abnormal completion
Completion device + 1
Q series C24
Setting processing
17.4 ZP.CSET (Initial Settings)
387
17.4.4
Errors
When the dedicated instruction is completed abnormally, the error flag (SM0) turns on and the error code is stored in
SD0.
See the following manuals regarding the error code, and check the errors and take corrective actions.
<Error codes>
4FFFH or less: User's manual (hardware design, maintenance and inspection) for the CPU module used
7000H or higher: User's Manual (Basic)
17.4.5
Program example
A program that changes the transmission buffer area for interface on CH1 side
• Set the transmission buffer to C00H to FFFH.
• Set the reception buffer to 600H to 7FFH.
When the input/output signals of the Q series C24 are X/Y00 to X/Y1F
Clears D0 to D111
Sets the execution type
Sets the request type
Sets the word/byte units to word
units
Sets the on-demand head
address
Sets the on-demand buffer size
Sets the transmission buffer head
address
Sets the transmission buffer size
Sets the reception buffer head
address
Sets the reception buffer size
Executes the initial setting
388
CHAPTER 17 DEDICATED INSTRUCTIONS
17.5
G(P).GETE
17
This instruction reads out a user frame.
Applicable device
Setting
data
Internal device
Bit
File register
Word
Link direct device
J\
Bit
Word
Intelligent function
module device
U\G
Index register Zn
(S1)



(S2)



(D)



[Instruction
code]
Constant
Others
[Executing
condition]
Command
G.GETE
G.GETE
Un
(S1)
(S2)
(D)
GP.GETE
Un
(S1)
(S2)
(D)
Command
GP.GETE
17.5.1
Setting data
Un
Setting data
Description
Start I/O signal of the module
(00 to FE: The 2 upper digits of an input/output signal expressed in 3-digit.)
Head number of the devices that store control data
(S2)
Head number of the devices storing the registered data that has been read
(D)
Head bit device number of the local station that turns ON for one scan upon instruction completion.
(D)+1 also turns on if the execution completes abnormally.
Data type
User
BIN-16 bit
User, System
System
Device name
Bit
The file registers of each of the local device and the program cannot be used as the setting data.
389
17.5 G(P).GETE
(S1)
Set by
17.5.2
Control data
Device
(S1)+0
(S1)+1
(S1)+2
Item
Setting data
Setting range
Set by

0


System
Dummy
Read result
The result of reading via the GETE instruction is stored.
0: Normal
Other than 0: Error code
Directed frame No.
Designate the user frame No.
1000 to 1199
User
Allowable number of
read bytes
Designate the maximum bytes of the user frame's registered data that
can be stored in (S2).
1 to 80
User
Registered bytes count
The number of bytes of the user frame's registered data that has been
read is stored.
1 to 80: Number of bytes of registered data

System
(S1)+3
Remark
● For information about errors caused by incorrect data designated by the user, see Page 392, Section 17.5.4.
● The "Set by" column indicates the following:
• User: Data set by the user before executing the dedicated instruction.
• System: The programmable controller CPU stores execution results of the dedicated instruction.
17.5.3
Functions
(1) This instruction reads data from the user frame in the Q series C24 as
designated by Un.
QCPU
Q series C24
b7
to
A
User frame
(S2)+0
b15 to
B
b0
+1
D
C
B
+2
F
E
C
Read
A
D
E
F
390
Read byte length
CHAPTER 17 DEDICATED INSTRUCTIONS
17
(2) Simultaneous execution of dedicated instructions
The following table lists the handling for when executing another instruction during execution of the GETE
instruction or executing the GETE instruction during execution of another instruction in the same channel.
Instruction
Availability of
simultaneous
execution
Handling of simultaneous execution


ONDEMAND
OUTPUT
PRR
INPUT
BIDOUT
BIDIN
CSET
PUTE

• Dedicated instructions simultaneous execution error (7FF0H) occurs in the dedicated instruction attempted
later.
GETE

• The next instruction will be ignored until the active instruction has been completed.
BUFRCVS
SPBUSY

UINI

CPRTCL


• Dedicated instructions simultaneous execution error (7FF0H) occurs in the dedicated instruction attempted
later.

: Available, : Not available
(a) Completion device
Turns on at the END processing of the scan where the GETE instruction is completed, and turns off at the next
END processing.
(b) Status display device at completion
Turns on and off depending on the completion status of the GETE instruction.
• Normal completion: Stays off and does not change.
• Abnormal completion: Turns on at the END processing of the scan where the GETE instruction is
completed, and turns off at the next END processing.
[Operation when the GETE instruction is being executed]
END
processing
END
processing
END
processing
END
processing
Sequence program
GETE instruction execution
Completion of reading user frames
by the GETE instruction
GETE instruction
ON
Completion device
OFF
ON
Abnormal
completion
Status display device OFF
at completion
Normal completion
One scan
391
17.5 G(P).GETE
(3) Whether the GETE instruction was completed normally/abnormally can be
checked by the completion device (D) or status display device at completion
((D)+1).
17.5.4
Errors
When the dedicated instruction is completed with an error, the complete status display device at completion ((D)+1),
turns on and the error code is stored in the control data read result ((S1)+1).
See the following manuals regarding the error code, and check the errors and take corrective actions.
<Error codes>
4FFFH or less: User's manual (hardware design, maintenance and inspection) for the CPU module used
7000H or higher: User's Manual (Basic)
17.5.5
Program example
A program that reads registered data of the user frame having registration number 3E8H to devices D4 and later
When the input/output signals of the Q series C24 are X/Y80 to X/Y9F
Read request
Sets the frame No. to be read
Sets the allowable number of data
to be read
Clears the device in which to store
the read user frame data
Executes user frame reading
Normal completion
Abnormal completion
392
CHAPTER 17 DEDICATED INSTRUCTIONS
17.6
G(P).PRR
17
In non procedure protocol communication, this instruction transmits data using a user frame according to the data
specified in the transmission user frame designation area.
Applicable device
Setting
data
Internal device
Bit
File register
Word
Link direct device
J\
Bit
Word
Intelligent function
module device
U\G
Index register Zn
(S)



(D)



[Instruction
code]
Constant
Others
[Executing
condition]
Command
G.PRR
G.PRR
Un
(S)
(D)
GP.PRR
Un
(S)
(D)
Command
GP.PRR
17.6.1
Setting data
Setting data
Description
(S)
Head number of the devices that store control data
(D)
Head bit device number of the local station that turns ON for one scan upon instruction
completion.
(D)+1 also turns on if the execution completes abnormally.
Set by
Data type
User
BIN-16 bit
User, System
Device name
System
Bit
The file registers of each of the local device and the program cannot be used as the setting data.
393
17.6 G(P).PRR
Un
Start I/O signal of the module
(00 to FE: The 2 upper digits of an input/output signal expressed in 3-digit.)
17.6.2
Control data
Device
Item
Setting data
Setting range
Set by
1, 2
User
Transmission channel
Designate the transmission channel.
1: Channel 1 (CH1 side)
2: Channel 2 (CH2 side)
Transmission result
The transmission completion result by the PRR instruction is
stored.
0: Normal
Other than 0: Error code

System
(S)+2
CR/LF addition designation
Designate whether or not to add CR/LF to the transmission
data.
0: Do not add CR/LF.
1: Add CR/LF.
0, 1
User
(S)+3
Transmission pointer
Transmission user frame designation area designates from
which the frame number data may be transmitted.
1 to 100
User
(S)+4
Output count
Designate the number of user frames to be transmitted.
1 to 100
User
(S)+0
(S)+1
Remark
● For information about errors caused by incorrect data designated by the user, see Page 396, Section 17.6.4.
● The "Set by" column indicates the following:
• User: Data set by the user before executing the dedicated instruction.
• System: The programmable controller CPU stores execution results of the dedicated instruction.
394
CHAPTER 17 DEDICATED INSTRUCTIONS
17.6.3
Functions
17
(1) This instruction transmits the user frame data using the non procedure
protocol of the Q series C24 as designated by Un, according to the control
data stored in the device designated by (S) and succeeding devices, as well as
the transmission user frame designation area of the Q series C24.
(2) Simultaneous execution of dedicated instructions
The following table lists the handling for when executing another instruction during execution of the PRR
instruction or executing the PRR instruction during execution of another instruction in the same channel.
Instruction*1
Availability of
simultaneous
execution
Handling of simultaneous execution
PRR

• The next instruction will be ignored until the active instruction has been completed.
(However, simultaneous execution is available when channels to be used are not the same.)
INPUT



• Dedicated instructions simultaneous execution error (7FF0H) occurs in the dedicated instruction
attempted later.
(However, simultaneous execution is available when channels to be used are not the same.)
OUTPUT
CSET
PUTE
GETE

BUFRCVS

SPBUSY

UINI
• Dedicated instructions simultaneous execution error (7FF0H) occurs in the dedicated instruction
attempted later.
Because the dedicated instructions listed below use a different communication protocol from that for the PRR
instruction, they are not used in the same channel.
• ONDEMAND, BIDOUT, BIDIN
• CPRTCL
If the dedicated instructions above are used in the same channel with the PRR instruction, the communication protocol
setting error (7FF2H) occurs.
(3) Whether the PRR instruction was completed normally or abnormally can be
checked with the completion device (D) or status display device at completion
((D)+1).
(a) Completion device
Turns on at the END processing of the scan where the PRR instruction is completed, and turns off at the next
END processing.
395
17.6 G(P).PRR
: Available, : Not available
*1
(b) Status display device at completion
Turns on and off depending on the completion status of the PRR instruction.
• Normal completion: Stays off and does not change.
• Abnormal completion: Turns on at the END processing of the scan where the PRR instruction is
completed, and turns off at the next END processing.
[Operation when the PRR instruction is being executed]
END
processing
END
processing
END
processing
END
processing
Sequence program
Completion of transmission
by the PRR instruction
PRR instruction execution
PRR instruction
ON
Completion device
OFF
ON
Status display device
at completion
Abnormal
completion
OFF
Normal completion
One scan
17.6.4
Errors
When the dedicated instruction is completed with an error, the status display device at completion ((D)+1), turns on
and the error code is stored in the control data transmission result ((S1)+1).
See the following manuals regarding the error code, and check the errors and take corrective actions.
<Error codes>
4FFFH or less: User's manual (hardware design, maintenance and inspection) for the CPU module used
7000H or higher: User's Manual (Basic)
396
CHAPTER 17 DEDICATED INSTRUCTIONS
17.6.5
Program example
17
A program that sends arbitrary data and the first to fifth user frames registered in the transmission frame setting
When the input/output signals of the Q series C24 are X/Y80 to X/Y9F
Transmission instruction
Sets arbitrary transmission data.
Sets the number of transmitted data.
Sets the transmission user frames
in D5 to D9.
Sets transmission frame No. in the buffer
memory.
Sets CH1 to the transmission channel.
17.6 G(P).PRR
Clears the device in which transmission
results are stored.
Sets to no CR/LF output.
Sets the output head pointer.
Sets the output counter.
Executes user frame transmission.
Sets normal completion flag.
Sets abnormal completion flag.
Normal end
Abnormal end
D0 Send data count
(0004H)
D1
(3412H)
D2
Send data
(AB56H)
D5 Transmission frame No. (03F2H)
Send data count
Send data
(0004H)
(3412H)
(AB56H)
Transmission frame No. (03F2H)
D6
(03F3H)
(03F3H)
D7
(8001H)
(8001H)
D8
(8000H)
(8000H)
D9
(041BH)
(041BH)
D10
(0000H)
D11 Interface No.
(0001H)
Interface No.
D12 Transmission result
(0000H)
Transmission result (other than 0000H)
D13 CR/LF output
(0000H)
CR/LF output
(0000H)
D14 Output head pointer
(0001H)
Output head pointer
(0001H)
D15 Output counter
(0005H)
Output counter
(0005H)
(0000H)
(0001H)
397
17.7
G(P).PUTE
This instruction registers a user frame.
Applicable device
Setting
data
Internal device
Bit
File register
Word
Link direct device
J\
Bit
Intelligent function
module device
U\G
Word
Index register Zn
(S1)



(S2)



(D)



[Instruction
code]
Constant
Others
[Executing
condition]
Command
G.PUTE
G.PUTE
Un
(S1)
(S2)
(D)
GP.PUTE
Un
(S1)
(S2)
(D)
Command
GP.PUTE
17.7.1
Setting data
Setting data
Un
Description
Start I/O signal of the module
(00 to FE: The 2 upper digits of an input/output signal expressed in 3-digit.)
(S1)
Head number of the devices that store control data
(S2)
Head number of the devices that store registered data
(D)
Head bit device number of the local station that turns ON for one scan upon instruction
completion.
(D)+1 also turns on if the execution completes abnormally.
Set by
Data type
User
BIN-16 bit
User, System
System
Device name
Bit
The file registers of each of the local device and the program cannot be used as the setting data.
17.7.2
Control data
Device
Item
Setting data
Register/delete designation
Designate whether to register or delete the user frame having
the number designated by (S1)
Register: 1
Delete: 3
(S1)+1
Register/delete result
The registration/deletion result by the PUTE instruction is
stored.
0: Normal
Other than 0: Error code
(S1)+2
Frame No.
Designate the user frame No.
Registered bytes count
1 to 80: Number of bytes of the user frame to be registered.
• Designate 1 to 80 as dummy when deleting.
(S1)+0
(S1)+3
398
Setting range
Set by
1, 3
User

System
1000 to 1199
User
1 to 80
User
CHAPTER 17 DEDICATED INSTRUCTIONS
17
Remark
● For information about errors caused by incorrect data designated by the user, see the description in "Errors".
● The "Set by" column indicates the following:
• User: Data set by the user before executing the dedicated instruction.
• System: The programmable controller CPU stores execution results of the dedicated instruction.
17.7.3
Functions
(1) This instruction registers or deletes the user frame for the Q series C24 as
designated by Un.
(2) When registering a user frame
(a) When registering a user frame, set 1 to the device for (S1)+0.
Data in the device designated by (S2) and after will be registered according to the control data.
(b) The registered data should be stored in the device designated by (S2) and after as
described below.
Thus, at least (registered data number)/2 devices will be necessary to store the registered data and they
should be assigned beginning with the device designated by (S2).
For example, when registering 6 bytes of data, 3 devices beginning with the device designated by (S2) will be
used.
17.7 G(P).PUTE
QCPU
Q series C24
b8 b7
User frame
(S2)+0
b15 to
B
+1
D
C
B
+2
F
E
C
to
A
b0
Register
A
D
Registered byte length
E
F
(3) When deleting a user frame
(a) When deleting a user frame, set 3 to the device for (S1)+0.
The user frames of the frame numbers designated by (S1)+2 will be deleted.
(b) The registered byte number designated by (S1)+3 and registered data storage
device designated by (S2) are not used by the PUTE instruction, but they are
necessary for formatting it.
Designate 1 to 80 for (S1)+3 and a dummy device for (S2).
399
(4) Simultaneous execution of dedicated instructions
The following table lists the handling for when executing another instruction during execution of the PUTE
instruction or executing the PUTE instruction during execution of another instruction in the same channel.
Instruction
Availability of
simultaneous
execution
Handling of simultaneous execution


ONDEMAND
OUTPUT
PRR
INPUT
BIDOUT
BIDIN
CSET
PUTE

• The next instruction will be ignored until the active instruction has been completed.
GETE

• Dedicated instructions simultaneous execution error (7FF0H) occurs in the dedicated instruction attempted
later.
BUFRCVS
SPBUSY

UINI

CPRTCL


• Dedicated instructions simultaneous execution error (7FF0H) occurs in the dedicated instruction attempted
later.

: Available, : Not available
(5) Whether the PUTE instruction was completed normally or abnormally can be
checked with the completion device (D) or status display device at completion
(D+1).
(a) Completion device
Turns on at the END processing of the scan where the PUTE instruction is completed, and turns off at the next
END processing.
(b) Status display device at completion
Turns on and off depending on the completion status of the PUTE instruction.
• Normal completion: Stays off and does not change.
• Abnormal completion: Turns on at the END processing of the scan where the PUTE instruction is
completed, and turns off at the next END processing.
[Operation when the PUTE instruction is being executed]
END
processing
END
processing
END
processing
END
processing
Sequence program
PUTE instruction execution
Completion of reading user frames
by the PUTE instruction
PUTE instruction
ON
Registration/
deletion request
OFF
Completion device
OFF
ON
ON
Status display device OFF
at completion
400
Abnormal
completion
Normal completion
One scan
CHAPTER 17 DEDICATED INSTRUCTIONS
17.7.4
Errors
17
When the dedicated instruction is completed with an error, the status display device at completion ((D)+1), turns on
and the error code is stored in the control data registration/deletion result ((S1)+1).
See the following manuals regarding the error code, and check the errors and take corrective actions.
<Error codes>
4FFFH or less: User's manual (hardware design, maintenance and inspection) for the CPU module used
7000H or higher: User's Manual (Basic)
17.7.5
Program example
The following shows an example of a sequence program when registering user frames.
Data set for the program example are as follows:
Setting item
User frame No.
Registration data (10 bytes)
Setting data
3E8H
Binary
46H,39H,30H,30H,30H,30H,46H,46H,30H,30H
ASCII
F90000FF00
When the input/output signals of the Q series C24 are X/Y80 to X/Y9F
Registration request
Sets the registration request
Sets the frame number to be registered
Sets the registration data for the frame
to be registered in D4 to D8
Sets the flash ROM write allow
Executes user frame registration
Normal completion
Abnormal completion
401
17.7 G(P).PUTE
Sets the number of registration data
bytes
17.8
ZP.UINI
This instruction can change the mode, transmission specifications and station number of the Q series C24.
It is applicable to the QJ71C24N (-R2/R4), and LJ71C24 (-R2).
Applicable device
Setting
data
Internal device
Bit
File register
Word
Link direct device
J\
Bit
Word
Intelligent function
module device
U\G
Index register Zn
(S)



(D)



Constant
Others
[Executing
condition]
[Instruction
code]
Command
ZP.UINI
ZP.UINI
"Un"
(S)
(D)
*1
*1
17.8.1
If the host station is a Basic model QCPU (function version B or later), Universal model QCPU, or LCPU, " " (double
quotation) of the first argument can be omitted.
Setting data
Setting data
Description
Start I/O signal of the module
(00 to FE: The 2 upper digits of an input/output signal expressed in 3-digit.)
"Un"/Un
(S)
Head number of the devices that store control data
(D)
Head bit device number of the local station that turns ON for one scan upon instruction
completion.
(D)+1 also turns on if the execution completes abnormally.
Set by
Data type
User
String/BIN-16
bit
User, System
Device name
System
Bit
The file registers of each of the local device and the program cannot be used as the setting data.
17.8.2
Control data
Device
Setting range
Set by
(S)+0
For system
Always specify this to 0.
0
User
(S)+1
Execution result
The execution result of the UINI instruction is stored.
0: Normal
Other than 0: Error code

System
(S)+2
Execution type
Specify the execution type.
0: Switch the settings by those indicated in (S)+3 and later.
1: Return the settings to the GX Developer switch settings.
(S)+3
CH1 transmission
specifications setting
Set the CH1 side transmission specifications.
Page 403, Section 17.8.2
(1)
(S)+4
CH1 communication
protocol setting
Set the CH1 side communication protocol.
Page 404, Section 17.8.2
(2)
(S)+5
CH2 transmission
specifications setting
Set the CH2 side transmission specifications.
Page 403, Section 17.8.2
(1)
(S)+6
CH2 communication
protocol setting
Set the CH2 side communication protocol.
Page 404, Section 17.8.2
(2)
(S)+7
Station No. setting
Set the host station No.
0 to 31
(S)+8
to
(S)+12
For system
Always specify this to 0.
0
402
Item
Setting data
0, 1
User
CHAPTER 17 DEDICATED INSTRUCTIONS
(1) (S)+3 (CH1 transmission specifications setting) and (S)+5 (CH2 transmission
specifications setting)
b15
to
b8 b7 b6 b5 b4 b3 b2 b1
00H to 0FH
b0
0
CH1 side*1
CH2 side*1
00H to 0FH
Description
Bit
b0
Communication
speed (Unit: bps)
ON(1)
Independent
Remarks
Be sure to set the CH1 side
to OFF(0).
Link
Data bit
7
8
b2
Parity bit
NO
Yes
Vertical parity
b3
Even/odd parity
Odd
Even
Valid only when parity bit is
set to Yes.
Parity bit is not included.
b4
Stop bit
1
2
b5
Sum check code
NO
Yes
b6
Write during RUN
Prohibited
Allowed
b7
Setting modifications
Prohibited
Allowed
Bit
Description
Set value
Communication
speed
Remarks
00H to 0FH
Refer to *2
All items in the table should be set to OFF for the interfaces which "GX Developer connection" is set in the
communication protocol setting. The Q series C24 operates with the values set in GX Developer.
Transmission setting
GX Developer side setting
Operation setting
Independent
Data bit
8
Parity bit
Yes
Even/odd parity
Odd
Stop bit
1
Sum check code
Yes
Write during RUN
Allowed
Setting modifications
Allowed/Prohibited
17.8 ZP.UINI
*2
Operation setting
OFF(0)
b1
b8
to
b15
*1
17
The setting value of the communication speed
Bit position
b15 to b8
Communication
speed
(Unit: bps)
Bit position
b15 to b8
50
0FH
14400
06H
300
00H
19200
07H
600
01H
28800
08H
1200
02H
38400
09H
2400
03H
57600
0AH
4800
04H
115200
0BH
9600
05H
230400
0CH
Remarks
Slow down the communication speed when
data cannot be communicated normally due
to overrun error, framing error, etc. in
communication with external devices.
• Transmission speed of 230400 bps is available for only CH1.
• When connecting external devices to both of two interfaces, the total of the communication speed should be
230400 bps of less. When connecting an external device to either of two interfaces, the maximum of 115200 bps
is available for the interface (a maximum of 230400 bps if using CH1 side)). In this case, set 300 bps for the other
interface to which no external device is connected.
• 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.
403
(2) (S)+4 (CH1 communication protocol setting) and (S)+6 (CH2 communication
protocol setting)
Setting No.
Description
0H
GX Developer connection
(For connection to MELSOFT products)
Remarks
1H
Format 1
2H
Format 2
MC protocol
3H
4H
Format 3
GX Developer communication rate and transmission specifications are automatically set.
For communication with ASCII code in the specified form of an A compatible 1C frame or
QnA compatible 2C/3C/4C frame
Format 4
5H
Format 5
6H
Nonprocedural protocol
7H
Bidirectional protocol
8H
For synchronous setting
9H
Pre-defined protocol
For communication with binary code in a QnA compatible 4C frame
For communication using non procedure protocol
For communication using bidirectional protocol
Set to the CH1 side when CH1 and CH2 interfaces are used in linked operation (operated
with the communication protocol of the CH2 side).
For communication using pre-defined protocol
For details of the CH transmission specifications setting, CH communication protocol setting and station No. setting,
refer to the User's Manual (Basic).
Remark
● For information about errors caused by incorrect data designated by the user, see Page 406, Section 17.8.4.
● The "Set by" column indicates the following:
• User: Data set by the user before executing the dedicated instruction.
• System: The programmable controller CPU stores execution results of the dedicated instruction.
404
CHAPTER 17 DEDICATED INSTRUCTIONS
17.8.3
Functions
17
(1) This instruction changes the transmission specifications, communication
protocol and host station No. of each channel of the Q series C24 specified by
Un.
(2) Execution of the UINI instruction changes the following buffer memory
settings to enable communication with the new settings.
Address Dec. (Hex.)
CH1
Application
CH2
When module is
started up
When UINI instruction
is executed
512 (200H)
Station No. (switch setting)
GX Developer set values
591 (24FH)
Station No. (instruction setting)
Set value changed by
UINI instruction
608 (260H)
Communication protocol status (switch
setting)
593 (251H)
609 (261H)
Transmission setting status (switch
setting)
594 (252H)
610 (262H)
Communication protocol status (current)
595 (253H)
611 (263H)
Transmission status (current)
592 (250H)
When mode is
switched by mode
switching request
signal (Y2/Y9) (
Page 345, CHAPTER
15)
GX Developer set values
GX Developer set values
GX Developer set values
Set value changed by
UINI instruction
Set values changed by
mode switching
● Station No. setting change
● Switching to synchronous operation or switching from synchronous operation to the other mode (independent operation)
(3) Whether the UINI instruction was completed normally or abnormally can be
checked with the completion device (D) or status display device at completion
((D)+1).
(a) Completion device
Turns on at the END processing of the scan where the UINI instruction is completed, and turns off at the next
END processing.
(b) Status display device at completion
Turns on and off depending on the completion status of the UINI instruction.
• Normal completion: Stays off and does not change.
• Abnormal completion: Turns on at the END processing of the scan where the UINI instruction is
completed, and turns off at the next END processing.
405
17.8 ZP.UINI
The UINI instruction can change the following settings that cannot be changed by mode switching that uses the mode
switching request signal (Y2/Y9).
[Operation when the UINI instruction is executed]
Sequence
program
END
processing
END
processing
END
processing
END
processing
UINI instruction execution
UINI instruction
ON
Completion
device
OFF
Error
ON completion
Status indication
OFF
device at completion
Normal completion
One scan
ON
Mode switching
signal (X6/XD)
OFF
Q series C24
Setting processing
Communication disabled
17.8.4
Errors
When the dedicated instruction is completed with an error, the status display device at completion ((D)+1), turns on
and the error code is stored in the control data transmission result ((S1)+1).
See the following manuals regarding the error code, and check the errors and take corrective actions.
<Error codes>
4FFFH or less: User's manual (hardware design, maintenance and inspection) for the CPU module used
7000H or higher: User's Manual (Basic)
406
CHAPTER 17 DEDICATED INSTRUCTIONS
17.8.5
Program example
17
The settings of the Q series C24 installed in the position of I/O No. X/Y00 to X/Y1F are changed as indicated below
when X20 is turned on.
Bit
Device
(S)+3
Specified
value
b0
OFF
Operation setting
b1
ON
Data bit
b2
ON
b3
OFF
b4
OFF
b5
ON
b6
CH1
transmission
specifications
setting
Set value
Independent
8 bits
Parity bit
Yes
Even/odd parity
Odd
Stop bit
1 bit
Sum check code
Yes
ON
Write during RUN
Allowed
b7
ON
Setting modifications
b8 to b15

Communication rate setting

(S)+4
(S)+5
Description
Position
CH1 communication protocol setting
b0
ON
Operation setting
b1
ON
Data bit
Allowed
19200bps
Synchronous setting
8 bits
ON
b3
OFF
b4
OFF
b5
ON
Sum check code
Yes
b6
ON
Write during RUN
Allowed
b7
ON
Setting modifications
Allowed

b8 to b15
Parity bit
Yes
Even/odd parity
Odd
Stop bit
1 bit
Communication rate setting

CH2 communication protocol setting
(S)+7

Station No. setting
07E7H
19200bps
MC protocol format 5
0005H
Station 1
0001H
407
17.8 ZP.UINI
(S)+6
0008H
Synchronous
b2
CH2
transmission
specifications
setting
07E6H
Clears the control data
UINI
CH1 mode CH2 mode CH1 mode CH2 mode
instruction switching
switching switching switching
command request
request
Always sets 0
Clears the execution result to 0
Sets the execution type to 0
Sets the CH1 transmission specifications
Sets the CH1 communication protocol
Sets the CH2 transmission specifications
Sets the CH2 communication protocol
Sets the host station No.
Executes the UINI instruction
Turns ON the interlock signal for
communication stop*1
Processing for normal completion
Processing for error completion
Turns OFF the interlock signal for
communication stop*1
Data communication processing
Interlock signal for
communication stop
(*1)
*1
408
Perform programming so that data communication processing is not executed while the interlock signal for
communication stop (M100) is ON.
CHAPTER 17 DEDICATED INSTRUCTIONS
17.8.6
Precautions
17
(1) Execute the UINI instruction after stopping all data communications with the
other device.
Otherwise, the following will occur.
(a) When the UINI instruction is executed during receive processing
The receive processing is stopped and the reception data accumulated until then are all discarded.
(b) When the UINI instruction is executed during transmission processing
The transmission processing is stopped upon acceptance of the UINI instruction.
(2) When a modem is connected, execute the UINI instruction after cutting off the
line with the other device. (The line is cut off when the UINI instruction is
executed.)
(3) If the communication protocol and/or transmission specifications are changed
with the UINI instruction, also change those of the other device according to
the new settings.
Also, if the station No. setting (host station No.) is changed, correct the station No. in the other device side
request message to the new station No.
(4) Simultaneous execution of dedicated instructions
Instruction
Availability of
simultaneous
execution
Handling of simultaneous execution
ONDEMAND
OUTPUT
PRR
INPUT
BIDOUT
BIDIN

• Dedicated instructions simultaneous execution error (7FF0H) occurs in the dedicated instruction attempted
later.
CSET
PUTE
GETE
CPRTCL
BUFRCVS
SPBUSY
UINI



• The next instruction will be ignored until the active instruction has been completed.
: Available, : Not available
(5) Before executing the UINI instruction, set the transmission setting
modification to "Enabled" in the GX Developer switch setting.
When the switch setting has not yet been made, the transmission setting modification is processed as "Enabled".
409
17.8 ZP.UINI
The following table shows the handling for when executing another instruction during execution of the UINI
instruction or executing the UINI instruction during execution of another instruction in the same channel.
(6) Do not use the UINI instruction and mode switching request signal (Y2/Y9)
together to execute mode switching.
(7) To use the current communication protocol, transmission specifications and
host station No. obtain the values from the following status storage areas
(current) of the buffer memory and set them to the control data.
Address Dec. (Hex.)
CH1
591 (24FH)
410
Application
CH2
Station No. (instruction setting)
594 (252H)
610 (262H)
Communication protocol status (current)
595 (253H)
611 (263H)
Transmission status (current)
APPENDIX
APPENDIX
Appendix 1
A
Specification Comparison between the Q
Series C24 and L series C24
The functions of the L series C24 correspond to those of the Q series C24, whose first five digits of the serial number
is 11062 and the function version is B or later.
The following table lists the specification comparison between the Q series C24 and L series C24.
Item
Notification function
Difference
Q series C24 (function version B)
Supported
L series C24
Not supported
When applying the program used in the system of the Q series to the L series, refer to precautions for applying a program in
the following manual.
 MELSEC-L CPU Module User's Manual (Function Explanation, Program Fundamentals)
Appendix 1 Specification Comparison between the Q Series C24 and L series C24
411
Memo
412
INDEX
Full-duplex communications. . . . . . . . . . . . . . . . . 212
A
Action for buffer full . . . . . . . . . . . . . . . . . . . . . . . 363
Additional codes . . . . . . . . . . . . . . . . . . . . . . . . . 296
ASCII-BIN conversion . . . . . . . . . . . . . . . . . . . . . 319
Auto modem initialization designation . . . . . . . . . . 115
I
G
GETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
GX Developer connection . . . . . . . . . . . . . . . 79,123
GX Developer connection designation . . . . . . . . . 111
4
B
Block monitoring device . . . . . . . . . . . . . . . . . . . . . 59
Buffer memory (for modem) . . . . . . . . . . . . . . . . . 105
Buffer memory (for on-demand data transmission)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Buffer memory (for user frame) . . . . . . . . . . . . . . . 238
BUFRCVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
H
I
I/O signals for handshake (for mode switching) . . . 350
I/O signals with the programmable controller CPU
(modem function) . . . . . . . . . . . . . . . . . . . . . . . . 102
Improper access . . . . . . . . . . . . . . . . . . . . . . 86,124
Information to be transmitted . . . . . . . . . . . . . . . . . 47
Initialization commands (for modem). . . . . . . . . . . 134
Initialization of modem/TA (terminal adapter) . . . . . 144
Initialization/connection timeout time designation . . 132
Interlock (for m:n communication) . . . . . . . . . . . . . 336
Interrupt program example. . . . . . . . . . . . . . . . . . 188
C
Callback denial notification accumulated count
designation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Callback function . . . . . . . . . . . . . . . . . . . . . . . . . 92
Callback function designation . . . . . . . . . . . . . . . . 117
Circuit disconnect wait time (programmable controller
CPU watch use) . . . . . . . . . . . . . . . . . . . . . . . . . 115
Communication data monitoring . . . . . . . . . . . . . . 358
Condition agreement transmission . . . . . . . . . . . . . 41
Constant cycle transmission . . . . . . . . . . . . . . . . . . 41
CPU abnormal monitoring . . . . . . . . . . . . . . . . . . . 61
CR/LF output designation area . . . . . . . . . . . . . . . 291
CSET instruction (initial settings) . . . . . . . . . . . . . 384
CSET instruction (programmable controller CPU
monitoring register/cancel) . . . . . . . . . . . . . . . . . . 375
Cycle time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Cycle time units . . . . . . . . . . . . . . . . . . . . . . . . . . 61
M
m:n................................
Message wait time . . . . . . . . . . . . . . . . . . . . . .
Mode switching . . . . . . . . . . . . . . . . . . . . . . . .
Modem connection channel designation . . . . . . .
Modem function list . . . . . . . . . . . . . . . . . . . . . .
Modem initialization time DR signal valid/invalid
designation . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modern function system setting . . . . . . . . . . . . .
Monitor buffer head address specification area . .
Monitor buffer size specification area . . . . . . . . .
Monitoring conditions . . . . . . . . . . . . . . . . . . . .
Monitoring target device . . . . . . . . . . . . . . . . . .
Monitoring timing . . . . . . . . . . . . . . . . . . . . . . .
D
Data communications using user frames . . . . . . . . 252
Data No. for Callback designation . . . . . . . . . . . . . 118
Data number for connection designation . . . . . . . . 111
Data number for initialization designation . . . . . . . . 111
Data registration for modem connection . . . . . . . . 139
Data registration for modem initialization . . . . . . . . 134
DC code control . . . . . . . . . . . . . . . . . . . . . . . . . 206
DC1/DC3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
DC2/DC4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Dedicated instruction list . . . . . . . . . . . . . . . . . . . 369
Default registration frame . . . . . . . . . . . . . . . . . . . 230
Deleting user frames . . . . . . . . . . . . . . . . . . . . . . 242
DTR/DSR (ER/DR) signal control . . . . . . . . . . . . . 204
E
Exclusive format-1 received data count designation
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
4
Half-duplex communications . . . . . . . . . . . . . . . . 212
. 334
. 202
. 345
. 132
. . 74
. 132
. 132
. 363
. 363
. . 42
. . 38
. . 39
N
No-communication interval time designation . . . .
No-reception Monitoring Time (timer 0) . . . . . . . .
No-reception monitoring time format specification
in non procedure protocol . . . . . . . . . . . . . . . . .
Notification function . . . . . . . . . . . . . . . . . . . . .
Number of connection retries designation . . . . . .
Number of registered bit blocks . . . . . . . . . . . . .
Number of registered word blocks . . . . . . . . . . .
. 111
. 195
. 197
. . 56
. 110
. . 61
. . 61
O
On-demand buffer memory head address designation
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
F
Format-0 and Format-1 (reception method) . . . . . . 261
On-demand data communication (user frame) . . . . 243
On-demand data length designation . . . . . . . . . . . 250
413
7
8
On-demand data list . . . . . . . . . . . . . . . . . . . . . . 244
On-demand function control procedure (ASCII code)
Timings of transmission of monitoring results . . . . . 41
Transmission control . . . . . . . . . . . . . . . . . . . . . 203
Transmission control end free area specification . . 205
Transmission control start free area specification
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
On-demand function control procedure (binary code)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
. 47
292
200
288
293
. 82
296
237
On-demand user frame designation . . . . . . . . . . . 250
Output count designation area . . . . . . . . . . . . . . . 292
Output head pointer designation area . . . . . . . . . . 291
Transmission data arrangement . . . . . . . . . . . . .
Transmission frame No. designation area. . . . . . .
Transmission Monitoring Time (timer 2) . . . . . . . .
Transmission procedure (user frame). . . . . . . . . .
Transmission program example (user frame) . . . .
Transmission specifications . . . . . . . . . . . . . . . .
Transparent codes . . . . . . . . . . . . . . . . . . . . . . .
Type of user frames . . . . . . . . . . . . . . . . . . . . . .
P
PLC CPU abnormal monitoring designation . . . . . . 59
Programmable controller CPU monitoring function . . 34
PRR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
PUTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
U
UINI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User frame . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User frame receive format designation . . . . . . . . .
User frame registration status storage area . . . . .
User frame setting for reception . . . . . . . . . . . . .
User frame storage area . . . . . . . . . . . . . . . . . . .
R
Reading user frames . . . . . . . . . . . . . . . . . . . . . 241
Receive interrupt-issued designation . . . . . . . . . . 185
Receive procedure . . . . . . . . . . . . . . . . . . . . . . . 266
Receive program example (user frame) . . . . . . . . 273
Receiving data with an interrupt program . . . . . . . 184
Reception control method (interrupt program) . . . . 187
Reception data list (user frame) . . . . . . . . . . . . . . 254
Reception method (Format-0 and Format-1) . . . . . 261
Register/read/delete of the data for connection
(for modem) . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Registering user frames . . . . . . . . . . . . . . . . . . . 240
Registration data byte count designation area . . . . 238
Remote password check . . . . . . . . . . . . . . 73,86,121
Remote password mismatch notification
accumulated count designation . . . . . . . . . . . . . . 116
Remote password mismatch notification count
designation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Response Monitoring Time (timer 1). . . . . . . . . . . 198
Retransmission time transmission method designation
....................................
.....
.....
.....
.....
RS/CS control (for modem function) . . . . . .
RS/CS control yes/no designation . . . . . . .
RS-232 CD terminal check designation . . .
RS-232 communication system designation
217
112
111
217
217
S
Sample program (mode switching) . . . . . . . . . . . . 355
Sample programs (for modem function) . . . . . . . . 164
Send data list (on-demand data) . . . . . . . . . . . . . 245
Send data list (user frame) . . . . . . . . . . . . . . . . . 289
Setting for transmission user frames . . . . . . . . . . 289
Setting items for programmable controller CPU
monitoring function . . . . . . . . . . . . . . . . . . . . . . . . 58
Simultaneous transmission priority/non-priority
designation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Start-up of the modem function . . . . . . . . . . . . . . 126
Stop by timer 0 error . . . . . . . . . . . . . . . . . . . . . . 363
Switching the mode from the programmable controller
CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
T
Timing for programmable controller CPU monitoring
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
414
402
220
270
239
267
239
V
Variable data (User frame) . . . . . . . . . . . . . . . . . 222
W
Word/bytes units setting . . . . . . . . . . . . . . . . . . . 192
REVISIONS
*The manual number is given on the bottom left of the back cover.
Print date
Dec., 1999
*Manual number
Revision
SH (NA)-080007-A
First edition
SH (NA)-080007-B
Add the contents of the function version B.
Put Windows base software products together from Mitsubishi Programmable Controller MELSEC
series to Mitsubishi integrated FA software MELSOFT series. Standardize the name from software
package (GPP function) to product name (GX Developer).
[Correction]
Entire manual (change MELSECNET/10H to MELSECNET/H), Contents, About the Manuals, About
the Generic Terms and Abbreviations, Section 1.1, 1.2 POINT, Section 2.1, 2.2.1, 2.2.3, 2.2.5, 2.2.6,
2.3.1, 2.3.2, Section 3.1.1, 3.2.3, 3.2.4, 3.3.1, 3.3.4, 3.3.5, 3.3.6, 3.4 (entire), Section 4.3, Chapter 9
(entire), Chapter 11 (entire), Section 12.2, 12.3, 12.4 (entire), 12.6 (entire), Section 13.3, 13.4, 13.6
(entire), Section 15.3, Section 16.2 (entire) to 16.7
[Addition]
Section 2.4 (9), Section 3.2.3 POINT
SH (NA)-080007-C
Standardize the name from utility package (QSCU) to product name (GX Configurator-SC).
[Correction]
About the Manuals, The Manual's Use and Structure, About the Generic Terms and Abbreviations,
Program example (Section 9.4.1, 9.4.2, 9.4.3, Section 11.5 (1) (2), Section 16.5, 16.6, 16.7), Section
1.1 (2) (diagram), 1.2, Chapter 3 (entire), Section 4.1 (2), Section 9.1.1 (4) 5), Section 11.3.2 (3),
11.3.3 (3), Section 13.6.1 (diagram)
[Addition]
Section 3.3.4, 3.3.6 (4), 3.4.5 (4)
Jan., 2003
SH(NA)-080007-D
[Additional model]
QJ71C24N, QJ71C24N-R2, QJ71C24N-R4
[Correction]
SAFETY PRECAUTIONS, About the Manuals, The Manual's Use and Structure, About the Generic
Terms and Abbreviations, Section 1.2, Section 2.2.4 (2) (c), Section 3.3.1, 3.3.5, 3.3.6, 3.4.2, 3.4.3,
3.4.7, 3.4.8 (3), 3.5, Section 6.1, Section 7.1, 7.2, Section 9.1.1 (4), Section 10.4.1 (2) 1), Section
11.2.4 (2), 11.4.3 (a), 11.5, Section 15.1, 15.2, 15.3, 15.4.2, Section 17.1, 17.3, 17.4
[Addition]
Section 4.4.2 (6), Chapter 16 (entire)
Dec., 2003
SH(NA)-080007-E
[Correction]
About the Generic Terms and Abbreviations, Section 3.4.6 (4), Section 6.1, 6.3 (1) (b), Section 9.1.1
(4), Section 11.2.4 (2)
Jun., 2004
SH(NA)-080007-F
[Correction]
About the Generic Terms and Abbreviations, Section 3.3.4 (4), 3.4.3 (6), 3.4.4 (5), Section 8.2 (2),
Section 11.3.1, Section 16.2 (1)
Sep., 2004
SH(NA)-080007-G
[Correction]
Section 1.2, Section 6.1, Section 9.1.1
[Addition]
Section 17.8
Feb., 2005
SH(NA)-080007-H
[Correction]
Section 3.4.2, 3.4.4, Chapter 17 (Simultaneous execution of dedicated instructions)
Mar., 2006
SH(NA)-080007-I
[Correction]
SAFETY PRECAUTIONS, Section 6.1, Section 17.1
Jun., 2007
SH(NA)-080007-J
[Change of a term]
"PLC" was changed to "programmable controller".
[Correction]
About The Generic Terms and Abbreviations, Section 2.3.1(4), Section 3.4.5, Section 11.4.3, 11.5,
Section 12.3, Section 13.4, Section 15.3, Section 17.2, 17.3, 17.4, 17.5, 17.6, 17.7, 17.8
Aug., 2008
SH(NA)-080007-K
[Correction]
SAFETY PRECAUTIONS, About The Generic Terms and Abbreviations, Section 3.1.1, 3.3.3, 3.3.6,
3.3.7, Section 7.1, Section 9.1.2, Section 17.2 to17.4, 17.8
Jun., 2009
SH(NA)-080007-L
[Partial correction]
About The Generic Terms and Abbreviations, Sections 1.1, 1.2, 3.3.1, 3.3.5, 9.1.2, 9.4.1,Chapter 15,
Sections 15.1.2, 15.3, 17.2, 17.3, 17.4, 17.5, 17.6, 17.7, 17.8
Oct., 2000
Jun., 2001
415
Print date
Jan., 2010
Aug., 2012
Dec., 2014
*Manual number
Revision
SH(NA)-080007-M
[Additional model]
LJ71C24, LJ71C24-R2
[Partial correction]
SAFETY PRECAUTIONS, INTRODUCTION, Related Manuals, The Manual's Use and Structure,
About The Generic Terms and Abbreviations, Definitions and Descriptions of Terminology, Section
1.2, 2.3.1, 2.3.2, 3.1.1, 3.1.3, 3.2.4, 3.3.1, 3.3.5, 3.3.6, 3.3.7, 8.3, 9.1.2, 9.4.1, 15.3, 15.4.1, 15.5.1,
16.1.1, 17.2, 17.3, 17.4, 17.7, 17.8
[Partial addition]
Product application, APPENDIXES
SH(NA)-080007-N
[Partial correction]
CONTENTS, Generic Terms and Abbreviations, Section 1.1, 1.2, 3.2.3, 3.3.1, 3.3.2, 3.3.3, 3.3.4,
3.3.6, 3.4.2, 3.4.7, 3.4.8, 3.5.2, 4.4.2, 6.3, Chapter 7, Sections 7.1, 7.2, 7.3, 8.2, 8.4, 8.5, 9.4, 11.2.2,
11.2.3, 11.3.1, 11.3.2, 11.3.3, 11.4.3, 12.4.1, 13.4.1, 14.3.1, 15.3, 16.1.2, 16.2, 16.3, 17.6, 17.7, 17.8,
WARRANTY
[Partial addition]
COMPLIANCE WITH EMC AND LOW VOLTAGE DIRECTIVES
SH(NA)-080007-O
[Partial correction]
SAFETY PRECAUTIONS, COMPLIANCE WITH EMC AND LOW VOLTAGE DIRECTIVES,
RELEVANT MANUALS, GENERIC TERMS AND ABBREVIATIONS, Section 2.2.5, 2.3.2, 3.3.7,
3.4.1, 3.4.6, 3.4.7, 3.4.8, 8.4, 9.1, 10.5, 11.1, 11.2.1, 11.3.1, 11.4.3, 12.4.1, Chapter 15, Section
16.1.2, 16.2, 17.6.5, 17.8.2
[Change of manual structure]
Subsections are added to Section 17.2 to 17.8.
Japanese manual version SH-080002-T
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.
 2014 MITSUBISHI ELECTRIC CORPORATION
416
WARRANTY
Please confirm the following product warranty details before using this product.
1. Gratis Warranty Term and Gratis Warranty Range
If any faults or defects (hereinafter "Failure") found to be the responsibility of Mitsubishi occurs during use of the product
within the gratis warranty term, the product shall be repaired at no cost via the sales representative or Mitsubishi Service
Company.
However, if repairs are required onsite at domestic or overseas location, expenses to send an engineer will be solely at
the customer's discretion. Mitsubishi shall not be held responsible for any re-commissioning, maintenance, or testing
on-site that involves replacement of the failed module.
[Gratis Warranty Term]
The gratis warranty term of the product shall be for one year after the date of purchase or delivery to a designated place.
Note that after manufacture and shipment from Mitsubishi, the maximum distribution period shall be six (6) months, and
the longest gratis warranty term after manufacturing shall be eighteen (18) months. The gratis warranty term of repair
parts shall not exceed the gratis warranty term before repairs.
[Gratis Warranty Range]
(1) The range shall be limited to normal use within the usage state, usage methods and usage environment, etc., which
follow the conditions and precautions, etc., given in the instruction manual, user's manual and caution labels on the
product.
(2) Even within the gratis warranty term, repairs shall be charged for in the following cases.
1. Failure occurring from inappropriate storage or handling, carelessness or negligence by the user. Failure caused
by the user's hardware or software design.
2. Failure caused by unapproved modifications, etc., to the product by the user.
3. When the Mitsubishi product is assembled into a user's device, Failure that could have been avoided if functions
or structures, judged as necessary in the legal safety measures the user's device is subject to or as necessary by
industry standards, had been provided.
4. Failure that could have been avoided if consumable parts (battery, backlight, fuse, etc.) designated in the
instruction manual had been correctly serviced or replaced.
5. Failure caused by external irresistible forces such as fires or abnormal voltages, and Failure caused by force
majeure such as earthquakes, lightning, wind and water damage.
6. Failure caused by reasons unpredictable by scientific technology standards at time of shipment from Mitsubishi.
7. Any other failure found not to be the responsibility of Mitsubishi or that admitted not to be so by the user.
2. Onerous repair term after discontinuation of production
(1) Mitsubishi shall accept onerous product repairs for seven (7) years after production of the product is discontinued.
Discontinuation of production shall be notified with Mitsubishi Technical Bulletins, etc.
(2) Product supply (including repair parts) is not available after production is discontinued.
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.
4. Exclusion of loss in opportunity and secondary loss from warranty liability
Regardless of the gratis warranty term, Mitsubishi shall not be liable for compensation of damages caused by any cause
found not to be the responsibility of Mitsubishi, loss in opportunity, lost profits incurred to the user by Failures of
Mitsubishi products, special damages and secondary damages whether foreseeable or not, compensation for accidents,
and compensation for damages to products other than Mitsubishi products, replacement by the user, maintenance of
on-site equipment, start-up test run and other tasks.
5. Changes in product specifications
The specifications given in the catalogs, manuals or technical documents are subject to change without prior notice.
417
TRADEMARKS
Microsoft, Windows, Windows Vista, Windows NT, Windows XP, Windows Server, Visio, Excel, PowerPoint, Visual Basic,
Visual C++, and Access are either registered trademarks or trademarks of Microsoft Corporation in the United States,
Japan, and other countries.
Intel, Pentium, and Celeron are either registered trademarks or trademarks of Intel Corporation in the United States and
other countries.
Ethernet is a trademark of Xerox Corp.
The SD and SDHC logos are either registered trademarks or trademarks of SD-3C, LLC.
All other company names and product names used in this manual are either trademarks or registered trademarks of their
respective companies.
418
SH(NA)-080007-O
SH(NA)-080007-O(1412)MEE
MODEL:
QJ71C24-U-OU-E
MODEL CODE: 13JL87
HEAD OFFICE : TOKYO BUILDING, 2-7-3 MARUNOUCHI, CHIYODA-KU, TOKYO 100-8310, JAPAN
NAGOYA WORKS : 1-14 , YADA-MINAMI 5-CHOME , HIGASHI-KU, NAGOYA , JAPAN
When exported from Japan, this manual does not require application to the
Ministry of Economy, Trade and Industry for service transaction permission.
Specifications subject to change without notice.