Mitsubishi Electric MELSEC iQ-R C Owner's manual

MELSEC iQ-R C Controller Module
Programming Manual

1
SAFETY PRECAUTIONS
(Read these precautions before using this product.)
Before using C Controller module, please read this manual and the relevant manuals carefully and pay full attention to safety
to handle the product correctly.
Make sure that the end users read this manual and then keep the manual in a safe place for future reference.
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.

2
CONSIDERATIONS FOR USE
Considerations for the Wind River Systems product
C Controller module has an embedded real-time operating system, VxWorks, manufactured by Wind River Systems, Inc. in
the United States. We, Mitsubishi, make no warranty for the Wind River Systems product and will not be liable for any
problems and damages caused by the Wind River Systems product during use of C Controller module.
For the problems or specifications of the Wind River Systems product, refer to the corresponding manual or consult Wind
River Systems, Inc.
Contact information is available on the following website.
• Wind River Systems, Inc.: www.windriver.com
INTRODUCTION
Thank you for purchasing the Mitsubishi MELSEC iQ-R series programmable controllers.
This manual describes the functions required for programming.
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.

3
CONTENTS
CONTENTS
SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
CONDITIONS OF USE FOR THE PRODUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
CONSIDERATIONS FOR USE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
INTRODUCTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
RELEVANT MANUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
CHAPTER 1 COMMON ITEMS 7
1.1 Header Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2 C Controller Module Dedicated Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Program processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Argument specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.3 MELSEC Data Link Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Program processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Accessible range and devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Argument specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
1.4 Considerations on Interrupt Service Routine (ISR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
CHAPTER 2 FUNCTION LIST 44
2.1 C Controller Module Dedicated Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
C Controller module dedicated functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
C Controller module dedicated functions for ISR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
2.2 MELSEC Data Link Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
CHAPTER 3 DETAILS OF FUNCTION 48
3.1 C Controller Module Dedicated Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
C Controller module dedicated functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
C Controller module dedicated functions for ISR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
3.2 MELSEC Data Link Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
CHAPTER 4 ERROR CODE LIST 174
4.1 Common Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
4.2 C Controller Module Dedicated Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
4.3 MELSEC Data Link Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
4.4 Error Codes Different From Conventional Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
APPENDIX 188
Appendix 1 Example for Replacing Ladder by C Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Program example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Appendix 2 How to Replace an Existing Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Replacement of projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Replacement of VxWorks standard API functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Replacement of functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Replacement of device type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Compilation of replaced project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

4
Appendix 3 Correspondence Table to Conventional Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
C Controller module dedicated functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
C Controller module dedicated function for ISR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Bus interface functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Bus interface functions for ISR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
MELSEC data link functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
INDEX 198
FUNCTION INDEX 200
REVISIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202
WARRANTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203
TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204

5
RELEVANT MANUALS
e-Manual refers to the Mitsubishi FA electronic book manuals that can be browsed using a dedicated tool.
e-Manual has the following features:
• Required information can be cross-searched in multiple manuals.
• Other manuals can be accessed from the links in the manual.
• Hardware specifications of each part can be found from the product figures.
• Pages that users often browse can be bookmarked.
Manual name [manual number] Description Available form
MELSEC iQ-R C Controller Module Programming Manual
[SH-081371ENG] (this manual)
Explains the programming specifications and dedicated
function library of a C Controller module.
e-Manual
PDF
MELSEC iQ-R C Controller Module User's Manual
(Startup)
[SH-081367ENG]
Explains the performance specifications, procedure before
operation, and troubleshooting of a C Controller module.
Print book
e-Manual
PDF
MELSEC iQ-R C Controller Module User's Manual
(Application)
[SH-081369ENG]
Explains the functions, devices, and parameters of a C
Controller module.
Print book
e-Manual
PDF
CW Workbench/CW-Sim Operating Manual
[SH-081373ENG]
Explains the system configuration, specifications, functions,
and troubleshooting of CW Workbench/CW-Sim.
e-Manual
PDF

6
TERMS
Unless otherwise specified, this manual uses the following terms.
Term Description
Basic model QCPU A generic term for Q00JCPU, Q00CPU, and Q01CPU.
C Controller module A generic term for MELSEC iQ-R series C Controller module.
C Controller module dedicated function A dedicated function library offered by C Controller module.
It is used to control the C Controller module.
CC-Link IE Controller Network module An abbreviation for CC-Link IE Controller Network module, RJ71GP21-SX.
CC-Link IE Field Network module An abbreviation for CC-Link IE Field Network module, RJ71GF11-T2.
CC-Link module An abbreviation for CC-Link module, RJ61BT11.
CW Configurator A generic product name for SWnDND-RCCPU. ('n' indicates its version.)
CW Workbench An abbreviation for C Controller module and C intelligent function module engineering tool, CW
Workbench.
CW-Sim An abbreviation for VxWorks simulator that can operate and debug the C Controller module and C
intelligent function module programs on a personal computer on which CW Workbench installed, without
connecting to the actual machine (target).
Dedicated function library A generic term for C Controller module dedicated function and MELSEC data link function.
Existing product A generic term for Q12DCCPU-V (Basic mode/Extended mode).
High Performance model QCPU A generic term for Q02CPU, Q02HCPU, Q06HCPU, Q12HCPU, and Q25HCPU.
Intelligent function module A generic term for modules which has functions other than input and output, such as A/D converter module
and D/A converter module.
MELSEC data link function A data link function library offered by C Controller module.
It is used to access other CPU modules as a connection target via network or in a multiple CPU system.
Process CPU A generic term for Q02PHCPU, Q06PHCPU, Q12PHCPU, and Q25PHCPU.
R12CCPU-V An abbreviation for R12CCPU-V C Controller module.
RCPU A generic term for R04CPU, R04ENCPU, R08CPU, R08PCPU, R08ENCPU, R08SFCPU, R16CPU,
R16PCPU, R16ENCPU, R16SFCPU, R32CPU, R32PCPU, R32ENCPU, R32SFCPU, R120CPU,
R120PCPU, R120ENCPU, and R120SFCPU.
Redundant CPU A generic term for Q12PRHCPU and Q25PRHCPU.
Universal model QCPU A generic term for Q00UJCPU, Q00UCPU, Q01UCPU, Q02UCPU, Q03UDCPU, Q03UDVCPU,
Q03UDECPU, Q04UDHCPU, Q04UDVCPU, Q04UDEHCPU, Q06UDHCPU, Q06UDVCPU,
Q06UDEHCPU, Q10UDHCPU, Q10UDEHCPU, Q13UDHCPU, Q13UDVCPU, Q13UDEHCPU,
Q20UDHCPU, Q20UDEHCPU, Q26UDHCPU, Q26UDVCPU, Q26UDEHCPU, Q50UDEHCPU, and
Q100UDEHCPU.
VxWorks A product name for the real-time operating system manufactured by Wind River Systems, Inc.

1 COMMON ITEMS
1.1 Header Files 7
1
1COMMON ITEMS
A user program is created by using the VxWorks standard API functions*1 and dedicated function library offered by a C
Controller module in accordance with the specification of VxWorks, the operating system of C Controller module.
*1 For details on the VxWorks standard API functions, refer to the following programmer's guide supported.
VxWorks "KERNEL PROGRAMMER'S GUIDE"
Dedicated function libraries offered by a C Controller module are as follows:
• C Controller module dedicated function
• MELSEC Data Link Functions
For the execution procedure of user programs, refer to the following manual.
MELSEC iQ-R C Controller Module User's Manual (Startup)
1.1 Header Files
Include the following header files in a user program to use the dedicated function library.
A header file is stored in a C Controller module.
(MELSEC iQ-R C Controller Module User's Manual (Application)
Dedicated function library Header file
C Controller module dedicated function CCPUFunc.h
MELSEC data link function MDFunc.h

81 COMMON ITEMS
1.2 C Controller Module Dedicated Functions
1.2 C Controller Module Dedicated Functions
C Controller dedicated functions of the dedicated function libraries are used to control C Controller module.
These functions can be used for reading status of C Controller module or accessing resources such as LED control and clock.
Program processing
The following shows the user program processing using the C Controller module dedicated function.
1. Start a task.
2. Read the status of C Controller module and access the resources such as LED control and clock by using the C
Controller module dedicated function.
3. Complete the task.
Considerations
Considerations for user WDT (user watchdog timer)
■User WDT error occurrence
If a user WDT cannot be reset due to a user program runaway, a user WDT error will occur.
In this case, take the following corrective actions.
• Increase the user WDT period set with the CCPU_StartWDT function.
• Lower the number of tasks with high CPU utilization or make them deactivated.
• Review the user program.
Reset the C Controller module once the corrective actions have been taken.
In the user program, a user WDT can be used to monitor the hardware and status of user program, and
processing timeout for accessing and controlling each module.
■User WDT setting range
The user WDT period can be set within the range of 100 ms to 10,000 ms.
■Output when a user WDT error occurs
When a user WDT error occurs, the output turns OFF.
Considerations for the dedicated instructions
Considerations for argument are shown below:
• For the first argument, "pcInstName", categorizing the dedicated instructions (D/DP/J/JP/G/GP/M) is not required.
• Devices of the own station cannot be specified. Reserve the required area with a user program, and specify the start
address of the area to the relevant argument.
• Specify devices of other stations by using a character string. Set the value (the number of elements to which one is added
for the termination code) to the number of elements for the array.
(Example) To specify D4: char cDev[3] = {"D4"};
Set '3', the total number of '2' for D4 and '1' for termination code, to the number of elements for the character string.
• When the data type is device name (control data, input data, and output data), specify the argument using an array.
• The size is required to be set according to the number of elements for the array, which is specified to the argument. When
data type is 16-bit binary, BCD 4-digit, or real number, set the size to '1'. When data type is 32-bit binary or BCD 8-digit, set
the size to '2'.
• When data type is bit (completion device), specify the argument using an array. Specify '1' for completion or '0' for
incompletion to the first array. In the second array, '0' or '1' is stored for the normal completion or abnormal completion,
respectively.
• For arguments without the setting data, set the setting data to NULL, and set the size to '0'.
• Errors which occur in the dedicated instruction are not registered in the event history.

1 COMMON ITEMS
1.2 C Controller Module Dedicated Functions 9
1
Argument specification
This section shows the argument specifications of the C Controller module dedicated functions.
Device type
The following tables show the device types specified to the C Controller module dedicated functions.
Devices are defined in the header file "CCPUFunc.h".
Either a code or a device name can be specified as a device type.
■Device types for accessing CC-Link IE Controller Network modules
Device type can be specified to the argument sDevType of the CCPU_WriteLinkDevice/CCPU_ReadLinkDevice functions.
■Device types for accessing CC-Link IE Field Network modules
Device type can be specified to the argument sDevType of the CCPU_WriteLinkDevice/CCPU_ReadLinkDevice functions.
*1 Using the following device range enables direct link registers (RWw, RWr) to be accessed.
RWw: LW0 to LW1FFF
RWr: LW2000 to LW3FFF
■Device types for accessing internal user devices and internal system devices
Device type can be specified to the argument sDevType of the CCPU_WriteDevice/CCPU_ReadDevice/CCPU_SetDevice/
CCPU_ResetDevice/CCPU_WriteDevice_ISR/CCPU_ReadDevice_ISR/CCPU_SetDevice_ISR/CCPU_ResetDevice_ISR
functions.
Device (Device name) Device type
Code Device name
Decimal Hexadecimal
Direct link input (LX) 1000 3E8H Dev_LX
Direct link output (LY) 2000 7D0H Dev_LY
Direct link relay (LB) 23000 59D8H Dev_LB
Direct link register (LW) 24000 5DC0H Dev_LW
Direct link special relay (SB) 25000 61A8H Dev_LSB
Direct link special register (SW) 28000 6D60H Dev_LSW
Device (Device name) Device type
Code Device name
Decimal Hexadecimal
Direct link input (RX) 1000 3E8H Dev_LX
Direct link output (RY) 2000 7D0H Dev_LY
Direct link register (RWr, RWw)*1 24000 5DC0H Dev_LW
Direct link special relay (SB) 25000 61A8H Dev_LSB
Direct link special register (SW) 28000 6D60H Dev_LSW
Device (Device name) Device type
Code Device name
Decimal Hexadecimal
Internal relay (M) 4 4H Dev_CCPU_M
Special relay (SM) 5 5H Dev_CCPU_SM
Data register (D) 13 DH Dev_CCPU_D
Special register (SD) 14 EH Dev_CCPU_SD
Link relay (B) 23 17H Dev_CCPU_B
Link register (W) 24 18H Dev_CCPU_W
File register (ZR) 220 DCH Dev_CCPU_ZR

10 1 COMMON ITEMS
1.3 MELSEC Data Link Functions
1.3 MELSEC Data Link Functions
MELSEC data link functions are the integrated communication function libraries which are independent of the communication
protocols.
A program to communicate with a CPU module can be created regardless of a target hardware or communication protocols
by using the MELSEC data link functions.
The communication functions supported by the MELSEC data link functions are as follows:
Program processing
The following shows the user program processing using the MELSEC data link function.
When accessing with a device name
1. Start a task.
2. Open a communication line. (mdOpen function)
3. Perform dummy access (such as device/model name reading) to an access target.
4. Access the target by using the MELSEC data link function.
5. To stop accessing the target, go to the procedure 6.
To access the target again, go back to the procedure 4.
6. Close the communication line. (mdClose function)
7. Complete the task.
When accessing with a label name
1. Start a task.
2. Open a communication line. (mdOpen function)
3. Acquire device information (label assignment information) from a target CPU module. (mdGetLabelInfo function)
4. Access the target CPU module by using the acquired device information (label assignment information).
(mdRandRLabelEx/mdRandWLabelEx function)
5. Check if there is no change in the device information (label assignment information) of the target CPU module.
If it is changed, go back to the procedure 3.
6. To stop accessing the target, go to the procedure 7.
To access the target again, go back to the procedure 4.
7. Close the communication line. (mdClose function)
8. Complete the task.
Communication function Description
Bus interface communication Accesses a CPU module mounted on the same base unit.
CC-Link IE Controller Network communication Accesses a CPU module on the CC-Link IE Controller Network via a CC-Link IE Controller Network
module.
CC-Link IE Field Network communication Accesses a CPU module on the CC-Link IE Field Network via a CC-Link IE Field Network module.
MELSECNET/H network communication Accesses a CPU module on the MELSECNET/H network via a MELSECNET/H network module.
CC-Link communication Accesses a CPU module on the CC-Link via a CC-Link module.

1 COMMON ITEMS
1.3 MELSEC Data Link Functions 11
1
Considerations
The following shows the considerations when using the MELSEC data link functions.
Considerations for programming
■Open/close processing of a communication line (mdOpen/mdClose function)
Perform the open/close processing of communication line (the mdOpen/mdClose function) only once at the start of task (task
activation) and at the end of task (task completion) respectively in each user program. Opening/closing the line every
communication decreases the communication performance.
■Execution after using the mdOpen function
At the first execution of the function after using the mdOpen function, it takes longer to execute the function since the CPU
module information needs to be acquired. The succeeding processing time can be shortened by performing dummy access at
the first time.
■Access to other stations on the same task
Accessing 33 or more other stations simultaneously on the same task of C Controller module using a user program may
decrease the communication performance. To access other stations simultaneously on the same task, limit it to 32 or less
stations.
■mdGetLabelInfo function call
The mdGetLabelInfo function does not need to be called each time to access a target CPU module.
Only if the error occurs (Error code: -81) when accessing by using the mdRandRLabelEx/mdRandWLabelEx function , call the
mdGetLabelInfo function again.
■taskDelete execution
Do not execute the taskDelete in a task using the MELSEC data link function. Also, do not delete a task using the MELSEC
data link function with the taskDelete. Otherwise, the MELSEC data link function may not operate properly.

12 1 COMMON ITEMS
1.3 MELSEC Data Link Functions
Accessing devices of the own station and of a CPU module on other stations
An interlock may be required to be provided depending on the link status of the own station and other stations.
■Access to devices on the own station
Create a user program that provides an interlock to enable reading/writing data when the following conditions are satisfied to
access devices via each network module.
Even if the above conditions are not satisfied; however, read/write processing to the own station is completed normally.
■Other station transient access (other station CPU module remote operation and device
access)
Create a user program that provides an interlock to enable reading/writing data when the following conditions are satisfied to
access devices via each network module.
Module to be routed Condition that requires interlock
CC-Link IE Controller Network module When the following conditions are met:
• The bits of the own station data link error status (SB49) is OFF (data linking).
• The cyclic transmission status (the bit corresponding to the communication target station which is stored from
SWB0 to B7) is OFF (normal communication).
CC-Link IE Field Network master/local
module
MELSECNET/H network module When the following conditions are met:
• The module status (SB20) is OFF (normal).
• The bits of the own station baton pass status (SB47) is OFF (normal).
• The bits of the own station data link status (SB49) is OFF (data linking).
CC-Link module When the following conditions are met:
• The module error (Xn0) is OFF (normal).
• 'Module READY' (XnF) is ON (activated).
• The bits of the own station data link status (Xn1) is ON (data linking).
Module to be routed Condition that requires interlock
CC-Link IE Controller Network module When the following conditions are met:
• The bits of the own station baton pass status (SB47) is OFF (normal).
• The baton pass status of a station to be accessed (the bit corresponding to the communication target station
which is stored from SWA0 to A7) is OFF (normal communication).
CC-Link IE Field Network master/local
module
MELSECNET/H network module When the following conditions are met:
• The condition that turns the interlock ON is met when accessing devices on the own station.
• The baton pass status of a station to be accessed (the bit corresponding to the communication target station
which is stored from SW70 to 73) is OFF (normal communication).
• The data link status (the bit corresponding to the communication target station which is stored from SW74 to
77) is OFF (normal communication).
CC-Link module When the following conditions are met:
• The condition that turns the interlock ON is met when accessing devices on the own station.
• The data link status of a station to be accessed (the bit corresponding to the communication target station
which is stored from SW80 to 83) is OFF (normal communication).

1 COMMON ITEMS
1.3 MELSEC Data Link Functions 13
1
Accessible range and devices
This section explains the accessible range and accessible devices when using MELSEC data link functions.
Bus interface communication
The following explains the accessible range and devices for bus interface communication.
■Accessible range
The accessible range for bus interface communication includes the own station (C Controller module), and the CPU module
and C Controller module in a multiple CPU system.
■Accessible devices
The devices accessible for communication via a bus are shown below.
• 'Batch' and 'Random' in the following table indicate as follows:
Batch: Batch write (mdSendEx function), batch read (mdReceiveEx function)
Random: Random write (mdRandWEx function), random read (mdRandREx function), bit set (mdDevSetEx
function), bit reset (mdDevRstEx function), random write by using a label name (mdRandWLabelEx
function), random read by using a label name (mdRandRLabelEx function)
• Bit devices can be accessed by using 'bit set' (mdDevSetEx function) and 'bit reset' (mdDevRstEx function).
• The fixed cycle communication area can be accessed only when the multiple CPU setting is configured.
• Device extension specifications (digit specification, bit specification and index specification) cannot be used.
• Accessing the host CPU
The following table shows the accessible devices when accessing the host module.
: Accessible, : Not accessible
Device Access method Access
target CPU
R12CCPU-V
Input relay X Batch/random 
Output relay Y Batch/random 
Internal relay M Batch/random 
Special relay SM Batch/random 
Data register D Batch/random 
Special register SD Batch/random 
Link relay B Batch/random 
Link register W Batch/random 
File register ZR Batch/random 
Intelligent function module device, module access device Un\G Batch/random 
CPU buffer memory U3En\G Batch 
Random 
Fixed cycle communication area U3En\HG Batch 
Random 
C Controller module
System configuration

14 1 COMMON ITEMS
1.3 MELSEC Data Link Functions
• Accessing the other CPU
The following table shows the accessible devices when accessing the other CPUs (that is a CPU module and a C Controller
module in a multiple CPU system).
: Accessible, : Not accessible
No. Access target CPU
(1) RCPU
(2) R12CCPU-V
Device Access method Access target CPU
(1) (2)
Input relay X Batch/random 
Output relay Y Batch/random 
Latch relay L Batch/random 
Internal relay M Batch/random 
Special relay SM Batch/random 
Annunciator F Batch/random 
Timer (Contact) T Batch/random 
Long timer (Contact) LT Batch/random 
Timer (Coil) T Batch/random 
Long timer (Coil) LT Batch/random 
Counter (Contact) C Batch/random 
Long counter (Contact) LC Batch/random 
Counter (Coil) C Batch/random 
Long counter (Coil) LC Batch/random 
Timer (Current value) T Batch/random 
Long timer (Current value) LT Batch/random 
Counter (Current value) C Batch/random 
Long counter (Current value) LC Batch/random 
Data register D Batch/random 
Special register SD Batch/random 
Index register Z Batch/random 
Long index register LZ Batch/random 
File register R Batch/random 
ZR Batch/random 
Refresh data register RD Batch/random 
Link relay B Batch/random 
Link register W Batch/random 
Link special relay SB Batch/random 
Retentive timer (Contact) ST Batch/random 
Long retentive timer (Contact) LST Batch/random 
Retentive timer (Coil) ST Batch/random 
Long retentive timer (Coil) LST Batch/random 
Link special register SW Batch/random 
Edge relay V Batch/random 
Own station random access buffer Batch/random 
Retentive timer (Current value) ST Batch/random 
Long retentive timer (Current value) LST Batch/random 
Remote register for sending RWw Batch/random 
Remote register for receiving RWr Batch/random 
Own station buffer memory Batch/random 
Link direct device (Link input) Jn\X Batch/random 
Link direct device (Link output) Jn\Y Batch/random 
Link direct device (Link relay) Jn\B Batch/random 
Link direct device (Link register) Jn\W Batch/random 

1 COMMON ITEMS
1.3 MELSEC Data Link Functions 15
1
Link direct device (Link special relay) Jn\SB Batch/random 
Link direct device (Link special register) Jn\SW Batch/random 
Intelligent function module device, module access device Un\G Batch/random 
Other station buffer memory Batch/random 
Other station random access buffer Batch/random 
Remote input RX Batch/random 
Remote output RY Batch/random 
Remote register RW Batch/random 
Link special relay SB Batch/random 
Link special register SW Batch/random 
CPU buffer memory U3En\G Batch 
Random 
Fixed cycle communication area U3En\HG Batch 
Random 
Global label GV Batch 
Random 
Safety input SA\X Batch/random 
Safety output SA\Y Batch/random 
Safety internal relay SA\M Batch/random 
Safety link relay SA\B Batch/random 
Safety timer SA\T Batch/random 
Safety retentive timer SA\ST Batch/random 
Safety counter SA\C Batch/random 
Safety data register SA\D Batch/random 
Safety link register SA\W Batch/random 
Safety special relay SA\SM Batch/random 
Safety special register SA\SD Batch/random 
Device Access method Access target CPU
(1) (2)

16 1 COMMON ITEMS
1.3 MELSEC Data Link Functions
CC-Link IE Controller Network communication
The following explains the range and devices accessible for communication via a CC-Link IE Controller Network module.
■Accessible range
The system configuration in the accessible range and the accessibility of each access target CPU via a CC-Link IE Controller
Network module are shown below.
Connected network
C Controller module
Module to be routed
Connected station
CPU
Connected module
Network to be routed
Access target CPU Target module via the
network
System configuration

1 COMMON ITEMS
1.3 MELSEC Data Link Functions 17
1
■Applicable access
Accessibility is shown in the following table. The own station and the connected station CPU are accessible.
: Accessible, : Not accessible
*1 The following CPUs are accessible:
Q12DCCPU-V (Extended mode)
Q24DHCCPU-V, Q24DHCCPU-LS, Q24DHCCPU-VG, and Q26DHCCPU-LS
*2 The station number 65 or later is accessible only when all control CPUs on the network to be routed are universal model QCPUs.
*3 It is not accessible when the connected station CPU is Q00J/Q00/Q01CPU.
1.
Connected
network
2.
Connected
station
CPU
3. Network to be
routed
4. Access target CPU
Programmable controller C Controller module WinCPU
module
Interface
board for
personal
computer
MELSEC
iQ-R
series
MELSEC
-Q series
MELSEC
-L series
MELSEC
iQ-R
series
MELSEC
-Q series
MELSEC
-Q series
CC-Link IE
Controller
Network
MELSEC iQ-
R series
programmabl
e controller
CC-Link IE Controller
Network

CC-Link IE Field Network 
*1 
MELSECNET/H network 
MELSECNET/10 network 
Ethernet 
Serial communication 
CC-Link 
MELSEC iQ-
R series C
Controller
module
CC-Link IE Controller
Network

CC-Link IE Field Network 
MELSECNET/H network 
MELSECNET/10 network 
Ethernet 
Serial communication 
CC-Link 
MELSEC-Q
series
programmabl
e controller
(Q mode)
CC-Link IE Controller
Network*2

*3 
CC-Link IE Field
Network*2

*3  *1 
MELSECNET/H network 
*3 
MELSECNET/10 network 
*3 
MELSECNET()
Ethernet 
Serial communication 
CC-Link 
MELSEC-Q
series C
Controller
module
CC-Link IE Controller
Network

CC-Link IE Field Network 
MELSECNET/H network 
MELSECNET/10 network 
MELSECNET()
Ethernet 
Serial communication 
CC-Link 

18 1 COMMON ITEMS
1.3 MELSEC Data Link Functions
■Accessible devices
The devices accessible for communication via a CC-Link IE Controller Network module are shown below.
• 'Batch' and 'Random' in the following table indicate as follows:
Batch: Batch write (mdSendEx function), batch read (mdReceiveEx function)
Random: Random write (mdRandWEx function), random read (mdRandREx function), bit set (mdDevSetEx
function), bit reset (mdDevRstEx function), random write by using a label name (mdRandWLabelEx
function), random read by using a label name (mdRandRLabelEx function)
• Bit devices can be accessed by using 'bit set' (mdDevSetEx function) and 'bit reset' (mdDevRstEx function).
• Device extension specifications (digit specification, bit specification and index specification) cannot be used.
• Accessing the own station
The accessible devices when accessing the CC-Link IE Controller Network module controlled by C Controller module are
shown in the following table.
: Accessible, : Not accessible
For details on replacement from the device types specified with an existing product, refer to the following section.
Page 190 Replacement of device type
<For other than the RECV function>
To access a CC-Link IE Controller Network module controlled by a C Controller module, use the method explained in the
following section. Accessing the own station by using a CC-Link IE Controller Network communication will result in the station
number/network number error.
Page 190 Replacement of device type
Device Access method Access target CPU
R12CCPU-V
RECV function Batch 
Random 