Mitsubishi Electric MELSEC iQ-R Series User manual

MELSEC iQ-R Serial Communication Module
User's Manual (Application)
-RJ71C24
-RJ71C24-R2
-RJ71C24-R4

1
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 for the programmable
controller system, refer to the user's manual for the module used and the MELSEC iQ-R Module Configuration Manual.
In this manual, the safety precautions are classified into two levels:" WARNING" and " CAUTION".
Under some circumstances, failure to observe the precautions given under " CAUTION" may lead to serious
consequences.
Observe the precautions of both levels because they are important for personal and system safety.
Make sure that the end users read this manual and then keep the manual in a safe place for future reference.
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.

2
[Design Precautions]
WARNING
●Configure safety circuits external to the programmable controller to ensure that the entire system
operates safely even when a fault occurs in the external power supply or the programmable controller.
Failure to do so may result in an accident due to an incorrect output or malfunction.
(1) Emergency stop circuits, protection circuits, and protective interlock circuits for conflicting
operations (such as forward/reserve rotations or upper/lower limit positioning) must be configured
external to the programmable controller.
(2) When the programmable controller detects an abnormal condition, it stops the operation and all
outputs are:
• Turned off if the overcurrent or overvoltage protection of the power supply module is activated.
• Held or turned off according to the parameter setting if the self-diagnostic function of the CPU
module detects an error such as a watchdog timer error.
(3) All outputs may be turned ON if an error occurs in a part, such as an I/O control part, where the
CPU module cannot detect any error. To ensure safety operation in such a case, provide a safety
mechanism or a fail-safe circuit external to the programmable controller. For a fail-safe circuit
example, refer to "General Safety Requirements" in the MELSEC iQ-R Module Configuration
Manual.
(4) Outputs may remain ON or OFF due to a failure of a component such as a relay and transistor in
an output circuit. Configure an external circuit for monitoring output signals that could cause a
serious accident.
●In an output circuit, when a load current exceeding the rated current or an overcurrent caused by a
load short-circuit flows for a long time, it may cause smoke and fire. To prevent this, configure an
external safety circuit, such as a fuse.
●Configure a circuit so that the programmable controller is turned on first and then the external power
supply. If the external power supply is turned on first, an accident may occur due to an incorrect output
or malfunction.
●For the operating status of each station after a communication failure, refer to manuals relevant to the
network. Incorrect output or malfunction due to a communication failure may result in an accident.
●When connecting an external device with a CPU module or intelligent function module to modify data
of a running programmable controller, configure an interlock circuit in the program to ensure that the
entire system will always operate safely. For other forms of control (such as program modification,
parameter change, forced output, or operating status change) of a running programmable controller,
read the relevant manuals carefully and ensure that the operation is safe before proceeding. Improper
operation may damage machines or cause accidents.
●Especially, when a remote programmable controller is controlled by an external device, immediate
action cannot be taken if a problem occurs in the programmable controller due to a communication
failure. To prevent this, configure an interlock circuit in the program, and determine corrective actions
to be taken between the external device and CPU module in case of a communication failure.

3
[Design Precautions]
[Design Precautions]
WARNING
●Do not write any data to the "system area" and "write-protect area" of the buffer memory in the
module. Also, do not use any "use prohibited" signals as an output signal from the CPU module to
each module. Doing so may cause malfunction of the programmable controller system. For the
"system area", "write-protect area", and the "use prohibited" signals, refer to the user's manual for the
module used.
●If a communication cable is disconnected, the network may be unstable, resulting in a communication
failure of multiple stations. Configure an interlock circuit in the program to ensure that the entire
system will always operate safely even if communications fail. Incorrect output or malfunction due to a
communication failure may result in an accident.
●To maintain the safety of the programmable controller system against unauthorized access from
external devices via the network, take appropriate measures. To maintain the safety against
unauthorized access via the Internet, take measures such as installing a firewall.
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.
●During control of an inductive load such as a lamp, heater, or solenoid valve, a large current
(approximately ten times greater than normal) may flow when the output is turned from OFF to ON.
Therefore, use a module that has a sufficient current rating.
●After the CPU module is powered ON or is reset, the time taken to enter the RUN status varies
depending on the system configuration, parameter settings, and/or program size. Design circuits so
that the entire system will always operate safely, regardless of the time.
●Do not power OFF the programmable controller or do not reset the CPU module while the settings are
being written. Doing so will make the data in the flash ROM and SD memory card undefined. The
values need to be set in the buffer memory and written to the flash ROM and SD memory card again.
Doing so may cause malfunction or failure of the module.
●When changing the operating status of the CPU module from external devices (such as remote RUN/
STOP functions), select "Do Not Open in Program" for "Open Method Setting" in the module
parameters. If "Open in Program" is selected, an execution of remote STOP causes the
communication line to close. Consequently, the CPU module cannot reopen the communication line,
and the external device cannot execute the remote RUN.

