MITSUBISHI ELECTRIC

Programmable Controller

User's Manual

QJ71DN91
DeviceNet Master-Slave Module
GX Configurator-DN

Art. no. 139835

01012008 MITSUBISHI ELECTRIC INDUSTRIAL AUTOMATION
SH(NA)-080143
Version J
 • SAFETY PRECAUTIONS •
(Always read these instructions before use)

Before using this product, please read this manual and the relevant manuals introduced in this manual
carefully and pay full attention to safety to handle the product correctly.
The instructions given in this manual are concerned with this product only. For the safety instructions of
the programmable controller system, please read the User's Manual of the CPU module used.
In this manual, the safety instructions are ranked as "DANGER" and "CAUTION".

Indicates that incorrect handling may cause hazardous conditions,

DANGER
resulting in death or severe injury.

Indicates that incorrect handling may cause hazardous conditions,

CAUTION
resulting in minor or moderate injuries and/or property damage.

Note that failure to observe a ! CAUTION level instruction may lead to a serious consequence
depending on the circumstances.
Always follow the instructions of both levels to ensure the safety.

Please keep this manual in a safe place for future reference and also pass it on to the end user.

[DESIGN PRECAUTIONS]
! DANGER
• If a communications error occurs on a DeviceNet network, faulty nodes will behave as follows:
(1) The master node (QJ71DN91) holds input data which had been received from slave nodes
before the error occurred.
(2) Whether output signals of a slave node are turned off or held is determined by the slave
node's specifications or the parameters set at the master node. When the QJ71DN91 is
used as a slave node, it holds data that have been input from the master node before the
communication error.
Utilizing communications states of slave nodes, create an interlock circuit on sequential
programs and provide safety mechanism externally so that the system will operate safely.

! CAUTION
• Do not install control wires or communication cables together with the main circuit or power
wires, or bring them close to each other.
Keep a distance of 300 mm (11.8 inch) or more between them.
Failure to do so may cause malfunctions due to noise.

A-1 A-1
[INSTALLATION PRECAUTIONS]
! CAUTION
• Use the programmable controller in an environment that meets the general specifications
contained in the User's Manual of the CPU module used.
Using it in an environment that does not meet them may result in an electric shock, fire,
malfunction, and damage to or deterioration of the product.
• While pressing the installation lever on the lower part of the module, insert the module fixing
projection into the hole in the base unit. Then, securely mount the module.
Incorrect module mounting may cause the module to malfunction, fail or fall off.
Secure the module with screws especially when it is used in an environment where constant
vibrations may occur.
• Tighten the screws within the specified torque range.
If the screws are loose, it may cause falling, short circuits, or malfunction.
If the screws are tightened too much, it may cause damage to the screw and /or the module,
resulting in falling, short circuits or malfunction.
• Before mounting/dismounting the module, be sure to shut off all phases of the external power
supply used by the system. Failure to do so may cause product damage.
• Do not directly touch the conductive area or electric components of the module.
Doing so may cause malfunction or failure in the module.

[WIRING PRECAUTIONS]
! DANGER
• Before installation or wiring, shut off all phases of the external power supply used in the system.
Failure to do so may cause an electric shock, damage to the product or malfunction.

! CAUTION
• Be careful to prevent foreign matter such as dust or wire chips from entering the module.
It may cause a fire, failure or malfunction.
• The top surface of the module is covered with a protective film to prevent foreign matter such as
wiring chips from entering the module during wiring.
Do not remove this film until wiring is complete.
Before starting the system, remove the film to release heat.
• Place the communication cables and power cables connected to the module in a duct or clamp
them.
Otherwise, dangling cables may swing or inadvertently be pulled, resulting in damage to the
module or cables or malfunctions due to poor cable contact.
• Do not pull the cable part when disconnecting the cable from the module. To disconnect a cable
with connector, hold the connector that is plugged into the module. To disconnect a cable
without connector, loosen the screws used for fastening.
Pulling the cable that is still connected to the module may damage the module and/or cable, or
cause a malfunction due to poor contact.
A-2 A-2
[STARTUP/MAINTENANCE PRECAUTIONS]
! DANGER
• Do not touch any terminal unless all phases of the external power supply have been shut off.
Doing so may cause a malfunction.
• Always turn off all phases of the external power supply before cleaning or retightening the
terminal screws.
Failure to do so may result in a malfunction.
• Do not disassemble or remodel the module.
Doing so will cause failure, malfunctions, injuries, or a fire.
• Before mounting/dismounting the module, be sure to shut off all phases of external power supply
used by the system.
Failure to do so may cause module failure or malfunctions.
• Do not mount/dismount the module onto/from a base unit more than 50 times (IEC 61131-2
compliant), after the first use of the product.
Doing so may cause malfunctions.
• Before handling the module, touch a grounded metal object to discharge the static electricity
from the human body.
Failure to do so may cause a failure or malfunctions of the module.

[DISPOSAL PRECAUTION]
! CAUTION
• When disposing of this product, treat it as industrial waste.

A-3 A-3
REVISIONS

*The manual number is given on the bottom left of the back cover.
Print Date *Manual Number Revision
Dec. 2000 SH (NA)-080143-A First Printing
Jun. 2001 SH (NA)-080143-B
Addition
Section 2.3, 2.4

Delete
Section 2.2.1, 2.2.2

Correction
SAFETY PRECAUTIONS, About the Generic Terms and Abbreviations,
Product Configuration, Section 2.2, 2.4, Section 6.2, 6.2.1, 6.2.2, 6.3.3,
6.5
Feb. 2002 SH (NA)-080143-C
Correction
About the Generic Terms and Abbreviations, Section 2.2, Section 6.2.1,
6.2.2
Dec. 2002 SH (NA)-080143-D
Addition
Section 2.5

Correction
Section 2.2, Section 3.3.2, 3.4.1, Section 6.1, 6.2.1, 6.3.2, 6.4, 6.5,
Section 9.2.1, 9.2.2
Feb. 2003 SH (NA)-080143-E
Correction
SAFETY PRECAUTIONS, INTRODUCTION, CONTENTS, Section 6.2.2,
Section 6.3.3, Section 6.4, Section 6.5
May. 2003 SH (NA)-080143-F
Correction
Section 6.3.1
Jun. 2004 SH (NA)-080143-G
Correction
Section 2.2, 2.3, Section 3.3.2, Section 4.2.1, Section 6.3.2, 6.5, 6.6,
Section 7.3.2, Section 8.1, 8.3, Section 9.3
Feb. 2006 SH (NA)-080143-H
Correction
SAFETY PRECAUTIONS, Compliance with the EMC and Low Voltage
Directives, Section 1.1, Section 2.1, 2.3, Section 3.2.1, 3.4, 3.5, Section
4.1, 4.2.1, Chapter 5, Chapter 6 (screen change), Section 6.2.2, Section
7.1, 7.2, 7.3.1, 7.4, 7.5.2, 7.7, Section 8.3, Section 9.3, Appendix 3
Mar. 2006 SH (NA)-080143-I
Addition
Section 2.5, 3.4.1

Correction
Section 3.4.1

A-4 A-4
Print Date *Manual Number Revision
Jan. 2008 SH(NA)-080143-J
Correction
Generic Terms and Abbreviations, Section 1.1, 2.1 to 2.3, 3.4, Chapter 4,
Section 5.1 to 5.4, 5.6, 6.1, 6.2, 6.4, 6.5, Chapter 7 and 8, Section 9.1,
9.2, Appendix 6

Addition
Definitions of Terminology, Section 2.4, 3.2, 6.5.1 to 6.5.17, 7.3.1, 7.4.1,
8.2.1, 8.3.1, 9.1.5, 9.2.3, Appendix 2

Deletion
Section 2.4 to 2.6, Chapter 5

Section Numbers Changed

Section 3.2 -> Chapter 4, Section 3.3.2 -> Sections 3.3.2 and 3.3.3,
Section 3.4.2 -> Section 3.4.2 to 3.4.14, Chapter 4 -> Chapter 5,
Appendix 2 to 6 -> Appendix 3 to 7

Japanese Manual Version SH-080125-J

This manual confers no industrial property rights or any rights of any other kind, nor does it confer any patent
licenses. Mitsubishi Electric Corporation cannot be held responsible for any problems involving industrial property
rights which may occur as a result of using the contents noted in this manual.
© 2000 MITSUBISHI ELECTRIC CORPORATION

A-5 A-5
 INTRODUCTION

Thank you for purchasing the MELSEC-Q series programmable controller.

Before using the product, please read this manual carefully to understand the functions and performance of
the Q series programmable controller to ensure correct use.

CONTENTS

SAFETY PRECAUTIONS..............................................................................................................................A- 1
REVISIONS ....................................................................................................................................................A- 4
INTRODUCTION............................................................................................................................................A- 6
CONTENTS....................................................................................................................................................A- 6
Compliance with the EMC and Low Voltage Directives................................................................................A-10
Generic Terms and Abbreviations .................................................................................................................A-10
Definitions of Terminology .............................................................................................................................A-11
Packing List ....................................................................................................................................................A-13

1 OVERVIEW 1- 1 to 1- 3

1.1 Features ................................................................................................................................................... 1- 1

2 SYSTEM CONFIGURATION 2- 1 to 2- 7

2.1 Overall Configuration ............................................................................................................................... 2- 1

2.2 Applicable Systems.................................................................................................................................. 2- 3
2.3 How to Check the Function Version, Serial No. and Software Version ................................................. 2- 5
2.4 Precautions on System Configuration..................................................................................................... 2- 7

3 SPECIFICATIONS 3- 1 to 3-48

3.1 Performance Specifications ..................................................................................................................... 3- 1

3.1.1 Maximum trunk line distance when using thick and thin cables ...................................................... 3- 2
3.2 Function Lists ........................................................................................................................................... 3- 3
3.3 I/O Signals for Programmable Controller CPU ....................................................................................... 3- 4
3.3.1 I/O signal list ...................................................................................................................................... 3- 4
3.3.2 I/O signals for the master function .................................................................................................... 3- 5
3.3.3 I/O signals for the slave function....................................................................................................... 3-13
3.4 Buffer Memory.......................................................................................................................................... 3-17
3.4.1 Buffer memory list ............................................................................................................................. 3-17
3.4.2 Message communication area for master function .......................................................................... 3-20
3.4.3 Own node status area for master function ....................................................................................... 3-25
3.4.4 Node status area for master function ............................................................................................... 3-29
3.4.5 Master function parameter setting area............................................................................................ 3-32
3.4.6 Communication data area for master function ................................................................................. 3-37
3.4.7 Link scan time area for master function ........................................................................................... 3-39
3.4.8 Own node status area for slave function .......................................................................................... 3-40
3.4.9 Parameter setting area for slave function......................................................................................... 3-41
3.4.10 Communication data area for slave function.................................................................................. 3-42
3.4.11 Own node information area ............................................................................................................ 3-43

A-6 A-6
 3.4.12 Hardware test area.......................................................................................................................... 3-44
3.4.13 Parameter saving area selection area............................................................................................ 3-46
3.4.14 Auto communication start setting area ........................................................................................... 3-46
3.5 Communication Performance .................................................................................................................. 3-47
3.5.1 Transmission delay ........................................................................................................................... 3-47
3.5.2 Communication cycle time................................................................................................................ 3-47
3.5.3 Link scan time.................................................................................................................................... 3-48

4 FUNCTIONS 4- 1 to 4-13

4.1 Master Function (I/O Communication Function) ..................................................................................... 4- 1

4.2 Master Function (Message Communication Function)........................................................................... 4- 8
4.3 Slave Function (I/O Communication Function) ....................................................................................... 4-11

5 SETUP AND PREPARATION 5- 1 to 5-14

5.1 Pre-operation Procedures........................................................................................................................ 5- 1

5.1.1 When using the master function ....................................................................................................... 5- 1
5.1.2 When using the slave function.......................................................................................................... 5- 2
5.1.3 When using both the master and slave functions ............................................................................ 5- 3
5.2 Implementation and Installation............................................................................................................... 5- 4
5.2.1 Handling precautions ........................................................................................................................ 5- 4
5.2.2 Installation environment .................................................................................................................... 5- 4
5.3 Part Names and Settings......................................................................................................................... 5- 5
5.3.1 LED indications ................................................................................................................................. 5- 6
5.3.2 Node No. switches ............................................................................................................................ 5- 7
5.3.3 Mode switch....................................................................................................................................... 5- 7
5.4 Hardware Test.......................................................................................................................................... 5- 8
5.5 Wiring........................................................................................................................................................ 5- 9
5.6 Communication Test ................................................................................................................................ 5-10
5.7 Precautions for Network Power Supply................................................................................................... 5-11
5.7.1 Network power supply unit position .................................................................................................. 5-11
5.7.2 Network power supply unit position and current capacity calculation ............................................. 5-12

6 UTILITY PACKAGE (GX Configurator-DN) 6- 1 to 6-33

6.1 Functions of the Utility Package .............................................................................................................. 6- 1

6.2 Installing and Uninstalling the Utility Package ........................................................................................ 6- 2
6.2.1 Handling precautions ........................................................................................................................ 6- 2
6.2.2 Operating environment...................................................................................................................... 6- 4
6.3 Utility Package Operation ........................................................................................................................ 6- 6
6.3.1 Common utility package operations ................................................................................................. 6- 6
6.3.2 Operation overview ........................................................................................................................... 6- 9
6.3.3 Starting the Intelligent function module utility................................................................................... 6-11
6.4 Auto Refresh ............................................................................................................................................ 6-13
6.5 Monitoring/Test......................................................................................................................................... 6-16
6.5.1 X/Y monitor/test................................................................................................................................. 6-19
6.5.2 Parameter area monitor/test ............................................................................................................. 6-20
6.5.3 Save parameters to flash ROM ........................................................................................................ 6-21

A-7 A-7
 6.5.4 Node configuration status monitor.................................................................................................... 6-22
6.5.5 Node communication status monitor ................................................................................................ 6-22
6.5.6 Node communication error status monitor ....................................................................................... 6-23
6.5.7 Node fault status monitor .................................................................................................................. 6-23
6.5.8 Failed node detection setting............................................................................................................ 6-24
6.5.9 Message communication area monitor/test ..................................................................................... 6-25
6.5.10 I/O address area monitor for master function ................................................................................ 6-26
6.5.11 Master function receive data monitor ............................................................................................. 6-27
6.5.12 Master function transmit data monitor/test ..................................................................................... 6-27
6.5.13 Slave function receive data monitor ............................................................................................... 6-28
6.5.14 Slave function transmit data monitor/test ....................................................................................... 6-28
6.5.15 Auto configuration ........................................................................................................................... 6-29
6.5.16 Flash ROM parameter clear ........................................................................................................... 6-30
6.5.17 Parameter backup........................................................................................................................... 6-31
6.6 Flash ROM Setting................................................................................................................................... 6-32

7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION 7- 1 to 7-36

7.1 Programming Precautions ....................................................................................................................... 7- 1

7.2 System Configuration............................................................................................................................... 7- 4
7.3 Parameters for Master Function .............................................................................................................. 7- 7
7.3.1 Program example using the utility package ..................................................................................... 7-10
7.3.2 Program example not using the utility package ............................................................................... 7-23
7.4 I/O Communication Function ................................................................................................................... 7-27
7.4.1 Program example using the utility package ..................................................................................... 7-27
7.4.2 Program example not using the utility package ............................................................................... 7-29
7.5 Message Communication Function......................................................................................................... 7-31
7.5.1 Example of reading message communication data ......................................................................... 7-31
7.5.2 Example of writing message communication data........................................................................... 7-33
7.6 Obtaining Error Information ..................................................................................................................... 7-34
7.7 Allocating Transmit/Receive Data Storage Devices for Future Expansion............................................ 7-35

8 PROGRAMMING FOR EXECUTING THE SLAVE FUNCTION 8- 1 to 8-12

8.1 System Configuration............................................................................................................................... 8- 1

8.2 Parameters for Slave Function ................................................................................................................ 8- 1
8.2.1 Program example using the utility package ..................................................................................... 8- 3
8.2.2 Program example not using the utility package ............................................................................... 8- 7
8.3 I/O Communication Function ................................................................................................................... 8- 9
8.3.1 Program example using the utility package ..................................................................................... 8- 9
8.3.2 Program example not using the utility package ............................................................................... 8-11
8.4 Obtaining Error Information ..................................................................................................................... 8-12

A-8 A-8
9 TROUBLESHOOTING 9- 1 to 9-18

9.1 Problem Identification .............................................................................................................................. 9- 2

9.1.1 Checking the LEDs ........................................................................................................................... 9- 2
9.1.2 When unable to communicate with all slave nodes (when using master function) ........................ 9- 3
9.1.3 When unable to communicate with a specific slave node (when using master function)............... 9- 4
9.1.4 When unable to communicate with master node (when using slave function) ............................... 9- 5
9.1.5 Troubleshooting for other cases ....................................................................................................... 9- 6
9.2 Error Codes .............................................................................................................................................. 9- 8
9.2.1 Communication error codes............................................................................................................. 9- 8
9.2.2 Execution error codes of message communication (for the master function only)......................... 9-13
9.2.3 General DeviceNet error codes of message communication (for the master function only).......... 9-16
9.3 Checking the QJ71DN91 Status by System Monitor in GX Developer ................................................. 9-17

APPENDIXES App- 1 to App- 7

Appendix 1 External Dimensions...............................................................................................................App- 1

Appendix 2 Functional upgrade of the QJ71DN91 ...................................................................................App- 2
Appendix 3 Differences from the AJ71DN91/A1SJ71DN91.....................................................................App- 2
Appendix 4 Parameter Setting Sheet (For the Master Function) .............................................................App- 3
Appendix 5 Parameter Setting Sheet (For the Slave Function) ...............................................................App- 4
Appendix 6 List of Communication Parameters of Slave Nodes from Various Manufactures ................App- 5
Appendix 7 EDS File of the QJ71DN91 ....................................................................................................App- 6

INDEX Index- 1 to Index- 2

A-9 A-9
Compliance with the EMC and Low Voltage Directives

When incorporating the Mitsubishi programmable controller into other machinery

or equipment and keeping compliance with the EMC and low voltage directives,
refer to Chapter 3, "EMC Directives and Low Voltage Directives" of the User's
Manual (Hardware) included with the CPU module or base unit used.
The CE logo is printed on the rating plate of the programmable controller,
indicating compliance with the EMC and low voltage directives.
No additional measures are necessary for this product to ensure compliance with
these directives.

Generic Terms and Abbreviations

Unless otherwise specified, this manual uses the following generic terms and
abbreviations to explain the QJ71DN91 DeviceNet master/slave module.

Generic term/abbreviation Description

® R
IBM-PC/AT-compatible Personal computer compatible with the IBM-PC/AT system (including PC98-NX )
personal computer

Generic product name for the SWnD5C-GPPW-E, SWnD5C-GPPW-EA, SWnD5C-GPPW-EV

GX Developer and SWnD5C-GPPW-EVA. ("n" is 4 or greater.)
"-A" and "-V" denote volume license product and upgraded product respectively.
R R
PC-9800
R
Abbreviation for PC-9800 series (except PC98-NX )

Generic term for the Q00JCPU, Q00CPU, Q01CPU, Q02CPU, Q02HCPU, Q06HCPU,
QCPU (Q mode) Q12HCPU, Q25HCPU, Q12PHCPU, Q25PHCPU, Q12PRHCPU, Q25PRHCPU, Q02UCPU,
Q03UDCPU, Q04UDHCPU, and Q06UDHCPU

Abbreviation for DeviceNet master/slave module setting/monitoring tool, GX Configurator-DN

GX Configurator-DN
(SW1D5C-QDNU-E)

QJ71DN91 Abbreviation for the QJ71DN91 DeviceNet master/slave module

R
Personal computer Generic term for IBM-PC/AT-compatible or PC-9800 personal computer

Generic term for the following:

R R
Microsoft Windows Vista Home Basic Operating System,
R R
R
Microsoft Windows Vista Home Premium Operating System,
Windows Vista R R
Microsoft Windows Vista Business Operating System,
R R
Microsoft Windows Vista Ultimate Operating System,
R R
Microsoft Windows Vista Enterprise Operating System

Generic term for the following:

R R R
Windows XP Microsoft Windows XP Professional Operating System,
R R
Microsoft Windows XP Home Edition Operating System

A - 10 A - 10
Definitions of Terminology

Terms used in this manual and their definitions are listed below.

Term Definition

Function that allows I/O (input/output) data communications between master and slave
I/O communication function
nodes.

Function that allows reading or writing of slave node’s attribute data in response to a
Message communication
request message. For further details, refer to the DeviceNet common service in the
function
DeviceNet Specifications (Release2.0).

Device that exchanges I/O data with slave nodes which are configured with the master
Master node
function parameters.

Slave node Device that exchanges I/O data with a master node.

Master/slave node Device that operates as a master and slave node.

Parameters for setting information such as connection type or I/O points, which are used to
Master function exchange I/O data with respective slave nodes when the QJ71DN91 is used as a master
parameters node.
Configured in sequence programs or GX Configurator-DN.

Function that detects slave nodes on the network and automatically creates master function
parameters.
Two options are available: "All configuration" used for detecting all slave nodes on the
Auto configuration
network and "Add configuration" used for detecting the slave nodes added to the network.
This function can reduce programming steps for master function parameter setting.
Executed in sequence programs or GX Configurator-DN.

Parameters provided for changing the number of I/O points for a slave node when the
Slave function parameters QJ71DN91 is used as a slave node.
Configured in sequence programs or GX Configurator-DN.

Auto communication start Setting by which I/O communications automatically start at power-up.
setting Configured in sequence programs or GX Configurator-DN.

Memory inside the QJ71DN91, in which data are temporarily stored.

Used for storing parameter settings and I/O data.
Buffer memory Parameters are stored on a flash ROM after debugging.
I/O data are transferred to devices of a programmable controller CPU by automatic refresh
or sequence program.

Memory inside the QJ71DN91, which stores parameters saved in the following buffer
memory areas:
• Master Function Parameters (Address: 01D4H to 03CFH)
Flash ROM • Slave Function Parameters (Address: 060EH, 060FH)
• Auto Communication Start Setting (Address: 0631H)
Parameters saved on the flash ROM are automatically loaded to the buffer memory when
power is turned ON from OFF or when the CPU module is reset.

Automatic data transfer between the buffer memory and devices of a programmable
Automatic refresh controller CPU.
Configured in Auto refresh setting in GX Configurator-DN.

A - 11 A - 11
 Term Definition

Used to specify a method for communicating I/O data between a master and slave nodes.
When the QJ71DN91 is used as a master node, one of the following connection types can
be selected for each slave node.
• Polling
Connection type • Bit strobe
• Change of state
• Cyclic
When the QJ71DN91 is used as a slave node, the polling method is applied to I/O
communications.

A - 12 A - 12
Packing List

The following are included in the package.

Model Product name Quantity

QJ71DN91 DeviceNet master/slave module 1
QJ71DN91 Terminating resistor 121 , 1/4W 2
Connector 1
SW1D5C-QDNU-E GX Configurator-DN Version 1 (single license product) (CD-ROM) 1
SW1D5C-QDNU-EA GX Configurator-DN Version 1 (volume license product) (CD-ROM) 1

A - 13 A - 13
 1 OVERVIEW
MELSEC-Q

1 OVERVIEW
1 This manual provides descriptions such as the specifications and parts names of the
QJ71DN91 DeviceNet master/slave module, which is used in combination with a
MELSEC-Q series programmable controller CPU.
For the DeviceNet specifications, refer to the DeviceNet Specifications (Release 2.0)
Volumes 1 and 2.
DeviceNet is a registered trademark of Open DeviceNet Vendor Association, Inc.

POINT
The QJ71DN91 is assumed to be compatible with most of DeviceNet products on
the market. However, the compatibility with products manufactured by other
vendors is not guaranteed.

1.1 Features

This section explains the features of the QJ71DN91.

(1) Operating as a DeviceNet master node
The QJ71DN91 is compliant with the DeviceNet Specifications (Release2.0) and
can operate as a master node.
(a) I/O communication function (Refer to Section 4.1.)
1) The QJ71DN91 can exchange I/O data with slave nodes (max. 63
nodes) using its own buffer memory.
Communications of 512 bytes of inputs (up to 256 bytes per node) and
512 bytes of outputs (up to 256 bytes per node) are available.
Master node Slave node
Programmable controller CPU QJ71DN91

SET Y11 I/O Communication

Request

*1 0700H
X Master Transmit
Function
Receive
Data area
07FFH
*1
0900H Master
Y Receive
Function
Transmit
Data area
09FFH

*1: Performed by automatic refresh or sequence program.

2) One of the following connection types can be selected for each slave
node.
• Polling
• Bit strobe
• Change of state
• Cyclic
1-1 1-1
1 OVERVIEW
MELSEC-Q

(b) Message communication function (Refer to Section 4.2.)

Using the buffer memory of the QJ71DN91, attribute data can be read from
or written to slave nodes. 1
For details of other message communications, refer to the DeviceNet
common service in the DeviceNet Specifications (Release2.0).
At one time, 240 bytes of message data can be transferred.

(c) Creating master function parameters using auto configuration

The QJ71DN91 can detect slave nodes on the network and automatically
create master function parameters.
Since programming steps for setting master function parameters are not
required, steps for the overall sequence program can be reduced.

(2) Operating as a DeviceNet slave node

The QJ71DN91 is compliant with the DeviceNet Specifications (Release2.0) and
can operate as a DeviceNet slave node.
(a) I/O communication function (Refer to Section 4.3.)
1) The QJ71DN91 can exchange I/O data with a master node using its
own buffer memory.
It can exchange 128 bytes of inputs and 128 bytes of outputs.
2) The connection type is polling.
Master node Slave node
QJ71DN91 Programmable controller CPU

I/O Communication SET Y11

Request

0B00H *1
Transmit Slave X
Function
Receive
0B3FH Data area

0C00H *1
Receive Slave Y
Function
Transmit
Data area
0C3FH

*1: Performed by automatic refresh or sequence program.

1-2 1-2
1 OVERVIEW
MELSEC-Q

(3) Operating as a DeviceNet master/slave node

The QJ71DN91can operate as a master and slave node concurrently.

QJ71DN91 master QJ71DN91 master/slave

(node No.1) (node No.4)

I/O communication
Master function Slave function Master function

DeviceNet slave 24V power DeviceNet slave

supply
(node No.2) (node No.5)
I/O I/O
communication communication

DeviceNet slave DeviceNet slave

(node No.3) (node No.6)
I/O I/O
communication communication

No communication between
DeviceNet slaves

(4) Easy setting by utility package

A utility package (GX Configurator-DN) is separately available.
Although the utility package is not essential, it allows on-screen parameter setting
and automatic refresh setting, reduces programming steps, and make the setting
and operation status check easy.

1-3 1-3
2 SYSTEM CONFIGURATION
MELSEC-Q

2 SYSTEM CONFIGURATION

This chapter explains the system configuration of DeviceNet.

2.1 Overall Configuration

The number of modules connectable to a DeviceNet network is 64, including master, 2

slave and master/slave nodes.
The QJ71DN91 can be used as a master node, a slave node or a master/slave node.
The following shows an example of a system configuration:

QJ71DN91
Master node
Drop line

Network power supply

Terminating resistor unit (24V DC) Trunk line (main line)
(121Ω, 1/4W)

QJ71DN91
Slave node
Slave node Terminating resistor
(121Ω, 1/4W)

Tap Power supply tap

Slave node Slave node

Drop line (branch line)

Slave node

(1) DeviceNet cables, taps and terminating resistors

DeviceNet cables are used as a trunk line and drop lines.
Each node is connected to the trunk line directly, or connected to a drop line via a
tap from the trunk line. Nodes need not be wired in order of node numbers.
Connect terminating resistors at both ends of the trunk line.

(2) Network power supply unit and power supply tap

In addition to power supply for each node, connect a network power supply unit
to distribute power to the communication circuit.
Connect a power supply tap to the trunk line, and install a network power supply
unit.

POINT
To minimize the affect of noise, keep DeviceNet cables, power cables, and signal
lines of I/O modules away from each other.

2-1 2-1
 2 SYSTEM CONFIGURATION
MELSEC-Q

Remarks
Please inquire to ODVA about the following devices that are required to construct a
DeviceNet network.
• Network power supply unit
• Power supply tap
2 • Tap
• Terminating resistor
• DeviceNet cable

Contact:
Open DeviceNet Vendor Association, Inc.
http://www.odva.org/

2-2 2-2
2 SYSTEM CONFIGURATION
MELSEC-Q

2.2 Applicable Systems

This section describes the systems to which the QJ71DN91 can be applied.

(1) Applicable modules and base units, and No. of modules

(a) When mounted with a CPU module
The table below shows the CPU modules and base units applicable to the
QJ71DN91 and quantities for each CPU model.
Depending on the combination with other modules or the number of
mounted modules, power supply capacity may be insufficient.
Pay attention to the power supply capacity before mounting modules, and if
the power supply capacity is insufficient, change the combination of the
modules.
2
Applicable CPU module *1 Base unit*
No. of modules
CPU type CPU model Main base unit Extension base unit
Q00JCPU Up to 8
Basic model
3 Q00CPU
QCPU* Up to 24
Q01CPU
Q02CPU
High Q02HCPU
Performance Q06HCPU Up to 64
model QCPU Q12HCPU
Programmable Q25HCPU
controller CPU Q12PHCPU
Process CPU Up to 64
Q25PHCPU
Q12PRHCPU
Redundant CPU N/A
Q25PRHCPU
Q02UCPU Up to 36
Universal model Q03UDCPU
3
QCPU* Q04UDHCPU Up to 64
Q06UDHCPU
: Applicable, : N/A
*1: Limited within the range of I/O points for the CPU module
*2: Can be installed to any I/O slot of a base unit.
*3: Use the QJ71DN91 whose serial No. (first five digits) is 03052 or later.

(b) Mounting to a MELSECNET/H remote I/O station

The QJ71DN91 cannot be mounted to any MELSECNET/H remote I/O
station.
Mount it to a CPU module on a master station.

2-3 2-3
2 SYSTEM CONFIGURATION
MELSEC-Q

(2) Support of the multiple CPU system

When using the QJ71DN91 in a multiple CPU system, refer to the QCPU User’s
Manual (Multiple CPU System) first.
(a) Compatible QJ71DN91
The function version of the first released QJ71DN91 is B, and it supports
multiple CPU systems.
(b) Intelligent function module parameters
Write intelligent function module parameters to only the control CPU of the
QJ71DN91.

(3) Supported software packages

Relation between the system containing the QJ71DN91 and software package is
shown in the following table.
GX Developer is necessary when using the QJ71DN91.

Software version
*1
GX Developer GX Configurator-DN
Single CPU system Version 7 or later
Q00J/Q00/Q01CPU Version 1.10L or later
Multiple CPU system Version 8 or later

Q02/Q02H/Q06H/ Single CPU system Version 4 or later Version 1.00A or later

Q12H/Q25HCPU
Multiple CPU system Version 6 or later Version 1.10B or later

Single CPU system

Q12PH/Q25PHCPU Version 7.10L or later Version 1.13P or later
Multiple CPU system

Q02U/Q03UD/Q04U Single CPU system

Version 8.48A or later Version 1.23Z or later
DH/Q06UDHCPU Multiple CPU system
*1: Version 1.14Q or earlier does not support Node Communication Error Status (address : 01C0H
to 01C3H/448 to 451). Please use Version 1.15R or later.

(4) Remote operation is not allowed from another DeviceNet node

Each DeviceNet node on DeviceNet cannot read/write/monitor the sequence
program or data of the programmable controller CPU where the QJ71DN91 is
installed.

2-4 2-4
2 SYSTEM CONFIGURATION
MELSEC-Q

2.3 How to Check the Function Version, Serial No. and Software Version

This section describes how to check the function version and serial No. of the
QJ71DN91 and GX Configurator-DN software version.

(1) Checking the function version and serial No. of the QJ71DN91
(a) Checking at "the SERIAL field of the rating plate" located on the side of the
module
The serial No. and function version of the module is shown in the SERIAL
field of the rating plate.

Serial No. (Upper 5 digits)

Function version

Relevant regulation standards

(b) Checking by GX Developer

The serial No. and function version of the module are displayed on the
"Production Info. List" and "Module’s Detailed Information" screens of GX
Developer.
The following explains how to check them on the "Production Info. List"
screen. (For the case of "Module’s Detailed Information", refer to Section
9.3.)

[Operating procedure]
[Diagnostics] [System monitor] [Product Inf. List]

[Serial No, Ver, and Production No.]

• Serial No. of the module is displayed in the Serial No. column.
• Function version of the module is displayed in the Ver. column.
• Serial No. printed on the rating plate is displayed in the Production
1
No. column.*
Note that, because the QJ71DN91 does not support the production
No. display, "-" is displayed.

*1: The Production No. column display is active only when the CPU used is a Universal
model QCPU.

2-5 2-5
2 SYSTEM CONFIGURATION
MELSEC-Q

POINT
The serial No. on the rating plate may be different from the serial No. displayed on
the product information screen of GX Developer.
• The serial No. on the rating plate indicates the management information of the
product.
• The serial No. displayed on the product information screen of GX Developer
indicates the function information of the product.
The function information of the product is updated when a new function is
added.

(2) Checking the software version of GX Configurator-DN

The software version of GX Configurator-DN can be checked GX Developer’s
"Product information" screen.

[Operating procedure]
GX Developer "Help" Product information

Software version

(In the case of GX Developer Version 8)

2-6 2-6
2 SYSTEM CONFIGURATION
MELSEC-Q

2.4 Precautions on System Configuration

(1) DeviceNet products manufactured by other vendors

The QJ71DN91 is assumed to be compatible with most of the DeviceNet
products on the market. However, the compatibility with products manufactured
by other vendors is not guaranteed.

2-7 2-7
 3 SPECIFICATIONS
MELSEC-Q

3 SPECIFICATIONS

