Mitsubishi Electric MELSEC iQ-R Series User manual

MELSEC iQ-R CANopen Module
User's Manual (Application)
-RJ71CN91

1
SAFETY PRECAUTIONS
(Read these precautions before using this product.)
Before using this product, please read this manual and the relevant manuals carefully and pay full attention to safety to handle
the product correctly.
The precautions given in this manual are concerned with this product only. For the safety precautions 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".
Under some circumstances, failure to observe the precautions given under " CAUTION" may lead to serious
consequences.
Observe the precautions of both levels because they are important for personal and system safety.
Make sure that the end users read this manual and then keep the manual in a safe place for future reference.
WARNING Indicates that incorrect handling may cause hazardous conditions, resulting in
death or severe injury.
CAUTION Indicates that incorrect handling may cause hazardous conditions, resulting in
minor or moderate injury or property damage.

2
[Design Precautions]
WARNING
●Configure safety circuits external to the programmable controller to ensure that the entire system
operates safely even when a fault occurs in the external power supply or the programmable controller.
Failure to do so may result in an accident due to an incorrect output or malfunction.
(1) Emergency stop circuits, protection circuits, and protective interlock circuits for conflicting
operations (such as forward/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.

3
[Design Precautions]
[Design Precautions]
WARNING
●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.
●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.
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.

4
[Installation Precautions]
[Installation Precautions]
[Wiring Precautions]
WARNING
●Shut off the external power supply (all phases) used in the system before mounting or removing the
module. Failure to do so may result in electric shock or cause the module to fail or malfunction.
CAUTION
●Use the programmable controller in an environment that meets 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.
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]
[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
operation may damage machines or cause accidents.
●Especially, when a remote programmable controller is controlled by an external device, immediate
action cannot be taken if a problem occurs in the programmable controller due to a communication
failure. To prevent this, configure an interlock circuit in the program, and determine corrective actions
to be taken between the external device and CPU module in case of a communication failure.
●Do not disassemble or modify the modules. Doing so may cause failure, malfunction, injury, or a fire.
●Use any radio communication device such as a cellular phone or PHS (Personal Handy-phone
System) more than 25cm away in all directions from the programmable controller. Failure to do so
may cause malfunction.
●Shut off the external power supply (all phases) used in the system before mounting or removing the
module. Failure to do so may cause the module to fail or malfunction.
●Tighten the screws within the specified torque range. Undertightening can cause drop of the
component or wire, short circuit, or malfunction. Overtightening can damage the screw and/or module,
resulting in drop, short circuit, or malfunction.
●After the first use of the product, do not mount/remove the module to/from the base unit, and the
terminal block to/from the module, and do not insert/remove the extended SRAM cassette to/from the
CPU module more than 50 times (IEC 61131-2 compliant) respectively. Exceeding the limit may cause
malfunction.
●After the first use of the product, do not insert/remove the SD memory card to/from the CPU module
more than 500 times. Exceeding the limit may cause malfunction.
●Do not touch the metal terminals on the back side of the SD memory card. Doing so may cause
malfunction or failure of the module.
●Do not touch the integrated circuits on the circuit board of an extended SRAM cassette. Doing so may
cause malfunction or failure of the module.
●Do not drop or apply shock to the battery to be installed in the module. Doing so may damage the
battery, causing the battery fluid to leak inside the battery. If the battery is dropped or any shock is
applied to it, dispose of it without using.

7
[Startup and Maintenance Precautions]
[Operating Precautions]
[Disposal Precautions]
[Transportation Precautions]
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.
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 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 can cause malfunction or failure of the
module.
CAUTION
●When disposing of this product, treat it as industrial waste.
●When disposing of batteries, separate them from other wastes according to the local regulations. For
details on battery regulations in EU member states, refer to the MELSEC iQ-R Module Configuration
Manual.
CAUTION
●When transporting lithium batteries, follow the transportation regulations. For details on the regulated
models, refer to the MELSEC iQ-R Module Configuration Manual.
●The halogens (such as fluorine, chlorine, bromine, and iodine), which are contained in a fumigant
used for disinfection and pest control of wood packaging materials, may cause failure of the product.
Prevent the entry of fumigant residues into the product or consider other methods (such as heat
treatment) instead of fumigation. The disinfection and pest control measures must be applied to
unprocessed raw wood.

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

9
INTRODUCTION
Thank you for purchasing the Mitsubishi Electric MELSEC iQ-R series programmable controllers.
This manual describes the functions, parameter settings, programming, and troubleshooting of the relevant product 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.
When applying the program examples provided in this manual to an actual system, ensure the applicability and confirm that it
will not cause system control problems.
Please make sure that the end users read this manual.
Relevant product
RJ71CN91

10
CONTENTS
SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
CONDITIONS OF USE FOR THE PRODUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
INTRODUCTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
RELEVANT MANUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
CHAPTER 1 FUNCTIONS 15
1.1 Overview of CANopen and CAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.2 NMT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
NMT state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Node control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
NMT start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Error event control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Boot-up control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Flying master. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
LSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Configuration manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.3 SDO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
SDO read. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
SDO multi read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
SDO write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
SDO multi write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
1.4 PDO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
TPDO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
RPDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
1.5 SYNC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
1.6 TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
1.7 EMCY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
1.8 Node Guarding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
1.9 Heartbeat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
1.10 Operation Setting at Error Occurrence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
1.11 Layer 2 Message Transmission and Receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Data transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
RTR transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
RTR response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Data reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Data/RTR transmission via CIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
1.12 CPU Module STOP Transition Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
CHAPTER 2 PARAMETER SETTINGS 73
2.1 Setting Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
2.2 Basic Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
2.3 Refresh Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Refresh processing time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
2.4 CANopen Setting (Starting CANopen Configuration Tool) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
CHAPTER 3 CANopen Configuration Tool 79

11
CONTENTS
3.1 Window Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Parameter window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Description window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
3.2 Setting Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Creating a new project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Transfer setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Parameter settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Writing the settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
3.3 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Network scan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
SDO send/receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Export/import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Module status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Select language. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
NMT master reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
3.4 Checking the Software Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
CHAPTER 4 PROGRAMMING 120
4.1 Communication Example of Layer 2 Message Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
System configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Parameter settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Program example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
4.2 Communication Example of CANopen 405 Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
CHAPTER 5 TROUBLESHOOTING 135
5.1 Checking with LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
5.2 Checking the Module Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
5.3 Troubleshooting Using the Buffer Memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
5.4 Troubleshooting by Symptom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
CANopen 405 mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Layer 2 message mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
5.5 List of Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
5.6 Event List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
APPENDICES 146
Appendix 1 I/O Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
List of I/O signals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Details of I/O signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Appendix 2 Buffer Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
List of buffer memory addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Details of buffer memory areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Appendix 3 Object Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Object dictionary list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Data type definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Communication profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Standard interface profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Object dictionary details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Appendix 4 Operation of the RJ71CN91 When the CPU Module Operating Status Is Changed. . . . . . . . . . . . . 221
Appendix 5 How to Set Parameters When Not Using CANopen Configuration Tool. . . . . . . . . . . . . . . . . . . . . . 223

12
Setting parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
List of buffer memory areas where parameters are set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
List of object dictionary to be set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
INDEX 226
REVISIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228
WARRANTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .229
TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .230

13
RELEVANT MANUALS
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.
Manual name [manual number] Description Available form
MELSEC iQ-R CANopen Module User's Manual
(Application)
[SH-081736ENG] (this manual)
Functions, parameter settings, programming, troubleshooting, I/O signals,
buffer memory, and object dictionary of the CANopen module
Print book
e-Manual
PDF
MELSEC iQ-R CANopen Module User's Manual
(Startup)
[SH-081734ENG]
Performance specifications, procedures before operation, system
configuration, wiring, and communication examples of the CANopen module
Print book
e-Manual
PDF

14
TERMS
Unless otherwise specified, this manual uses the following terms.
Term Description
Buffer memory Memory in an intelligent function module for storing data such as setting values and monitored values.
When integrated into the CPU module, this memory refers to a memory for storing data such as setting values and
monitored values of the Ethernet function, and data used for data communication of the multiple CPU system function.
CAN The abbreviation for Controller Area Network
CANopen CAN based higher-layer protocol
CDCF The abbreviation for the concise device configuration file.
CiA The abbreviation for CAN in Automation.
Non-profit organization for standardization of CAN protocols.
CIF The abbreviation for the command interface.
CPU module A generic term for the MELSEC iQ-R series CPU module
Device A device (X, Y, M, D, or others) in a CPU module
Engineering tool Another term for the software package for the MELSEC programmable controllers
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 GX
Works3, and an optional label, which can be created for any specified device.
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
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.
RTR The abbreviation for the remote transmit request.

1 FUNCTIONS
1.1 Overview of CANopen and CAN 15
1
1FUNCTIONS
1.1 Overview of CANopen and CAN
This section describes overview of CANopen and CAN.
Function modes
The RJ71CN91 has three function modes. Available functions and buffer memory assignment vary depending on the function
mode. (Page 154 Buffer Memory)
The following table lists and describes the overview of the function modes.
The following table shows availability of functions in each function mode.
: Available, : Not available
Function mode Overview
CANopen 405 mode This mode is used to communicate with CANopen nodes. CAN nodes cannot be used.
11-bit CAN-ID Layer 2 message
mode
This mode is used to communicate with CAN nodes. CANopen nodes cannot be used.
The standard format (11-bit CAN-ID) is used for communications.
29-bit CAN-ID Layer 2 message
mode
This mode is used to communicate with CAN nodes. CANopen nodes cannot be used.
The extended format (29-bit CAN-ID) is used for communications.
Function CANopen 405 mode 11-bit CAN-ID Layer 2 message mode, 29-
bit CAN-ID Layer 2 message mode
NMT 
SDO 
PDO 
SYNC 
TIME 
EMCY 
Node guarding 
Heartbeat 
Operation setting at error occurrence 
Layer 2 message transmission and receive 
CPU module STOP transition message 

16 1 FUNCTIONS
1.1 Overview of CANopen and CAN
CAN-ID
CAN-ID is an identifier used for bus arbitration and identification of CAN messages.
In bus arbitration, a CAN message with a smaller ID has higher priority to use the bus. CAN-IDs with lower priority will wait
until the bus is free.
This section describes CAN-IDs used in each function mode.
■CANopen 405 mode
11-bit CAN-IDs are used. As shown below, in CANopen, a CAN-ID is composed of a node ID and function code.
In CANopen, each function comes with a function code. However, for some functions, a CAN-ID can be set as desired. The
following table shows CAN-IDs used for the functions of this module and whether CAN-IDs can be set as desired.
: Can be set, : Cannot be set
*1 Broadcast message; Node ID is fixed as 0.
*2 Cannot be set with the parameter of CANopen Configuration Tool. Specify the value with the object dictionary.
For details on the setting method, refer to the following.
Page 223 How to Set Parameters When Not Using CANopen Configuration Tool
*3 The CAN-ID of EMCY to be sent by the own node cannot be changed. However, the CAN-ID of a message to be received as EMCY can
be set as desired for the ID of each target node.
*4 To set the CAN-ID as desired, it is not possible to use the same CAN-ID as the CAN-ID of another function used in the same network, or
the CAN-ID that is use-prohibited (reserved) in CANopen. The following table shows whether or not each CAN-ID (range) is available for
use as desired in this module.
Function Optional setting Function code (binary) Node ID CAN-ID
NMT 0000 00H*1 0000H
SYNC *2 0001 00H*1 0080H
EMCY *3 0001 01H to 7FH 0081H to 00FFH
TIME *2 0010 00H*1 0100H
TPDO Optional*4 Optional*4 Optional*4
RPDO Optional*4 Optional*4 Optional*4
SDO (Request) 1011 01H to 7FH 0581H to 05FFH
SDO (Response) 1100 01H to 7FH 0601H to 067FH
NMT error control 1110 01H to 7FH 0701H to 077FH
b10 b7 b6 b0
Function code
CAN message
11-bit CAN-ID
Data11-bit CAN-ID
Node ID

1 FUNCTIONS
1.1 Overview of CANopen and CAN 17
1
: Available, : Not available
*5 Do not use the CAN-ID used in the network by another function. The duplication of the CAN-ID with another function may cause
malfunction.
■11-bit CAN-ID Layer 2 message mode
11-bit CAN-IDs are used. Set any value for each node and each CAN message.
■29-bit CAN-ID Layer 2 message mode
29-bit CAN-IDs are used. Set any value for each node and each CAN message.
Object dictionary
Object dictionary is a structure with specifications defined in CANopen. It is used in the CANopen 405 mode.
The data within the object dictionary is used to set CAN bus parameters, initialize special functions, control data flow, store
data in various formats and send EMCY messages. (Page 186 Object Dictionary)
To read and write data from/to the object dictionary, use the SDO function. (Page 28 SDO)
CAN-ID Availability Remarks
0000H Used in the NMT function.
0001H to 007FH Use prohibited in CANopen.
0080H Used in the SYNC function.
0081H to 00FFH Used in the EMCY function.
0100H Used in the TIME function.
0101H to 0180H Use prohibited in CANopen.
0181H to 0580H *5 
0581H to 5FFH Used in the SDO function.
0600H *5 
0601H to 067FH Used in the SDO function.
0680H to 06DFH *5 
06E0H to 06FFH Use prohibited in CANopen.
0701H to 077FH Used in NMT error control.
0780H to 07FFH Use prohibited in CANopen.

18 1 FUNCTIONS
1.2 NMT
1.2 NMT
NMT is a function to manage the CANopen network status. The NMT master controls all NMT slaves within the CANopen
network.
NMT state
NMT state is the operating status of a CANopen node. When the NMT state is Operational, the CANopen node is capable of
all communications.
The following table lists the NMT states for the RJ71CN91.
The following figure shows the NMT state transition paths (No.1 to 9).
NMT state Description
Initialization The CANopen node is being initialized.
Pre-operational Communications other than PDO are possible. (SDO, SYNC, EMCY, TIME, Node control, and Heartbeat/
Node-guarding communications are possible.)
Changing the object dictionary regarding PDO, setting and changing CANopen node parameters are
possible.
CANopen nodes that are powered off and on or reset will enter this state automatically.
Operational All communications are possible. (PDO, SDO, SYNC, EMCY, TIME, Node control, and Heartbeat/Node-
guarding communications are possible.)
A CANopen node transitions to this state automatically or requires node control by the NMT master.
When all nodes enter this state, start-up of the CANopen network is completed.
Stop All communications are stopped. (Only Node control and Heartbeat/Node-guarding communications are
possible.)
A CANopen node transitions to this state when it has an error or is executing a specific application.
(1) Initialization
(2) Pre-operational
(3) Operational
(4) Stop
Path
Number
Condition for the NMT state to change
NMT master NMT slaves
1 Power off and on or reset Power off and on or reset
2 CANopen node initialization is completed. CANopen node initialization is completed.
3 • NMT start-up is enabled.*1
• Remote node start is accepted.*3
• Remote node start is accepted.*3
4 • A communication error is detected.*2
• Pre-operational transition is accepted.*3
• A communication error is detected.*2
• Pre-operational transition is accepted.*3
5 • Remote node stop is accepted.*3 • Remote node stop is accepted.*3
(1)
(2)
(3)
START
No.1
No.9
No.2
No.3 No.4
No.5
No.7
(4)
No.8
No.6