4
[Installation Precautions]
[Installation Precautions]
[Wiring Precautions]
WARNING
●Shut off the external power supply (all phases) used in the system before mounting or removing the
module. Failure to do so may result in electric shock or cause the module to fail or malfunction.
CAUTION
●Use the programmable controller in an environment that meets general specifications written in Safety
Guidelines included in the base unit. Failure to do so may result in electric shock, fire, malfunction, or
damage to or deterioration of the product.
●To mount a module, place the concave part(s) located at the bottom onto the guide(s) of the base unit,
and push in the module until the hook(s) located at the top snaps into place. Incorrect interconnection
may cause malfunction, failure, or drop of the module.
●To mount a module with no module fixing hook, place the concave part(s) located at the bottom onto
the guide(s) of the base unit, push in the module, and fix it with screw(s). 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.
●When using an extension cable, connect it to the extension cable connector of the base unit securely.
Check the connection for looseness. Poor contact may cause malfunction.
●When using an SD memory card, fully insert it into the memory card slot. Check that it is inserted
completely. Poor contact may cause malfunction.
●Securely insert an extended SRAM cassette into the cassette connector of a CPU module. After
insertion, close the cassette cover and check that the cassette is inserted completely. Poor contact
may cause malfunction.
●Do not directly touch any conductive parts and electronic components of the module, SD memory
card, extended SRAM cassette, or connector. Doing so may cause malfunction or failure of the
module.
WARNING
●Shut off the external power supply (all phases) used in the system before installation and wiring.
Failure to do so may result in electric shock or cause the module to fail or malfunction.
●After installation and wiring, attach the included terminal cover to the module before turning it on for
operation. Failure to do so may result in electric shock.

5
[Wiring Precautions]
CAUTION
●Individually ground the FG and LG terminals of the programmable controller with a ground resistance
of 100 ohms or less. Failure to do so may result in electric shock or malfunction.
●Use applicable solderless terminals and tighten them within the specified torque range. If any spade
solderless terminal is used, it may be disconnected when the terminal screw comes loose, resulting in
failure.
●Check the rated voltage and signal layout before wiring to the module, and connect the cables
correctly. Connecting a power supply with a different voltage rating or incorrect wiring may cause fire
or failure.
●Connectors for external devices must be crimped or pressed with the tool specified by the
manufacturer, or must be correctly soldered. Incomplete connections may cause short circuit, fire, or
malfunction.
●Securely connect the connector to the module. Poor contact may cause malfunction.
●Do not install the control lines or communication cables together with the main circuit lines or power
cables. Keep a distance of 100mm or more between them. Failure to do so may result in malfunction
due to noise.
●Place the cables in a duct or clamp them. If not, dangling cable may swing or inadvertently be pulled,
resulting in damage to the module or cables or malfunction due to poor contact. Do not clamp the
extension cables with the jacket stripped. Doing so may change the characteristics of the cables,
resulting in malfunction.
●Check the interface type and correctly connect the cable. Incorrect wiring (connecting the cable to an
incorrect interface) may cause failure of the module and external device.
●Tighten the terminal screws or connector screws within the specified torque range. Undertightening
can cause drop of the screw, short circuit, fire, or malfunction. Overtightening can damage the screw
and/or module, resulting in drop, short circuit, fire, or malfunction.
●When disconnecting the cable from the module, do not pull the cable by the cable part. For the cable
with connector, hold the connector part of the cable. For the cable connected to the terminal block,
loosen the terminal screw. Pulling the cable connected to the module may result in malfunction or
damage to the module or cable.
●Prevent foreign matter such as dust or wire chips from entering the module. Such foreign matter can
cause a fire, failure, or malfunction.
●A protective film is attached to the top of the module to prevent foreign matter, such as wire chips,
from entering the module during wiring. Do not remove the film during wiring. Remove it for heat
dissipation before system operation.