This chapter provides the performance specifications of the QJ71DN91, I/O signals
used with a programmable controller CPU, and buffer memory specifications.
For the general specifications for the QJ71DN91, refer to the User’s Manual
(Hardware) of the CPU module used.

3.1 Performance Specifications

Table 3.1 shows the performance specifications of the QJ71DN91.

3
Table 3.1 Performance specifications

Item Specification
Node type DeviceNet master (Group 2 only client)
Node No. 0 to 63

Number of Message connection 63

Master connections I/O connection 63 (polling, bit strobe, change of state, cyclic)
function
I/O Send Max. 4096 points (512 bytes), max. 256 bytes per node
Communication communication Receive Max. 4096 points (512 bytes), max. 256 bytes per node
data size Message Send Max. 240 bytes
communication Receive Max. 240 bytes
Communication specifications

Node type DeviceNet slaves (Group 2 server)

Node No. 0 to 63
Number of
Slave I/O connection 1 (polling)
connections
function
Send Max. 1024 points (128 bytes)
Communication I/O
data size communication
Receive Max. 1024 points (128 bytes)

Communication speed Selectable from 125 kbps, 250 kbps and 500kbps.
Maximum trunk line distance Drop line length
Communication Combination
Thick Thin
speed of thick and Maximum Total
cables cables
Maximum cable length * thin cables
125 kbaud 500 m 156 m
250 kbaud 250 m 100 m See 3.1.1 6m 78 m
500 kbaud 100 m 39 m
Current consumption required on the network 0.03 A
Number of writes to flash ROM Max. 100000 times
No. of occupied I/O points 32 points (I/O allocation: Intelligent 32 points)
5 V DC internal current consumption 0.17 A
Weight 0.11 kg
* : The maximum cable length complies with the DeviceNet Specifications (Release 2.0) Volumes 1 and 2.

3-1 3-1
3 SPECIFICATIONS
MELSEC-Q

3.1.1 Maximum trunk line distance when using thick and thin cables

The maximum transmission distance in the case of using thick and thin cables is
shown below.

Table 3.2 Maximum trunk line distance when using thick and thin cables

Maximum trunk line distance when using thick

Communication speed
and thin cables
125 kbaud Thick cable length + 5 Thin cable length < 500 m
250 kbaud Thick cable length +2.5 Thin cable length < 250 m
3
500 kbaud Thick cable length + Thin cable length < 100 m

3-2 3-2
3 SPECIFICATIONS
MELSEC-Q

3.2 Function Lists

The functions of the QJ71DN91 are listed below.

(1) List of master and slave functions

Table 3.3 List of master and slave functions
Reference
Function Description
section
The QJ71DN91 master node can exchange I/O data with
each slave node (up to 63 nodes), using its own buffer
I/O memory.
4.1
communication Transfer of 512 input bytes (up to 256 bytes per node) and
512 output bytes (up to 256 bytes per node) is available.
Master The connection type is selectable for each slave node.
function The QJ71DN91 master node can read attribute data from or
write them to slave nodes, using its own buffer memory.
Message For further details, refer to the DeviceNet common service in
4.2
communication the DeviceNet Specifications (Release2.0).
Up to 240 bytes of message data can be transferred at a
time.
The QJ71DN91 slave node can exchange I/O data with the
master node, using its own buffer memory.
Slave I/O
Transfer of 128 input bytes and 128 output bytes is 4.3
function communication
available.
The connection type is polling method.

(2) List of configuration functions

Table 3.4 List of configuration functions
Reference
Function Description
section
The following parameters in the buffer memory can be
stored in the flash ROM inside the QJ71DN91:
• Parameters for Master Function
(Address: 01D4H to 03CFH)
7.3 (3)
Saving data to flash ROM • Parameters for Slave Function (Address: 060EH, 060FH)
8.2 (2)
• Auto Communication Start Setting (Address: 0631H)
The parameters saved in the flash ROM are automatically
loaded to the buffer memory when power is turned ON from
OFF or when the CPU module is reset.
This function detects slave nodes on the network, allowing
automatic configuration of master function parameters.
Two options are available: "All configuration" used for
detecting all slave nodes on the network and "Add 3.4.5 (2)
Auto configuration
configuration" used for detecting the slave node(s) added to 7.3 (2)
the network.
Programming steps for setting the master function
parameters can be reduced.

3-3 3-3
3 SPECIFICATIONS
MELSEC-Q

3.3 I/O Signals for Programmable Controller CPU

This section explains the input/output signals that the QJ71DN91 sends to or receives
from a programmable controller CPU.

3.3.1 I/O signal list

The I/O signal assignments shown are based on the case where the start I/O No. of
the QJ71DN91 is "0000" (mounted to slot 0 of a main base unit).
Device X denotes an input signal from the QJ71DN91 to the programmable controller
CPU.
Device Y denotes an output signal from the programmable controller CPU to the
QJ71DN91.
Table 3.5 lists the I/O signals used for the programmable controller CPU.
Table 3.5 I/O signal list
QJ71DN91 Programmable controller CPU Programmable controller CPU QJ71DN91
Availability Availability
Input No. Signal name Master Slave Output No. Signal name Master Slave
function function function function
X00 Watchdog Timer Error Y00
X01 I/O Communicating Y01
X02 Message Communication Completion — Y02
X03 Error Set Signal for Master Function — Y03
X04 Slave Down Signal — Y04
X05 Message Communication Error Signal — Y05
X06 Saving Parameters to Flash ROM Y06
X07 Parameters Saved to Flash ROM Y07
X08 Error Set Signal for Slave Function — Y08 Use prohibited — —
X09 Use prohibited — — Y09
X0A H/W Test in Progress For hardware test Y0A
X0B H/W Test Completion For hardware test Y0B
X0C H/W Test Error Detection For hardware test Y0C
X0D Y0D
Use prohibited — —
X0E Y0E
X0F Module Ready Y0F
X10 Y10
X11 Y11 I/O Communication Request
Use prohibited — —
X12 Y12 Message Communication Request —
X13 Y13 Error Reset Request for Master Function —
X14 Auto-Configuring — Y14 Use prohibited — —
X15 Auto Configuration Completion — Y15 Auto Configuration Request —
X16 Y16 Use prohibited — —
Request for Saving Parameters to Flash
X17 Y17
ROM
X18 Y18 Error Reset Request for Slave Function —
X19 Y19
X1A Use prohibited — — Y1A
X1B Y1B
X1C Y1C Use prohibited — —
X1D Y1D
X1E Y1E
X1F Y1F

IMPORTANT
Do not set any "use-prohibited" signal to ON.
Doing so may cause malfunctions of the programmable controller system.
3-4 3-4
3 SPECIFICATIONS
MELSEC-Q

3.3.2 I/O signals for the master function

This section describes the ON/OFF timings and conditions of the I/O signals used for
the master function.

(1) Watchdog Timer Error (X00)

This is set to ON when a hardware failure occurs in the QJ71DN91.
OFF: Module normal
ON: Module error
When Watchdog Timer Error (X00) is set to ON, Module Ready (X0F) is set to
OFF.

Watchdog Timer Error (X00)

Module Ready(X0F)

(2) I/O Communicating (X01), I/O Communication Request (Y11)

These signals are used to start I/O communications with each slave node.
Execute the signal action while Module Ready (X0F) is ON.
(a) When starting I/O communication by I/O Communication Request (Y11)
• When I/O Communication Request (Y11) is set to ON, parameters are
checked.
• If the parameter check is completed successfully, I/O communication with
each slave node is started and I/O Communicating (X01) is set to ON.
• If the parameter check has failed, the ERR. LED lights up and Error Set
Signal for Master Function (X03) is set to ON. At this time, I/O
Communicating (X01) is not set to ON.
For details of Error Set Signal for Master Function (X03), refer to Section
(4).
• Setting I/O Communication Request (Y11) to OFF stops I/O
communication with each slave node, causing I/O Communicating (X01)
to turn OFF.

When parameter check completed successfully

Module Ready (X0F)

I/O Communication Request (Y11)

I/O Communicating (X01)

Parameter
check

3-5 3-5
3 SPECIFICATIONS
MELSEC-Q

When parameter check failed

Module Ready (X0F)

I/O Communication Request (Y11)

I/O Communicating (X01) OFF

Error Set Signal for Master Function (X03)

Parameter
check

POINT
(1) I/O Communicating (X01) is not set to ON even if I/O Communication Request
(Y11) is turned ON with the following output signals set to ON,
• Auto Configuration Request (Y15)
• Request for Saving Parameters to Flash ROM (Y17)
Turn OFF the output signals, and set I/O Communication Request (Y11) to ON
from OFF.
(2) To stop I/O communication, set I/O Communication Request (Y11) and after
200ms or more has elapsed, reset it.

3-6 3-6
3 SPECIFICATIONS
MELSEC-Q

(b) When starting I/O communication automatically at power-up

Set "Start" in Automatic Communication Start Setting (address: 0631H).
• When power is turned ON, Module Ready (X0F) is set to ON and
parameters are checked.
• If the parameter check is completed successfully, I/O communication with
each slave node is started and I/O Communicating (X01) is set to ON.
• If the parameter check has failed, the ERR. LED lights up and Error Set
Signal for Master Function (X03) is set to ON. At this time, I/O
Communicating (X01) is not set to ON.
For details of Error Set Signal for Master Function (X03), refer to Section
(4).
• Setting I/O Communication Request (Y11) to ON and then OFF stops I.O
communication with each slave node, causing I/O Communicating
(X01)to turn OFF.

When parameter check completed successfully

Module Ready (X0F)

I/O Communicating (X01)

Parameter
check

When parameter check failed

Module Ready (X0F)

I/O Communicating (X01)

OFF

Error Set Signal for

Master Function (X03)

Parameter
check

3-7 3-7
3 SPECIFICATIONS
MELSEC-Q

(3) Message Communication Completion (X02), Message

Communication Error Signal (X05), Message Communication
Request (Y12)
These signals are used for message communication. Execute each signal action
when Master Function Communication Status (address: 01B0H) is "OPERATE
(C0H)" or "STOP (40H)".

POINT
For message communications, the master function parameters must be set.
If the master function parameters have not been set, a message connection is
opened using message group 1.

(a) After setting command data in Message Communication Command

(address: 0110H to 011FH), when Message Communication Request (Y12)
is set to ON, message communication is started.
(Allow an interval of 100ms or more between turn-ON actions of Message
Communication Request (Y12).)

(b) Upon completion of a message communication, the processing result is

stored in Message Communication Result (address: 0120H to 012FH), and
Message Communication Completion (X02) is set to ON.
When failed, Message Communication Error Signal (X05) is set to ON.

(c) Setting Message Communication Request (Y12) to OFF causes Message

Communication Completion (X02) and Message Communication Error
Signal (X05) to turn OFF.

Message Communication
Request (Y12)

Message Communication
Completion (X02)

Message Communication When failed

Error Signal (X05)
Message comm. Message comm. Message comm. Message comm.
command data result data
(MOV/TO (MOV/TO (MOV/FROM (MOV/FROM
instruction) instruction) instruction) instruction)
(During data transmission only) (During data reception only)

3-8 3-8
3 SPECIFICATIONS
MELSEC-Q

(4) Error Set Signal for Master Function (X03), Error Reset Request for
Master Function (Y13)
These signals are used for notification of an error occurred during master
function execution and for error code resetting.
(a) When a master function error occurs, the error information is stored in Error
Information for Master Function (address: 01B1H), and Error Set Signal for
Master Function (X03) is set to ON.
When the error is corrected, Error Set Signal for Master Function is set to
OFF. (While I/O communication is stopped, however, it is not set to OFF.)

(b) After the error is removed, setting Error Reset Request for Master Function
(Y13) to ON clears the error code in Error Information for Master Function
(address: 01B1H).
Error Reset Request
for Master Function (Y13)

Error Set Signal

for Master Function (X03)

Error Information for

Master Function (01B1H)
Error code
(MOV/FROM instruction) cleared

(5) Slave Down Signal (X04)

This signal indicates whether or not there is a slave node that is in I/O
communication stop status (a failed node).
(a) If any one of the slave nodes that are set by parameters is detected as a
failed node, this signal is set to ON.
OFF: All nodes communicating normally
ON: Faulty node exists
(b) Slave Down Signal (X04) is set to OFF when communication with the failed
node resumes.

POINT
(1) The I/O communication status of each slave node can be confirmed at Node
Communication Status (address: 01BCH to 01BFH).
(2) Reserved nodes are recognized as failed nodes.
To prevent a reserved node from being detected as a failed node, turn ON the
corresponding bit in Failed Node Detection Setting (address: 01CCH to 01CFH).

3-9 3-9
3 SPECIFICATIONS
MELSEC-Q

(6) Saving Parameters to Flash ROM (X06), Parameters Saved to

Flash ROM (X07), Request for Saving Parameters to Flash ROM
(Y17)
These signals are used to save the parameters in the buffer memory to the flash
ROM. Execute each signal action while I/O Communicating (X01) is OFF.
(a) When Request for Saving Parameters to Flash ROM (Y17) is set to ON,
parameters are checked.

(b) If the parameter check is completed successfully, saving the parameters to

the flash ROM is started, and Saving Parameters to Flash ROM (X06) is
set to ON.

(c) If the parameter check has failed, the ERR. LED lights up and Error Set
Signal for Master Function (X03) or Error Set Signal for Slave Function
(X08) is set to ON.
For details of Error Set Signal for Master Function (X03), refer to Section
(4).
For details of Error Set Signal for Slave Function (X08), refer to Section
3.3.3 (4).

(d) Upon completion of parameter saving to the flash ROM, Parameters Saved
to Flash ROM (X07) is set to ON.

(e) When Request for Saving Parameters to Flash ROM (Y17) is set to OFF,
Saving Parameters to Flash ROM (X06) and Parameters Saved to Flash
ROM (X07) are set to OFF.

When parameter check completed successfully

I/O Communication Request (Y11)

I/O Communicating (X01)

Request for Saving Parameters

to Flash ROM (Y17)

Saving Parameters
to Flash ROM (X06)

Parameters Saved
to Flash ROM (X07)

Parameters
(MOV/TO Parameter
instruction) check

3 - 10 3 - 10
3 SPECIFICATIONS
MELSEC-Q

When parameter check failed

I/O Communication
Request (Y11)

I/O Communicating (X01)

Request for Saving Parameters

to Flash ROM (Y17)

Saving Parameters
to Flash ROM (X06) OFF

Parameters Saved
to Flash ROM (X07) OFF

Error Set Signal

for Master Function (X03)
Error Set Signal
for Slave Function (X08)
Parameters Parameter
(MOV/TO check
instruction)

POINT
(1) Even if Request for Saving Parameters to Flash ROM (Y17) is set to ON while
I/O Communicating (X01) is ON, Parameters Saved to Flash ROM (X07) is not
set to ON. Set I/O Communication Request (Y11) to ON, and after confirming
that I/O Communicating (X01) is OFF, set Request for Saving Parameters to
Flash ROM (Y17) to OFF and then ON.
(2) Even if Request for Saving Parameters to Flash ROM (Y17) is set to ON while
the following output signal is ON, Parameters Saved to Flash ROM (X07) is not
set to ON.
• I/O Communication Request (Y11)
• Auto Configuration Request (Y15)
Set the output signal to OFF, and then set Request for Saving Parameters to
Flash ROM (Y17) to OFF and then ON.
(3) Since there is a restriction on the number of writes to Flash ROM, execute
Request for Saving Parameters to Flash ROM (Y17) only when parameters are
newly created or changed.

(7) Module Ready (X0F)

This signal indicates whether or not the QJ71DN91 is operable.
When the QJ71DN91 is ready to operate, it is set to ON.
When Watchdog Timer Error (X00) turns ON, this Module Ready (X0F) is set to
OFF.

3 - 11 3 - 11
3 SPECIFICATIONS
MELSEC-Q

(8) Auto-Configuring (X14), Auto Configuration Completion (X15), Auto

Configuration Request (Y15)
These signals are used to configure parameters automatically. Execute them
while I/O Communicating (X01) is OFF.
(a) When Auto Configuration Request (Y15) is set to ON, auto configuration
starts and Auto-Configuring (X14) is set to ON.
Up to approx. 60 seconds are needed for completion of auto configuration.

(b) Upon completion of auto configuration, parameters are stored in

Parameters for Master Function (address: 01D4H to 03CFH) and Auto
Configuration Completion (X15) is set to ON.

(c) When Auto Configuration Request (Y15) is set to OFF, Auto-Configuring

(X14) and Auto Configuration Completion (X15) are set to OFF.
I/O Communication Request (Y11)

I/O Communicating (X01)

Auto Configuration Request (Y15)

Auto-Configuring (X14)

Auto Configuration Completion (X15)

POINT
Auto Configuration Completion (X15) is not set to ON even if Auto Configuration
Request (Y15) is set to ON while the following output signals are ON.
• I/O Communication Request (Y11)
• Request for Saving Parameters to Flash ROM (Y17)
Turn the output signals to OFF, and set Auto Configuration Request (Y15) to ON
from OFF again.

(9) H/W Test in Progress (X0A), H/W Test Completion (X0B), H/W
Test Error Detection (X0C)
The hardware test status is indicated.
For the hardware test, refer to Section 5.4.
(a) Turning ON the module with the mode set to 9 starts the hardware test, and
H/W Test in Progress (X0A) is set to ON.

(b) Upon normal completion of the hardware test, H/W Test Completion (X0B)
is set to ON.

(c) If a failure occurs in the hardware test, H/W Test Error Detection (X0C) is
set to ON. At this time, H/W Test Completion (X0B) is not set to ON.

3 - 12 3 - 12
3 SPECIFICATIONS
MELSEC-Q

3.3.3 I/O signals for the slave function

This section describes the ON/OFF timings and conditions of the I/O signals used for
the slave function.

(1) Watchdog Timer Error (X00)

Refer to Section 3.3.2 (1).

(2) I/O Communicating (X01), I/O Communication Request (Y11)

These are used to start I/O communication with a master node.
Execute these signal actions while Module Ready (X0F) is ON.
(a) When starting I/O communication by I/O Communication Request (Y11)
• When I/O Communication Request (Y11) is set to ON, parameters are
checked.
• If the parameter check is completed successfully, I/O communication with
the master node is started and I/O Communicating (X01) is set to ON.
Note that, until receiving an I/O communication request from the master
node, the module waits for connection establishment.
• If the parameter check has failed, the ERR. LED lights up and Error Set
Signal for Slave Function (X08) is set to ON. At this time, I/O
Communicating (X01) is not set to ON.
For details of Error Set Signal for Slave Function (X08), refer to Section
(4).
• Setting I/O Communication Request (Y11) to OFF stops I/O
communication with the master node, causing I/O Communicating (X01)
to turn OFF.

When parameter check completed successfully

Module Ready (X0F)

I/O Communication Request (Y11)

I/O Communicating (X01)

Parameter
check

3 - 13 3 - 13
3 SPECIFICATIONS
MELSEC-Q

When parameter check failed

Module Ready (X0F)

I/O Communication Request (Y11)

I/O Communicating (X01)

OFF

Error Set Signal for

Slave Function (X08)

Parameter
check

POINT
(1) I/O Communicating (X01) is not set to ON even if I/O Communication Request
(Y11) is turned ON with the following output signals set to ON,
• Auto Configuration Request (Y15)
• Request for Saving Parameters to Flash ROM (Y17)
Turn OFF the output signals, and set I/O Communication Request (Y11) to ON
from OFF.
(2) To stop I/O communication, set I/O Communication Request (Y11) and after
200ms or more has elapsed, reset it.

3 - 14 3 - 14
3 SPECIFICATIONS
MELSEC-Q

(b) When starting I/O communication automatically at power-up

Set "Start" in Automatic Communication Start Setting (address: 0631H).
• When power is turned ON, Module Ready (X0F) is set to ON and
parameters are checked.
• If the parameter check is completed successfully, I/O communication with
the master node is started and I/O Communicating (X01) is set to ON.
Note that, until receiving an I/O communication request from the master
node, the module waits for connection establishment.
• If the parameter check has failed, the ERR. LED lights up and Error Set
Signal for Slave Function (X08) is set to ON. At this time, I/O
Communicating (X01) is not set to ON.
For details of Error Set Signal for Slave Function (X08), refer to Section
(4).
• Setting I/O Communication Request (Y11) to ON and then OFF stops I/O
communication with the master node, causing I/O Communicating (X01)
to turn OFF.

When parameter check completed successfully

Module Ready (X0F)

I/O Communicating (X01)

Parameter
check

When parameter check failed

Module Ready (X0F)

I/O Communicating (X01) OFF

Error Set Signal

for Slave Function (X08)

Parameter
check

(3) Saving Parameters to Flash ROM (X06), Parameters Saved to

Flash ROM (X07), Request for Saving Parameters to Flash ROM
(Y17)
Refer to Section 3.3.2 (6).

3 - 15 3 - 15
3 SPECIFICATIONS
MELSEC-Q

(4) Error Set Signal for Slave Function (X08), Error Reset Request for
Slave Function (Y18)
These signals are used for notification of an error occurred during slave function
execution and for error code resetting.
(a) When a slave function error occurs, the error information is stored in Error
Information for Slave Function (address: 0601H), and Error Set Signal for
Slave Function (X08) is set to ON.
When the error is corrected, Error Set Signal for Slave Function (X08) is set
to OFF. (While I/O communication is stopped, however, it is not set to
OFF.)

(b) After the error is removed, setting Error Reset Request for Slave Function
(Y18) to ON clears the error code in Error Information for Slave Function
(address: 0601H).
Error Reset Request
for Slave Function (Y18)

Error Set Signal

for Slave Function (X08)

Error Information
for Slave Function Error code
(0601H)(MOV/FROM cleared
instruction)

(5) Module Ready (X0F)

Refer to Section 3.3.2 (7).

3 - 16 3 - 16
3 SPECIFICATIONS
MELSEC-Q

3.4 Buffer Memory

This section explains the buffer memory of the QJ71DN91.

3.4.1 Buffer memory list

The buffer memory list is shown in Table 3.6.

Table 3.6 Buffer memory list (1/2)

Address Availability
Reference
Item Description Master Slave Read/Write *1
Hex. Dec. section
function function
0000H to
0 to 271 Use prohibited — — — — —
010FH
0110H to Message Communication A command for message
272 to 287 — R/W
011FH Command communication is set.
0120H to Message Communication Stores result data of message
288 to 303 — R 3.4.2
012FH Result communication.
0130H to Message Communication Stores transmit and receive data of
304 to 423 — R/W
01A7H Data message communication.
01A8H to
424 to 431 Use prohibited — — — — —
01AFH
Master Function Stores the communication status of
01B0H 432 — R
Communication Status the master function.
Error Information for Stores a communication error code of
01B1H 433 — R
Master Function the error occurred.
Stores an illegal frame count of the
3.4.3
01B2H 434 Bus Error Counter CAN chip (communication chip for — R
DeviceNet) when it exceeds 96.
Stores the number of times the
01B3H 435 Bus Off Counter QJ71DN91 was placed in the bus off — R
status.
01B4H to Stores parameter setting status of
436 to 439 Node Configuration Status — R 3.4.4
01B7H each slave node.
01B8H to
440 to 443 Use prohibited — — — — —
01BBH
01BCH to Node Communication Stores I/O communication status of
444 to 447 — R
01BFH Status each slave node.
01C0H to Node Communication Stores I/O communication error status
448 to 451 — R 3.4.4
01C3H Error Status of each slave node.
01C4H to Stores communication fault status of
452 to 455 Node Fault Status — R
01C7H each slave node.
01C8H to
456 to 459 Use prohibited — — — — —
01CBH
01CCH to Failed Node Detection Whether or not to detect any failed
460 to 463 — R/W 3.4.4
01CFH Setting node is set.
01D0H to
464 to 467 Use prohibited — — — — —
01D3H
01D4H to Parameters for Master Parameters for master function are
468 to 975 — R/W 3.4.5
03CFH Function *2 set.
03D0H to
976 to 1007 Use prohibited — — — — —
03EFH
Auto Configuration
03F0H 1008 Operation of auto configuration is set. — R/W 3.4.5
Operation Setting
03F1H to
1009 to 1279 Use prohibited — — — — —
04FFH
Stores the start addresses and sizes
(in word units) of Master Function
0500H to I/O Address Area for Receive Data (address: 0700H to
1280 to 1531 — R 3.4.6
05FBH Master Function 07FFH) and Master Function Transmit
Data (address: 0900H to 09FFH) for
slave nodes.

3 - 17 3 - 17
3 SPECIFICATIONS
MELSEC-Q

Table 3.6 Buffer memory list (2/2)

Address Availability
Reference
Item Description Master Slave Read/Write *1
Hex. Dec. section
function function
Stores the current link scan time. (Unit:
05FCH 1532 Present Link Scan Time — R
ms)
Stores the minimum link scan time after
05FDH 1533 Minimum Link Scan Time — R 3.4.7
power-ON. (Unit: ms).
Stores the maximum link scan time after
05FEH 1534 Maximum Link Scan Time — R
power-ON. (Unit: ms).
05FFH 1535 Use prohibited — — — — —
Slave Function Stores the communication status of the
0600H 1536 — R
Communication Status slave function.
3.4.8
Error Information for Slave Stores a communication error code of the
0601H 1537 — R
Function error occurred in the slave function.
0602H to
1538 to 1549 Use prohibited — — — — —
060DH
Slave Function Receive- The I/O receive data size (bytes) for the
060EH 1550 — R/W
Bytes Setting Area slave function is set.
3.4.9
Slave Function Transmit- The I/O transmit data size (bytes) for the
060FH 1551 — R/W
Bytes Setting Area slave function is set.
0610H to
1552 to 1567 Use prohibited — — — — —
061FH
0620H to
1568 to 1572 Model Name Stores "QJ71DN91" in ASCII code. R
0624H
Stores the number of the node currently
0625H 1573 Node No. R 3.4.11
in operation.
Stores the mode switch number currently
0626H 1574 Mode Switch No. R
in operation.
0627H to
1575 to 1581 Use prohibited — — — — —
062DH
Stores the test item number of the
062EH 1582 Hardware Test Item Area hardware test or communication test that For hardware test R
is currently being executed. 3.4.12
Hardware Test Result Stores the result of the hardware test or
062FH 1583 For hardware test R
Area communication test.
Select the area of the parameters to be
0630H 1584 Parameter Area Select Bit R/W 3.4.13
saved to a flash ROM.
Set whether or not to auto-start I/O
Auto Communication Start communication with parameters saved on
0631H 1585 R/W 3.4.14
Setting *2 the flash ROM at the time of power ON
from OFF or CPU reset.
Set whether or not to reset the QJ71DN91’s
Operation Setting Area for CAN chip (communication chip) to restart
0632H 1586 R/W 3.4.3
Bus Off Error communications in the event of a bus off
error.
0633H to
1587 to 1791 Use prohibited — — — — —
06FFH
0700H to Master Function Receive Stores the data received from each slave
1792 to 2047 — R 3.4.6
07FFH Data node.
0800H to
2048 to 2303 Use prohibited — — — — —
08FFH
0900H to Master Function Transmit
2304 to 2559 Data to be sent to each slave node is set. — R/W 3.4.6
09FFH Data
0A00H to
2560 to 2815 Use prohibited — — — — —
0AFFH
0B00H to Slave Function Receive Stores the data received from the master
2816 to 2879 — R 3.4.10
0B3FH Data node.
0B40H to
2880 to 3071 Use prohibited — — — — —
0BFFH
0C00H to Slave Function Transmit
3072 to 3135 Data to be sent to the master node is set. — R/W 3.4.10
0C3FH Data
0C40H to 3136 to
Use prohibited — — — — —
7FFFH 32767

3 - 18 3 - 18
3 SPECIFICATIONS
MELSEC-Q

*1: Indicates whether or not data can be read or written from sequence programs.
R: Read only, R/W: Read/Write
*2: Can be saved to a flash ROM.
Parameters in the buffer memory are cleared when power is turned off or when the CPU module is
reset, unless they are saved to a flash ROM.

3 - 19 3 - 19
3 SPECIFICATIONS
MELSEC-Q

3.4.2 Message communication area for master function

This area is used for the message communication of the master function.
For the execution timing, refer to Section 3.3.2 (3).

(1) Message Communication Command (address: 0110H to 011FH/272

to 287)
Set a command for message communication.
(a) Getting attribute data of a slave node

Table 3.7 Get Attribute

Buffer memory address
Item Description
(Hex.)
0110H Command No. 0101H=Get Attribute
Slave node No. (slave Low byte: Node No. of the slave node (MAC ID)
0111H
MAC ID), class ID High byte: Class ID of the object
0112H Instance ID Instance ID of the object
Low byte: Attribute ID of the object
0113H Attribute ID
High byte: Always sets to 0.

(b) Setting attribute data into a slave node

Table 3.8 Set Attribute

Buffer memory address
Item Description
(Hex.)
0110H Command No. 0102H =Set Attribute
Slave node No. (slave Low byte: Node No. of the slave node (MAC ID)
0111H
MAC ID), class ID High byte: Class ID of the object
0112H Instance ID Instance ID of the object
Low byte: Attribute ID of the object
0113H Attribute ID High byte: Byte length of the attribute data to be set
1 to 240 (1H to F0H)

(c) Reading communication error information of a slave node

Table 3.9 Reading communication error information
Buffer memory address
Item Description
(Hex.)
0110H Command No. 0001H =Reads Communication Error Information
Slave node No. (slave Low byte: Node No. of the slave node (MAC ID)
0111H
MAC ID) High byte: Always sets to 0.

(d) Resetting
Table 3.10 Reset
Buffer memory address
Item Description
(Hex.)
0110H Command No. 0201H =Reset
Slave node No. (slave Low byte: Node No. of the slave node (MAC ID)
0111H
MAC ID), class ID High byte: Class ID of the object
0112H Instance ID Instance ID of the object

3 - 20 3 - 20
3 SPECIFICATIONS
MELSEC-Q

(e) Other message communications

Data to be set are shown below.
For details, refer to DeviceNet common service in the DeviceNet
Specifications (Release2.0).
Table 3.11 Other message communications
Buffer memory address
Item Description
(Hex.)
0110H Command No. FE**H: Refer to DeviceNet Common Service for**.
Slave node No. (slave Low byte: Node No. of the slave node (MAC ID)
0111H
MAC ID), class ID High byte: Class ID of the object
0112H Instance ID Instance ID of the object
Low byte: Attribute ID of the object
0113H Attribute ID, data length High byte: Byte length of the attribute data to be set
1 to 240 (1H to F0H)

(2) Message Communication Result (address: 0120H to 012FH/288 to

303)
The result of processing for message communication is stored.
(a) Getting attribute data of a slave node
Table 3.12 Get Attribute
Buffer memory address
Item Description
(Hex.)
0120H Command No. 0101H =Get Attribute
Normal completion: 0000H
0121H Execution error code
Failed: Execution error code (Refer to Section 9.2.2.)
Slave node No. (slave Low byte: Node No. of the slave node (MAC ID)
0122H
MAC ID), class ID High byte: Class ID of the object
0123H Instance ID Instance ID of the object
Low byte: Attribute ID of the object
0124H Attribute ID, data length High byte: Byte length of the gotten attribute data
1 to 240 (1H to F0H)

(b) Setting attribute data of a slave node

Table 3.13 Set Attribute
Buffer memory address
Item Description
(Hex.)
0120H Command No. 0102H =Set Attribute
Normal completion: 0000 H
0121H Execution error code
Failed: Execution error code (Refer to Section 9.2.2.)
Slave node No. (slave Low byte: Node No. of the slave node (MAC ID)
0122H
MAC ID), class ID High byte: Class ID of the object
0123H Instance ID Instance ID of the object
Low byte: Attribute ID of the object
0124H Attribute ID, data length High byte: Byte length of the attribute data
(1 to 240)

3 - 21 3 - 21
3 SPECIFICATIONS
MELSEC-Q

(c) Reading communication error information of a slave node

Table 3.14 Read communication error information
Buffer memory
Item Description
address (Hex.)
0120H Command No. 0001H =Read communication error information
Normal completion: 0000H
0121H Execution error code
Failed: Execution error code (Refer to Section 9.2.2.)

(d) Resetting
Table 3.15 Reset
Buffer memory
Item Description
address (Hex.)
0120H Command No. 0201H =Reset
Normal completion: 0000H
0121H Execution error code
Failed: Execution error code (Refer to Section 9.2.2.)
Slave node No. (slave Low byte: Node No. of the slave node (MAC ID)
0122H
MAC ID), class ID High byte: Class ID of the object
0123H Instance ID Instance ID of the object

(e) Other message communications

Table 3.16 Other message communications
Buffer memory
Item Description
address (Hex.)
0120H Command No. FE**H: Refer to DeviceNet Common Service for**.
Normal completion: 0000H
0121H Execution error code
Failed: Execution error code (Refer to Section 9.2.2.)
Slave node No. (slave Low byte: Node No. of the slave node (MAC ID)
0122H
MAC ID), class ID High byte: Class ID of the object
0123H Instance ID Instance ID of the object
Low byte: Attribute ID of the object
0124H Attribute ID, data length High byte: Byte length of the gotten attribute data
1 to 240 (1H to F0H)

3 - 22 3 - 22
3 SPECIFICATIONS
MELSEC-Q

(3) Message Communication Data (address: 0130H to 01A7H /304 to

423)
This area stores data sent/received by message communications.
(a) Getting attribute data of a slave node
Attribute data is stored in units of bytes.

0130H 2nd byte 1st byte

4th byte 3rd byte
6th byte 5th byte
to Attribute data that was gotten
•••

•••
01A7H

(b) Setting attribute data of a slave

Attribute data to be set is configured in units of bytes.

0130H 2nd byte 1st byte

4th byte 3rd byte
6th byte 5th byte
to Attribute data to be set
•••

•••

01A7H

3 - 23 3 - 23
3 SPECIFICATIONS
MELSEC-Q

(c) Reading communication error information of a slave node

The communication error information that was read is stored.

Table 3.17 Reading communication error information

