MELSEC iQ-R CC-Link IE Field Network Remote Head Module User's Manual (Application)

MELSEC iQ-R CC-Link IE Field Network
Remote Head Module User's Manual

(Application)
-RJ72GF15-T2
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 MELSEC iQ-R Module Configuration Manual.
In this manual, the safety precautions are classified into two levels: " WARNING" and " CAUTION".
Indicates that incorrect handling may cause hazardous conditions, resulting in

WARNING death or severe injury.
Indicates that incorrect handling may cause hazardous conditions, resulting in

CAUTION 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
[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/reverse 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.
● 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.
2
WARNING
● 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. Failure to do so may result in an
accident due to an incorrect output or malfunction.
● 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.
● Configure safety circuits external to the remote head module to ensure that the entire system
operates safely even when a fault occurs in the external power supply or the remote head module.
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/reverse rotations or upper/lower limit positioning) must be configured
external to the remote head module.
(2) When the remote head module detects an abnormal condition, outputs are:
• Held or turned off according to the parameter setting of each module mounted on the main
base unit or extension base unit if the self-diagnostic function of the remote head 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
remote head 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 remote head module. For a fail-safe circuit
example, refer to "General Safety Requirements" in the MELSEC iQ-R Module Configuration
Manual.
● Configure a circuit so that the remote head module 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.
● When connecting an external device with a remote head module to modify data of a running remote
head module, configure an interlock circuit in the program of the master station to ensure that the
entire system will always operate safely. For other forms of control (such as parameter change, forced
output, or operating status change) of a running remote head module, 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 head module is remotely controlled by an external device, immediate
action cannot be taken if a problem occurs in the remote head module due to a communication failure.
To prevent this, configure an interlock circuit in the program of the master station, and determine
corrective actions to be taken between the external device and remote head module in case of a
communication failure.
● Do not write any data to the buffer memory in the remote head module. Doing so may cause
malfunction of the programmable controller system.
● Do not write any data from the remote head module to the "system area" and "write-protect area" of
the buffer memory in each module. Also, do not use any "use prohibited" signals as an output signal
from the remote head 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.
3
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 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 also may cause malfunction or failure of the module.
● When changing the operating status of the CPU module from external devices (such as the remote
RUN/STOP functions), select "Do Not Open by Program" for "Opening Method" of "Module
Parameter". If "Open by Program" is selected, an execution of the remote STOP function causes the
communication line to close. Consequently, the CPU module cannot reopen the line, and external
devices cannot execute the remote RUN function.
● After the remote head module is powered on or is reset, the time taken to enter the RUN status varies
depending on the system configuration and/or parameter settings. Design circuits so that the entire
system will always operate safely, regardless of the time.
● Do not power off or reset the remote head module while the parameters are being written. Doing so
may cause malfunction or failure of the module.
[Installation 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.
4
[Installation Precautions]
CAUTION
● Use the programmable controller in an environment that meets the general specifications in the Safety
Guidelines included with 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 SD 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 the 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 can cause malfunction or failure of the
module.
[Wiring Precautions]
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 a blank cover module (RG60) to each empty slot and an included
extension connector protective cover to the unused extension cable connector before powering on the
system 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.
● 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.
6
[Startup and Maintenance Precautions]
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 and 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.

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
● 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.
7
CAUTION
● 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.
● 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.
● When connecting an external device with a remote head module to modify data of a running
programmable controller, configure an interlock circuit in the program of the master station to ensure
that the entire system will always operate safely. For other forms of control (such as parameter
change, forced output, or operating status change) of a running remote head module, read the
relevant manuals carefully and ensure that the operation is safe before proceeding. Improper
● Especially, when a remote head module is remotely controlled by an external device, immediate
action cannot be taken if a problem occurs in the remote head module due to a communication failure.
To prevent this, configure an interlock circuit in the program of the master station, and determine
corrective actions to be taken between the external device and remote head module in case of a
communication failure.
[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 change or
modification may cause system malfunction, damage to the machines, or accidents.
● Do not power off the programmable controller or 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 undefined. The values need to be set in the buffer memory and written to the flash ROM
again. Doing so can cause malfunction or failure of the module.
[Disposal Precautions]
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.
8
[Transportation Precautions]
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.
INTRODUCTION
Thank you for purchasing the Mitsubishi Electric MELSEC iQ-R series programmable controllers.
This manual describes the functions, parameter settings, and troubleshooting of the relevant products listed below.
Before using this product, please read this manual and the relevant manuals carefully and develop familiarity with the
functions and performance of the MELSEC iQ-R series programmable controller to handle the product correctly.
Please make sure that the end users read this manual.
Relevant product
RJ72GF15-T2
10
CONTENTS
SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
CONDITIONS OF USE FOR THE PRODUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
RELEVANT MANUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
CHAPTER 1 FUNCTIONS 16
CONTENTS
1.1 Data Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.2 Cyclic Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Cyclic transmission of bit device data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Cyclic transmission of word device data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
1.3 Remote Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Remote RUN/STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Remote RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
1.4 Label Access Setting from External Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Setting procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
File operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
1.5 RAS Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Self-diagnostic function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Error clear function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Event history function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Redundant power supply system diagnostic function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
1.6 Security Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
1.7 Monitor Function (Current Value Change) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
1.8 Redundant Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
System configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Procedures before operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
System switching operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Determining control system and standby system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
System consistency check and operations when an error occurs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
System switching function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Memory copy function from control system to standby system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Functions restricted in a redundant system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Setting example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
1.9 Safety Communication Relay Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
System configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Procedures before operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Restricted functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Setting example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
CHAPTER 2 PARAMETER SETTINGS 76

2.1 CPU Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Name Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Operation Related Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
RAS Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Network Required Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
11
Network Application Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
2.2 Module Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
CHAPTER 3 AVAILABLE FILE OPERATION 85
CHAPTER 4 TROUBLESHOOTING 87
4.1 Troubleshooting Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4.2 Checking with LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4.3 Checking the Module Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
4.4 Checking the Network Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
4.5 Replacing the Remote Head Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
For a system configuration other than a redundant system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
For the standby system in a redundant system configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
4.6 Troubleshooting by Symptom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
When cyclic transmission cannot be performed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
When transient transmission cannot be performed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
When the POWER LED of the power supply module turns off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
When the specific extension base unit cannot be recognized. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
When the specific Q series extension base unit cannot be recognized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
When a redundant system is configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Safety communication relay cannot be performed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
4.7 Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Error code system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
How to clear errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
List of error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
4.8 List of Parameter Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
System Parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
CPU Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
4.9 Event List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
How to read the event list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Event list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
APPENDICES 134
Appendix 1 List of Link Special Relay (SB) Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Appendix 2 List of Link Special Register (SW) Areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Appendix 3 List of Special Relay (SM) Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Appendix 4 List of Special Register (SD) Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Appendix 5 Access Code and Attribute Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Appendix 6 Processing Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Processing time used to calculate the transmission delay time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
System switching time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Appendix 7 New or Revised Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
INDEX 168
REVISIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170
WARRANTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171
TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172
12
RELEVANT MANUALS
Manual name [manual number] Description Available form
MELSEC iQ-R CC-Link IE Field Network Remote Head Functions, parameter settings, and troubleshooting of the CC- Print book
Module User's Manual (Application) Link IE Field Network remote head module
e-Manual
[SH-081616ENG] (this manual)
PDF
MELSEC iQ-R CC-Link IE Field Network Remote Head Specifications, procedures before operation, system Print book
Module User's Manual (Startup) configuration, wiring, and communication examples of the
e-Manual
[SH-081614ENG] CC-Link IE Field Network remote head module PDF
e-Manual refers to the Mitsubishi Electric 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.
• Sample programs can be copied to an engineering tool.
13
TERMS
Unless otherwise specified, this manual uses the following terms.
Term Description
Base unit A generic term for main base units, extension base units, and RQ extension base units
Buffer memory Memory in an intelligent function module for storing data such as setting values and monitored values.
CC-Link IE module A generic term for the CC-Link IE Controller Network-equipped module and CC-Link IE Field Network-
equipped master/local module
Control system A system that controls a redundant system and performs network communications in a redundant
system
CPU module A generic term for the MELSEC iQ-R series, MELSEC-Q series, and MELSEC-L series CPU module
Cyclic transmission A function by which data are periodically exchanged among stations on the same network using link
devices
Data link A generic term for cyclic transmission and transient transmission
Dedicated instruction An instruction for using the functions of a module
Device A device (X, Y, W, or others) in a CPU module and remote head module
Disconnection A process of stopping data link if a data link error occurs
Engineering tool The product name of the software package for the MELSEC programmable controllers
Ethernet device A generic term for the devices supporting IP communication (such as personal computers)
Ethernet-equipped module A generic term for the RJ71EN71 (when the Ethernet function is used) and MELSEC iQ-R series CPU
module (when the Ethernet function is used)
Global label A label that is valid for all the program data when multiple program data are created in the project.
There are two types of global label: a module specific label (module label), which is generated
automatically by the engineering tool, and an optional label, which can be created for any specified
device.
I/O module A generic term for the input module, output module, I/O combined module, and interrupt module
Intelligent device station A station that exchanges I/O signals (bit data) and I/O data (word data) with another station by cyclic
transmission. This station responds to a transient transmission request from another station and also
issues a transient transmission request to another station.
Intelligent function module A module that has functions other than input and output, such as an A/D converter module and D/A
converter module
Label A label that represents a device in a given character string
Link device A device (RX, RY, RWr, or RWw) in a module on CC-Link IE Field Network
Link special register (SW) Word data that indicates the operating status and data link status of a module on CC-Link IE Field
Network
Link special relay (SB) Bit data that indicates the operating status and data link status of a module on CC-Link IE Field Network
Local station A station that performs cyclic transmission and transient transmission with the master station and other
local stations
Master station A station that controls the entire network. This station can perform cyclic transmission and transient
transmission with all stations. Only one master station can be used in a network.
Master/local module A generic term for the RJ71GF11-T2, QJ71GF11-T2, QS0J71GF11-T2, LJ71GF11-T2 CC-Link IE Field
Network master/local module and the following modules when the CC-Link IE Field Network function is
used:
• RJ71EN71
• RnENCPU
Module label A label that represents one of memory areas (I/O signals and buffer memory areas) specific to each
module in a given character string. For the module used, GX Works3 automatically generates this label,
which can be used as a global label.
Network module A generic term for the following modules:
• Ethernet interface module
• CC-Link IE Controller Network module
• Module on CC-Link IE Field Network
• MELSECNET/H network module
• MELSECNET/10 network module
• RnENCPU (network part)
New control system A remote head module that has switched to control system from standby system after system switching
New standby system A remote head module that has switched to standby system from control system after system switching
Power supply module The abbreviation for the MELSEC iQ-R series power supply module
RAS The abbreviation for Reliability, Availability, and Serviceability. This term refers to the overall usability of
automated equipment.
14
Term Description
Redundant power supply base unit A generic term for base units used for a redundant configuration of power supplies.
This unit is used together with redundant power supply modules, to build a redundant power supply
system.
Redundant power supply module A power supply module used for a redundant configuration of power supplies.
This module is used together with a redundant power supply base unit, to build a redundant power
supply system.
Redundant power supply system A system that has two power supply modules on a base unit. Even if one power supply module has
failed, operation can be continued with the other power supply module.
Redundant system A system consisting of two systems that have same configuration (CPU module, power supply module,
network module, and other modules). Even after an error occurs in one of the two system, the other
system takes over the control of the entire system. For details, refer to "Redundant system" of the
following manual.
 MELSEC iQ-R Module Configuration Manual
Remote device station A station that exchanges I/O signals (bit data) and I/O data (word data) with another station by cyclic
transmission. This station responds to a transient transmission request from another station.
Remote head module The abbreviation for the RJ72GF15-T2 CC-Link IE Field Network remote head module
Remote I/O station A station that exchanges I/O signals (bit data) with the master station by cyclic transmission
Remote input (RX) Bit data input from a slave station to the master station (For some areas in a local station, data are input
in the opposite direction.)
Remote output (RY) Bit data output from the master station to a slave station (For some areas in a local station, data are
output in the opposite direction.)
Remote register (RWr) Word data input from a slave station to the master station (For some areas in a local station, data are
input in the opposite direction.)
Remote register (RWw) Word data output from the master station to a slave station (For some areas in a local station, data are
output in the opposite direction.)
RQ extension base unit The abbreviation for the MELSEC iQ-R series RQ extension base unit
SIL2 function module Another name for the R6PSFM
This module is used with the SIL2 Process CPU as a pair and performs safety control. The module can
only be paired with the SIL2 Process CPU.
SIL2 mode An operation mode for the I/O module and the intelligent function module that perform the safety input/
output in the SIL2 level. For details on the SIL2 mode, refer to the following.
 Manuals for the I/O module or intelligent function module used
SIL2 Process CPU A generic term for the R08PSFCPU, R16PSFCPU, R32PSFCPU, and R120PSFCPU.
This module is used with a SIL2 function module as a pair, and performs both standard control and
safety control. This module is also used with a redundant function module as a pair and configures a
redundant system.
Slave station A generic term for a local station, remote I/O station, remote device station, and intelligent device
station
Standby system A backup system in a redundant system
System A A system that is set as the system A to distinguish two systems, which are connected with two tracking
cables.
When the two systems start up at the same time, this system will be a control system. System switching
does not affect the system A/B setting.
System B A system that is set as the system B to distinguish two systems, which are connected with two tracking
cables.
When the two systems start up at the same time, this system will be a standby system. System
switching does not affect the system A/B setting.
System switching A function which switches the systems between the control system and the standby system to continue
operation of the redundant system when a failure or an error occurs in the control system
Tracking cable An optical fiber cable used to connect two redundant function modules in a redundant system
Transient transmission A function of communication with another station, which is used when requested by a dedicated
instruction or the engineering tool
15
1 FUNCTIONS
1.1 Data Communication
Data communication with the master station

Data is communicated by the following methods between the remote head module and the master station.
• Cyclic transmission ( Page 17 Cyclic Transmission)
• Transient transmission ( User's manual for the master/local module used)
Data communication with the connected module

The following methods are used for data communication with a module connected to the remote head module.
Data communication method Description Reference
I/O refresh Input refresh Inputs ON/OFF data from the input module, intelligent function module, or Page 17 Cyclic
network module to the remote head module. transmission of bit
device data
Output refresh Outputs ON/OFF data from the remote head module to the output module,
intelligent function module, or network module.
Intelligent function module refresh Performs I/O data communication between the buffer memory of the intelligent Page 23 Cyclic
function module and the remote head module device. transmission of word
device data
Network module refresh Performs I/O data communication between link special relay (SB), link special  User's manual for
register (SW), as well as link device of the network module and the remote head the network module
module device. used
1 FUNCTIONS
16 1.1 Data Communication
1.2 Cyclic Transmission
This section describes how to perform cyclic transmission of bit and word device data of the remote head module.
1
Cyclic transmission of bit device data

The CPU module (1) can use the input (X) and output (Y) data from a module connected to the remote head module (3) as if
they were the input and output data of the master/local module (2).
(1) (2) (3)

X RX RX
X
Y RY RY Y
1 FUNCTIONS
1.2 Cyclic Transmission 17
Data flow
This section describes the cyclic transmission data flow of bit device data and the setting for transmission.
• When data is input from an intelligent device station to the master station: The input (X) data from each module connected
to the remote head module is input to the remote input (RX) of the master station.
• When data is output from the master station to the intelligent device station: The remote output (RY) data of the master
station is output to the output (Y) of each module connected to the remote head module.
1 FUNCTIONS
18 1.2 Cyclic Transmission
■When the default I/O assignment settings are used
This section describes the data flow when 0000H is set to the start I/O number of the RX/RY setting of the master station, and
when the I/O assignment setting of the remote head module is not changed from the default. 1
RJ72GF15-T2 RX10 RY10R2 RX10 RY10R2
(1)
RX RX X X X X X
0000H 0000H 0000H 0000H
0000H 0000H
000FH 000FH 000FH 000FH
003FH 003FH
03FFH
3FFFH
RY RY Y Y Y Y Y
0000H 0000H 0000H 0000H
0000H 0000H
000FH 000FH 000FH 000FH
003FH 003FH
03FFH
3FFFH
(1) RX/RY ranges of the remote head module (station No.1) which are assigned to the master station
• RX: 0000H to 003FH
• RY: 0000H to 003FH
1 FUNCTIONS
■When the settings of I/O assignment are changed
This section describes the data flow when 0000H is set to the start I/O number of the RX/RY setting of the master station, and
when the I/O assignment setting of the remote head module is changed from the default.
The following shows the assignment when the I/O assignment is set as shown in the following window.
RJ72GF15-T2 RX10 RY10R2 RX10 RY10R2
(1)
RX RX X X X X X
0000H 0000H 0000H 0000H 0000H
0000H
000FH 000FH 000FH 000FH
003FH 003FH
03FFH
3FFFH
RY RY Y Y Y Y Y
0000H 0000H 0000H 0000H
0000H 0000H
000FH 000FH 000FH 000FH
003FH 003FH
03FFH
3FFFH
(1) RX/RY ranges of the remote head module (station No.1) which are assigned to the master station
• RX: 0000H to 003FH
• RY: 0000H to 003FH
1 FUNCTIONS
Setting method
In the network configuration setting of the master station, set the total number of I/O points of the modules connected to the
1
remote head module, in 16-point units.
• To set an empty slot on the intelligent device station or to change a start I/O number, change the I/O
assignment setting in the remote head module.
• If the number of points will be increased for a system expansion in future, for example, set a large number
for the RX/RY setting in the network configuration setting of the master station. Doing so will eliminate the
need to change the parameter setting of the master station at the time of the system expansion. However,
increasing the number of points also increases the processing time.
1 FUNCTIONS
Output status for each status
Depending on the status of the data link and remote head module, data may not be able to be output.
The following table summarizes how the status of the data link and remote head module affects the output status.
: Not dependent on the status
Switch Remote head Data link Output status
module status status
RUN Operating normally Cyclic The output differs depending on the status and setting of the master station. ( User's manual
transmission for the master/local module used)
being performed (1) When the CPU module on the master station is in the stop error state:
The output (Y) status is determined by the setting for the output mode upon error in the module
parameter.
 User's manual for the module used
The analog output status from the digital-analog converter module is determined by the setting of
the analog output HOLD/CLEAR function.
 User's manual for digital-analog converter module used
(2) When the CPU module on the master station is in the STOP state:
The output (Y) is determined by the refresh parameters (refresh device of RY for the remote head
module) of the master station.
• If Y is specified for the device of the CPU module, the output (Y) of the remote head module
turns off.
• If other than Y (such as M, L) is specified for the device of the CPU module, the output (Y) of
the remote head module depends on the output status during CPU STOP setting of the master
station.
RUN Operating normally Cyclic The output (Y) status is determined by the setting for the output mode upon error in the module
transmission parameter.
stopped  User's manual for the module used
RUN Operating normally Disconnected The output (Y) is held for two seconds after the communication with the master station is
terminated due to a problem such as disconnection of the Ethernet cable.
When a redundant system of redundant line is configured, the output (Y) is held for the time of "3
second + system switching monitoring time set in the master station".
The output (Y) status during disconnection is determined by the setting for the output mode upon
error in the module parameter.
RUN/STOP Error  The output (Y) status is determined by the setting for the output mode upon error in the module
parameter.
STOP Operating normally  The output (Y) status of the intelligent function module is determined by the setting for the output
mode upon error in the module parameter.
 User's manual for the intelligent function module used
1 FUNCTIONS
Cyclic transmission of word device data
The CPU module (1) can use the word data (such as data stored in the buffer memory) of the module connected to the remote 1
head module (3) as if it were the word device of the master/local module (2).
(1) (2) (3)

D RWr RWr
RWw RWw
1 FUNCTIONS
Data flow
This section describes the cyclic transmission data flow of word device data and the setting for transmission.
• When data is transferred from the master station to the intelligent device station: The remote register (RWw) data of the
master station is transferred to the buffer memory of the intelligent function module connected to the remote head module.
• When data is transferred from the intelligent device station to the master station: The buffer memory data of the intelligent
function module connected to the remote head module is transferred to the remote register (RWr) of the master station.
■When "0000H" is set to the start I/O number of the RWw/RWr setting of the master station
(1) (2) (3)
Ò Ó Ô
RWw 0000H RWw 0000H W Un\G
0000H to 0003H to 0003H
to 0003H
0007H 0007H 0007H
03FFH 03FFH
1FFFH
RWr Ò RWr Ó Ô
0000H 0000H 1000H
0006H 0006H 1006H
0007H 0007H 1007H
03FFH 13FFH
1FFFH
1FFFH
(1) Master station

(2) Remote head module
(3) Intelligent function module
 Set RWw/RWr ranges assigned to the remote head module in the network configuration setting of the master station.
 Assign 1024 points (W0 to W3FF) from RWw0.
Assign 1024 points (W1000 to W13FF) from RWr0.
 Set the refresh ranges for the remote head module and the buffer memory of the intelligent function module in the refresh settings of the intelligent function
module.
1 FUNCTIONS
Setting method
1. Perform the refresh settings of the intelligent function module connected to the remote head module.
1
[Navigation window]  [Parameter]  [Module Information]  Target Module  [Refresh settings]
Specify the following devices as the devices to be refreshed.

Item Setting range of refresh target device
"Transfer to the intelligent function module" W0 to W3FF
"Transfer to the CPU" W1000 to W13FF
2. Set RWw/RWr ranges assigned to the remote head module in the network configuration setting of the master station.
The number of points should be higher than the number of points set for the refresh settings of the intelligent function module
in step 1 above. (Set the number of points whichever is greater between "Transfer to the intelligent function module" and
"Transfer to the CPU".)
If the number of points will be increased for a system expansion in future, for example, set a large number for
the RWw/RWr setting in the network configuration setting of the master station. Doing so will eliminate the
need to change the parameter setting of the master station at the time of the system expansion. However,
increasing the number of points also increases the processing time.
1 FUNCTIONS
Precautions
When the firmware version of the master station of MELSEC iQ-R series is "04" or earlier, network reconnection processing is
performed in all stations in the following cases.
• Connecting and disconnecting cables
• Powering off and off
For that reason, a data link error may momentarily occur in all the stations, and the outputs of the connected slave stations
may turn off.
As needed, specify that the output is to be maintained in the master station and digital-analog converter module. ( Page
22 Output status for each status)
1 FUNCTIONS
1.3 Remote Operation
The operating status of the remote head module can be changed using an engineering tool or dedicated instructions from the
1
module. The following types of remote operation are available:
• Remote RUN/STOP
• Remote RESET
Remote RUN/STOP
This function remotely changes the operating status of the remote head module to RUN or to STOP, keeping the switch of the
remote head module at the RUN position. This function is useful to run or stop a remote head module located in an
inaccessible place or in the control panel by using external signals.
When the switch of the remote head module is at the STOP position, or when the CPU module on the master
station is in the STOP state (including disconnection), even if remote RUN is performed, the remote head
module will not enter the RUN state.
Executing method
The following methods are available,
■Using an engineering tool

• From the menu, open the "Remote Operation" window to execute the function. ( GX Works3 Operating Manual)
[Online]  [Remote Operation]
• Execute the function using the CC-Link IE Field Network diagnostics. ( Page 96 Remote operation)
■By an external device using SLMP

Execute the function with the SLMP command. ( SLMP Reference Manual)
■Using the module dedicated instructions

Execute the function with the dedicated instructions of a network module. ( MELSEC iQ-R Programming Manual
(Instructions, Standard Functions/Function Blocks))
1 FUNCTIONS
1.3 Remote Operation 27
Remote RESET
This function remotely resets the remote head module without switch operation when the remote head module is in STOP
state (including when either a moderate or major error occurs in the remote head module).
Even when the switch of the remote head module is at the RUN position, this function can reset the module if
it is in the STOP state.
Remote RESET setting

Remote reset can be disabled.
[Navigation window]  [Parameter]  [RJ72GF15-T2]  [CPU Parameter]  [Operation Related Setting]  [Remote
Reset Setting]
Window
Displayed items
Item Description Setting range
Remote Reset Set when externally resetting the remote head module. • Disable
• Enable
(Default: Enable*1)
*1 The default differs from that of the CPU module. Care should be taken when performing remote set through all stations specification.
Executing method
The following methods are available.
■Using an engineering tool

• From the menu, open the "Remote Operation" window to execute the function. ( GX Works3 Operating Manual)
[Online]  [Remote Operation]
• Execute the function using the CC-Link IE Field Network diagnostics. ( Page 96 Remote operation)
■By an external device using SLMP

Execute the function with the SLMP command. ( SLMP Reference Manual)
1 FUNCTIONS
28 1.3 Remote Operation
1.4 Label Access Setting from External Device
This setting enables external devices to communicate with the remote head module through GOT, SLMP, or other method by
1
specifying global label names.
Communication by specifying global label names includes the following:
• Communication from external devices (such as a monitoring device and personal computer) using label names
• Specification of label names for GOT (engineering tool for GOT) objects and figures
GOT
Ethernet
· ·
(1) (2)
(1) Remote head module

(2) Ethernet-equipped module
The local label and module label cannot be accessed from external devices
Setting procedure
This section describes the setting procedure to enable access from external devices by specifying the global label name.
Operating procedure
1. Set the label in "Global [Global Label Setting]"
and select the "Access from External Device"
checkbox.
[Navigation window]  [Label]  [Global
Label]  [Global]
2. Check the capacity of the label communication
data.
[Online]  [CPU Memory Operation]
 GX Works3 Operating Manual
3. Write the parameters, global label setting, and
global label assignment information files to the
remote head module.
File operation
The label communication data can be written from an engineering tool. Reading and deleting*1 are not possible.
*1 Deleting an entire folder is possible.
1 FUNCTIONS
1.4 Label Access Setting from External Device 29
1.5 RAS Function
Self-diagnostic function
This function diagnoses the remote head module to see whether an error exists or not.
Timing of self-diagnostics
If an error occurs when the remote head module is powered on or while it is in the RUN/STOP state, the remote head module
detects and displays the error. However, depending on the error occurrence status, the remote head module may not be able
to detect an error. Configure safety circuits external to the programmable controller to ensure that the entire system operates
safely even in such a case.
Check method of error

This section describes the check methods when error occurs.
■Using the special relay and special register

If the remote head module detects an error, 'Latest self-diagnostic error' (SM0) and 'Latest self-diagnostic error' (SM1) turns
on, and the error code corresponding to the error definition is stored in 'Latest self-diagnostic error code' (SD0). If multiple
errors are detected, the latest error code is stored in 'Latest self-diagnostic error code' (SD0). Configure interlocking for either
the remote head module or the machine system using 'Latest self-diagnostic error' (SM0), 'Latest self-diagnostic error' (SM1),
and 'Latest self-diagnostic error code' (SD0) on the master station program. Also, a maximum of 16 error codes for the error
definitions of the errors currently occurring will be stored into 'Self-diagnostic error number 1' (SD10) to 'Self-diagnostic error
number 16' (SD25). (The error codes of the 17th error and later are not stored.)
■Using LED
The error occurrence can be checked through the status of the ERR LED. ( MELSEC iQ-R CC-Link IE Field Network
Remote Head Module User's Manual (Startup))
■Using the engineering tool

The error status for the overall system, error or event history currently being generated can be checked in the module
diagnostics. ( GX Works3 Operating Manual)
• Currently occurring errors: Maximum 16 errors (error definition) currently occurring in the remote head module can be
displayed.*1 However, even when an additional error occurs after a moderate or major error, the error information is not
refreshed.
*1 Maximum number of errors can be displayed differs depending on the error type. (Minor error: 15, Moderate error: 1, Major error: 1)
When 15 minor errors are displayed and a new minor error occurs, description of the new error is not displayed. Also, when an error with
the same code has already been displayed, the date and time of occurrence and detailed information of the relevant error are not
updated.
• Error history: Occurred errors are logged in the event history. ( Page 34 RAS Function)
Operation setting at error detection

Configure each operation setting when an error is detected.
■Mode when an error is detected

The operation when an error is detected by self-diagnostics differs depending on the module parameter of the data link or the
connected module. ( Page 22 Output status for each status)
■Error detection setting

Set whether or not to detect errors in "Error Detections Setting" of "RAS Setting" in "CPU Parameter". ( Page 79 RAS
Setting)
1 FUNCTIONS
30 1.5 RAS Function
■Remote head module operation setting at error detection
Set the operation of the remote head module when an error is detected, in "Remote head Module Operation Setting at Error
Detection" of "RAS Setting" in "CPU Parameter". ( Page 79 RAS Setting) 1
■Remote head module operation setting
Set the operation of the remote head module when an error occurs in each intelligent function module.
[Navigation window]  [Parameter]  [System Parameter]  [I/O Assignment] tab  [I/O Assignment Setting]
Window
Displayed items
Item Description Setting range Default
Remote head Module Set whether to stop or continue the operation of the remote head module Critical: Stop, Moderate: Critical: Stop, Moderate:
Operation Setting at when the major or moderate error is detected in the configured module. Continue Continue
Error Detection When "Stop" is set, the operating status of the remote head module is set to Critical: Stop, Moderate:
the STOP state and the cyclic transmission is stopped. Stop
When "Continue" is set, the operating status of the remote head module is Critical: Continue,
maintained. Moderate: Continue
When the remote head module is in the STOP state, the operation is as
follows.
• The transfer from the link device (RX, RY, RWr, RWw) of the remote head
module to the user device (X, Y, W) is as follows.
The transfer from RY to Y stops. The transfer from RWw to W stops. The
transfer from X to RX continues. The transfer from W to RWr continues.
• The data transfer between the devices in the remote head module stops.
All outputs of the remote head module are turned off.
1 FUNCTIONS
1.5 RAS Function 31
Error clear function
This function clears all the existing errors at once.
Error clear of only specific remote head module

Operate the specific remote head module and clear the errors of the specific remote head module.
■How to clear errors

Errors can be cleared in the following way.
• Using the engineering tool: Clear errors with module diagnostics of GX Works3. ( GX Works3 Operating Manual)
The event history of error clear using the engineering tool is stored in the connected remote head module.
• Using SM/SD: Clear errors by operating SM/SD.
1. Check the detected error with 'Latest self-diagnostic error code' (SD0).
2. Eliminate the cause of the detected error.
3. Turn off and on 'Error reset' (SM50).
■Precautions
Note the following precautions when using the error clear function.
• Since the function clears all of the currently detected errors at once, errors that should not yet be cleared may be cleared.
• Executing this function does not remove the cleared errors from the event history.
• For an error which occurred by a module other than the target remote head module of error clear, the error cause cannot be
eliminated even though the error is cleared using this function. For example, when "Module verification error" (error code:
2400H) or "Module major error" (error code: 2450H) occurred, the error cause cannot be eliminated even though the error
is cleared in the remote head module using this function. To eliminate the error cause, clear the error of the target module
and reset the remote head module.
1 FUNCTIONS
32 1.5 RAS Function
Error clear of all remote head modules
Operate the master station and clear the errors in all the connected remote head modules.
1
This operation clears all the currently occurring errors at once so that none of them can be detected.
■How to clear errors

Errors are cleared in the following way using the master station program or the engineering tool.
1. Eliminate the causes of the errors in the remote head modules.
2. Check that the bit corresponding to each remote head module is 0, using 'Baton pass status of each station' (SW00A0 to
SW00A7) of the master station.
3. Turn on 'Error clear' (SB000F) of remote head module from the master station. When 'Error clear' (SB000F) is turned on,
each remote head module clears the errors and the errors will not be detected.
4. Turn off 'Error clear' (SB000F) of remote head module from the master station. When 'Error clear' (SB000F) is turned off,
each remote head module becomes able to detect the error.
■Precautions
• After the errors are cleared, always turn off 'Error clear' (SB000F).
• Since the function clears all of the currently detected errors at once, errors that should not yet be cleared may be cleared.
• Executing this function does not remove the cleared errors from the event history.
• For an error which occurred by a module other than the target remote head module of error clear, the error cause cannot be
eliminated even though the error is cleared using this function. For example, when "Module verification error" (error code:
2400H) or "Module major error" (error code: 2450H) occurred, the error cause cannot be eliminated even though the error
is cleared in the remote head module using this function. To eliminate the error cause, clear the error of the target module
and reset the remote head module.
1 FUNCTIONS
1.5 RAS Function 33
Event history function
This function collects the event information from each module, such as errors detected by the module and operation
performed to the module, and stores them in the remote head module.*1 Once errors and operations are stored, they can be
checked chronologically.
Using this function enables the following.
• Investigating the cause of defects in the equipment/device
• Checking the control data update status of the own remote head module and the module being managed by the own
remote head module
• Detecting unauthorized access to the own remote head module and the module being managed by the own remote head
module
*1 If the remote head module is operated online using the engineering tool, processing performed automatically by the system may be
stored as an event history.
• The event history is constantly collected regardless of the operating state of the remote head module. There
are occasions, however, when the event history information cannot be collected due to such an error as a
major error in a module and base unit error.
• The remote head module periodically receives clock data from the master station. If the master station is not
connected to the remote head module, the clock data will not be corrected.
• If the remote head module is powered off and on, the clock will restart from the time of the power-off. (The
clock pauses during power-off) Therefore, the time and date of the event that occurred during initial
processing may be different from the actual time and date. Also, the time and date of event occurrence
already saved in the event history cannot be corrected even if clock data is received from the master
station.
• If the remote head module is powered off when the event history is being written to the flash ROM, the time
when the power was turned off may not be correctly written to the flash ROM. When the module is powered
on, if the time when the power was turned off does not exist in the flash ROM, the time is retrieved from the
occurrence date of the final event stored in the event history. If the time could not be retrieved from the
event history, the clock will restart from the initial value (2000/01/01 00:00:00).
• In a redundant system, the clock of the remote head module in the standby system automatically
synchronizes with that of the remote head module in the control system.
1 FUNCTIONS
34 1.5 RAS Function
Storing the event history
This section describes storing of the event history.
1
■Modules from which event history information is collected
Event history information is collected from the remote head module and other modules installed on the same base unit (the
main base unit and extension base units). In the case of the Q series module mounted on the RQ extension base unit, only an
event history with the event type being "System" and the classification being "Warning" is stored.
Events that have occurred in equipment on the network are not collected as event history.
■Events stored in the remote head module

Information stored in the event history includes operation initiator and other detailed information for troubleshooting purposes.
For events that are stored in the event history on the remote head module, refer to the event list. ( Page 129 Event List)
■Event history file

• Storage destination memory: Data memory
• File size: The storage size of an event history file is 128K bytes. If the size exceeds 128K bytes, records are deleted from
the oldest one to store the latest one. An event history file size is obtained from the following calculation formula.
Event history file size = File header size + Event history management information size + (Number of records  Size per event
history record)
Element Size
File header size 20 bytes
Event history management information size 12 bytes
Size per event history record 40 bytes minimum*1
*1 Because the contents of detailed information may differ depending on the event to be stored or the detailed information may include a
variable-length file name, the size per event history record is variable.
The number of events to be saved in the event history file differs depending on the event type to be stored. 3276 events can
be registered for the RUN, STOP, and switch operation of the remote head module. (The size of an event such as changing
the operating status to RUN or STOP is 40 bytes.)
[Calculation formula]
128 bytes  1024 = 131072 bytes
131072 bytes - (20 bytes + 12 bytes) = 131040 bytes
131040 bytes  40 bytes = 3276 events
• File creation timing: File is created when power is turned off and on (when there is no event history file), at the time of reset
(when there is no event history file), and at the time of parameter writing (when there is no event history file).
When a new event history file is created, that operation is logged into the event file as an event history.
The following table shows how the event history is treated depending on operation.
Operation Operation for the event history
Memory initialization When this event occurs, the event history is stored into the data memory. If the maximum number of event history files
storable into the data memory is exceeded, all subsequent event histories will be lost. ( Page 35 Storing the event
history)
Event history creation The event history stored in the data memory before the creation of the event history file is saved in the data memory. (If
any event was lost, it is logged as "*HST LOSS*").
■Loss of event history information

If events are detected frequently, or the power is turned off or reset immediately after event detection, some event histories
may be lost without being collected. When event history loss occurs, "*HST LOSS*" is displayed in the "Event Code" field of
the engineering tool.
1 FUNCTIONS
1.5 RAS Function 35
Viewing the event history
The event history can be viewed using the menu of the engineering tool. For operating procedures and how to interpret the
displayed information, refer to the following:
Clearing the event history

The event history can be cleared in the event history window. Once the event history is cleared, all the event histories in the
data memory are deleted. For operating procedures and other details, refer to the following:
1 FUNCTIONS
36 1.5 RAS Function
Redundant power supply system diagnostic function
This function diagnoses the redundant power supply system where the power supply module is redundant using the 1
redundant power supply base unit.
For the redundant power supply system, refer to the following.
Redundant power supply system diagnostics

■Description
When a redundant power supply is configured, this function checks the following. When an error is detected, a self-diagnostic
error occurs. ( Page 106 Self-diagnostic error code of the remote head module (1000H to 3FFFH))
• The input power supply voltage of power supply module 1 and power supply module 2 is not dropped or is not turned off.
• There is no failure in the power supply module 1 or power supply module 2.
■Diagnostics conditions
Diagnostics is performed only when all the following conditions are satisfied.
• A redundant power supply base unit is used.
• "Detect" is set for "Redundant Power Supply System Error" in "Error Detections Setting" of "RAS Setting" in "CPU
Parameter".
Setting method
Error detection of redundant power supply system is set in "Redundant Power Supply System Error". ( Page 79 RAS
Setting)
[CPU Parameter]  [RAS Setting]  [Error Detections Setting]  [Redundant Power Supply System Error]
When "Not Detected" is set for "Redundant Power Supply System Error", the diagnostics of the redundant
power supply system is not performed. Therefore, even if there is an error on one of the power supply
modules when the redundant power supply base unit is used, the error cannot be detected if the other power
supply module is operating normally.
1 FUNCTIONS
1.5 RAS Function 37
Method for checking information related to the function
The status of the redundant power supply module can be checked with special relay (SM) and special register (SD).
■Special relay
SM number Name
SM150 Power-off/power supply voltage drop detection
SM151 Power supply module failure detection
SM152 Momentary power failure detection (power supply module 1)
SM153 Momentary power failure detection (power supply module 2)
SM154 Invalid power supply module
For details on the special relay (SM), refer to the following.

Page 141 Redundant power supply system
■Special register
SD number Name
SD150 Power-off/power supply voltage drop detection status
SD151 Power supply failure detection status
SD152 Momentary power failure detection count (power supply module 1)
SD153 Momentary power failure detection count (power supply module 2)
SD154 Details of the invalid power supply module
For details on the special register (SD), refer to the following.

Page 153 Redundant power supply system
1 FUNCTIONS
38 1.5 RAS Function
Replacement of the redundant power supply module
This section describes the procedure for replacing the redundant power supply module in the redundant power supply system
1
configuration.
■Preventing detection of error in redundant power supply module

1. Set "Not Detected" in the following.
2. Replace the redundant power supply module.

Since an error is not detected in the redundant power supply system when the redundant power supply module is replaced,
the error in the redundant power supply system do not need to be cleared.
■Detecting error in redundant power supply module

1. Set "Detect" in the following.

3. Clear the error in the redundant power supply system by turning on either 'Error clear' (SM50) of the remote head module
or 'Error clear' (SB000F) of the master station.
■Detecting error in redundant power supply module and preventing detection of error in
normal redundant power supply module
1. Set "Detect" in the following.
2. Turn on 'Error clear' (SB000F) of the master station.

When 'Error clear' (SB000F) of the master station is on, the remote head module does not detect an error in the redundant
power supply module.
4. Turn off 'Error clear' (SB000F) of the master station.
1 FUNCTIONS
1.5 RAS Function 39
1.6 Security Function
This function protects the user property (1) stored inside remote head modules in the MELSEC iQ-R series system from
unauthorized access (including access via the Internet or an intranet), theft, alteration, and faulty operation.
GOT
(1)
Data to be protected Purpose Function Reference

Remote head module To prevent unauthorized read and write of files File password function • GX Works3 Operating Manual
(A password is used.) • MELSEC iQ-R Ethernet User's
Manual (Application)
• SLMP Reference Manual
• MELSEC- iQ-R Serial
Communication Module User's
To limit access to access from a specific communication Remote password function • MELSEC iQ-R Ethernet User's
path via the Ethernet equipped module or serial Manual (Application)
communication module (A password is used.) • MELSEC- iQ-R Serial
Communication Module User's
1 FUNCTIONS
40 1.6 Security Function
1.7 Monitor Function (Current Value Change)
This function changes the value of the remote head module device or the buffer memory of the intelligent function module
1
mounted on the remote head module.
When the CPU module on the master station is in the STOP state, the value of device (Y) on the remote head module side
can be set as on.
The following table lists the output depending on the current value change of device (Y) and operating status of each module.
For the method of current value change, refer to the following.

Remote head module Status of the CPU Current value Output status
status module on the master change of
station device (Y)
RUN RUN ON ON
RUN OFF OFF
(When the master station is performing transmission so that the output
status of device (Y) of the remote head module is turned on, the output
status of device (Y) will not become off even if current value change is
performed from the remote head module.)
STOP RUN ON ON
STOP
RUN OFF OFF
STOP OFF
(If the CPU module of the master station goes into the STOP state, the
remote head module will also go into the STOP state. At this time, if the
master station is performing transmission so that the output status of
device (Y) of the remote head module is turned on, the output status of
device (Y) will not become off even if current value change is performed
from the remote head module.
When the link refresh source of RY of the master station is set to Y, the
master station will not send ON because it will be cleared even if "Hold" is
set for the output status setting for CPU STOP.)
RUN (when disconnected)  ON ON
OFF OFF
STOP (when disconnected)  ON ON
OFF OFF
1 FUNCTIONS
1.7 Monitor Function (Current Value Change) 41
1.8 Redundant Function
This function improves system reliability by making the remote head module redundant so that the remote head module can
continue control even if an error occurs in either of the remote head modules.
In the redundant system described in this manual, continuous operation of the system is not always
guaranteed as this would depend on the failure status.
Also, when the systems are switched because of an error in a module on the base unit in which the remote
head module is mounted, the same error is detected also in the standby system, and the remote head
modules of both systems stop.
Configure safety circuits external to the programmable controller to ensure that the entire system operates
safely even in such a case.
1 FUNCTIONS
42 1.8 Redundant Function
System configuration
This section describes the redundant system configuration of the remote head module. 1
The remote head modules are mounted in the CPU slot and slot No.0 of the main base unit.
The remote head module mounted in the CPU slot is remote head No.1 (1) and the remote head module mounted in the slot
No.0 is remote head No.2 (2).
(1) (2)
When a redundant system is configured, to specify the mounted remote head module, an I/O number is also assigned to the
remote head module. I/O numbers fixed to remote head numbers are assigned as follows:
Remote head number Start I/O number of remote head module
Remote head No.1 3E00H
Remote head No.2 3E10H
• When the remote head module of remote head No.1 is not mounted or has failed, the redundant system will
not start.
• When the remote head module of remote head No.1 has failed and systems have been switched, replace
the remote head module immediately and perform the restoration operation. The redundant system does
not start even if the system is powered off and on or reset while remote head No.1 is in the state of failure.
1 FUNCTIONS
1.8 Redundant Function 43
Single line
In single line, all the stations are connected to a single network line. Two types of single line are available: redundant master
station and redundant slave station.
For the redundant master station, refer to the following.
 MELSEC iQ-R CC-Link IE Field Network User's Manual (Application)
■Redundant slave station

For the redundant slave station, the two remote head modules are connected as redundant remote head module. When an
error occurs in the remote head module of the control system, the control switches to the remote head module of the standby
system to control the slave station and continue the data link.
(1)
(2) (3) (4)
(1) Master station

(2) Local station (control system)
(3) Local station (standby system)
(4) Intelligent device station (The remote head module is redundant with remote head No.1 being the control system and remote head No.2 being the standby
system.)
Redundant line
In redundant line, two network lines are prepared and the remote head module is connected to each network line.
When an error occurs in the network of the control system, the control switches to the network of the standby system to
control the redundant system and continue the data link.
Ensure that the configuration of the network of both systems is the same. For details, refer to the following.
1 FUNCTIONS
Procedures before operation
This section describes the points that must be kept in mind about the operation procedure when a redundant system is 1
configured.
Mounting modules and connecting cables

• Mount the remote head module into the CPU slot and slot No.0 of the main base unit.
• In redundant line, connect the Ethernet cable of system A to remote head No.1 and the Ethernet cable of system B to
remote head No.2.
Setting parameters
Write the same parameters to remote head No.1 and remote head No.2.
When the parameters are write to remote head No.1 only, the parameters are copied automatically by the memory copy
function, however, starting up the remote head module takes some time.
Also, according to the line type set in remote head No.1, the network number and station number of remote head No.2 are
automatically set as follows.
Line type Network number Station number
Single line Same as remote head No.1 Station number of remote head No. + 1
Error occurs in the engineering tool when the station number of remote head No.1 is 120
(maximum value).
Redundant line Same as remote head No.1 Same as remote head No.1
• If the model set in a project is different from the model set in the actual remote head module, the actual
system configuration cannot be read for the module configuration of the engineering tool. Write the
parameters to the remote head module, reset or power off and on the module, set the same model to the
project and actual remote head module, and read the configuration again.
• CPU parameters can be set only in remote head No.1. The CPU parameters of remote head No.2 are
automatically set based on the CPU parameters set in remote head No.1. Therefore, CPU parameters do
not need to be written to remote head No.2 using the engineering tool.
Resetting the remote head module

When the remote head module is redundant with redundant slave station, power on the remote head module before powering
on the master station.
If the master station is powered on before the remote head module is powered on, the actual network configuration and the
network map of the CC-Link IE Field Network diagnostics may be a mismatch.
Network diagnostics
Check the communication status of the remote head modules of both systems for CC-Link IE Field Network diagnostics.
In redundant line, even if the CC-Link IE Field Network diagnostics was performed from the control system master station,
only the communication status of the remote head module of the control system can be displayed. To the communication
status of the remote head module of the standby system, change the connection of the engineering tool to the master station
of the standby system and perform the CC-Link IE Field Network diagnostics.
1 FUNCTIONS
System switching operation
The send range of cyclic transmission of both systems is as follows:
• The own station send range of the link devices (RY, RWw) of both systems is the same due to pairing.
• The remote head module of the control system sends and receives cyclic data.
• The remote head module of the standby system only receives cyclic data.
When an error occurs in the control system, the control switches to the standby system to continue the system operations.
This section describes the system switching operation of the remote head module for the redundant slave station with single
line.
For the system switching operation when the remote head module is redundant with single line and redundant master station,
or with redundant line, refer to the following.
Before system switching operation

The remote head module of the control system performs I/O refresh with the module on the base unit.
The remote head module of the standby system receives data from the master station and inputs from the module on the base
unit. However, it does not send data to the master station and does not output to a module on the base unit.
Each number in the figure, from No.0 to No.2, represents a station number.
No.0 No.1 No.2 No.3
Master station Remote head module Remote head module I/O module Remote head module
(control system) (standby system)
RX, RWr RX, RWr RX, RWr

Ó
No.1, 2 No.1, 2 No.1, 2
Õ RX, RWr
No.3 No.3
RY, RWw RY, RWw RY, RWw

Ô
No.1, 2 No.1, 2 No.1, 2
Ö RY, RWw
No.3 No.3
: Send range of station No.

: Send data from the master station
: Send data from the slave station
: Send and receive data of external device
 The redundant remote head modules have serialized station numbers. Based on the pairing setting of the master station, the devices (RX, RY, RWr, RWw)
of both stations are set as identical.
 Only the control system sends data to the master station.
 Both the control system and the standby system receive data from the master station.
 Both the control system and standby system perform input from the I/O module.
 Only the control system performs output to the I/O module.
1 FUNCTIONS
After system switching operation
The new control system performs I/O refresh with a module on the base unit.
1
Send data is passed to the new control system when systems are switched to continue cyclic transmission.
Each number in the figure, from No.0 to No.2, represents a station number.
No.0 No.1 No.2 No.3
Master station Remote head module Remote head module I/O module Remote head module
(standby system) (control system)
RX, RWr RX, RWr RX, RWr
No.1, 2 No.1, 2 No.1, 2

RX, RWr
No.3 No.3
RY, RWw RY, RWw RY, RWw
No.1, 2 No.1, 2 No.1, 2

RY, RWw
No.3 No.3
: Send range of station No.

: Send data from the master station
: Send data from the slave station
: Send and receive data of external device
 The devices (RX, RY, RWr, RWw) of both stations in the master station are set as identical even after systems are switched.
1 FUNCTIONS
Determining control system and standby system
The control system and standby system of the remote head modules are determined either in order of system power supply
startup or remote head module reset clear.
Single line
This section describes the system determination for when the remote head module is redundant with single line and
redundant slave station.
After the system starts, the CTRL LED of the remote head module of the control system and the SBY LED of the remote head
module of the standby system turn on.
■When the system starts by turning the power on

Remote head No.1 will be the control system and remote head No.2 will be the standby system.
• When remote head No.2 is the control system and the power is turned off and on, remote head No.1
switches to the control system and remote head No.2 switches to the standby system.
• When only remote head No.1 is mounted or remote head No.2 has failed, remote head No.1 will be the
control system.
• When only remote head No.2 is mounted or remote head No.1 has failed, the system does not start. To start
the system, remote head No.1 must be replaced, or remote head No.2 must be mounted in the CPU slot.
■When the system starts by resetting the remote head module of the control system
Only the remote head module of the control system is reset, and system switching occurs.
After reset clear, the reset remote head module will be the standby system.
• When only remote head No.1 is mounted or remote head No.2 has failed, the entire system is reset.
• When remote head No.2 is reset and remote head No.1 has failed, the entire system is reset. However,
after reset clear, the system does not start. To start the system, remote head No.1 must be replaced, or
remote head No.2 must be mounted in the CPU slot.
■When the system starts by resetting the remote head module of the standby system
Only the remote head module of the standby system is reset.
After reset clear, the reset remote head module will be the standby system.
■When the system starts by simultaneously resetting the remote head modules of both
systems or by performing remote reset operation
The entire system is reset.
After reset clear, remote head No.1 will be the control system, and remote head No.2 will be the standby system.
Remote reset operation can be performed only on the remote head module of the control system.
■When the system starts after the remote head module of the standby system is replaced
The replaced remote head module will be the standby system.
The remote head module of the control system will remain as the control system.
Replacement of the remote head module can be performed only on the remote head module of the standby
system.
For the replacement procedure, refer to the following.
Page 100 For the standby system in a redundant system configuration
1 FUNCTIONS
Redundant line
In redundant line configuration, the control system and standby system of the remote head module are determined by tracking
1
the master station.
■When the system starts by turning the power on

The control system and standby system are determined by tracking the master station.
• In the interval after the system starts by power-on till the control system and standby system are determined
by tracking the system status of the master station, remote head No.1 will be the control system and remote
head No.2 will be standby system.
• If the remote head modules are not connected with the master station, the control system and the standby
system are determined by tracking the system status of the master station when the modules are connected
with the master station.
• If the files of both systems are mismatch, memory copy operation is performed for remote head No.2
(standby system) from remote head No.1 (control system). After memory copy operation completes, the
control system and the standby system are determined by tracking the system status of the master station.
• When only remote head No.2 is mounted or remote head No.1 has failed, the system does not start. To start
the system, remote head No.1 must be replaced, or remote head No.2 must be mounted in the CPU slot.
■When the system starts by resetting the remote head module of the control system
Only the remote head module of the control system is reset.
The redundant master station system detects a reset of the remote head module of the control system, and systems are
switched.
By tracking the system switching of the redundant master station system, the remote head module of the standby system will
become the control system.
After reset clear, the reset remote head module will be the standby system by tracking the system status of the master station.
• When only remote head No.1 is mounted or remote head No.2 has failed, the entire system is reset. After
reset clear, the reset remote head module will be the control system by tracking the system status of the
master station.
■When the system starts by resetting the remote head module of the standby system
Only the remote head module of the standby system is reset.
After reset clear, the reset remote head module will be the standby system by tracking the system status of the master station.
• When only remote head No.1 is mounted or remote head No.2 has failed, the entire system is reset. After
reset clear, the reset remote head module will be the standby system by tracking the system status of the
master station.
1 FUNCTIONS
■When the system starts by simultaneously resetting the remote head modules of both
systems or by performing remote reset operation
The entire system is reset.
After reset clear, the control system and standby system are determined by tracking the master station.
Remote reset operation can be performed only on the remote head module of the control system.
■When the system starts after the remote head module of the standby system is replaced
The replaced remote head module will be the standby system by tracking the system status of the master station.
Replacement of the remote head module can be performed only on the remote head module of the standby
system.
For the replacement procedure, refer to the following.
Page 100 For the standby system in a redundant system configuration
1 FUNCTIONS
System consistency check and operations when an error occurs
When the redundant function is used, for control of the system to continue when systems are switched, the files and operating 1
statuses of the remote head modules of the control system and standby system must be the same.
The system consistency check checks whether the files and operating status of the remote head module of the standby
system are the same as those of the control system.
Check item
The following table lists the check items for the system consistency check.
Check item Description
File The parameters and device initial values are checked.
Operating status The operating status (RUN state/STOP state) of the remote head module is
checked.
Execution conditions
The following table lists the execution conditions for the system consistency check.
: Executed, : Not executed
Execution conditions*1 Check item
Execution timing Operating status of the Operating status of the Files*2 Operating
standby system control system status
Power-on    
When reset is cleared in the control system or    
the standby system
When the standby system is connected    
When operating status changes RUN RUN *3 
STOP  
STOP RUN or STOP  
STOP  RUN RUN  
STOP  
Reset clear RUN  
STOP  
*1 This function is not executed on a condition not mentioned in the table.

*2 Depending on the execution timing, some file types are not treated as system consistency check targets. ( Page 52 Target file)
*3 Only at the time of system switching, the system consistency check is executed.
1 FUNCTIONS
System consistency check of files
The files for operating the redundant system are checked.
■Target file
The following is a list of files to be checked for system consistency.
Target file
CPU parameter
System parameter
Module parameter
Module extension parameter*1
Device comment*2
Global label setting file
Initial global label value file
Remote password
*1 Only the parameter files of the mounted modules are checked. A module for which "Module Status Setting (Empty)" is selected in the
"Module Configuration" window of the engineering tool is not treated as a check target.
*2 Only files with the name COMMENT.DCM are checked for system consistency.
■Operations when a mismatch is occurred

After the memory copy is executed from the control system to the standby system, the standby system is automatically reset
and restarted.
System consistency check of operating status

Because the same operations cannot continue after system switching if the operating statuses of the remote head modules of
both systems are not the same, whether the operating statuses (RUN state/STOP state) match is checked.
■Description
Whether the operating statuses of the remote head modules (RUN state/STOP state) are the same is checked.
■Operations when a mismatch is occurred

When the operating statuses (RUN state/STOP state) do not match, system switching is not be possible.
The CTRL LED of the remote head module flashes because system switching is not possible.
Match the operating statuses of both systems (RUN state/STOP state). ( Page 91 When the CTRL LED is flashing)
1 FUNCTIONS
System switching function
This section describes how to switch systems when a redundant system is operating, whether or not the system switching can 1
be executed, operations after the cause of failure to switch systems is eliminated, and how to check information on system
switching.
For calculation method of the time required for system switching, refer to the following.
Page 166 System switching time
System switching method

Two types of system switching of the remote head module are available: Automatic system switching (switching automatically
performed by the redundant system) and manual system switching (switching that can be arbitrarily performed).
Line type System System switching cause Order of priority
switching
method
Single line Automatic Reset or hardware failure High 1
system switching 
Moderate error or major error 2

Data link error Low 3
Manual system System switching operation using the engineering tool 4
switching
Redundant Automatic Tracking of system switching of redundant master station system 
line system switching
When multiple simultaneous system switching requests occur, system switching is performed in descending order of priority of
switching causes.
In single line
■System switching due to reset or hardware failure
If the remote head module of the control system is in any of the following state and the redundant system goes out of control,
the remote head module of the standby system switches to the control system to continue the control of the redundant
system.
• The remote head module is reset.
• Hardware failure has occurred
(1)
(4)
(2) (3)
(1) Master station

(2) Control system  New standby system
(3) Standby system  New control system
(4) System switching (Resetting of control system or hardware failure has occurred.)
1 FUNCTIONS
■System switching due to moderate error or major error
When either a moderate or major error occurs in the remote head module of the control system, the remote head module of
the standby system switches to the control system. The remote head module of the control system where the moderate or
major error has occurred switches to the standby system.
However, depending on the content of the major error, the remote head module of the control system may not switch to the
standby system.
(1)
(4)
(2) (3)
(1) Master station

(4) System switching (A moderate or major error has occurred in the control system.)
■System switching due to data link error

When the data link of the remote head module of the control system continues to be in an error state (D LINK LED is either off
or flashes) for the system switching monitoring time set in the master station or longer, the remote head module of the standby
system switches to the control system. The remote head module of the control system where the data link error has occurred
switches to the standby system.
(1)
(4)
(2) (3)
(1) Master station

(4) System switching (The data link continues to be in an error state for the system switching monitoring time or longer.)
System switching does not occur if a data link error occurs due to any of following at power-on.
• No Ethernet cable is connected to the remote head module of the control system.
• An Ethernet cable connected to the remote head module of the control system is disconnected.
■System switching operation from the engineering tool

For how to operate engineering tools, refer to the following.
The system switching operation using the engineering tool can be performed only from the remote head module of the control
system.
Also, to perform system switching operation using the engineering tool, 'System switching by a user' (SM1646) must be kept
on (permitting manual switching) beforehand.
1 FUNCTIONS
In redundant line
■Tracking of system switching of the master station 1
By tracking the system switching of the master station, systems of the remote head module are switched.
For system switching of the master station, refer to the following.
Conditions of system switching

The following table lists the conditions of system switching.
: System switching enabled, : System switching disabled
System switching condition Single line Redundant line
Automatic system switching Manual system Automatic
switching system
switching
Reset or Moderate error Data link error System System
hardware failure or major error switching switching of
operation using redundant
the engineering master station
tool system
Normal or minor error (standby system)     
(Always tracks the
Moderate error or major error (standby    
system)*1 system state of the
master station.)
Error detected in network (standby system)*1    
Memory copy being executed from the    
control system to the standby system*1
Mismatch between operating statuses of    
both systems*1
System switching being executed*1    
*1 When system switching is not possible, the CTRL LED of the remote head module of the control system flashes.
• When even one of the conditions for system switching disabled is satisfied, system switching is not
executed.
• In case an operation or phenomenon not mentioned in the table occurs, system switching is not performed.
1 FUNCTIONS
Operations after the cause of failure to switch systems is eliminated
In a single line configuration, after systems have failed to be switched, if the cause of failure in the system switching of the
remote head module of the standby system is eliminated, systems may be switched.
■Standby system is reset or hardware failure

The following table lists cases in which systems fail to be switched because the standby system is reset or a hardware failure
occurs.
System System switching cause of System status before Status after resetting remote head No.2 after eliminating
switching control system and after the system the cause of failure to switch systems
method switching cause occurs
Automatic Moderate error or major error*1 Remote head No.1: Control Remote head No.1: Control system
system system  Control system Remote head No.2: Standby system
switching Remote head No.2: Standby Since remote head No.1 is the control system, remote head No.2 starts
system   as the standby system.
Reset or hardware failure Remote head No.1: Control Remote head No.1: 
system   Remote head No.2: 
Remote head No.2: Standby Systems do not start.
system  
Data link error Remote head No.1: Control Remote head No.1: Control system
system  Control system Remote head No.2: Standby system
Remote head No.2: Standby Since remote head No.1 is normal, remote head No.2 starts as the
system   standby system.
Manual System switching operation using Remote head No.1: Control Remote head No.1: Control system
system the engineering tool system  Control system Remote head No.2: Standby system
switching Remote head No.2: Standby Since remote head No.1 is normal, remote head No.2 starts as the
system   standby system.
*1 Depending on the content of the major error, the remote head module of the control system may not switch to the standby system.
■Moderate error or major error in the standby system

The following table lists cases in which systems fail to be switched due to a moderate or major error in the standby system.
System System switching cause of System status before Status after powering off and on remote head No.2 after
switching control system and after the system eliminating the cause of failure to switch systems
Automatic Moderate error or major error*1 Remote head No.1: Control Remote head No.1: Control system
system system  Control system Remote head No.2: Standby system
switching Remote head No.2: Standby Since remote head No.1 is the control system, remote head No.2 starts
system  Standby system as the standby system.
system  Control system
system  Standby system standby system.
1 FUNCTIONS
■Data link error of the standby system
The following table lists cases in which systems fail to be switched due to a data link error in the standby system.
System System switching cause of System status before Status after powering off and on remote head No.2 after 1
switching control system and after the system eliminating the cause of failure to switch systems
Automatic Moderate error or major error*1 Remote head No.1: Control Remote head No.1: 
system system  Standby system Remote head No.2: Control system
switching Remote head No.2: Standby Since remote head No.1 is faulty, remote head No.2 starts as the
system  Control system control system.
system  Control system
1 FUNCTIONS
Check method of information on system switching
This section describes how to check information on system switching when systems are switched.
When automatic system switching or manual system switching is performed, information on the system switching event can
be checked in the following ways.
Check method Information
Special register (SD) Result of system switching and detailed information on system switching
CTRL LED and SBY LED of the remote head module Result of system switching
Event history Result and cause of system switching, transition state of the systems
■Special register
The result of system switching and detailed information on system switching can be checked using the special register.
• Whether systems have been switched can be checked by checking 'System switching cause (when the systems are
successfully switched)' (SD1649). When system switching occurs, the system switching cause is stored in 'System
switching cause (when the systems are successfully switched)' (SD1649) of the control system and standby system each.
• When systems fail to be switched even though the system switching cause has occurred, the cause of failure in system
switching is stored in 'Cause of system switching failure' (SD1644).
The following table lists the special register related to system switching and whether to set or not each register in the remote
head module of new control system and new standby system each.
: Set, : Not set
SD number Name Whether to set or not at the time of system switching
New control system New standby system
SD1643 System switching cause  
SD1644 Cause of system switching failure  
SD1648 Cause of the other system monitoring error  
SD1649 System switching cause (when the systems are  
successfully switched)
SD1681 Latest self-diagnostic error code (the other  
system)
For details on the special register (SD), refer to the following.

Page 148 List of Special Register (SD) Areas
■CTRL LED and SBY LED of the remote head module

The following table lists the LED indication when system switching is completed successfully by a system switching cause.
Item When system switched from the control system to the When system switched from the standby system to the
standby system control system
CTRL LED On  Off Off  On (When system switching is enabled in standby system)
Off  Flashing (When system switching is disabled in standby system)
SBY LED Off  On On  Off
The following table lists the LED indication when system switching is not completed successfully by a cause of system
switching failure
Item Control system Standby system
CTRL LED On or flashes*1 Off
SBY LED Off On
*1 This LED flashes when system switching is disabled in the standby system.
■Event history
Information on the system switching cause, the result of system switching, and the transition state of the systems (control
system and standby system) can be checked in the event history of the engineering tool.
The following items are stored in the event histories of both systems when systems are switched.
• When systems are switched due to automatic system switching: "System switching (system)" (event code: 00F00)
• When systems are switched due to manual system switching: "System switching (user)" (event code: 2B000)
For details on the event history, refer to the following.
Page 129 Event List
1 FUNCTIONS
Memory copy function from control system to standby system
This function transfers data such as parameters of the remote head module of control system to the remote head module of 1
standby system to match the remote head module of the control system.
Memory copy is not executed from the standby system to the control system. Also, when memory copy is completed
successfully, the event history is stored in the remote head module.
Files copied by the memory copy function

The memory copy function copies files required for starting a redundant system.
The following table lists the files to be copied by the memory copy function.
: Memory copy possible, : Memory copy not possible, : Storage not possible
File type Copy
Remote head module built-in memory
Device/label memory Data memory
CPU parameter  
System parameter  
Module parameter  
Module extension parameter  
Device comment  
Global label setting file  
Initial label value file Initial global label value file  
Event history  
Device data storage file  
General-purpose data  
Remote password  
When the memory copy is executed, files are copied after the memory of the remote head module of the
standby system that has differences is initialized.
The memory copy cannot be executed to the files such as event history and those files are deleted from the
memory of the standby system remote head module. Back up the files before executing the memory copy as
required.
Execution method of memory copy

When a file mismatch is detected by system consistency check in any of the following timings, memory copy is automatically
executed.
• Power-on (Irrespective of the system status when the system started previously, memory copy from remote head No.1 to
remote head No.2 is performed.)
• Reset clear of remote head module of the control system or standby system
• Replacement of remote head module of the standby system
Execution conditions of memory copy

The memory copy function can be executed irrespective of the operating status of the remote head module of the control
system and standby system.
However, memory copy is not executed in the following cases.
• When memory is being formatted
• When data is being written to the remote head module of control system
1 FUNCTIONS
Operations when memory copy is executed
The operations when memory copy is executed is explained using an example when power is turned off and on.
1. Powering off and on the system.
2. When a file mismatch is detected by system consistency check, the ERR LED of the standby system flashes. Also, the
CTRL LED of the control system flashes to indicate the system switching disable state.
3. The SBY LED of the standby system flashes, and memory copy automatically starts.
4. After the memory copy operation is completed successfully, the standby system is automatically reset.
When the memory copy operation fails, the standby system will not be reset.
The SBY LED of the standby system turns off to indicate that the memory copy operation has been completed with an error.
Also, the CTRL LED of the control system flashes to indicate the system switching disable state.
5. After the standby system restarts, the CTRL LED of the control system and the SBY LED of the standby system turn on.
Precautions
When an error occurs while memory copy is being executed, the remote head module of the standby system will not perform
memory copy correctly, and that leads to a moderate error.
While memory copy is being executed, the following operations cannot be performed from the engineering tool for the remote
head module of the control system or the standby system.
• CPU memory operation
• Writing data to the programmable controller
• Deleting data from the programmable controller
• System switching
1 FUNCTIONS
Functions restricted in a redundant system
The following table lists the functions restricted when using the remote head module in a redundant system. 1
Function Restrictions
Remote operation Remote RESET Only when this operation is performed on the remote head module of the control system, the entire system is
reset. However, depending on the status of the remote head module, remote RESET may not be performed.
■When there is an error in remote head No.1 or remote head No.2
• When only remote head No.2 is mounted: The system is not reset.
• When a major error occurs in remote head No.1 or remote head No.2, the system on both of remote head No.1
and remote head No.2 is not reset.
(When only remote head No.1 is mounted, the system is reset.)
■When the remote head modules of both systems are not in the STOP state
When the remote head module of the control system is in the STOP state and the remote head module of the
standby system is in the RUN state, the remote head module of the control system and the standby system cannot
be reset by performing the remote RESET operation on the remote head module of the control system. Perform
the remote RESET operation after setting the remote head modules of both systems to the STOP state.
■When a remote operation is performed on the remote head modules of both systems via different routes
When a remote operation is performed on the remote head module of the control system and the standby system
via different routes, the remote head module of the control system and the standby system cannot be reset by
performing the remote RESET operation on the remote head module of the control system. To perform a remote
RESET operation on the remote head module of the control system, cancel the remote operation on the remote
head module of the standby system before performing the remote RESET operation.
RAS function Event history Events related to system switching are stored in the remote head modules of both systems, but events that have
function occurred in one of the remote head modules are stored only in that remote head module. Also, events that have
occurred in a module on the base unit are stored only in the remote head module of the control system.
Only the events stored in individual remote head modules can be cleared/displayed.
Monitor function Device/buffer The execution result of the current value change executed in the control system for the devices of remote head
memory batch module is not reflected in the new control system even if systems are switched.
monitor Connect the engineering tool to the new control system and re-execute the current value change.
Synchronization CC-Link IE Field Cannot be used.
function Network
synchronous
communication
function
Inter-module
synchronization
function
SLMP communication function • When systems are switched during communication, since neither the remote head module of the control system
MC protocol communications function prior to system switching nor that of the new control system can send a response and a response wait timeout
occurs, a retry from the communication equipment is required. However, for the RJ71C24, depending on the
response monitoring time setting, a response wait timeout may not occur.
• In SLMP (MC protocol) communications using the remote head module, when performing communications to
the other system in a state where the other system cannot respond (such as reset and disconnection of Ethernet
cables), a timeout error may occur.
1 FUNCTIONS
Setting example
This section describes the settings for when the remote head module is redundant with single line and redundant slave
station.
For the setting examples of redundant master station and redundant local station with single line, and the setting example of
redundant line, refer to the following.
System configuration example
Setting in the master station

Connect the engineering tool to the CPU module on the master station and set parameters.
1. Set the CPU module as follows.

[Project]  [New]
2. Click the [OK] button to add the module labels of the CPU module.
1 FUNCTIONS
3. Set the master/local module for slot No.0 in the I/O assignment setting.
1
4. Click the [OK] button to add the module labels of the master/local module.
5. Set the network topology as follows.

[Navigation window]  [Parameter]  [Module Information]  [RJ71GF11-T2]  [Basic Settings]  [Network Topology]
1 FUNCTIONS
6. Set the network configuration as follows.
[Navigation window]  [Parameter]  [Module Information]  [RJ71GF11-T2]  [Basic Settings]  [Network
Configuration Settings]
7. Set the refresh settings as follows.

[Navigation window]  [Parameter]  [Module Information]  [RJ71GF11-T2]  [Basic Settings]  [Refresh Settings]
8. Write the set parameters to the CPU module on the master station. Then reset the CPU module or power off and on the
system.
[Online]  [Write to PLC]
In this setting example, default settings are used for the parameters other than those described. For the
parameters, refer to the following.
1 FUNCTIONS
Settings in the slave station
Connect the engineering tool to the remote head module of remote head No.1 and set parameters.
1
In a redundant system, also write the same parameters to remote head No.2.
1. Set the remote head module as follows.
[Project]  [New]
2. Set the remote head No.2 remote head module for slot No.0 in the I/O assignment setting.
3. Set the items in "Network Required Setting" of "CPU Parameter" as follows.

[Navigation window]  [Parameter]  [RJ72GF15-T2 (SR)]  [CPU Parameter]  [Network Required Setting]
4. Set the module parameter of the module mounted on the remote head module. ( Manual for the module used)
5. Write the set parameters to the remote head No.1 and remote head No.2 remote head modules, and reset or powering
off and on the remote head No.1 and remote head No.2 remote head modules.
In this setting example, default settings are used for the parameters other than those described. For the
parameter setting, refer to following. ( Page 76 PARAMETER SETTINGS)
1 FUNCTIONS
1.9 Safety Communication Relay Function
This function relays safety communications between the SIL2 Process CPU included in the master station and the module set
to the SIL2 mode included in the remote head module.
System configuration
This section describes the system configuration of the safety communication relay function.
The system of the safety communication relay function is configured as described below.
System configuration Description
Redundant master station The master station is configured in a redundant system.
Redundant line Each of the control system and standby system is configured on a different
network to make the network line redundant.
Redundant master station

The system of the redundant master station is configured as shown below.
(1) (2) (3) (4) (1) (2) (3) (4)
(5) (6)
(1)SIL2 Process CPU

(2)SIL2 function module
(3)Redundant function module
(4)RJ71GF11-T2
(5)Remote head module
(6)Module set to SIL2 mode
For the redundant master station, refer to the following.

1 FUNCTIONS
66 1.9 Safety Communication Relay Function
Redundant line
The system of the redundant line is configured as shown below.
1
(1) (2) (3) (4) (1) (2) (3) (4)
(5)
(6)
(1)SIL2 Process CPU

(2)SIL2 function module
(3)Redundant function module
(4)RJ71GF11-T2
(5)Remote head module
(6)Module set to SIL2 mode
For the redundant line, refer to the following.

1 FUNCTIONS
1.9 Safety Communication Relay Function 67
Procedures before operation
This section describes the procedures to configure the system of the safety communication relay function before operation.
Mounting procedures
1. Installation of batteries
Install batteries to the SIL2 Process CPU of both systems. ( MELSEC iQ-R CPU Module User's Manual (Startup))
2. Installation of an extended SRAM cassette or an SD memory card
Install an extended SRAM cassette or SD memory card to the SIL2 Process CPU of both systems as necessary. (
MELSEC iQ-R CPU Module User's Manual (Startup))
During access to the SD memory card, do not turn off the power, reset, or remove the SD memory card. ( MELSEC iQ-R
CPU Module User's Manual (Application))
3. Mounting of the module
Mount each module on the base unit. ( MELSEC iQ-R Module Configuration Manual)
Wiring procedures
1. Wiring
Connect each module and external devices.
Wiring location Reference
Wiring for the power supply module  MELSEC iQ-R Module Configuration Manual
Wiring for the redundant function module  MELSEC iQ-R CPU Module User's Manual (Application)
Wiring from the RJ71GF11-T2 to the remote head module •  MELSEC iQ-R Ethernet/CC-Link IE User's Manual (Startup)
•  MELSEC iQ-R CC-Link IE Field Network Remote Head Module User's
Manual (Startup)
Wiring for the I/O module  Manual for the I/O module used
Procedures for the remote head module

1. Power-on of the system
Before turning on the power, check the following items.
• The power supply is connected properly.
• The power supply voltage meets the specifications.
• The remote head module is in the STOP state.
2. Creation of a project
Start the engineering tool and create a project. ( MELSEC iQ-R CC-Link IE Field Network Remote Head Module User's
Manual (Startup))
3. Connection between a personal computer and the remote head module
Connect a personal computer with the engineering tool installed to the remote head module. ( MELSEC iQ-R CC-Link IE
Field Network Remote Head Module User's Manual (Startup))
4. Initialization of the remote head module

Initialize the remote head module using the engineering tool. ( MELSEC iQ-R CC-Link IE Field Network Remote Head
Module User's Manual (Startup))
5. Parameter setting of the remote head module
Set the system parameters, CPU parameters, and module parameters of each module. ( MELSEC iQ-R CC-Link IE Field
Network Remote Head Module User's Manual (Application))
• Setting of the system parameters and the CPU parameters
• Setting of the module parameters of each module
1 FUNCTIONS
6. Writing to the remote head module
Write the parameters set by the engineering tool to the remote head module. ( MELSEC iQ-R CC-Link IE Field Network
Remote Head Module User's Manual (Startup)) 1
7. Reset of the remote head module
Restart the system of the remote head module using either of the following methods.
• Turning off and on the power.
• Resetting the remote head module ( MELSEC iQ-R CC-Link IE Field Network Remote Head Module User's Manual
(Startup))
Procedures for the SIL2 Process CPU

1. Power-on of the system
Before turning on the power, check the following items for both systems.
• The power supply is connected properly.
• The power supply voltage meets the specifications.
• The SIL2 Process CPU is in the STOP state.
After turning on the power, check that the following LEDs are turned on.
• Power supply module: POWER LED
• SIL2 Process CPU: READY LED
• SIL2 function module: READY LED
• Redundant function module: RUN LED
• RJ71GF11-T2: RUN LED
Although the LED on each module will be in the following state, proceed to the next step.
• SIL2 Process CPU: ERROR LED flashes.
• SIL2 function module: ERROR LED flashes.
• Redundant function module: ERR LED turns on.
• RJ71GF11-T2: ERR LED turns on.
2. Creation of a project
Start the engineering tool and create a project. ( MELSEC iQ-R CPU Module User's Manual (Application))
3. Connection between a personal computer and the SIL2 Process CPU
Connect a personal computer with the engineering tool installed to the SIL2 Process CPU. ( MELSEC iQ-R CPU Module
User's Manual (Application))
4. Initialization of the SIL2 Process CPU
Initialize the SIL2 Process CPU using the engineering tool.
After initializing one SIL2 Process CPU, connect the other SIL2 Process CPU to the personal computer. After the connection,
initialize the SIL2 Process CPU using the engineering tool.
5. Parameter setting for the SIL2 Process CPU
Set the system parameters, CPU parameters, and module parameters of each module. ( MELSEC iQ-R CC-Link IE Field
Network User's Manual (Application))
The system parameters can be set by loading the actual system configuration into the module configuration
diagram using the engineering tool.
6. Safety communication setting

Set the safety communication. ( MELSEC iQ-R CC-Link IE Field Network User's Manual (Application))
7. Writing of the system A/B setting

Set the system A/B setting using the engineering tool. ( MELSEC iQ-R CPU Module User's Manual (Application))
1 FUNCTIONS
8. User information setting
Set the user information for the SIL2 Process CPU and the project of both systems. ( GX Works3 Operating Manual)
9. Creation of a program
Create a safety program and a standard program.
10. Writing of data to the programmable controller
Write the parameters set by the engineering tool and the programs created above to both systems. ( MELSEC iQ-R CPU
Module User's Manual (Application))
11. Reset of the SIL2 Process CPU
Restart both systems by either of the following methods.
• Turning off and on the power.
• Reset of the SIL2 Process CPU
12. Check of the LED on the SIL2 Process CPU
Check that the LED on each module is in the following state. The CARD READY LED turns on or off according to whether an
SD memory card has been installed or not.
• Control system
• Standby system*1
*1 The MST LED on the standby system RJ71GF11-T2 flashes in a redundant master station system.
The following LEDs turn on in the event of an error. Check the details of the error using the engineering tool, and eliminate the
error cause.
• SIL2 Process CPU: ERROR LED ( MELSEC iQ-R CPU Module User's Manual (Startup))
• SIL2 function module: ERROR LED ( MELSEC iQ-R CPU Module User's Manual (Startup))
• Redundant function module: ERR LED, L ERR LED ( MELSEC iQ-R CPU Module User's Manual (Startup))
• RJ71GF11-T2: ERR LED, L ERR LED ( MELSEC iQ-R Ethernet/CC-Link IE User's Manual (Startup))
1 FUNCTIONS
Validation of the module
1. Safety module operation
1
Check that systems of the SIL2 Process CPU and the remote head module are powered on, and validate the module set to
the SIL2 mode by "Safety Module Operation" of the engineering tool. ( MELSEC iQ-R CC-Link IE Field Network User's
Manual (Application))
2. Power-off of the system
After validation, power off the systems for the SIL2 Process CPU and the remote head module.
3. Restart of the SIL2 Process CPU and the remote head module
Set the RUN/STOP/RESET switch on the SIL2 Process CPU and remote head module of both systems to the RUN position,
and turn on the power.
1 FUNCTIONS
Procedures for operation check
1. Various check
Check the status of the modules and the operation of the programs used in the system.
• Check that no errors have occurred in each module.
• Check that the status of the LED on each module is as follows.
• Control system
• Standby system*1
• Remote head module*2*3
*1 The MST LED on the standby system RJ71GF11-T2 flashes in a redundant master station system.
*2 In the redundant master station system, these LEDs are always off because the remote head module is not redundant.
CTRL LED
SBY LED
*3 The above illustrations show an example of the input module with diagnostic functions. For LEDs on other modules, refer to the manual
for the module used.
• Is an error detected in the CC-Link IE Field Network diagnostics? ( MELSEC iQ-R CC-Link IE Field Network User's
Manual (Application))
• Check that the safety program and the standard program operate properly.
2. Switching of the safety operation mode
Switch the safety operation mode to the SAFETY MODE to operate the system using the SIL2 Process CPU normally. (
MELSEC iQ-R CPU Module User's Manual (Application))
When the CPU module is set to the STOP state, the continuation error of the operating status mismatch is
detected in the standby system.
1 FUNCTIONS
3. Execution of the program
Power off the SIL2 Process CPU and remote head module of both systems. Then, set the RUN/STOP/RESET switch on the
SIL2 Process CPU and remote head module of both systems to the RUN position, and turn on the power. Check that the 1
PROGRAM RUN LED on the CPU module in the control system turns on.
When the RUN/STOP/RESET switch is set to the RUN position while the power is turned on, the continuation
error of the operating status mismatch is detected in the standby system.
4. Monitoring of the program

Check that the program is operating properly using the engineering tool.
1 FUNCTIONS
Restricted functions
The following table lists the functions restricted when the remote head module is used in a system of the safety
communication relay function.
Function Restrictions
Remote operation Remote RESET Only when this operation is performed on the remote head module of the control system, the entire system is
reset. However, depending on the status of the remote head module, remote RESET may not be performed.
■When there is an error in remote head No.1 or remote head No.2
• When only remote head No.2 is mounted: The system is not reset.
• When a major error occurs in remote head No.1 or remote head No.2, the system on both of remote head No.1
and remote head No.2 is not reset.
(When only remote head No.1 is mounted, the system is reset.)
■When the remote head modules of both systems are not in the STOP state
When the remote head module of the control system is in the STOP state and the remote head module of the
standby system is in the RUN state, the remote head module of the control system and the standby system cannot
be reset by performing the remote RESET operation on the remote head module of the control system. Perform
the remote RESET operation after setting the remote head modules of both systems to the STOP state.
■When a remote operation is performed on the remote head modules of both systems via different routes
When a remote operation is performed on the remote head module of the control system and the standby system
via different routes, the remote head module of the control system and the standby system cannot be reset by
performing the remote RESET operation on the remote head module of the control system. To perform a remote
RESET operation on the remote head module of the control system, cancel the remote operation on the remote
head module of the standby system before performing the remote RESET operation.
RAS function Event history Events related to system switching are stored in the remote head modules of both systems, but events that have
function occurred in one of the remote head modules are stored only in that remote head module. Also, events that have
occurred in a module on the base unit are stored only in the remote head module of the control system.
Only the events stored in individual remote head modules can be cleared/displayed.
Monitor function Device/buffer The execution result of the current value change executed in the control system for the devices of remote head
memory batch module is not reflected in the new control system even if systems are switched.
monitor Connect the engineering tool to the new control system and re-execute the current value change.
Synchronization CC-Link IE Field Cannot be used.
function Network
synchronous
communication
function
Inter-module
synchronization
function
SLMP communication function • When systems are switched during communication, since neither the remote head module of the control system
MC protocol communications function prior to system switching nor that of the new control system can send a response and a response wait timeout
occurs, a retry from the communication equipment is required.
• In SLMP (MC protocol) communications using the remote head module, when communication is made to the
other system while the other system cannot respond (because of being reset, disconnection of Ethernet cables,
or other causes), a timeout error may occur.
Setting example
For a setting example, refer to the following.
1 FUNCTIONS
Precautions
1
When the momentary power failure occurs
The safety communications may stop since the safety communication relay function is discontinued and an error is detected.
The function restarts when the momentary power failure is cleared.
Take any of the following actions.
Action
Take measures for momentary power failure. ( MELSEC iQ-R Module Configuration Manual)
For transmission interval monitoring time, satisfy the following calculation formula.*1
■Transmission interval monitoring time of the master station (safety station)
TM > (S2cyc  2) + (LS  6) + (PT  2) + 110
■Transmission interval monitoring time of the module set to SIL2 mode Main
TM > (SCmst  2) + (LS  6) + (PT  2) + 110
*1 The meanings of the variables in the equation are as follows.
Variable Meaning
TM Transmission interval monitoring time [ms]
S2cyc Control cycle time of the module set to SIL2 mode Main [ms]
SCmst Safety cycle time of the master station [ms]
LS Link scan time [ms]
PT Allowable momentary power failure time of the power supply module with the remote head module [ms]
When the ring topology is configured

Satisfy the following calculation formula for the transmission interval monitoring time of the module set to SIL2 mode Main.*1
If the calculation formula is not satisfied, the safety communications stop due to the loopback or clearing it.
• TM≥(SCmst2)+(LS10)+24
Variable Meaning
TM Transmission interval monitoring time [ms]
SCmst Safety cycle time of the master station [ms]
LS Link scan time [ms]
1 FUNCTIONS
2 PARAMETER SETTINGS
This chapter describes CPU parameters of the remote head module and module parameters of the module mounted on the
remote head module.
2.1 CPU Parameters

This section describes details on CPU parameters together with their setting windows.
[Navigation window]  [Parameter]  [RJ72GF15-T2]  [CPU Parameter]
Item Description Reference

Name Setting Set titles and comments for the remote head module. Page 77 Name Setting
Operation Related Set remote reset for the remote head module. Page 78 Operation Related
Setting Setting
RAS Setting Set parameters for the RAS function. Page 79 RAS Setting
Network Required Set network numbers and station numbers for the remote head module. Page 80 Network Required
Setting Setting
Network Application Set module operation mode, transfer between devices, and redundancy for the remote head Page 81 Network Application
Setting module. Setting
• The remote head module does not employ static routing. However, it supports dynamic routing.
• Use a master station for the routing setting to communicate with other network by using static routing. The
remote head module communicates based on the routing setting of the master station.
76 2.1 CPU Parameters
Name Setting
Set titles and comments for the remote head module.
Item Description Setting Range

Title Setting Title Set titles (name or application) for the remote head module. Up to 32 one-byte characters
(Default: Blank)
Comment Setting Comment Set a comment for title for the remote head module. Up to 256 one-byte characters
(Default: Blank)
2.1 CPU Parameters 77
Operation Related Setting
Set remote reset for the remote head module.

Remote Reset Setting Remote Reset Set whether to permit reset with an external remote operation for • Disable
the remote head module. • Enable
(Default: Enable *1)
*1 The default differs from that of the CPU module. Caution is required when reset is performed with all stations specification.
RAS Setting
Set parameters for the RAS function.

Error Detection Setting Module Verification Set whether or not to detect the module verification error. • Detect
Error*1 • Not detect
Fuse Blown Set whether or not to detect a fuse blown of the module (Default: Detect)
mounted on the remote head module.
Redundant Power Set whether or not to detect an error of the power supply module
Supply System Error at the redundant power supply system configuration.
Remote head Module Operation Module Verification Set the remote head module operation at a module verification • Stop
Setting at Error Detection*2 Error error. • Continue
(Default: Stop)
Fuse Blown Set the remote head module operation at a fuse blown of the
module mounted on the remote head module.
Online module change setting Direct change Set "Enable" or "Disable" to "Direct change setting". • Disable
setting [Precautions] • Enable
When the direct change is enabled, a minor error occurs by the (Default: Disable)
direct change.
Therefore, the operating status of the remote head module does
not change to the STOP state even if the "Module Verification
Error" of "Remote head Module Operation Setting at Error
Detection" is set to "Stop".
*1 When "Not detect" is enabled and the operating remote head module is removed, a module verification error is not detected, but an error
may occur if an program tries to access the removed module. Also, the removed CPU module will not be accessible even when it is re-
installed. Therefore, if access is tried to the re-installed CPU module through the STOP and RUN operations, it may result in an error.
*2 Set the operation of the remote head module when an error is detected by the self-diagnostic function.
When "Stop" is set, the operating status of the remote head module is set to the STOP state and the cyclic transmission is stopped.
When "Continue" is set, the operating status of the remote head module is maintained.
When the remote head module is in the STOP state, the operation is as follows.
 The transfer from the link device (RX, RY, RWr, RWw) of the remote head module to the user device (X, Y, W) is as follows.
The transfer from RY to Y stops.
The transfer from RWw to W stops.
The transfer from X to RX continues.
The transfer from W to RWr continues.
 The data transfer between the devices in the remote head module stops.
 All outputs of the remote head module are turned off.
Network Required Setting
Set network numbers and station numbers for the remote head module.
Item Description Setting Range*1*2

Network No. Network No. Set the network number of the remote head module. • Blank
• 1 to 239
(Default: Blank)
Station No. Station No. Set the station number of the remote head module. • Blank
• 1 to 120
(Default: Blank)
*1 When the "Network No." and "Station No." fields are left empty in the online mode, the head module will operate with the station number
set by the CC-Link IE Field Network diagnostics for the master station. For details, refer to the following.
Page 96 Station number setting of the remote head module
*2 To include the module set to the SIL2 mode in the system configuration, do not leave the "Network No." and "Station No." fields empty.
Network Application Setting
Set module operation mode, transfer between devices, and redundancy for the remote head module.

Module Module Online mode • Online
Operation Operation • Select this mode to connect the remote head module to the network for • Offline
Mode Mode performing data link with other stations. (Default: Online)
Offline mode
• Select this mode to disconnect the remote head module from the network for
stopping data link with other stations.
Transfer Setting Transfer Setting Set parameters to transfer devices of the remote head module as cyclic data. Page 82 Transfer Setting
between between between Devices
Devices Devices
Redundant Line Type Displays a type of the line to use the remote head module as a redundant • Single Line
System system. • Redundant Line
Settings
Transfer Setting between Devices
Set the settings for transfer between devices (3) to transfer the following devices of the remote head module (2) to the master
station (1) as cyclic data.
• Link special relay (SB)
• Link special register (SW)
• Special relay (SM)
• Special register (SD)
• Link register (W)
(1) (2)
RWw RWw W SB/SW/SM/SD

0000H
03FFH
RWr RWr
1000H
(3)
13FFH
1FFFH
2

Setting Right-click in the "Transfer Setting between Devices" window and • Start/End
Method select a device setting method from the "Setting Method" menu. • Points/Start
• Start/End: Enter the start and end numbers of devices. (Default: Start/End)
• Points/Start: Enter the points and start numbers of devices.
Device Set a transfer source device and transfer destination device. • SB
Name Set W device for either the transfer source device or transfer • SW
destination device. • SM
• SD
•W
(Default: Blank)
Points Set the number of points of the device to be transferred. • SB: 16 to 8192*1
• SW: 1 to 8192
• SM: 16 to 2048*1
• SD: 1 to 2048
• W: 1 to 8192
(Default: Blank)
Start Set the start number of the device to be transferred. Source
• SB: 00000H to 01FF0H*1
• SW: 00000H to 01FFFH
• SM: 0 to 2032*1
• SD: 0 to 2047
• W: 00000H to 01FFFH
(Default: Blank)
Destination
• SB: 00000H to 01FF0H*1
• SM: 0 to 2032*1
• SD: 0 to 2047
• W: 01000H to 01FFFH
(Default: Blank)
End Set the end number of the device to be transferred. Source
• SB: 0000FH to 01FFFH*1
• SM: 15 to 2047*1
• SD: 0 to 2047
• W: 00000H to 01FFFH
(Default: Blank)
Destination
The number is automatically set according to the setting of the transfer source.
*1 For bit devices, specify a device number in 16-point units to make possible to use in units of words.
2.2 Module Parameter
This section describes differences in module parameters between the module mounted on the remote head module and CPU
module.
Refresh settings
• Refresh target: Only specified device is selectable. Module label and refresh data register (RD) cannot be selected.
• Transfer to intelligent function module and transfer to CPU: The settable device range is limited. The device range allowed
is as follows.
Item Setting range of refresh target device
Data to transfer to the When data is received from the • W0 to W03FF
intelligent function module master station with cyclic • Y (The ones not used by I/O)
transmission
When data is written from the • W0 to W1FFF (The ones not assigned to cyclic transmission)
master station with transient • X/Y (The ones not used by I/O and not assigned to cyclic transmission)
transmission • SB1000 to SB1FFF
• SW1000 to SW1FFF
• RD0 to RD12287
Data to transfer to the CPU When data is sent to the master • W1000 to W13FF
module station with cyclic transmission • X (The ones not used by I/O)
When data is read to the master • W0 to W1FFF (The ones not assigned to cyclic transmission)
station with transient transmission • X/Y (The ones not used by I/O and not assigned to cyclic transmission)
• SB1000 to SB1FFF
• SW1000 to SW1FFF
• RD0 to RD12287
Automatic serial number assignment of the refresh settings is useful to make a batch access to all the
scattered buffer memory of the intelligent function module existing in more than one area.
• Use the refresh settings of the intelligent function module to make an automatic serial number assignment
of the link register (W) to the buffer memory of the remote head module to perform refresh.
• Master stations are able to read and write from/to the link register (W) of the remote head module with a
single READ/WRITE instruction.
When the master station directly accesses the buffer memory of the intelligent function module with a
REMFR/REMTO instruction, the number of the REMFR/REMTO instructions corresponds to the number of
areas of the buffer memory.
Interrupt settings
The interrupt settings are not available.
If the interrupt settings are set, an error occurs in the remote head module.
Refresh Group
The refresh group setting of the refresh settings is not available.
Parameter setting method

For the RJ61BT11, "Program" cannot be set in "Parameter Setting Method" of "Required Setting".
84 2.2 Module Parameter
3 AVAILABLE FILE OPERATION
The following table lists file operations which are available for each file type.
: Available, : N/A
File type Operation using engineering tool Operation with SLMP and FTP server
function
Write Read Delete Write Read Delete
Parameter  *2
  *2
 *1
 *1 3
*1
Device comment      *1
Global label setting file    *1  *1
*1
Initial label value file Initial global label value file      *1
Event history      
Device data storage file    *1  *1
General-purpose data      
Remote password *2  *2 *1  *1
*1 Available only when the remote head module operation status is STOP. A communication error occurs when operated in the RUN state.
*2 Available only when the remote head module operation status is STOP. If performed in RUN state, the operating status of the remote
head module is changed by the remote STOP function, and then the operation continues.

85
MEMO

86
4 TROUBLESHOOTING
This chapter describes errors that may occur during system operation, error causes, and actions to be taken.
For the troubleshooting specific to each module, refer to the manual for the module used.
Reading devices and saving the program at the time of an error helps to analyze the error cause. For read
operations from the programmable controller, refer to the following.
4.1 Troubleshooting Procedure 4

When the system has any trouble, perform troubleshooting in the following order.
1. Check the LED status of the power supply module. ( Page 101 When the POWER LED of the power supply module
turns off)
2. Check the LED status of the remote head module. ( Page 89 Checking with LED)
3. Check the LED status of each I/O module and intelligent function module. ( User's Manual (Application) for the
module used)
4. Connect an engineering tool, and execute the system monitor function. The error module can be identified.
[Diagnostics]  [System Monitor]
4 TROUBLESHOOTING
4.1 Troubleshooting Procedure 87
5. Select the error module, and execute the module diagnostics function. The error cause and the action to be taken can be
displayed. ( Page 92 Checking the Module Status)
[Diagnostics]  [System Monitor]  Double-click the error module.
6. When data link cannot be performed even though the remote head module is normal in the module diagnostics, execute
the CC-Link IE Field Network diagnostics, and take action. ( Page 95 Checking the Network Status)
7. If the error cause cannot be identified by the module diagnostics and CC-Link IE Field Network diagnostics, check the
executed operations and detected error logs on the event history window.
[Diagnostics]  [System Monitor]  [Event History] button
8. If the error cause cannot be identified in steps 1 to 7, perform troubleshooting by symptom. ( User's Manual
(Application) for the module used)
4 TROUBLESHOOTING
88 4.1 Troubleshooting Procedure
4.2 Checking with LED
This section describes troubleshooting using LED.
Error status can be determined by status of the RUN LED and the ERR LED.
RUN LED ERR LED Error status*1 Description
Off On, flashing Major error An error such as hardware failure or memory failure. The module stops operating.
On Flashing Moderate error An error, such as parameter error, which affect module operation. The module stops
operating.
On On Minor error An error such as communication failure. The module continues operating.
*1 When multiple errors occur, the error status is displayed in the order of major, moderate, and minor.
When the RUN LED turns off 4

When the RUN LED turns off after powering on the remote head module, check the following.
Check item Action
Is the remote head module mounted correctly? Securely mount the remote head module on the main base unit.
Does the RUN LED turn on when the power supply module is replaced and The power supply module before the replacement has failed. Replace the
the system is powered on again? power supply module.
(Check the LED status after the power supply module on the extension base
unit is also replaced.)
Does the RUN LED remain off even after the power supply module is replaced One of the modules except the power supply module has failed. Repeatedly
and the system is powered on again? supply power to the system, returning the modules to the system one by one.
(Check the LED status after the power supply module on the extension base The last module mounted immediately before the RUN LED turns off has
unit is also replaced.) failed. Replace the corresponding module.
Is the remote head module of the standby system being replaced in a Reset the replaced remote head module of the standby system.
redundant system?
If the above action does not solve the problem, perform the module communication test to check for hardware failure. (
Page 94 Module communication test)
When the BUS RUN LED turns off

When the BUS RUN LED turns off after powering on the remote head module, check the following.
Check item Action
Is the switch on the remote head module set to RUN? Set the switch on the remote head module to RUN to start data link.
Is it in the remote STOP state? Cancel the remote STOP state and start data link.
Has an error occurred in the remote head module? Identify the error cause on the system monitor window using the engineering
tool, and take action. ( Page 87 Troubleshooting Procedure)
Is the master station in the RUN state? Set the operating status of the master station to RUN. If the master station has
stopped due to an error, troubleshoot it referring to the manual for the master
station. ( User's manual for the master/local module used)
Is the remote head module disconnected during STOP of the master station? • Set the operating status of the master station to RUN and reconnect the
remote head module to the network.
• Reset the remote head module because it retains the STOP status of the
master station.
If the above action does not solve the problem, perform the module communication test to check for hardware failure. (
Page 94 Module communication test)
When the ERR LED turns on or is flashing

When the ERR LED turns on or is flashing, check the following.
Check item Action
Does any error occur in the module diagnostics? Take the actions displayed on the window.
Is an error displayed in the CC-Link IE Field Network diagnostics? Take the actions displayed on the window.
If the above actions do not solve the problem, perform the following tests to check for an error.
• Module communication test ( Page 94 Module communication test)
• Cable test ( MELSEC iQ-R CC-Link IE Field Network User's Manual (Application))
4 TROUBLESHOOTING
4.2 Checking with LED 89
When the D LINK LED turns off
When the D LINK LED turns off, check the following.
Check item Action
Is the master station connected to the network and operating normally? • If an error has occurred in the CPU module on the master station, eliminate
the cause of the CPU module error. ( User's manual for the CPU module
used)
• Connect the engineering tool to the master station, and check if the master
station is performing data link by executing the CC-Link IE Field Network
diagnostics. ( User's manual for the master/local module used)
Are the Ethernet cables used normally? • Check if the Ethernet cable which conforms the standard is used. (
User's manual for the master/local module used)
• Check if the station-to-station distance is set within range. ( MELSEC
iQ-R CC-Link IE Field Network Remote Head Module User's Manual
(Startup))
• Check if the Ethernet cables are not disconnected.
Is a switching hub connected in ring topology? Configure the network in ring topology without a switching hub.
Are the switching hub and other stations connected to the remote head Check if the switching hub and other stations are powered on.
module operating normally?
Is the switching hub used operating normally? Check if a switching hub which conforms the standard is used. ( User's
manual for the master/local module used)
Is the station number of the remote head module duplicated with any of the Change the duplicated station number.
other stations?
Does the network number of the remote head module match with that of the Match the network number of the remote head module with that of the
connected network? connected network.
Is an error displayed in the CC-Link IE Field Network diagnostics? Take the actions displayed on the window.
When the D LINK LED is flashing

When the D LINK LED is flashing, check the following.
Check item Action
Does the station number indicated in the dot matrix LED of the remote head • Match the network number of the remote head module with that of the
module match with that of the remote head module specified in the network remote head module specified in the network configuration setting of the
configuration setting of the master station? master station. ( User's manual for the master/local module used)
• Initialize the remote head module and rewrite the parameter using the
engineering tool.
If the above actions do not solve the problem, connect the engineering tool to the master station and execute the CC-Link IE
Field Network diagnostics. ( User's manual for the master/local module used)
4 TROUBLESHOOTING
90 4.2 Checking with LED
When the L ERR LED turns on
When the L ERR LED turns on, check the following.
Check item Action
(Startup))
Is the switching hub used operating normally? • Check if a switching hub which conforms the standard is used. ( User's
manual for the master/local module used)
• Power off and on the switching hub.
Are other stations connected to the remote head module operating normally? Check the operation status of modules on other stations.
4
Is the mode of the module on the master station set to Online? Change the mode to Online. ( User's manual for the master/local module
used)
Is there any source of noise near the module or cables? Change the location of the module or cables.
Is the loopback function enabled for the master station? When the loopback function is enabled, check if the ring topology is correctly
configured for the port where the L ER LED is on. ( User's manual for the
master/local module used)
When the LINK LED turns off

When the LINK LED turns off, check the following.
Check item Action
(Startup))
Does the cabling condition (bending radius) meet the specifications? Refer to the manual for the Ethernet cable, and correct the bending radius.
Are the switching hub and other stations connected to the remote head Check if the switching hub and other stations are powered on.
module operating normally?
When the CTRL LED is flashing

When the CTRL LED is flashing, check the following.
Check item Action
Has a moderate error or major error occurred in the remote head module of Perform troubleshooting using ERR LED. ( Page 89 When the ERR LED
the standby system? turns on or is flashing)
Is the D LINK LED of the remote head module of the standby system off or Perform troubleshooting using D LINK LED. ( Page 90 When the D LINK
flashing? LED turns off, Page 90 When the D LINK LED is flashing)
Is the SBY LED of the remote head module of the standby system flashing? The memory is being copied from the control system to the standby system.
Wait until memory copy from the control system to the standby system was
completed, the remote head module of the standby system is automatically
reset, and the system is restarted.
Are the operating statuses of the remote head modules of both systems (RUN Match the operating statuses of both systems (RUN state/STOP state).
state/STOP state) mismatch?
4 TROUBLESHOOTING
4.2 Checking with LED 91
4.3 Checking the Module Status
The following items can be checked in the "Module Diagnostics" window for the remote head module.
Item Description
Error Information Displays the details of the errors currently occurring.
Click the [Event History] button to check the history of errors that have
occurred on the network, errors detected for each module, and operations that
have been executed.
Module Information List Displays various status information of the remote head module.
Supplementary Function CCIEF diagnostics Enables checking the cause to resolve the problem when an error occurs in
CC-Link IE Field Network. ( Page 95 Checking the Network Status)
Error Information
Check the details of the error currently occurring and action to remove the error.
Item Description
Status Major: An error such as hardware failure or memory failure
Moderate: An error, such as parameter error, which affect module operation
Minor: An error such as communication failure
Detailed Information Displays detailed information about each error (maximum of 3 pieces).
Cause Displays the detailed error causes.
Corrective Action Displays the actions to eliminate the error causes.
4 TROUBLESHOOTING
92 4.3 Checking the Module Status
Module Information List
Switch to the [Module Information List] tab to check various status information of the remote head module.
Item Description
LED information Displays the LED status of the remote head module.
SW information Displays the switch status of the remote head module.
Individual information Station Type Displays "Intelligent device station".
Network No. Displays the network number set for the selected module.
Station No. Displays the station number set for the selected module.
Communication Mode Displays the communication mode set for the selected module.
MAC address (1st octet) Displays the 1st octet of the MAC address.
MAC address (2nd octet) Displays the 2nd octet of the MAC address.
MAC address (3rd octet) Displays the 3rd octet of the MAC address.
MAC address (4th octet) Displays the 4th octet of the MAC address.
4 TROUBLESHOOTING
4.3 Checking the Module Status 93
Module communication test
The module communication test checks the hardware of the remote head module. When the communication using the remote
head module is unstable, whether an hardware failure occurs or not can be checked.
The following lists the tests performed.
Test item Description
Internal self-loopback test Checks whether the communication function of the module can be performed
normally.
External self-loopback test Checks whether the communication can be performed normally with the cable
connected between two connectors.
■Procedure
1. Connect the P1 and P2 of the remote head module with an Ethernet cable.
2. Using the switch on the remote head module, repeat three cycles of STOPRESET/TESTSTOP, taking less than one
second per cycle. (The RUN LED flashes after the 3rd cycle.)
3. Reset the remote head module to start the module communication test.
• Do not perform a module communication test while connected to another station. The operation of another
station may failed.
• The redundant function cannot be used during execution of the module communication test.
■Checking the status and result of module communication test

The test status and result can be checked with LED indication of the module.
Test status LED indication
Test in progress The dot matrix LED indicates "UCT".
Normal completion The dot matrix LED indicates "OK".
Abnormal end The ERR LED turns on and the dot matrix LED indicates "ERR" and error number alternately at intervals of 1 second.
■Error number when the test abnormally ended

The dot matrix LED indicates the error number with the form of "Port number Error number".
For example, "1 3" is indicated when error No.3 occurs in P1.
If the module communication test fails, check the following.
Error Description Action
number
1 Internal self-loopback test failure Please consult your local Mitsubishi representative.
2 External self-loopback test connection error Check the Ethernet cable connection or replace the Ethernet cable, and perform the test
again. If the test fails again, please consult your local Mitsubishi representative.
3 External self-loopback test communication Replace the Ethernet cable and perform the test again. If the test fails again, please consult
error your local Mitsubishi representative.
4 TROUBLESHOOTING
94 4.3 Checking the Module Status
4.4 Checking the Network Status
Perform the CC-Link IE Field Network diagnostics to check the network status and error details or to perform an operation test
for troubleshooting.
This section describes a method for diagnosing the system by directly connecting the engineering tool to the remote head
module. For the method connecting the engineering tool to the master station, refer to the following.
 User's manual for the master/local module used
Diagnostic items
The following table lists items that can be diagnosed by the CC-Link IE Field Network diagnostics.
(2)
(1)
(3)
Item Description Reference

(1) Remote head module status Displays the communication status of the remote head module.  MELSEC iQ-R CC-Link IE
and error details Field Network User's Manual
(Application)
(2) Communication Test Checks if transient transmission data can be properly routed from the connected
station to the communication target station.
IP Communication Test Checks the arrival time and route of IP communications from the connected station
to the communication target.
Cable Test Checks the connection status of cables between the test target station and the
devices connected to the port of the station.
(3) Remote Operation Remotely operates the remote head module (RUN, STOP, RESET). Page 96 Remote operation
• The CC-Link IE Field Network diagnostics cannot be started when another station has been specified for
"Other Station Setting" in the "Specify Connection Destination Connection" window. Directly connect the
engineering tool to the remote head module to be diagnosed, and start the CC-Link IE Field Network
diagnostics.
• For the redundant system configuration, the CC-Link IE Field Network diagnostics cannot be started when
another remote head module has been specified in "Target System" of the "Specify Connection Destination
Connection" window. Directly connect the engineering tool to the remote head module to be diagnosed,
specify the own remote head module ("Not Specified" in "Multiple CPU Setting" and "Not Specified" in
"Specify Redundant CPU"), and start the CC-Link IE Field Network diagnostics.
4 TROUBLESHOOTING
4.4 Checking the Network Status 95
Remote operation
For remote operations from the CC-Link IE Field Network diagnostics, follow the steps below.
1. Select the module where the remote operations are
performed in the CC-Link IE Field Network diagnostics.
2. Click the [Remote Operation] button in the "CC-Link IE
Field Diagnostics" window. Or right-click a module icon
in the "Network Status" and click [Remote Operation].
"Remote Operation" window is displayed.
3. Select a remote operation (RUN, STOP, or RESET) to
be performed in "Operation".*1
4. Click the [Execute] button to perform the remote

operation.
*1 To perform remote RESET, preset "Remote Reset Setting" under "Operation Related Setting" of "CPU Parameter" to "Enable".
For details on the remote operations, refer to the following.

Page 27 Remote Operation
Station number setting of the remote head module

For the station number setting of the remote head module using the CC-Link IE Field Network diagnostics, follow the steps
below.
1. Start the CC-Link IE Field Network diagnostics from the engineering tool connected to the master station.
2. Select the icon of the remote head module with no station number setting from the network map window.
3. Click the [Set Station No.] button in "Selected Station Communication Status Monitor".
4. Set the station number in the following window, and click the [OK] button.
When the station number setting of the remote head module is performed from the master station of the
MELSEC-Q/L series, use the master/local module with a serial number (first five digits) of "13032" or later and
GX Works2 with Version 1.53F or later.
■Precautions
• The network number will be the same as that of the master station.
• When a network number and a station number are set in the "Network Required Setting" tab of "CPU Parameter", the
parameter settings take priority.
4 TROUBLESHOOTING
96 4.4 Checking the Network Status
■When a redundant system of single line is configured
When the remote head module is used in a redundant system of single line the station number setting of the remote head
module from the master station is as follows:
1. The remote head modules of both systems are
displayed in the network map.
2. Select the remote head No.1 or No.2 and set the station
number.
3. The station numbers are set in the remote head

modules of both systems.
The station number of the remote head No.1 will be the
station number set and that of the remote head No.2 will be
the station number set + 1.*1
However, when 120 is set in the station number, the station
number of the remote head No.1 will be 119 and that of the
remote head No.2 will be 120.
*1 When the station number set + 1 already exists on the same network, an error occurs.
4 TROUBLESHOOTING
4.4 Checking the Network Status 97
■When a redundant system of redundant line is configured
When the remote head module is used in a redundant system of redundant line, the station number setting of the remote head
module from the master station is as follows:
■Control system 1. Only the remote head module of either system is
displayed in the network map.
■Standby system
2. Select the remote head module in the control system or

standby system to set the station number.
■Control system 3. The station numbers are set in the remote head
modules of both systems.
■Standby system
4 TROUBLESHOOTING
98 4.4 Checking the Network Status
4.5 Replacing the Remote Head Module
This section describes the procedure for replacing the remote head module.
For a system configuration other than a redundant system

The remote head module can be replaced without stopping the data link in the entire network.
Even if the remote head module connected does not have a station number, it can be set from the CC-Link IE Field Network
diagnostics of the master station.
1. Read parameters written in the remote head module to a project of the engineering tool.
[Online]  [Read from PLC]
2. Connect the engineering tool to the master station, and stop the data link of the remote head module from the CC-Link IE
4
Field Network diagnostics.
3. From the CC-Link IE Field Network diagnostics, set the remote head module as a temporary error invalid station.
4. Power off the programmable controller on the remote head module side, and remove the Ethernet cable from the remote
head module.
 MELSEC iQ-R CC-Link IE Field Network Remote Head Module User's Manual (Startup)
5. Replace the remote head module.

6. Connect the Ethernet cable to the remote head module, and power on the programmable controller.
7. Set the station number of the remote head module to that of the remote head module before the replacement by using
the CC-Link IE Field Network diagnostics from the master station. ( Page 96 Station number setting of the remote
head module)
8. Change the connection destination of the engineering tool to the remote head module, and write the parameters read in
the step 1 to the replaced remote head module.
The written parameters are reflected when the system is powered off and on, or when the remote head module is reset.
9. Set the switch of the remote head module to the RUN position.
10. Cancel the temporary error invalid station setting on the master station, and start the link.
11. Check if communication is normal by using the CC-Link IE Field Network diagnostics. ( Page 95 Checking the
Network Status)
4 TROUBLESHOOTING
4.5 Replacing the Remote Head Module 99
For the standby system in a redundant system configuration
This section describes the procedure of replacing the remote head module of the standby system in a redundant system
configuration
The remote head module of the standby system can be replaced while the remote head module of the control system controls
the system at power-on (online).
1. Check that the remote head module to be replaced is set to the standby system (the CTRL LED turns off). To replace the
remote head module of the control system, switch the module to the standby system using the engineering tool.
2. Disconnect the Ethernet cable from the remote head module to be replaced.
3. Set the switch of the remote head module of the standby system to the STOP position.
4. Remove the remote head module of the standby system from the main base unit.
5. Set the switch of the remote head module to be replaced to the STOP position.
6. Mount the remote head module to be replaced on the main base unit.
7. Reset the replaced remote head module of the standby system.
8. Check that the RUN LED of the remote head module of the standby system turns on, and that power is being supplied
normally.
9. When a file mismatch was detected by the consistency check between systems, memory copy from the control system to
the standby system is automatically executed. Then, the remote head module of the standby system is automatically
reset, and the system is restarted.
10. Connect the Ethernet cable to the remote head module.

11. Set the switch of the remote head module of the standby system to the same position as that of the remote head module
of the control system.
When the remote head module of the standby system is removed, a minor error occurs in the remote head
module of the control system. Replace the remote head module of the standby system, and clear the error in
the remote head module of the control system if required.
4 TROUBLESHOOTING
100 4.5 Replacing the Remote Head Module
4.6 Troubleshooting by Symptom
If any function of the remote head module does not operate normally, perform troubleshooting by checking the following items.
If the ERR LED is on or flashing, eliminate the error cause using the engineering tool.
When cyclic transmission cannot be performed

The following lists the actions to be taken if cyclic transmission cannot be performed.
Check item Action
Is the D LINK LED of the remote head module turned on? If the D LINK LED is turned off or flashing, perform troubleshooting using LED.
( Page 90 When the D LINK LED turns off, Page 90 When the D LINK
LED is flashing)
Is "I/O Assignment Setting" in the [I/O Assignment] tab of the "System Set the I/O assignment correctly. ( MELSEC iQ-R Module Configuration 4
Parameter" window correctly set? Manual)
Is the switch on the remote head module set to RUN? Set the switch of the remote head module to RUN.
Is the RUN LED of the remote head module turned on? If the RUN LED is turned off, perform troubleshooting using LED. ( Page
89 When the RUN LED turns off)
If the above actions do not solve the problem, check the link device assignment of the master station and the refresh target
device setting of refresh parameters for an error. ( User's manual for the master/local module used)
When transient transmission cannot be performed

The following table lists the actions to be taken if transient transmission cannot be performed.
Check item Action
Is the D LINK LED of the remote head module turned on? If the D LINK LED is off or flashing, perform troubleshooting using LED. (
Page 90 When the D LINK LED turns off, Page 90 When the D LINK LED is
flashing)
If the above actions do not solve the problem, refer to the troubleshooting of the master/local module. ( User's manual for
the master/local module used)
When the POWER LED of the power supply module turns off
When the POWER LED of the power supply module turns off, check the following items.
Check item Action
Is the power supply module mounted on the base unit normally? Remove the power supply module from the base unit, and mount it back on
the base unit. Then, restore power to the system.
Is the RUN LED of the remote head module turned on? The power supply module has failed. Replace the power supply module.
Is the power supply voltage appropriate? Supply power voltage within the specified range. ( MELSEC iQ-R Module
Configuration Manual)
Does the internal current consumption within the entire system exceed the Review the system configuration so that the internal current consumption
rated output current of the power supply module? does not exceed the rated output current. ( MELSEC iQ-R Module
Configuration Manual)
Does the POWER LED turn on when power is restored to the system after all One of the modules except the power supply module has failed.
modules, except the power supply module, have been removed? Repeatedly supply power to the system, returning the modules to the system
one by one. The last module mounted immediately before the POWER LED
turns off has failed. Replace the corresponding module.
If the POWER LED of the power supply module does not turn on even after the items above are checked and the actions are
taken, the possible cause is a hardware failure of the power supply module. Please consult your local Mitsubishi
representative.
4 TROUBLESHOOTING
4.6 Troubleshooting by Symptom 101
When the specific extension base unit cannot be recognized
When the specific extension base unit cannot be recognized, check the following items.
Check item Action
Is the extension base unit that cannot be recognized the Q series extension Refer to the troubleshooting for the case where the specific Q series
base unit? extension base unit cannot be recognized. ( Page 102 When the specific
Q series extension base unit cannot be recognized)
Is the POWER LED of the power supply module of the extension base unit Refer to the troubleshooting for the power supply module. ( Page 101
that cannot be recognized turned off? When the POWER LED of the power supply module turns off)
Is the extension cable installed correctly? Correctly install the extension cable.
Can the specific extension base unit be recognized after the above items were Execute in the order shown below.
checked? • Replace the extension cable.
• Replace the corresponding extension base unit.
• Replace the base unit at one level before the corresponding extension base
unit.
If the specific extension base unit cannot be recognized even after the items above are checked and the actions are taken,
the possible cause is a hardware failure. Please consult your local Mitsubishi representative.
When the specific Q series extension base unit cannot be

recognized
When the specific Q series extension base unit cannot be recognized, check the following items.
Check item Action
Is the POWER LED of the power supply module of the Q series extension Refer to the troubleshooting for the power supply module. ( User's Manual
base unit that cannot be recognized turned off? (Hardware Design, Maintenance, and Inspection) for the Q series CPU
module used)
Is the POWER LED of the power supply module of the extension base unit Refer to the troubleshooting for the power supply module. ( Page 101
that cannot be recognized turned off? When the POWER LED of the power supply module turns off)
Is the connector pin for setting the number of extension base units correctly Correctly mount the connector pin for setting the number of extension base
mounted? units.
Is the extension cable installed correctly? Correctly install the extension cable.
Can the specific Q series extension base unit be recognized after the above Execute in the order shown below.
items were checked? • Replace the extension cable.
• Replace the corresponding Q series extension base unit.
• Replace the base unit at one level before the corresponding Q series
extension base unit.
If the specific extension base unit cannot be recognized even after the items above are checked and the actions are taken,
the possible cause is a hardware failure. Please consult your local Mitsubishi representative.
4 TROUBLESHOOTING
102 4.6 Troubleshooting by Symptom
When a redundant system is configured
The redundant system has not started.

When the redundant system of the remote head module has not started, check the following items.
Check item Action
Does a moderate error or major error occur in the remote head No.1 and Perform troubleshooting using LED. ( Page 89 When the ERR LED turns
No.2? on or is flashing)
Is the switch of the remote head No.1 and No.2 set to RUN? Set the switch of the remote head No.1 and No.2 to RUN.
Is the D LINK LED of the remote head No.1 and No.2 turned off? Perform troubleshooting using LED. ( Page 90 When the D LINK LED
turns off)
Is the D LINK LED of the remote head No.1 and No.2 flashing? Perform troubleshooting using LED. ( Page 90 When the D LINK LED is
flashing) 4
The systems cannot be switched.

When the systems of the remote head modules cannot be switched even if the system switching cause occurs, check the
following items.
Check item Action
Has a moderate error or major error occurred in the remote head module of Perform troubleshooting using LED. ( Page 89 When the ERR LED turns
the standby system? on or is flashing)
Is the RUN LED of the remote head module of the standby system off? Perform troubleshooting using LED. ( Page 89 When the RUN LED turns
off)
Is "Module Operation Mode" under "Network Application Setting" of "CPU Set "Module Operation Mode" under "Network Application Setting" of "CPU
Parameter" set to "Offline" in the remote head module of the standby system? Parameter" to "Online". ( Page 81 Network Application Setting)
Is the remote head module of the standby system in the module Complete the module communication test if the test is in progress.
communication test status?
Is the remote head module of the standby system being replaced? Complete the replacement of the remote head module of the standby system.
Is the D LINK LED of the remote head module of the standby system off or Perform troubleshooting using LED. ( Page 90 When the D LINK LED
flashing? turns off, Page 90 When the D LINK LED is flashing)
In a redundant line configuration, is the system switching disabled for the Enable the system switching for the master/local module. ( MELSEC iQ-R
master/local module of the master station on the remote head module side CC-Link IE Field Network User's Manual (Application))
network of the standby system?
In a redundant line configuration, is the system switching disabled for the CPU Enable the system switching for the CPU module. ( MELSEC iQ-R CPU
module of the master station on the remote head module side network of the Module User's Manual (Application))
standby system?
Is the D LINK LED of the new control system turned off? Perform troubleshooting using LED. ( Page 90 When the D LINK LED
turns off)
4 TROUBLESHOOTING
4.6 Troubleshooting by Symptom 103
Safety communication relay cannot be performed
The following lists the actions to be taken if safety communication relay cannot be performed.
Check item Action
Is the D LINK LED of the remote head module turned on? If the D LINK LED is turned off or flashing, perform troubleshooting using LED.
( Page 90 When the D LINK LED turns off, Page 90 When the D LINK
LED is flashing)
Is the switch on the remote head module set to RUN? Set the switch on the remote head module to RUN to start data link.
Is it in the remote STOP state? Cancel the remote STOP state and start data link.
If the above actions do not solve the problem, refer to the troubleshooting of each module. ( Manual for the module used)
4 TROUBLESHOOTING
104 4.6 Troubleshooting by Symptom
4.7 Error Codes
The remote head module stores the corresponding error code in the special register (SD) upon detection of an error using the
self-diagnostic function. If an error occurs when the data communications are requested from the engineering tool, intelligent
function module, or network system connected, the remote head module returns the corresponding error code to the request
source. The error details and cause can be identified by checking the error code. The error code can be checked in either of
the following ways.
• Module diagnostics in the engineering tool ( Page 87 Troubleshooting Procedure)
• Special register ('Latest self-diagnostic error code' (SD0), 'Self-diagnostic error number' (SD10 to SD25) ( Page 148
List of Special Register (SD) Areas)
This section describes errors that may occur in the remote head module and actions to be taken for the errors.
4
Error code system
All error codes are given in hexadecimal format (4 digits) (16-bit unsigned integer). The type of error includes the error, which
is detected through the self-diagnostic function of each module, and the common error, which is detected during
communication between modules. The following table lists the error detection type and the error code ranges.
Error detection type Range Description
Detection by the self-diagnostic 1000H to 3FFFH Error specific to each module, such as self-diagnostic errors
function of each module
Detected during communication 4000H to 4FFFH Error in the CPU module or remote head module
between modules
7000H to 7FFFH Error in the serial communication module
B000H to BFFFH Error in the CC-Link module
C000H to CFFFH Error in the Ethernet-equipped module
D000H to DFFFH Error in the CC-Link IE Field Network module
Detailed information
Upon detection of an error by the self-diagnostic function, the detailed information of the error cause is stored together with an
error code. The detailed information can be checked using the engineering tool. The following detailed information is added to
each error code. (Up to two types of information are stored for each error code. The types differ depending on error code.)
Detailed information 1 and 2 for the latest error code(s) can also be checked with the special register (SD). ( Page 148
List of Special Register (SD) Areas)
Detailed information Item Description
Detailed information 1 Drive/file information Information on the corresponding drive name and file name
Parameter information Information on the parameter, such as parameter storage location and parameter type
System configuration information Information on the system configuration, such as I/O numbers and power supply numbers
Frequency information Information on the frequency, such as the number of writes to memory
Failure information Information on failures
System switching information Information on the system switching
Detailed information 2 Drive/file information Information on the corresponding drive name and file name
Parameter information Information on the parameter, such as parameter storage location and parameter type
System configuration information Information on the system configuration, such as I/O numbers and power supply numbers
4 TROUBLESHOOTING
4.7 Error Codes 105
How to clear errors
Error clear is available only for the error which can be cleared. ( Page 32 RAS Function)
List of error codes
Self-diagnostic error code of the remote head module (1000H to 3FFFH)

The following table lists error codes detected by the self-diagnostic function of the remote head module.
Error Error name Error details and cause Action Detailed Diagnostic
code information timing
1000H Power shutoff • A momentary power failure has Check the power supply status.  Always
occurred.
• The power supply has been shut off.
1010H Power shutoff Power has been shut off or the power • Check the power supplied to the power supply System Always
(either of the supply voltage has dropped in either of modules on the base unit. configuration
redundant the redundant power supply modules on • Check that two power supply modules are information
power supply the redundant power supply base unit. mounted on the base unit. If the same error
modules) Or, only one redundant power supply code is displayed again, the possible cause is a
module is mounted. hardware failure of the power supply module.
Please consult your local Mitsubishi
representative.
1020H Failure (either A failure has been detected in either of The possible cause is a hardware failure of the System Always
of the the redundant power supply modules on power supply module. Please consult your local configuration
redundant the redundant power supply base unit. Mitsubishi representative. information
power supply
modules)
1030H Invalid power An invalid power supply module has Mount only applicable power supply modules. System Always
supply module been mounted on the redundant power If the same error code is displayed again, the configuration
supply base unit. possible cause is a hardware failure of the power information
supply module. Please consult your local
Mitsubishi representative.
1031H Redundant A power supply module other than the Mount only applicable power supply modules. System Always
power supply redundant power supply module has If the same error code is displayed again, the configuration
system error been mounted on the redundant power possible cause is a hardware failure of the power information
supply base unit. supply module. Please consult your local
1080H ROM write The number of writes to the flash ROM Replace the remote head module. Frequency At power-on,
count error (data memory and system memory) has information at RESET, at
exceeded 100000. write
(Number of writes > 100000 times)
1200H Module A moderate error has been notified from Check the detailed information (system System Always
moderate error the intelligent function module configuration information) of the error by executing configuration
connected. module diagnostics using the engineering tool, information
identify the error module, and eliminate the error
cause.
1210H Module An inter-module synchronous signal Check the detailed information (system System Always
moderate error error has been notified from the configuration information) of the error by executing configuration
intelligent function module connected. module diagnostics using the engineering tool, information
identify the error module, and eliminate the error
cause.
1830H Receive queue Number of reception requests of Lower the transient transmission usage frequency,  Always
full transient transmission exceeded upper and then perform again.
limit of simultaneously processable
requests.
1831H Receive Transient reception failed. Lower the transient transmission usage frequency, System Always
processing and then perform again. configuration
error information
1832H Transient data Too much transient transmission Correct the number of transient transmissions  Always
transmission processing exists and transient executions.
error transmission cannot be performed.
1850H Network error A CC-Link IE Field Network error has Check the details of the error by executing the CC-  Always
occurred. Link IE Field Network diagnostics, and take action
according to the action for the relevant error.
4 TROUBLESHOOTING
106 4.7 Error Codes
1B61H Standby A moderate error or major error has Eliminate the error cause, and restart the system.  Always
system remote been detected in the remote head If the same error code is displayed again, the
head module module of the standby system. (The possible cause is a hardware failure of the remote
error error is detected in the control system.) head module. Please consult your local Mitsubishi
representative.
1B70H Communication Data communications cannot be • When the remote head module of the standby  Always
s with the other performed with the other system. (The system is in the reset mode, exit the reset mode.
system error is detected in the control system or • When the remote head module of the standby
disabled the standby system.) system is not mounted, mount the module.
• Take measures to reduce noise.
• If the same error code is displayed again, the
possible cause is a hardware failure of the
remote head module or base unit. Please
consult your local Mitsubishi representative. 4
1BD0H System The systems were not switched. There Check the cause of system switching failure in the System At execution of
switching error was a cause of system switching failure. detailed information (system switching information) switching system
(The error is detected in the control of the error by executing module diagnostics using information switching
system.) the engineering tool, eliminate the error cause, and
switch the systems from the engineering tool
again. If the same error code is displayed again,
the possible cause is a hardware failure of the
remote head module. Please consult your local
1D10H Inter-module Cyclic transmission skip occurred. • Increase the value set in "Fixed Scan Interval  Always
synchronization Setting of Inter-module Synchronization" under
transmission "Inter-module Synchronous Setting" in the [Inter-
skip module Synchronous Setting] tab of the "System
occurrence Parameter" window so that the inter-module
synchronization cycle will not be exceeded.
• Reduce the refresh processing time by reducing
the data targeted for synchronization refreshing
so that the inter-module synchronization cycle
will not be exceeded.
• Set modules not requiring synchronization to
asynchronous so that the inter-module
synchronization cycle will not be exceeded.
2000H Module The module type set in the system Re-set the module type in the system parameters System At power-on,
configuration parameters ("I/O Assignment Setting" in in accordance with the remote head module or configuration at RESET
error the [I/O Assignment] tab of the "System intelligent function module actually mounted. information
Parameter" window) differs from that of
the module actually mounted.
2001H Module The I/O numbers set in the system Re-set the I/O numbers in the system parameters System At power-on,
configuration parameters ("I/O Assignment Setting" in in accordance with the intelligent function module configuration at RESET
error the [I/O Assignment] tab of the "System or I/O module actually mounted. information
Parameter" window) are overlapping
between modules.
2002H Module The number of points assigned to the Re-set the number of points in the system System At power-on,
configuration intelligent function module in the system parameters in accordance with the intelligent configuration at RESET
error parameters ("I/O Assignment Setting" in function module actually mounted. information
the [I/O Assignment] tab of the "System
Parameter" window) is smaller than that
of the module actually mounted.
2004H Module • CC-Link IE Controller Network • Remove the CC-Link IE Controller Network System At power-on,
configuration module* or/and CC-Link IE Field module or CC-Link IE Field Network module configuration at RESET
error Network module* are mounted on the which is mounted on the main base unit or information
main base unit or extension base unit. extension base unit.
• Nine or more CC-Link master/local • Decrease the total number of CC-Link master/
modules are mounted on the main local modules mounted on the main base unit
base unit and extension base unit. and extension base unit to eight or less.
The CC-Link IE built-in Ethernet * The CC-Link IE built-in Ethernet interface module
interface module is included if the is included if the module is used as a CC-Link IE
module is used as a CC-Link IE Controller Network module or CC-Link IE Field
Controller Network module or CC-Link Network module.
IE Field Network module.
2006H Module A module is mounted on the 65th slot or Remove the module mounted on the 65th slot or System At power-on,
configuration later. later. configuration at RESET
error information
4 TROUBLESHOOTING
4.7 Error Codes 107
2007H Module A module is mounted on the slot whose Remove the module mounted on the slot whose System At power-on,
configuration number is later than that specified in the number is later than that specified in the system configuration at RESET
error system parameters ("I/O Assignment parameters. information
Setting" in the [I/O Assignment] tab of
the "System Parameter" window).
2008H Module A module is mounted over or across the • Remove the module mounted over or across the System At power-on,
configuration maximum number of I/O points (4096). maximum number of I/O points (4096). configuration at RESET
error • Replace the module mounted on the last slot to information
the one that does not exceed the maximum
number of I/O points (4096).
2009H Module There is no response from the I/O • Check and correct the setting of "I/O System Always
configuration module or intelligent function module Assignment Setting" in the [I/O Assignment] tab configuration
error accessed. of the "System Parameter" window. information
• Reset the remote head module, and run it again.
If the same error code is displayed again, the
possible cause is a hardware failure of the I/O
module or intelligent function module. Please
consult your local Mitsubishi representative.
2020H Module There is a mounted module that is not • Remove the unsupported module. System At power-on,
configuration supported, or there is a mounted module • Check whether the modules support the network configuration at RESET
error that does not support the network type type (module model name) set in the system information
(module model name) set in the system parameters.
parameters ("I/O Assignment Setting" in • If all the modules and the network type (module
the [I/O Assignment] tab of the "System model name) are supported, the possible cause
Parameter" window). is a hardware failure of the remote head module,
base unit, or module (I/O module or intelligent
function module) connected. Please consult
your local Mitsubishi representative.
2022H Module A power supply module other than the Mount the redundant power supply module. System At power-on,
configuration redundant power supply module has If the same error code is displayed again, the configuration at RESET
error been mounted on the redundant power possible cause is a hardware failure of the power information
supply base unit. supply module, remote head module, or base unit.
representative.
2040H Remote head • The number of remote head modules • Correctly set the number of remote head System At power-on,
module set in the system parameters ("I/O modules (including the empty setting) in the configuration at RESET
configuration Assignment Setting" in the [I/O system parameters in accordance with the information
error Assignment] tab of the "System number of remote head modules actually
Parameter" window) differs from the mounted.
number of remote head modules • Correctly set the system parameters so that the
actually mounted. setting and actual remote head module
• The remote module is mounted on the mounting status will be the same.
slot different from the one specified in
the system parameters (I/O
assignment setting).
2041H Remote head • The remote head module is not • Correctly set the number of remote head System At power-on,
module mounted on the slot that is set for the modules (including the empty setting) in the configuration at RESET
configuration remote head module in the system system parameters in accordance with the information
error parameters ("I/O Assignment Setting" number of remote head modules actually
in the [I/O Assignment] tab of the mounted.
"System Parameter" window). • Remove the I/O module or intelligent function
• The remote head module is mounted module mounted between the remote head
on the slot that is set for empty in the modules.
system parameters ("I/O Assignment
Setting" in the [I/O Assignment] tab of
the "System Parameter" window).
• An I/O module or intelligent function
module is mounted between the
remote head modules.
2043H Remote head The remote head module is mounted on • Mount the remote head module on the System At power-on,
module the inapplicable slot. applicable slot (CPU slot or slot No.0). configuration at RESET
configuration • Remove the remote head module from the information
error inapplicable slot.
4 TROUBLESHOOTING
108 4.7 Error Codes
2044H Remote head The own remote head No. set in the Re-set the own remote head No. in the system System System
module system parameters ("I/O Assignment parameters in accordance with the mounting configuration configuration
configuration Setting" in the [I/O Assignment] tab of position of the remote head module. information information
error the "System Parameter" window) differs
from the one determined by the
mounting position of the remote head
module.
2050H Remote head An unsupported CPU module or remote Remove the unsupported CPU module or remote System System
module head module is mounted. head module. configuration configuration
configuration If all the remote head modules are supported, the information information
error possible cause is a hardware failure of the remote
head module or base unit. Please consult your
local Mitsubishi representative.
2060H Base unit Eight or more extension base units are Reduce the number of extension base units to System At power-on, 4
configuration connected. seven or less. configuration at RESET
error information
2061H Base unit Any of the following base units is Remove the inapplicable base unit: QA1S3B, System At power-on,
configuration connected: QA1S3B, QA1S5B/ QA1S5B/QA1S6B, QA6B, QA6ADP+A5B/ configuration at RESET
error QA1S6B, QA6B, QA6ADP+A5B/ A6BB, and QA1S6ADP+A1S5B/A1S6B. information
A6B, or QA1S6ADP+A1S5B/
A1S6B.
2063H Base unit Extension base unit levels are Check and correct the level setting of the System At power-on,
configuration overlapping. extension base units. configuration at RESET
error information
2070H Base unit • An unsupported base unit is • Disconnect the unsupported base unit. If all the System At power-on,
configuration connected. base units are supported, the possible cause is configuration at RESET
error • A GOT is bus-connected to the Q a hardware failure of the remote head module or information
series extension base unit. base unit. Please consult your local Mitsubishi
representative.
• Disconnect the GOT bus-connected to the Q
series extension base unit.
2080H Inter-module An inter-module synchronization signal The possible cause is a hardware failure of the System At power-on,
synchronization error has been detected. remote head module, base unit, or module (I/O configuration at RESET
configuration module or intelligent function module) connected. information
error Please consult your local Mitsubishi
representative.
20E0H Invalid module A module that the remote head module • Mount only applicable modules. System Always
cannot recognize is mounted. • The possible cause is a hardware failure of the I/ configuration
O module or intelligent function module information
accessed. Please consult your local Mitsubishi
representative.
2180H Invalid file An invalid file has been detected. Check the detailed information (drive/file Drive/file Always
information) of the error by executing module information
diagnostics using the engineering tool, select the
correct file name, and write the specified file to the
remote head module. If the same error code is
displayed again, the possible cause is a hardware
failure of the remote head module. Please consult
21A2H File A file other than the remote head Check the detailed information (parameter Drive/file At write, at
specification module project file has been written. information) of the error by executing module information power-on, at
error diagnostics using the engineering tool, and RESET, at
overwrite the file corresponding to the displayed STOP  RUN
number (file name.extension) with the one created state
in the project of the remote head module.
2220H Parameter The parameter setting is corrupted. Check the detailed information (parameter Parameter At power-on,
error information) of the error by executing module information at RESET, at
diagnostics using the engineering tool, and write STOP  RUN
the displayed parameter setting to the remote state
head module. If the same error code is displayed
again, the possible cause is a hardware failure of
the data memory in the remote head module or the
module (I/O module or intelligent function module)
connected. Please consult your local Mitsubishi
representative.
4 TROUBLESHOOTING
4.7 Error Codes 109
2221H Parameter The set value is out of range. Check the detailed information (parameter Parameter At power-on,
error information) of the error by executing module information at RESET, at
diagnostics using the engineering tool, and correct STOP  RUN
the parameter setting corresponding to the state, at
displayed number. If the same error code is instruction
displayed again, the possible cause is a hardware execution, at
failure of the data memory in the remote head module
module or the module (I/O module or intelligent access
function module) connected. Please consult your
2222H Parameter Use of the function that is not supported Check the detailed information (parameter Parameter At power-on,
error by the module is enabled in parameter. information) of the error by executing module information at RESET, at
the parameter setting corresponding to the state
displayed number. If the same error code is
failure of the data memory in the remote head
module or the module (I/O module or intelligent
function module) connected. Please consult your
2223H Parameter The parameter that needs a reset of the Reset the remote head module, and run it again. Parameter At write, at
error remote head module was modified and information power-on, at
overwritten. RESET, at
STOP  RUN
state
2224H Parameter A memory area cannot be ensured. • Check the detailed information (parameter Parameter At write, at
error information) of the error by executing module information power-on, at
diagnostics using the engineering tool, display RESET, at
the error-detected area by clicking the [Error STOP  RUN
Jump] button, and increase the capacity of the state
area. (If the capacity of the area cannot be
increased, decrease the capacity of other
areas.)
• Reduce the number of labels used.
2225H Parameter A parameter information other than that Check the detailed information (parameter Parameter At write, at
error of the remote head module project has information) of the error by executing module information power-on, at
been written. diagnostics using the engineering tool, and RESET, at
overwrite the parameters with the one created in STOP  RUN
the project of the remote head module. state
2241H Parameter • The I/O numbers set in the system • Check if the system configuration displayed on Parameter At power-on,
error (module) parameters differ from those of the the system monitor window of the engineering information at RESET, at
module actually mounted. tool match the actual system configuration. STOP  RUN
• The target module is not mounted on • For the module where "Module Status Setting" state, at
the slot where the system parameters under "I/O Assignment Setting" in the [I/O instruction
and module parameters are set. Assignment] tab of the "System Parameter" execution, at
• The module type set in parameter window is set to "Empty", do not set module
differs from that of the module actually "Synchronize" in "Select Inter-module access
mounted. Synchronous Target Module" under "Inter-
• Although "Module Status Setting" module Synchronous Setting" in the [Inter-
under "I/O Assignment Setting" in the module Synchronous Setting] tab of the "System
[I/O Assignment] tab of the "System Parameter" window.
Parameter" window is set to "Empty", • Check the detailed information (parameter
the module is set to "Synchronize" in information) of the error by executing module
"Select Inter-module Synchronous diagnostics using the engineering tool, and
Target Module" under "Inter-module correct the parameter setting corresponding to
Synchronous Setting" in the [Inter- the displayed number. If the same error code is
module Synchronous Setting] tab of displayed again, the possible cause is a
the "System Parameter" window. hardware failure of the data memory in the
remote head module or the module (I/O module
or intelligent function module) connected.
representative.
4 TROUBLESHOOTING
110 4.7 Error Codes
2242H Parameter The intelligent function module has Check the detailed information (system System At power-on,
error (module) detected a module parameter error. configuration information) of the error by executing configuration at RESET, at
module diagnostics using the engineering tool, and information STOP  RUN
check the module corresponding to the displayed state
number. If the same error code is displayed again,
the possible cause is a hardware failure of the data
memory in the remote head module or the
intelligent function module connected. Please
2260H Parameter Network numbers are overlapping. Check the detailed information (parameter Parameter At power-on,
error (network) information) of the error by executing module information at RESET
diagnostics using the engineering tool, and correct
the parameter setting corresponding to the
displayed number. If the same error code is 4
module or the intelligent function module
representative.
2261H Parameter Different line types (single line and Check the detailed information (parameter Parameter At power-on,
error (network) redundant line) are set to the master information) of the error by executing module information at RESET, at
station and a slave station. diagnostics using the engineering tool, and correct STOP  RUN
displayed number. If the same error code is
module or the intelligent function module
representative.
2280H Parameter The refresh setting is not set correctly. Check the detailed information (parameter Parameter At power-on,
error (refresh) information) of the error by executing module information at RESET, at
the parameter setting corresponding to the state, at
displayed number so that the data are refreshed instruction
within the specified device range. (Take actions execution, at
such as reducing the refresh device range.) module
access
2281H Parameter A device that cannot be used as a Check the detailed information (parameter Parameter At power-on,
error (refresh) refresh device is specified. information) of the error by executing module information at RESET, at
displayed number.
2282H Parameter The number of specified refresh points is Check the detailed information (parameter Parameter At power-on,
error (refresh) invalid. information) of the error by executing module information at RESET, at
displayed number.
2283H Parameter The total number of refresh points Check the detailed information (parameter Parameter At power-on,
error (refresh) exceeded the maximum limit. information) of the error by executing module information at RESET, at
displayed number.
2290H Parameter The interrupt settings were set. Clear the values of the interrupt settings. Parameter At power-on
error (interrupt) information
2320H Remote • The start I/O number of the remote • Set the start I/O number of the remote password System At power-on,
password password target module is set to other target module within the range of 0H to 0FF0H. configuration at RESET, at
setting error than 0H to 0FF0H. • On the specified slot, mount an intelligent information STOP  RUN
• There is a problem on the slot function module that supports the remote state
specified by the start I/O number of password setting.
the remote password setting.
(1) No module is mounted.
(2) The mounted intelligent function
module does not support the remote
password setting.
4 TROUBLESHOOTING
4.7 Error Codes 111
2400H Module • The module information at power-on • Check the detailed information (system System Always
verification differs from the information of configuration information) of the error by configuration
error modules actually mounted. executing module diagnostics using the information
• The I/O module or intelligent function engineering tool, and check the module
module is not mounted properly or corresponding to the displayed number.
was removed during operation. • Take measures to reduce noise.
possible cause is a hardware failure of the error
module. Please consult your local Mitsubishi
representative.
2401H Module A CPU module, remote head module, I/ • Check the detailed information (system System Always
verification O module, or intelligent function module configuration information) of the error by configuration
error was mounted on the base unit during executing module diagnostics using the information
operation. engineering tool, and check the module
corresponding to the displayed number.
• Do not mount a CPU module, remote head
module, I/O module, nor intelligent function
module during operation.
representative.
2420H Fuse blown The output module with a blown fuse • Check the FUSE LED of each output module, System Always
error has been detected. and replace the one with the FUSE LED on. configuration
• Check the detailed information (system information
configuration information) of the error by
executing module diagnostics using the
engineering tool, and replace the module
corresponding to the displayed slot number.
2440H Module major An error has been detected in the I/O • Take measures to reduce noise. System At power-on,
error module or intelligent function module • Reset the remote head module, and run it again. configuration at RESET
during the initial processing. If the same error code is displayed again, the information
representative.
2442H Module major An error has been detected in the I/O • Take measures to reduce noise. System At module
error module or intelligent function module. • Reset the remote head module, and run it again. configuration access
If the same error code is displayed again, the information
representative.
2443H Module major An error has been detected in the I/O • Take measures to reduce noise. System At module
error module or intelligent function module. • Reset the remote head module, and run it again. configuration access
representative.
2450H Module major • A major error has been notified from • Take measures to reduce noise. System Always
error the intelligent function module • Check the connection of an extension cable. configuration
connected. • Check the detailed information (system information
• The I/O module or intelligent function configuration information) of the error by
module is not mounted properly or executing module diagnostics using the
was removed during operation. engineering tool, and check the module
corresponding to the displayed number.
representative.
4 TROUBLESHOOTING
112 4.7 Error Codes
24C0H System bus An error was detected on the system • Take measures to reduce noise. System At module
error bus. • Reset the remote head module, and run it again. configuration access
remote head module, base unit, extension
cable, or module (I/O module or intelligent
cable, or module (I/O module or intelligent 4
24C2H System bus • The I/O module or intelligent function • Check the detailed information (system System Always
error module is not mounted properly or configuration information) of the error by configuration
was removed during operation. executing module diagnostics using the information
• An error was detected on the system engineering tool, and check the module
bus. corresponding to the displayed number.
• Check the connection of an extension cable.
possible cause is a hardware failure of the base
unit, extension cable, or module (I/O module or
intelligent function module) connected. Please
24C5H System bus An error was detected on the system • Take measures to reduce noise.  At module
error bus. • Reset the remote head module, and run it again. access
possible cause is a hardware failure of the base
unit, extension cable, or module (I/O module or
24C6H System bus An error was detected on the system • Take measures to reduce noise.  At module
error bus. • Reset the remote head module, and run it again. access
remote head module or extension cable. Please
24C8H System bus An error was detected on the system • Take measures to reduce noise.  At power-on,
error bus. • Reset the remote head module, and run it again. at RESET
extension cable, or module (I/O module or
4 TROUBLESHOOTING
4.7 Error Codes 113
24D0H System bus • The extension level setting of the Q • Check and correct the level setting of the Q System Always
error series extension base unit is series extension base unit. configuration
overlapping with that of any other • Check the connection of an extension cable. information
extension base units. • Check that the 10m mark is printed on the base
• An error was detected on the system unit connected when using the ten-meter
bus. extended cables (RC100B). ( MELSEC iQ-R
Module Configuration Manual)
remote head module, base unit, or extension
cable. Please consult your local Mitsubishi
representative.
24E0H System bus An error was detected on the system • Take measures to reduce noise. System Always
error bus. • Reset the remote head module, and run it again. configuration
remote head module or base unit. Please
2500H Network A failure has detected in network • Check whether the network is incorrectly Time Always
processing processing. configured in a ring topology, and correct the information
error wiring.
• If the same error code is displayed again, please
2501H Network A failure has detected in network • Check whether the network is incorrectly Time Always
processing processing. configured in a ring topology, and correct the information
error wiring.
• If the same error code is displayed again, please
2600H Inter-module The cyclic processing does not finish • Increase the value set in "Fixed Scan Interval  Always
synchronization before the start timing for the next inter- Setting of Inter-module Synchronization" under
processing module synchronization cycle. "Inter-module Synchronous Setting" in the [Inter-
error module Synchronous Setting] tab of the "System
Parameter" window so that the link scan time will
not exceed the inter-module synchronization
cycle.
• Reduce the number of cyclic assignment points
and the number of connected slave modules to
decrease the link scan time.
2610H Inter-module An inter-module synchronization error • Take measures to reduce noise.  Always
synchronization has been detected. • Reset the remote head module, and run it again.
signal error If the same error code is displayed again, the
2611H Inter-module An inter-module synchronization error • Check that the remote head module is System Always
synchronization has been detected. connected to the inter-module synchronous configuration
signal error master using the CC-Link IE Field Network information
diagnostics of the engineering tool.
3001H Station number A station with the same station number Correct the station number or station type of the Parameter Always
duplication was found in the same network. station where the error was detected. information
detection After taking the above actions, power off and on or
reset all stations where the error was detected.
4 TROUBLESHOOTING
114 4.7 Error Codes
3006H Pairing setting Pairing is not set to the stations in a Check the pairing setting in the network Parameter At power-on,
error redundant system. configuration setting of the master station. information at RESET
3007H Pairing setting Pairing is set to the stations not included Check the pairing setting in the network Parameter At power-on,
error in a redundant system. configuration setting of the master station. information at RESET
3040H Response data Response data of the dedicated • Increase the request interval.  Always
creation failure instruction cannot be created. • Decrease the number of request nodes.
• Wait for a response to the previous request
before sending the next request.
• Correct the timeout value.
3200H Label Memory/Device Setting set in the CPU • Write the global label setting file together with Drive/file At power-on,
information parameters differ from those assigned to the CPU parameter file to the remote head information at RESET, at
mismatch the global label setting file. module. STOP  RUN
• If no global label is used, delete the global label
setting file.
state 4
3205H Label • After the global label setting file was • Write CPU parameters, global label setting, and Drive/file At power-on,
information modified, only the modified file was global label assignment information files to the information at RESET, at
mismatch written to the remote head module. Or, remote head module. STOP  RUN
after the global label setting file was • If no global label is used, delete the global label state
modified, only the CPU parameters setting file.
were written to the remote head • If the external device access setting is not used,
module. (The global label setting file initialize the memory where the global label
was not written to the remote head assignment information file is stored, and write
module.) the CPU parameters and global label setting file
• After the CPU parameters were to the remote head module.
modified, only the CPU parameters
were written to the remote head
module.
• After the external device access
setting of the global label setting was
modified, only the global label
assignment information was written to
the remote head module. Or, after the
external device access setting of the
global label setting was modified, only
the CPU parameters were written to
the remote head module. (The
external device access setting of the
global label setting file was not written
to the remote head module.)
3206H Label After the global label setting file was • Write both the global label setting file and initial Drive/file At power-on,
information modified, only the modified file was global label value file to the remote head information at RESET, at
mismatch written to the remote head module. Or, module. STOP  RUN
without writing the modified global label • If no initial global label value is used, delete the state
setting file, only the initial global label initial global label value file.
value file was written to the remote head
module.
3600H Inter-module The value of the inter-module Correct the parameter so that all modules Parameter Always
synchronization synchronization cycle setting differs from performing inter-module synchronization have the information
cycle mismatch the one set in the master station. same frequency setting.
3601H Inter-module In the network synchronous Check the network configuration setting of the Parameter Always
synchronization communication setting of the network master module and check if inter-module information
cycle mismatch configuration setting of the master synchronization is set.
station, the own station is not set as a
target of inter-module synchronization.
3602H Inter-module Inter-module synchronization cycle • Check the network status and take corrective  Always
synchronization failure occurred between networks. action using the CC-Link IE Field Network
signal failure diagnostics.
via network • Check if the switching hub and the cables are
connected properly.
• If the error occurs again even after taking the
above, please consult your local Mitsubishi
representative.
4 TROUBLESHOOTING
4.7 Error Codes 115
3714H System A file mismatch was detected in the • Check the detailed information (drive/file Drive/file At write, at
consistency system consistency check. (The error is information) of the error by executing module information power-on, at
check error detected in the standby system.) diagnostics using the engineering tool, format RESET, at
(file) the corresponding drive of the remote head STOP  RUN
module in the standby system, write all files to state, at
the remote head module, and then restart the execution of
remote head module of the standby system. system
• Execute the memory copy function to match files switching
in the control system and the standby system.
Reset the remote head module, and run it again.
3C00H Hardware A hardware failure has been detected. • Take measures to reduce noise. Failure Always
to failure • Reset the remote head module, and run it again. information
3C02H If the same error code is displayed again, the
3C0FH Hardware A hardware failure has been detected. • Take measures to reduce noise. Failure Always
failure • Reset the remote head module, and run it again. information
3C10H Hardware A hardware failure has been detected. • Take measures to reduce noise. Failure At power-on,
failure • Reset the remote head module, and run it again. information at RESET
3C11H Hardware A hardware failure has been detected. • Take measures to reduce noise. Failure Always
failure • Reset the remote head module, and run it again. information
3C12H Hardware • The waveform of the voltage out of the • Check the waveform of the voltage applied to Failure Always
failure specified range has been detected in the power supply module. information
the power supply module. • Reset the remote head module, and run it again.
• A hardware failure has been detected If the same error code is displayed again, the
in the power supply module, remote possible cause is a hardware failure of the
head module, base unit, or extension power supply module, remote head module,
cable. (In a redundant power supply base unit, or extension cable. Please consult
system, a hardware failure has been your local Mitsubishi representative.
detected in both of two power supply
modules.)
3C21H Memory error An error has been detected in the • Take measures to reduce noise. Failure Always
memory. • Reset the remote head module, and run it again. information
3C2FH Memory error An error has been detected in the • Take measures to reduce noise. Failure Always
4 TROUBLESHOOTING
116 4.7 Error Codes
memory. • Format the memory. Write all files to the remote information
head module. Then, reset the remote head
module, and run it again. If the same error code
is displayed again, the possible cause is a
hardware failure of the remote head module.
representative.
Mitsubishi representative. 4
4 TROUBLESHOOTING
4.7 Error Codes 117
Error codes detected by other causes than self-diagnostic function (4000H to 4FFFH)
If an error occurs when the data communications are requested from the engineering tool, intelligent function module, or
network system connected, the remote head module returns the corresponding error code (4000H to 4FFFH) to the request
source.
These error codes are not stored in 'Latest self-diagnostic error code' (SD0) because the errors are not the ones detected by
the self-diagnostic function of the remote head module.
When the request source is an engineering tool, a message and an error code are displayed on the engineering tool.
When the request source is an intelligent function module or network system, the remote head module returns an error code
to the request source.
Error code Error name Error details and cause Action
4000H Common error Serial communication sum check error • Connect the serial communication cable correctly.
4001H Common error An unsupported request was executed. • Check the command data of the SLMP/MC
(The request was executed to the remote head protocol.
module that does not support the request.) • Check the CPU module model name selected in
• Check the target CPU module model name.
4002H Common error An unsupported request was executed. • Check the command data of the SLMP/MC
protocol.
• Check the CPU module model name selected in
• Execute the request again.
• If the same error code is displayed again, the
possible cause is a hardware failure of the remote
head module. Please consult your local Mitsubishi
representative.
4003H Common error Command for which a global request cannot be Check the command data of the SLMP/MC protocol.
performed was executed.
4004H Common error All the operations to the remote head module are Perform operations to the remote head module
disabled because of the following reason: again after the start-up processing ends.
• The remote head module is starting up.
4005H Common error The volume of data handled according to the Check the command data of the SLMP/MC protocol.
specified request is too large.
4006H Common error Initial communication has failed. • When using serial communication, inquire of the
external device manufacturer for support
conditions.
• When using serial communication, check the CPU
module model name selected in the engineering
tool.
• When using Ethernet communication, shift the
communication start timing.
4008H Common error The remote head module is BUSY. (The buffer is not Execute the request again after the specified period
vacant.) of time has elapsed.
4010H Remote head module The request cannot be executed because the Set the operating status of the remote head module
operation error remote head module is running. to STOP, and execute the request again.
4013H Remote head module The request cannot be executed because the Set the operating status of the remote head module
operation error remote head module is not in a STOP state. to STOP, and execute the request again.
4021H File related error The specified drive (memory) does not exist or there • Check the specified drive (memory) status.
is an error. • Back up data in the remote head module, and
then initialize the memory.
4022H File related error The file with the specified file name or file No. does Check the specified file name and file No.
not exist.
4023H File related error The file name and file No. of the specified file do not Delete the file and then recreate the file.
match.
4024H File related error The specified file cannot be handled by a user. Do not access the specified file.
4025H File related error The specified file is processing the request from Forcibly execute the request. Or, execute the
another engineering tool. request again after the processing being performed
ends.
4026H File related error The file password set in advance to the target drive Specify the file password set in advance, and then
(memory) must be specified. access to the drive (memory).
4 TROUBLESHOOTING
118 4.7 Error Codes
4027H File related error The specified range is larger than the file size. Check the specified range and access within that
range.
4028H File related error The same file already exists. Forcibly execute the request. Or, change the file
name and execute the request again.
4029H File related error The specified file capacity cannot be obtained. Review the specified file capacity, and execute the
request again.
402AH File related error The specified file is abnormal. Back up data in the remote head module, and then
initialize the memory.
402BH File related error The request cannot be executed in the specified Set the operating status of the remote head module
drive (memory). to STOP, and execute the request again.
402CH File related error The request cannot be executed currently. Execute the request again after a while.
4030H Device specification error The specified device is not supported. Check the specified device.
4031H Device specification error • The specified device number is out of range. • Check the specified device number. 4
• The remote head module does not support the • Check the specified device.
specified device.
4032H Device specification error The device modification was incorrectly specified. • Check the device modification method.
Or, the unusable device (TS, TC, SS, SC, CS, or • Check the specified device.
CC) was specified in any of the following SLMP/MC
protocol commands; Read random, Write random (in
units of words), Entry monitor device, or Execute
monitor.
4033H Device specification error Writing cannot be done because the specified device Do not write the data in the specified device, and do
is for system use. not turn on or off.
4034H Device specification error The dedicated instruction cannot be executed since Since the completion device for the SREAD or
the completion device for the dedicated instruction SWRITE instruction does not turn on in the remote
does not turn on. head module on the target station, execute the
instruction again after setting the operating status of
the remote head module on the target station to the
RUN status.
4040H Intelligent function module The request cannot be executed to the specified Check whether the specified module is the intelligent
specification error intelligent function module. function module having the buffer memory.
4041H Intelligent function module The access range exceeds the buffer memory range Check the start address and access number of
specification error of the specified intelligent function module. points and access using a range that exists in the
intelligent function module.
4042H Intelligent function module The specified intelligent function module cannot be • Check that the specified intelligent function
specification error accessed. module is operating normally.
• Check the specified module for a hardware fault.
4043H Intelligent function module The intelligent function module does not exist in the Check the I/O number of the specified intelligent
specification error specified position. function module.
4044H Intelligent function module A control bus error occurred during access to the Check the specified intelligent function module and
specification error intelligent function module. other modules and base units for a hardware fault.
4049H Intelligent function module A request cannot be processed because the module Turn off module ready (Yn+0) of the positioning
specification error extension parameter of the positioning module is module or execute the processing again after
being used for the positioning control. removing the extension parameter of the positioning
module from the target data.
4051H Protect error The specified drive (memory) cannot be accessed. Check that the drive (memory) can be used.
4052H Protect error The specified file attribute is read only, so the data Do not write data in the specified file. Or, change the
cannot be written. file attribute.
4053H Protect error An error occurred when writing data to the specified Check the specified drive (memory) and write data
drive (memory). again.
4054H Protect error An error occurred when deleting the data in the Check the specified drive (memory) and delete data
specified drive (memory). again.
4063H Online registration error The registered number of locked files exceeded the Execute the request again after the file access from
maximum value. another engineering tool ends.
4066H Online registration error The specified file password is incorrect. Check and specify the correct file password.
4067H Online registration error Monitor communication has failed. Execute again after checking the communication
route such as the communication cable.
4068H Online registration error Operation is disabled because it is being performed Execute the request again after the processing of
with another engineering tool. the function executed from another engineering tool
ends.
406AH Online registration error The drive (memory) number other than 4 was Check the drive and specify the drive number
specified. correctly.
4 TROUBLESHOOTING
4.7 Error Codes 119
406BH Online registration error Online operation was interrupted due to a remote Check the status of the remote head module by
head module error. executing the module diagnostics.
Identify the error, and take a corrective action
referring to the troubleshooting section.
4080H Any other error Request data error Check the request data that has been specified.
4082H Any other error The specified command cannot be executed Execute the command again after the processing of
because it is being executed. the command from another engineering tool ends.
408BH Any other error The remote request cannot be executed. • Change the status of the remote head module so
that the remote request can be executed, and
execute the request again.
• For remote operation, set the parameter to
"Enable remote reset".
40C0H Label communication error The specified label name does not exist. Check the label setting. If the "Access from External
Device" checkbox is not selected, check the
checkbox.
40C1H Label communication error Label access with a label name has failed because Specify the array element number within the set
the specified array element number is out of range. range.
40C2H Label communication error Label access with a label name has failed because Specify the label by bit specification, and access
the bit array type label is not specified by bit again.
specification.
40C3H Label communication error Label access with a label name has failed because Specify the label by word specification, and access
the word array type label is not specified by word again.
specification.
40C4H Label communication error Label access with a label name has failed because Reduce the number of labels in the program, and
the number of labels used in the program exceeded access the labels multiple times.
its limit.
40C8H Label communication error Registration of a label definition has failed because Reduce the number of registered labels with the
the number of registered labels reached its limit. "Access from External Device" checkbox selected.
40C9H Label communication error A label definition could not be registered because • Reduce the number of registered labels with the
the registration target memory capacity has been "Access from External Device" checkbox selected.
exceeded its limit. • Change the settings of the functions that use the
registration target memory.
40CAH Label communication error A label definition could not be changed, added, or Write the label communication data to the
deleted because the label communication data does programmable controller.
not exist in the remote head module.
40CBH Label communication error Data are not written to the CPU module because the Change the size of data written from the external
data type of the specified label does not match the device (SLMP/MC protocol device) so that it
size of the write data. matches the data type of the label in the specified
remote head module.
40CCH Label communication error Online program change has failed because the Write the global setting file and the global label
global setting file before modification and the global assignment information to the programmable
label assignment information do not match. controller together after modification.
40CEH Label communication error An attempt was made to access a label that cannot • Change the data type of the specified label to the
be accessed with a label name. one other than "Function Block" or "Pointer".
• Change the class of the specified label to the one
other than "VAR_GLOBAL_CONSTANT".
• Specify a device that is not being modified. (Bit-
specified word devices and digit-specified bit
devices can be specified.)
4100H Any other error Hardware failure of the remote head module. Replace the remote head module.
4108H Any other error The device monitor/test cannot be performed Execute the function again. Check that the access
normally. prohibited area is not accessed, and execute the
function again.
410CH Any other error Writing to the specified data is not supported. • Check that the version of the engineering tool
used is correct.
• Check the settings and make a correction.
4110H Remote head module error The request cannot be executed because a Reset the remote head module, and execute the
moderate or major error has occurred in the remote request again.
head module.
4121H File related error The specified drive (memory) or file does not exist. Execute again after checking the specified drive
(memory) or file.
4122H File related error The specified drive (memory) or file does not exist. Execute again after checking the specified drive
(memory) or file.
4 TROUBLESHOOTING
120 4.7 Error Codes
4123H File related error The specified drive (memory) is abnormal. Initialize the memory, and restore the drive (memory)
to its normal state.
4124H File related error The specified drive (memory) is abnormal. Initialize the memory, and restore the drive (memory)
to its normal state.
4125H File related error The specified drive (memory) or file is performing Execute again after a while.
processing.
4126H File related error The specified drive (memory) or file is performing Execute again after a while.
processing.
4127H File related error File password mismatch Execute again after checking the file password.
4128H File related error File password mismatch with copy destination Execute again after checking the file password.
4129H File related error The request cannot be executed since the specified Execute again after changing the target drive
drive (memory) is ROM. (memory).
412AH File related error The request cannot be executed since the specified Execute again after changing the target drive 4
drive (memory) is ROM. (memory).
412BH File related error The specified drive (memory) is write-inhibited. Execute again after changing the write inhibit
condition or drive (memory).
412CH File related error The specified drive (memory) is write-inhibited. Execute again after changing the write inhibit
condition or drive (memory).
412DH File related error The specified drive (memory) does not have enough Execute again after increasing the free space of the
free space. drive (memory).
412EH File related error The specified drive (memory) does not have enough Execute again after increasing the free space of the
free space. drive (memory).
412FH File related error The drive (memory) capacity differs between the Execute again after checking the drive (memory)
drive (memory) copy destination and copy source. copy destination and copy source.
4130H File related error The drive (memory) type differs between the drive Execute again after checking the drive (memory)
(memory) copy destination and copy source. copy destination and copy source.
4131H File related error The file name of the file copy destination is the same Execute again after checking the file names.
as that of the copy source.
4132H File related error The specified number of files does not exist. Execute again after checking the specified data.
4133H File related error The specified drive (memory) has no free space. Execute again after increasing the free space of the
drive (memory).
4134H File related error The attribute specification data of the file is wrong. Execute again after checking the specified data.
4135H File related error The date/time data of the engineering tool (personal Execute again after checking the clock setting of the
computer) is out of range. engineering tool (personal computer).
4136H File related error The specified file already exists. Execute again after checking the specified file name.
4137H File related error The specified file is read-only. Execute again after changing the condition of the
specified file.
4138H File related error Simultaneously accessible files exceeded the Execute again after decreasing file operations.
maximum.
4139H File related error The size of the specified file has exceeded that of Execute again after checking the size of the
the existing file. specified file.
413AH File related error The specified file has exceeded the already existing Execute again after checking the size of the
file size. specified file.
413BH File related error The same file was simultaneously accessed from Execute again after a while.
different engineering tools.
413CH File related error The specified file is write-inhibited. Execute again after changing the file condition.
413DH File related error The specified file capacity cannot be secured. Execute again after increasing the capacity of the
specified drive (memory).
413EH File related error Operation is disabled for the specified drive Execute again after changing the target drive
(memory). (memory).
413FH File related error The file is inhibited to be written to the file storage Execute again after changing the specified drive
area. (memory).
414CH Intelligent function module The specified buffer memory address cannot be Execute again after checking the buffer address.
specification error accessed.
4150H File related error An attempt was made to initialize the drive (memory) Do not initialize the target drive (memory) as it
protected by the system. cannot be initialized.
4151H File related error An attempt was made to delete the file/folder Do not delete the target file as it cannot be deleted.
protected by the system.
4 TROUBLESHOOTING
4.7 Error Codes 121
41C1H File related error The format information data of the specified drive • The file information data may be corrupted.
(memory) is abnormal. • Back up data in the remote head module, and
41C2H File related error File open specification data for file access is wrong. Execute again after checking the specification data.
41C3H File related error Simultaneously accessible files exceeded the Execute again after decreasing file operations.
maximum.
41C4H File related error Simultaneously accessible files exceeded the Execute again after decreasing file operations.
maximum.
41C5H File related error The specified file does not exist. Execute again after checking the file.
41C7H File related error The specified file or drive (memory) does not exist. Execute again after checking the file or drive
(memory).
41C8H File related error The size of the specified file has exceeded that of • Execute again after checking the size of the
the existing file. specified file.
• If the error recurs after re-execution, the file
information data may be corrupted.
• Back up data in the remote head module, and
41C9H File related error • Access to the file sector has failed. Back up data in the remote head module, and then
• The format information data of the target drive initialize the memory.
(memory) is abnormal.
41CAH File related error • Access to the file sector has failed. Back up data in the remote head module, and then
• The format information data of the target drive initialize the memory.
(memory) is abnormal.
41CBH File related error The file name is specified in a wrong method. Execute again after checking the file name.
41CCH File related error The specified file does not exist. Or, the specified Execute again after checking the name of the file
subdirectory does not exist. and subdirectory.
41CDH File related error An access to the file is prohibited in the system. • Do not access the specified file or subdirectory.
• Execute again after checking the file and
subdirectory.
41CEH File related error The file cannot be written because the specified file Execute again after checking the attribute of the
is read-only. specified file.
41CFH File related error The specified drive (memory) has been used Execute again after checking the drive (memory)
exceeding the capacity. capacity.
41D0H File related error The specified drive (memory) has no free space. Or, • Execute again after increasing the free space of
the number of files in the directory of the specified the drive (memory).
drive (memory) has exceeded the maximum. • Delete files in the drive (memory), and execute the
function again.
41D1H File related error The file name is specified in a wrong method. • Execute again after checking the file name.
• If the error recurs after re-execution, the file
information data may be corrupted.
• Back up data in the remote head module, and
41D5H File related error The file of the same name exists. Forcibly execute the request, or execute after
changing the file name.
41D6H File related error The format information data of the specified drive • The file information data may be corrupted.
41D7H File related error The format information data of the specified drive • The file information data may be corrupted.
41D8H File related error The specified file is being accessed. Execute again after a while.
41DFH File related error The specified drive (memory) is write-protected. Execute again after canceling the write protect of the
specified drive (memory).
41E0H File related error The specified drive (memory) is abnormal or does Back up data, and then initialize the memory.
not exist.
41E1H File related error Access to the SD memory card has failed. Back up data, and then write the data to the data
memory.
41E7H File related error The format information data of the specified drive • The file information data may be corrupted.
41E8H File related error The format information data of the specified drive • The file information data may be corrupted.
4 TROUBLESHOOTING
122 4.7 Error Codes
41E9H File related error The specified file is being accessed. Execute again after a while.
41EBH File related error The file name is specified in a wrong method. Execute again after checking the file name.
41ECH File related error The file system of the specified drive (memory) is • The file information data may be corrupted.
logically corrupted. • Back up data in the remote head module, and
41EDH File related error The specified drive (memory) does not have Execute again after deleting unnecessary files.
continuous free space. (The free space for file is
sufficient but the continuous free space is
insufficient.)
41F3H File related error The file size is larger than the following: Specify a smaller value for the file size when
• the value to be acquired when 2 bytes are creating a file or changing the file size. Alternatively,
subtracted from 4G bytes. divide the file so that each file size is smaller.
41F4H File related error The request cannot be executed because the
operation is prohibited by the system.
Do not request the file operation because it is
prohibited by the system. 4
41FBH File related error The specified file is already being manipulated from Execute again after the currently performed
the engineering tool. operation is completed.
41FCH File related error An attempt was made to initialize the drive (memory) Stop all accesses to the specified drive (memory),
being used. and execute the request again.
41FDH File related error There are no data written to the data memory. Write all the required files to the programmable
controller.
4202H Online module change The request cannot be executed because the • Execute the request again after the online module
function error specified module is being changed online. change processing ends.
• If the online module change operation cannot be
completed, power off the system, and change the
module.
4220H Online module change The remote head module does not support for the Execute the online module change by using the
function error specified method of online module change. method that can be used in the current system
configuration.
4240H Redundant system related The following operations is requested to the remote Perform these operations to the remote head
error head module in the standby system, but cannot be module in the control system.
performed because they are not supported.
• System switching
4241H Redundant system related Data communications cannot be performed with the Check that there is no error or failure in the remote
error other system because of any of the following head module of the other system, and perform a
reasons: retry. If the same error code is displayed again, the
• The remote head module of the other system is in possible cause is a hardware failure of the remote
a reset state. head module. Please consult your local Mitsubishi
• Hardware failure of the remote head module of the representative.
other system
4243H Redundant system related The request cannot be executed because a Check the moderate or major error, eliminate the
error moderate or major error has occurred in the remote error cause, and then execute the request again.
head module of the standby system.
4244H Redundant system related The request cannot be executed because the Match the operating status of the remote head
error operating status of the remote head module in the module between the systems, and execute the
control system differs from that of the remote head request again.
module in the standby system.
4246H Redundant system related The request cannot be executed because the Execute the request again after the system
error systems are being switched. switching processing ends.
4247H Redundant system related The request cannot be executed because the Execute the request again after the memory copy
error memory copy function is being executed. processing ends. The completion status can be
checked in the following special relay areas.
• SM1654 (Memory copy being executed): Off
• SM1655 (Memory copy completion): On
4248H Redundant system related Data communications cannot be performed with the Check the following, and execute the request again.
error system specified as a connection destination • The system switching processing has completed.
(request destination module I/O number) because of • The redundant system has started up
either of the following reasons: successfully.
• The request was issued during the system
switching processing.
• The system specified as a connection destination
(request destination module I/O number) does not
exist.
4 TROUBLESHOOTING
4.7 Error Codes 123
4249H Redundant system related The request cannot be executed because the Determine the control system or standby system
error system setting (control system or standby system) (start up the system as the redundant system
has not been determined (the system has not been normally), and execute the request again. Or, do not
started up as the redundant system). specify any connection destination system (request
destination module I/O number), and execute the
request again.
424AH Redundant system related The request cannot be executed because the PLC Do not specify any connection destination system
error No.1, PLC No.2, control system, or standby system (request destination module I/O number), and
is set as a connection destination (request execute the request again.
destination module I/O number).
424BH Redundant system related The request cannot be executed because system Perform either of the following operations to enable
error switching is disabled because of the following system switching, and execute the request again.
reasons: • Turn on SM1646 (System switching by a user).
• SM1646 (System switching by a user) is off.
424FH Redundant system related The request cannot be executed because system Check that the systems are switched successfully. If
error switching due to a different cause was executed not, monitor SD1644 (Cause of system switching
during execution of system switching by the failure), eliminate the error cause, and then execute
engineering tool. the function again.
425AH Redundant system related The request cannot be executed because the Start up the system as the redundant system
error system has not operated as the redundant system normally, execute the function again.
4269H Any other error The remote RUN (function) cannot be executed. Execute the function again after a while.
433CH Maintenance and inspection The error was not cleared. (Error clear was Execute again after a while.
error performed during execution of error clear.) If the same error code is displayed again, the
possible cause is a hardware failure of the target
representative.
4400H Security function error A file protected by a password has been opened Enter a correct password and perform password
without unlocking the password. authentication.
4401H Security function error • Read password authentication has failed when • Set a correct read password and perform
required. password authentication.
• The file password format is incorrect. • Access the file with the correct method.
4402H Security function error • Write password authentication has failed when • Set a correct write password and perform
required. password authentication.
• The file password format is incorrect. • Access the file with the correct method.
4403H Security function error Both passwords for reading and for writing that are Set correct passwords for both reading and writing,
set upon Create, Change, Delete, or Disable do not and perform password authentication.
match the previous ones.
4404H Security function error A file error was detected before or after performing • Initialize the drive including the target file by
Create, Change, or Delete. initializing the memory.
• Write the target file to the programmable controller
again, and then register or cancel the file
password.
4408H Security function error Password authentication failed when access was Set a correct password and perform password
required. authentication again.
4409H Security function error Password authentication failed when access was Set a correct password and perform password
required. authentication again 1 minutes later.
440AH Security function error Password authentication failed when access was Set a correct password and perform password
440BH Security function error Password authentication failed when access was Set a correct password and perform password
440CH Security function error Password authentication failed when access was Set a correct password and perform password
440DH Security function error Password authentication failed when access was Set a correct password and perform password
440EH Security function error The security function was activated and password Set a correct password and perform password
authentication cannot be performed. authentication again after a certain period of time.
4500H Remote head module error The request cannot be executed because the The request cannot be executed because it is not
system is in the redundant line configuration. supported by the redundant line configuration.
4501H Remote head module error The system cannot be switched because the Execute again after eliminating the network error in
network error is occurring in the remote head the remote head module of the standby system.
module of the standby system.
4905H Any other error The capacity of label area used exceeded its limit. Delete the unused global label definitions, compile
the program, and then write the program to the
programmable controller.
4 TROUBLESHOOTING
124 4.7 Error Codes
4A00H Network error • Access to the specified station cannot be made • Set to the related stations the routing parameters
since the routing parameters are not set to the for access to the specified station.
start source CPU module and/or relay CPU • Retry after a while. Or, start communication after
module. checking that the system for data routing has
• For routing via a multiple CPU system, the control started.
CPU of the network module for data routing has • Do not use the same third octet of the IP address
not started. (network number) specified for the IP
• The third octet of the IP address (network number) communication test with that of the remote head
specified for the IP communication test is the module where the test is executed.
same as that of the remote head module where • Set the CPU module that performs IP packet
the test is executed. transfer as the control CPU of the CC-Link IE
• The CPU module that performs IP packet transfer module, which is on the path that IP packets
is not the control CPU of the CC-Link IE module, travel.
which is on the path that IP packets travel.
4A01H Network error • The network of the number set to the routing • Check and correct the routing parameters set to 4
parameters does not exist. the related stations.
• The specified CPU module cannot be • Set communication through the network that is
communicated through the network that is not supported by the specified CPU module.
supported by the CPU module.
4A02H Network error Access to the specified station cannot be made. • Check the network module for error, or check that
the modules are not in offline.
• Check if the network numbers/PC numbers are
correctly set.
4A03H Network error A request for network test was issued. Check the request of the SLMP/MC protocol.
4A20H IP communication test error • The first octet and second octet of the IP • Check and correct the IP address settings of the
addresses do not match between the CPU module CPU module.
and the request destination device on the same • Check and correct the IP address of the request
path that IP packets travel. destination device.
• The first octet and second octet of the IP • Check and correct the IP address of the CC-Link
addresses do not match between the CPU module IE module.
and the CC-Link IE module on the same path that • Check and correct the IP address of the request
IP packets travel. source device.
• The first octet and second octet of the IP
addresses do not match between the CC-Link IE
modules on the same path that IP packets travel.
• The first octet and second octet of the IP
addresses do not match between the request
source device and the CPU module connected to
the request destination device by Ethernet.
4A22H IP communication test error The IP address is not set to the CC-Link IE module • Set the IP address to the CC-Link IE module used
on the path that IP packets travel. as a master station or control station.
• Check the communication status with the master
station or control station when the CC-Link IE
module is used as a local station or normal station.
• Replace the CC-Link IE module (master station or
control station) with the one that supports the IP
packet transfer function.
• Conduct the IP communication test again after the
CC-Link IE module is started up.
• Check and correct the IP address of the request
destination device.
4A23H IP communication test error • The CPU module on the path that IP packets • Replace the CPU module with the one supporting
travel does not support the IP packet transfer the IP packet transfer function.
function. • Correct routing parameter so that IP packets are
• Routing parameters are set so that IP packets are routed to the CPU module that supports the IP
routed to CPU modules that are incompatible with packet transfer function.
IP packet transfer. • Check and correct the IP address of the request
destination device.
4 TROUBLESHOOTING
4.7 Error Codes 125
4A24H IP communication test error • The network module on the path that IP packets • Replace the CC-Link IE module with the one
travel does not support the IP packet transfer supporting the IP packet transfer function.
function. • Correct routing parameter so that IP packets are
• Routing parameters are set so that IP packets are routed to the CC-Link IE module that supports the
routed to the network module that does not IP packet transfer function.
support the IP packet transfer function. • Check and correct the setting so that the third
• The third octet (Network No.) of the IP address of octet (Network No.) of the IP address of the device
the device on the path that IP packets travel is on the path that IP packets travel does not overlap
overlapping with the network No. of the module with the network No. of the module connected to
connected to the CPU module and does not the CPU module and does not support the IP
support the IP packet transfer function. packet transfer function.
• The third octet (Network No.) of the IP address of • Check and correct the setting so that the third
the request destination device is overlapping with octet (Network No.) of the IP address of the
the network No. of the module connected to the request destination device does not overlap with
CPU module and does not support the IP packet the network No. of the module connected to the
transfer function. CPU module and does not support the IP packet
transfer function.
• Check and correct the IP address of the request
destination device.
4A25H IP communication test error • The IP packet transfer setting is not set in the CPU • In the CPU module, select "Use" for the IP packet
module or the Ethernet module connected with the transfer function setting in the CPU parameters.
request source device. • In the Ethernet module, select "Use" for the IP
• Routing parameters are set so that IP packets are packet transfer function setting in the module
routed to the CPU module where IP packet parameters.
transfer setting is not set. • Correct routing parameters so that IP packets are
• The Ethernet module is not mounted with the routed to the CPU module where IP packet
remote head module. transfer setting is set.
• In the Ethernet module, "Disable" is selected for • Check and correct the IP address of the request
"Communications by Network No./Station No." destination device.
under "Own Node Settings" of "Module • Mount the Ethernet module with the remote head
Parameter". module.
• In the Ethernet module, the third octet (network • Select "Enable" for "Communications by Network
No.) of the IP address and the network number No./Station No." under "Own Node Settings" of
are not the same in "Own Node Settings" of "Module Parameter" in the Ethernet module.
"Module Parameter". Or, the fourth octet of the IP • Check and correct the network number and
address and the station number are not the same. station number of the Ethernet module.
4A27H IP communication test error The CPU module that performs IP packet transfer is Set the CPU module that performs IP packet transfer
not the control CPU of the CC-Link IE module, which as the control CPU of the CC-Link IE module, which
is on the path that IP packets travel. is on the path that IP packets travel.
4A28H IP communication test error In the remote head module, the request path and the Correct the routing parameter setting so that IP
response path of IP packets differ. packets travel the same path for both request and
response transmission.
4A29H IP communication test error The third octet (network No.) of the IP address of the • Check and correct the IP address settings of the
request destination device is overlapping with the Ethernet module.
request source device and third octet (network No.) • Check and correct the IP address of the request
of the IP address of the Ethernet module. destination device.
4A2AH IP communication test error An IP address of a device on CC-Link IE Controller Specify an IP address of a device on CC-Link IE
Network or CC-Link IE Field Network or that of the Controller Network or CC-Link IE Field Network or
CPU module is not specified. that of the CPU module.
4B00H Target module error • An error occurred in the access destination or the • Check the error occurred in the specified access
relay station. destination or the relay station, and take an action.
• The specified connection destination (request • Check the connection destination (request
destination module I/O number) is incorrect. destination module I/O number or request
• The CPU module or remote head module of the destination station number (PC number)) in the
access destination has not started up. request data of SLMP/MC protocol.
• Check the stop error in the CPU module or the
moderate or major error in the remote head
module, and take an action.
4B02H Target module error The request is not addressed to the remote head Perform operation for the module that can execute
module. the specified function.
4B03H Target module error • The specified route is not supported by the • Check whether the specified route is supported or
specified CPU module or remote head module not.
version. • Check the mounting status of the CPU module or
• The communication target CPU module or remote remote head module.
head module is not mounted. • Check the stop error in the CPU module or the
moderate or major error in the remote head
module, and take an action.
4 TROUBLESHOOTING
126 4.7 Error Codes
4B04H Target module error The specified connection destination (request An invalid value is set as the start I/O number of the
destination module I/O number) is not supported. connection target module. Set the start I/O number
of the target module correctly, and retry data
communications.
Error codes of CC-Link IE Field Network (D000H to DFFFH)

For the error messages, error details and causes, and action of the error codes (D000H to DFFFH), refer to the following.
4 TROUBLESHOOTING
4.7 Error Codes 127
4.8 List of Parameter Numbers
This section lists parameter numbers.
System Parameter
The following is the list of parameter numbers of system parameters.
Item Parameter No.
I/O Assignment Base/Power/Extension Cable Setting Slots 0201H
Base, Power Supply Module, Extension Cable 0203H
I/O Assignment Setting Points, Start XY, Module Status Setting 0200H
Control PLC Settings 0202H
Module Name 0203H
Remote head Module Operation Setting at Error Detection 3600H
Setting of Points Occupied by Empty Slot 0100H
Inter-module Synchronous Select Inter-module Synchronous Target Module 0101H
Setting
Fixed Scan Interval Setting of Inter-module Synchronization 0101H
CPU Parameter
The following is the list of parameter numbers of the CPU parameter.
Item Parameter No.
Name Setting Title Setting 3100H
Comment Setting 3101H
Operation Related Setting Remote Reset Setting 3202H
RAS Setting Error Detection Setting 3501H
Remote head Module Operation Setting at Error Detection 3501H
Online module change setting Direct change setting 3505H
Network Required Setting Network No. 6D00H
Station No. 6D00H
Network Application Setting Module Operation Mode 6D00H
Transfer Setting between Devices 6D01H
Redundant System Settings Line Type 6D02H
4 TROUBLESHOOTING
128 4.8 List of Parameter Numbers
4.9 Event List
The remote head module collects information from each module such as errors detected by the module, operations performed
for the module, and stores it in the data memory. ( Page 34 RAS Function) When an event occurs, its event code and
description can be read using an engineering tool.
For details on events occurred on each module, refer to the manual for the module used.
How to read the event list

The event list contains the following information.
4
Item Description
Event code ID number assigned to an event
Event type Type of an event
Event category Category of an event
Detected event Description of a detected event
Detailed information 1 to 3 Details of a detected event
Detailed information
The following table lists the details of information displayed in the detailed information 1 to 3.
Detailed Item Description
information
Detailed information Operation source information Information on the operation source
1 • Connection port (such as Ethernet and USB)
• I/O No.
• Remote head No.
• Network No.
• Station No.
• IP address
Own station information Information on the own station
• I/O No.
• Network No.
• Station No.
System switching information Information on the system switching cause, the cause of system switching failure,
and the transition state of the systems (control system and standby system)
4 TROUBLESHOOTING
4.9 Event List 129
Detailed Item Description
information
Detailed information Start instruction issuing source Information on the start instruction issuing source
2 • Network No.
• Station No.
Error-detected station information Information on the error-detected station
• Error occurrence port
• All receive frame count
• Error frame count
Cause of baton pass interruption 'Cause of baton pass interruption' (SW0048)
Cause of data link stop 'Cause of data link stop' (SW0049)
(Except for the stop by the data link stop instruction.)
Remote password information Information on the corresponding remote password
• I/O No.
• Result
• Connection No.
File password information Information on the corresponding file password
• Operation
• Result
• Memory (drive No.)
• File name
Drive/file information Information on the corresponding drive name and file name
• Drive No.
• File name/folder name
Copy source drive/file information Information on the corresponding drive name and file name
• Drive No.
• File name
Operation target information Information on the operation target: I/O number
Remote operation type information Information on the remote operation type
System configuration information Information on the system configuration
Setting/change information Information on the setting and change
Cause of parameter change Cause of parameter change
System switching information Information on the system switching cause, the cause of system switching failure,
and the transition state of the systems (control system and standby system)
Detailed information Copy destination drive/file information Information on the corresponding drive name and file name
3 • Drive No.
• File name
4 TROUBLESHOOTING
130 4.9 Event List
Event list
The following table lists events related to the remote head module.
Event Event Event Detected event Description Detailed information
code type category Detailed Detailed Detailed
information 1 information 2 information 3
00100 System Info Link-up Link-up has occurred when the Operation  
network cable connected to the source
external device was connected. information
00400 Power-on and reset The remote head module has been 
power-on or reset.
00420 Event history file A event history file has been
00500
generation
<<Own station>>
generated.
Baton pass of the own station was Own station
4
Baton pass return returned from interruption status to information
normal status.
00510 <<Own station>> Data Data link of the own station was 
link restart restarted.
00513 <<Own station>> Data Data link startup of the own station Own station Start instruction
link start instruction instruction was received. information issuing source
acceptance
00514 <<Own station>> Data Data link stop instruction of the own
link stop instruction station was received.
acceptance
00520 <<Own station>> Temporary error invalid station setting 
Temporary error invalid instruction was received.
station setting
instruction acceptance
00521 <<Own station>> Temporary error invalid station cancel
Temporary error invalid instruction was received.
station cancel
00530 <<Own station>> Reserved station cancel setting
Reserved station instruction was received.
cancel setting
00531 <<Own station>> Reserved station enable setting
Reserved station instruction was received.
enable setting
00542 <<Own station>> A receive frame error (line status: Error-detected
Receive frame error caution level) has been occurred. station
line status caution information
level
00750 Network number or Network number or station number of Operation Setting/change
station number is not the own station is not set. source information
set. information
4 TROUBLESHOOTING
4.9 Event List 131
00800 System Warning Link-down Link-down has occurred when Operation  
network cable connected to the source
external device was disconnected. information
00C00 <<Own station>> Baton pass of the own station was Own station Cause of baton
Baton pass interruption interrupted. information pass interruption
00C10 <<Own station>> Data Data link of the own station was Cause of data
link stop stopped. link stop
00C28 <<Own station>> A receive frame error (line status: Error-detected
Receive frame error warning level) has been occurred. station
line status warning information
level
00F00 System switching (by The system switching cause had System 
the system) been generated by the system, and switching
the systems were switched. information
00F01 Automatic memory Memory copy from control system to 
copy (control system) standby system has been executed.
00F02 Automatic memory Memory copy from control system to
copy (standby system) standby system has been executed.
10200 Security Info Remote password lock The lock processing for the remote Operation Remote
password was performed. source password
information information
10201 Remote password The lock processing for the remote
unlock successful password was performed and
completed successfully.
10202 Remote password The lock processing for the remote
unlock failed password was performed and was not
completed successfully.
10400 File password Registration, change, or deletion of a File password
registration/change/ file password was performed and information
deletion successful completed successfully.
10401 File password Registration, change, or deletion of a
registration/change/ file password was performed and was
deletion failed not completed successfully.
10402 Security Info File password clear Clear of a file password was Operation File password
successful performed and completed source information
successfully. information
10403 File password clear Clear of a file password was
failed performed and was not completed
successfully.
4 TROUBLESHOOTING
132 4.9 Event List
20100 Operation Info Error clear Error clear was performed. Operation Operation target 
source information
information
20200 Event history clear The event history was cleared. 
24001 Remote operation A remote operation request (RUN or Remote
request accepted STOP) was accepted. operation type
information
24031 Network number, Setting or change of the network  Setting/change
station number setting/ number or station number of the own information
change execution station was executed.
24052 <<Own station>> The parameter was changed or newly Own station Cause of
Parameter change/
new parameter
accepted at power-on. information parameter
change
4
acceptance
24100 Operating status The operating status was changed to  
change (RUN) RUN.
24101 Operating status The operating status was changed to
change (STOP) STOP.
24150 CPU operating status The CPU operating status of the
change of the master master station was changed to RUN.
station (RUN)
24151 CPU operating status The CPU operating status of the
change of the master master station was changed to STOP.
station (STOP)
24200 Creation of new • A new folder was created. Operation Drive/file
folders, writes to files/ • A new file was created or data was source information
folders*1 written to a file. information
24201 File copy*1 A file was copied. Copy source Copy
24202 Folder/file rename*1 drive/file destination
A folder name or file name was
information drive/file
changed.
information
25000 Online module change The online module change System 
processing has completed. configuration
information
2A200 Warning Memory initialization The memory was initialized. Drive/file
2A202 Folder/file deletion*1 information
A folder or file was deleted.
2B000 System switching The system switching cause had System
(user) been generated by a user, and the switching
systems were switched. information
*1 For file-related events such as write to and deletion of files, operations for the parameter files are logged into the event history.
4 TROUBLESHOOTING
4.9 Event List 133
APPENDICES
Appendix 1 List of Link Special Relay (SB) Areas
The link special relay (SB) is turned on/off depending on various factors during data link. An error status of the data link can be
checked by monitoring it.
Application of the link special relay (SB)

By using the link special relay (SB), the status of CC-Link IE Field Network can be checked from HMI (Human Machine
Interfaces) as well as the engineering tool.
Ranges turned on/off by users and by the system

• Turned on/off by users: SB0000 to SB001F
• Turned on/off by the system: SB0020 to SB0FFF
APPX
134 Appendix 1 List of Link Special Relay (SB) Areas
List of link special relay (SB) areas
The following lists the link special relay (SB) areas.
Do not turn on or off areas whose numbers are not on the list or ranges turned on/off by the system. Doing so
may cause malfunction of the programmable controller system.
No. Name Description

SB0006 Clear communication error count Clears the link special register areas related to communication errors (SW0074 to SW0077, SW007C to
SW007F) to 0.
Off: Clear not requested
On: Clear requested (valid while on)
SB0046 Station number setting status of Stores the station number setting status.
own station Off: Station number set
On: Station number not set
If parameters are set using the engineering tool, this relay is always OFF.
SB0047 Baton pass status of own station Stores the baton pass status (transient transmission availability) of the own station.
Off: Normal
On: Error
When this relay is turned on, the cause of the error can be checked with 'Baton pass status of own station'
(SW0047) and 'Cause of baton pass interruption' (SW0048).
Depending on the link refresh timing, the update of 'Baton pass status of own station' (SW0047) and 'Cause
of baton pass interruption' (SW0048) may be offset by one sequence scan.
SB0049 Data link error status of own station Stores the data link error status of the own station.
Off: Normal
On: Error
When this relay is turned on, the cause of the error can be checked with 'Cause of data link stop' (SW0049).
Depending on the link refresh timing, the update of 'Cause of data link stop' (SW0049) may be offset by one
sequence scan.
(Conditions)
• This relay is enabled when 'Baton pass status of own station' (SB0047) is off.
• When 'Baton pass status of own station' (SB0047) is turned on (error), data prior to error is held.
SB004A Minor error status of own station Stores the minor error occurrence status of the own station.
Off: No minor error
A
On: Minor error
SB004B Moderate/major error status of own Stores the moderate/major error occurrence status of the own station.
station Off: No moderate/major error
On: Moderate/major error
SB004C Operation status of own station Stores the operating status of the own station.
Off: RUN
On: STOP or moderate/major error
SB004F Station number status of the Stores information on whether the module is operating with the network number and station number set in
operating station the "Network Required Setting" of "CPU Parameter", or with the numbers set in the CC-Link IE Field
Network diagnostics.
Off: Operating using the values set in "Network Required Setting" of "CPU Parameter"
On: Operating using the values set in the CC-Link IE Field Network diagnostics (When no parameter is set
in the remote head module, or no station number has been set in the CC-Link IE Field Network
diagnostics after the network and station number fields are left blank in "Network Required Setting" of
"CPU Parameter".)
(Conditions)
SB006A PORT1 link-down status of own Stores the link down status of the own station P1 side.
station Off: Link-up
On: Link-down
The time that link-up starts after power-on or Ethernet cable connection may vary. Normally link-up takes
several seconds. Note, however, that the time may be extended further if the link-up processing is repeated
depending on the status of the device on the line.
SB006B PORT2 link-down status of own Stores the link down status of the own station P2 side.
station Off: Link-up
On: Link-down
The time that link-up starts after power-on or Ethernet cable connection may vary. Normally link-up takes
several seconds. Note, however, that the time may be extended further if the link-up processing is repeated
depending on the status of the device on the line.
APPX
Appendix 1 List of Link Special Relay (SB) Areas 135
SB006C PORT1 current error frame Stores if a receive frame error line status caution level is currently occurring in the P1 side of the own station.
reception status of own station (1) Off: A receive frame error line status caution level is not occurring.
On: A receive frame error line status caution level is occurring.
SB006D PORT2 current error frame Stores if a receive frame error line status caution level is currently occurring in the P2 side of the own station.
reception status of own station (1) Off: A receive frame error line status caution level is not occurring.
On: A receive frame error line status caution level is occurring.
SB006E PORT1 error frame reception Stores if a receive frame error line status caution level has occurred in the P1 side of the own station from
detection status of own station power-on until the present.
(latch) (1) Off: A receive frame error line status caution level has not yet occurred.
On: A receive frame error line status caution level has occurred.
SB006F PORT2 error frame reception Stores if a receive frame error line status caution level has occurred in the P2 side of the own station from
detection status of own station power-on until the present.
(latch) (1) Off: A receive frame error line status caution level has not yet occurred.
On: A receive frame error line status caution level has occurred.
SB007C Line type setting status Stores the setting status of line types when the redundant system was configured.
Off: Single Line
On: Redundant Line
The relay turns off for the configuration other than the redundant system.
SB00F1 CPU operating status of master Stores the operating status of the CPU module on the master operating station.
station*1 Off: RUN
On: STOP state, PAUSE state, or moderate/major error
(Conditions)
SB0101 CPU moderate/major error status Stores the moderate/major error occurrence status of the CPU module on the master operation station.
of master station*1 Off: No moderate/major error
On: Moderate/major error
(Conditions)
SB0111 CPU minor error status of master Stores the minor error occurrence status of the CPU module on the master operating station.
station*1 Off: No minor errors, or a moderate/major error being occurred
On: Minor error
(Conditions)
SB01E9 Inter-module synchronization cycle Stores the cycle over occurrence status of the inter-module synchronization function. This relay is turned on
over flag if link scan is not completed within the inter-module synchronization cycle.
Off: Processing time overflow has not occurred.
On: Processing time overflow has occurred.
Once this relay is turned on, it remains turned on even if the processing is operated within the specified
inter-module synchronization cycle. The status is cleared by turning off and on the power supply or resetting
the remote head module.
SB01EE Redundant function information of Stores the redundant system support information of the own station.
own station Off: Redundant function not supported
On: Redundant function supported
SB1000 Areas for the CC-Link master/local By setting these areas as the refresh target device of the link special relay (SB) of the CC-Link master/local
to module module, the data link status of CC-Link can be checked.
SB1FFF
*1 The information is updated when the master station is connected.
APPX
136 Appendix 1 List of Link Special Relay (SB) Areas
Appendix 2 List of Link Special Register (SW) Areas
The link special register (SW) stores the information during data link as a numerical value. Error locations and causes can be
checked by monitoring the link special register (SW).
Application of the link special register (SW)

By using the link special register (SW), the status of CC-Link IE Field Network can be checked from HMI (Human Machine
Interfaces) as well as the engineering tool.
Range where data are stored by users and range where data are stored by the system
• Stored by users: None
• Stored by the system: SW0020 to SW0FFF
List of link special register (SW) areas

The following lists the link special register (SW) areas.
Do not write any data to an area whose number is not on the list or range where data are stored by the
system. Doing so may cause malfunction of the programmable controller system.

SW0040 Network number Stores the network number of the own station.
Range: 1 to 239
SW0042 Station number Stores the station number of the own station.
Range: 1 to 120, 255 (station number not set)
SW0043 Mode status of own Stores the module operation mode of the own station.
station 00H: Online mode
02H: Offline mode
0BH: Module communication test mode
A
SW0047 Baton pass status of Stores the baton pass status (transient transmission availability) of the own station.
own station 0: Data link in progress
2: Baton pass in progress
3: Baton pass being terminated
4: Test in progress
5: Offline
SW0048 Cause of baton pass Stores the cause of interruption in the communication (baton pass) of the own station.
interruption 00H: At normal communication or power-on
30H: Cable disconnection
33H: Disconnection or return in progress
40H: Offline mode
SW0049 Cause of data link stop Stores the cause which stopped the data link of the own station.
This register is disabled for offline mode.
00H: At normal communication or power-on
01H: Stop direction
02H: Monitoring time timeout
10H: Parameter unreceived
11H: Station number of the own station out of the range
12H: Reserved station setting of the own station
13H: Own station number duplication
16H: Station number not set
18H: Parameter error
19H: Parameter communication in progress
1AH: Station type mismatch
1BH: Parameter mismatch
20H: Moderate/major error
SW004A Data link stop request Stores the station number of the station that performed the data link stop request for the own station.
station Range: 1 to 120, 125 (master station)
The data link stop request is performed by 'System link stop' (SB0003) from the station stored in SW004A.
(Conditions)
• This register is enabled when 'Baton pass status of own station' (SB0047) is off.
APPX
Appendix 2 List of Link Special Register (SW) Areas 137
SW004B Module status of own Stores the status of the own station.
station No value is stored for offline mode.
01H: STOP (normal)
02H: STOP (moderate/major error)
03H: STOP (minor error)
04H: RUN (normal)
05H: RUN (minor error)
0FH: Initial processing
SW004E Network No. set for Stores the network number set in the CC-Link IE Field Network diagnostics.
diagnostics Range: 1 to 239, 65535 (not set)
SW004F Station No. set for Stores the station number set in the CC-Link IE Field Network diagnostics.
diagnostics Range: 1 to 120, 65535 (not set)
SW0064 Connection status of Stores the connection status of the own station.
own station 00H: Normal (communication in progress on P1 and P2)
01H: Normal (communication in progress on P1, cable disconnected on P2)
04H: Normal (loopback communication in progress on P1, cable disconnected on P2)
10H: Normal (cable disconnected on P1, communication in progress on P2)
11H: Disconnecting (cable disconnected on P1 and P2)
12H: Disconnecting (cable disconnected on P1, establishing line on P2)
21H: Disconnecting (establishing line on P1, cable disconnected on P2)
22H: Disconnecting (establishing line on P1 and P2)
40H: Normal (cable disconnected on P1, loopback communication in progress on P2)
SW0074 PORT1 cable Stores the cumulative count that was detected for cable disconnections at the P1 side.
disconnection detection When 'Clear communication error count' (SB0006) is turned on, the stored value for the number of errors is cleared.
count When FFFFH (maximum value 65535) is counted, the value returns to 0 and the module continues to count.
SW0075 PORT1 receive error Stores the cumulative count that error data was received at the P1 side.
detection count The count stores only error data that is not transmitted to all stations.
When 'Clear communication error count' (SB0006) is turned on, the stored value for the number of errors is cleared.
When FFFFH (maximum value 65535) is counted, counting stops.
SW0076 PORT1 total no. of Stores the cumulative count that data was received at the P1 side.
received data (lower 1 When 'Clear communication error count' (SB0006) is turned on, the stored value for the number of errors is cleared.
word) When FFFFFFFFH (maximum value 4294967295) is counted, counting stops.
SW0077 PORT1 total no. of
received data (upper 1
word)
SW007C PORT2 cable Stores the cumulative count that was detected for cable disconnections at the P2 side.
disconnection detection When 'Clear communication error count' (SB0006) is turned on, the stored value for the number of errors is cleared.
count When FFFFH (maximum value 65535) is counted, the value returns to 0 and the module continues to count.
SW007D PORT2 receive error Stores the cumulative count that error data was received at the P2 side.
detection count The count stores only error data that is not transmitted to all stations.
When 'Clear communication error count' (SB0006) is turned on, the stored value for the number of errors is cleared.
When FFFFH (maximum value 65535) is counted, counting stops.
SW007E PORT2 total no. of Stores the cumulative count that data was received at the P2 side.
received data (lower 1 When 'Clear communication error count' (SB0006) is turned on, the stored value for the number of errors is cleared.
word) When FFFFFFFFH (maximum value 4294967295) is counted, counting stops.
SW007F PORT2 total no. of
received data (upper 1
word)
SW01E9 Inter-module Stores the cumulative count that a link scan could not complete an Inter-module synchronization cycle.
synchronization cycle The stored count is cleared by turning off and on the power supply or resetting the remote head module.
over count When FFFFH (maximum value 65535) is counted, counting stops.
SW1000 Areas for the CC-Link By setting these areas as the refresh target device of the link special register (SW) of the CC-Link master/local
to master/local module module, the data link status of CC-Link can be checked.
SW1FFF
APPX
138 Appendix 2 List of Link Special Register (SW) Areas
Appendix 3 List of Special Relay (SM) Areas
The following table shows how to read the special relay (SM) list.
Item Description
No. Special relay number
Name Special relay name
Data stored Data stored in the special relay and its meaning
Details Detailed description of the data stored
Set by (setting timing) Set side of data (system or user) and timing when data is set by the system
<Set by>
• S: System
• U: User (via network or by test operation from an engineering tool).
• U/S: User and system
<Set timing>
• Every END: Data is set every time END processing is performed.
• Initial: Data is set when initial processing is performed (e.g. powering on the system, changing the operating status from
STOP to RUN).
• Status change: Data is set when the status is changed.
• Error: Data is set when an error occurs.
• Request: Data is set when requested by a user (using the special relay).
• Writing: Data is set when a user performs a writing operation.
• Power-on to RUN or STOP to RUN: Data is set when the operating status changes from power-on to RUN or from
STOP to RUN.
• Copy start: Data is set when memory copy is started.
• Copy end: Data is set when memory copy is completed.
Do not change the values of special relay set by the system by an engineering tool. Doing so may result in
system down or communication failure.
Diagnostic information
The following table lists the special relay areas relating to the diagnostic information.
A
No. Name Data stored Details Set by (setting timing)
SM0 Latest self-diagnostic error Off: No error • This relay is turned on when the self- S (Error)
On: Error diagnostics returns an error.
• The ON state is maintained even after the
error has been later cleared.
SM1 Latest self-diagnostic error Off: No error • This relay is turned on when the self- S (Error)
On: Error diagnostics returns an error.
error has been later cleared.
SM50 Error clear OffOn: Error clear request • This relay clears the error state when the U/S (Status change)
OnOff: Error clear mode transfers from off to on.
complete • This relay is turned on and off when the error
clear has been completed.
SM53 AC/DC DOWN Off: No AC/DC DOWN • This relay is turned on when a momentary S (Error)
detection power failure within 20ms is detected while
On: AC/DC DOWN the AC power supply module is in use. The
detected ON state is reset when the system is powered
off and on.
• This relay is turned on when a momentary
power failure within 10ms is detected while
the DC power supply module is in use. The
ON state is reset when the system is powered
off and on.
SM60 Fuse blown Off: Normal • This relay is turned on when at least one S (Error)
On: Fuse blown detected output module is in fuse blown state and the
ON state is maintained even after later
recovering to the normal state.
APPX
Appendix 3 List of Special Relay (SM) Areas 139
SM61 I/O module verification error Off: Normal • This relay is turned on when the state of the I/ S (Error)
On: Error O module is different from one registered
during power-on, and the ON state is
maintained even after later recovering to the
normal state.
SM80 Detailed information 1 in use Off: Not used This relay is turned on if the detailed information S (Status change)
flag On: In use n exists when 'Latest self-diagnostic error'
(SM0) switched to on.
SM112 Detailed information 2 in use
flag
APPX
140 Appendix 3 List of Special Relay (SM) Areas
Redundant power supply system
The following table lists the special relay areas relating to the redundant power supply system. The information of the
redundant power supply system is stored.
All relays are turned off when the redundant power supply base unit is not used.
SM150 Power-off/power supply Off: Power-on/normal • This relay is turned on when one or more of S (Status change)
voltage drop detection power supply voltage the power supply modules whose power has
On: Power-off/voltage drop been shut off or power supply voltage has
detected/power supply dropped (not including a momentary power
module not mounted failure), or one or more of empty slots for the
power supply module are detected.
• This relay is turned on when the factor that
any of 'Power-off/power supply voltage drop
detection status' (SD150) bits turns on
occurs.
• This relay is turned off when all factors that bit
of 'Power-off/power supply voltage drop
detection status' (SD150) turns on are
eliminated.
• This relay is turned off when the main base
unit is not the redundant power supply main
base unit.
SM151 Power supply module failure Off: Not detected/power-off/ • This relay is turned on when one or more S (Status change)
detection no power supply faulty power supply modules have been
module detected.
On: Faulty power supply • This relay is turned on when the factor that
module detected any of 'Power supply failure detection status'
(SD151) bits turns on occurs.
of 'Power supply failure detection status'
(SD151) turns on are eliminated.
base unit. A
SM152 Momentary power failure Off: No momentary power • This relay is turned on when one or more S (Status change)
detection (power supply failure detection momentary power failures of the input power
module 1) On: Momentary power supply to the power supply module 1 have
failure detected been detected. After this relay is turned on,
the ON state is retained even when the
momentary power failure is stopped.
• This relay is turned off when starting the
remote head module.
• This relay is turned off when the power supply
module 1 turns off.
base unit.
SM153 Momentary power failure Off: No momentary power • This relay is turned on when one or more S (Status change)
detection (power supply failure detection momentary power failures of the input power
module 2) On: Momentary power supply to the power supply module 2 have
failure detected been detected. After this relay is turned on,
the ON state is retained even when the
momentary power failure is stopped.
• This relay is turned off when starting the
remote head module.
• This relay is turned off when the power supply
module 2 turns off. This relay is turned off
when the main base unit is not the redundant
power supply main base unit.
APPX
SM154 Invalid power supply module Off: Valid/power-off/no • This relay is turned on when one or more of S (Status change)
power supply module invalid power supply modules are existed.
On: Invalid • This relay is turned on when the factor that
any of 'Details of the invalid power supply
module' (SD154) bits turns on occurs.
of 'Details of the invalid power supply module'
(SD154) turns on are eliminated.
base unit.
APPX
System information
The following table lists the special relay areas relating to the system information.
SM203 STOP contact Off: Other than STOP state This relay is turned on in STOP state. S (Status change)
On: STOP state
SM230 Remote head No.1 error flag Off: Remote head No.n • This relay is turned off when the remote head S (Status change)
SM231 Remote head No.2 error flag normal module of the remote head No.n is normal
On: Remote head No.n (including minor error).
moderate/major error • This relay is turned on when a moderate or
major error occurs in the remote head module
of the remote head No.n.
SM240 Remote head No.1 reset flag Off: Remote head No.n not • This relay is turned off when the remote head S (Status change)
being reset module of the remote head No.n is not being
SM241 Remote head No.2 reset flag
On: Remote head No.n in reset.
reset mode • This relay is turned on when the remote head
module of the remote head No.n is being
reset (including the case when the remote
head module is removed from the base unit).
System clock
The following table lists the special relay areas relating to the system clock.
SM400 Always On Always on Power-on to RUN or STOP
ON to RUN
OFF
SM401 Always Off Always off S (Status change)

ON
OFF
Fixed scan function information A

The following table lists the special relay areas relating to the fixed scan function information.
SM480 Cycle overrun flag for inter- Off: No error for the inter- • This relay is turned on during inter-module S (Status change)
module synchronization module synchronization synchronization when the I/O refresh,
(Normal) intelligent function module refresh, and data
On: Error state for the inter- transfer between the devices are not
module synchronization completed within the inter-module
synchronization cycle.
later processing is completed within the
specified inter-module synchronization cycle.
(Cleared by turning power off and on or
resetting).
SM488 Inter-module synchronization Off: No error for the inter- • This relay is turned on when the inter-module S (Status change)
error (out of synchronization module synchronization synchronization signal cannot be identified
was detected on the remote signal (Normal) within the inter-module synchronization cycle
head module) On: Error state for the inter- specified in the parameter or more than one
module synchronization signal has been identified within the same
signal inter-module synchronization cycle.
inter-module synchronization signal can be
later identified within the specified inter-
module synchronization cycle. (Cleared by
turning power off and on or resetting).
APPX
Drive information
The following table lists the special relay areas relating to the drive information.
SM632 Data memory write error Off: No write operation/ This relay is turned on when a write error is S (Writing)
normal detected during write operation to the data
On: Write error memory. This relay is turned off when the write
instruction is issued.
SM633 Data memory write flag Off: No write operation This relay is turned on when the write S (Writing)
On: Executing write processing to the data memory is in progress.
operation This relay is turned off when the write
processing is completed.
SM634 Number of rewriting Off: The number of rewrite This relay is turned on when the number of data S (Writing)
operations error to data operations is lower memory rewriting operations reaches 100000.
memory flag than 100000 (The remote head module needs to be
On: The number of rewrite replaced.)
operations reaches
100000
APPX
Online module change function
The following table lists the special relay areas relating to the online module change function.
SM1600 Module selection request flag OffOn: Requested This relay is turned on to select an online S (Status change)/U
change target module. When changing a (Request)
module directly, the system turns on this relay
upon removal of the target module. This relay
can be turned on only when the value set in
'Online module change progress status'
(SD1617) is 0 (Normal operation). This relay is
turned off upon completion of the online module
change processing. If the selection cancel is
requested, this relay is turned off after the
selection is canceled.
SM1601 Module selection completion Off: No module selected This relay is turned on when an online change S (Status change)
flag On: Selected target module has been selected. This relay is
change processing.
SM1602 Module removal request flag OffOn: Requested This relay is turned on to request a removal of S (Status change)/U
the selected module. When changing a module (Request)
directly, the system turns on this relay upon
removal of the target module. This relay can be
turned on only when the value set in 'Online
module change progress status' (SD1617) is 2
(Module selected). This relay is turned off upon
completion of the online module change
processing.
SM1603 Module removal ready flag Off: Not ready This relay is turned on when the selected S (Status change)
On: Ready module is ready to be removed. This relay is
change processing.
SM1604 Module removal completion Off: Not completed This relay is turned on when the selected S (Status change)
flag On: Completed module has been removed. This relay is turned
off upon completion of the online module A
change processing.
SM1605 Module mounting completion Off: Not completed This relay is turned on when a new module has S (Status change)
flag On: Completed been mounted. This relay is turned off upon
processing.
SM1606 Module recognition request OffOn: Requested This relay is turned on to request recognition of S (Status change)/U
flag the newly-mounted module. When changing a (Request)
module directly, the system turns on this relay
upon mounting of the module. This relay can be
(Module mounted). This relay is turned off upon
processing.
SM1607 Module recognition Off: Not recognized This relay is turned on when the newly-mounted S (Status change)
completion flag On: Recognized module is recognized by the system. This relay
is turned off upon completion of the online
module change processing.
SM1608 Module control resumption OffOn: Requested This relay is turned on to start control of the S (Status change)/U
request flag replaced module. When changing a module (Request)
directly, the system turns on this relay upon
recognition of the module. This relay can be
(Module recognized). This relay is turned off
upon completion of the online module change
processing.
SM1609 Online module change Off: Processing not This relay is turned on upon completion of the S (Status change)
completion flag completed online module change processing. This relay is
On: Completed turned off in the next scan.
APPX
SM1615 Module selection cancellation OffOn: Module selection This relay is turned on to cancel a module S (Status change)/U
request flag cancellation requested selection request. This relay can be turned on (Request)
only when the value set in 'Online module
change progress status' (SD1617) is 2 (Module
selected). This relay is turned off after the
selection is canceled.
SM1616 Online module change Off: Disabled Note that the setting details in the direct change S (Initial)
availability flag On: Enabled setting cannot be checked with 'Online module
change availability flag' (SM1616). To check the
direct change setting, check the CPU
parameters.
SM1617 Online module change status Off: Function not executed This relay is turned on when 'Module selection S (Status change)
flag On: Function being request flag' (SM1600) is turned on to start the
executed online module change processing. This relay is
change processing.
SM1618 Online module change error Off: No error This relay is turned on when an error is S (Status change)/U
flag On: Error detected. This relay is turned off when the error (Request)
cause is eliminated and the online module
change related request is executed.
An error occurs in selecting a module. Thus,
turn off the relay before module selection.
SM1619 Disable request flag during Off: No disabled request This relay is turned on when a disabled request S (Status change)
online module change On: Disable request is issued during the online module change
detected processing. This relay is turned off upon
processing.
Redundant function (own system remote head module information)

The following table lists the special relay areas relating to the redundant function. The remote head module information of the
own system is stored.
These relays are enabled only for a redundant system. All relays are turned off when a redundant system is not used.
: Can be set, : Cannot be set
No. Name Data stored Details Set by (setting Effective system
timing) Control Standby
system system
SM1634 Control system Flag that indicates the operating status of the remote head module S (Status change)  
judgment flag SM1634=Off, SM1635=Off: Systems not determined
SM1634=Off, SM1635=On: Standby system
SM1635 Standby system
SM1634=On, SM1635=Off: Control system
judgment flag
SM1637 System switching Off: Not detected This relay is turned on after the standby S (Status change)  
detection (standby On: Detected system has been switched to the control
system to control system.
system)
SM1646 System switching by Off: Disabled This relay stores whether to enable system U  
a user On: Enabled switching operation by a user using an
engineering tool. The initial value is off.
SM1654 Memory copy being Off: Not executed This relay is turned on during memory copy S (Status change)  
executed On: Being from the control system to the standby
executed system.
This relay is turned off when memory copy is
complete.
SM1655 Memory copy Off: Not This relay is turned on upon completion of S (Status change)  
completion completed memory copy from the control system to the
On: Completed standby system.
The initial value is off.
APPX
Redundant function (other system remote head module information)
The following table lists the special relay areas relating to the redundant function. The remote head module information of the
other system is stored.
All relays are turned off when a redundant system is not used.
No. Name Data stored Details Set by (setting Effective system
system system
SM1679 Error reset (the other OffOn: Standby This relay is turned off and on to clear the U/S (Status change)  
system) system error reset minor error occurred in the standby system.
requested This relay is turned off when the error clear of
OnOff: Standby the standby system has been completed.
system error reset The initial value is off.
completed
SM1680 Error of the other Off: No error This relay is turned on if an error occurs on S (Every END/system  
system monitoring On: Error communications with the other system when switching)
an initial processing (including when the
system is determined while waiting for the
other system starts up) or an END
processing is performed. (This relay is turned
on when any of 'Cause of the other system
monitoring error' (SD1648) bits turns on.)
This relay is turned off when an error is
cleared.
SM1681 Latest self-diagnostic Off: No error This relay is turned on if a diagnostic error S (Every END)  
error On: Error occurs in the other system remote head
module.
The status of 'Latest self-diagnostic error'
(SM0) for the other system remote head
module is reflected.
SM1682 Latest self-diagnostic Off: No error This relay is turned on if a self-diagnostic S (Every END)  
error On: Error error occurs in the other system remote head
module. A
The status of 'Latest self-diagnostic error'
(SM1) of the other system remote head
SM1683 Detailed information Off: Not used This relay is turned on when there is detailed S (Every END)  
1 in use flag (the On: In use information 1 for an error occurred in the
other system) other system remote head module.
The status of 'Detailed information 1 in use
flag' (SM80) of the other system remote head
SM1684 Detailed information Off: Not used This relay is turned on when there is detailed S (Every END)  
2 in use flag (the On: In use information 2 for an error occurred in the
other system) other system remote head module.
The status of 'Detailed information 2 in use
flag' (SM112) of the other system remote
head module is reflected.
APPX
Appendix 4 List of Special Register (SD) Areas
The following table shows how to read the special register (SD) list.
Item Description
No. Special register number
Name Special register name
Data stored Data stored in the special register
Details Detailed description of the data stored
Set by (setting timing) Set side of data (system or user) and timing when data is set by the system
<Set by>
• S: System
• U/S: User and system
<Set timing>
• Always: Data is regularly set.
• Every END: Data is set every time END processing is performed.
• Initial: Data is set when initial processing is performed (e.g. powering on the system, changing the operating status from
STOP to RUN).
• Status change: Data is set when the status is changed.
• Error: Data is set when an error occurs.
• Request: Data is set when requested by a user (using the special relay).
• Switch change: Data is set when the switch of the remote head module is changed.
• Writing: Data is set when a user performs a writing operation.
• Cause occurrence: Data is set when the system switching cause occurs by the system.
• System switching: Data is set when two systems are switched (between the control system and the standby system)
Do not change the values of special register set by the system by an engineering tool. Doing so may result in
system down or communication failure.
Diagnostic information
The following table lists the special register areas relating to the diagnostic information.
No. Name Description Details Set by (setting
timing)
SD0 Latest self- Latest self- Error codes are stored in a hexadecimal value when the diagnostics detects an error. S (Error)
diagnostic diagnostic
error code error code
SD1 Latest self- Latest self- The year value (four digits) of the date/time when data of 'Latest self-diagnostic error S (Error)
diagnostic diagnostic code' (SD0) was updated is stored as a BIN code.
error time error time
SD2 The month value of the date/time when data of 'Latest self-diagnostic error code'
(SD0) was updated is stored as a BIN code.
SD3 The day value of the date/time when data of 'Latest self-diagnostic error code' (SD0)
was updated is stored as a BIN code.
SD4 The hour value of the date/time when data of 'Latest self-diagnostic error code'
SD5 The minute value of the date/time when data of 'Latest self-diagnostic error code'
SD6 The second value of the date/time when 'Latest self-diagnostic error code' (SD0)
was updated is stored as a BIN code.
SD7 The day of week value of the date/time when 'Latest self-diagnostic error code'
(SD0) was updated is stored as a BIN code. (0: Sun, 1: Mon, 2: Tue, 3: Wed, 4: Thu,
5: Fri, 6: Sat)
APPX
148 Appendix 4 List of Special Register (SD) Areas
timing)
SD10 Self-diagnostic Self-diagnostic The maximum of 16 types of error codes are stored into 'Self-diagnostic error S (Error)
error number error number 1 number' (SD10) onwards when the diagnostics detects an error. (The same error
SD11 Self-diagnostic code as one already stored in 'Self-diagnostic error number' (SD10) onwards is not
stored). The 17th error code onwards are not stored. Also error codes are not stored
error number 2
when 16 types of error codes have already been stored into 'Self-diagnostic error
SD12 Self-diagnostic number' (SD10) to 'Self-diagnostic error number' (SD25).
error number 3
SD13 Self-diagnostic
error number 4
error number 5
error number 6
error number 7
error number 8
error number 9
error number
10
error number
11
error number
12
error number
13
SD23 Self-diagnostic A
error number
14
error number
15
error number
16
SD53 AC/DC DOWN The number of The value of this register increments by one and stored as a BIN code, each time S (Error)
AC/DC DOWN input voltage drops to 85% (AC power)/65% (DC power) or less of the nominal value
detections while the remote head module is carrying out an operation. A counting cycle from 0
to 65535 to 0 is repeated.
SD60 Number of Number of The lowest number of module in which a fuse blew is stored. S (Error)
module with module with
blown fuse blown fuse
SD61 I/O module I/O module The lowest I/O number of the module which has an error detected by the I/O module S (Error)
verify error verify error verification is stored.
module module
number number
SD80 Detailed Detailed Detailed information 1 information category code is stored. S (Error)
information 1 information 1 b0 to b7: Information category code
information information • 0: N/A
category category code • 2: Drive/file information
• 4: Parameter information
• 5: System configuration information
• 6: Number of times information
• 7: Time information
• 24: Failure information
• 27: System switching information
b8 to b15: Not used (fixed to 0)
APPX
Appendix 4 List of Special Register (SD) Areas 149
timing)
SD81 to Detailed Detailed • The detailed information 1 corresponding to 'Latest self-diagnostic error code' S (Error)
SD111 information 1 information 1 (SD0) is stored.
• There are seven types of information to be stored as described below.
• The type of the detailed information 1 can be obtained using 'Detailed information
1 information category' (SD80). (The value of the "Detailed information 1
information category code" stored in 'Detailed information 1 information category'
(SD80) corresponds to the following (2), (4) to (7), (24), and (27).)
(2) Drive/file information
■SD81: With or without specification
• b0: Drive No.
• b1: File name
■SD82: Drive No.
■SD83 (1st character) to SD90 (8th character): File name (first 8 characters of
Unicode character string)
(4) Parameter information
• b0: Parameter type
• b1: Parameter storage location
• b2: I/O No.
• b3: Parameter No.
• b4: Network No.
• b5: Station No.
• b6: System information
■SD82: Parameter type, parameter storage location
• b0 to b7: Parameter type (1: System parameter, 2: CPU parameter, 3: Module
parameter, 4: Module extension parameter)
• b8 to b15: Parameter storage location (4: Data memory)
■SD83: I/O No.
For no assignment of I/O No., FFFFH is given.
■SD84: Parameter No.
■SD85: Network No.
■SD86: Station No.
1 to 120
■SD87 to SD97: System information
APPX
timing)
SD81 to Detailed Detailed (5) System configuration information S (Error)
SD111 information 1 information 1 ■SD81: With or without specification
• b0: I/O No.
• b1: Slot No.
• b2: Base No.
• b3: Power supply No.
• b4: CPU No.
• b5: Network No.
• b6: Station No.
■SD82: I/O No.
■SD83: Slot No., Base No.
• b0 to b7: Slot No. (0 to 11: Slot No.)
• b8 to b15: Base No. (0: Main base unit, 1 to 7: 1st to 7th extension base unit, 8:
8th or more)
■SD84: Power supply No., CPU No.
• b0 to b7: Power supply No. (1: Power supply module 1, 2: Power supply module 2)
• b8 to b15: CPU No. (1: Remote head No.1, 2: Remote head No.2)
1 to 120
(6) Number of times information
When there is no specification, 0 is set to each SD.
• b0: Count (setting)
• b1: Count (measured)
■SD82: Count (setting) (L)
■SD83: Count (setting) (H)
■SD84: Count (measured) (L)
■SD85: Count (measured) (H)
(7) Time information
When there is no specification, 0 is set to each SD.
• b0: Time (setting) (ms)
• b1: Time (setting) (s)
• b2: Time (measured) (ms)
• b3: Time (measured) (s)
A
■SD92: Time (setting) (ms)
■SD93: Time (setting) (s)
■SD94: Time (measured) (ms)
■SD95: Time (measured) (s)
(24) Failure information
Failure information is system information.
(27) System switching information
• b0: System switching cause
• b2: Cause of system switching failure
■SD82: System switching cause
• 1: Power-off, reset, or hardware failure
• 2: Moderate error or major error
• 3: System switching due to data link error
• 16: System switching of redundant master station system
• 17: System switching request using an engineering tool
■SD83: Argument of system switching instruction
■SD84: Cause of system switching failure
• 1: The standby system is not available for communications. (The standby system
is in reset processing or not connected.)
• 2: Communication timeout
• 3: Moderate error or major error in the standby system
• 4: Both systems operate differently.
• 5: Memory copy from the control system to the standby system being executed
• 7: Data link error is detected in the standby system.
• 8: System switching being performed
• 9: Online module change being performed
SD112 Detailed Detailed Detailed information 2 information category code is stored. S (Error)
information 2 information 2 b0 to b7: Information category code
information information • 0: N/A
category category code • 2: Drive number and file name
• 4: Parameter information
• 5: System configuration information
b8 to b15: Not used (fixed to 0)
APPX
timing)
SD113 Detailed Detailed • The detailed information 2 corresponding to 'Latest self-diagnostic error code' S (Error)
to information 2 information 2 (SD0) is stored.
SD143 • There are four types of information to be stored as described below.
• The type of the detailed information 2 can be obtained using 'Detailed information
2 information category' (SD112). (The value of the "Detailed information 2
information category code" stored in 'Detailed information 2 information category'
(SD112) corresponds to the following (2), (4), and (5).)
(2) Drive number and file name
• b0: Drive No.
• b1: File name
■SD114: Drive No.
■SD115 (1st character) to SD122 (8th character): File name (first 8 characters of
Unicode character string)
(4) Parameter information
• b0: Parameter type
• b1: Parameter storage location
• b2: I/O No.
• b3: Parameter No.
• b4: Network No.
• b5: Station No.
• b6: System information
■SD114: Parameter type, parameter storage location
• b0 to b7: Parameter type (1: System parameter, 2: CPU parameter, 3: Module
parameter, 4: Module extension parameter)
• b8 to b15: Parameter storage location (4: Data memory)
■SD115: I/O No.
For no assignment of I/O No., FFFFH is given.
■SD116: Parameter No.
1 to 120
■SD119 to SD129: System information
(5) System configuration information
• b0: I/O No.
• b1: Slot No.
• b2: Base No.
• b3: Power supply No.
• b4: CPU No.
• b5: Network No.
• b6: Station No.
■SD114: I/O No.
■SD115: Slot No., Base No.
• b0 to b7: Slot No. (0 to 11: Slot No.)
• b8 to b15: Base No. (0: Main base unit, 1 to 7: 1st to 7th extension base unit, 8:
8th or more)
■SD116: Power supply No., CPU No.
• b0 to b7: Power supply No. (1: Power supply module 1, 2: Power supply module 2)
• b8 to b15: CPU No. (1: Remote head No.1, 2: Remote head No.2)
1 to 120
APPX
Redundant power supply system
The following table lists the special register areas relating to the system information. The information of the redundant power
supply system is stored.
All registers are turned off when the redundant power supply base unit is not used.
timing)
SD150 Power-off/power Power-off/power • Power supply module status (power is shut off, power supply voltage S (Status change)
supply voltage drop supply voltage drop drop (not including a momentary power failure) is detected, or an
detection status detection status empty slot for the power-supply module exists) is stored using the
0: Power-on/normal following bit pattern.
voltage • When the main base unit is not the redundant power supply main base
1: Power-off/voltage unit, 0 is stored.
drop detected/no ■Powered-off/power supply voltage drop detection status (power supply
power supply module 1)
module b0: Main base unit
b1: 1st extension base unit
b2: 2nd extension base unit

b7: 7th extension base unit
■Powered-off/power supply voltage drop detection status (power supply
module 2)
b8: Main base unit

SD151 Power supply failure Power supply failure • The power supply module failure detection status is stored in the S (Status change)
detection status detection status following bit patterns.
0: Not detected/ • Bits corresponding to power-off or empty slots for the power supply
power-off/no power module turn off.
supply module 1: • When the main base unit is not the redundant power supply main base
Detected unit, 0 is stored.
■Power supply failure detection status (power supply module 1)
b0: Main base unit
A

■Power supply failure detection status (power supply module 2)
b8: Main base unit

SD152 Momentary power Momentary power • This register counts the number of momentary power failures. S (Status change)
failure detection failure detection • This register monitors the status of the power supply module mounted
count (power supply count for power on the main base unit and counts the number of momentary power
module 1) supply module 1 failures.
SD153 Momentary power Momentary power • When the remote head module starts, the counter of the both power S (Status change)
failure detection failure detection supply modules is cleared to 0.
count (power supply count for power • When either of the power supply module is turned off, the counter of
module 2) supply module 2 the power supply module which is turned off is cleared to 0.
• The counter is incremented by one upon one momentary power failure
on each power supply. A counting cycle from 0 to 65535 to 0 is
repeated.
• When the main base unit is not the redundant power supply main base
unit, 0 is stored.
APPX
timing)
SD154 Details of the invalid Details of the invalid • When an invalid power supply module exists, the status is stored using S (Status change)
power supply power supply the following bit pattern.
module module • Bits corresponding to power-off or empty slots for the power supply
0: Valid/power-off/ module turn off.
no power supply • When the main base unit is not the redundant power supply main base
module unit, 0 is stored.
1: Invalid ■Details of the invalid power supply module (power supply module 1)
b0: Main base unit

■Details of the invalid power supply module (power supply module 2)
b8: Main base unit

APPX
System information
The following table lists the special register areas relating to the system information.
timing)
SD200 Status of switch Remote head The switch status of the remote head module is stored as follows: S (Switch change)
module switch 0: RUN
status 1: STOP
SD201 LED status Remote head The information that indicates LED status (0: off, 1: on, 2: flashing) of the S (Status change)
module LED status remote head module is stored in the following bit patterns. 0 = Off, 1 =
On, 2 = Flashing
b0, b1: RUN
b2, b3: ERR
b4, b5: BUS RUN
b6, b7: D LINK
b8, b9: CTRL
b10, b11: SD/RD
b12, b13: SBY
b14, b15: L ERR
SD203 Remote head Remote head The operating status of the remote head module is stored as follows: S (Always)
module operating module operating 0: RUN
status status 2: STOP
SD228 Redundant system Number of remote The number of remote head modules which constitute a redundant S (Initial)
information head modules system is stored.
1: Non-redundant system
2: Redundant system
SD229 Remote head The remote head number of the own remote head module is stored when S (Initial)
module number a redundant system is configured.
SD230 Remote head No.1 The operation information for each remote head number is stored. (The S (During END/Error)
operating status amount of stored information depending on the number of remote head
SD231 Remote head No.2 modules indicated in 'Redundant system information' (SD228) is stored).
b0 to b3: Operating status
operating status
• 0: RUN
• 2: STOP
• 4: INITIALIZE
A
• FH: RESET
b4, b5: Classification
• 0: Normal
• 1: Minor error
• 2: Moderate error
• 3: Major error
b6: Empty
b7: Stop error flag
• 0: No stop error
• 1: Stop error
b8 to b14: Empty
b15: Mounting status
• 0: Not mounted
• 1: Mounted
SD241 Extension stage 0: Main base unit The maximum number of implemented extension base units is stored. S (Initial)
number only
1 to 7: Number of
extension base
units
SD242 Identification for Identification of the Identify whether or not Q series module can be mounted. When no SD S (Initial)
whether or not Q base type memory card is inserted, the value is fixed to 0.
series module can 0: Cannot be b0: Main base unit (fixed to 0)
be mounted mounted (There is b1: 1st extension base unit (Q series module can be mounted.)
no base unit on b2: 2nd extension base unit (Q series module can be mounted.)
which the Q series 
module can be b7: 7th extension base unit (Q series module can be mounted.)
mounted.) b8 to b15: Fixed to 0
1: Can be mounted
(There is a base
unit on which the Q
series module can
be mounted.)
APPX
timing)
SD243 No. of base slots No. of base slots The number of slots of the base unit, which is specified in "Base/Power/ S (Initial)
SD244 Extension Cable Setting" in the [I/O Assignment] tab of "System
Parameter", is stored. When the number of slots of the base unit is not
specified, that of the base unit actually mounted is stored.
■SD243
b0 to b3: Main
b4 to b7: Extension 1
■SD244
SD250 Loaded maximum I/ Loaded maximum I/ The value obtained by dividing the last I/O number for an implemented S (Initial)
O O number unit plus one by 16 is stored.
Example 1: Last I/O number 010FH
• SD250 = 0011H
Example 2: Last I/O number 0FFFH
• SD250 = 0100H
SD260 Number of points X (L) The number of points assigned to the X device is stored in 32 bits. S (Initial)
assigned to bit Fixed to 12288.
SD261 X (H)
devices
SD262 Y (L) The number of points assigned to the Y device is stored in 32 bits. S (Initial)
Fixed to 12288.
SD263 Y (H)
SD264 M (L) The number of points assigned to the M device is stored in 32 bits. S (Initial)
SD265 M (H) Fixed to 0.
SD266 B (L) The number of points assigned to the B device is stored in 32 bits. S (Initial)
SD267 B (H) Fixed to 0.
SD268 SB (L) The number of points assigned to the SB device is stored in 32 bits. S (Initial)
Fixed to 8192.
SD269 SB (H)
SD270 F (L) The number of points assigned to the F device is stored in 32 bits. S (Initial)
Fixed to 0.
SD271 F (H)
SD272 V (L) The number of points assigned to the V device is stored in 32 bits. S (Initial)
Fixed to 0.
SD273 V (H)
SD274 L (L) The number of points assigned to the L device is stored in 32 bits. S (Initial)
SD275 L (H) Fixed to 0.
SD276 S (L) The number of points assigned to the S device is stored in 32 bits. S (Initial)
Fixed to 0.
SD277 S (H)
SD280 Number of points D (L) The number of points assigned to the D device is stored in 32 bits. S (Initial)
assigned to word Fixed to 0.
SD281 D (H)
devices
SD282 W (L) The number of points assigned to the W device is stored in 32 bits. S (Initial)
Fixed to 8192.
SD283 W (H)
SD284 SW (L) The number of points assigned to the SW device is stored in 32 bits. S (Initial)
SD285 SW (H) Fixed to 8192.
SD288 Number of points T (L) The number of points assigned to the T device is stored in 32 bits. S (Initial)
assigned to timer/ Fixed to 0.
SD289 T (H)
counter devices
SD290 ST (L) The number of points assigned to the ST device is stored in 32 bits. S (Initial)
SD291 ST (H) Fixed to 0.
SD292 C (L) The number of points assigned to the C device is stored in 32 bits. S (Initial)
Fixed to 0.
SD293 C (H)
SD294 LT (L) The number of points assigned to the LT device is stored in 32 bits. S (Initial)
Fixed to 0.
SD295 LT (H)
SD296 LST (L) The number of points assigned to the LST device is stored in 32 bits. S (Initial)
Fixed to 0.
SD297 LST (H)
SD298 LC (L) The number of points assigned to the LC device is stored in 32 bits. S (Initial)
Fixed to 0.
SD299 LC (H)
APPX
timing)
SD300 Number of points Z The number of points assigned to the Z device is stored. S (Initial)
assigned to the Fixed to 0.
index register
SD302 Number of points LZ The number of points assigned to the LZ device is stored. S (Initial)
assigned to the long Fixed to 0.
index register
SD306 Number of points ZR (L) The number of points assigned to the ZR device is stored in 32 bits. S (Initial)
assigned to the file Fixed to 0.
SD307 ZR (H)
register
SD308 Number of points RD (L) The number of points assigned to the RD device is stored in 32 bits. S (Initial)
assigned to refresh Fixed to 12288.
SD309 RD (H)
devices
Fixed scan function information

The following table lists the special register areas relating to the fixed scan function information.
timing)
SD480 Inter-module synchronization 0: No cycle overrun event The number of counts in which the inter-module S (Status change)
cycle over count 1 to 65535: Cumulative synchronous I/O refresh, intelligent function module
number of times refresh, and data transfer between the devices have
not been completed is stored within the inter-module
synchronization cycle. When the count exceeds 65535,
it returns to 0 and starts a new cycle.
SD520 Current scan time*1 Current scan time (unit: ms) • The current scan time is stored into 'Current scan S (Always)
SD521 Current scan time (unit: s) time' (SD520) and 'Current scan time' (SD521). (The
time is measured in increments of s).
'Current scan time' (SD520): The ms part is stored.
(Range: 0 to 65535)
'Current scan time' (SD521): The s part is stored.
(Range: 0 to 999)
Example: If the current scan time is 23.6ms, the
following values are stored: A
SD520 = 23
SD521 = 600
• This register is cleared to 0 when the mode transfers
from STOP to RUN mode.
SD522 Minimum scan time*1 Minimum scan time (unit: ms) • The scan time is stored into 'Minimum scan time' S (Always)
(SD522) and 'Minimum scan time' (SD523). (The
SD523 Minimum scan time (unit: s)
time is measured in increments of s).
'Minimum scan time' (SD522): The ms part is stored.
(Range: 0 to 65535)
'Minimum scan time' (SD523): The s part is stored.
(Range: 0 to 999)
SD524 Maximum scan time*1 Maximum scan time (unit: • The scan time is stored into 'Maximum scan time' S (Always)
ms) (SD524) and 'Maximum scan time' (SD525). (The
SD525 Maximum scan time (unit: s) time is measured in increments of s).
'Maximum scan time' (SD524): The ms part is stored.
(Range: 0 to 65535)
'Maximum scan time' (SD525): The s part is stored.
(Range: 0 to 999)
*1 The scan time of the remote head module shows the interval of the I/O refresh and intelligent function module (including a network
module) refresh.
APPX
Drive information
The following table lists the special register areas relating to the drive information.
timing)
SD620 Data memory (drive 4) usage Data memory (drive 4) usage Usage status of the data memory is stored using the S (Status change)
status status following bit pattern. (ON indicates being used.)
b0: Event history
b1: Unused
b2: Label communication data
b3 to b15: Unused
SD622 Data memory (drive 4) Data memory (drive 4) The capacity of the data memory is stored in S (Initial)
capacity capacity: the lower digits increments of 1K byte.
(unit: K bytes) (The amount of free space for a formatted memory card
is stored.)
SD623 Data memory (drive 4) The capacity of the data memory is stored in S (Initial)
capacity: the higher digits increments of 1K byte.
(unit: K bytes) (The amount of free space for a formatted memory card
is stored.)
SD633 Data memory write (transfer) Write (transfer) status display This register displays write (transfer) status to the data S (Writing)
status (percent) memory in percentage. (0 to 100%). The initial value is
"0". Upon completion of writing, this register is set to
"100". It is set to "0" at the time when the write
command is issued.*1
SD634 Index for the number of data Index of the number of write • This register indicates the index value for the number S (Writing)
SD635 memory write operations operations up to now of write operations to the data memory up to now
(stored as a 32-bit BIN value). However, the number
of write operations is not equal to the index value.
• When the index value exceeds 100000, an error is
generated. (The index value is continued to be
counted even when it exceeds 100000.) If the index
value exceeds 100000, the remote head module
must be replaced.
*1 "100" is stored when powering off and on or reset the remote head module. (Since the event history will be stored and data will be
written into the data memory at the timing of powering off and on and resetting the remote head module, "100" is stored.)
APPX
Online module change function
The following table lists the special register areas relating to the online module change function.
timing)
SD1600 Module selection (base Base unit No. where the The base unit number where the online change target module S (Status change)/U
unit No.) online change target is mounted is specified. (Request)
module is mounted 0: Main base unit
1: 1st extension base unit

7: 7th extension base unit
FFFFH: Not specified (Default)
The value returns to its default (FFFFH) upon completion of
the online module change processing. When changing a
module directly, the system stores the corresponding base
unit number upon removal of the target module.
SD1601 Module selection (slot Slot No. where the online The slot number where the online change target module is S (Status change)/U
No.) change target module is mounted is specified. (Request)
mounted 0: Slot No.0
1: Slot No.1

11: Slot No.11
the online module change processing. When changing a
module directly, the system stores the corresponding slot
number upon removal of the target module.
SD1602 I/O No. of the module I/O No. of the module This register stores the value of the I/O number of the module S (Status change)
being changed online being changed online being changed online divided by 16.
Other than FFFFH: I/O No.  16
the online module change processing.
SD1617 Online module change Online module change This resister stores the online module change progress S (Status change)
progress status progress status status.
0: Normal operation
A
1: Module being selected
2: Module selected
3: Module removal requested
4: Module removal ready
5: Module removed
6: Module mounted
7: Module being recognized
8: Module recognized
9: Module control resumed
The value becomes 0 upon completion of the online module
change processing.
SD1618 Online module change 0: Normal operation The corresponding error code is stored when an error is S (Status change)/U
error code Other than 0: Error code detected during online module change. For the value stored, (Request)
refer to the list of error codes in the following manual.
•  MELSEC iQ-R CPU Module User's Manual
(Application)
This register is cleared to 0 when the error cause is eliminated
and the online module change related request is executed.
However, the error code needs to be cleared to 0 before
module selection since this register is not cleared to 0 if an
error occurs in selecting a module.
SD1619 Disable request error 0: Normal operation The corresponding error code is stored when a disable S (Status change)
code during online Other than 0: Error code request is executed during online module change. The error
module change code is cleared to 0 when the error cause is eliminated and
the online module change related request is executed.
For the value stored, refer to the list of error codes in the
following manual.
 MELSEC iQ-R CPU Module User's Manual (Application)
APPX
Redundant function
The following table lists the special register areas relating to the redundant function.
No. Name Description Details Set by (setting Effective system
system system
SD1643 System switching System switching System switching cause occurred in own S (System switching)  
cause cause occurred in system is stored. The system switching
own system cause is stored in this register even if the
systems cannot be switched by a cause of
system switching failure.
This register is cleared to 0 when the system
is powered on and off or reset.
0: Initial value (the control system never
been switched)
1: Reset or hardware failure of the remote
head module
2: Moderate error or major error
3: System switching due to data link error
16: Follow the system switching of the
redundant line master station.
17: System switching request from the
engineering tool
When the systems are switched by resetting
the control system, "1" is not stored in 'Cause
of system switching' (SD1643) of the new
standby system.
SD1644 Cause of system Cause number of Error cause in the control system is stored in S (System switching)  
switching failure system switching this register when a system switching is
failure failed.
0: System switching completed normally
(default)
1: The standby system is not available for
communications. (The standby system is in
reset processing or not connected.)
2: Communication timeout
3: Moderate error or major error in the
standby system
4: Both systems operate differently.
5: Memory copy from the control system to
the standby system being executed
7: Data link error is detected in the standby
system.
8: System switching being performed
9: Online module change being performed
• When own system is powered on, this
register is cleared to 0.
• When the system switching is completed,
0 is stored in this register.
SD1648 Cause of the other Cause of the other The following corresponding bit turns on S (Every END/system  
system monitoring system monitoring when communication error occurs in the switching)
error error other system. That bit turns off when the
error is cleared after that.
Each bit turns on when the value is "0" and
off when the value is "1".
b0: Fixed to 0
b1: Reset or hardware failure in the other
system
b2: Moderate error or major error in the other
system
b3 to b14: Fixed to 0
b15: The other system is not available for
communications.
• If any of b1, b2, and b15 is on, the other
bits are off.
• When the other system is reset or in a
hardware failure, b15 may turn on
depending on the timing.
APPX
system system
SD1649 System switching System switching System switching cause is stored. S (System switching)  
cause (when the cause (when the • When the systems are switched, the cause
systems are systems are for system switching is stored in 'System
successfully successfully switching cause (when the systems are
switched) switched) successfully switched)' (SD1649) of both
systems.
• This register is cleared to 0 when the
system is powered on and off or reset.
• The following shows the values stored in
this register.
0: Initial value (the control system never
been switched)
1: Reset or hardware failure of the remote
head module
2: Moderate error or major error
3: System switching due to data link error
16: Follow the system switching of the
redundant line master station.
17: System switching request from the
engineering tool
When the systems are switched by resetting
the control system, "1" is not stored in
'System switching cause (when the systems
are successfully switched)' (SD1649) of the
new standby system.
SD1654 Memory copy Memory copy This register stores the execution status of S (Status change)  
completion status completion status the memory copy.
When the value other than 0 is stored, the
memory copy is completed with an error or
cannot be executed.
0: Memory copy completed normally
4241H: Power-off of the standby system
4247H: Memory copy being executed
4248H: Unsupported copy destination I/O A
number
SD1681 Latest self-diagnostic Latest self- • This register stores an error code for the S (Every END)  
error code (the other diagnostic error error occurred in the other system with
system) code (the other hexadecimal.
system) • 'Latest self-diagnostic error code' (SD0) of
the other system is reflected.
SD1682 to Latest self-diagnostic Latest self- • An error time for the error occurred in the S (Every END)  
SD1688 error time (the other diagnostic error other system is stored.
system) time (the other • Data configuration is the same as 'Latest
system) self-diagnostic error time' (SD1) to 'Latest
self-diagnostic error time' (SD7).
• The values in 'Latest self-diagnostic error
time' (SD1) to 'Latest self-diagnostic error
time' (SD7) of the other system are
reflected.
SD1689 Detailed information Information • A detailed information 1 category code for S (Every END)  
1 information category code 1 the error occurred in the other system is
category (the other (the other system) stored.
system) • Data configuration is the same as 'Detailed
information 1 information category'
(SD80).
• The value in 'Detailed information 1
information category' (SD80) of the other
system is reflected.
SD1690 to Detailed information Detailed • A detailed information 1 for the error S (Every END)  
SD1720 1 (the other system) information 1 (the occurred in the other system is stored.
other system) • Data configuration is the same as 'Detailed
information 1' (SD81 to SD111).
• The values in 'Detailed information 1'
(SD81 to SD111) of the other system are
reflected.
APPX
system system
SD1721 Detailed information Information • A detailed information 2 category code for S (Every END)  
2 information category code 2 the error occurred in the other system is
category (the other (the other system) stored.
system) • Data configuration is the same as 'Detailed
information 2 information category'
(SD112).
• The value in 'Detailed information 2
information category' (SD112) of the other
system is reflected.
SD1722 to Detailed information Detailed • A detailed information 2 for the error S (Every END)  
SD1752 2 (the other system) information 2 (the occurred in the other system is stored.
other system) • Data configuration is the same as 'Detailed
information 2' (SD113 to SD143).
• The values in 'Detailed information 2'
(SD113 to SD143) of the other system are
reflected.
APPX
Appendix 5 Access Code and Attribute Code
The following table lists the access codes and attribute code that are set when accessing the remote head module by using
the RIRD or RIWT instruction of the master/local module.
Device description*1 Name Device type Unit Access code Attribute code
Bit Word
Input X   Hexadecimal 01H 05H
Output Y   Hexadecimal 02H
Link register W   Hexadecimal 24H
Link special relay SB   Hexadecimal 63H
Link special register SW   Hexadecimal 64H
Special relay SM   Decimal 43H
Special register SD   Decimal 44H
*1 Devices not listed in the table cannot be accessed. To access a bit device, specify 0 or a multiple of 16.
APPX
Appendix 5 Access Code and Attribute Code 163
Appendix 6 Processing Time
Processing time used to calculate the transmission delay time
This section describes the processing time of the remote head module.
To calculate the processing time of CC-Link IE Field Network, add the processing time of the remote head
module to the processing time of the slave stations.
For the processing time of the CC-Link IE Field Network, refer to the following.
Cyclic transmission delay time

The following is the formula to calculate the cyclic transmission delay time.*1
Condition Input Output
Normal value Rio = 0.5  (Z + 1)  LS + X + Y Rio = 0.5  Z  LS + X + Y
Maximum value Rio = (Z + 1)  LS + X + Y Rio = Z  LS + X + Y
Variable Meaning
Rio Processing time [s]
X (Number of RX/RY points)  0.026 + (Number of RWw/RWr points)  0.255 + 620 + Ka [s]
• Number of RX/RY points: The number of RX/RY points assigned to the remote head module in the network configuration setting of the master
module
• Number of RWw/RWr points: The number of RWw/RWr points assigned to the remote head module in the network configuration setting of the
master module
• Ka: 90  The number of mounted modules in which refresh settings are configured
Y (Response time of the connected modules) [s] ( Manual for the module used)
Z X  LS (Round down the calculated value to the nearest integer.) [s]
LS Link scan time [s]
The above formula calculates the average value when the number of RX/RY points is the same as the number of actual I/O
points of the module connected to the remote head module, and an auto refresh of the same number of points as the number
of RWw/RWr points was performed.
Transmission delay time of the safety communication relay

The following is the formula to calculate the I/O processing time of the intelligent device station (safety station) included in the
transmission delay time of the safety communication relay.*1
Condition Input Output
Normal value SRi = 0.5  (Z+1)  LS + Ys SRo = 0.5  Z  LS + Ys
Maximum value SRi = (Z+1)  LS + Ys SRo = Z  LS + Ys
Variable Meaning
SRi Input response time [s]
SRo Output response time [s]
Ys Safety I/O response time of the mounted modules [s] ( Manual for the module used)
Z X  LS (Round down the calculated value to the nearest integer.) [s]
LS Link scan time [s]
APPX
164 Appendix 6 Processing Time
Transmission delay time of the dedicated instructions
The following is the formula to calculate the transmission delay time of the dedicated instructions.*1*2
Condition Calculation formula
Normal value Rio = 12  X
Maximum value Rio = 24  X
*1 When the master station is in "Normal" mode

Variable Meaning
Rio Processing time [s]
X (Number of RX/RY points)  0.026 + (Number of RWw/RWr points)  0.255 + 620 + Ka [s]
• Number of RX/RY points: The number of RX/RY points assigned to the remote head module in the network configuration setting of the master
module
• Number of RWw/RWr points: The number of RWw/RWr points assigned to the remote head module in the network configuration setting of the
master module
• Ka: 90  The number of mounted modules in which refresh settings are configured
The above formula calculates the average value when the number of RX/RY points is the same as the number of actual I/O
points of the module connected to the remote head module, and an auto refresh of the same number of points as the number
of RWw/RWr points was performed.
APPX
Appendix 6 Processing Time 165
System switching time
The calculation formula for the system switching time of the remote head module is as follows:*1
Line Type System System switching cause Calculation formula
switching
method
Single Line Automatic system Reset or hardware failure HSW = 15.5 + (2  LS)
switching
Moderate error or major error HSW = 13 + (3  LS)
Data link error HSW = 2106 + TC + (3  LS)
Manual system System switching operation using the HSW = 13 + (3  LS)
switching engineering tool
Redundant Automatic system Tracking of system switching of redundant HSW = 13 + (3  LS)
Line switching master station system
Variable Meaning
HSW System switching time of the remote head module [ms]
LS Link scan time [ms] ( MELSEC iQ-R CC-Link IE Field Network User's Manual (Application))
TC Setting value [ms] of system switching monitoring time set in the master station ( MELSEC iQ-R CC-Link IE Field Network User's Manual
(Application))
For the cyclic data hold time at system switching, refer to the following.
APPX
166 Appendix 6 Processing Time
Appendix 7 New or Revised Functions
The following table lists the new or revised functions of the remote head module.
New or revised function Firmware version*2
Safety communication relay function "05" or later
*2 When 8-digit number is displayed on "Firmware Version" of "Product Information List" window in engineering tool, the first 2-digit shows
the firmware version.
APPX
Appendix 7 New or Revised Functions 167
INDEX
C Remote device station . . . . . . . . . . . . . . . . . . . . .15

Remote head module . . . . . . . . . . . . . . . . . . . . . 15
CC-Link IE Field Network diagnostics . . . . . . . . . 95 Remote I/O station . . . . . . . . . . . . . . . . . . . . . . .15
Control system . . . . . . . . . . . . . . . . . . . . . . . . . 14 Remote input (RX) . . . . . . . . . . . . . . . . . . . . . . .15
Cyclic transmission . . . . . . . . . . . . . . . . . . . . . . 14 Remote operation . . . . . . . . . . . . . . . . . . . . . . . .96
Remote output (RY) . . . . . . . . . . . . . . . . . . . . . .15
D Remote password function . . . . . . . . . . . . . . . . .40
Remote register (RWr) . . . . . . . . . . . . . . . . . . . .15
Data link . . . . . . . . . .................... 14 Remote register (RWw) . . . . . . . . . . . . . . . . . . . .15
Dedicated instruction . .................... 14
Device . . . . . . . . . . . .................... 14
Diagnostic items . . . . .................... 95 S
Disconnection . . . . . . .................... 14 SIL2 function module . . . . . . . . . . . . . . . . . . . . . 15
SIL2 mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
E SIL2 Process CPU . . . . . . . . . . . . . . . . . . . . . . .15
Single line . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Engineering tool . . . . . . . . ................ 14 Slave station . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Error information . . . . . . . . ................ 92 Standby system . . . . . . . . . . . . . . . . . . . . . . . . .15
Ethernet-equipped module . ................ 14 Station number setting of the remote head module
Event history file . . . . . . . . ................ 35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96
G T
Global label . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Tracking cable . . . . . . . . . . . . . . . . . . . . . . . . . .15
Transient transmission . . . . . . . . . . . . . . . . . . . .15
I
Intelligent device station. . . . . . . . . . . . . . . . . . . 14
Intelligent function module . . . . . . . . . . . . . . . . . 14
L
Label . . . . . . . . . . . . . . . . . ............... 14
Link device . . . . . . . . . . . . . ............... 14
Link special register (SW) . . ............... 14
Link special relay (SB) . . . . . ............... 14
Local station . . . . . . . . . . . . ............... 14
M
Master station . . . . . . . . . . . ............... 14
Master/local module . . . . . . ............... 14
Module communication test . ............... 94
Module information list . . . . . ............... 93
Module label . . . . . . . . . . . . ............... 14
N
New control system . . . . . . . . . . . . . . . . . . . . . . 14
New standby system . . . . . . . . . . . . . . . . . . . . . 14
P
Power supply module . . . . . . . . . . . . . . . . . . . . 14
R
RAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Redundant line . . . . . . . . . . . . . . . . . . . . . . . . . 44
Redundant power supply base unit . . . . . . . . . . . 15
Redundant power supply module . . . . . . . . . . . . 15
Redundant slave station . . . . . . . . . . . . . . . . . . 44
168
MEMO
169
REVISIONS
*The manual number is given on the bottom left of the back cover.
Revision date *Manual number Description
May 2016 SH(NA)-081616ENG-A First edition
August 2016 SH(NA)-081616ENG-B Error correction
January 2017 SH(NA)-081616ENG-C  Added or modified parts
SAFETY PRECAUTIONS, INTRODUCTION, TERMS, Section 1.2, 1.5, 1.8, 2.1, 4.7, 4.8
December 2017 SH(NA)-081616ENG-D ■Added function
Safety communication relay function
■Added or modified parts
SAFETY PRECAUTIONS, RELEVANT MANUALS, TERMS, Section 1.2, 1.8, 1.9, 2.1, 4.5, 4.6,
Appendix 6, 7
Japanese manual number: SH-081615-C

This manual confers no industrial property 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.
 2016 MITSUBISHI ELECTRIC CORPORATION
170
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 to:
(1) Damages caused by any cause found not to be the responsibility of Mitsubishi.
(2) Loss in opportunity, lost profits incurred to the user by Failures of Mitsubishi products.
(3) Special damages and secondary damages whether foreseeable or not, compensation for accidents, and
compensation for damages to products other than Mitsubishi products.
(4) 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.
171
TRADEMARKS
Ethernet is a registered trademark of Fuji Xerox Co., Ltd. in Japan.
The company names, system names and product names mentioned in this manual are either registered trademarks or
trademarks of their respective companies.
In some cases, trademark symbols such as '' or '' are not specified in this manual.
172 SH(NA)-081616ENG-D
SH(NA)-081616ENG-D(1712)MEE
MODEL: RJ72GF15-T2-U-OU-E
MODEL CODE: 13JX53
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.

MELSEC iQ-R CC-Link IE Field Network Remote Head Module User's Manual (Application)

Uploaded by

Copyright:

Available Formats

MELSEC iQ-R CC-Link IE Field Network Remote Head Module User's Manual (Application)

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MELSEC iQ-R CC-Link IE Field Network Remote Head Module User's Manual (Application)

Uploaded by

Copyright:

Available Formats

MELSEC iQ-R CC-Link IE Field Network

Remote Head Module User's Manual

Indicates that incorrect handling may cause hazardous conditions, resulting in

Indicates that incorrect handling may cause hazardous conditions, resulting in

[Startup and Maintenance Precautions]

CHAPTER 2 PARAMETER SETTINGS 76

CHAPTER 3 AVAILABLE FILE OPERATION 85

1.1 Data Communication

Data communication with the master station

Data communication with the connected module

Cyclic transmission of bit device data

(1) (2) (3)

RJ72GF15-T2 RX10 RY10R2 RX10 RY10R2

RJ72GF15-T2 RX10 RY10R2 RX10 RY10R2

(1) (2) (3)

(1) Master station

Specify the following devices as the devices to be refreshed.

■Using an engineering tool

■By an external device using SLMP

■Using the module dedicated instructions

Remote RESET setting

■Using an engineering tool

■By an external device using SLMP

(1) Remote head module

Check method of error

■Using the special relay and special register

■Using the engineering tool

Operation setting at error detection

■Mode when an error is detected

■Error detection setting

Error clear of only specific remote head module

■How to clear errors

• Using SM/SD: Clear errors by operating SM/SD.

2. Eliminate the cause of the detected error.

3. Turn off and on 'Error reset' (SM50).

■How to clear errors

1. Eliminate the causes of the errors in the remote head modules.

■Events stored in the remote head module

■Event history file

■Loss of event history information

Clearing the event history

Redundant power supply system diagnostics

For details on the special relay (SM), refer to the following.

For details on the special register (SD), refer to the following.

■Preventing detection of error in redundant power supply module

2. Replace the redundant power supply module.

■Detecting error in redundant power supply module

2. Replace the redundant power supply module.

2. Turn on 'Error clear' (SB000F) of the master station.

Data to be protected Purpose Function Reference

For the method of current value change, refer to the following.

■Redundant slave station

(2) (3) (4)

(1) Master station

Mounting modules and connecting cables

Resetting the remote head module

Before system switching operation

No.0 No.1 No.2 No.3

• Remote head module23

Item Description Setting Range12