6
[Wiring Precautions]
[Startup and Maintenance Precautions]
CAUTION
●Programmable controllers must be installed in control panels. Connect the main power supply to the
power supply module in the control panel through a relay terminal block. Wiring and replacement of a
power supply module must be performed by qualified maintenance personnel with knowledge of
protection against electric shock. For wiring, refer to the MELSEC iQ-R Module Configuration Manual.
●For Ethernet cables to be used in the system, select the ones that meet the specifications in the user's
manual for the module used. If not, normal data transmission is not guaranteed.
WARNING
●Do not touch any terminal while power is on. Doing so will cause electric shock or malfunction.
●Correctly connect the battery connector. Do not charge, disassemble, heat, short-circuit, solder, or
throw the battery into the fire. Also, do not expose it to liquid or strong shock. Doing so will cause the
battery to produce heat, explode, ignite, or leak, resulting in injury or fire.
●Shut off the external power supply (all phases) used in the system before cleaning the module or
retightening the terminal screws, connector screws, or module fixing screws. Failure to do so may
result in electric shock.

7
[Startup and Maintenance Precautions]
CAUTION
●When connecting an external device with a CPU module or intelligent function module to modify data
of a running programmable controller, configure an interlock circuit in the program to ensure that the
entire system will always operate safely. For other forms of control (such as program modification,
parameter change, forced output, or operating status change) of a running programmable controller,
read the relevant manuals carefully and ensure that the operation is safe before proceeding. Improper
operation may damage machines or cause accidents.
●Especially, when a remote programmable controller is controlled by an external device, immediate
action cannot be taken if a problem occurs in the programmable controller due to a communication
failure. To prevent this, configure an interlock circuit in the program, and determine corrective actions
to be taken between the external device and CPU module in case of a communication failure.
●Do not disassemble or modify the modules. Doing so may cause failure, malfunction, injury, or a fire.
●Use any radio communication device such as a cellular phone or PHS (Personal Handy-phone
System) more than 25cm away in all directions from the programmable controller. Failure to do so
may cause malfunction.
●Shut off the external power supply (all phases) used in the system before mounting or removing the
module. Failure to do so may cause the module to fail or malfunction.
●Tighten the screws within the specified torque range. Undertightening can cause drop of the
component or wire, short circuit, or malfunction. Overtightening can damage the screw and/or module,
resulting in drop, short circuit, or malfunction.
●After the first use of the product, do not mount/remove the module to/from the base unit, and the
terminal block to/from the module, and do not insert/remove the extended SRAM cassette to/from the
CPU module more than 50 times (IEC 61131-2 compliant) respectively. Exceeding the limit may cause
malfunction.
●After the first use of the product, do not insert/remove the SD memory card to/from the CPU module
more than 500 times. Exceeding the limit may cause malfunction.
●Do not touch the metal terminals on the back side of the SD memory card. Doing so may cause
malfunction or failure of the module.
●Do not touch the integrated circuits on the circuit board of an extended SRAM cassette. Doing so may
cause malfunction or failure of the module.
●Do not drop or apply shock to the battery to be installed in the module. Doing so may damage the
battery, causing the battery fluid to leak inside the battery. If the battery is dropped or any shock is
applied to it, dispose of it without using.
●Startup and maintenance of a control panel must be performed by qualified maintenance personnel
with knowledge of protection against electric shock. Lock the control panel so that only qualified
maintenance personnel can operate it.