Buffer memory address
Item Description
(Hex.)
Stores data showing whether or not the slave node
0130H Slave status is set with parameters, whether or not it has
responded, etc. (See 1).)
0131H Use prohibited —
Stores the same error code as in Error Information
0132H Communication error for Master Function (address 01B1H).
(Refer to Section 9.2.1.)
Stores a general DeviceNet error code sent from the
General DeviceNet error
0133H slave node. Valid only when the communication
code
error code is 35 (0023H). (Refer to Section 9.2.3.) *1
Stores an additional error code sent from the slave
0134H Additional error code
node. *2
Stores the number of times the QJ71DN91 has
0135H Heartbeat timeout count
detected failure of each slave node.

*1: Refer to the manual of each slave node for actual failures and troubleshooting.
*2: Refer to the manual of each slave node for the meaning of each error code.

1) Slave status
The ON/OFF status of each bit notifies of a slave node error as shown
below.

Bit 8 to 15 Bit7 Bit6 Bit5 Bit4 Bit3 Bit2 Bit1 Bit0

Used by the system

Slave node did not respond.

Slave node refused to set

the attribute data.

I/O data size set by a

parameter is different from
the actual size.

Set as a reserved node

with a parameter.

If the corresponding bit is ON, any of

these errors may have occurred.

(d) Other message communications

For details, refer to DeviceNet Specifications (Release2.0) Volumes 1 and
2.

3 - 24 3 - 24
3 SPECIFICATIONS
MELSEC-Q

3.4.3 Own node status area for master function

This area stores the communication status, error information, etc. of the master
function.

(1) Master Function Communication Status (address: 01B0H/432)

The communication status of the master function is stored.
(a) High byte
The I/O communication status of the master station is stored.

Table 3.18 Master function I/O communication status

Value Name Operation
00H Offline Being initialized
40H Stop I/O communication stopped
C0H Operate I/O communication in progress

1) When "No start" is set for Auto Communication Start Setting (address:
0631H)
Upon power-up, the status automatically changes from Offline (00H) to
Stop (40H).
When I/O Communication Request (Y11) is set to ON, the status
changes to Operate (C0H).
2) When "Start" is set for Auto Communication Start Setting (address:
0631H)
Upon power-up, the status automatically changes from Offline (00H) to
Operate (C0H).
3) When a reset message is received through the network
The status automatically returns to Offline (00H), and then changes to
Operate (C0H).

3 - 25 3 - 25
3 SPECIFICATIONS
MELSEC-Q

(b) Low byte

The communication status of the network is stored.
Depending on the communication status, each bit turns ON/OFF as shown
below.

Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

A faulty node exists.

Always
OFF

Parameter error
Always OFF
Network has a serious
problem and communication
is not available.
If the corresponding bit is ON, any
of these errors may have occurred.

3 - 26 3 - 26
3 SPECIFICATIONS
MELSEC-Q

(2) Error Information for Master Function (address: 01B1H/433)

A code for a communication error occurred in the master function is stored.
For error notification and a clearing method of this area, refer to Section 3.3.2 (4).
(a) High byte
An error code is stored. (Refer to Section 9.2.1.)

(b) Low byte

The number of the node (MAC ID), where an error occurred, is stored.
FEH, FFH (254, 255): Own node (QJ71DN91)
0H to 3FH (0 to 63): Node No. (MAC ID) of the slave node where an error
occurred.

POINT
If errors occur at multiple nodes, the error information of the node with the smallest
node No. (MAC ID) is stored.

(3) Bus Error Counter (address: 01B2H/434)

The number of times that the illegal frame count of the CAN chip (DeviceNet's
communication chip) exceeded 96 is stored.
An increase of this value means that communications are unreliable.

(4) Bus Off Counter (address: 01B3H/435)

The number of times that the QJ71DN91 was placed in the bus off status is
stored.
An increase of this value means that communications are unreliable.

(5) Operation Setting Area for Bus Off Error (address: 0632H/1586)
Set whether or not to reset the QJ71DN91’s CAN chip (communication chip) to
resume the communication in the event of a bus off error,
Setting "1" in this area enables communication resumption without resetting the
CPU module.
This setting must be done before I/O communication (before setting I/O
Communication Request (Y11) to ON).
Even if "1" is set in this area after occurrence of a bus off error, the CAN chip is
not reset.
0: Stop communication without resetting the CAN chip (Default)
1: Resume communication by resetting the CAN chip
*: When any value other than 0 and 1 is set, the CAN chip is not reset.

(a) Confirming a bus off error

A bus off error can be confirmed by a LED and relevant values in the buffer
memory.
1) LED
The NS LED on the QJ71DN91 turns ON red.
2) Buffer memory
How many times the error occurred is stored in Bus Error Counter
(address: 01B2H) and Bus Off Counter (address: 01B3H).

3 - 27 3 - 27
3 SPECIFICATIONS
MELSEC-Q

(b) After resetting the CAN chip

The LED and relevant values in the buffer memory are changed as follows:
1) LED
When the CAN chip is reset, the NS LED status on the QJ71DN91
changes as follows: turning ON (red) OFF flashing (green)
remaining ON (green).
2) Buffer memory
Values in Bus Error Counter (address: 01B2H) and Bus Off Counter
(address: 01B3H) are not cleared even if the CAN chip is reset.

3 - 28 3 - 28
3 SPECIFICATIONS
MELSEC-Q

3.4.4 Node status area for master function

The operation status of each slave node is stored in this area.

(1) Node Configuration Status (address: 01B4H to 01B7H/436 to 439)

The parameter setting status of each slave node is stored.
• When the corresponding bit is ON: Parameters have already been set.
• When the corresponding bit is OFF: Parameters have not been set.
Table 3.19 Node No. corresponding to each bit in Node Configuration Status
Buffer memory address Node No. corresponding to each bit
(Hex.) Bit 15 Bit 14 … Bit 1 Bit 0
01B4H Node 15 Node 14 … Node 1 Node 0
01B5H Node 31 Node 30 … Node 17 Node 16
01B6H Node 47 Node 46 … Node 33 Node 32
01B7H Node 63 Node 62 … Node 49 Node 48

(a) Bit ON timing

When a slave node executes the following, and when the parameter check
is completed successfully, the bit corresponding to the slave node turns
ON.
• Starting I/O communication (Refer to Section 3.2.2 (2).)
• Saving master function parameters to flash ROM (Refer to Section 3.3.2
(6).)

(b) Bit OFF timing

1) Remove settings of a slave node from master function parameters and
execute the following:
• Starting I/O communication (Refer to Section 3.3.2 (6).)
• Saving master function parameters to flash ROM (Refer to Section
3.3.2 (6).)
When the parameter check is completed successfully, the bit
corresponding to the slave node turns OFF.
2) When the master node is powered ON from OFF, or when the CPU
module is reset, all bits turn ON.

(2) Node Communication Status (address: 01BCH to 01BFH/444 to

447)
The I/O communication status of each slave node is stored.
While I/O Communicating (X01) is OFF, all bits are OFF.
• When the corresponding bit is ON: Communication in progress
• When the corresponding bit is OFF: Communication stopped
Table 3.20 Node No. corresponding to each bit in Node Communication Status
Buffer memory address Node No. corresponding to each bit
(Hex.) Bit 15 Bit 14 … Bit 1 Bit 0
01BCH Node 15 Node 14 … Node 1 Node 0
01BDH Node 31 Node 30 … Node 17 Node 16
01BEH Node 47 Node 46 … Node 33 Node 32
01BFH Node 63 Node 62 … Node 49 Node 48

3 - 29 3 - 29
3 SPECIFICATIONS
MELSEC-Q

(3) Node Communication Error Status (address: 1C0H to 1C3H/448 to

451)
The I/O communication error status of each slave node is stored.
While I/O Communicating (X01) is OFF, all bits are OFF.
Note that no error is detected for the node whose corresponding bit is ON in
Failed Node Detection Setting (address: 01CCH to 01CFH).
• When the corresponding bit is ON: Communication error exists.
• When the corresponding bit is OFF: No communication error
Table 3.21 Node No. corresponding to each bit in Node Communication Error Status
Buffer memory address Node No. corresponding to each bit
(Hex.) Bit 15 Bit 14 … Bit 1 Bit 0
01C0H Node 15 Node 14 … Node 1 Node 0
01C1H Node 31 Node 30 … Node 17 Node 16
01C2H Node 47 Node 46 … Node 33 Node 32
01C3H Node 63 Node 62 … Node 49 Node 48

POINT
When any of the bits in this area turns ON, Slave Down Signal (X04) is set to ON.

(4) Node Fault Status (address: 01C4H to 01C7H/452 to 455)

The communication fault status of each slave node is stored.
• When the corresponding bit is ON: Fault information exists
• When the corresponding bit is OFF: No fault information
Reading communication error information of the node in message
communication will turn OFF the corresponding bit. (Refer to Section 4.2 (3).)
Table 3.22 Node No. corresponding to each bit in Node Fault Status
Buffer memory address Node No. corresponding to each bit
(Hex.) Bit 15 Bit 14 … Bit 1 Bit 0
01C4H Node 15 Node 14 … Node 1 Node 0
01C5H Node 31 Node 30 … Node 17 Node 16
01C6H Node 47 Node 46 … Node 33 Node 32
01C7H Node 63 Node 62 … Node 49 Node 48

3 - 30 3 - 30
3 SPECIFICATIONS
MELSEC-Q

(5) Failed Node Detection Setting (address: 01CCH to 01CFH /460 to

463)
Whether or not to detect a failed node is set in this area.
The setting determines whether or not the OFF status in Node Communication
Status (address: 01BCH to 01BFH) is reflected to Slave Down Signal (X04).
• When the corresponding bit is ON: Slave Down Signal (X04) is not set to ON
even if the slave node went down.
• When the corresponding bit is OFF: Slave Down Signal (X04) is set to ON if the
slave node went down.
Table 3.23 Node No. corresponding to each bit in Failed Node Detection Setting
Buffer memory address Node No. corresponding to each bit
(Hex.) Bit 15 Bit 14 … Bit 1 Bit 0
01CCH Node 15 Node 14 … Node 1 Node 0
01CDH Node 31 Node 30 … Node 17 Node 16
01CEH Node 47 Node 46 … Node 33 Node 32
01CFH Node 63 Node 62 … Node 49 Node 48

POINT
For a node that is set as a reserved node with a master function parameter, turn
ON the corresponding bit of Failed Node Detection Setting. If it remains OFF, it is
recognized as a failed node even if it is just a reserved node.

3 - 31 3 - 31
3 SPECIFICATIONS
MELSEC-Q

3.4.5 Master function parameter setting area

Parameters for master function are set in this area.

To exchange I/O data with each slave node (up to 63 nodes), information such as
connection types and I/O points is set.

(1) Parameters for Master Function (address: 01D4H to 03CFH/468 to

975)
Master function parameters are set in this area.
For use of auto configuration, refer to Section 7.3 (2).
For saving parameters to a flash ROM, refer to Section 7.3 (3).

Table 3.24 Master function parameters

Buffer memory
Item Description
address (Hex.)
01D4H to
Use prohibited —
01D6H
Specified to keep link scan time constant.
01D7H Constant scan
(Setting range: 0 to 65535 ms (FFFFH))*1
Low byte: Node No. (MAC ID) of the 1st slave node
00H to 3FH (0 to 63)
High byte: 01H Node that supports UCMM and uses any of message groups
Node No. and message
01D8H 3, 2, and 1.
group
03H Node that supports UCMM and uses message group 1
04H Node that does not support UCMM (Group 2 only server)
80H Reserved node
Select a connection type for I/O communication.
0001H = Polling
01D9H Connection type 0002H = Bit strobe
0004H = Change of state
1st slave 0008H = Cyclic
node Low byte: Number of input byte modules
01DAH Number of byte modules High byte: Number of output byte modules (set in hexadecimal)
Eight bit modules (8 points) are counted as one byte module.
Low byte: Number of input word modules
01DBH Number of word modules
High byte: Number of output word modules (set in hexadecimal)
Number of double-word Low byte: Number of input double-word modules
01DCH
modules High byte: Number of output double-word modules (set in hexadecimal)
Set an expected packet rate for the slave node.
Setting varies depending on the connection type. For details, refer to Table
01DDH Expected packet rate 3.25. (Setting range: 0 to 65535 ms (FFFFH))*1
0000H: 200ms (Default)
Other than 0000H: Set value – 1 (ms)

3 - 32 3 - 32
3 SPECIFICATIONS
MELSEC-Q

Buffer memory
Item Description
address (Hex.)
Set an action for watchdog timeout of the slave node.
0000H: Equivalent to the following Timeout (Default)
0001H: Timeout
The connection is placed in timeout status.
Not recovered until an operator stops the communication and then
resumes it.
01DEH Watchdog timeout action 0002H: Auto Delete
The connection is automatically deleted. At this time the
1st slave communication stops once, and then resumes automatically.
node The output is cleared once.
0003H: Auto Reset
The communication continues while the connection is maintained.
The output is not cleared.
Set a production inhibit time.
Setting varies depending on the connection type. For details, refer to Table
01DFH Production inhibit time 3.25. (Setting range: 0 to 65535 ms (FFFFH))*1
0000H: 10ms (Default)
Other than 0000H: Set value –1 (ms)
01E0H to
Settings for 2nd to 63rd slave nodes Same as those for 1st slave node
03CFH
*1: When setting a value of 32768 or more, set it in hexadecimal.

POINT
When changing master function parameters, set default values for the areas after
the changed area.
(Example) When changing the number of slave nodes that perform I/O
communication, set default values in the areas for the 5th and 6th slave
nodes.

3 - 33 3 - 33
3 SPECIFICATIONS
MELSEC-Q

Table 3.25 Details of the expected packet rate and production inhibit time
Expected packet rate Production inhibit time
(1) Set a communication watchdog timer value for the (1) Set a minimum transmit interval of the slave node,
slave node. When the communication between the which is the minimum time during which the slave
master node and the slave node stops for the node can prepare transmit data. The master node
duration represented by "set value 4," the slave transmits a polling request to the slave node when
node executes the operation specified by the this time or longer has elapsed.*1
Watchdog Timeout Action.
Polling
(2) When the specified expected packet rate value is not equal to 1 (not equal to 0 ms), the expected packet rate
must be equal to or greater than the production inhibit time.
(3) When the set value = 1, i.e., when the expected (3) When the set value = 1, i.e. when the production
packet rate = 0 ms, the watchdog timer monitoring inhibit time = 0 ms, the master node transmits a
function is disabled. polling request to the slave node at intervals of the
module scan.
(1) Set a communication watchdog timer value for the (1) Set a minimum transmit interval of the slave node,
slave node. When the communication between the which is the minimum time during which the slave
master node and the slave node stops for the can prepare transmit data. The master node
duration represented by "set value 4," the slave transmits a bit strobe request to the slave node
node executes the operation specified by the when this time or longer has elapsed.*1
Watchdog Timeout Action.
Bit strobe*2
(2) When the specified expected packet rate value is not equal to 1 (not equal to 0 ms), the expected packet rate
must be equal to or greater than the production inhibit time.
(3) When the set value = 1, i.e., when the expected (3) When the set value = 1, i.e. when the production
packet rate = 0 ms, the watchdog timer monitoring inhibit time = 0 ms, the master node transmits a bit
function is disabled. strobe request to the slave node at intervals of the
module scan.
(1) Set a communication watchdog timer value for the (1) Set a minimum time during which the slave node can
slave node. When the communication between the receive data. The master node transmits output
master node and the slave node stops for the data to the slave node at this time intervals. (The
duration represented by "set value 4," the slave master node also transmits data to the slave node
node executes the operation specified by the when output data changes.)*1
Change of state Watchdog Timeout Action.
(2) When the specified expected packet rate value is not equal to 1 (not equal to 0 ms), the expected packet rate
must be equal to or greater than the production inhibit time.
(3) When the set value = 1, i.e., when the expected (3) When the set value = 1, i.e. when the production
packet rate = 0 ms, the watchdog timer monitoring inhibit time = 0 ms, the master node transmits data
function is disabled. to the slave node only when output data changes.
(1) Specify an interval of data transmissions from the (1) Specify an interval of data transmissions from the
slave node to the master node. master node to the slave node.*1
(2) When the specified expected packet rate value is not equal to 1 (not equal to 0 ms), the expected packet rate
Cyclic
must be equal to or greater than the production inhibit time.
(3) Setting of the set value = 1, i.e., the expected packet (3) Setting of the set value = 1, i.e., the production
rate = 0 ms is inhibited. inhibit time = 0 ms is inhibited.
*1: If the setting of the production inhibit time is shorter than the scan time of the module, the master node transmits data to the slave node
at the intervals of the module’s scan.
*2: The setting of the production inhibit time must be the same in all bit strobe connections.

3 - 34 3 - 34
3 SPECIFICATIONS
MELSEC-Q

(2) Auto Configuration Operation Setting (address: 03F0H/1008)

The operation of auto configuration is set in this area.
For the execution timing, refer to Section 7.3 (2).
(a) Setting details
1) High byte
Set an auto configuration type.
00H: All configuration (Default)
01H: Add configuration
2) Low byte
Set the maximum detection node No.
00H to 3FH (0 to 63) (Default: 3FH)

(b) Operation of auto configuration

1) When "All configuration" is set:
• Clears all of Parameters for Master Function (address: 01D4H to
03CFH). (Except the Constant scan area)
• Detects all of the slave nodes within a range from node 0 to the
maximum detection node on the network.
• Stores parameters of the detected slave nodes into the "Parameters
for Master Function" area (address: 01D4H to 03CFH).
2) When "Add configuration" is set:
• Detects all of the slave nodes within a range from node 0 to the
maximum detection node on the network, except for slave nodes
that have been already set to the master node.
• Stores parameters of the detected slave nodes into the area after
the preset area in Parameters for Master Function (address: 01D4H
to 03CFH).
Note that the area after the parameter storing area is not cleared.

3 - 35 3 - 35
3 SPECIFICATIONS
MELSEC-Q

(c) Contents of Parameters for Master Function set by auto configuration

An execution of auto configuration reads parameters of each slave node and
writes them to Parameters for Master Function (address: 01D4H to 03CFH).
Set values can be changed in sequence programs or GX Configurator-DN.

Table 3.26 Auto configuration settings

Buffer memory
Item Description
address (Hex.)
Low byte: Node No. (MAC ID) of the 1st slave node
00H to 3FH (0 to 63)
Node No. and message High byte: 01H Node that supports UCMM and uses any of message
01D8H
group groups 3, 2, and 1.
03H Node that supports UCMM and uses message group 1
04H Node that does not support UCMM (Group 2 only server)
Connection type for I/O communication.
0001H = Polling
01D9H Connection type 0002H = Bit strobe
0004H = Change of state
1st slave
0008H = Cyclic
node
Low byte: Number of input byte modules
01DAH Number of byte modules High byte: Number of output byte modules (set in hexadecimal)
Eight bit modules (8 points) are counted as one byte module.
Low byte: Number of input word modules
01DBH Number of word modules
High byte: Number of output word modules (set in hexadecimal)
Number of double-word Low byte: Number of input double-word modules
01DCH
modules High byte: Number of output double-word modules (set in hexadecimal)
01DDH Expected packet rate Default value is stored. (0000H: 200ms)
01DEH Watchdog timeout action Default value is stored. (0000H: Timeout)
01DFH Production inhibit time Default value is stored. (0000H: 10ms)
01E0H to
Settings for 2nd to 63rd slave nodes Same as those for 1st slave node
03CFH

3 - 36 3 - 36
3 SPECIFICATIONS
MELSEC-Q

3.4.6 Communication data area for master function

Communication data for the master function are stored in this area.

(1) Master Function Receive Data (address: 0700H to 07FFH/1792 to

2047)
Data received from each slave node are stored.
Data are aligned on word boundaries of slave nodes and stored as shown below.
For double-word data, the low word is stored first and then the high word.
When the number of byte input modules is an odd number, one byte of an empty
area is inserted.
Bit input modules are treated in the same way as byte input modules.
The following is an example.
<Example>
1st node - Number of byte input modules = 3
Number of word input modules = 2
Number of double-word input modules = 2
2nd node - Number of byte input modules = 1
3rd node - Number of byte input modules = 1

Buffer memory When the number of byte input

address modules is an odd number, one
byte of an empty area is inserted.
0700H 2nd byte module 1st byte module

0701H Empty 3rd byte module

0702H 1st word module

0703H 2nd word module

Input data of the 1st node
Low word of the
0704H
1st double-word module
High word of
0705H
the 1st double-word module
Low word of
0706H
the 2nd double-word module
High word of
0707H
the 2nd double-word module
0708H Empty 1st byte module Input data of the 2nd node

0709H Empty 1st byte module Input data of the 3rd node

Word input module: Numeric data represented by 9 to 16 bits

Double-word input module: Numeric data represented by 17 to 32 bits
Byte input module: ON/OFF data, or numeric data represented by 1 to 8
bits

3 - 37 3 - 37
3 SPECIFICATIONS
MELSEC-Q

(2) Master Function Transmit Data (address: 0900H to 09FFH/2304 to

2559)
Data to be sent to each slave node are set in this area.
Data are aligned on word boundaries of slave nodes and stored as shown below.
For double-word data, the low word is stored first and then the high word.
When the number of byte input modules is an odd number, one byte of an empty
area is inserted.
The following is an example.
<Example>
1st node - Number of byte output modules = 3
Number of word output modules = 2
Number of double-word output modules = 2
2nd node - Number of byte output modules = 1
3rd node - Number of byte output modules = 1

Buffer memory When the number of byte input

address modules is an odd number,one
byte of an empty area is inserted.
0900H 2nd byte module 1st byte module

0901H Empty 3rd byte module

0902H 1st word module

0903H 2nd word module

Output data of the 1st node
Low word of
0904H
the 1st double-word module
High word of
0905H
the 1st double-word module
Low word of
0906H
the 2nd double-word module
High word of
0907H
the 2nd double-word module
0908H Empty 1st byte module Output data of the 2nd node

0909H Empty 1st byte module Output data of the 3rd node

3 - 38 3 - 38
3 SPECIFICATIONS
MELSEC-Q

(3) I/O Address Area for Master Function (address: 0500H to 05FBH
/1280 to 1531)
This area stores the start addresses and sizes (number of words) of Master
Function Receive Data (address: 0700H to 07FFH/1792 to 2047) and Master
Function Transmit Data (address: 0900H to 09FFH/2304 to 2559) for each node.
This area can be used to check the start address of each node.
Input data start address of
0500H
1st slave node
Input data size of 1st slave
0501H
node (No. of words)
0502H Output data start address of
1st slave node
Output data size of 1st slave
0503H
node (No. of words)
0504H Input data start address of
2nd slave node

Output data size of 63rd slave

5FBH
node (No. of words)

3.4.7 Link scan time area for master function

Link scan time values are stored in this area.

(1) Present Link Scan Time (address: 05FCH /1532)

The present link scan time is stored. (Unit: ms)

(2) Minimum Link Scan Time (address 05FDH/1533)

The minimum link scan time after power-ON is stored. (Unit: ms)

(3) Maximum Link Scan Time (address 05FEH/1534)

The maximum link scan time after power-ON is stored. (Unit: ms)

3 - 39 3 - 39
3 SPECIFICATIONS
MELSEC-Q

3.4.8 Own node status area for slave function

This area stores the communication status, error information, etc. of the slave function.

(1) Slave Function Communication Status (address: 0600H/1536)

The I/O communication status of the slave function is stored.
Table 3.27 Slave function communication status
Value Name Operation
0000H Offline Initialization in progress, bus-off, or network power OFF
0040H Stop I/O communication stopped
0080H Ready Waiting to establish a connection from the master node
00C0H Operate I/O communication in progress

(a) When "No start" is set for Auto Communication Start Setting (address:
0631H)
Upon power-up, the status automatically changes from Offline (0000H) to
Stop (0040H).
When I/O Communication Request (Y11) is set to ON, the status changes
to Operate (00C0H).
Note that, until receiving an I/O communication request from the master
node, the module is placed in Ready status (0080H).

(b) When "Start" is set for Auto Communication Start Setting (address: 0631H)
Upon power-up, the status automatically changes from Offline (0000H) to
Operate (00C0H).
Note that, until receiving an I/O communication request from the master
node, the module is placed in Stop status (0040H).

(c) When a reset message is received through the network

The status automatically returns to Offline (0000H), and then changes to
Operate (00C0H).

(2) Error Information for Slave Function (address: 0601H/1537)

A code for a communication error occurred in the slave function is stored.
For error notification and a clearing method of this area, refer to Section 3.3.3 (4).
(a) High byte
An error code is stored. (Refer to Section 9.2.1.)

(b) Low byte

The number of the node (MAC ID), where an error occurred, is stored.
FEH, FFH (254, 255): Own node (QJ71DN91)
0H to 3FH (0 to 63): Node No. (MAC ID) of the node where an error
occurred.

3 - 40 3 - 40
3 SPECIFICATIONS
MELSEC-Q

3.4.9 Parameter setting area for slave function

Parameters for the slave function are set in this area.

(1) Slave Function Receive-Bytes Setting Area (address:

060EH/1550)/Slave Function Transmit-Bytes Setting Area (address:
060FH/1551)
Input/output points for the slave function are set.
For saving parameters to a flash ROM, refer to Section 8.2 (2).

Table 3.28 Slave function parameters

Buffer memory
Item Description
address (Hex.)
Slave function receive-bytes (input size) Set a size of I/O data that can be received for the slave function.
060EH
setting area (Setting range: 0 to 128 bytes, Default: 8 bytes)
Slave function transmit-bytes (output size) Set a size of I/O data that can be sent for the slave function.
060FH
setting area (Setting range: 0 to 128 bytes, Default: 8 bytes)

3 - 41 3 - 41
3 SPECIFICATIONS
MELSEC-Q

3.4.10 Communication data area for slave function

Communication data for the slave function are stored in this area.

(1) Slave Function Receive Data (address: 0B00H to 0B3FH/2816 to

2879)
Data received from the master node are stored.
The data size that is set in Slave Function Receive-Bytes Setting Area (address:
060EH) is valid.

0B00H 2nd byte 1st byte

0B01H 4th byte 3rd byte

0B02H 6th byte 5th byte

(2) Slave Function Transmit Data (address: 0C00H to 0C3FH /3072 to

3135)
Data to be sent to the master node are set in this area.
I/O data of the size, which is set in Slave Function Transmit-Bytes Setting Area
(address: 060FH), are sent.

0C00H 2nd byte 1st byte

0C01H 4th byte 3rd byte

0C02H 6th byte 5th byte

POINT
When the QJ71DN91 is used as a master node, set an even number of byte
modules. If an odd number is set and when word modules and double-word
modules are set at the same time, these word and double-word data cannot be
sent or received normally.

3 - 42 3 - 42
3 SPECIFICATIONS
MELSEC-Q

3.4.11 Own node information area

Information of the own node (QJ71DN91) is stored in this area.

(1) Model Name (address: 0620H to 0624H/1568 to 1572)

"QJ71DN91" is stored in ASCII code format.

0620H "J" "Q"

0621H "1" "7"

0622H "N" "D"

0623H "1" "9"

0624H "0" "0"

(2) Node No. (address: 0625H/1573)

The node No. of the currently operating node is stored.
00H to 3FH (Stored in binary format)

(3) Mode Switch No. (address: 0626H/1574)

The mode switch No. of the currently active mode is stored.

3 - 43 3 - 43
3 SPECIFICATIONS
MELSEC-Q

3.4.12 Hardware test area

This area is used for hardware test and communication test.

For the hardware test, refer to Section 5.4.
For the communication test, refer to Section 5.6.

(1) Hardware Test Item Area (address: 062EH/1582)

The test item No. of the hardware or communication test being executed is
stored.
Table 3.29 Hardware test items

Test item No. Meaning Description

0000H Before test Hardware test not yet started.
0001H ROM check Testing if ROM is normal.
0002H RAM check Testing if RAM is normal.
0003H Microcomputer check Testing if microcomputer is normal.
0004H CAN controller check Testing if CAN controller is normal.
FFFFH Test completion Hardware test was executed and completed normally.

Table 3.30 Communication test items

Test item No. Meaning Description

0000H Before test Communication test not yet started.
Node No. duplication Checking if any other node has the same node No. as the
0001H
check own node.
Checking if communication with one or more nodes on the
0002H Communication check
network is available.
Communication test was executed and completed
FFFFH Test completion
normally.

3 - 44 3 - 44
3 SPECIFICATIONS
MELSEC-Q

(2) Hardware Test Result Area (address: 062FH/1583)

The hardware or communication test result is stored.

Table 3.31 Hardware test results

Error code Error Action

0000H No error Hardware test completed normally.
60AAH RAM error Hardware failure. Please consult your local Mitsubishi
61AAH ROM error service center or representative, explaining a detailed
62AAH CAN controller check error description of the problem.
Network power supply
63AAH Verify that power is supplied to the network.
error
70AAH
71AAH Hardware failure. Please consult your local Mitsubishi
72AAH Microcomputer error service center or representative, explaining a detailed
73AAH description of the problem.
74AAH

Table 3.32 Communication test results

Error code Error Detail Action
Any other node on the network
Node No. • Assign unique node numbers to all nodes on
0001H has the same node No. as the
duplication error the network.
own node.
• Set the same communication speed value to all
nodes on the network.
A bus off occurred during the
0002H Bus off error • Check the overall network for disconnection of
test.
terminating resistors, DeviceNet cable length,
etc.
Network power The network power supply is
0003H • Turn ON the network power supply.
supply error OFF.
• Connect one or more nodes to the network.
• Set the same communication speed value to all
0004H Communication Data could not be sent or nodes on the network.
0005H error received correctly. • Check the overall network for disconnection of
terminating resistors, DeviceNet cable length,
etc.
Communication test was
0006H No error —
completed normally.

3 - 45 3 - 45
3 SPECIFICATIONS
MELSEC-Q

3.4.13 Parameter saving area selection area

This area is used to save parameters in the buffer memory to a flash ROM.
For the execution timing, refer to Section 7.3 (3) and 8.2 (2).

(1) Parameter Area Select Bit (address: 0630H/1584)

Select an area of the parameters that are to be saved to a flash ROM.
When clearing the parameters on the flash ROM, set 8000H. In this case,
parameters in the buffer memory are not cleared.
Default values vary depending on the operation mode. Refer to Table 3.33.

b15 to b3 b2 b1 b0
Not used

Flash ROM clear Parameters for master function

1: Clear Parameters for slave function
0: Not cleared
Auto communication start setting
1: Save
0: Not saved

Table 3.30 Default values for Parameter Area Select Bit

Mode Default value

0 to 2 (master function only) 0005H
3 to 5 (slave function only) 0006H
6 to 8 (master and slave functions) 0007H

3.4.14 Auto communication start setting area

The auto communication start setting is set in this area.

(1) Auto Communication Start Setting (address: 0631H/1585)

Set whether or not to automatically start I/O communication using the parameters
saved on the flash ROM when power is turned ON from OFF or when the CPU
module is reset.
For saving parameters to flash ROM, refer to Section 7.3 (3) and 8.2 (2).
0: Not start I/O communication automatically. (Default)
1: Start I/O communication automatically.
* : I/O communication does not start automatically when any value other than 0
and 1 is set.

3 - 46 3 - 46
3 SPECIFICATIONS
MELSEC-Q

3.5 Communication Performance

3.5.1 Transmission delay

(1) Input transmission delay

The calculation formulas for the input transmission delay are shown below.
Reading receive data by sequence
Using auto refresh
program
Maximum value LC 2 + ST [ms]
Normal value LC +ST 0.5 [ms]

LC: Communication cycle time [ms] (Refer to Section 3.5.2.)

ST: Sequence scan time [ms]

(2) Output transmission delay

The calculation formulas for the output transmission delay are shown below.
Writing transmit data by sequence
Using auto refresh
program
Maximum value LC 2 [ms] LC 2 + ST [ms]
Normal value LC [ms] LC + ST 0.5 [ms]

LC: Communication cycle time [ms] (See Section 3.5.2.)

ST: Sequence scan time [ms]

3.5.2 Communication cycle time

The communication cycle time is an interval from the time a polling or bit strobe
request is sent to a slave node until another request is sent to the same node.
The calculation formulas for the communication cycle time of each slave node are
shown below.
(1) LS<PIT: LC = LS + PIT [ms]
(2) LS>PIT: LC = LS [ms]
LC: Communication cycle time [ms]
LS: Link scan time [ms] (Refer to Section 3.5.3.)
PIT: Production inhibit time [ms] (Refer to Section 3.4.5.)

3 - 47 3 - 47
3 SPECIFICATIONS
MELSEC-Q

3.5.3 Link scan time

The link scan time represents a time during which the QJ71DN91 waits for responses
from all nodes after sending a polling request or bit-strobe requests.
The following shows the link scan time calculation formulas.
LS = (TIn + TOn + 0.097) + 0.222 BR + 1.0 [ms]
LS: Link scan time [ms]
TIn: Transmission time for data received from the n-th slave. [ms] (Refer
to (1) below.)
TOn: Transmission time for data sent to the n-th slave. [ms] (Refer to (2)
below.)
: Indicates that the values in the parentheses "( )" must be added up
for all of the slave nodes. (Except for reserved nodes)
BR: Coefficient corresponding to the baud rate
500kbaud = 1, 250kbaud = 2, 125kbaud = 4

(1) How to calculate TIn

(a) When the length of the data received from the n-th slave is 8 bytes or less
TIn = BT + BTa Receive data length (bytes) [ms]
BT, BTa: Coefficient corresponding to the baud rate (See *1.)

(b) When the length of the data received from the n-th slave is 9 bytes or more
TIn = (BT + BTa 8 + 0.190) a + {BT + BTa (b + 1) + 0.450} [ms]
BT, BTa: Coefficient corresponding to the baud rate (See *1.)
a: Result obtained by dividing the receive data length by 7
(Truncate the fractional part.)
b: Remainder obtained by dividing the receive data length by
7

(2) How to calculate TOn

(a) When the length of the data sent to the n-th slave is 8 bytes or less
TOn = BT + BTa Transmit data length (bytes) [ms]
BT, BTa: Coefficient corresponding to the baud rate (See *1.)

(b) When the length of the data sent to the n-th slave is 9 bytes or more
TOn = (BT + BTa 8 + 0.130) c + {BT + BTa (d + 1) + 1.2} [ms]
BT, BTa: Coefficient corresponding to the baud rate (See *1.)
c: Result obtained by dividing the transmit data length by 7
(Truncate the fractional part.)
d: Remainder obtained by dividing the transmit data length by 7

*1 The following shows the coefficients corresponding to the baud rates.

125kbaud 250kbaud 500kbaud
BT 0.376 0.188 0.094
BTa 0.064 0.032 0.016

3 - 48 3 - 48
 4 FUNCTIONS
MELSEC-Q

4 FUNCTIONS

This chapter explains the functions of the QJ71DN91.

4.1 Master Function (I/O Communication Function)

This function allows I/O data communication with respective slave nodes (up to 63
nodes), using the buffer memory of the QJ71DN91.
Communications of 512 bytes of inputs (up to 256 bytes per node) and 512 bytes of
outputs (up to 256 bytes per node) are available.
Master node Slave node
Programmable controller CPU QJ71DN91

I/O Communication
SET Y11 Request

4
0700H
X MasterFunction
Transmit
Receive Data
area
07FFH

0900H
Y Receive
Master Function
Transmit Data
area
09FFH

(1) Setting for I/O communication with each slave node

(a) Set the information such as connection types or I/O points in Parameters
for Master Function (address: 01D4H to 03CFH) to exchange I/O data with
each slave node.

(b) Parameters for master function are set in GX Configurator-DN or sequence

programs. (Refer to Section 7.3.)

(2) Reading/writing I/O data

(a) I/O data are stored in the following buffer memory areas.
Buffer memory Reference
Item Description
address (Hex.) section
Master function
0700H to 07FFH Data received from each slave node are stored.
receive data
3.4.6
Master function
0900H to 09FFH Data to be sent to each slave node are set.
transmit data

(b) Data transfer between the buffer memory and programmable controller
CPU devices
Reference
Transfer method Description
section
Auto refresh Configure the auto refresh settings in GX Configurator-DN. 7.4.1
MOV or FROM/TO instruction Configure the settings in sequence programs. 7.4.2

4-1 4-1
4 FUNCTIONS
MELSEC-Q

(3) Operation flow

This section explains how I/O communication is performed with each slave node.
(a) When starting I/O communication by I/O Communication Request (Y11)
Module Ready (X0F)

Auto Configuration
Request (Y15) OFF 3)
Request for Saving
Parameters to Flash
ROM (Y17) OFF 3)
4) 7)
I/O Communication
Request (Y11)
5)
I/O Communicating
(X01)
6)
Error Set Signal for
Master Function (X03)

Error Information for

Master Function
(01B1H) MOV/FROM 4
instruction
Parameters for Master 1)
Function MOV/TO Parameter
(01D4H to 03CFH) instruction check
Master Function Receive
Data (0700H to 07FFH) MOV/FROM
instruction
2)
Master Function Transmit
Data (0900H to 09FFH) MOV/TO MOV/TO
instruction instruction

1) Set parameters in Parameters for Master Function (address: 01D4H to

03CFH).
2) Set initial values of ON/OF information for each slave node in Master
Function Transmit Data (address: 0900H to 09FFH).
3) Set Auto Configuration Request (Y15) and Request for Saving
Parameters to Flash ROM (Y17) to OFF.
4) When I/O Communication Request (Y11) is set to ON, the parameters
are checked.
5) When the parameter check is succeeded, I/O communication with
each slave node is started and I/O Communicating (X01) is set to ON.
• The status of input from each slave node is stored in Master
Function Receive Data (address: 0700H to 07FFH).
• The ON/OFF information to be sent to each slave node is set in
Master Function Transmit Data (address: 0900H to 09FFH).
6) If the parameter check has failed, the ERR. LED lights up and Error
Set Signal for Master Function (X03) is set to ON. At this time, I/O
Communicating (X01) is not set to ON.
Check the error code in Error Information for Master Function
(address: 01B1H), and take corrective actions.
7) Setting I/O Communication Request (Y11) to OFF stops I/O
communication with each slave node, causing I/O Communicating
(X01) to turn OFF.

4-2 4-2
4 FUNCTIONS
MELSEC-Q

(b) When starting I/O communication automatically at power-up

Set "Start" in Automatic Communication Start Setting (address: 0631H).
2)
Module Ready (X0F)

5)
I/O Communication
Request (Y11)

I/O Communicating 3)
(X01)
4)
Error Set Signal for
Master Function (X03)

Error Information for

Master Function (01B1H) MOV/FROM
instruction
Parameters for Master
Function (01D4H to 03CFH) 1) Parameter
check
Master Function Receive
Data (0700H to 07FFH) MOV/FROM
instruction
Master Function Transmit
Data (0900H to 09FFH) MOV/TO
instruction

1) Save the following parameters to the flash ROM in advance.

• Parameters for Master Function (address: 01D4H to 03CFH)
• Auto Communication Start Setting (address: 0631H)
2) When the power is turned ON, parameters saved in the flash ROM is
loaded into the buffer memory automatically.
Module Ready (X0F) is set to ON, and the parameters are checked.
3) When the parameter check is succeeded, I/O communication with
each slave node is started and I/O Communicating (X01) is set to ON.
• The status of input from each slave node is stored in Master
Function Receive Data (address: 0700H to 07FFH).
• The ON/OFF information to each slave node is set in Master
Function Transmit Data (address: 0900H to 09FFH).
4) If the parameter check has failed, the ERR. LED lights up and Error
Set Signal for Master Function (X03) is set to ON. At this time, I/O
Communicating (X01) is not set to ON.
Check the error code in Error Information for Master Function
(address: 01B1H), and take corrective actions.
5) Setting I/O Communication Request (Y11) to ON and then OFF stops
I/O communication with each slave node, causing I/O Communicating
(X01) to turn OFF.

4-3 4-3
4 FUNCTIONS
MELSEC-Q

(4) Overview of each connection type

One of the connection types shown below can be selected for each slave node.
For available connection types, refer to the manual for each slave node.
• Polling
• Bit strobe
• Change of state
• Cyclic
I/O communications of respective connection types are explained below.

(a) Polling
Polling is a communication method by which the following steps 1) to 6) are
repeated to slave nodes.
1) The master node sends output data.
2) Step 1) triggers input data transmission from the slave node.
3) The master node sends output data.
4) Step 3) triggers input data transmission from the slave node.
5) The master node sends output data.
6) Step 5) triggers input data transmission from the slave node.

Master node

1)

4) 6)

3) 5)
2)

Slave node

4-4 4-4
4 FUNCTIONS
MELSEC-Q

(b) Bit strobe

Bit strobe is a communication method by which the following steps 1) to 4)
are repeated to each slave node.
1) Up to one bit of output information is simultaneously sent to
respective slave nodes.
2) Step 1) triggers input data transmission from the slave node.
3) Step 1) triggers input data transmission from the slave node.
4) Step 1) triggers input data transmission from the slave node.

Master node

4)
1) 3)
2)

Slave node

4-5 4-5
4 FUNCTIONS
MELSEC-Q

(c) Change of state

Change of state is a communication method by which the following steps 1)
and 2) are performed to each slave node by changes in I/O data.
No data transmission is performed unless any change is made in I/O data,
1) When output data of the master node changes, the master node
sends the data to the slave node.
2) When input data of the slave node changes, the slave node sends
the data to the master node.
The change-of-state communication does not have a concept of
communication cycle.

Master node

1) 2)

Slave node

4-6 4-6
4 FUNCTIONS
MELSEC-Q

(d) Cyclic
Cyclic is a communication method by which the following steps 1) and 2)
are repeated to each slave node at fixed intervals.
1) Data of the master node are sent to the slave node.
2) Data of the slave node are sent to the master node.
The cycle of cyclic transmission can be specified for each slave node.
Specify it to the following parameter items:
Cycle of transmission from master node: Production inhibit time
Cycle of transmission from slave node: Expected packet rate
The cyclic communication does not have a concept of communication
cycle.

Master node

1) 2)

Slave node

4-7 4-7
4 FUNCTIONS
MELSEC-Q

4.2 Master Function (Message Communication Function)

The QJ71DN91 can read or write attribute data of slave nodes using its own buffer
memory.
For details of other message communications, refer to DeviceNet Common Service
in DeviceNet Specifications (Release 2.0).
At one time, 240 bytes of message data can be transferred.
For the execution timing, refer to Section 3.3.2 (3).
(1) Get Attribute
Programmable controller CPU QJ71DN91 Slave node (MAC ID)

0110H Class
1) Message 2)
TO Comm.
Command area Instance
011FH
2) Message Comm. Attribute
SET Y12 Request
Attribute

Instance

Attribute

0120H
6) Message 3)
FROM Comm.
X02 X05 Result area
012FH Class
0130H
Message Instance
Comm.
Data area Attribute
01A7H
4) Message
communication Instance
complete
FROM Attribute
X02 X05 5)
Message Comm. Attribute
Completion Attribute

*: In DeviceNet, the areas used for reading and writing by communication

are specified by the numbers such as class ID, instance ID, and attribute
ID. For details, refer to the manual of each slave node.
1) Set command data in Message Communication Command (address:
0110H to 011FH).
2) Set Message Communication Request (Y12) to ON to read out
attribute data from the slave that is specified in the command data.
3) The attribute data of the slave node are stored in Message
Communication Data (address: 0130H to 01A7H).
4) Upon completion of reading, the processing result is stored in
Message Communication Result (address: 0120H to 012FH), and
Message Communication Completion (X02) is set to ON.
5) The slave node’s attribute data stored in Message Communication
Data (address: 0130H to 01A7H) are read out to the programmable
controller CPU.
6) If failed, Message Communication Error Signal (X05) is set to ON.
Read data in Message Communication Result (address: 0120H to
012FH) to identify the cause of the error.
4-8 4-8
4 FUNCTIONS
MELSEC-Q

(2) Set Attribute

Programmable controller CPU QJ71DN91 Slave node (MAC ID)

0110H Class
1) Message 3)
TO Comm.
Command area Instance
011FH
Attribute
0130H
2) Message
Attribute
TO Comm.
Data area
01A7H
3) Message Comm.
SET Y12 Request
Class

0120H Instance
Message
Comm.
Attribute
Result area
012FH

4) Message
communication Instance
Next complete Attribute
processing
X02 X05 5) Attribute
Message Comm.
Completion
Class

Instance

Attribute

Attribute

Instance

Attribute

1) Set command data in Message Communication Command (address:

0110H to 011FH).
2) Set attribute data in Message Communication Data (address: 0130H to
01A7H).
3) Set Message Communication Request (Y12) to ON to write the
attribute to the slave node that is specified in the command data.
4) Upon completion of writing, the processing result is stored in Message
Communication Result (address: 0120H to 012FH), and Message
Communication Completion (X02) is set to ON.
5) If failed, Message Communication Error Signal (X05) is set to ON.
Read data in Message Communication Result (address: 0120H to
012FH) to identify the cause of the error.

4-9 4-9
4 FUNCTIONS
MELSEC-Q

(3) Reading communication error information

Programmable controller CPU QJ71DN91 Slave node (MAC ID)
I/O
0110H communication Class 1
1) Message
TO Comm.
Command area Instance
011FH
Message Comm. Attribute
2)
SET Y12 Request Attribute

Slave 2) Instance
information
storage area Attribute
Attribute
0120H
5) Message Attribute
FROM Comm.
X02 X05 Result area
012FH
0130H
Message
Comm. Class
Data area
01A7H Instance
3) Message Attribute
communication
complete Attribute
FROM
X02 X05 4) Attribute
Message Comm.
Completion
Instance

Attribute

The status of each slave station is stored during I/O communication.

1) Set command data in Message Communication Command (address:

0110H to 011FH).
2) When Message Communication Request (Y12) is set to ON, the
communication error information of the relevant slave node, which has
been accumulated in the QJ71DN91, is stored in Message
Communication Data (address: 0130H to 01A7H).
3) Upon completion of reading, the processing result is stored in
Message Communication Result (address: 0120H to 012FH), and
Message Communication Completion (X02) is set to ON.
4) The slave node’s communication error information stored in Message
Communication Data (address: 0130H to 01A7H) is read out to the
programmable controller CPU.
5) If failed, Message Communication Error Signal (X05) is set to ON.
Read data in Message Communication Result (address: 0120H to
012FH) to identify the cause of the error.

4 - 10 4 - 10
4 FUNCTIONS
MELSEC-Q

4.3 Slave Function (I/O Communication Function)

This function allows I/O data communication with the master node, using the buffer
memory of the QJ71DN91.
Communications of 128 input bytes and 128 output bytes are available.
The polling method is used as the connection type.

Master node Slave node

QJ71DN91 Programmable controller CPU

I/O Communication SET Y11

Request

0B00H
Transmit Slave X
Function
Receive
Data area
0B3FH

0C00H Slave
Receive Y
Function
Transmit
Data area
0C3FH

(1) Setting for I/O communication with the master node

(a) Set the number of I/O points in Parameters for Slave Function (address:
060EH, 060FH) to exchange I/O data with the master node.
This setting is not needed if the default values (8 bytes for each) are used.

(b) Slave function parameters are set in GX Configurator-DN or sequence

programs. (Refer to Section 8.2.)

(2) Reading/writing I/O data

(a) I/O data are stored in the following buffer memory areas.
Buffer memory Reference
Item Description
address (Hex.) section
Slave function receive
0B00H to 0B3FH Data received from the master node are stored.
data
3.4.10
0C00H to Slave function transmit
Data to be sent to the master node are set.
0C3FH data

(b) Data transfer between the buffer memory and programmable controller
CPU devices
Reference
Transfer method Description
section
Auto refresh Configure the auto refresh settings in GX Configurator-DN. 8.3.1
MOV or FROM/TO instruction Configure the settings in sequence programs. 8.3.2

4 - 11 4 - 11
4 FUNCTIONS
MELSEC-Q

(3) Operation flow

This section explains how I/O communication is performed with the master node.
(a) When starting I/O communication by I/O Communication Request (Y11)
Module Ready (X0F)

Auto Configuration
Request (Y15) OFF 3)
Request for Saving
Parameters to Flash
OFF 3)
ROM (Y17)
4) 7)
I/O Communication
Request (Y11)
5)
I/O Communicating
(X01)
6)
Error Set Signal for
Slave Function (X08)

Error Information for

Slave Function (0601H) MOV/FROM
instruction
Parameters for Slave 1)
Function (060EH, 060FH) MOV/TO Parameter
instruction check

Slave Function Receive

Data (0B00H to 0B3FH) MOV/FROM
instruction
Slave Function Transmit 2)
Data (0C00H to 0C3FH) MOV/TO MOV/TO
instruction instruction

1) Set parameters in Parameters for Slave Function (address: 060EH,

060FH).
2) In Slave Function Transmit Data (address: 0C00H to 0C3FH), set initial
values of ON/OFF information to be sent to the master node.
3) Set Auto Configuration Request (Y15) and Request for Saving
Parameters to Flash ROM (Y17) to OFF.
4) When I/O Communication Request (Y11) is set to ON, the parameters
are checked.
5) When the parameter check is succeeded, I/O communication with the
master node is started and I/O Communicating (X01) is set to ON.
Note that, until receiving an I/O communication request from the
master node, the module waits for connection establishment.
• Data sent from the master node are stored in Slave Function
Receive Data (address: 0B00H to 0B3FH).
• The ON/OFF information to be sent to the master node is set in
Slave Function Transmit Data (address: 0C00H to 0C3FH).
6) If the parameter check has failed, the ERR. LED lights up and Error
Set Signal for Slave Function (X08) is set to ON. At this time, I/O
Communicating (X01) is not set to ON.
Check the error code in Error Information for Slave Function (address:
0601H), and take corrective actions.
7) Setting I/O Communication Request (Y11) to OFF stops I/O
communication with the master node, causing I/O Communicating
(X01) to turn OFF.

4 - 12 4 - 12
4 FUNCTIONS
MELSEC-Q

(b) When starting I/O communication automatically at power-up

Set "Start" in Automatic Communication Start Setting (address: 0631H).
2)
Module Ready (X0F)

5)
I/O Communication
Request (Y11)
3)
I/O Communicating
(X01)
4)
Error Set Signal for
Slave Function (X08)

Error Information for

Slave Function (0601H) MOV/FROM
instruction
Parameters for Slave
Function (060EH, 060FH) Parameter
1) check

Slave Function Receive

Data (0B00H to 0B3FH) MOV/FROM
instruction

Slave Function Transmit

Data (0C00H to 0C3FH) MOV/TO
instruction

1) Save the following parameters to the flash ROM in advance.

• Parameters for Slave Function (address: 060EH, 060FH)
• Auto Communication Start Setting (address: 0631H)
2) When the power is turned ON, parameters saved in the flash ROM is
loaded into the buffer memory automatically.
Module Ready (X0F) is set to ON, and the parameters are checked.
3) When the parameter check is succeeded, I/O communication with the
master node is started and I/O Communicating (X01) is set to ON.
Note that, until receiving an I/O communication request from the
master node, the module waits for connection establishment.
• Data sent from the master node are stored in Slave Function
Receive Data (address: 0B00H to 0B3FH).
• The ON/OFF information to be sent to the master node is set in
Slave Function Transmit Data (address: 0C00H to 0C3FH).
4) If the parameter check has failed, the ERR. LED lights up and Error
Set Signal for Slave Function (X08) is set to ON. At this time, I/O
Communicating (X01) is not set to ON.
Check the error code in Error Information for Slave Function (address:
0601H), and take corrective actions.
5) Setting I/O Communication Request (Y11) to ON and then OFF stops
I/O communication with the master node, causing I/O Communicating
(X01) to turn OFF.

4 - 13 4 - 13
5 SETUP AND PREPARATION
MELSEC-Q

5 SETUP AND PREPARATION

This chapter describes the procedures to be followed before starting the system that
includes the QJ71DN91.

5.1 Pre-operation Procedures

5.1.1 When using the master function

Start

Perform hardware test. (Mode 9) (See Section 5.4.)

Set node No. (See Section 5.3.2.)

Set mode to 0, 1, or 2. (See Section 5.3.3.)

Connect DeviceNet cable to QJ71DN91. (See Section 5.5.)

Not use
Use GX Configurator-DN?

Use
5

Auto configuration (See Section 7.3.1 (1).) *1 Auto configuration (See Section 7.3.1 (1).) *1
Execute auto configuration. Not needed when setting Create sequence program for executing auto
parameters for master function manually. configuration. Not needed when setting parameters for
master function manually.

Parameters for master function (See Section 7.3.1 (2).) Parameters for master function (See Section 7.3.2 (2).)
Set parameters for master function. Create sequence program for setting master function
parameters.

Auto communication start setting (See Section 7.3.1 (1), (2).) Auto communication start setting (See Section 7.3.2 (3).)
Set auto communication start setting. Not needed when starting Create sequence program for auto communication
I/O communication by I/O Communication Request (Y11). start setting. Not needed when starting I/O
communication by I/O Communication Request (Y11).

Saving parameters to flash ROM (See Section 7.3.1 (3).) Saving parameters to flash ROM (See Section 7.3.2 (3).)
Save parameters to flash ROM. Create sequence program for saving parameters to
flash ROM.

Refresh setting (See Section 7.4.1.) Refresh setting (See Section 7.4.2.)
Configure auto refresh settings. Write intelligent Create sequence program for refresh.
function module parameters to CPU module.

Programming for control (See Section 7.4.1.) Programming for control (See Section 7.4.2.)

Create sequence program for control. After writing it to Create sequence program for control. After writing it to
programmable controller, reset CPU module. programmable controller, reset CPU module.

Failed Failed
Test run Test run
OK OK
Set Request for Saving Parameters to Flash ROM
(Y17) to ON to save parameters to flash ROM.

Operation
*1: Check that power supplies to slave nodes and network are ON and the wiring is correct.

5-1 5-1
 5 SETUP AND PREPARATION
MELSEC-Q

5.1.2 When using the slave function

Start

Perform hardware test. (Mode 9) (See Section 5.4.)

Set node No. (See Section 5.3.2.)

Set mode to 3, 4, or 5. (See Section 5.3.3.)

Connect DeviceNet cable to QJ71DN91. (See Section 5.5.)

Not use
Use GX Configurator-DN?

Use

Parameters for slave function (See Section 8.2.1 (1).) Parameters for slave function (See Section 8.2.2 (1).)
Set parameters for slave function. Create sequence program for setting parameters for
Not needed unless I/O points for slave function are slave function. Not needed unless I/O points for slave
changed. function are changed.

Auto communication start setting (See Section 8.2.1 (1).) Auto communication start setting (See Section 8.2.2 (2).)

5 Set auto communication start setting. Not needed when starting

I/O communication by I/O Communication Request (Y11).
Create sequence program for auto communication start
setting. Not needed when starting I/O communication
by I/O Communication Request (Y11).

Saving parameters to flash ROM (See Section 8.2.1 (2).) Saving parameters to flash ROM (See Section 8.2.2 (2).)
Save parameters to flash ROM. Create sequence program for saving parameters to
flash ROM.

Refresh setting (See Section 8.3.1.) Refresh setting (See Section 8.3.2.)
Configure auto refresh settings. Write intelligent Create sequence program for refresh.
function module parameters to CPU module.

Programming for control (See Section 8.3.1.) Programming for control (See Section 8.3.2.)

Create sequence program for control. After writing it to Create sequence program for control. After writing it to
programmable controller, reset CPU module. programmable controller, reset CPU module.

Failed Failed
Test run Test run
OK OK
Set Request for Saving Parameters to Flash ROM
(Y17) to ON to save parameters to flash ROM.

Operation

5-2 5-2
5 SETUP AND PREPARATION
MELSEC-Q

5.1.3 When using both the master and slave functions

Refer to Chapter 7 for programming for the master function, and Chapter 8 for
programming for the slave function.
Start

Perform hardware test. (Mode 9) (See Section 5.4.)

Set node No. (See Section 5.3.2.)

Set mode to 6, 7, or 8. (See Section 5.3.3.)

Connect DeviceNet cable to QJ71DN91. (See Section 5.5.)

Not use
Use GX Configurator-DN?

Use

Auto configuration *1 Auto configuration *1

Execute auto configuration. Not needed when setting Create sequence program for executing auto
parameters for master function manually. configuration. Not needed when setting parameters for
master function manually.

Parameters for master function Parameters for master function

Set parameters for master function. Create sequence program for setting parameters for
master function.

Parameters for slave function Parameters for slave function

Set parameters for slave function. Create sequence program for setting parameters for
Not needed unless I/O points for slave function are slave function. Not needed unless I/O points for slave
changed. function are changed.

Auto communication start setting Auto communication start setting

Set auto communication start setting. Not needed when starting Create sequence program for auto communication
I/O communication by I/O Communication Request (Y11). start setting. Not needed when starting I/O
communication by I/O Communication Request (Y11).

Saving parameters to flash ROM Saving parameters to flash ROM

Save parameters to flash ROM. Create sequence program for saving parameters to
flash ROM.

Refresh setting Refresh setting

Configure auto refresh settings. Write intelligent Create sequence program for refresh.
function module parameters to CPU module.

Programming for control Programming for control

Create sequence program for control. After writing it to Create sequence program for control. After writing it to
programmable controller, reset CPU module. programmable controller, reset CPU module.

Failed Failed
Test run Test run
OK OK
Set Request for Saving Parameters to Flash ROM
(Y17) to ON to save parameters to flash ROM.

Operation

*1: Check that power supplies to slave nodes and network are ON and the wiring is correct.

5-3 5-3
5 SETUP AND PREPARATION
MELSEC-Q

5.2 Implementation and Installation

This section describes handling precautions to be taken from unpacking to mounting

the QJ71DN91.
For more details, refer to the User's Manual of your programmable controller CPU.

5.2.1 Handling precautions

(1) Do not drop the module casing or connector, or do not subject it to strong
impact.

(2) Do not remove the printed-circuit board of the module from its case.
Doing so may cause a failure.

(3) Be careful to prevent foreign matter such as wire chips from entering the
module.
It may cause a fire, failure or malfunction.

(4) The top surface of the module is covered with a protective film to prevent
foreign matter such as wiring chips from entering the module during wiring.
Do not remove this film until wiring is complete.
Before starting the system, remove the film to release heat.

(5) Tighten the fixing screws within the following torque ranges.
A loose screw may cause a short circuit, failure or malfunctions.
Screw Tightening torque range
*1
Module fixing screw (usually not required) (M3) 0.36 to 0.48 N•m
DeviceNet connector screw 0.353 to 0.480 N• m
DeviceNet connector wiring screw 0.608 to 0.823 N• m
*1: The module can be easily mounted to a base unit, using the hook on the upper part of
the module. However, it is recommended to secure it with the module fixing screws
when used in an environment where constant vibrations may occur.

(6) Be sure to insert the module fixing projection into the hole in the base unit.
Then, securely mount the module.
Incorrect module mounting may cause the module to malfunction, fail or fall
off.

5.2.2 Installation environment

For more details on the installation environment, refer to the User's Manual of your
programmable controller CPU.

5-4 5-4
5 SETUP AND PREPARATION
MELSEC-Q

5.3 Part Names and Settings

This section describes the part names, LED indications, and respective switch settings
of the QJ71DN91.
QJ71DN91
RUN MS

NS
ERR.

NODE ADDRESS

5 6
4
2 3

7 8

X10
9
01
Node No.
5 6 switches
4
2 3

X1
7 8

MODE/DR 9
0 : M/125 01
1 : M/250
2 : M/500 M 78 9
4 56

AB E

3 : S/125 O
Mode
CD

4 : S/250 D
23

switch
5 : S/500 E
F01
6 : D/125
7 : D/250
8 : D/500

DeviceNet
connector

QJ71DN91

5-5 5-5
5 SETUP AND PREPARATION
MELSEC-Q

5.3.1 LED indications

The following explains the names of the LEDs on the QJ71DN91 and their
indications in mode 0 to 8.
For the LED indications in mode 9 to C, refer to Section 5.4 Hardware Test or 5.6
Communication Test.

Table 5.1 LED names and indications

LED name Color LED status
QJ71DN91
RUN MS
RUN Green On: Operating normally
Off: Watchdog timer error
NS
ERR. ERR. Red On: Node No. setting error
Flashing: Node No. switch or mode switch was changed during
module operation.
MS Green On: Communication is available.
Flashing: Parameter error
NS Green On: Communication in progress
Flashing: Waiting for communication (waiting for I/O
communication request from programmable controller
CPU, or waiting for communication start of the target
module)
Red On: Node No. duplication or bus off error (communication line
error)
Flashing: <In master function mode> A node that does not
respond exists.
<In slave function mode> Communication with the
master node is interrupted.
Green/Red Off: Power to the network is not being supplied.

5-6 5-6
5 SETUP AND PREPARATION
MELSEC-Q

5.3.2 Node No. switches

The following explains the node No. switches of the QJ71DN91.

Table 5.2 Node No. switches

Name Description
5 Node No. switch Used to set the node No. of the module. (Factory default: 0)
2 3

X10 Do not change the node No. during module operation since it
is recognized when the module is powered ON or reset.
0

5
If changed, the ERR. LED will flash.
2 3

X1
0
Setting range: 0 to 63 (The Err. LED will flash if any other than
these is set.)
* The node No. must be unique.

POINT
(1) If the module is used as both a master and slave node, the same node No. is
applied to the master and slave functions.
(2) Since lower numbers have priority over higher numbers, set a lower number to
a master node.

5.3.3 Mode switch

The following explains the mode switch of the QJ71DN91.

Table 5.3 Mode switch

Name Setting Function Description
8
M Mode switch 0 Master function Operates as a master node, at communication speed of 125k baud
O
C
4

D (factory default).
E 0
1 Operates as a master node, at communication speed of 250k baud.
2 Operates as a master node, at communication speed of 500k baud.
3 Slave function Operates as a slave node, at communication speed of 125k baud.
4 Operates as a slave node, at communication speed of 250k baud.
5 Operates as a slave node, at communication speed of 500k baud.
6 Master and slave Operates as a master and slave node, at communication speed of 125k baud.
7 functions * Operates as a master and slave node, at communication speed of 250k baud.
8 Operates as a master and slave node, at communication speed of 500k baud.
9 Hardware test Performs the ROM/RAM check and self-loopback test.
A Communication Performs the transmit/receive test, at communication speed of 125k baud.
B test Performs the transmit/receive test, at communication speed of 250k baud.
C Performs the transmit/receive test, at communication speed of 500k baud.
D to F Use prohibited -

* Select a mode between 6 and 8 when using both the master and slave functions.

5-7 5-7
5 SETUP AND PREPARATION
MELSEC-Q

5.4 Hardware Test

The hardware test checks whether or not the module operates normally in stand-
alone condition. It performs ROM check, RAM check, self-loopback test, etc.
Be sure to perform the hardware test before building a system.
For the test related to DeviceNet communications, refer to Section 5.6
Communication Test and perform it after wiring.

Execute the hardware test in the following sequence:

Start

Connect network power supply and power

it ON. (See Section 5.5.)

Set mode to 9. (See Section 5.3.3.)

By powering ON from OFF or resetting CPU

module, test starts.

During test, MS LED flashes green.

RUN MS

NS
ERR.

When completed normally, MS LED stays

ON green. RUN MS

NS
ERR.

When failed, MS LED turns OFF and ERR.

LED turns ON.
RUN MS

NS
ERR.

Failed
Test result?

Normal completion
End Check error code in Hardware Test Result
Area (address: 062FH), and take corrective
actions.

5-8 5-8
5 SETUP AND PREPARATION
MELSEC-Q

5.5 Wiring

(1) Connecting a DeviceNet cable

The following explains how to connect a DeviceNet cable to the QJ71DN91.

V+ (red)

CAN_H (white)

Shield (drain wire)

CAN_L (blue)

V- (black)

The figure above shows the QJ71DN91's DeviceNet connector.

Stickers in the colors of respective wires are put on the connector.
Connect the DeviceNet cable correctly so that the colors of the wires will match
those of the stickers.

(2) Grounding the network

The DeviceNet network should be grounded at a single point, near the center of
the network.
Connect the cable shield (drain wire) to the ground terminal of the power supply
unit, and ground it to the protective ground conductor.
If multiple power supply units exist on the network, ground only the power supply
unit near the center of the network, and do not ground others.
Also, in such a case, use power supply taps.
Power supply tap
Power supply tap (near the center of the network) Power supply tap

V+
CAN_H
Shield (drain wire)
CAN_L
V-

FG V+ V- FG V+ V- FG V+ V-
Power supply Power supply Power supply
unit unit unit

5-9 5-9
5 SETUP AND PREPARATION
MELSEC-Q

5.6 Communication Test

The transmission and reception tests are performed after connecting the QJ71DN91
and other DeviceNet devices with DeviceNet cables.
There is no restriction on the node No. setting of the communication target.

Execute the test in the following sequence:

Start

Connect QJ71DN91 and other DeviceNet

devices with DeviceNet cables. (See Section 5.5.)

Set same communication speed as those of other

DeviceNet devices. Set mode to A, B or C.
(See Section 5.3.3.)

Turn ON network power supply and other

DeviceNet devices.

By powering ON from OFF or resetting CPU

module, test starts.

During test, MS LED flashes green.

RUN MS

NS
ERR.
When completed normally, MS LED stays
ON green.
RUN MS

NS
ERR.
When failed, MS LED turns OFF and ERR.
LED turns ON.
RUN MS

NS
ERR.

Failed
Test result?

Normal completion
End Check error code in Hardware Test Result
Area (address: 062FH), and take corrective
actions.

5 - 10 5 - 10
5 SETUP AND PREPARATION
MELSEC-Q

5.7 Precautions for Network Power Supply

This section describes the precautions for network power supply.

5.7.1 Network power supply unit position

Follow the procedure below to determine the position to install the network power
supply unit.
1) Calculate the current consumption of each node on the network.
2) Measure the total length of the network.
3) Referring to Tables 5.4 and 5.5, find a maximum current value corresponding to
the network length and the cable type used.
4) If the current value calculated at step 1) is less than the one obtained at step 3),
any of the positions described on the next page can be used.
5) If the current value calculated at step 1) exceeds the one obtained at step 3),
install the network power supply unit near the center of the network referring to the
next page, and check if power can be supplied to all nodes.
6) As a result of step 5), if power cannot be supplied to all nodes, increase the
number of network power supply units.

Table 5.4 Maximum current capable of being supplied to master/slave

nodes, for each length of the network using thick cables
Network length (m) 0 25 50 100 150 200 250 300 350 400 450 500
Maximum current (A) 8.00 8.00 5.42 2.93 2.01 1.53 1.23 1.03 0.89 0.78 0.69 0.63

Table 5.5 Maximum current capable of being supplied to master/slave

nodes, for each length of the network using thin cables
Network length (m) 0 10 20 30 40 50 60 70 80 90 100
Maximum current (A) 3.00 3.00 3.00 2.06 1.57 1.26 1.06 0.91 0.80 0.71 0.64

POINT
Use a network power supply unit of which the current capacity is more than the
required total current consumption.
If the current capacity is insufficient, use of multiple power supplies is possible.
However, use power supply taps in such a case.

5 - 11 5 - 11
5 SETUP AND PREPARATION
MELSEC-Q

5.7.2 Network power supply unit position and current capacity calculation

This section describes where to install the network power supply unit and how to
calculate the current capacity.
(1) Connecting the network power supply unit to one end of the network
When the network is 200m long in total and uses thick cables, the current
capacity can be calculated as shown below.
Network power
supply unit

Terminating Terminating
resistor resistor

Master node Slave node Slave node Slave node Slave node
0.1A 0.15A 0.05A 0.25A 0.1A

200m

Total power supply distance = 200m