8
[Startup and Maintenance Precautions]
[Operation Precautions]
[Disposal Precautions]
[Transportation Precautions]
CAUTION
●Before handling the module, touch a conducting object such as a grounded metal to discharge the
static electricity from the human body. Failure to do so may cause the module to fail or malfunction.
CAUTION
●When changing data and operating status, and modifying program of the running programmable
controller from an external device such as a personal computer connected to an intelligent function
module, read relevant manuals carefully and ensure the safety before operation. Incorrect change or
modification may cause system malfunction, damage to the machines, or accidents.
●Do not power OFF the programmable controller or do not reset the CPU module while the setting
values in the buffer memory are being written to the flash ROM in the module. Doing so will make the
data in the flash ROM and SD memory card undefined. The values need to be set in the buffer
memory and written to the flash ROM and SD memory card again. Doing so may cause malfunction or
failure of the module.
CAUTION
●When disposing of this product, treat it as industrial waste.
●When disposing of batteries, separate them from other wastes according to the local regulations. For
details on battery regulations in EU member states, refer to the MELSEC iQ-R Module Configuration
Manual.
CAUTION
●When transporting lithium batteries, follow the transportation regulations. For details on the regulated
models, refer to the MELSEC iQ-R Module Configuration Manual.
●The halogens (such as fluorine, chlorine, bromine, and iodine), which are contained in a fumigant
used for disinfection and pest control of wood packaging materials, may cause failure of the product.
Prevent the entry of fumigant residues into the product or consider other methods (such as heat
treatment) instead of fumigation. The disinfection and pest control measures must be applied to
unprocessed raw wood.

9
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.

10
INTRODUCTION
Thank you for purchasing the Mitsubishi Electric MELSEC iQ-R series programmable controllers.
This manual describes the functions and programming to use the module listed below.
Before using the product, please read this manual and relevant manuals carefully and develop familiarity with the
performance of MELSEC iQ-R series programmable controller to handle the product correctly.
When applying the example programs provided in this manual to an actual system, ensure the applicability and confirm that it
will not cause system control problems.
Please make sure that the end users read this manual.
The program examples shown in this manual are the examples in which C24 is assigned to the input/output
No. X/Y0 to X/Y1F unless otherwise specified. To use the program examples shown in this manual, the input/
output number assignment is required. For details on the assignment of input/output number, refer to the
following manual.
MELSEC iQ-R Module Configuration Manual
Relevant products
RJ71C24, RJ71C24-R2, RJ71C24-R4

11
CONTENTS
CONTENTS
SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
CONDITIONS OF USE FOR THE PRODUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
INTRODUCTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
RELEVANT MANUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
PART 1 BASIC FUNCTIONS
CHAPTER 1 DATA COMMUNICATION USING MC PROTOCOL 22
1.1 Accessing to CPU Module Using MC Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
File access method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1.2 Data Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Formats and codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Parameter settings for MC protocol communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Applicability of multiple CPU systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Applicability of remote password function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Using MX Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
CHAPTER 2 DATA COMMUNICATION USING PREDEFINED PROTOCOL 26
2.1 Data Communication Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.2 Communication Type of Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.3 Packet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Packet elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.4 Execution Condition of Predefined Protocol Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
CHAPTER 3 DATA COMMUNICATION USING NONPROCEDURAL PROTOCOL 52
3.1 Receiving Data from Target Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Receiving methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Receive area and receive data arrangement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Program for data reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Reception error detection and check methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Receive data clear. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Receive end data quantity and receive end code settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
3.2 Transmitting Data to Target Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Sending methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Send area and send data arrangement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Program for data transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Transmission error detection and check methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
3.3 Considerations for Data Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
CHAPTER 4 DATA COMMUNICATION USING BIDIRECTIONAL PROTOCOL 86
4.1 Receiving Data from Target Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Receiving methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Receive area, receive data arrangement and contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Program for data reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Reception error detection and check methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