Total current capacity = 0.1A + 0.15 + 0.05A + 0.25A + 0.1A = 0.65A
Max. current capacity available for total thick cable length of 200m (See Table
5.4.) = 1.53A
Therefore, this configuration allows power supply to all nodes.

(2) Connecting the network power supply unit to the center of the
network
When the network uses thick cables, the current capacity can be calculated as
shown below.
In this case, the network power supply unit can supply twice the current
compared to when it is connected to the end of the network.
Network power
supply unit

Terminating Terminating
resistor resistor

Master node Slave node Slave node Slave node Slave node Slave node
0.1A 0.25A 0.2A 0.15A 0.25A 0.15A

120m 120m

Power supply distance on the left side = Power supply distance on the right side
= 120m
Total current capacity of the left side = 0.1A + 0.25A + 0.2A = 0.55A
Total current capacity of the right side = 0.15A + 0.25A + 0.15A = 0.55A
Max. current capacity available for thick cable length of 120m (See Table 5.4.) =
approx. 2.56A
(Straight-line approximation between 100m and 150m)
Therefore, this configuration allows power supply to all nodes.
5 - 12 5 - 12
5 SETUP AND PREPARATION
MELSEC-Q

(3) When the network power supply current capacity is insufficient

In the case where the network power supply unit is connected to the following
network that uses thick cables:

Network power
supply unit

Terminating Terminating
resistor resistor

Master node Slave node Slave node Slave node Slave node Slave node
1.1A 1.25A 0.5A 0.25A 0.25A 0.85A

120m 120m

Power supply distance on the left side = Power supply distance on the right side
= 120m
Total current capacity of the left side = 1.1A + 1.25A + 0.5A = 2.85A
Total current capacity of the right side = 0.25A + 0.25A + 0.85A = 1.35A
Max. current capacity available for thick cable length of 120m (See Table 5.4.) =
approx. 2.56A
(Straight-line approximation between 100m and 150m)

In this configuration, the current capacity on the left side is insufficient.

In this case, move the network power supply unit in the direction of insufficient
current capacity (to the left in the figure above).

Network power
supply unit

Terminating Terminating
resistor resistor

Master node Slave node Slave node Slave node Slave node Slave node
1.1A 1.25A 0.5A 0.25A 0.25A 0.85A

100m 140m

Total power supply distance on the left side = 100m

Total power supply distance on the right side = 140m
Total current capacity of the left side = 1.1A + 1.25A = 2.35A
Total current capacity of the left side = 0.5A + 0.25A + 0.25A + 0.85A = 1.85A
Max. current capacity available for thick cable length of 100m (See Table 5.4.) =
approx. 2.93A
Max. current capacity available for thick cable length of 140m (See Table 5.4.) =
approx. 2.19A
(Straight-line approximation between 100m and 150m)

As a result of shifting the network power supply unit, it is able to supply power to
all nodes.
5 - 13 5 - 13
5 SETUP AND PREPARATION
MELSEC-Q

(4) When using both trunk and drop lines

The current capacity is calculated as shown below when the network power
supply unit is connected to a network that has a 200m-long trunk line of thick
cables and a 6m-long drop line of a thin cable.

Network power
supply unit

Terminating Terminating
resistor resistor

Master node Slave node Slave node Slave node

1.0A 0.15A 0.05A 0.25A

Slave node
0.1A

200m

Total thick-cable length = 200m

Total drop-line length = 6m
Total current capacity = 0.5A + 0.15A + 0.05A + 0.25A + 0.1A = 1.05A
Max. current capacity available for thick cable length of 200m (See Table 5.4.) =
1.53A
Max. current capacity available for thin cable length of 6m (See Table 5.6.) =
0.75A
Total current consumed by devices connected to drop line = 0.1A

Therefore, this configuration allows power supply to all nodes.

Table 5.6 Maximum current capacity for each drop line length
Drop line length (m) 0.30 0.90 1.50 2.25 3.00 4.50 6.00
Max. current (A) 3.00 3.00 3.00 2.00 1.50 1.00 0.75

5 - 14 5 - 14
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

6 UTILITY PACKAGE (GX Configurator-DN)

6.1 Functions of the Utility Package

Table 6.1 lists the functions of the utility package.

Table 6.1 Utility package (GX Configurator-DN) function list

Reference
Function Description
section
(1) The QJ71DN91’s buffer memory is configured for automatic refresh.
(2) Values set for auto refresh and stored in the QJ71DN91’s buffer memory are
Auto refresh 6.4
automatically read out when the END instruction is executed in the programmable
controller CPU.
The buffer memory and I/O signals of the QJ71DN91 are monitored or tested.
Monitoring/test 6.5
Auto configuration and parameter backup are also available.
Flash ROM setting The data to be set to the flash ROM are edited online. 6.6

6-1 6-1
 6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

6.2 Installing and Uninstalling the Utility Package

For how to install or uninstall the utility package, refer to "Method of installing the
MELSOFT Series" included in the utility package.

6.2.1 Handling precautions

The following explains the precautions on using the GX Configurator-DN.

(1) For safety

Since GX Configurator-DN is add-in software for GX Developer, read "Safety
Precautions" and the basic operating procedures in the GX Developer Operating
Manual.

(2) About installation

GX Configurator-DN is add-in software for GX Developer Version 4 or later.
Therefore, GX Configurator-DN must be installed on the personal computer that
has already GX Developer Version 4 or later installed.

(3) Screen error of Intelligent function module utility

Insufficient system resource may cause the screen to be displayed
inappropriately while using the Intelligent function module utility.
If this occurs, close the Intelligent function module utility, GX Developer
(program, comments, etc.), and other applications, and then start GX Developer
6 and Intelligent function module utility again.

(4) To start the Intelligent function module utility

(a) In GX Developer, select "QCPU (Q mode)" for PLC series and specify a
project.
If any other than "QCPU (Q mode)" is selected for PLC series, or if no
project is specified, the Intelligent function module utility will not start.

(b) Multiple Intelligent function module utilities can be started.

However, [Open parameters] and [Save parameters] operations under
[Intelligent function module parameter] are allowed for one Intelligent
function module utility only. Only the [Monitor/test] operation is allowed for
the other utilities.

(5) Switching between two or more Intelligent function module utilities

When two or more Intelligent function module utility screens cannot be displayed
side by side, select a screen to be displayed on the top of others using the task
bar.

6-2 6-2
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

(6) Number of parameters that can be set in GX Configurator-DN

When multiple intelligent function modules are mounted, the number of
parameters set must not exceed the following limit.
When intelligent function modules Maximum number of parameter settings
are installed to: Initial setting Auto refresh setting
Q00J/Q00/Q01CPU 512 256
Q02/Q02H/Q06H/Q12H/Q25HCPU 512 256
Q12PH/Q25PHCPU 512 256
Q02UCPU 2048 1024
Q03UD/Q04UDH/Q06UDHCPU 4096 2048

For example, if multiple intelligent function modules are installed to the

Q25HCPU, configure the settings in GX Configurator so that the number of
parameters set for all the intelligent function modules does not exceed the limit of
the Q25HCPU. Calculate the total number of parameter settings separately for
the initial setting and for the auto refresh setting.
The number of parameters that can be set for one module in GX Configurator-DN
is as shown below.
Target module Initial setting Auto refresh setting
QJ71DN91 0 (Not used) 18 (Max.)

Example) Counting the number of parameter settings in Auto refresh setting

This one row is counted as one setting.

Blank rows are not counted.
Count up all the setting items on this
screen, and add the total to the number
of settings for other intelligent
function modules to get a grand total.

6-3 6-3
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

6.2.2 Operating environment

This section explains the operating environment of the personal computer that runs GX
Configurator-DN.
Item Description
Installation (Add-in) target*1 Add-in to GX Developer Version 4 (English version) or later*2
®
Computer Windows -based personal computer
CPU Refer to the following table "Operating system and performance required for personal
Required memory computer".
Hard disk For installation 65 MB or more
space*3 For operation 10 MB or more
Display 800 600 dots or more resolution*4
® ®
Microsoft Windows 95 Operating System (English version)
® ®
Microsoft Windows 98 Operating System (English version)
® ®
Microsoft Windows Millennium Edition Operating System (English version)
® ®
Microsoft Windows NT Workstation Operating System Version 4.0 (English version)
® ®
Microsoft Windows 2000 Professional Operating System (English version)
® ®
Microsoft Windows XP Professional Operating System (English version)
Operating system ® ®
Microsoft Windows XP Home Edition Operating System (English version)
® ®
Microsoft Windows Vista Home Basic Operating System (English version)
® ®
Microsoft Windows Vista Home Premium Operating System (English version)
® ®
Microsoft Windows Vista Business Operating System (English version)
® ®
Microsoft Windows Vista Ultimate Operating System (English version)
® ®
Microsoft Windows Vista Enterprise Operating System (English version)
*1: Install GX Configurator-DN in GX Developer Version 4 or higher in the same language.
GX Developer (English version) and GX Configurator-DN (Japanese version) cannot be used in combination, and GX
Developer (Japanese version) and GX Configurator-DN (English version) cannot be used in combination.
*2: GX Configurator-DN is not applicable to GX Developer Version 3 or earlier.
®
*3: At least 15GB is required for Windows Vista .
®
*4: Resolution of 1024 768 dots or more is recommended for Windows Vista .

Operating system and performance required for personal computer

Performance required for personal computer
Operating system
CPU Memory
® ®
Windows 95 Pentium 133MHz or more 32MB or more
® ®
Windows 98 Pentium 133MHz or more 32MB or more
® ®
Windows Me Pentium 150MHz or more 32MB or more
® ®
Windows NT Workstation 4.0 Pentium 133MHz or more 32MB or more
® ®
Windows 2000 Professional Pentium 133MHz or more 64MB or more
® ®
Windows XP Professional Pentium 300MHz or more 128MB or more
® ®
Windows XP Home Edition Pentium 300MHz or more 128MB or more
® R
Windows Vista Home Basic Pentium 1GHz or more 1GB or more
® R
Windows Vista Home Premium Pentium 1GHz or more 1GB or more
® R
Windows Vista Business Pentium 1GHz or more 1GB or more
® R
Windows Vista Ultimate Pentium 1GHz or more 1GB or more
® R
Windows Vista Enterprise Pentium 1GHz or more 1GB or more

6-4 6-4
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

POINT
• The functions shown below are not available for Windows XP and Windows
R

®
Vista .
If any of the following functions is attempted, this product may not operate
normally.
Start of application in Windows compatible mode
R

Fast user switching

Remote desktop
Large fonts (Details setting of Display Properties)
®
Also, 64-bit version Windows XP and Windows Vista are not supported.
R

• Use a USER authorization or higher in Windows Vista .

®

6-5 6-5
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

6.3 Utility Package Operation

6.3.1 Common utility package operations

(1) Control keys

Special keys that can be used for operation of the utility package and their
applications are shown in the table below.
Key Application
Cancels the current entry in a cell.
Esc
Closes the window.
Tab Moves between controls in the window.

Used in combination with the mouse operation to select

Ctrl
multiple cells for test execution.
Deletes the character where the cursor is positioned.
Delete When a cell is selected, clears all of the setting contents in
the cell.

Back
Space Deletes the character where the cursor is positioned.

Moves the cursor.

Page
up Moves the cursor one page up.

Page
Down Moves the cursor one page down.

Enter Completes the entry in the cell.

6-6 6-6
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

(2) Data created with the utility package

The following data or files that are created with the utility package can be also
handled in GX Developer. Figure 6.1 shows respective data or files are handled
in which operation.

<Intelligent function module parameter>

(a) This represents the data created in Auto refresh setting, and they are
stored in an intelligent function module parameter file in a project created
by GX Developer.
Project
Program
Parameter
PLC Parameter
Network Parameter
Intelligent Function Module Parameter

(b) Steps 1) to 3) shown in Figure 6.1 are performed as follows:

1) From GX Developer, select:
[Project] [Open project] / [Save]/ [Save as]
2) From the module selection screen of the utility, select:
[Intelligent function module parameter] [Open parameters] / [Save
parameters]
3) From GX Developer, select:
[Online] [Read from PLC] / [Write to PLC] "Intelligent function
module parameters"
Or, from the module selection screen of the utility,
[Online] [Read from PLC] / [Write to PLC]

6-7 6-7
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

<Flash ROM data>

(a) This means the data set in Flash ROM setting and they can be stored in
any directory separately from projects of GX Developer.

(b) Steps 4) and 5) in Figure 6.1 are performed as follows:

4) The operation can be executed from the Flash ROM setting screen or
Monitor/Test screen of the utility.
"Flash ROM Setting" screen Load file / Save file
"Monitor/Test" screen Load file / Save file
5) The operation can be executed from the Monitor/Test screen of the
utility.
"Monitor/Test" screen Read from module / Write to module

<Text files>
(a) A text file can be created by clicking the Make text file button on the initial
setting, Auto refresh setting, or Monitor/Test screen.
The text files can be utilized to create user documents.
GX Developer/
GX Configurator-DN Disk
Project Project
1)

A A
2)

B Personal
B
4) computer

QCPU 3) 5) QJ71DN91
QJ71DN91
Q25HCPU RUN MS

NS
MODE ERR.

RUN
ERR.
USER NODE ADDRESS

X10
5 A: Intelligent function module parameters
BOOT 0

5
B: Flash ROM data.
X1
C: Data saved by "Make text file"
A
0

B
M
O
4

D
E 0

USB

RS-232
QJ71DN91

Figure 6.1 Correlation chart for data created with the utility package

6-8 6-8
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

6.3.2 Operation overview

GX Developer screen

[Tools] - [Intelligent function utility] - [Start]

Screen for selecting a target

intelligent function module

Enter "Start I/O No.", and select "Module type"

Refer to Section 6.3.3. and "Module model name".
1)
Auto refresh

Auto refresh setting screen

Refer to Section 6.4.

6-9 6-9
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

1)
[Online] - [Monitor/Test] [Tools] - [Flash ROM setting]

Selecting monitor/test module screen Flash ROM setting

Select "Module type"

Select and "Module model name."

Monitor/Test Select a module to be monitored/tested.

Monitor/Test screen Flash ROM setting screen

Refer to Section 6.6.

Refer to Section 6.5.

6 - 10 6 - 10
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

6.3.3 Starting the Intelligent function module utility

[Purpose]
Starting the Intelligent function module utility from GX Developer, activate the
screen for selecting a module to set parameters.
From this screen, the screen for configuring auto refresh of the QJ71DN91, and
the screen for selecting a module to be monitored/tested can be started.

[Operating procedure]
[Tools] [Intelligent function utility] [Start]

[Setting screen]

[Explanation of items]
(1) Activation of other screens
(a) Auto refresh setting screen
"Start I/O No.* " "Module type" "Module model name"
Auto refresh

(b) Monitor/test module selection screen

[Online] [Monitor/Test]
* Enter the start I/O No. in hexadecimal.

(2) Command buttons

Delete Deletes the initial setting and auto refresh setting of the selected
module.
Exit Closes this screen.

6 - 11 6 - 11
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

(3) Menu bar

(a) File menu
Intelligent function module parameters of the project opened by GX
Developer are handled.
[Open parameters]: Reads a parameter file.
[Close parameters]: Closes the parameter file. If any data are modified, a
dialog asking for file saving will appear.
[Save parameters]: Saves the parameter file.
[Delete parameters]: Deletes the parameter file.
[Exit]: Closes the current screen.

(b) Online menu

[Monitor/Test]: Activates the Select monitor/test module screen.
[Read from PLC]: Reads intelligent function module parameters from the
CPU module.
[Write to PLC]: Writes intelligent function module parameters to the CPU
module.

POINT
(1) Saving intelligent function module parameters in a file
Since intelligent function module parameters cannot be saved in a file by the
project saving operation of GX Developer, save them on the shown module
selection screen.
(2) Reading/writing intelligent function module parameters from/to a
programmable controller using GX Developer
(a) Intelligent function module parameters can be read from and written into
a programmable controller after having been saved in a file.
(b) Set a target programmable controller CPU in GX Developer:
[Online] [Transfer setup].
(3) Checking the required utility
While the start I/O is displayed on the Intelligent function module utility setting
screen, "*" may be displayed for the model name.
This means that the required utility has not been installed or the utility cannot
be started from GX Developer.
Check the required utility, selecting [Tools] - [Intelligent function utility] - [Utility
list...] in GX Developer.

6 - 12 6 - 12
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

6.4 Auto Refresh

[Purpose]
Configure the QJ71DN91's buffer memory for automatic refresh.
This auto refresh setting eliminates the need for reading and writing by sequence
programs.

[Operating procedure]
"Start I/O No.* " "Module type" "Module model name" Auto refresh
* Enter the start I/O No. in hexadecimal.

[Setting screen]

POINT
Do not edit or write any data that were set by GX Configurator-DN Version 1.15R or
later with or to GX Configurator-DN Version 1.14Q or earlier.
Doing so will corrupt the set data.
If a numerical value is entered accidentally, press Cancel .

6 - 13 6 - 13
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

[Setting items]
Reference
Item Buffer memory address (Hex.)
section
Master Function Communication Status 01B0H
Error Information for Master Function 01B1H
3.4.3
Bus Error Counter 01B2H
Bus Off Counter 01B3H
Node Configuration Status 01B4H to 01B7H
Node Communication Status, Node Communication Error
01BCH to 01C3H
Status 3.4.4
Node Fault Status 01C4H to 01C7H
Failed Node Detection Disable Status 01CCH to 01CFH
Present Link Scan Time 05FCH
Minimum Link Scan Time 05FDH 3.4.7
Maximum Link Scan Time 05FEH
Slave Function Communication Status 0600H
3.4.8
Error Information for Slave Function 0601H
I/O Address Area for Master Function 0500H to 05FBH
Master Function Receive Data 0700H to 07FFH 3.4.6
Master Function Transmit Data 0900H to 09FFH
Slave Function Receive Data 0B00H to 0B3FH
3.4.10
Slave Function Transmit Data 0C00H to 0C3FH

[Explanation of items]
(1) Items
Module side Buffer size: Displays the buffer memory size of the setting item.
Module side Transfer word count: Displays the number of words to be transferred.
Transfer direction: " " indicates that data are written from the programmable
controller CPU to the buffer memory.
" " indicates that data are loaded from the buffer memory to
the programmable controller CPU.
PLC side Device: Enter a CPU module side device that is to be automatically
refreshed.
Applicable devices are X, Y, M, L, B, T, C, ST, D, W, R, and
ZR.
When using bit devices X, Y, M, L or B, set a number that can
be divided by 16 points (examples: X10, Y120, M16, etc.)
Also, buffer memory data are stored in a 16-point area,
starting from the specified device number. For example, if X10
is entered, data are stored in X10 to X1F.

6 - 14 6 - 14
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

(2) Command buttons

Make text file Creates a file containing the screen data in text file format.
End setup Saves the set data and ends the operation.

Cancel Cancels the setting and ends the operation.

POINT
• The auto refresh settings are stored in an intelligent function module parameter
file.
The auto refresh settings become effective by turning the power OFF and then
ON or resetting the CPU module after writing the intelligent function module
parameters to the CPU module.
• The auto refresh settings cannot be changed from sequence programs.
However, processing equivalent to auto refresh can be added using the
FROM/TO instruction in the sequence program.

6 - 15 6 - 15
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

6.5 Monitoring/Test

[Purpose]
Start buffer memory monitoring/testing and I/O signal monitoring/testing from this
screen.

[Operating procedure]
"Select monitor/test module" screen "Start I/O No. " "Module type"
"Module model name" Monitor/test
* Enter the start I/O No. in hexadecimal.

The screen can also be started from System monitor of GX Developer Version 6
or later.
Refer to the GX Developer Operating Manual for details.

[Setting screen]

[Setting items]
Reference
Item Buffer memory address (Hex.)
section
Model Name 0620H to 0624H
Node Number 0625H 3.4.11
Mode Switch Number 0626H
Bus Error Counter 01B2H
3.4.3
Bus Off Counter 01B3H
H/W Test Item Area 062EH
3.4.12
H/W Test Result Area 062FH
Master Function Communication Status 01B0H
3.4.3
Error Information for Master Function 01B1H
Present Link Scan Time (Units: ms) 05FCH
Minimum Link Scan Time (Units: ms) 05FDH 3.4.7
Maximum Link Scan Time (Units: ms) 05FEH
Slave Function Communication Status 0600H
3.4.8
Error Information for Slave Function 0601H

6 - 16 6 - 16
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

Reference
Item Buffer memory address (Hex.)
section
X/Y Monitor/Test 6.5.1
Parameter Area Monitor/Test 6.5.2
Save Parameters to Flash ROM 6.5.3
Node Configuration Status Monitor 6.5.4
Node Communication Status Monitor 6.5.5
Node Communication Error Status Monitor 6.5.6
Node Fault Status Monitor 6.5.7
Failed Node Detection Setting 6.5.8
Message Communication Area Monitor/Test – 6.5.9
I/O Address Area Monitor for Master Function 6.5.10
Master Function Receive Data Monitor 6.5.11
Master Function Transmit Data Monitor/Test 6.5.12
Slave Function Receive Data Monitor 6.5.13
Slave Function Transmit Data Monitor/Test 6.5.14
Auto Configuration 6.5.15
Flash ROM Parameter Clear 6.5.16
Parameter Backup 6.5.17

6 - 17 6 - 17
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

[Explanation of items]
(1) Items
Setting item: Displays I/O signals and buffer memory names.
Current value: Monitors the I/O signal states and present buffer memory values.
Setting value: Enter or select values to be written into the buffer memory for test
operation.

(2) Command buttons

Write to module Writes parameters to the flash ROM of the QJ71DN91.

Read from module Reads parameters from the flash ROM of the
QJ71DN91.
Save file Saves parameters on the hard disk, etc.

Load file Reads parameters saved on the hard disk, etc.

Current value display Displays the current value of the item selected. (This is
used to check the text that cannot be displayed in the
current value field. However, in this utility package, all
items can be displayed in the display fields).
Make text file Creates a file containing the screen data in text file
format.
Start monitor / Selects whether or not to monitor current values.

Stop monitor
Execute test Performs a test on the selected items. To select more
than one item, select them while holding down the
Ctrl key.
Close Closes the screen that is currently open and returns to
the previous screen.

REMARK
The "Execute test" operation is explained below, using an example of writing data to
"Failed Node Detection Setting".

(1) Change the setting value for "Node 1" to "Do not detect".
Nothing is written to the QJ71DN91 at this point.

(2) Click the setting value field of "Node 1" to select.

To write more than one setting item at the same time, select the items while
holding down the Ctrl key.

(3) Click Execute test to execute the write operation.

Upon completion of writing, the display in the current value field will change to
"Do not detect".

6 - 18 6 - 18
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

6.5.1 X/Y monitor/test

[Purpose]
Monitor I/O signals and tests output signals.

[Operating procedure]
Monitor/Test screen X/Y Monitor/Test

[Setting screen]

[Setting items]
Reference
Item Buffer memory address (Hex.)
section
X00: Watchdog Timer Error 3.3.2 (1)
3.3.2 (2)
X01: I/O Communicating
3.3.3 (2)
X02: Message Communication Completion 3.3.2 (3)
X03: Error Set Signal for Master Function 3.3.2 (4)
X04: Slave Down Signal 3.3.2 (5)
X05: Message Communication Error Signal 3.3.2 (3)
X06: Saving Parameters to Flash ROM
3.3.2 (6)
X07: Parameters Saved to Flash ROM
X08: Error Set Signal for Slave Function 3.3.3 (4)
X0A: H/W Test in Progress
X0B: H/W Test Completion – 3.3.2 (9)
X0C: H/W Test Error Detection
X0F: Module Ready 3.3.2 (7)
X14: Auto-Configuring
3.3.2 (8)
X15: Auto Configuration Completion
3.3.2 (2)
Y11 : I/O Communication Request
3.3.3 (2)
Y12: Message Communication Request 3.3.2 (3)
Y13: Error Reset Request for Master Function 3.3.2 (4)
Y15: Auto Configuration Request 3.3.2 (8)
Y17: Request for Saving Parameters to Flash ROM 3.3.2 (6)
Y18: Error Reset Request for Slave Function 3.3.3 (4)

6 - 19 6 - 19
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

6.5.2 Parameter area monitor/test

[Purpose]
Configure parameters for master function, parameters for slave function, and
auto communication start settings.
For auto configuration of the parameters for master function, refer to Section
6.5.15.
For saving parameters to the flash ROM, refer to Section 6.5.3.

[Operating procedure]
Monitor/Test screen Param. Area Mon.

[Setting screen]

[Setting items]
Reference
Item Buffer memory address (Hex.)
section
Parameters for Master Function 01D4H to 03CFH 3.4.5
Parameters for Slave Function 060EH, 060FH 3.4.9
Auto Communication Start Setting 0631H 3.4.14

6 - 20 6 - 20
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

6.5.3 Save parameters to flash ROM

[Purpose]
Save parameters to the flash ROM.
Follow the instructions shown in the Setting item column.

[Operating procedure]
Monitor/Test screen Flash ROM Save

[Setting screen]

[Setting items]
Reference
Item Buffer memory address (Hex.)
section
1. Stop I/O Communication.
2. Select Parameter Saving Area. 3.3.2 (6)
3. Save Parameters to Flash ROM. – 7.3.1 (3)
4. Confirm Parameter Saving to Flash ROM. 8.2.1 (2)
5. Turn Off Parameter Saving Request.

6 - 21 6 - 21
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

6.5.4 Node configuration status monitor

[Purpose]
Monitor the parameter setting status of each slave node.

[Operating procedure]
Monitor/Test screen Config. Status Mon.

[Setting screen]

[Setting items]
Reference
Item Buffer memory address (Hex.)
section
Node 0 to Node 63 01B4H to 01B7H 3.4.4 (1)

6.5.5 Node communication status monitor

[Purpose]
Monitor the I/O communication status of each slave node.

[Operating procedure]
Monitor/Test screen Comm. Status Mon.

[Setting screen]

[Setting items]
Reference
Item Buffer memory address (Hex.)
section
Node 0 to Node 63 01BCH to 01BFH 3.4.4 (2)

6 - 22 6 - 22
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

6.5.6 Node communication error status monitor

[Purpose]
Monitor the I/O communication error status of each slave node.

[Operating procedure]
Monitor/Test screen Comm. Err. Status Mon.

[Setting screen]

[Setting items]
Reference
Item Buffer memory address (Hex.)
section
Node 0 to Node 63 01C0H to 01C3H 3.4.4 (3)

6.5.7 Node fault status monitor

[Purpose]
Monitor the communication fault status of each slave node.

[Operating procedure]
Monitor/Test screen Fault Status Mon.

[Setting screen]

[Setting items]
Reference
Item Buffer memory address (Hex.)
section
Node 0 to Node 63 01C4H to 01C7H 3.4.4 (4)

6 - 23 6 - 23
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

6.5.8 Failed node detection setting

[Purpose]
Test whether or not to detect a failed node.

[Operating procedure]
Monitor/Test screen Failed Node Detection Setting

[Setting screen]

[Setting items]
Reference
Item Buffer memory address (Hex.)
section
Node 0 to Node 63 01CCH to 01CFH 3.4.4 (5)

6 - 24 6 - 24
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

6.5.9 Message communication area monitor/test

[Purpose]
Test the message communication area.
For the execution timing, refer to Section 3.3.2 (3).

[Operating procedure]
Monitor/Test screen Msg. Comm. Area

[Setting screen]

[Setting items]
Reference
Item Buffer memory address (Hex.)
section
Message Communication Command 0110H to 011FH
Message Communication Result 0120H to 012FH 3.4.2
Message Communication Data 0130H to 01A7H

6 - 25 6 - 25
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

6.5.10 I/O address area monitor for master function

[Purpose]
Monitor the start address and size (words) for each slave node in Master
Function Receive Data (address: 0700H to 07FFH) and Master Function Transmit
Data (address: 0900H to 09FFH).

[Operating procedure]
Monitor/Test screen Address Area For Master

[Setting screen]

[Setting items]
Reference
Item Buffer memory address (Hex.)
section
1st Slave, Input Data Start Address 0500H
1st Slave, Input Data Size (Words) 0501H
1st Slave, Output Data Start Address 0502H 3.4.6 (3)
1st Slave, Output Data Size (Words) 0503H
2nd to 63rd Slaves 0504H to 05FBH

6 - 26 6 - 26
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

6.5.11 Master function receive data monitor

[Purpose]
Monitor the data received from each slave node.

[Operating procedure]
Monitor/Test screen Master Receive Data

[Setting screen]

[Setting items]
Reference
Item Buffer memory address (Hex.)
section
Master Function Receive Data 0700H to 07FFH 3.4.6 (1)

6.5.12 Master function transmit data monitor/test

[Purpose]
Test the data to be sent to each slave node.

[Operating procedure]
Monitor/Test screen Master Transmit Data

[Setting screen]

[Setting items]
Reference
Item Buffer memory address (Hex.)
section
Master Function Transmit Data 0900H to 09FFH 3.4.6 (2)

6 - 27 6 - 27
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

6.5.13 Slave function receive data monitor

[Purpose]
Monitor the data received from the master node.

[Operating procedure]
Monitor/Test screen Slave Receive Data

[Setting screen]

[Setting items]
Reference
Item Buffer memory address (Hex.)
section
Slave Function Receive Data 0B00H to 0B3FH 3.4.10 (1)

6.5.14 Slave function transmit data monitor/test

[Purpose]
Test the data to be sent to the master node.

[Operating procedure]
Monitor/Test screen Slave Transmit Data

[Setting screen]

[Setting items]
Reference
Item Buffer memory address (Hex.)
section
Slave Function Transmit Data 0C00H to 0C3FH 3.4.10 (2)

6 - 28 6 - 28
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

6.5.15 Auto configuration

[Purpose]
Using the auto configuration, set the parameters for master function.
Follow the instructions shown in the Setting item column.

[Operating procedure]
Scroll down on the Monitor/Test screen.

[Setting screen]

[Setting items]
Reference
Item Buffer memory address (Hex.)
section
1. Stop I/O Communication.
2. Set Auto Configuration Operation.
3.3.2 (8)
3. Execute Auto Configuration. –
7.3.1 (1)
4. Confirm Auto-Configured Parameters.
5. Save Parameters to Flash ROM.

6 - 29 6 - 29
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

6.5.16 Flash ROM parameter clear

[Purpose]
Clear the parameters from the flash ROM.
Follow the instructions shown in the Setting item column.

[Operating procedure]
Scroll down on the Monitor/Test screen.

[Setting screen]

[Setting items]
Reference
Item Buffer memory address (Hex.)
section
7.3.1 (4)
Flash ROM Parameter Clear –
8.2.1 (3)

6 - 30 6 - 30
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

6.5.17 Parameter backup

[Purpose]
Read the parameters saved in the QJ71DN91’s flash ROM, and save them in the
personal computer.
Or, read the parameters saved in the personal computer, and save them in the
QJ71DN91’s flash ROM.
Follow the instructions shown in the Setting item column.
[Operating procedure]
Scroll down on the Monitor/Test screen.

[Setting screen]

Param. Backup

[Setting items]
Reference
Item Buffer memory address (Hex.)
section
Parameter Saving Area Selection 0630H 3.4.13
Parameters for Master Function 01D4H to 03CFH 3.4.5
Parameters for Slave Function 060EH, 060FH 3.4.9
Auto Communication Start Setting 0631H 3.4.14

6 - 31 6 - 31
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

6.6 Flash ROM Setting

[Purpose]
Edit the flash ROM settings offline.
Edited parameters can be written to the module from the "Parameter Backup"
screen under "Monitor/Test".

[Operating procedure]
Flash ROM setting screen "Module type" "Module model name" Select

[Setting screen]

Param. Backup

6 - 32 6 - 32
6 UTILITY PACKAGE (GX Configurator-DN)
MELSEC-Q

[Explanation of items]
(1) Items
Setting item: Displays parameter names.
Setting value: Enter or select values to be set in the flash ROM.

(2) Command button

Save file Saves the parameters on the hard disk, etc.
Load file Reads the parameters saved on the hard disk, etc.
Close Closes the currently open screen and returns to the previous screen.

6 - 33 6 - 33
 7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION

This chapter explains programming for executing the master function.

When applying the program examples introduced in this chapter to the actual system,
make sure to examine the applicability and confirm that it will not cause system control
problems.

7.1 Programming Precautions

When creating programs, pay attention to the following:

(1) To perform I/O communication with a slave node, perform the following:
• Place the I/O communication read processing program at the beginning of the
sequence program.
• Place the I/O communication write processing program at the end of the
sequence program.

Refresh processing request, I/O communication read processing

•
•
•
•
•
•

I/O communication write processing

(2) Reading receive data and writing transmit data must be performed when there is
no error in the module and the module is in the ready status.
Module error Module ready

7
X0 X0F
Program for communication

3) Create a program that detects the communication status of each node and
performs interlock. Also, create an error handling program.
Module error Module ready Node communication status

X0 X0F
FROM H0 H1BC K4MO K4

M0
Node No. 0 error handling program

M1
Node No. 1 error handling program

M0
Node No. 0 normal processing program

M1
Node No. 1 normal processing program

7-1 7-1
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

(4) When handling transmit/receive data of multiple words, pay attention to the
following:
Consistency of 1-word or 2-word (for double-word modules) is guaranteed for
transmit/receive data.
When data of three words or more are handled, new and old data may be mixed
in units of one word.
Therefore, confirm correct data transfer using a method such as providing a
handshake area at each end of transmit/receive data areas, as shown in the
following example.
Programmable controller CPU QJ71DN91 master QJ71DN91 slave Programmable controller CPU

Master function Slave function

receive data transmit data
700H C00H
701H C01H
702H C02H
1)Transmit request (Receive completion 6)
703H (Transmit complete flag) C03H notification flag)
M0
7) Master function Slave function
transmit data receive data
D0 900H B00H D100
Transmit 2) 5)
D1 901H Transmit data B01H Receive data D101 Receive data
data
D2 902H 3) B02H 4) D102
903H (Transmit request flag) B03H (Receive complete flag)

Transmitting node (QJ71DN91 master)

1) 2)
\ \ \
Stores transmit data in Master
Transmit complete Transmit request Transmit Master function function transmit data area.
flag: 703H flag: 903H data transmit data: 900H

7
3) \
Sets Transmit request flag.
Transmit
request
flag: 903H

\ 7) \
Resets Transmit request flag.
Transmit complete Transmit
flag: 703H request
flag: 903H

Receiving node (QJ71DN91 slave)

4) 5)
\ \ \
Reads receive data from Slave
Receive complete Receive completion Slave function Receive data function receive data area.
flag: B03H notification receive data
flag: C03H :B00H

6) \
Sets Receive completion
Receive notification flag.
completion
notification
flag
:C03H
\ \
Resets Receive completion
Receive complete Receive
notification flag.
flag: B03H completion
notification
flag
:C03H

7-2 7-2
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

1) Transmission command turns ON.

2) Data in D0 to D2 are stored in the transmit data area (address: 900H to
902H).
3) Upon completion of storing the transmit data, the transmit request flag
(address: 903H) turns ON.
4) The master function transmit data are sent through I/O communication,
and the receive complete flag (address: B03H) turns ON.
5) Data in the receive data area (address: B00H to B02H) are stored in
D100 to D102.
6) Upon completion of storing the data into D100 to D102, the receive
completion notification flag (address: C03H) turns ON.
7) When data are received on the receiving node, the transmit request
flag (address: 903H) turns OFF.

7-3 7-3
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

7.2 System Configuration

The explanation of the programs in this chapter is based on the following system.

(1) System configuration

Q06HCPU Q06HCPU
QJ71DN91(master node)*1 QJ71DN91(slave node)*2

Master node 3rd slave node

(Node No.0) (Node No.4, polling)

Terminating resistor Terminating resistor

24V power supply 1st slave node 2nd slave node 4th slave node
(Node No.1, polling) (Node No.2, polling) (Node No.3, bit strobe)
Omron CompoBus/D Omron CompoBus/D Rockwell Automation
8-point input 8-point output Flex I/O DeviceNet adapter
(DRT1-ID08) (DRT1-OD08) + 16-point input
(1794ADN+IB16)*3

*1: The QJ71DN91 (master node) is installed to slot 0 of the base unit, with the start I/O No. set to
"0000H".
*2: The QJ71DN91 (slave node) is installed to slot 1 of the base unit, with the start I/O No. set to
"0020H".
*3: Rockwell Automation’s Flex I/O DeviceNet adapter has input data of two bytes for its status. It
also has 2-byte input data and 2-byte output data.

(2) Settings
(a) Settings of the master node (QJ71DN91 (master node))
For communication with the 1st to 4th slave nodes, set the information such
as connection type and I/O points as the parameters for master function.
(Refer to Section 7.3.)
Item Setting
Node No. (Node No. switches) 0 (00)
Communication speed (Mode switch) 125kbaud (Mode 0)
Receive data X100 to X16F
Transmit data Y100 to Y14F

7-4 7-4
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

(b) Settings of the slave nodes

For the setting of node No. and communication speed, refer to the manual
for each slave node.
1) 1st slave node
(Omron’s CompoBus/D, 8-point input (DRT1-ID08))
Item Setting
Node No. Node No.1
Communication speed 125kbaud
Connection type Polling
I/O points 8 input points

2) 2nd slave node

(Omron’s CompoBus/D, 8-point output (DRT1-OD08))
Item Setting
Node No. Node No.2
Communication speed 125kbaud
Connection type Polling
I/O points 8 output points

3) 3rd slave node (QJ71DN91(slave node))

Item Setting
Node No. (Node No. switches) Node No.4 (04)
Communication speed (Mode switch) 125kbaud (Mode 3)
Connection type Polling
Slave function receive-bytes (input points) 8 bytes
Slave function transmit-bytes (output points) 8 bytes

4) 4th slave node

(Rockwell Automation’s Flex I/O DeviceNet adapter + 16-point input
(1794ADN + IB16))
Item Setting
Node No. Node No.3
Communication speed 125kbaud
Connection type Bit strobe
I/O points 16 input points

7-5 7-5
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

(3) Communications
The following shows the relation among the programmable controller CPU,
master node’s buffer memory, and a slave node.

Programmable controller CPU QJ71DN91 master node Remote I/O (node No. 1)
8-point input
Receive data
FROM
X100 to X107 Node No. 1 I00 to I07
700H
Input 00 to input 07
701H
QJ71DN91 slave node (node No. 4)
FROM 702H Node No. 4
X110 to X14F 8-byte transfer
703H
704H C00H
Node No. 3 status
705H C01H Transmit data
FROM
X160 to X16F 706H
Node No. 3
C02H
C03H
Transmit data
TO B00H
Y100 to Y107 900H Node No. 2
B01H Receive data
901H
B02H
TO 902H Node No. 4
Y110 to Y14F B03H
903H
Remote I/O (node No. 3)
904H 16-point input
Node No. 3
905H
Status

I00 to I15
Input 00 to input 15

Dummy output

Remote I/O (node No. 2)

8-point input

O00 to O07
Output 00 to output 07

7-6 7-6
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

7.3 Parameters for Master Function

(1) Setting items

The following table lists the parameters for master function, which are set in a
program example.
For details of the parameters for master function, refer to Section 3.4.5.
For setting by auto configuration, refer to (2) in this section.
For saving parameters to the flash ROM, refer to (3) in this section.
Buffer memory
Item Set value
address (Hex.)
01D7H Constant scan 0000H (0ms)
01D8H Node No. and message group 0401H (Node No.1, group 2 only server)
01D9H Connection type 0001H (Polling)
01DAH Number of byte modules 0001H (Input 1, Output 0)
01DBH 1st slave Number of word modules 0000H (Input 0, Output 0)
01DCH node Number of double-word modules 0000H (Input 0, Output 0)
01DDH Expected packet rate 0000H (200ms)
01DEH Watchdog timeout action 0000H (Timeout)
01DFH Production inhibit time 0000H (10ms)
01E0H Node No. and message group 0402H (Node No.2, group 2 only server)
01E1H Connection type 0001H (Polling)
01E2H Number of byte modules 0100H (Input 0, Output 1)
01E3H 2nd slave Number of word modules 0000H (Input 0, Output 0)
01E4H node Number of double-word modules 0000H (Input 0, Output 0)
01E5H Expected packet rate 0000H (200ms)
01E6H Watchdog timeout action 0000H (Timeout)
01E7H Production inhibit time 0000H (10ms)
01E8H Node No. and message group 0104H (Node No.4, message group 3)
01E9H Connection type 0001H (Polling)
01EAH Number of byte modules 0808H (Input 8, Output 8)
01EBH 3rd slave Number of word modules 0000H (Input 0, Output 0)
01ECH node Number of double-word modules 0000H (Input 0, Output 0)
01EDH Expected packet rate 501 (500ms)
01EEH Watchdog timeout action 0002H (Auto delete)
01EFH Production inhibit time 21 (20ms)
01F0H Node No. and message group 0103H (Node No.3, message group 3)
01F1H Connection type 0002H (Bit strobe)
01F2H Number of byte modules 0204H (Input 4, Output 2)
01F3H 4th slave Number of word modules 0000H (Input 0, Output 0)
01F4H node Number of double-word modules 0000H (Input 0, Output 0)
01F5H Expected packet rate 0000H (200ms)
01F6H Watchdog timeout action 0000H (Timeout)
01F7H Production inhibit time 0000H (10ms)

7-7 7-7
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

(2) Operation flow of auto configuration

The following explains the operation flow in the case of using auto configuration.
When using the utility package, refer to Section 7.3.1 (1).
When not using the utility package, refer to Section 7.3.2 (1).
I/O Communication Request (Y11) 2)

I/O Communicating (X01)

Request for Saving Parameters OFF 2)

to Flash ROM (Y17) 3) 7)

Auto Configuration Request (Y15)

4)

Auto Configuring (X14)

5)

Auto Configuration Completion (X15)

1)
MOV/TO
Auto Configuration Operation Setting (03F0H) instruction
6) 8)
MOV/TO
Parameters for Master Function (01D4H to 03CFH) instruction

Slave (Node No.1)

Slave (Node No.2)
Slave (Node No.3)

1) Set a type of auto configuration and the maximum detection node No.
in Auto Configuration Operation Setting (address: 03F0H).
(Example) When the auto configuration type is "All configuration" and
the maximum detection node No. is 4, set 0004H.
2) Set I/O Communication Request (Y11) and Request for Saving
Parameters to Flash ROM (Y17) to OFF.
3) Set Auto Configuration Request (Y15) to ON.
4) Auto configuration is started, and Auto-Configuring (X14) is set to ON.
Up to approx. 60 seconds are needed for completion of auto
configuration.
5) Upon completion of auto configuration, Auto Configuration Completion
(X15) is set to ON.
6) Parameters saved in each slave node are loaded and stored in
Parameters for Master Function (address: 01D4H to 03CFH).
The parameter settings loaded from the slave nodes are stored in
order of node No.
7) When Auto Configuration Request (Y15) is set to OFF, Auto-
Configuring (X14) and Auto Configuration Completion (X15) are set to
OFF.
8) Check Parameters for Master Function (address: 01D4H to 03CFH).
Confirm that the settings such as node No., connection type, I/O points
are correct. Correct values if any incorrect setting is identified.

7-8 7-8
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

(3) Operation flow of parameter saving to flash ROM

The following explains the operation flow in the case of saving parameters to the
flash ROM.
When using the utility package, refer to Section 7.3.1 (3).
When not using the utility package, refer to Section 7.3.2 (3).
I/O Communication Request (Y11) 3)

I/O Communicating (X01)

Auto Configuration Request (Y15) OFF 3)

4) 8)
Request for Saving Parameters to Flash ROM (Y17)
5)
Saving Parameters to Flash ROM (X06)
7)
Parameters Saved to Flash ROM (X07)
6)
Error Set Signal for Master Function (X03)

MOV/FROM
Error Information for Master Function (01B1H) instruction
2)
Parameter Area Select Bit (0630H) MOV/TO
instruction
1)
MOV/TO Parameter
Parameters instruction check

Flash ROM

1) Set parameters in the following buffer memory areas:

• Parameters for Master Function (address: 01D4H to 03CFH)
• Auto Communication Start Setting (address: 0631H)
2) Specify a parameter saving area in Parameter Area Select Bit
(address: 0630H).
3) Set I/O Communication Request (Y11) and Auto Configuration
Request (Y15) to OFF.
4) When Request for Saving Parameters to Flash ROM (Y17) is set to
ON, parameters are checked.
5) If the parameter check is completed successfully, saving the
parameters to the flash ROM is started, and Saving Parameters to
Flash ROM (X06) is set to ON.
6) If the parameter check has failed, the ERR. LED lights up and Error
Set Signal for Master Function (X03) is set to ON.
Check the error code in Error Information for Master Function
(address: 01B1H), and take corrective actions.
7) Upon completion of parameter saving to the flash ROM, Parameters
Saved to Flash ROM (X07) is set to ON.
8) When Request for Saving Parameters to Flash ROM (Y17) is set to
OFF, Saving Parameters to Flash ROM (X06) and Parameters Saved
to Flash ROM (X07) are set to OFF.
7-9 7-9
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

7.3.1 Program example using the utility package

(1) When using auto configuration

POINT
(1) Pre-determine the slave node settings (e.g. connection type) before executing
auto configuration.
(2) Check that the power of the slave nodes and the network is ON and the wiring
is correct.

(a) The setting items for auto configuration are shown below.

2)

1)

1) Scroll the [Monitor/Test] screen, and bring up the auto configuration

setting area.
For information on how to display the [Monitor/Test] screen, refer to
Section 6.3.
2) Perform auto configuration according to the following steps 1 to 5.
1. Stop I/O communication. (Refer to (b).)
2. Set auto configuration operation. (Refer to (c).)
3. Execute auto configuration (Refer to (d).)
4. Confirm auto-configured parameters. (Refer to (e).)
5. Save parameters to flash ROM. (Refer to (3).)

7 - 10 7 - 10
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

(b) [1. Stop I/O Communication.]

Clicking the I/O Comm. Stop button on the [Monitor/Test] screen will
display the [1. Stop I/O Communication.] screen.
Follow the setting instructions.

1)

2)

3)

4)

1) When the current value for "Y11: I/O Communication Request" is "I/O
Comm. Request", set "I/O Comm. Stop Request".
Select "I/O Comm. Stop Request" Execute test button
2) When the current value for "X01: I/O Communicating" is "I/O
Communicating", set "I/O Comm. Request" for "Y11: I/O
Communication Request".
Select "I/O Comm. Request" Execute test button
Then, set "I/O Comm. Stop Request" for "Y11: I/O Communication
Request".
Select "I/O Comm. Stop Request" Execute test button
Check that the current value for "X01: I/O Communicating" was
changed to "I/O Comm. Stop".

7 - 11 7 - 11
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

3) When the current value for "Y17: Request for Saving Parameters to
Flash ROM" is "Save Request", set "OFF" for it.
Select "OFF" Execute test button
4) Click the Close button.

(c) [2. Set Auto Configuration Operation.]

Clicking the Operation Setting button on the [Monitor/Test] screen will
display the [1. Set Auto Configuration Operation.] screen.
Follow the setting instructions.

1)

2)

1) Set the auto configuration operation. (Refer to Section 3.4.5.)

To specify All configuration, set "003F" for "Auto Configuration
Operation Setting".
Select "003F" Execute test button
2) Click the Close button.

7 - 12 7 - 12
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

(d) [3. Execute Auto Configuration.]

Clicking the Auto Config button on the [Monitor/Test] screen will display the
[3. Execute Auto Configuration.] screen.
Follow the setting instructions.

1)

2)
3)

4)

5)

1) Set "Config. Request" for "Y15: Auto Configuration Request".

Select "Config. Request" Execute test button
2) Auto configuration is started, and "Executing" is displayed for "X14:
Auto-Configuring".
3) Upon completion of auto configuration, "Completed" is displayed for
"X15: Auto Configuration Completion".
4) After completing the auto configuration, set "OFF" for "Y15: Auto
Configuration Request".
Select "OFF" Execute test button
5) Click the Close button.

7 - 13 7 - 13
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

(e) [4. Confirm Auto-Configured Parameters.]

Clicking the Param. Check button on the [Monitor/Test] screen will display
the [4. Confirm Auto-Configured Parameters.] screen.

1)

2)

3)

4)

1) Check the parameters for master function.

Check that the settings such as node No., connection type, and I/O
points are correct. (For the setting details, refer to Section 7.3 (1).)
2) Correct values if any incorrect setting is identified.
Select a value in a Setting value field Execute test button
Repeat this if more than one value must be corrected.
3) To start I/O communication automatically at power-up, set "Start" for
"Auto Communication Start Setting".
Select "Start" Execute test button
4) Click the Close button.

7 - 14 7 - 14
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

POINT
(1) Slave node settings detected by auto configuration are stored in order of node
No.
(2) When changing parameters for master function, set default values in the areas
after the parameter-set areas.
(Example) When changing the number of slave nodes that can perform I/O
communication from 6 to 4, set default values in the areas for 5th
and 6th slave nodes.

7 - 15 7 - 15
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

(2) When setting parameters manually

(a) Set the parameters for master function.
Clicking the Parameter Area Monitor/Test button on the [Monitor/Test]
screen will display the [Parameter Area Monitor/Test] screen.
For information on how to display the [Monitor/Test] screen, refer to Section
6.3.

1)

2)

3)

1) Set parameters for 1st to 4th slave nodes. (For the setting details, refer
to Section 7.3 (1).)
Select a value in a Setting value field Execute test button
Repeat this if more than one parameter must be set.
2) To start I/O communication automatically at power-up, set "Start" for
"Auto Communication Start Setting".
Select "Start" Execute test button
3) Click the Close button.

7 - 16 7 - 16
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

(b) Save parameters to a flash ROM (Refer to (3) in this section.)

POINT
When changing parameters for master function, set default values in the areas after
the parameter-set areas.
(Example) When changing the number of slave nodes that can perform I/O
communication from 6 to 4, set default values in the areas for 5th and
6th slave nodes.

7 - 17 7 - 17
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

(3) When saving the parameters to a flash ROM

Clicking the Flash ROM Save button on the [Monitor/Test] screen will display the
[5. Save Parameters to Flash ROM.] or [Save Parameters to Flash ROM] screen.
(The same setting details are displayed on the both screens.)
Follow the setting instructions.
POINT
Save the parameters in the buffer memory to a flash ROM. Otherwise, they are
cleared when the power is turned OFF or the CPU module is reset.

1)

2)

3)

1) When the current value for "Y11: I/O Communication Request" is "I/O
Comm. Request", set "I/O Comm. Stop Request".
Select "I/O Comm. Stop Request" Execute test button
2) When the current value for "X01: I/O Communicating" is "I/O
Communicating", set "I/O Comm. Request" for "Y11: I/O
Communication Request".
Select "I/O Comm. Request" Execute test button
Then, set "I/O Comm. Stop Request" for "Y11: I/O Communication
Request".
Select "I/O Comm. Stop Request" Execute test button
Check that the current value for "X01: I/O Communicating" was
changed to "I/O Comm. Stop".
3) When the current value for "Y15: Auto Configuration Request" is
"Config. Request", set "OFF" for "Y15: Auto Configuration Request".
Select "OFF" Execute test button

7 - 18 7 - 18
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

4)

5)
6)

7)

8)

9)

10)

4) Select the parameter saving area.

When saving the parameters for master function and the auto
communication start setting, set "Master/Auto Comm." for "Parameter
Saving Area Selection".
Select "Master/Auto Comm. " Execute test button
5) Set "Save Request" for "Y17: Request for Saving Parameters to Flash
ROM".
Select "Save Request" Execute test button
6) Parameter saving to the flash ROM is started, and "Saving" is
displayed for "X06: Saving Parameters to Flash ROM".
7) Upon completion of the saving, "Saving Completed" is displayed for
"X07: Parameters Saved to Flash ROM".

7 - 19 7 - 19
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

8) If parameter check has failed, "Error Occurred" is displayed for "X03:

Error Set Signal for Master Function".
Check the error code in the current value column of "Error Information
for Master Function", and take corrective actions. (Refer to Section
9.2.1.)
9) After completing the parameter saving to the flash ROM, set "OFF" for
"Y17: Request for Saving Parameters to Flash ROM".
Select "OFF" Execute test button
10) Click the Close button.

POINT
Since the number of writes to flash ROM is limited, use Request for Saving
Parameters to Flash ROM (Y17) only when creating or changing parameters.

7 - 20 7 - 20
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

(4) When clearing parameters from the flash ROM

Clicking the Flash ROM Clear button on the [Monitor/Test] screen will display the
[Flash ROM Parameter Clear] screen.
Follow the setting instructions.

1)

2)
3)

4)

5)

6)

1) Set "Param. Clear" for "Flash ROM Parameter Clear".

Select "Param. Clear" Execute test button
2) Set "Param. Clear Request" for "Flash ROM Parameter Clear
Request".
Select "Param. Clear Request" Execute test button
3) Clearing the parameters in the flash ROM is started, and "Clearing" is
displayed for "Flash ROM Parameter Clearing".
4) When clearing the flash ROM parameters is completed, "Clear
Completed" is displayed for "Flash ROM Parameter Clear
Completion".
7 - 21 7 - 21
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

5) After completion of clearing the flash ROM parameters, set "OFF" for
"Request for Saving Parameters to Flash ROM".
Select "OFF" Execute test button
6) Click the Close button.

7 - 22 7 - 22
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

7.3.2 Program example not using the utility package

(1) When using auto configuration

(a) Device list
Reference
Device Description
section
M10 Parameter Setting Command for Master Function
M300 Auto Configuration Command ―
M301 Auto-Configuration Flag
X01 I/O Communicating
X14 Auto-Configuring
X15 Auto Configuration Completion
3.3.2 (8)
Y11 I/O Communication Request
Y15 Auto Configuration Request
Y17 Request for Saving Parameters to Flash ROM
D0 Auto Configuration Operation Setting 3.4.5

(b) Program example

Auto configuration
Auto configuration operation setting
All configuration
Max. detection node No. = 4
Writes parameters to buffer memory.

Sets Auto Configuration Request

to ON.
Auto configuring

Auto configuration completed

Sets Auto Configuration Request

to OFF.

Sets Parameter Setting Command

for Master Function to ON.
Change settings. (See (2).) *1

Save parameters to flash ROM. (See (3).)

*1: Check that the settings such as node No., connection type, and I/O points are correct.
Correct values if any incorrect setting is identified. (For the setting details, refer to Section 7.3 (1).)

POINT
(1) Pre-determine the slave node settings (e.g. connection type) before executing
auto configuration.
(2) Check that the power of the slave nodes and the network is ON and the wiring
is correct.
(3) Slave node settings detected by auto configuration are stored in order of node
No.
(4) When changing parameters for master function, set default values in the areas
after the parameter-set areas.
(Example) When changing the number of slave nodes that can perform I/O
communication from 6 to 4, set default values in the areas for 5th
and 6th slave nodes.

7 - 23 7 - 23
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

(2) When setting parameters manually

(a) Device list
Reference
Device Description
section
M10 Parameter Setting Command for Master Function
X01 I/O Communicating ―
Y11 I/O Communication Request
Parameters for Master Function (for 1st to 4th slave
D4 to D35 3.4.5
nodes)

(b) Program example

Parameters for master function
[1st slave node]
Node No.=1, group 2 only server

Connection type = Polling

Input byte module = 1
Output byte module = 0
Input word module = 0
Output word module = 0
Input double-word module = 0
Output double-word module = 0
Expected packet rate
Default = 200ms
Watchdog timeout action
Default = Timeout
Production inhibit time
Default = 10ms
[2nd slave node]
Node No.=2, group 2 only server

Connection type = Polling

Input byte module = 0
Output byte module = 1
Input word module = 0
Output word module = 0
Input double-word module = 0
Output double-word module = 0
Expected packet rate
Default = 200ms
Watchdog timeout action
Default = Timeout
Production inhibit time
Default = 10ms

7 - 24 7 - 24
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

Parameters for master function

[3rd slave node]
Node No.= 4, message group = 3

Connection type = Polling

Input byte module = 8
Output byte module = 8
Input word module = 0
Output word module = 0
Input double-word module = 0
Output double-word module = 0
Expected packet rate = 500ms

Watchdog timeout action = Auto delete

Production inhibit time = 20ms

[4th slave node]
Node No. = 3, message group = 3

Connection type = Bit strobe

Input byte module = 4
Output byte module = 2
Input word module = 0
Output word module = 0
Input double-word module = 0
Output double-word module = 0
Expected packet rate
Default = 200ms
Watchdog timeout action
Default = Timeout
Production inhibit time
Default = 10ms
Write parameters to buffer memory.

Save parameters to flash ROM. (See (3).)

POINT
When changing parameters for master function, set default values in the areas after
the parameter-set areas.
(Example) When changing the number of slave nodes that can perform I/O
communication from 6 to 4, set default values in the areas for 5th and
6th slave nodes.

7 - 25 7 - 25
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

(3) When saving parameters to a flash ROM

(a) Device list
Reference
Device Description
section
M302 Parameter Saving Command
―
M303 Saving Parameters to Flash ROM Flag
X01 I/O Communicating
X06 Saving Parameters to Flash ROM
X07 Parameters Saved to Flash ROM
3.3.2 (6)
Y11 I/O Communication Request
Y15 Auto Configuration Request
Y17 Request for Saving Parameters to Flash ROM
D36 Parameter Area Select Bit 3.4.13
D37 Auto Communication Start Setting 3.4.14

(b) Program example

Setting parameters for master function
Using auto configuration (See (1).)
Setting manually (See (2).)
Parameter saving
Parameter Area Select Bit
Master/Auto Comm.
Auto Communication Start Setting
Start
Writes parameters to buffer memory.

Sets Request for Saving Parameters

to Flash ROM to ON.
Saving parameters to flash ROM

Saving parameters to flash ROM

completed
Sets Request for Saving Parameters
to Flash ROM to OFF.

POINT
(1) Save the parameters in the buffer memory to a flash ROM. Otherwise, they are
cleared when the power is turned OFF or the CPU module is reset.
(2) Since the number of writes to flash ROM is limited, use Request for Saving
Parameters to Flash ROM (Y17) only when creating or changing parameters.

7 - 26 7 - 26
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

7.4 I/O Communication Function

7.4.1 Program example using the utility package

(1) Device list

Reference
Device Description
section
M11 I/O Communication Start Command ―
1
M96 to M111* Node Communication Status 3.4.4
1
X100 to X10F* 1st slave node: Node No.1
1 Master Function
X110 to X14F* 3rd slave node: Node No.4 3.4.6
*1 Receive Data
X150 to X16F 4th slave node: Node No.3
Y11 I/O Communication Request 3.3.2 (2)
1
Y100 to Y10F* Master Function 2nd slave node: Node No.2
*1 3.4.6
Y110 to Y14F Transmit Data 3rd slave node: Node No.4

*1: Devices used in the auto refresh function of GX Configurator-DN.

(2) Operation in the utility package

(a) Auto refresh setting (Refer to Section 6.4.)
1) Node Communication Status, Node Communication Error Status
………………………………………………..M96 to M111
2) Master Function Receive Data…………….X100 to X16F
3) Master Function Transmit Data……………Y100 to Y14F

1)

2)
3)

7 - 27 7 - 27
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

(b) Writing intelligent function module parameters (Refer to Section 6.3.3.)

Write parameters of the intelligent function modules (auto refresh settings)
to the CPU module.
Perform this operation from the screen for selecting a target intelligent
function module.

(3) Program example

Setting parameters for master function (See Section 7.3.)

I/O communication function

Sets I/O Communication
Request to ON.
1st slave node: Node No.1
Error handling program for node No.1

Input data processing program for node No.1

2nd slave node: Node No.2

Error handling program for node No.2

Output data processing program

for node No.2

3rd slave node: Node No.4

Error handling program for node No.4

Input data processing program for node No.4

Output data processing program

for node No.4

4th slave node: Node No.3

Error handling program for node No.3

Input data processing program for node No.3

POINT
To ensure consistency of transmit/receive data of multiple words, take a measure
such as providing a handshake area at the end of transmit/receive data to check
the data transfer.
For the program example, refer to Section 7.1 (4).

7 - 28 7 - 28
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

7.4.2 Program example not using the utility package

(1) Device list

Reference
Device Description
section
M11 I/O Communication Command ―
M100 to M115 Node Communication Status 3.4.4
X01 I/O Communicating 3.3.2 (2)
X100 to X107 1st slave node: Node No.1
Master Function
X110 to X14F 3rd slave node: Node No.4 3.4.6
Receive Data
X160 to X16F 4th slave node: Node No.3
Y11 I/O Communication Request 3.3.2 (2)
Y100 to Y107 Master Function 2nd slave node: Node No.2
3.4.6
Y110 to Y14F Transmit Data 3rd slave node: Node No.4

7 - 29 7 - 29
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

(2) Program example

Setting parameters for master function (See Section 7.3.)

I/O communication function

Sets initial transmit data values.

Set I/O Communication

Request to ON.
Reads node communication status.
1st slave node: Node No.1
Error handling program for node No.1

Input data processing program for node No.1

2nd slave node: Node No.2

Error handling program for node No.2

Output data processing program

for node No.2

Writes transmit data.

3rd slave node: Node No.4
Error handling program for node No.4

Reads receive data.

Input data processing program for node No.4

Output data processing program

for node No.4

Writes transmit data.

4th slave node: Node No.3
Error handling program for node No.3

Reads receive data.

Input data processing program for node No.3

POINT
To ensure consistency of transmit/receive data of multiple words, take a measure
such as providing a handshake area at the end of transmit/receive data to check
the data transfer.
For the program example, refer to Section 7.1 (4).

7 - 30 7 - 30
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

7.5 Message Communication Function

This section explains an example of a sequence program created for message

communication.

7.5.1 Example of reading message communication data

An example program in this section performs Get Attribute to node No.3.

For the area enclosed with a dotted line, refer to the manual for the relevant slave node
since the class ID, instance ID, and attribute ID are different depending on the actual
area and the slave node.

(1) Device list

Reference
Device Description
section
M0 Get Attribute Command
―
M100 Get Attribute Execute Flag
X02 Message Communication Completion
3.3.2 (3)
Y12 Message Communication Request
D0 to D3 Message Communication Command
D10 to D14 Message Communication Result 3.4.2
D20 to D28 Message Communication Data
D100 Master Function Communication Status 3.4.3

7 - 31 7 - 31
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

(2) Program example

Reads master function
communication status.

Executes Get Attribute

if Master Function Comm.
Status is C0H or 40H.

Get Attribute

Node No.3, Class ID = 1

Instance ID = 1

Attribute ID = 7

Writes message comm.

command to buffer memory.
Sets Message Comm.
Request to ON.

Error handling program

Gets byte length

of attribute data.
Calculates byte length
of attribute data.

Reads attribute data.

Sets Message Comm.

Request to OFF.

7 - 32 7 - 32
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

7.5.2 Example of writing message communication data

An example program in this section performs Set Attribute to node No.3.

For the area enclosed with a dotted line, refer to the manual for the relevant slave node
since the class ID, instance ID, and attribute ID are different depending on the actual
area and the slave node.

(1) Device list

Reference
Device Description
section
M200 Set Attribute Execute Flag
―
M201 Set Attribute Command
X02 Message Communication Completion
3.3.2 (3)
Y12 Message Communication Request
D30 Message Communication Data
D300 to D303 Message Communication Command 3.4.2
D310 to D314 Message Communication Result
D200 Master Function Communication Status 3.4.3

(2) Program example

Sets attribute data.

Writes attribute data to buffer memory.

Reads master function

communication status.

Executes Set Attribute

if Master Function Comm.
Status is C0H or 40H.

Set Attribute

Node No.3, Class ID = 3

Instance ID = 1

Byte length of attribute

data = 1, Attribute ID = 3
Writes message comm.
command to buffer memory.
Sets Message Comm.
Request to ON.

Error handling program

Sets Message Comm.

Request to OFF.

7 - 33 7 - 33
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

7.6 Obtaining Error Information

This section explains an example of a sequence program that obtains the error
information for the master function.

(1) Device list

Reference
Device Description
section
M60 Error Reset Command ―
X03 Error Set Signal for Master Function
3.3.2 (4)
Y13 Error Reset Request for Master Function
D500 Error Information for Master Function
D501 Node No. of Error Node 3.4.3
D502 Error Code

(2) Program example

Reads error information
for master function from buffer memory.

Node No. of error node

Error information for master function

Error code

Sets Error Reset Request

for Master Function to ON.

Sets Error Reset Request

for Master Function to OFF.

7 - 34 7 - 34
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

7.7 Allocating Transmit/Receive Data Storage Devices for Future Expansion

If transmit/receive data of each slave node may change depending on the system,
reserve the data storage devices for each slave node in advance.
Using the information in I/O Address Area for Master Function (address: 0500H to
05FBH) and executing the FROM or TO instruction will eliminate the need for modifying
the sequence program even if the transmit/receive data length is changed.
The figure below shows an example in which the transmit/receive data storage devices
of each node are allocated in units of 64 points, in the same system configuration
described in Section 7.2.
In this example, the devices are allocated as follows: 64 points from X200 for storing
receive data of node No.1, 64 points from X240 for storing receive data of node No.2,
and so on.
The information in I/O Address Area for Master Function (address: 0500H to 05FBH) is
stored in D1000 to D1251, and the FROM or TO instruction is executed using the start
buffer memory address of this information and the data length.
Programmable controller CPU QJ71DN91 master node Remote I/O (node No. 1)
8-point input
Receive data
Receive FROM I00 to I07
X200 to X207 700H Node No. 1
data area for 701H Input 00 to input 07
X208 to X23F FROM
node No.1 (For future 702H
(64 points)
Node No. 4 QJ71DN91 slave node
expansion) 703H
(node No. 4)
Receive 704H
705H 8-byte transfer
data area for X240 to X27F Node No. 3 status

node No.2 (For future 706H Node No. 3

(64 points) expansion) C00H

Receive C01H
Transmit data
data area for C02H
X280 to X2BF C03H
node No.4
(64 points)
FROM B00H
Receive X2C0 to X2DF B01H
data area for Receive data
X2E0 to X2FF B02H
node No.3
(64 points)
(For future expansion) B03H

Transmit data
Transmit TO 900H Node No. 2 Remote I/O (node No. 3)
data area for Y200 to X23F 901H 16-point input
node No.1 (For future TO 902H Node No. 4
expansion)
(64 points) 903H Status
Transmit Y240 to X247 904H I00 to I15
data area for 905H Node No. 3 Input 00 to input 15
Y248 to X27F
node No.2 (For future
(64 points) expansion) Dummy output
Transmit
data area for Y280 to X2BF
node No.4
Remote I/O (node No. 2)
(64 points) TO
Y2C0 to X2CF 8-point input
Transmit
data area for Y2D0 to X2FF
(For future O00 to O07
node No.3 expansion) Output 00 to output 07
(64 points)

500H
D1000 to D1251
I/O address I/O address
information FROM area for
to
Based on this master
information,
execute FROM/TO
function
instructions.
5FBH

7 - 35 7 - 35
7 PROGRAMMING FOR EXECUTING THE MASTER FUNCTION
MELSEC-Q

The following explains a sequence program example for this case.

(1) Device list

Reference
Device Description
section
M11 I/O Communication Start Command ―
X01 I/O Communicating 3.3.2 (2)
X200 to X23F 1st slave node: Node No.1
X240 to X27F Master Function 2nd slave node: Node No.2
3.4.6
X280 to X2BF Receive Data 3rd slave node: Node No.4
X2C0 to X2FF 4th slave node: Node No.3
Y11 I/O Communication Request 3.3.2 (2)
Y200 to Y23F 1st slave node: Node No.1
Y240 to Y27F Master Function 2nd slave node: Node No.2
Y280 to Y2BF Transmit Data 3rd slave node: Node No.4 3.4.6
Y2C0 to Y2FF 4th slave node: Node No.3
D1000 to D1251 I/O Address Area for Master Function