12
Receive data clear. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
4.2 Transmitting Data to Target Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Sending methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Send area and send data arrangement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Program for data transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Transmission error detection and check methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
4.3 Processing when Simultaneous Transmission is Performed during Full-Duplex Communications . . . 104
Processing when simultaneous transmissions occur . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Processing of transmitted/received data when simultaneous transmissions occur. . . . . . . . . . . . . . . . . . . . . . 105
4.4 Considerations for Data Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
CHAPTER 5 DEBUG SUPPORT FUNCTION 109
5.1 Circuit Trace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Procedure for the circuit trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Performing circuit trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Circuit trace option setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
5.2 Protocol Execution Log Storage Function (for Predefined Protocol only) . . . . . . . . . . . . . . . . . . . . . . . . 113
Checking with Engineering tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Checking with the buffer memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
PART 2 ADDITIONAL FUNCTIONS
CHAPTER 6 USING THE PROGRAMMABLE CONTROLLER CPU MONITORING
FUNCTION 119
6.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
6.2 Programmable Controller CPU Monitoring Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Data registration for using the programmable controller CPU monitoring function . . . . . . . . . . . . . . . . . . . . . . 120
CPU module monitoring information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Monitoring timing of CPU module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Timings of transmitting monitoring results to the target device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Transmission methods of monitoring results and data transmitted to the target device . . . . . . . . . . . . . . . . . . 127
Data arrangement of device information and programmable controller CPU status information . . . . . . . . . . . 130
Execution order for using the programmable controller CPU monitoring function. . . . . . . . . . . . . . . . . . . . . . . 137
6.3 Settings for Using the Programmable Controller CPU Monitoring Function . . . . . . . . . . . . . . . . . . . . . . 138
Parameter setting items for the programmable controller CPU monitoring function . . . . . . . . . . . . . . . . . . . . . 138
How to register and cancel the programmable controller CPU monitoring function . . . . . . . . . . . . . . . . . . . . . 142
6.4 Considerations for Using the Programmable Controller CPU Monitoring Function . . . . . . . . . . . . . . . . 146
CHAPTER 7 COMMUNICATIONS BY THE MODEM FUNCTION 148
7.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Function list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
7.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
System configuration when performing data communication with target device . . . . . . . . . . . . . . . . . . . . . . . . 152
Considerations for system configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
7.3 Specifications of Modem Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Applicability of remote password function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
List of input/output signals for the modem function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Buffer memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Considerations for using the modem function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