(2) Program example

Setting parameters for master function (See Section 7.3.)

M11 Sets I/O Communication

Request to ON.
Reads I/O Address Area
for Master Function.

Reads receive data according to

information in I/O Address Area
for Master Function.

Performs controls based on the receive data read out.

Writes transmit data according to

information in I/O Address Area
for Master Function.

7 - 36 7 - 36
 8 PROGRAMMING FOR EXECUTING THE SLAVE FUNCTION
MELSEC-Q

8 PROGRAMMING FOR EXECUTING THE SLAVE FUNCTION

This chapter explains programming for executing the slave function.

When applying the program examples introduced in this chapter to the actual system,
make sure to examine the applicability and confirm that it will not cause system control
problems.

8.1 System Configuration

The explanation of the programs in this chapter is based on the system shown in
Section 7.2.
Note that the transmit/receive data of the QJ71DN91 (slave node) are assigned to the
following devices.
Item Device
Receive data X200 to X23F
Transmit data Y200 to Y23F

8.2 Parameters for Slave Function

POINT
To change I/O points for slave function, parameters for slave function must be set.
However, for the I/O points of the QJ71DN91 (slave node) shown in Chapter 7,
parameters for slave function need not be set because default values are used.

(1) Settings
The following table shows the slave function parameters that are to be set in the
program example.
For details of the slave function parameters, refer to Section 3.4.9.
For saving parameters to a flash ROM, refer to (2) in this section.
Buffer memory
Item Set value
address (Hex.)
8 060EH Slave Function Receive-Bytes (Input Size) Setting Area K16 (16 bytes)
060FH Slave Function Transmit-Bytes (Output Size) Setting Area K16 (16 bytes)

8-1 8-1
8 PROGRAMMING FOR EXECUTING THE SLAVE FUNCTION
MELSEC-Q

(2) Operation flow of parameter saving to flash ROM

The following explains the operation flow in the case of saving parameters to the
flash ROM.
When using the utility package, refer to Section 8.2.1 (2).
When not using the utility package, refer to Section 8.2.2 (2).
I/O Communication Request (Y11) 3)

I/O Communicating (X01)

Auto Configuration Request (Y15) OFF 3)

4) 8)
Request for Saving Parameters
to Flash ROM (Y17)
5)
Saving Parameters to
Flash ROM (X06)
7)
Parameters Saved to
Flash ROM (X07)
6)
Error Set Signal for
Slave Function (X08)

Error Information for MOV/FROM

Slave Function (0601H) instruction
2)
MOV/TO
Parameter Area Select Bit (0630H) instruction
1)
MOV/TO Parameter
Parameters instruction check

Flash ROM

1) Set parameters in the following buffer memory areas:

• Parameters for Slave Function (address : 060EH, 060FH)
• Auto Communication Start Setting (address : 0631H)
2) Specify a parameter saving area in Parameter Area Select Bit
(address: 0630H). 8
3) Set I/O Communication Request (Y11) and Auto Configuration
Request (Y15) to OFF.
4) When Request for Saving Parameters to Flash ROM (Y17) is set to
ON, parameters are checked.
5) If the parameter check is completed successfully, saving the
parameters to the flash ROM is started, and Saving Parameters to
Flash ROM (X06) is set to ON.
6) If the parameter check has failed, the ERR. LED lights up and Error
Set Signal for Slave Function (X08) is set to ON.
Check the error code in Error Information for Slave Function (address:
0601H), and take corrective actions.
7) Upon completion of parameter saving to the flash ROM, Parameters
Saved to Flash ROM (X07) is set to ON.
8) When Request for Saving Parameters to Flash ROM (Y17) is set to
OFF, Saving Parameters to Flash ROM (X06) and Parameters Saved
to Flash ROM (X07) are set to OFF.
8-2 8-2
8 PROGRAMMING FOR EXECUTING THE SLAVE FUNCTION
MELSEC-Q

8.2.1 Program example using the utility package

(1) Setting example

(a) Setting the parameters for slave function.
Clicking the Parameter Area Monitor/Test button on the [Monitor/Test]
screen will display the [Parameter Area Monitor/Test] screen.
For information on how to display the [Monitor/Test] screen, refer to Section
6.3.

1)

2)

3)

1) Enter "16" for "Slave Function Input Sizes Setting Area" and "Slave
Function Output Sizes Setting Area".
Select "16" Execute test button
2) To start I/O communication automatically at power-up, set "Start" for
"Auto Communication Start Setting".
Select "Start" Execute test button
3) Click the Close button.

(b) Saving the parameters to the flash ROM (Refer to (2) in this section.)

8-3 8-3
8 PROGRAMMING FOR EXECUTING THE SLAVE FUNCTION
MELSEC-Q

(2) When saving parameters to flash ROM

Clicking the Flash ROM Save button on the [Monitor/Test] screen will display the
[5. Save Parameters to Flash ROM.] or [Save Parameters to Flash ROM] screen.
(The same setting details are displayed on the both screens.)
Follow the setting instructions.
POINT
Save the parameters in the buffer memory to a flash ROM. Otherwise, they are
cleared when the power is turned OFF or the CPU module is reset.

1)

2)

3)

1) When the current value for "Y11: I/O Communication Request" is "I/O
Comm. Request", set "I/O Comm. Stop Request".
Select "I/O Comm. Stop Request" Execute test button
2) When the current value for "X01: I/O Communicating" is "I/O
Communicating", set "I/O Comm. Request" for "Y11: I/O
Communication Request".
Select "I/O Comm. Request" Execute test button
Then, set "I/O Comm. Stop Request" for "Y11: I/O Communication
Request".
Select "I/O Comm. Stop Request" Execute test button
Check that the current value for "X01: I/O Communicating" was
changed to "I/O Comm. Stop".
3) When the current value for "Y15: Auto Configuration Request" is
"Config. Request", set "OFF" for "Y15: Auto Configuration Request".
Select "OFF" Execute test button
8-4 8-4
8 PROGRAMMING FOR EXECUTING THE SLAVE FUNCTION
MELSEC-Q

4)

5)
6)

7)

8)

9)

10)

4) Select the parameter saving area.

When saving the parameters for slave function and the auto
communication start setting, set "Slave/Auto Comm." for "Parameter
Saving Area Selection".
Select "Slave/Auto Comm." Execute test button
5) Set "Save Request" for "Y17: Request for Saving Parameters to Flash
ROM".
Select "Save Request" Execute test button
6) Parameter saving to the flash ROM is started, and "Saving" is
displayed for "X06: Saving Parameters to Flash ROM".
7) Upon completion of the saving, "Save Completed" is displayed for
"X07: Parameters Saved to Flash ROM".

8-5 8-5
8 PROGRAMMING FOR EXECUTING THE SLAVE FUNCTION
MELSEC-Q

8) If parameter check has failed, "Error Occurred" is displayed for "X08:

Error Set Signal for Slave Function".
Check the error code in the current value column of "Error Information
for Slave Function", and take corrective actions. (Refer to Section
9.2.1.)
9) After completing the parameter saving to the flash ROM, set "OFF" for
"Y17: Request for Saving Parameters to Flash ROM".
Select "OFF" Execute test button
10) Click the Close button.

POINT
Since the number of writes to flash ROM is limited, use Request for Saving
Parameters to Flash ROM (Y17) only when creating or changing parameters.

(3) When clearing parameters from the flash ROM

Refer to Section 7.3.1 (4).

8-6 8-6
8 PROGRAMMING FOR EXECUTING THE SLAVE FUNCTION
MELSEC-Q

8.2.2 Program example not using the utility package

(1) Setting example

(a) Device list
Reference
Device Description
section
M30 Parameter Setting Command for Slave Function
X21 I/O Communicating —
Y31 I/O Communication Request
Slave Function Receive-Bytes (Input Sizes) Setting
D50
Area
3.4.9
Slave Function Transmit-Bytes (Output Sizes) Setting
D51
Area

(b) Program example

Parameters for slave function
Sets 16 bytes for input size
of slave function.
Sets 16 bytes for output size
of slave function.
Writes parameters to buffer memory.

Save parameters to flash ROM. (See (2).)

8-7 8-7
8 PROGRAMMING FOR EXECUTING THE SLAVE FUNCTION
MELSEC-Q

(2) When saving parameters to a flash ROM

(a) Device list
Reference
Device Description
section
M402 Parameter Saving Command
—
M403 Saving Parameters to Flash ROM Flag
X21 I/O Communicating
X26 Saving Parameters to Flash ROM
X27 Parameters Saved to Flash ROM
3.3.2 (6)
Y31 I/O Communication Request
Y35 Auto Configuration Request
Y37 Request for Saving Parameters to Flash ROM
D52 Parameter Area Select Bit 3.4.13
D53 Auto Communication Start Setting 3.4.14

(b) Program example

Setting parameters for slave function (See (1).)

Parameter saving
Parameter Area Select Bit
Slave/Auto Comm.
Auto Communication Start Setting
Start
Writes parameters to buffer memory.
Sets Request for Saving Parameters
to Flash ROM to ON.
Saving parameters to flash ROM

Saving parameters to flash ROM completed

Sets Request for Saving Parameters
to Flash ROM to OFF.

POINT
(1) Save the parameters in the buffer memory to a flash ROM. Otherwise, they are
cleared when the power is turned OFF or the CPU module is reset.
(2) Since the number of writes to flash ROM is limited, use Request for Saving
Parameters to Flash ROM (Y17) only when creating or changing parameters.

8-8 8-8
8 PROGRAMMING FOR EXECUTING THE SLAVE FUNCTION
MELSEC-Q

8.3 I/O Communication Function

8.3.1 Program example using the utility package

(1) Device list

Reference
Device Description
section
M31 I/O Communication Start Command —
X21 I/O Communicating 3.3.3 (2)
*1
X200 to X23F Slave Function Receive Data 3.4.10
Y31 I/O Communication Request 3.3.3 (2)
1
Y200 to Y23F* Slave Function Transmit Data 3.4.10

*1: Devices used in the auto refresh function of GX Configurator-DN.

(2) Operation in the utility package

(a) Auto refresh setting (Refer to Section 6.4.)
1) Slave Function Receive Data………………X200 to X23F
2) Slave Function Transmit Data……………...Y200 to Y23F

1)
2)

(b) Writing intelligent function module parameters (Refer to Section 6.3.3.)

Write parameters of the intelligent function modules (auto refresh settings)
to the CPU module.
Perform this operation from the screen for selecting a target intelligent
function module.

8-9 8-9
8 PROGRAMMING FOR EXECUTING THE SLAVE FUNCTION
MELSEC-Q

(3) Program example

Setting parameters for slave function (See Section 8.2.)

I/O communication function

Sets I/O Communication
Request to ON.

Input data processing program

Output data processing program

POINT
To ensure consistency of transmit/receive data of multiple words, take a measure
such as providing a handshake area at the end of transmit/receive data to check
the data transfer.
For the program example, refer to Section 7.1 (4).

8 - 10 8 - 10
8 PROGRAMMING FOR EXECUTING THE SLAVE FUNCTION
MELSEC-Q

8.3.2 Program example not using the utility package

(1) Device list

Reference
Device Description
section
M31 I/O Communication Start Command —
X21 I/O Communicating 3.3.3 (2)
X200 to X23F Slave Function Receive Data 3.4.10
Y31 I/O Communication Request 3.3.3 (2)
Y200 to Y23F Slave Function Transmit Data 3.4.10

(2) Program example

Setting parameters for slave function (See Section 8.2.)

I/O communication function

Sets initial transmit data values.
Sets I/O Communication
Request to ON.
Reads receive data.

Input data processing program

Output data processing program

Writes transmit data.

POINT
To ensure consistency of transmit/receive data of multiple words, take a measure
such as providing a handshake area at the end of transmit/receive data to check
the data transfer.
For the program example, refer to Section 7.1 (4).

8 - 11 8 - 11
8 PROGRAMMING FOR EXECUTING THE SLAVE FUNCTION
MELSEC-Q

8.4 Obtaining Error Information

This section explains an example of a sequence program that obtains the error
information for the slave function.

(1) Device list

Reference
Device Description
section
M51 Error Reset Command —
X28 Error Set Signal for Slave Function
3.3.3 (4)
Y38 Error Reset Request for Slave Function
D500 Error Information for Slave Function 3.4.8

(2) Program example

Reads error information
for slave function from
buffer memory.
Error handling program

Sets Error Reset Request

for Slave Function to ON.

Sets Error Reset Request

for Slave Function to OFF.

8 - 12 8 - 12
 9 TROUBLESHOOTING
MELSEC-Q

9 TROUBLESHOOTING

This chapter describes the errors that may occur while using the QJ71DN91 as well as
their troubleshooting procedures.
This chapter contains the following information:
Section 9.1 Problem Identification
Troubleshooting procedures are shown according to symptoms.
Section 9.2 Error Codes
Troubleshooting procedures are shown according to error codes.

9-1 9-1
9 TROUBLESHOOTING
MELSEC-Q

9.1 Problem Identification

This section explains checking procedures and actions to be taken when a problem
occurs.

9.1.1 Checking the LEDs

Problem occurred

Set Mode switch in range of 0 to 8

Mode switch set in 0 to 8? No
and reset.
Yes

MS LED lit green? (MS LED is OFF.)

No
Power ON the module.
Yes

NS LED lit? No Turn ON the network power (24V).

Yes

NS LED lit green

No
or flashing green?

NS LED lit red? No

Yes Yes NS LED flashing red?

Check if: Yes

Node No. is within the range of 0 to 63.
The same node No. exists on the network.
I/O communication with one or more
The same communication speed is set for
slave nodes has failed.
the entire network.
Check 1B1H "Error Information for
Terminating resistors are connected to both ends of
Master Function" or 601H "Error
the trunk line.
Information for Slave Function"
Check for an error code.
in the buffer memory for an error code,
If the above check results are normal, check the entire
and take corrective actions.
network condition such as noise or installation.

ERR.LED lit? No Set I/O Communication Request (Y11) to ON.

Yes

Parameter error has occurred.

Check 1B1H "Error Information for 9
Master Function" or 601H "Error
Information for Slave Function" in
the buffer memory for an error code,
and take corrective actions.

9-2 9-2
9 TROUBLESHOOTING
MELSEC-Q

9.1.2 When unable to communicate with all slave nodes (when using master function)

Unable to communicate with all slave nodes.

(NS LED is flashing green or lit red.)

Mode switch set in 0 to 2 or 6 to 8? No Set Mode switch in range of 0 to 2

or 6 to 8 and reset.

Yes

Is DeviceNet cable connected to

No Connect DeviceNet cable.
QJ71DN91s connector securely?

Yes

Is network power supply ON? No Turn ON the network power supply.

Yes

Same communication
speed set for all nodes? No Set same communication speed for all nodes.

Yes

Terminating resistors connected? No Connect terminating resistors.

Yes
Is there
a slave node having same node No. as Yes Eliminate node No. duplication.
QJ71DN91?

No

Have the parameters

No
been written?

Yes

Are the parameters

matched with hardware configuration of the No Configure and write correct parameters.
actual slave nodes?

Yes

I/O Communication
No Set I/O Communication Request (Y11) to ON.
Request (Y11) set to ON?

Yes

Is there an error code? Yes Take corrective actions according to

the error code.

No

Check the entire network condition such

as noise or installation.

9-3 9-3
9 TROUBLESHOOTING
MELSEC-Q

9.1.3 When unable to communicate with a specific slave node (when using master function)

Unable to communicate with a specific slave node.

(NS LED is flashing red.)

Is the slave node powered ON? No Power ON the slave node.

Yes
Is DeviceNet
cable connected to the slave no No Connect DeviceNet cable securely.
securely?

Yes

Is comm. speed same as other nodes? No Set the same communication speed.

Yes

Node No. duplicated? No Eliminate node No. duplication.

Yes

Is the
slave node set with parameters? No

Yes
Is the
parameter for node No. same as the No
actual one?
Yes

Set as reserved node? Yes

No
Specified
connection type matched with the slave No
node spec?

Yes

UCMM support
and message group matched with the No
slave node spec?
Yes

Value set
for watchdog timeout action matched with No
the slave node spec?

Yes

I/O configuration
parameters matched with the actual No
configuration?

Yes

Production inhibit time too short? Yes

No

Production inhibit time too long? Yes

No

Have the parameters been written? No Configure and write correct parameters.

Yes
Yes Take corrective actions according
Is there an error code?
to the error code.
No
Check the entire network condition
such as noise or installation.

9-4 9-4
9 TROUBLESHOOTING
MELSEC-Q

9.1.4 When unable to communicate with master node (when using slave function)

Unable to communicate with master node.

(NS LED is flashing green or lit red.)

Mode switch set in 3 to 8? No Set Mode switch in range of 3 to 8 and reset.

Yes

Is DeviceNet
Connect DeviceNet cable securely.
cable connected to QJ71DN91's No
connector securely

Yes

Is network power supply ON? No Turn ON the network power supply.

Yes

Same communication speed No Set same communication speed for all nodes.
set for all nodes?

Yes

Terminating resistors connected? No Connect terminating resistors.

Yes

Is there
a slave node having same node No. as Yes Eliminate node No. duplication.
QJ71DN91?
No

I/O points for

No Set correct I/O points according to the
slave function matched with parameter settings
master node settings.
of master node?

Yes

Polling and UCMM

support (group 3) set with parameter No Set polling and UCMM support (group 3)
for master node? for master node.

Yes

I/O Communication Request (Y11) No Set I/O Communication Request (Y11) to ON.
set to ON?
Yes

Take corrective actions according to

Is there an error code? Yes the error code.

No

Check the entire network condition

such as noise or installation.

9-5 9-5
9 TROUBLESHOOTING
MELSEC-Q

9.1.5 Troubleshooting for other cases

Symptom Check Action

Are the following output signals ON?
Set the output signals to OFF, and then set
• I/O Communication Request (Y11)
Auto Configuration Request (Y15) to OFF and
• Request for Saving Parameters to Flash
ON again.
ROM (Y17)
• Set "Not start" in Auto Communication Start
Auto configuration is not
Setting (address: 0631H), and save the
executed.
• Is "Start" set in Auto Communication Start parameters to a flash ROM.
Setting (address: 0631H)? • Setting I/O Communication Request (Y11) to
(I/O Communicating is ON?) ON and then OFF will stop I/O
communication, and thereby I/O
Communicating (X01) is set to OFF.
• Are the slave nodes powered ON?
Check that the slave nodes and network are
• Is the network powered ON?
powered up and the wiring is correct.
• Is the wiring correct?
• If the target slave node is the QJ71DN91, When the auto communication start setting is
check if "Start" is set in Auto Communication not set up for the target slave node
Start Setting (address: 0631H) or if I/O (QJ71DN91), set I/O Communication Request
Unable to obtain expected Communication Request (Y11) is ON. (Y11) to OFF and then ON.
parameters by auto The slave node settings detected by auto
configuration. configuration are stored in order of node No.
• Are the slave nodes set in order of node No?
Correct values in Parameters for Master
Function (address: 01D4H to 03CFH).
Referring to the manual for each slave node,
• Are the connection types and I/O points check available connection types and I/O
correct? points. Correct values in Parameters for Master
Function (address: 01D4H to 03CFH).
Are the following output signals ON? Set the output signals to OFF, and then set
• I/O Communication Request (Y11) Request for Saving Parameters to Flash ROM
• Auto Configuration Request (Y15) (Y17) to OFF and ON again.
• Set "Not start" in Auto Communication Start
Parameter saving/clearing Setting (address: 0631H), and save the
is not started. • Is "Start" set in Auto Communication Start parameters to a flash ROM.
Setting (address: 0631H)? • Setting I/O Communication Request (Y11) to
(I/O Communicating is ON?) ON and then OFF will stop I/O
communication, and thereby I/O
Communicating (X01) is set to OFF.
Check Parameter Area Select Bit (address:
Parameters are not 0630H), and set Request for Saving
• If the parameter saving area correct?
saved. Parameters to Flash ROM (Y17) to OFF and
then ON again.

9-6 9-6
9 TROUBLESHOOTING
MELSEC-Q

Symptom Check Action

• Set "Not start" in Auto Communication Start
Setting (address: 0631H), and save the
After power-up, I/O • Is "Start" set in Auto Communication Start parameters to a flash ROM.
communication starts Setting (address: 0631H)? • Setting I/O Communication Request (Y11) to
automatically. (I/O Communicating is ON?) ON and then OFF will stop I/O
communication, and thereby I/O
Communicating (X01) is set to OFF.

9-7 9-7
9 TROUBLESHOOTING
MELSEC-Q

9.2 Error Codes

This section describes error codes and respective corrective actions.

9.2.1 Communication error codes

A communication error code is stored in the high byte of Error Information for Master
Function (address: 01B1H) or Error Information for Slave Function (address: 0601H).
Read it when Error Set Signal for Master Function (X03) or Error Set Signal for Slave
Function (X08) is set to ON, and check the error details.
Communication error codes can be checked in System monitor of GX Developer.
(Refer to Section 9.3.)

(1) When the error-detected node No. (low byte of error information) is FFH
Error Detectability
Detected
code Description Action Master Slave
in:
(Hex.) function function
• Set the node No. within the range of 0 to
The node No. (MAC ID) value is out of
63.
36H QJ71DN91 range.
• Set the mode switch to any other than D
The mode switch value is out of range.
to F.
The node No. (MAC ID) is duplicated on
39H QJ71DN91 • Set a unique node No.
the network.
E0H QJ71DN91 Power is not supplied to the network. • Supply power to the network (DC24V).
Other modules cannot be identified on
E1H QJ71DN91 • Connect other modules to the network.
the network.
The node No. switches or mode switch • Restore the setting of the node No.
F0H QJ71DN91
has been changed during operation. switches or mode switch.

9-8 9-8
9 TROUBLESHOOTING
MELSEC-Q

(2) When the error-detected node No. (low byte of error information) is FEH
Error Detectability
Detected
code Description Action Master Slave
in:
(Hex.) function function
Zero (0) is set for both the input and • Set the input and output points according
02H QJ71DN91
output points of a slave node. to the slave node specifications.
The low byte of the slave node No. in the
03H QJ71DN91 • Set it within the range of 0 to 63.
buffer memory is out of range.
The high byte of the slave node No. in • Set it within the range of 01H to 04H, or to
04H QJ71DN91
the buffer memory is out of range. 80H.
The connection type in the buffer
05H QJ71DN91 • Set 0001H, 0002H, 0004H, or 0008H.
memory is out of range.
The same node No. has already been
06H QJ71DN91 set for a slave node in the buffer • Set unique node numbers for all nodes.
memory.
07H QJ71DN91 No slave node has been set. • Set at least one slave node.
The total input data length of all slave
08H QJ71DN91 • Reduce it to 512 bytes or less.
nodes is too long.
The total output data length of all slave
09H QJ71DN91 • Reduce it to 512 bytes or less.
nodes is too long.
The parameter value for the watchdog
0AH QJ71DN91 • Set 0000H, 0001H, 0002H, or 0003H.
timeout action is invalid.
The expected packet rate value in the • Change the setting so that the expected
0BH QJ71DN91 buffer memory is smaller than the packet rate value is greater than or equal
production inhibit time value. to the production inhibit time value.
• Save the parameters again.
Flash ROM checksum error (Parameters
0CH QJ71DN91 • Do not turn OFF the power or reset while
for Master Function area)
saving the parameters.
• Save the parameters again.
Flash ROM checksum error (Parameters
0DH QJ71DN91 • Do not turn OFF the power or reset while
for Slave Function area)
saving the parameters.
• Save the parameters again.
Flash ROM checksum error (Auto
0EH QJ71DN91 • Do not turn OFF the power or reset while
Communication Start Setting area)
saving the parameters.
• Clear all parameters again.
0FH QJ71DN91 Flash ROM all clear error • Do not turn OFF the power or reset while
clearing the parameters.
The number of input points per slave • Correct the number of input points per
10H QJ71DN91
node exceeds 256 bytes. slave node to 256 bytes or less.
The number of output points per slave • Correct the number of output points per
11H QJ71DN91
node exceeds 256 bytes. slave node to 256 bytes or less.
The production inhibit time value was set • Set the production inhibit time value to a
15H QJ71DN91
to 0 ms (set value 1) in cyclic. value other than 0 ms.
All slave nodes are set as reserved • Set the parameters according to the slave
16H QJ71DN91
nodes by parameters. nodes connected to the network.
The number of slave function receive
80H QJ71DN91 • Set it within the range of 0 to 128 bytes.
bytes is out of range.
The number of slave function transmit
81H QJ71DN91 • Set it within the range of 0 to 128 bytes.
bytes is out of range.
Both of the slave function transmit and • Set either of the transmit or receive bytes
82H QJ71DN91
receive bytes are set to 0. to any other than 0.

9-9 9-9
9 TROUBLESHOOTING
MELSEC-Q

Error Detectability
Detected
code Description Action Master Slave
in:
(Hex.) function function
• Set I/O points of slave nodes in
Parameters for Master Function.
When using both the master and slave
• Set transmit/receive bytes in Parameters
A0H QJ71DN91 functions, the number of I/O points is set
for Slave Function.
to 0 for both of them.
(Either of master or slave function values
must be set.)

9 - 10 9 - 10
9 TROUBLESHOOTING
MELSEC-Q

(3) When the error-detected node No. (low byte of error information) is other than
FFH and FEH
Error Detectability
Detected
code Description Action Master Slave
in:
(Hex.) function function
A network problem was detected after • Check that the cables are connected
01H QJ71DN91
communication was started. correctly.
• Check the entire network and slave node
states for MAC ID and baud rate setting,
1EH QJ71DN91 The slave node did not respond.
a failed slave node, or disconnection of a
terminating resistor.
• Read the communication error
A slave node responded with a non-
20H Slave node information, and take an appropriate
prescribed error.
action according to the error information.
• Read the communication error
A slave node responded with an error
23H Slave node information, and take an appropriate
when establishing a connection.
action according to the error information.
The input data size set with a parameter
• Check the slave node manual and set the
24H QJ71DN91 is different from the size for the actual
correct input data size.
slave node.
The output data size set with a
• Check the slave node manual and set the
25H QJ71DN91 parameter is different from the size for
correct output data size.
the actual slave node.
• Check the slave node manual, and
prevent any data of the function not
Response data of the function that is not supported by the QJ71DN91 from being
26H QJ71DN91 supported by the QJ71DN91 was sent from the slave node.
received. • Check the entire network and slave node
states for any fault such as disconnection
of a terminating resistor.
• Check the entire network and slave node
The connection is already in the
27H Slave node states for any fault such as disconnection
specified mode.
of a terminating resistor.
• Check the entire network and slave node
Unexpected invalid data was received
28H QJ71DN91 states for any fault such as disconnection
when the connection was established.
of a terminating resistor.
Connection has already been • Wait for a while, and reset the slave node
29H Slave node
established with that slave node. if the connection cannot be established.
The data length of a polling response is
• Check the entire network and slave node
different from the length of the data that
2AH QJ71DN91 states for any fault such as disconnection
was read from the slave node when a
of a terminating resistor.
connection was established.
When a polling response was divided • Check the entire network and slave node
2BH QJ71DN91 into several data units, the first data unit states for any fault such as disconnection
was received twice. of a terminating resistor.
When a polling response was divided • Check the entire network and slave node
2CH QJ71DN91 into several data blocks, data of an states for any fault such as disconnection
unexpected number was received. of a terminating resistor.
When a polling response was divided
• Check the entire network and slave node
into several data blocks, the second data
2DH QJ71DN91 states for any fault such as disconnection
block or later was received before the
of a terminating resistor.
first one.

9 - 11 9 - 11
9 TROUBLESHOOTING
MELSEC-Q

Error Detectability
Detected
code Description Action Master Slave
in:
(Hex.) function function
• The same node No. is set for two or more
slave nodes. Correct the duplicated
Two or more identical node numbers parameter settings.
3BH QJ71DN91
(MAC IDs) were detected in parameters. • A slave node having the same node No.
as that of this node exists in the
parameters.
• Check if the connection type value is
correct.
47H QJ71DN91 Incorrect connection type was specified.
• Read the communication error
information, and take appropriate actions.
• Check the entire network and slave node
The polling connection in the slave states for any fault such as disconnection
80H QJ71DN91
function has timed out. of a terminating resistor.
• Check the master node status.
A connection other than for explicit • Do not allocate any I/O connection other
81H QJ71DN91
messages and polling was allocated. than for polling.
The number of bytes received by polling
• Set the master node’s I/O points that
82H QJ71DN91 is greater than the max. number of
match the settings of the QJ71DN91.
receive points.

9 - 12 9 - 12
9 TROUBLESHOOTING
MELSEC-Q

9.2.2 Execution error codes of message communication (for the master function only)

An execution error code is stored in Message Communication Result (address: 0121H).

Read it when Message Communication Completion signal (X02) is set to ON, and
check the error details.

(1) When reading communication error information

Error
Detected
code Description Action
in:
(Dec.)
161 QJ71DN91 The specified slave node No. is other than 0 to 63. • Specify a slave node No. within the range of 0 to 63.

(2) When getting/setting attribute, or resetting

Error
Detected
code Description Action
in:
(Dec.)
• Referring to the slave node manual, check the
Resources required for the object to execute a
2 Slave node condition under which the slave node notifies this
requested service could not be used.
error, and take an appropriate action.
• Check whether or not the specified MAC ID, class ID,
instance ID and attribute ID are correct.
The requested service was not installed, or it was
8 Slave node • Referring to the slave node manual, check the
not defined for this object class/instance.
condition under which the slave node notifies this
error, and take an appropriate action.
• Check whether or not the specified MAC ID, class ID,
instance ID and attribute ID are correct.
9 Slave node Invalid attribute data were detected. • Referring to the slave node manual, check the
condition under which the slave node notifies this
error, and take an appropriate action.
• Check whether or not the specified MAC ID, class ID,
instance ID and attribute ID are correct.
The object is already placed in the mode/status that • Verify the current status by reading the attribute.
11 Slave node
is requested by the service. • Referring to the slave node manual, check the
condition under which the slave node notifies this
error, and take an appropriate action.
• Check whether or not the specified MAC ID, class ID,
instance ID and attribute ID are correct.
The object cannot execute the requested service in • Verify the current status by reading the attribute.
12 Slave node
the current mode/status. • Referring to the slave node manual, check the
condition under which the slave node notifies this
error, and take an appropriate action.
• Check whether or not the specified MAC ID, class ID,
instance ID and attribute ID are correct.
A request to change an attribute whose change is
14 Slave node • Referring to the slave node manual, check the
inhibited was received.
condition under which the slave node notifies this
error, and take an appropriate action.
• Check whether or not the specified MAC ID, class ID,
instance ID and attribute ID are correct.
15 Slave node Permission/privilege check failed. • Referring to the slave node manual, check the
condition under which the slave node notifies this
error, and take an appropriate action.

9 - 13 9 - 13
9 TROUBLESHOOTING
MELSEC-Q

Error
Detected
code Description Action
in:
(Dec.)
• Check whether or not the specified MAC ID, class ID,
instance ID and attribute ID are correct.
The requested service cannot be executed in the
16 Slave node • Referring to the slave node manual, check the
current device status.
condition under which the slave node notifies this
error, and take an appropriate action.
• Check the entire network and slave node states for
17 QJ71DN91 Slave node did not respond. any fault such as slave node failure, or disconnection
of a terminating resistor.
• Check whether or not the specified MAC ID, class ID,
instance ID and attribute ID are correct.
• In the case of set attribute, verify that the specified
Sufficient data was not provided to execute the
19 Slave node data is sufficient and the data length is correct.
specified operation.
• Referring to the slave node manual, check the
condition under which the slave node notifies this
error, and take an appropriate action.
• Check whether or not the specified MAC ID, class ID,
instance ID and attribute ID are correct.
20 Slave node The specified attribute is not supported. • Referring to the slave node manual, check the
condition under which the slave node notifies this
error, and take an appropriate action.
• Reduce the data returned from the slave node to 240
21 Slave node The service provided excessive data.
bytes or less.
• Check whether or not the specified MAC ID, class ID,
instance ID and attribute ID are correct.
The specified object does not exist in the slave
22 Slave node • Referring to the slave node manual, check the
node.
condition under which the slave node notifies this
error, and take an appropriate action.
• Check the entire network and slave node states for
50 QJ71DN91 The response data format is invalid. any fault such as disconnection of a terminating
resistor.
55 QJ71DN91 The specified slave node No. is other than 0 to 63. • Specify a node No. in the range of 0 to 63.
• Check the entire network and slave node states for
57 QJ71DN91 The divided data were received in incorrect order. any fault such as disconnection of a terminating
resistor.
The data length set in the buffer memory is 241 or
257 QJ71DN91 • Set the data length to 240 bytes or less.
more.
An invalid value was set as a command No. in the
• Set 0001H, 0101H, 0102H, 0201H, or FE**H as a
258 QJ71DN91 Message Communication Command area of the
command No.
buffer memory.
300 QJ71DN91 The own node is set offline. • Set Y11 to ON to set the own node online.
301 QJ71DN91 An error occurred during data queuing. • Perform a hardware test to check for hardware failure.
• Check the entire network and slave node states for
302 QJ71DN91 A timeout occurred while waiting for a response. any fault such as disconnection of a terminating
resistor.
• Check the entire network and slave node states for
303 QJ71DN91 An invalid response was obtained. any fault such as disconnection of a terminating
resistor.
The specified node No. is currently set for a • Set a node No. that is not being used for a reserved
304 QJ71DN91
reserved node. node.
• Send messages to address any other than the own
305 QJ71DN91 The message was sent to the own node.
node.

9 - 14 9 - 14
9 TROUBLESHOOTING
MELSEC-Q