13
CONTENTS
7.4 Startup of the Modem Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Startup procedure of the modem function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Initial settings of Serial communication module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Register/read/delete data for initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Register/read/delete data for connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Initialization of modem/TA (terminal adapter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Line connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Data communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Line disconnection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
7.5 Sample program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Program for data communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
CHAPTER 8 RECEIVING DATA WITH AN INTERRUPT PROGRAM 219
8.1 Settings for Receiving Data Using an Interrupt Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
8.2 Interrupt Program Startup Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
8.3 Reception Control Method Using an Interrupt Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
8.4 Program Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
8.5 Considerations when Receiving Data with an Interrupt Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
CHAPTER 9 CHANGING DATA LENGTH UNITS TO BYTE UNITS (WORD/BYTE
UNITS SETTING) 225
CHAPTER 10 CHANGING DATA COMMUNICATION MONITORING TIME 227
10.1 No-reception Monitoring Time (timer 0) Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
C24 operation by no reception monitoring time (timer 0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Changing the no-reception monitoring time (timer 0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
10.2 Response Monitoring Time (timer 1) Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
C24 operation by response monitoring time (timer 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Changing the response monitoring time (timer 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
10.3 Send Monitoring Time (timer 2) Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
C24 operation by send monitoring time (timer 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Changing the send monitoring time (timer 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
10.4 Transmission Wait Time Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
C24 operation by transmission wait time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Changing the transmission wait time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
CHAPTER 11 DATA COMMUNICATIONS USING DC CODE TRANSMISSION
CONTROL 236
11.1 Control Contents of DTR/DSR (ER/DR) Signal Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
C24 DTR control contents and free OS area specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
C24 DSR control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
11.2 Control Contents of DC Code Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
DC1/DC3 transmission control, DC1/DC3 reception control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
DC2/DC4 transmission control, DC2/DC4 reception control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
11.3 Considerations for Using Transmission Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
CHAPTER 12 DATA COMMUNICATIONS USING HALF-DUPLEX
COMMUNICATIONS 243
12.1 Half-duplex Communications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
12.2 Data Transmission and Reception Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

14
12.3 Changing the Communication Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
12.4 Connector Connections for Half-duplex Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248
12.5 Considerations for Half-duplex Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
CHAPTER 13 CONTENTS AND REGISTRATION OF USER FRAMES FOR DATA
COMMUNICATION 250
13.1 User Frame Types and Contents During Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250
User frames to be registered and used by the user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Default registration frame (read only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
13.2 Transmission/Reception Processing Using User Frame Registration Data . . . . . . . . . . . . . . . . . . . . . . . 259
Transmitting data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Receiving data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
13.3 Considerations for Registering, Reading, and Deleting User Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
13.4 Registering/Reading/Deleting User Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
CHAPTER 14 ON-DEMAND DATA COMMUNICATIONS USING USER FRAMES 267
14.1 Data Communication Function Using User Frame. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
14.2 User Frame On-Demand Data Transmission and Buffer Memory Used . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
14.3 On-Demand Function Control Procedure During User Frame Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Data communication using the ASCII code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Data communications using the binary code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
14.4 Example of On-Demand Data Transmission Program Using User Frames . . . . . . . . . . . . . . . . . . . . . . . . 274
CHAPTER 15 DATA COMMUNICATIONS USING USER FRAMES 276
15.1 Procedure of Data Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
15.2 Data Reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Receive data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Timing for start/completion of data reception. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Reception procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Setting of receive user frames. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
15.3 Program for Data Reception with User Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Application program for data reception using a combination that specifies the start frame . . . . . . . . . . . . . . . 303
Application program for data reception using a combination that does not specify the start frame . . . . . . . . . 310
15.4 Data Transmission. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Send data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Transmission procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Settings of send user frames. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
15.5 Application Program for Data Transmission using a Combination that does not Specify the Start
Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
CHAPTER 16 TRANSPARENT CODES AND ADDITIONAL CODES 326
16.1 Handling Transparent Code and Additional Code Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
16.2 Registering Transparent Codes and Additional Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
16.3 Handling Transparent and Additional Codes for Nonprocedural Protocol Data Communication. . . . . . 328
16.4 Data Communication Using Nonprocedural Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Example of data reception. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Example of data transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
16.5 Handling Transparent and Additional Codes for Bidirectional Protocol Data Communication. . . . . . . . 339
16.6 Data Communication Using Bidirectional Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Example of data reception. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

15
CONTENTS
Example of data transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
CHAPTER 17 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION) 347
17.1 ASCII-Binary Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
17.2 Settings for ASCII-BIN Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
17.3 ASCII-BIN Conversion for Data Communicated with Nonprocedural Protocol . . . . . . . . . . . . . . . . . . . . . 348
17.4 Data Communication Using Nonprocedural Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Example of data reception. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Example of data transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
17.5 ASCII-BIN Conversion for Data Communicated with Bidirectional Protocol. . . . . . . . . . . . . . . . . . . . . . . 359
17.6 Data Communication Using Bidirectional Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Example of data reception. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Example of data transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
CHAPTER 18 DATA COMMUNICATIONS BETWEEN TARGET DEVICE AND CPU
MODULE IN M:N BASIS 366
18.1 Considerations on Data Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
18.2 Arrangement for Interlock among Target Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Maximum communication time per target device station. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Message structure when communicating data among target devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
18.3 Examples of Procedure for Data Communications with CPU Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Sequential data communications between target devices and the CPU module . . . . . . . . . . . . . . . . . . . . . . . 371
Data communications between target devices and CPU module by designating a master station and slave
stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
CHAPTER 19 SWITCHING THE MODE AFTER STARTING 377
19.1 Mode Switching Operation and Contents that can be Changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
Settings that can be changed with mode switching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
Operation for mode switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
19.2 Considerations for Mode Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
19.3 I/O Signals for Handshake with CPU Module and Buffer Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
19.4 Mode Switching Method by Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
19.5 How to Switch Mode from Target Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
CHAPTER 20 USING SEND/RECEIVE DATA MONITORING FUNCTION 387
20.1 Send/receive Data Monitoring Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Send/receive data monitoring operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
20.2 Send/receive Data Monitoring Function Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
Buffer memory for send/receive data monitoring function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
20.3 Send/receive Data Monitoring Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
CHAPTER 21 INDEPENDENT/LINKED OPERATION OF INTERFACE 397
21.1 Setting and Data Flow of Independent Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
21.2 Setting and Data Flow of Interlink Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Setting example for MELSOFT connection via C24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
CHAPTER 22 PARAMETER REGISTRATION TO CPU MODULE 401

16
CHAPTER 23 RS-422/485 INTERFACE ECHO BACK ENABLE/PROHIBIT
SPECIFICATION 403
CHAPTER 24 ERRONEOUS NOISE SIGNAL RECEPTION PREVENTION
FUNCTION 405
24.1 Erroneous Noise Signal Reception Prevention Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
24.2 Setting for the Erroneous Noise Signal Reception Prevention Function . . . . . . . . . . . . . . . . . . . . . . . . . 406
CHAPTER 25 AUTOMATIC REMOVAL OF NULL CHARACTERS INCLUDED IN
SEND DATA 407
25.1 Automatic Removal of NULL Characters during Data Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
25.2 Setting for NULL Character Automatic Removal Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
25.3 NULL Character Removal to Send Data using Nonprocedural Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . 408
25.4 Program Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Program example of data communication using the nonprocedural protocol . . . . . . . . . . . . . . . . . . . . . . . . . .410
25.5 NULL Characters Removal for Send Data using Bidirectional Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . 415
25.6 Program Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Program example of data communication using the bidirectional protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
PART 3 PARAMETER SETTINGS AND TROUBLESHOOTING
CHAPTER 26 PARAMETER SETTING 422
26.1 Parameter Setting Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
26.2 Module Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Basic settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Application settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
Interrupt settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Refresh setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
26.3 Module Extended Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
User frame contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Modem initialization data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Modem connection data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
CHAPTER 27 TROUBLESHOOTING 440
27.1 Checking Module Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
Error information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
Module information list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Intelligent function module monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Error information clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
Individual station test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
Loopback test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
27.2 How to Clear Programmable Controller CPU Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
27.3 Troubleshooting by Symptom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
SD LED does not flash even after a send request was made . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
RD LED does not flash even though the target device is transmitting a message . . . . . . . . . . . . . . . . . . . . . . 459
No response message is returned even though the target device transmitted a message and the RD LED
flashes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
Read request signal does not turn ON even though the target device transmitted a message and the RD
LED flashes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461

17
CONTENTS
The CPRTCL instruction execution is not completed although the RD LED flashes. . . . . . . . . . . . . . . . . . . . . 462
RUN LED turns OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
ERR LED flashes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
ERR LED turns ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
C ERR LED turns ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
Hardware information communication error "SIO" occurs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
Hardware information communication error "PRO." occurs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
Hardware information communication error "P/S" occurs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
Hardware information communication error "C/N" occurs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
Hardware information communication error "NAK" occurs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Communication is intermittent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Undecodable data are transmitted or received . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
Whether the communication error is caused on C24 or target device is unclear . . . . . . . . . . . . . . . . . . . . . . . 471
Communication is not established via modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Communication is not established with the ISDN sub-address when using a modem . . . . . . . . . . . . . . . . . . . 472
Fixed cycle send is not performed normally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
Condition match send is not performed normally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
Data cannot be received by an interrupt program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
Data cannot be written to flash ROM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
27.4 Error Code List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
27.5 Event History List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
APPENDIX 492
Appendix 1 Module Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
Appendix 2 Input/Output Signal List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
Appendix 3 Buffer Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
Buffer memory list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
Appendix 4 Dedicated Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
Dedicated instruction list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
Appendix 5 Operation Image and Data Structure of Predefined Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
Operation image of each communication type of protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
Verification operation of receive packet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
Data examples of packet elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
Appendix 6 Processing Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
Appendix 7 When Connecting the Module to a Remote Head Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Communication example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
Appendix 8 Added and Changed Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
INDEX 565
REVISIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .568
WARRANTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .569
TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .570

18
RELEVANT MANUALS
e-Manual refers to the Mitsubishi FA electronic book manuals that can be browsed using a dedicated tool.
e-Manual has the following features:
• Required information can be cross-searched in multiple manuals.
• Other manuals can be accessed from the links in the manual.
• The hardware specifications of each part can be found from the product figures.
• Pages that users often browse can be bookmarked.
TERMS
Unless otherwise specified, this manual uses the following terms.
Manual name [manual number] Description Available form
MELSEC iQ-R Serial Communication Module User's
Manual (Application)
[SH-081251ENG] (this manual)
Functions, input/output signals, buffer memory, parameter setting, and trouble
shooting of Serial communication module
Print book
e-Manual
PDF
MELSEC iQ-R Serial Communication Module User's
Manual (Startup)
[SH-081250ENG]
Specifications, procedures prior to operation, system configurations, wring,
and data communication examples of Serial communication module
Print book
e-Manual
PDF
MELSEC Communication Protocol Reference
Manual
[SH-080008]
Specifications, accessible range, message protocols, and functions of
MELSEC Communication Protocol
Print book
e-Manual
PDF
Terminology Description
3C frame
(Formats 1 to 4)
4C frame
(Formats 1 to 4)
A message format for C24 for data communications with ASCII code data using the MC protocol
This is the same message format as the communication frame using the dedicated protocol for the QnA series
Serial Communication Module.
• 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)
4C frame
(Format 5)
A message format for C24 for data communication with binary code data using the MC protocol
This is the same message format as the communication frame using the dedicated protocol for the QnA series
Serial Communication Module.
• QnA compatible 4C frame (Format 5): QnA extension frame (Format 5)
Bidirectional protocol A data communication function to communicate any data between a CPU module and the target device using the
communication procedure for C24
Buffer memory A memory of an Intelligent function module to store data (including setting value and monitored value) sent to/
receive from CPU module
BUFRCVS An abbreviation for Z.BUFRCVS
C24 Another term for the MELSEC iQ-R series Serial Communication Module
CPRTCL An abbreviation for G.CPRTCL or GP.CPRTCL
CPU module A generic term for MELSEC iQ-R series CPU module
CSET An abbreviation for ZP.CSET
Data communication function A generic term for MC protocol, predefined protocol, nonprocedural protocol, and bidirectional protocol
Engineering tool A tool for setting, programming, debugging, and maintaining programmable controllers.
For the supported tools, refer to the following manual.
MELSEC iQ-R Module Configuration Manual
GETE An abbreviation for G.GETE or GP.GETE
Independent operation A mode of interface operation to communicate data with the target device with a function specified in each
communication protocol setting without interaction between two interfaces of C24
INPUT An abbreviation for G.INPUT
Intelligent function module A generic term for modules which has functions other than input and output, such as A/D converter module and
D/A converter module
Interlink operation A mode of interface operation to communicate data with the target device with the two interfaces linked one
another when two interfaces of C24 are connected to target devices respectively
The two interfaces communicate data with the same data communication function (MC protocol (identical format)
or nonprocedural protocol) and the same transmission specifications. (Interlink operation of the predefined
protocol and the bidirectional protocol is not allowed.)