Error
Detected
code Description Action
in:
(Dec.)
• Check whether the parameter value for the message
306 QJ71DN91 Failed to open a message connection.
group is set correctly or not.
• Verify that the transmit message can be responded by
317 Slave node The response data length is too long.
the slave node.

9 - 15 9 - 15
9 TROUBLESHOOTING
MELSEC-Q

9.2.3 General DeviceNet error codes of message communication (for the master function
only)

A general DeviceNet error code is stored in Message Communication Data (address:

0133H).
Read it when Message Communication Completion signal (X02) is set to ON, and
check the error details. (Valid when Communication error code is 35 (0023H).)

Error code
Error name Description
Hex. Dec.
0000H to 0001H 0 to 1 Reserved Reserved by DeviceNet.
The requested service could not be executed because there was no
0002H 2 Resource unavailable
space in the required resource.
0003H to 0007H 3 to 7 Reserved Reserved by DeviceNet.
The requested service is not supported. Or, the requested service is not
0008H 8 Service not supported
defined by the specified object class/instance.
0009H 9 Invalid attribute value The requested service had an error in the attribute data.
000AH 10 Reserved Reserved by DeviceNet.
The specified object has already been changed into the requested
000BH 11 Already in requested mode/state
mode/status.
The specified object was not in the state that could execute the requested
000CH 12 Object state conflict
service.
000DH 13 Reserved Reserved by DeviceNet.
000EH 14 Attribute not settable The requested setup service specified an unchangeable attribute.
000FH 15 Privilege violation The service requester did not have the access privilege.
The specified device was not in the state that could execute the
0010H 16 Device state conflict
requested service.
The response data length exceeded the data length that can be
0011H 17 Reply data too large
processed.
0012H 18 Reserved Reserved by DeviceNet.
The requested service did not provide sufficient data to execute
0013H 19 Not enough data
processing.
0014H 20 Attribute not supported The requested service specified an undefined attribute.
0015H 21 Too much data The requested service includes invalid data.
0016H 22 Object does not exist The requested service specified an unimplemented object.
0017H 23 Reserved Reserved by DeviceNet.
The attribute data of this object had not been saved before this service
0018H 24 No stored attribute data
was requested.
The attribute data of this object was not saved due to an error that
0019H 25 Store operation failure
occurred during the save operation.
001AH to 001EH 26 to 30 Reserved Reserved by DeviceNet.
A vender-specific error occurred. A specific error occurred is indicated in
the "Additional error code" area (0134H) of the error response. This error
001FH 31 Vendor specific error
code can be used only when the error codes shown in this table and
object class definitions do not apply to the corresponding error.
The requested service had a parameter error. This code can be used
only when the parameter satisfies neither the requirements of the
0020H 32 Invalid parameter
DeviceNet specifications nor the requirements defined by application
object specifications.
0021H to 0027H 33 to 39 Future extensions Reserved by DeviceNet.
An unimplemented class/instance/attribute was specified for the member
0028H 40 Invalid Member ID
ID of the requested service.
0029H 41 Member not settable The requested setup service specified an unchangeable member.
002AH to 00CFH 42 to 207 Reserved Reserved by DeviceNet.
This error code range is used to indicate errors specific to the object
class. The code in this range can be used only when any error code in
00D0H to 00FFH 208 to 255 Reserved for Object Class and service errors this table does not correctly explain the error that occurred. Using the
"Additional error code" area (0134H), the "General DeviceNet error code"
area (0133H) can be explained in detail.

9 - 16 9 - 16
9 TROUBLESHOOTING
MELSEC-Q

9.3 Checking the QJ71DN91 Status by System Monitor in GX Developer

Error codes and LED status can be checked by selecting the detailed information of
the QJ71DN91 from System monitor of GX Developer.

(a) Operation procedure

Select "Diagnostics" – "System monitor", choose a module, and then
"Module's Detailed Information" – "H/W Information."

(b) Product information

The serial No. and function version are displayed as shown below.

050220000000000-B
Function version B
Serial No. (first 5 digits) 05022

9 - 17 9 - 17
9 TROUBLESHOOTING
MELSEC-Q

(c) H/W LED Information

The LED status of the QJ71DN91 is displayed. (0: OFF, 1: ON)
ERR: Indicates the "ERR" LED status.
MS RED: Indicates the "MS (red)" LED status.
MS GREEN: Indicates the "MS (green)" LED status.
NS RED: Indicates the "NS (red)" LED status.
NS GREEN: Indicates the "NS (green)" LED status.

(d) H/W SW Information

The switch setting status of the QJ71DN91 is displayed.
NA: Displays the node No. setting status.
MODE: Displays the mode switch status.

9 - 18 9 - 18
 APPENDIXES
MELSEC-Q

APPENDIXES

Appendix 1 External Dimensions

The external dimensions of the QJ71DN91 are shown below.

QJ71DN91
RUN MS

NS
ERR.

NODE ADDRESS

5 6
4

2 3

7 8
X10
9
01

5 6
4

2 3
X1

7 8
98 (3.86)
MODE/DR 9
0 : M/125 01
1 : M/250
2 : M/500 M 78 9

4 56

AB E
3 : S/125 O

CD
4 : S/250 D

23
5 : S/500 E
F01
6 : D/125
7 : D/250
8 : D/500

QJ71DN91

90 (3.54) 12 27.4 (1.08)

(0.47)

(Unit: mm)

App

App - 1 App - 1
APPENDIXES
MELSEC-Q

Appendix 2 Functional upgrade of the QJ71DN91

The table below lists new functions of the QJ71DN91 and serial No. and software
version of the products that support each function.

First 5 digits of serial

Software version Reference
Upgraded item No.
section
QJ71DN91 GX Developer GX Configurator-DN
Node Communication Error Status
Version 1.15R or
(address: 01C0H to 01C3H/448 to 451) 04102 or later — 3.4.4 (3)
later
added.
Operation Setting Area for Bus Off Error
08032 or later — — 3.4.3 (5)
(address: 0632H/1586) added.
—: Available irrespective of serial No. and software version, : N/A

Appendix 3 Differences from the AJ71DN91/A1SJ71DN91

The following table lists the differences between the QJ71DN91 and the
AJ71DN91/A1SJ71DN91.
Model name
QJ71DN91 AJ71DN91/A1SJ71DN91
Function
DeviceNet master function and DeviceNet
DeviceNet master/slave function DeviceNet master function only
slave function
Number of I/O points of the DeviceNet
Input 4096 points, output 4096 points Input 2048 points, output 2048 points
master function
Auto configuration function Available Not available
Auto refresh function with programmable
Available (requires GX Configurator-DN) Not available
controller CPU
Constant scan Available Not available
Hardware test/communication test function Available Not available
3 methods
2 methods
• Setting with sequence programs
Parameter setting method • Setting with sequence programs
• Setting with GX Configurator-DN
• Setting with configuration software
• Setting with the auto configuration function

App

App - 2 App - 2
APPENDIXES
MELSEC-Q

Appendix 4 Parameter Setting Sheet (For the Master Function)

Buffer memory
Item Description Set value
address (Hex.)
Specify a value to make the link scan time constant.
01D7H Constant scan
(Setting range: 0 to 65535ms (FFFFH))

[ th slave node]
Buffer memory
Item Description Set value
address (Hex.)
Low byte: Node No. of th slave node (MAC ID)
00H to 3FH (0 to 63)
High byte: 01H Node that supports UCMM and uses any of
message groups 3, 2, and 1.
01D8H + ( - 1) 8 Node No. and message group 03H Node that supports UCMM and uses message
group 1
04H Node that does not support UCMM (Group 2 only
server)
80H Reserved node
Select a connection type for I/O communication.
0001H = Polling
01D9H + ( - 1) 8 Connection type 0002H = Bit strobe
0004H = Change of state
0008H = Cyclic
Low byte: Number of input byte modules
01DAH + ( - 1) 8 Number of byte modules High byte: Number of output byte modules (set in hexadecimal)
Eight bit modules (8 points) are counted as one byte module.
Low byte: Number of input word modules
01DBH + ( - 1) 8 Number of word modules
High byte: Number of output word modules (set in hexadecimal)
Low byte: Number of input double-word modules
Number of double-word
01DCH + ( - 1) 8 High byte: Number of output double-word modules (set in
modules
hexadecimal)
Set an expected packet rate for the slave node.
(Setting range: 0 to 65535 ms (FFFFH))
01DDH + ( - 1) 8 Expected packet rate
0000H: 200ms (Default)
Other than 0000H: Set value – 1 (ms)
Set an action for watchdog timeout of the slave node.
0000H: Equivalent to the following Timeout (Default)
01DEH + ( - 1) 8 Watchdog timeout action 0001H: Timeout
0002H: Auto Delete
0003H: Auto Reset
Set a production inhibit time.
(Setting range: 0 to 65535ms (FFFFH))
01DFH + ( - 1) 8 Production inhibit time
0000H: 10ms (Default)
Other than 0000H: Set value –1 (ms)
When setting parameters, use a copy of this sheet.

App - 3 App - 3
APPENDIXES
MELSEC-Q

Appendix 5 Parameter Setting Sheet (For the Slave Function)

Buffer memory
Item Description Set value
address (Hex.)
Slave function receive-bytes Set a size of I/O data that can be received for the slave function.
060EH
(input size) setting area (Setting range: 0 to 128 bytes, Default: 8 bytes)
Slave function transmit-bytes Set a size of I/O data that can be sent for the slave function.
060FH
(output size) setting area (Setting range: 0 to 128 bytes, Default: 8 bytes)

App - 4 App - 4
APPENDIXES
MELSEC-Q

Appendix 6 List of Communication Parameters of Slave Nodes from Various Manufactures

The following table lists an example of parameter setting for communicating with slave
nodes from various manufacturers. For more details on the parameter settings, please
contact each manufacturer.
Set value (values in parentheses are for the case of setting with sequence programs) Remarks
No. of byte No. of word No. of double- Watch-
Expected Production
Name of Connection modules modules word modules dog Message
Model Name Packet Inhibit UCMM
manufacturer type Timeout group
Output Input Output Input Output Input Rate Time
Action
DeviceNet
00H to 00H to 200ms Timeout 10ms
QJ71DN91 master/slave Polling (H1) 00H 00H 00H 00H Yes 3
80H 80H (K201) (H1) (H0)
Mitsubishi module
Electric A500 Series
Corporation inverter 1000ms Timeout 10ms
FR-A5ND Polling (H1) 04H 04H 00H 00H 00H 00H Yes 3
DeviceNet (K1001) (H1) (K11)
option
1000ms 10ms
Polling (H1)
(K1001) (K11)
1000ms 10ms
Flex I/O Bit strobe (H2)
(K1001) Timeout (K11)
1794ADN DeviceNet 00H 02H 00H 00H 00H 00H Yes 3
Rockwell Change-of- 0ms (H1) 0ms
adapter
Automation state (H4) (H0) (H0)
Japan Co., 30ms 25ms
Cyclic (H8)
Ltd. (K31) (K26)
Flex I/O input
1794-IB16 — 02H 02H 00H 00H 00H 00H — — — — —
module
1794- Flex I/O output
— 02H 02H 00H 00H 00H 00H — — — — —
OB16 module
DRT1- CompoBus/D Polling (H1)/ 1000ms Timeout 10ms
00H 01H 00H 00H 00H 00H No —
ID08 8-point input bit strobe (H2) (K1001) (H1) (K11)
DRT1- CompoBus/D Polling (H1)/ 1000ms Timeout 10ms
00H 02H 00H 00H 00H 00H No —
ID16 16-point input bit strobe (H2) (K1001) (H1) (K11)
DRT1- CompoBus/D 1000ms Timeout 10ms
Polling (H1) 01H 00H 00H 00H 00H 00H No —
OD08 8-point output (K1001) (H1) (K11)
Omron DRT1- CompoBus/D 1000ms Timeout 10ms
Polling (H1) 02H 00H 00H 00H 00H 00H No —
Corporation OD16 16-point output (K1001) (H1) (K11)
CompoBus/D
DRT1- Polling (H1)/ 1000ms Timeout 10ms
4-point analog 00H 00H 00H 04H 00H 00H No —
AD04 bit strobe (H2) (K1001) (H1) (K11)
input
CompoBus/D
DRT1- 1000ms Timeout 10ms
2-point analog Polling (H1) 00H 00H 02H 00H 00H 00H No —
DA02 (K1001) (H1) (K11)
output
DeviceNet
SX5D- 1000ms Timeout 10ms
16-point digital Polling (H1) 00H 02H 00H 00H 00H 00H No —
SBN16S (K1001) (H1) (K11)
input
DeviceNet
SX5D- 1000ms Timeout 10ms
IDEC (Izumi) 16-point digital Polling (H1) 02H 00H 00H 00H 00H 00H No —
SBT16K (K1001) (H1) (K11)
Corporation output
DeviceNet
SX5D- 8-point digital 1000ms Timeout 10ms
Polling (H1) 01H 01H 00H 00H 00H 00H No —
SBM16K input/8-point (K1001) (H1) (K11)
digital output

App - 5 App - 5
APPENDIXES
MELSEC-Q

Appendix 7 EDS File of the QJ71DN91

The following shows the EDS file of the QJ71DN91. The EDS file is stored in the CD-
ROM of GX Configurator-DN.
$ Mitsubishi Master/Slave EDS file
$ File Description Section
[File]
DescText="QJ71DN91 EDS file";
CreateDate=08-28-2000; $ created
CreateTime=12:00:00;
ModDate=08-28-2000; $ last change
ModTime=12:00:00;
Revision=1.1; $ Revision of EDS
$ Device Description Section
[Device]
VendCode=0xA1;
VendName="MITSUBISHI ELECTRIC CORPORATION";
ProdType=0x0C; $ Communication Adapter Device
ProdTypeStr="Communication Adapter"; $ Communication Adapter Device
ProdCode=4;
MajRev=1;
MinRev=1;
ProdName="QJ71DN91";
Catalog="";
$ I/O Characteristics Section
[IO_Info]
Default=0x0001; $ Poll Only
PollInfo=0x0001,
1, $ Default Input = Input1
1; $ Default Output = Output1
$ Input Connections
Input1= $ Input(Producing)
8, $ 8 byte
0, $ 0 bits are significant
0x0001, $ Poll Only Connection
"Input Data", $ Name
6, $ Path Size
"20 04 24 64 30 03", $ Assembly Object Instance 100
"Data"; $ Help
$ Output Connections
Output1= $ Output(Consuming)
8, $ 8 byte
0, $ 0 bits are significant
0x0001, $ Poll Only Connection
"Output Data", $ Name
6, $ Path Size
"20 04 24 65 30 03", $ Assembly Object Instance 101
"Data"; $ Help
[ParamClass]
MaxInst=0;
Descriptor=0x00;
CfgAssembly=0;
App - 6 App - 6
APPENDIXES
MELSEC-Q

MEMO

App - 7 App - 7
INDEX

Ind
[A] [F]
Add configuration .......................................... 3-35 Failed node detection setting ........................3-31
All configuration............................................. 3-35 Flash ROM setting .........................................6-32
Auto-configuring (X14) .................................. 3-12 Functions of the utility package .......................6-1
Auto configuration .........................................A-11 Function version...................................... 2-5,9-17
Auto configuration completion (X15) ............ 3-12
Auto communication start setting ................. 3-46 [G]
Auto configuration operation setting ............. 3-35 General DeviceNet error codes.....................9-16
Auto configuration request (Y15) .................. 3-12 GX Configurator-DN ................................ 2-4, 6-1
Auto refresh ................................................... 6-13 GX Developer ..................................................2-4

[B] [H]
Bit strobe.......................................................... 4-5 Hardware test...................................................5-8
Buffer memory list ......................................... 3-17 Hardware test item area ................................3-44
Bus error counter........................................... 3-27 Hardware test result area ..............................3-45
Bus off counter .............................................. 3-27 H/W test completion (X0B) ............................3-12
H/W test error detection (X0C) ......................3-12
[C] H/W test in progress (X0A)............................3-12
Change of state ............................................... 4-6
Checking the LEDs ......................................... 9-2 [I]
Communication error codes............................ 9-8 I/O address area for master function.............3-39
Communication test ...................................... 5-10 I/O communicating (X01)....................... 3-5, 3-13
Cyclic ............................................................... 4-7 I/O communication request (Y11) ......... 3-5, 3-13
I/O signal list.....................................................3-4
[D]
Differences from the AJ71DN91/A1SJ71DN91 [L]
.....................................................................App-2 LED indications ................................................5-6
Link scan time ................................................3-48
[E] List of communication parameters of slave nodes
EDS file........................................................App-6 from various manufacturers........................ App-5
Error codes ...................................................... 9-8
Error information for master function ............ 3-27 [M]
Error information for slave function............... 3-40 Master function (I/O communication function)
Error reset request for master function (Y13) ................................................................ 4-1, 7-35
......................................................................... 3-9 Master function communication status..........3-25
Error reset request for slave function (Y18) Master function receive data .........................3-37
....................................................................... 3-16 Master function transmit data ........................3-38
Error set signal for master function (X03)....... 3-9 Maximum link scan time ................................3-39
Error set signal for slave function (X08) ....... 3-16 Message communication command .............3-20
Execution error codes of message communication Message communication completion (X02)....3-8
....................................................................... 9-13 Message communication data ......................3-23
Expected packet rate .................................... 3-34 Message communication error signal (X05)
External dimensions....................................App-1 ..........................................................................3-8
Message communication function......... 4-8, 7-31
Message communication request (Y12) .........3-8

Index - 1 Index - 1
 [M] Slave function receive data ...........................3-42
Message communication result .................... 3-21 Slave function receive-bytes setting area .....3-41
Ind Minimum link scan time................................. 3-39 Slave function transmit data ..........................3-42
Mode switch..................................................... 5-8 Slave function transmit-bytes setting area....3-41
Mode switch No. .......................................... 3-43 Starting the intelligent function module utility
Model name................................................... 3-43 ........................................................................6-11
Module ready (X0F) ...................................... 3-11 System configuration .......................................2-1
Monitoring...................................................... 6-16
[T]
[N] Test.................................................................6-16
Node communication error status................. 3-30 Transmission delay........................................3-47
Node communication status ......................... 3-29
Node configuration status ............................. 3-29 [W]
Node fault status ........................................... 3-30 Watchdog timer error (X00) .............................3-5
Node No. ..................................................... 3-43 When unable to communicate with all slave nodes
Node No. switches .......................................... 5-7 ..........................................................................9-3
When unable to communicate with a specific slave
[O] node..................................................................9-4
Obtaining error information (master function) When unable to communicate with master node
....................................................................... 7-34 ..........................................................................9-5
Obtaining error information (slave function) Wiring ...............................................................5-9
....................................................................... 8-12
ODVA............................................................... 2-2
Operation overview ......................................... 6-9
Operation setting area for bus off error ........ 3-27

[P]
Parameters saved to flash ROM (X07) ........ 3-10
Parameter saving area selection area.......... 3-46
Parameters for the master function ....... 3-32, 7-9
Parameters for the slave function.......... 3-41, 8-1
Performance specifications............................. 3-1
Polling .............................................................. 4-4
Precautions for network power supply ......... 5-11
Present link scan time ................................... 3-39
Production inhibit time................................... 3-34
Programming precautions............................... 7-1

[R]
Request for saving parameters to flash ROM
(Y17) .............................................................. 3-10

[S]
Saving parameters to flash ROM (X06) ....... 3-10
Slave function (I/O communication function)
................................................................ 4-11, 8-9
Slave function communication status ........... 3-40

Index - 2 Index - 2
WARRANTY
Please confirm the following product warranty details before using this product.

1. Gratis Warranty Term and Gratis Warranty Range

If any faults or defects (hereinafter "Failure") found to be the responsibility of Mitsubishi occurs during use of the product
within the gratis warranty term, the product shall be repaired at no cost via the sales representative or Mitsubishi Service
Company.
However, if repairs are required onsite at domestic or overseas location, expenses to send an engineer will be solely at
the customer’s discretion. Mitsubishi shall not be held responsible for any re-commissioning, maintenance, or testing on-
site that involves replacement of the failed module.
[Gratis Warranty Term]
The gratis warranty term of the product shall be for one year after the date of purchase or delivery to a designated
place.
Note that after manufacture and shipment from Mitsubishi, the maximum distribution period shall be six (6) months, and
the longest gratis warranty term after manufacturing shall be eighteen (18) months. The gratis warranty term of repair
parts shall not exceed the gratis warranty term before repairs.
[Gratis Warranty Range]
(1) The range shall be limited to normal use within the usage state, usage methods and usage environment, etc.,
which follow the conditions and precautions, etc., given in the instruction manual, user's manual and caution labels
on the product.
(2) Even within the gratis warranty term, repairs shall be charged for in the following cases.
1. Failure occurring from inappropriate storage or handling, carelessness or negligence by the user. Failure caused
by the user's hardware or software design.
2. Failure caused by unapproved modifications, etc., to the product by the user.
3. When the Mitsubishi product is assembled into a user's device, Failure that could have been avoided if functions
or structures, judged as necessary in the legal safety measures the user's device is subject to or as necessary
by industry standards, had been provided.
4. Failure that could have been avoided if consumable parts (battery, backlight, fuse, etc.) designated in the
instruction manual had been correctly serviced or replaced.
5. Failure caused by external irresistible forces such as fires or abnormal voltages, and Failure caused by force
majeure such as earthquakes, lightning, wind and water damage.
6. Failure caused by reasons unpredictable by scientific technology standards at time of shipment from Mitsubishi.
7. Any other failure found not to be the responsibility of Mitsubishi or that admitted not to be so by the user.

2. Onerous repair term after discontinuation of production

(1) Mitsubishi shall accept onerous product repairs for seven (7) years after production of the product is discontinued.
Discontinuation of production shall be notified with Mitsubishi Technical Bulletins, etc.
(2) Product supply (including repair parts) is not available after production is discontinued.

3. Overseas service
Overseas, repairs shall be accepted by Mitsubishi's local overseas FA Center. Note that the repair conditions at each FA
Center may differ.

4. Exclusion of loss in opportunity and secondary loss from warranty liability

Regardless of the gratis warranty term, Mitsubishi shall not be liable for compensation of damages caused by any cause
found not to be the responsibility of Mitsubishi, loss in opportunity, lost profits incurred to the user by Failures of Mitsubishi
products, special damages and secondary damages whether foreseeable or not , compensation for accidents, and
compensation for damages to products other than Mitsubishi products, replacement by the user, maintenance of on-site
equipment, start-up test run and other tasks.

5. Changes in product specifications

The specifications given in the catalogs, manuals or technical documents are subject to change without prior notice.

6. Product application
(1) In using the Mitsubishi MELSEC programmable controller, the usage conditions shall be that the application will not
lead to a major accident even if any problem or fault should occur in the programmable controller device, and that
backup and fail-safe functions are systematically provided outside of the device for any problem or fault.
(2) The Mitsubishi programmable controller has been designed and manufactured for applications in general industries,
etc. Thus, applications in which the public could be affected such as in nuclear power plants and other power plants
operated by respective power companies, and applications in which a special quality assurance system is required,
such as for Railway companies or Public service purposes shall be excluded from the programmable controller
applications.
In addition, applications in which human life or property that could be greatly affected, such as in aircraft, medical
applications, incineration and fuel devices, manned transportation, equipment for recreation and amusement, and
safety devices, shall also be excluded from the programmable controller range of applications.
However, in certain cases, some applications may be possible, providing the user consults their local Mitsubishi
representative outlining the special requirements of the project, and providing that all parties concerned agree to the
special circumstances, solely at the users discretion.
Microsoft, Windows, Windows NT, and Windows Vista are registered trademarks of Microsoft Corporation in
the United States and other countries.
Pentium is a registered trademark of Intel Corporation in the United States and other countries.
Other company and product names herein are either trademarks or registered trademarks of their respective
owners.
SPREAD
Copyright (c) 1996 FarPoint Technologies, Inc.

SH(NA)-080143-J
 MITSUBISHI ELECTRIC

HEADQUARTERS EUROPEAN REPRESENTATIVES EUROPEAN REPRESENTATIVES EURASIAN REPRESENTATIVES

MITSUBISHI ELECTRIC EUROPE B.V. EUROPE GEVA AUSTRIA ALFATRADE Ltd. MALTA Kazpromautomatics Ltd. KAZAKHSTAN
German Branch Wiener Straße 89 99, Paola Hill Mustafina Str. 7/2
Gothaer Straße 8 AT-2500 Baden Malta- Paola PLA 1702 KAZ-470046 Karaganda
D-40880 Ratingen Phone: +43 (0)2252 / 85 55 20 Phone: +356 (0)21 / 697 816 Phone: +7 7212 / 50 11 50
Phone: +49 (0)2102 / 486-0 Fax: +43 (0)2252 / 488 60 Fax: +356 (0)21 / 697 817 Fax: +7 7212 / 50 11 50
Fax: +49 (0)2102 / 486-1120 TEHNIKON BELARUS INTEHSIS srl MOLDOVA
MITSUBISHI ELECTRIC EUROPE B.V. CZECH REPUBLIC Oktyabrskaya 16/5, Off. 703-711 bld. Traian 23/1
Czech Branch BY-220030 Minsk MD-2060 Kishinev
Avenir Business Park, Radlická 714/113a Phone: +375 (0)17 / 210 46 26 Phone: +373 (0)22 / 66 4242 MIDDLE EAST REPRESENTATIVES
CZ-158 00 Praha 5 Fax: +375 (0)17 / 210 46 26 Fax: +373 (0)22 / 66 4280
Phone: +420 - 251 551 470 ILAN & GAVISH Ltd. ISRAEL
ESCO DRIVES & AUTOMATION BELGIUM HIFLEX AUTOM.TECHNIEK B.V. NETHERLANDS 24 Shenkar St., Kiryat Arie
Fax: +420 - 251-551-471 Culliganlaan 3 Wolweverstraat 22 IL-49001 Petah-Tiqva
MITSUBISHI ELECTRIC EUROPE B.V. FRANCE BE-1831 Diegem NL-2984 CD Ridderkerk Phone: +972 (0)3 / 922 18 24
French Branch Phone: +32 (0)2 / 717 64 30 Phone: +31 (0)180 – 46 60 04 Fax: +972 (0)3 / 924 0761
25, Boulevard des Bouvets Fax: +32 (0)2 / 717 64 31 Fax: +31 (0)180 – 44 23 55
F-92741 Nanterre Cedex TEXEL ELECTRONICS Ltd. ISRAEL
Koning & Hartman b.v. BELGIUM Koning & Hartman b.v. NETHERLANDS 2 Ha´umanut, P.O.B. 6272
Phone: +33 (0)1 / 55 68 55 68 Woluwelaan 31 Haarlerbergweg 21-23
Fax: +33 (0)1 / 55 68 57 57 IL-42160 Netanya
BE-1800 Vilvoorde NL-1101 CH Amsterdam Phone: +972 (0)9 / 863 39 80
MITSUBISHI ELECTRIC EUROPE B.V. IRELAND Phone: +32 (0)2 / 257 02 40 Phone: +31 (0)20 / 587 76 00 Fax: +972 (0)9 / 885 24 30
Irish Branch Fax: +32 (0)2 / 257 02 49 Fax: +31 (0)20 / 587 76 05
Westgate Business Park, Ballymount CEG INTERNATIONAL LEBANON
INEA BH d.o.o. BOSNIA AND HERZEGOVINA Beijer Electronics AS NORWAY Cebaco Center/Block A Autostrade DORA
IRL-Dublin 24 Aleja Lipa 56 Postboks 487
Phone: +353 (0)1 4198800 Lebanon - Beirut
BA-71000 Sarajevo NO-3002 Drammen Phone: +961 (0)1 / 240 430
Fax: +353 (0)1 4198890 Phone: +387 (0)33 / 921 164 Phone: +47 (0)32 / 24 30 00 Fax: +961 (0)1 / 240 438
MITSUBISHI ELECTRIC EUROPE B.V. ITALY Fax: +387 (0)33/ 524 539 Fax: +47 (0)32 / 84 85 77
Italian Branch AKHNATON BULGARIA Sirius Trading & Services srl ROMANIA
Viale Colleoni 7 4 Andrej Ljapchev Blvd. Pb 21 Aleea Lacul Morii Nr. 3
I-20041 Agrate Brianza (MB) BG-1756 Sofia RO-060841 Bucuresti, Sector 6
Phone: +39 039 / 60 53 1 AFRICAN REPRESENTATIVE
Phone: +359 (0)2 / 817 6004 Phone: +40 (0)21 / 430 40 06
Fax: +39 039 / 60 53 312 Fax: +359 (0)2 / 97 44 06 1 Fax: +40 (0)21 / 430 40 02 CBI Ltd. SOUTH AFRICA
MITSUBISHI ELECTRIC EUROPE B.V. POLAND INEA CR d.o.o. CROATIA Craft Con. & Engineering d.o.o. SERBIA Private Bag 2016
Poland Branch Losinjska 4 a Bulevar Svetog Cara Konstantina 80-86 ZA-1600 Isando
Krakowska 50 HR-10000 Zagreb SER-18106 Nis Phone: + 27 (0)11 / 977 0770
PL-32-083 Balice Phone: +385 (0)1 / 36 940 - 01/ -02/ -03 Phone:+381 (0)18 / 292-24-4/5 Fax: + 27 (0)11 / 977 0761
Phone: +48 (0)12 / 630 47 00 Fax: +385 (0)1 / 36 940 - 03 Fax: +381 (0)18 / 292-24-4/5
Fax: +48 (0)12 / 630 47 01
AutoCont C.S. s.r.o. CZECH REPUBLIC INEA SR d.o.o. SERBIA
MITSUBISHI ELECTRIC EUROPE B.V. SPAIN Technologická 374/6 Izletnicka 10
Spanish Branch CZ-708 00 Ostrava-Pustkovec SER-113000 Smederevo
Carretera de Rubí 76-80 Phone: +420 595 691 150 Phone: +381 (0)26 / 617 163
E-08190 Sant Cugat del Vallés (Barcelona) Fax: +420 595 691 199 Fax: +381 (0)26 / 617 163
Phone: 902 131121 // +34 935653131
Fax: +34 935891579 B:ELECTRIC, s.r.o. CZECH REPUBLIC AutoCont Control s.r.o. SLOVAKIA
Mladoboleslavská 812 Radlinského 47
MITSUBISHI ELECTRIC EUROPE B.V. UK CZ-197 00 Praha 19 - Kbely SK-02601 Dolny Kubin
UK Branch Phone: +420 286 850 848, +420 724 317 975 Phone: +421 (0)43 / 5868210
Travellers Lane Fax: +420 286 850 850 Fax: +421 (0)43 / 5868210
UK-Hatfield, Herts. AL10 8XB
Phone: +44 (0)1707 / 27 61 00 Beijer Electronics A/S DENMARK CS MTrade Slovensko, s.r.o. SLOVAKIA
Fax: +44 (0)1707 / 27 86 95 Lykkegårdsvej 17 Vajanskeho 58
DK-4000 Roskilde SK-92101 Piestany
MITSUBISHI ELECTRIC CORPORATION JAPAN Phone: +45 (0)46/ 75 76 66 Phone: +421 (0)33 / 7742 760
Office Tower “Z” 14 F Fax: +45 (0)46 / 75 56 26 Fax: +421 (0)33 / 7735 144
8-12,1 chome, Harumi Chuo-Ku
Tokyo 104-6212 Beijer Electronics Eesti OÜ ESTONIA INEA d.o.o. SLOVENIA
Phone: +81 3 622 160 60 Pärnu mnt.160i Stegne 11
Fax: +81 3 622 160 75 EE-11317 Tallinn SI-1000 Ljubljana
Phone: +372 (0)6 / 51 81 40 Phone: +386 (0)1 / 513 8100
MITSUBISHI ELECTRIC AUTOMATION, Inc. USA Fax: +372 (0)6 / 51 81 49 Fax: +386 (0)1 / 513 8170
500 Corporate Woods Parkway
Vernon Hills, IL 60061 Beijer Electronics OY FINLAND Beijer Electronics AB SWEDEN
Phone: +1 847 478 21 00 Peltoie 37 Box 426
Fax: +1 847 478 22 53 FIN-28400 Ulvila SE-20124 Malmö
Phone: +358 (0)207 / 463 540 Phone: +46 (0)40 / 35 86 00
Fax: +358 (0)207 / 463 541 Fax: +46 (0)40 / 93 23 01
UTECO A.B.E.E. GREECE Omni Ray AG SWITZERLAND
5, Mavrogenous Str. Im Schörli 5
GR-18542 Piraeus CH-8600 Dübendorf
Phone: +30 211 / 1206 900 Phone: +41 (0)44 / 802 28 80
Fax: +30 211 / 1206 999 Fax: +41 (0)44 / 802 28 28
MELTRADE Ltd. HUNGARY GTS TURKEY
Fertő utca 14. Bayraktar Bulvari Nutuk Sok. No:5
HU-1107 Budapest TR-34775 Yukarı Dudullu-Ümraniye-İSTANBUL
Phone: +36 (0)1 / 431-9726 Phone: +90 (0)216 526 39 90
Fax: +36 (0)1 / 431-9727 Fax: +90 (0)216 526 3995
Beijer Electronics SIA LATVIA CSC Automation Ltd. UKRAINE
Ritausmas iela 23 4-B, M. Raskovoyi St.
LV-1058 Riga UA-02660 Kiev
Phone: +371 (0)784 / 2280 Phone: +380 (0)44 / 494 33 55
Fax: +371 (0)784 / 2281 Fax: +380 (0)44 / 494-33-66
Beijer Electronics UAB LITHUANIA
Savanoriu Pr. 187
LT-02300 Vilnius
Phone: +370 (0)5 / 232 3101
Fax: +370 (0)5 / 232 2980

MITSUBISHI
ELECTRIC Mitsubishi Electric Europe B.V. /// FA - European Business Group /// Gothaer Straße 8 /// D-40880 Ratingen /// Germany
FACTORY AUTOMATION Tel.: +49(0)2102-4860 /// Fax: +49(0)2102-4861120 /// [email protected] /// www.mitsubishi-automation.com