MODBUS(R) Interface Module User`s Manual

MITSUBISHI ELECTRIC
MELSEC System Q
Programmable Logic Controllers
User's Manual
QJ71MB91
MODBUS Interface Module
GX Configurator-MB
Art. no.: 168869
10 11 2005
SH(NA)-080578ENG
Version A
MITSUBISHI ELECTRIC
INDUSTRIAL AUTOMATION
SAFETY PRECAUTIONS
(Always read these instructions before using this product.)
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. 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".
Note that the
DANGER
Indicates that incorrect handling may cause hazardous conditions,
resulting in death or severe injury.
CAUTION
Indicates that incorrect handling may cause hazardous conditions,
resulting in medium or slight personal injury or physical damage.
CAUTION level may lead to a serious consequence according to the circumstances.
Always follow the instructions of both levels because they are important to personal safety.
Please save this manual to make it accessible when required and always forward it to the end user.
[DESIGN PRECAUTIONS]
DANGER
For the operating status of each station in the case of a communication error, see the manual of each
station. Erroneous output or malfunction may cause an accident.
When controlling a running PLC (modifying data) by connecting peripheral devices to the CPU
module or connecting a personal computer to the intelligent function module, configure an
interlocking circuit in a sequence program so that the safety of the overall system is always
maintained. Also, before performing other control operations (program modifications and operation
status modifications (status control)) on the running PLC, be sure to read the manual carefully and
thoroughly confirm the safety.
Especially in the above mentioned control operations that are performed from an external device to a
remote PLC, any problems on the PLC side may not be dealt with promptly due to faulty data
communication. In addition to configuring an interlocking circuit in a sequence program, determine
how the system handles data communication errors between the devices and the PLC CPU.
Do not write any data in the "system area (Use prohibited)" of the buffer memory of the intelligent
function module. Also, do not output (turn on) the "use prohibited" signal, which is one of the output
signals from the PLC CPU to the intelligent function module. If data is written to the "system area
(Use prohibited)" or the "use prohibited" signal is output, there is a risk that the PLC system may
malfunction.
A-1
[DESIGN PRECAUTIONS]
CAUTION
Do not bundle the control wires and the communication cables with the main circuit and the power
wires, and do not install them close to each other. They should be installed at least 100 mm (3.94 in.)
away from each other. Failure to do so may generate noise that may cause malfunctions.
[INSTALLATION PRECAUTIONS]
CAUTION
Use the PLC in the operating environment that meets the general specifications described in the
user's manual of the CPU Module to use. Using the PLC in any other operating environments may
cause electric shocks, fires or malfunctions, or may damage or degrade the module.
While pressing the installation lever located at the bottom of module, insert the module fixing tab into
the fixing hole in the base unit until it stops. Then, set the module in position using the fixing hole as
a supporting point. Incorrect mounting may cause malfunctions, failure or a drop of the module.
Secure the module with screws in an environment of frequent vibrations.
Be sure to tighten the screws using the specified torque. If the screws are loose, it may cause a short
circuit, malfunctions or a drop of the module. Overtightening the screws may damage the screws
and/or module, resulting in a short circuit, malfunctions or a drop of the module.
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 electronic components of the module. Doing so may
cause malfunction or failure in the module.
A-2
[WIRING PRECAUTIONS]
DANGER
Be sure to shut off all phases of the external power supply used in the system before wiring.
Failure to do so may result in an electric shock or damage to the product.
When powering up the system for operation after completing the wiring, make sure that supplied
terminal covers are correctly attached. Not attaching the terminal covers could result in an electric
shock.
]
CAUTION
Properly crimp, press-fit or solder the wires of the connector for external connections using the
manufacturer-specified tools.
Incomplete connection may cause a short circuit, fire, or malfunction.
Fully connect the connector to the module.
Before wiring the module, check the rated voltage and the terminal layout. Connecting a power
supply that is different from the rating or incorrectly wiring the product could result in fire or damage.
Make sure to place the communication and power cables to be connected to the module in a duct or
fasten them using a clamp. If the cables are not placed in a duct or fastened with a clamp, their
positions may be unstable or moved, and they may be pulled inadvertently.
This may damage the module and the cables or cause the module to malfunction due to poor cable
connection.
Wire the module correctly after confirming the type of the connected interface. If the cable is
connected to a different interface or wired incorrectly, it may cause a fire or breakdown.
Tighten the terminal screws within the range of the specified torque. If the terminal screws are loose,
it may result in a short circuit or malfunction. If the screws are tightened too much, it may cause
damage to the screw and/or the module, resulting in a drop of the module, short circuit or
malfunction.
When removing a communication or power cable from the module, do not pull the cable part. For the
cable with connector, hold the connector part connected to the module. When removing the cable
connected to the terminal block, first loosen the screws on the terminal block. Pulling the cable that is
still connected to the module may cause malfunction or damage to the module and/or cable.
Carefully prevent foreign matter such as wire chips from entering the module.
Failure to do so may cause a fire, breakdown or malfunction of the module.
A protective film is attached onto the module top in order to prevent foreign matter such as wire chips
from entering the module while wiring.
Do not remove this protective film during wiring work. However, be sure to remove it for heat
dissipation before system operation.
A-3
[STARTUP/MAINTENANCE PRECAUTIONS]
DANGER
Do not touch the terminals while power is on. Doing so could cause an electric shock.
Before cleaning up and retightening terminal screws and module mounting screws, be sure to shut
off all phases of the external power supply used by the system. Not doing so may cause failure or
malfunction of the module. If the screws are loose, it may cause a drop of the module, short circuit,
or malfunction. If the screws are tightened too much, it may cause damages to the screws and/or the
module, resulting in a drop of the module, short circuit or malfunction.
CAUTION
Before performing online operations (especially, program modification, forced output or operating
status change) by connecting a peripheral device to a running CPU, read the manual carefully and
ensure the safety. Incorrect operation will cause mechanical damage or accidents.
Do not disassemble or modify each module. Doing so could cause failure, malfunction, injury or fire.
When using a wireless communication device such as a cellular phone, keep a distance of 25cm
(9.85 inch) or more from the PLC in all directions. Failure to do so can cause a 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 module failure or malfunctions.
Do not mount/remove the module onto/from a base unit more than 50 times (IEC61131-2-compliant),
after the first use of the product. Exceeding 50 times 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.
[OPERATING PRECAUTIONS]
DANGER
Please read the manual carefully and ensure the safety before performing control operations
(especially, data or program modification and operation status change) to a running PLC. Incorrect
data or program modifications or improper operating status change may cause system malfunctions,
mechanical damages or accidents.
[DISPOSAL PRECAUTIONS]
CAUTION
When disposing of this product, treat is as an industrial waste.
A-4
REVISIONS
* The manual number is given on the bottom left of the back cover.
Print Date
Nov., 2005
* Manual Number
Revision
SH(NA)-080578ENG-A First edition
Japanese Manual Version SH-080567-B
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.
2005 MITSUBISHI ELECTRIC CORPORATION
A-5
INTRODUCTION
Thank you for purchasing the MELSEC-Q series PLC.
Before using the equipment, please read this manual carefully to develop full familiarity with the functions
and performance of the Q series PLC you have purchased, so as to ensure correct use.
CONTENTS
SAFETY PRECAUTIONS •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• A - 1
REVISIONS••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• A - 5
Conformation to the EMC Directive and Low Voltage Instruction ••••••••••••••••••••••••••••••••••••••••••••••••••••• A - 10
The Manual's Usage and Structure ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• A - 11
About the Generic Terms and Abbreviations•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• A - 13
Meanings and Definitions of Terms ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• A - 13
Product Configuration•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• A - 14
CHAPTER1 OVERVIEW
1.1
1 - 1 to 1 - 4
Features ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••1 - 1
CHAPTER2 SYSTEM CONFIGURATION
2 - 1 to 2 - 8
2.1
Applicable System ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••2 - 1
2.2
Network Configuration •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••2 - 3
2.3
Checking the Function Version/Software Version ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••2 - 7
CHAPTER3 SPECIFICATIONS
3 - 1 to 3 - 23
3.1
Performance Specifications •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••3 - 1
3.2
RS-232 Interface Specification •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••3 - 3
3.2.1
3.2.2
3.3
RS-422/485 Interface Specification •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••3 - 6
3.3.1
3.3.2
3.3.3
3.4
RS-422/485 terminal block specification••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••3 - 6
RS-422/485 cable specification•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••3 - 7
Precautions when transferring data using RS-422/485 line•••••••••••••••••••••••••••••••••••••••••••3 - 8
I/O Signals for PLC CPU •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 3 - 10
3.4.1
3.5
RS-232 connector specification ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••3 - 3
RS-232 cable specification ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••3 - 5
I/O signal list•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 3 - 10
Applications and Assignment of Buffer Memory •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 3 - 13
3.5.1
Buffer memory list ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 3 - 13
CHAPTER4 MODBUS(R) STANDARD FUNCTIONS
4 - 1 to 4 - 60
4.1
MODBUS(R) Standard Function Support List •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••4 - 1
4.2
Frame Specifications ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 10
4.2.1
A-6
Frame mode•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 11
4.3
Protocol Data Unit Formats by Functions •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 15
4.4
Read Coils (FC: 01) •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 18
4.5
Read Discrete Inputs (FC: 02)•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 19
4.6
Read Holding Registers (FC: 03) •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 20
4.7
Read Input Registers (FC: 04) ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 21
4.8
Write Single Coil (FC: 05) ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 22
4.9
Write Single Register (FC: 06) ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 23
4.10 Read Exception Status (FC: 07) ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 24
4.11 Diagnostics (FC:08) •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 25
4.11.1
4.11.2
4.11.3
4.11.4
4.11.5
4.11.6
4.11.7
4.11.8
4.11.9
4.11.10
4.11.11
4.11.12
4.11.13
4.11.14
4.11.15
4.11.16
Return query data (sub-function code: 00) ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 25
Restart communications option (sub-function code: 01)••••••••••••••••••••••••••••••••••••••••••••• 4 - 26
Return diagnostic register (sub-function code: 02) ••••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 28
Change ASCII input delimiter (sub-function code: 03) ••••••••••••••••••••••••••••••••••••••••••••••• 4 - 30
Force listen only mode (sub-function code: 04) ••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 31
Clear counters and diagnostic register (sub-function code: 10)•••••••••••••••••••••••••••••••••••• 4 - 33
Return bus message count (sub-function code: 11)•••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 35
Return bus communication error count (sub-function code: 12) ••••••••••••••••••••••••••••••••••• 4 - 36
Return bus exception error count (sub-function code: 13) •••••••••••••••••••••••••••••••••••••••••• 4 - 37
Return slave message count (sub-function code: 14)•••••••••••••••••••••••••••••••••••••••••••••••• 4 - 38
Return slave no response count (sub-function code: 15) ••••••••••••••••••••••••••••••••••••••••••• 4 - 39
Return slave NAK count (sub-function code: 16) ••••••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 40
Return slave busy count (sub-function code: 17) ••••••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 41
Return bus character overrun count (sub-function code: 18) ••••••••••••••••••••••••••••••••••••••• 4 - 42
Return IOP overrun error count (sub-function code: 19) •••••••••••••••••••••••••••••••••••••••••••• 4 - 43
Clear overrun counter and flag (sub-function code: 20) ••••••••••••••••••••••••••••••••••••••••••••• 4 - 44
4.12 Get Communications Event Counter (FC: 11)••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 45
4.13 Get Communications Event Log (FC: 12) •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 47
4.14 Write Multiple Coils (FC: 15) •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 50
4.15 Write Multiple Registers (FC: 16) •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 52
4.16 Report Slave ID (FC: 17) •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 53
4.17 Read File Record (FC: 20) (SC: 06)••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 55
4.18 Write File Record (FC: 21) (SC: 06)••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 57
4.19 Mask Write Register (FC: 22)••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 59
4.20 Read/Write Multiple Registers (FC: 23) •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4 - 60
CHAPTER5 FUNCTION
5 - 1 to 5 - 22
5.1
Function List ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 5 - 1
5.2
Master Function ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 5 - 3
5.2.1
5.2.2
5.3
Automatic communication function •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 5 - 3
Dedicated instruction ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 5 - 16
Slave Function••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 5 - 17
5.3.1
5.3.2
5.3.3
Automatic response function •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 5 - 17
MODBUS(R) device assignment function •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 5 - 18
Link operation function ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 5 - 21
A-7
CHAPTER6 PRE-OPERATIONAL PROCEDURES AND SETTINGS
6 - 1 to 6 - 24
6.1
Handling Precautions ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••6 - 1
6.2
Pre-Operational Procedures and Settings •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••6 - 2
6.3
Part Names ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••6 - 4
6.4
Unit Tests•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••6 - 6
6.4.1
6.4.2
6.5
Hardware test ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••6 - 6
Self-loopback test •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••6 - 8
Connection to a Target Device ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 6 - 11
6.5.1
6.5.2
How to connect the RS-232 interface ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 6 - 12
How to connect the RS-422/485 interface•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 6 - 14
6.6
Intelligent Function Module Switch Setting••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 6 - 19
6.7
Maintenance, Inspection••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 6 - 24
6.7.1
6.7.2
Maintenance, inspection ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 6 - 24
When removing or installing the module•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 6 - 24
CHAPTER7 PARAMETER SETTING
7 - 1 to 7 - 31
7.1
Parameter Settings and Setting Procedure ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••7 - 1
7.2
Automatic Communication Parameter ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••7 - 4
7.2.1
7.3
Automatic communication parameter details••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••7 - 4
MODBUS(R) Device Assignment Parameter•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 7 - 11
7.3.1
7.3.2
7.3.3
7.3.4
7.3.5
7.3.6
MODBUS(R) device assignment to the PLC CPU device memory•••••••••••••••••••••••••••••••• 7 - 13
MODBUS(R) extended file register assignment to the PLC CPU file register ••••••••••••••••••• 7 - 23
QJ71MB91 buffer memory assignment ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 7 - 24
Specifying the error status read device ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 7 - 26
Specifying access target when mounted to MELSECNET/H remote I/O station•••••••••••••••• 7 - 29
Specifying the CPU response monitoring timer ••••••••••••••••••••••••••••••••••••••••••••••••••••••• 7 - 30
CHAPTER8 UTILITY PACKAGE (GX Configurator-MB)
8 - 1 to 8 - 36
8.1
GX Configurator-MB Functions•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••8 - 1
8.2
Installing or Uninstalling GX Configurator-MB•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••8 - 2
8.2.1
8.2.2
8.3
GX-Configurator-MB Operations •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••8 - 6
8.3.1
8.3.2
8.3.3
8.4
Precautions for use •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••8 - 2
Operating environment •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••8 - 4
Common operations of GX Configurator-MB ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••8 - 6
Operation outline ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••8 - 9
Starting Intelligent function utility ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 8 - 11
Initial Setting ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 8 - 14
8.4.1
8.4.2
Automatic communication parameter ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 8 - 16
MODBUS(R) device assignment parameter ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 8 - 18
8.5
Auto Refresh Setting ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 8 - 21
8.6
Monitor/Test•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 8 - 23
8.6.1
8.6.2
8.6.3
A-8
X/Y Monitor/test•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 8 - 28
MODBUS(R) device assignment parameter status••••••••••••••••••••••••••••••••••••••••••••••••••• 8 - 30
Automatic communication status••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 8 - 31
8.6.4
8.6.5
Error log ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 8 - 33
Communication status•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 8 - 34
CHAPTER9 PROGRAMMING
9.1
Parameter Setting •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 9 - 1
9.1.1
9.1.2
9.2
Automatic communication parameter ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 9 - 1
MODBUS(R) device assignment parameter ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 9 - 4
Program Example for Normal System Configuration •••••••••••••••••••••••••••••••••••••••••••••••••••••••• 9 - 8
9.2.1
9.2.2
9.2.3
9.3
9 - 1 to 9 - 44
Automatic communication parameter ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 9 - 8
MODBUS(R) device assignment parameter ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 9 - 14
When using the automatic communication function and dedicated instructions on the same
channel •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 9 - 18
Program Example for Use in MELSECNET/H Remote I/O Network •••••••••••••••••••••••••••••••••••• 9 - 25
9.3.1
9.3.2
Automatic communication parameter ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 9 - 25
MODBUS(R) device assignment parameter ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 9 - 37
CHAPTER10 DEDICATED INSTRUCTIONS
10 - 1 to 10 - 23
10.1
Dedicated Instruction List ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 10 - 1
10.2
MBRW Instruction •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 10 - 2
10.3
MBREQ Instruction ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••10 - 13
CHAPTER11 TROUBLESHOOTING
11 - 1 to 11 - 46
11.1
Troubleshooting ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 11 - 1
11.2
Checking QJ71MB91 Status•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••11 - 11
11.3
Checking the Communication Status of QJ71MB91 ••••••••••••••••••••••••••••••••••••••••••••••••••••••11 - 17
11.4
Error Codes •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••11 - 21
11.4.1
11.4.2
11.4.3
11.5
Error code storage area•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••11 - 21
Exception code list •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••11 - 28
Error code list ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••11 - 30
Turning Off the ERR. LED •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••11 - 40
11.5.1
11.5.2
11.5.3
Turning off the ERR. LED by GX Configurator-MB ••••••••••••••••••••••••••••••••••••••••••••••••••11 - 40
Turning off the ERR. LED by sequence program ••••••••••••••••••••••••••••••••••••••••••••••••••••11 - 44
Turning off the ERR. LED by request message from the master •••••••••••••••••••••••••••••••••11 - 46
APPENDICES
Appendix 1
App - 1 to App - 13
A Series Modules •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• App - 1
Appendix 1.1 Comparisons in performance specifications ••••••••••••••••••••••••••••••••••••••••••••••••• App - 1
Appendix 1.2 Functional comparisons•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• App - 2
Appendix 1.3 Utilization of existing programs ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• App - 3
Appendix 2 Processing Time ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• App - 6
Appendix 3
INDEX
External Dimensions •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••App - 12
Index- 1 to Index- 2
A-9
Conformation to the EMC Directive and Low Voltage Instruction
When incorporating the Mitsubishi PLC into other machinery or system 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 PLC, indicating compliance with the
EMC and low voltage directives. No additional measures are necessary for
this product to make compliance with the EMC and low voltage directives.
A - 10
The Manual's Usage and Structure
This manual lists the process and functions up to systems operation using
the MODBUS interface module (QJ71MB91), divided into subjects.
Refer to the corresponding section when you need to know the following:
(1) Features (
CHAPTER 1)
CHAPTER 1 describes the features of the QJ71MB91.
(2) System Configuration (
CHAPTER 2)
Section 2.1 lists the applicable PLC CPU and corresponding software package.
Section 2.2 lists network configuration example.
(3) Performance and Specifications (
CHAPTER 3)
Section 3.1 lists the performance specifications of the QJ71MB91.
Section 3.2 and 3.3 list the specifications of each interface.
Section 3.4 and 3.5 list the I/O signals and buffer memory of the QJ71MB91.
(4) MODBUS Standard Functions Supporting QJ71MB91 (
CHAPTER 4)
Section 4.1 lists the MODBUS standard functions supporting QJ71MB91.
Sections 4.2 to 4.20 list the frame specifications of the MODBUS standard functions
supporting QJ71MB91.
(5) Usable Functions (
CHAPTER 5)
CHAPTER 5 describes the functions of the QJ71MB91.
(6) Settings and Procedures Necessary for System Operation
(
CHAPTER 6)
CHAPTER 6 describes the pre-operation settings and procedures.
(7) Parameter Settings of the QJ71MB91 (
CHAPTER 7)
CHAPTER 7 describes the parameter setting procedures and parameter details.
(8) Setting Parameters from the Utility Package (
CHAPTER 8)
CHAPTER 8 describes how to use the utility package.
(9) Setting Parameters from the Sequence Program (
CHAPTER 9)
CHAPTER 9 describes the I/O signals used for parameter settings, the I/O signal
timing charts, and program examples.
(10)Reading from/Writing to the MODBUS Device using the Sequence
Program (
CHAPTER 10)
CHAPTER 10 describes the dedicated instructions designed to read or write
MODBUS device data with sequence programs.
A - 11
(11)Error Code and Corresponding Process Details (
CHAPTER 11)
Section 11.1 lists troubleshooting.
Section 11.2 lists the confirmation methods of the module conditions.
Section 11.3 lists the confirmation of the communication conditions.
Section 11.4 lists the storage location and details of the error codes.
Section 11.5 lists the methods to turn off the ERR. LED.
About the notation of the numerical values used in this manual
In this manual, the numerical values with the suffix "H" are displayed in
hexadecimal values.
(Example)
A - 12
10......Decimal
10H....Hexadecimal
About the Generic Terms and Abbreviations
Unless otherwise specified, this manual uses the following generic terms
and abbreviations to explain the QJ71MB91 MODBUS interface module.
General term/Abbreviation
QJ71MB91
GX Developer
MODBUS Protocol
FC
SC
PLC CPU
Description
Abbreviation for the QJ71MB91 MODBUS interface module.
GX Developer (SWnD5C-GPPW). ("n" must be 4 or more.)
Generic term for the protocol designed to use MODBUS protocol messages.
Abbreviation for the function code.
Abbreviation for the sub code.
Generic term for the Q00JCPU, Q00CPU, Q01CPU, Q02CPU, Q02HCPU,
Q06HCPU, Q12HCPU, Q25HCPU, Q12PHCPU and Q25PHCPU
The side from which a request is sent to execute a function.
The side where the execution request from the master is processed and its execution
Master
Slave
Master function
Slave function
result is sent.
The function that allows communication with the MODBUS
compatible slave device as the
master of MODBUS .
The function that allows communication with the MODBUS
compatible master device as
the slave of MODBUS .
The message used to give a function execution request to the slave In the MODBUS
Request message
protocol, a function execution request is given from the master to the slave.
Response message
A function execution request cannot be given from the slave to the master.
The message with which the slave returns a function execution result to the master.
Abbreviation of the connected communication targets (devices corresponding to personal
Target device
computers, other QJ71MB91 MODBUS
Personal computer
MELSECNET/H
communication.
Abbreviation for DOS/V personal computers of IBM PC/AT and compatible.
Abbreviation of the MELSECNET/H network system.
interface modules, MODBUS
protocols) for data
Meanings and Definitions of Terms
The following explains the meanings and difinitions of the terms used in this
manual.
MODBUS
MODBUS
Term
protocol
device
Sequence program
Device memory
Listen only mode
Description
Communication protocol developed for PLC by Schneider Electric SA.
Device used for communication using the MODBUS protocol
Programming system devised to make a contact type sequence compatible with the
PLC language as-is. Draw two vertical control buses and describe contacts, etc.
between the buses to perform programming.
Memory provided for the PLC CPU to record the data handled in sequence program
operation.
Mode detaching the slave station from the circuit.
A - 13
Product Configuration
The following indicates the product configuration of the QJ71MB91
MODBUS interface module.
Model
QJ71MB91 MODBUS
Item name
interface module
QJ71MB91
Terminal resistor 330
1/4 W (for RS-422 communication)
SW1D5C-QMBU-E
SW1D5C-QMBU-EA
Terminal resistor 110
1/2 W (for RS-485 communication)
GX Configurator-MB Version 1 (1-license product)
GX Configurator-MB Version 1 (Multiple-license product)
A - 14
Quantity
1
2
2
(CD-ROM)
(CD-ROM)
1
1
1
OVERVIEW
1
This manual explains the specifications, functions, programming, and troubleshooting of
interface module (hereinafter referred to
2
The QJ71MB91 is used when a MELSEC-Q series PLC is connected to the MODBUS
protocol system.
MODBUS
is a registered trademark of Schneider Electric S.A.
1.1 Features
SYSTEM
CONFIGURATION
the MELSEC-Q series QJ71MB91 MODBUS
as QJ71MB91).
OVERVIEW
CHAPTER1 OVERVIEW
3
with various MODBUS slave devices (hereinafter referred to as slave) of other
manufacturers.
The master function includes the following two functions.
(a) Automatic communication function
By setting the automatic communication parameters, MODBUS device data can
be automatically read from or written to the slaves at the specified intervals using
the QJ71MB91 buffer memory.*1
Data can be transferred between the QJ71MB91 buffer memory and PLC CPU
device memory by making the auto refresh setting with the utility package (GX
Configurator-MB) or by accessing any intelligent function module device with a
sequence program.
MODBUS R slave device
(Third party remote I/O, etc)
RS-485
QJ71MB91
RUN
NEU.
SD
RD
CH1
ERR.
NEU.
SD
RD
CH2
5
6
Holding register
CH1
RS-232
4
MODBUS(R) STANDARD
FUNCTIONS
The QJ71MB91 supports the master function of the MODBUS communication,
which is an open network system for factory automation, and thereby is compatible
SPECIFICATIONS
communication
FUNCTION
(1) Supporting the master function of MODBUS
SDA
1
SG
SDB
2
4
5
6
7
PLC CPU
Device memory
Buffer memory
Read
Read
Auto Refresh
MODBUS R slave device
(Third party sensor, etc)
QJ71MB91 (Master function)
Holding register
7
Read
Write
MODBUS R slave device
(Third party PLC)
Holding register
8
Automatically issues the
MODBUS R device read/write
request message to Slave.
Figure 1.1 Communication using the automatic communication function
* 1 The MODBUS device is defined as a device area of the slave where data can be read/written in
response to a request from the master.
1.1 Features
PARAMETER SETTING
RDB
CH2
RS-422
/485
1-1
UTILITY PACKAGE
(GX Configurator-MB)
RDA
(FG)
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
3
(FG)
Device memory
1
OVERVIEW
(b) Communication using dedicated instruction
Dedicated instructions can be used to make communication from sequence
programs at any timing.
The QJ71MB91 supports the following two dedicated instructions.(
CHAPTER 10)
1) MBRW instruction
Reads or writes MODBUS device data from or to a slave.
This enables reading slave data to the PLC CPU device memory or writing
PLC CPU data to slaves.
2) MBREQ instruction
The user-determined request message format (function code + data unit) can
be issued to the slaves.
QJ71MB91
(Master
function)
PLC CPU
Command
[Z.MBRW
Device memory
]
MODBUS R Slave device
Holding register
Request message
(Read request for holding register 400500)
Response message
Response
Message
( Holding
register
(Holding
register
400500 =400500
1234H=) 1234H)
1234H
RS-232, RS-422 or RS-485
Figure 1.2 Communication using dedicated instruction
1-2
1.1 Features
400500
1234H
OVERVIEW
1
(a) Automatic response function
The QJ71MB91 can automatically respond to a request message received from
the master.
Any sequence program for the slave function is not needed.
(b) MODBUS device assignment function
Using MODBUS device assignment parameters, the MODBUS devices are
correlated with the PLC CPU device memory.
This enables direct access from the master to the PLC CPU device memory.
Supporting the MODBUS devices of large capacity, the QJ71MB91 allows all
device memories of the PLC CPU to be assigned.
No sequence
program required
MODBUS
Master
device
QJ71MB91 (Slave function)
R
R
MODBUS device assignment parameter
D299
400499
D300
400500
D301
400501
Request message (Write 1234H
to holding register 400500)
5
FUNCTION
1234H
R
MODBUS device
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
D300
Device
4
RS-232, RS-422 or RS-485
Figure 1.3 MODBUS
device assignment function
7
PARAMETER SETTING
Device
3
MODBUS(R) STANDARD
FUNCTIONS
PLC CPU
2
SYSTEM
CONFIGURATION
The QJ71MB91 supports the slave function of the MODBUS communication, which
is an open network system for factory automation, and thereby is compatible with
various MODBUS master devices (hereinafter referred to as master) of other
manufacturers.
The slave function includes the following two functions.
OVERVIEW
communication
SPECIFICATIONS
(2) Supporting the slave function of MODBUS
8
UTILITY PACKAGE
(GX Configurator-MB)
1
1.1 Features
1-3
1
OVERVIEW
(3) Link operation function
The master connected to the CH1 side (RS-232) can communicate with multiple
slaves connected to the CH2 side (RS-422/485) via the QJ71MB91.
This function allows the MODBUS master device with RS-232 interface (for one-onone communication) to communicate with multiple MODBUS slave devices.
The request message/response message
can be relayed between channel 1 and 2.
Request
message
RS-232
QJ71MB91
CH1
ERR.
NEU.
SD
RD
SDA
1
SG
MODBUS master device
(Third party PLC)
CH2
CH1
RS-232
Response
Message
R
RUN
NEU.
SD
RD
SDB
(FG)
RDA
2
3
4
RDB
CH2
RS-422
/485
Request
message
5
(FG)
6
7
RS-485
Response
Message
R
MODBUS slave device
(Third party remote I/O, etc)
R
MODBUS slave device
(Third party sensor, etc)
Figure 1.4 Communication using the link operation function
(4) Supporting high-speed communication of 115200 bps.
The total transmission speed of up to 115200bps is available for Channel 1 and 2.
(5) Easy setting by utility package
The optional utility package (GX Configurator-MB) is available.
Though not required, using the utility package allows on-screen initial setting
(automatic communications parameters, MODBUS device assignment parameters)
and auto refresh setting, reducing the size of sequence programs and also facilitating
the checking of the setting and operating states.
It is recommended to use the utility package with the QJ71MB91.
By making various parameter settings with the utility package, communications can
be made without sequence programs.
1-4
1.1 Features
2
SYSTEM CONFIGURATION
1
OVERVIEW
CHAPTER2 SYSTEM CONFIGURATION
This chapter explains the system configuration of the QJ71MB91.
2
SYSTEM
CONFIGURATION
2.1 Applicable System
This section presents applicable systems.
(1) Applicable modules and quantities
3
The PLC CPUs and network modules (for remote I/O stations) applicable to the
QJ71MB91 and the number of mountable modules are shown below.
Q00CPU
Q01CPU
Remarks
Up to 8
4
(*1)
Up to 24
Q02CPU
PLC CPU
Q02HCPU
Q06HCPU
Up to 64
Applicable in the Q mode only.
(*1)
Q12HCPU
Q25HCPU
Q12PHCPU
Q25PHCPU
5
Up to 64
(*1)
QJ72LP25-25
Network module
QJ72LP25G
QJ72LP25GE
MODBUS(R) STANDARD
FUNCTIONS
Q00JCPU
Number of
mountable modules
Up to 64
MELSECNET/H remote I/O station
(*2)
QJ72BR15
FUNCTION
Applicable module
SPECIFICATIONS
Table2.1 Applicable modules and quantities
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
* 1 Refer to the following manual.
QCPU User’s Manual (Function Explanation, Program Fundamentals)
* 2 Refer to the following manual.
Q Corresponding MELSECNET/H Network System Reference Manual
(Remote I/O network)
The QJ71MB91 can be installed to any I/O slot of the base unit. (Limited to within the
I/O point range of the PLC CPU and network module (remote I/O station))
Always take account of the power supply capacity when mounting the QJ71MB91,
since it may be insufficient depending on the combination with other modules or the
number of modules mounted.
PARAMETER SETTING
7
(2) Applicable base unit
UTILITY PACKAGE
(GX Configurator-MB)
8
2.1 Applicable System
2-1
2
SYSTEM CONFIGURATION
(3) Compatibility with multiple CPU system
The QJ71MB91 can be used in the multiple CPU system.
Please refer to the following manual before using the QJ71MB91 in the multiple CPU
system.
QCPU User’s Manual (Multiple CPU System)
(a) Intelligent function module parameters
The intelligent function module parameters must be written only to the control
CPU of the QJ71MB91.
(4) Compatible software package
The compatibility between the systems containing the QJ71MB91 and the software
packages is as shown below.
GX Developer is required to start up the system in which the QJ71MB91 is used.
Table2.2 Compatible software package
Software Version
Item
GX Developer
Single CPU system
Version 7 or later
Multiple CPU system
Version 8 or later
Single CPU system
Version 4 or later
Multiple CPU system
Version 6 or later
GX Configurator-MB
Q00J/Q00/Q01CPU
Q02/Q02H/Q06H/
Q12H/Q25HCPU
Single CPU system
Version 7.10L or later
Q12PH/Q25PHCPU
Multiple CPU system
When mounted to MELSECNET/H remote I/O
station
2-2
2.1 Applicable System
Version 6.01B or later
Version 1.05F or later
SYSTEM CONFIGURATION
1
The following shows MODBUS
network configuration examples using the QJ71MB91.
Table2.3 Network configuration using QJ71MB91
QJ71MB91
System Configuration
2
Reference
RS-422/485
This section (1) (c)
This section (1) (d)
3
This section (1) (a)
1:1
This section (1) (b)
Master
RS-232, RS-422/485
RS-485
1:n
RS-232
RS-422/485
This section (2) (a)
1:1
RS-232, RS-422/485
This section (2) (b)
This section (2) (c)
Slave
RS-485
1:n
This section (2) (d)
1:n
This section (2) (e)
RS-232, RS-485
(with link operation
function)
RS-232 (Master),
This section (3) (a)
RS-485 (Slave)
1:n
This section (3) (b)
5
FUNCTION
RS-485 (Master)
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
RS-232 (Slave)
4
7
PARAMETER SETTING
Master/Slave
SPECIFICATIONS
RS-232
SYSTEM
CONFIGURATION
Line Used
MODBUS(R) STANDARD
FUNCTIONS
Master/Slave
OVERVIEW
2.2 Network Configuration
8
UTILITY PACKAGE
(GX Configurator-MB)
2
2.2 Network Configuration
2-3
2
SYSTEM CONFIGURATION
(1) Using the QJ71MB91 as a master station
(a) Connecting to a slave station (1:1) with a RS-232 line
QJ71MB91 (Master function)
R
MODBUS slave device
QJ71MB91
RUN
NEU.
ERR.
NEU.
SD
RD
CH1
SD
RD
CH2
RS-232
CH1
RS-232
SDA
1
SG
2
SDB
3
(FG)
4
RDA
5
(FG)
6
RDB
7
CH2
RS-422
/485
Figure 2.1 Connecting to a slave station (1:1) with a RS-232 line
(b) Connecting to a slave station (1:1) with a RS-422/485 line
QJ71MB91 (Master function)
QJ71MB91
RUN
ERR.
NEU.
SD
RD
NEU.
SD
RD
CH1
CH2
R
CH1
RS-232
MODBUS slave device
SDA
1
SG
2
SDB
3
(FG)
RS-422/485
4
RDA
5
(FG)
6
RDB
7
CH2
RS-422
/485
Figure 2.2 Connecting to a slave station with a RS-422/485 line
(c) Connecting to slave stations (1:1) with RS-232 and RS-422/485 lines
QJ71MB91 (Master function)
R
MODBUS slave device
QJ71MB91
RUN
NEU.
SD
RD
CH1
ERR.
NEU.
SD
RD
CH2
RS-232
CH1
RS-232
R
MODBUS slave device
SDA
1
SG
SDB
2
3
(FG)
4
RDA
RS-422/485
5
(FG)
6
RDB
7
CH2
RS-422
/485
Figure 2.3 Connecting to slave stations (1:1)with RS-232 and RS-422/485 lines
(d) Connecting to slave stations (1:n)
QJ71MB91 (Master function)
QJ71MB91
CH1
RUN
NEU.
SD
RD
ERR.
NEU.
SD
RD
CH2
CH1
RS-232
SDA
SDB
RDA
2
3
4
5
(FG)
RDB
CH2
RS-422
/485
RS-485
1
SG
(FG)
6
7
R
MODBUS
slave device
R
MODBUS
slave device
Figure 2.4 Connecting to slave stations (1:n)
2-4
2.2 Network Configuration
R
MODBUS
slave device
SYSTEM CONFIGURATION
1
OVERVIEW
(2) Using the QJ71MB91 as a slave station
(a) Connecting to a master station (1:1) with a RS-232 line
MODBUS R master device
QJ71MB91 (Slave function)
2
QJ71MB91
CH1
RS-232
RUN
NEU.
SD
RD
ERR.
NEU.
SD
RD
CH2
SYSTEM
CONFIGURATION
CH1
RS-232
SDA
1
SG
2
SDB
3
(FG)
4
RDA
5
(FG)
6
RDB
7
CH2
RS-422
/485
Figure 2.5 Connecting to a master station (1:1) with a RS-232 line
(b) Connecting to a master station (1:1) with a RS-422/485 line
3
QJ71MB91 (Slave function)
QJ71MB91
RUN
NEU.
CH1
SD
RD
ERR.
NEU.
SD
RD
CH2
SPECIFICATIONS
R
MODBUS master device
CH1
RS-232
RS-422/485
SDA
1
SG
SDB
2
3
(FG)
RDA
4
5
(FG)
RDB
CH2
RS-422
/485
6
7
Figure 2.6 Connecting to a master station (1:1) with a RS-422/485 line
4
MODBUS(R) STANDARD
FUNCTIONS
(c) Connecting to master stations (1:1) with RS-232 and RS-422/485 lines
QJ71MB91 (Slave function) *1
R
MODBUS master device
QJ71MB91
CH1
R
RUN
NEU.
SD
RD
ERR.
NEU.
SD
RD
CH2
MODBUS master device
RS-232
CH1
RS-232
RS-422/485
SDA
1
SG
SDB
2
3
(FG)
RDA
RDB
CH2
RS-422
/485
5
4
5
(FG)
6
7
Figure 2.7 Connecting to master stations with RS-232 and RS-422/485 lines
* 1 The same station number is used for both RS-232 and RS-422/485 interfaces.
FUNCTION
(d) Connecting to a master station (1:n)
R
MODBUS master device
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
RS-485
QJ71MB91
CH1
RUN
NEU.
SD
RD
ERR.
NEU.
SD
RD
CH2
CH1
RS-232
MODBUS R
slave device
R
SDA
1
SG
SDB
(FG)
RDA
2
3
4
5
(FG)
RDB
CH2
RS-422
/485
MODBUS slave
device
6
7
7
PARAMETER SETTING
QJ71MB91 (Slave function)
Figure 2.8 Connecting to a master station (1:n)
8
UTILITY PACKAGE
(GX Configurator-MB)
2
2.2 Network Configuration
2-5
2
SYSTEM CONFIGURATION
(e) Connecting to a master station (1:n) with the link operation function
R
MODBUS master device
QJ71MB91 (Slave function)
QJ71MB91
RUN
ERR.
NEU.
SD
NEU.
SD
CH1
RD
CH2
RD
RS-232
CH1
RS-232
RS-485
SDA
1
SG
2
SDB
3
(FG)
4
RDA
5
(FG)
6
RDB
7
CH2
RS-422
/485
R
R
MODBUS
MODBUS
slave device
slave device
Figure 2.9 Connecting to a master station (1:n) with the link operation function
(3) Connecting master and slave stations separately through each interface
(a) Using the RS-232 interface as the master station and the RS-422/485 interface as
the slave station
R
MODBUS master device
QJ71MB91
QJ71MB91
CH1
RUN
NEU.
SD
RD
ERR.
NEU.
SD
RD
CH2
(Master function)
RS-232
R
MODBUS
slave device
CH1
RS-232
SDA
1
SG
2
SDB
(Slave function)
3
(FG)
4
RDA
5
(FG)
6
RDB
7
CH2
RS-422
/485
RS-485
R
MODBUS
slave device
R
MODBUS
slave device
Figure 2.10 Using the RS-232 interface as the master station and the RS-422/485
interface as the slave station
(b) Using the RS-232 interface as the slave station and the RS-422/485 interface as
the master station
R
MODBUS master device
QJ71MB91
QJ71MB91
CH1
RUN
NEU.
SD
RD
RS-232
ERR.
NEU.
SD
RD
CH2
(Slave function)
CH1
RS-232
SDA
1
SG
SDB
RDA
RS-485
2
3
(FG)
4
5
(Master function)
(FG)
RDB
CH2
RS-422
/485
6
7
MODBUS R
slave device
MODBUS R
slave device
Figure 2.11 Using the RS-232 interface as the slave station and the RS-422/485 interface
as the master station
2-6
2.2 Network Configuration
SYSTEM CONFIGURATION
1
Check the QJ71MB91 function version and the GX Configurator-MB software version by
the following methods.
OVERVIEW
2.3 Checking the Function Version/Software Version
2
(1) Checking the QJ71MB91 function version
SYSTEM
CONFIGURATION
(a) Checking the "Serial section of the rating plate" on the side of the module.
The serial No. and function version of the module are indicated in the Serial
section of the rating plate.
3
SPECIFICATIONS
Serial No. (Upper 5 digits)
function version
Comformed standard.
(b) Checking on GX Developer
The serial No. and function version of the module can be checked on GX
Developer.
The serial No. and function version are displayed on the "Product Information List"
[Starting Procedure]
Product Information List
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
[System Monitor]
7
PARAMETER SETTING
[Diagnostics]
5
FUNCTION
or "Module's Detailed Information" screen of GX Developer.(
Section 11.2
(3))
The following shows how to confirm the serial No. and function version on the
"Product Information List" screen.
MODBUS(R) STANDARD
FUNCTIONS
4
Figure 2.12 Rating plate
8
UTILITY PACKAGE
(GX Configurator-MB)
2
Figure 2.13 Product information list
2.3 Checking the Function Version/Software Version
2-7
2
SYSTEM CONFIGURATION
[Serial No., Ver.]
• The serial No. section displays the serial No. of the corresponding module.
• The Ver. column indicates the function version of the corresponding module.
(2) Checking the GX Configurator-MB software version.
The software version of GX Configurator-MB can be confirmed on the GX Developer’s
"Product Information" screen.
[Starting Procedure]
GX Developer
[Help]
[Product Information]
Software version
Figure 2.14 Product information
2-8
2.3 Checking the Function Version/Software Version
3
SPECIFICATIONS
1
OVERVIEW
CHAPTER3 SPECIFICATIONS
This chapter explains the performance specifications of the QJ71MB91, interface
specifications, I/O signals for communications with PLC CPU, and buffer memory.
Please refer to the following manual for general specifications.
2
SYSTEM
CONFIGURATION
QCPU User's Manual (Hardware Design, Maintenance and Inspection)
3.1 Performance Specifications
This section provides the performance specifications of QJ71MB91.
3
Table3.1 Performance specifications
1 channel
300
600
1200
2400
4800
9600
14400
19200
28800
38400
57600
115200 (bps)
SPECIFICATIONS
1 channel, RS-422/485
-
Section 6.6
specifications
Communication is available with total transmission
speed of two interfaces within 115200bps.
Transmission
RS-232
Max. 15m (49.2 ft.)
-
Max. 1200m (4592.4 ft.) (Overall distance)
-
Number of slaves*1
32 modules per channel
-
Function (for send)
7 functions
Section 7.2.1
distance
(Overall distance)
Automatic
RS-422/485
5
communication
function
Input area size
4k words
Output area size
4k words
Section 3.5.1
Master
Number of instructions that
function
can be executed
6
1 command per channel
concurrently*2
Dedicated
Function (for send)
MBRW instruction: 9 functions
CHAPTER 10
MBREQ instruction: 19 functions
Input area size
Max. 253 bytes per instruction
Output area size
Max. 253 bytes per instruction
7
(Continued on next page)
8
UTILITY PACKAGE
(GX Configurator-MB)
instruction
4
MODBUS(R) STANDARD
FUNCTIONS
Transmission
Transmission speed
RS-232
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Number of interfaces
Reference
FUNCTION
Specifications
PARAMETER SETTING
Item
3.1 Performance Specifications
3-1
3
SPECIFICATIONS
Table3.1 Performance specifications (Continued)
Item
Automatic
response function
MODBUS
Slave function Device size
Function (for receive)
Specifications
Reference
17 functions
CHAPTER 4
Coil
64k points
Input
64k points
Input register
64k points
Holding register
64k points
Extended file register
No. of simultaneously acceptable request
messages
Max. 1018k points
1 request per channel
-
1 to 247
Section 6.6
32 points
-
0.31A
-
Station No.
Number of occupied I/O points
5VDC internal current consumption
External dimensions
98 (H)
Weight
Section 7.3.1
27.4 (W)
0.20kg
90 (D) [mm]
Appendix 3
-
* 1 Indicates the maximum number of slaves that can be communication targets.
* 2 Indicates the maximum number of dedicated instructions that can be executed simultaneously from
a sequence program.
3-2
3.1 Performance Specifications
SPECIFICATIONS
1
OVERVIEW
3.2 RS-232 Interface Specification
This section explains RS-232 interface specifications.
3.2.1 RS-232 connector specification
This section provides the specifications of RS-232 connector that is connected to a target
device.
number
Signal code
Signal name
(Use
(Use
prohibited)
prohibited)
2
RD (RXD)
Receive data
3
SD (TXD)
Send data
1
Signal direction
QJ71MB91
Target device
3
-
SPECIFICATIONS
Pin
1
6
7
3
4
8
9
4
5
(Use
(Use
prohibited)
prohibited)
SG (GND)
Signal ground
-
4
MODBUS(R) STANDARD
FUNCTIONS
2
5
6
(Use
(Use
prohibited)
prohibited)
-
Output for
7*1
cable
-
SYSTEM
CONFIGURATION
2
5
disconnection
detection
Input for cable
FUNCTION
disconnection
detection
9
(Use
(Use
prohibited)
prohibited)
-
6
Figure 3.1 RS-232 connector specification
* 1 Connect Pin 8 to Pin 7.
Without connecting Pin 7 and 8, Pin 8 turns off and the CS signal may turn off (error code: 7403 H).
(1) Descriptions of control signals
The following explains control signals. (The pin number of the connector is indicated
within the brackets.)
(a) RD signal (2)
Signal for receiving data.
(b) SD signal (3)
Signal for sending data.
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
-
7
PARAMETER SETTING
8*1
8
UTILITY PACKAGE
(GX Configurator-MB)
3
3.2 RS-232 Interface Specification
3.2.1 RS-232 connector specification
3-3
3
SPECIFICATIONS
(2) ON/OFF status of each signal
The ON and OFF statuses of a signal are indicated below.
(Output side)
ON
......................... 5V to 15VDC,
OFF ......................... -5V to -15VDC,
(Input side)
3V to 15VDC
-3V to -15VDC
(3) Interface connector
For QJ71MB91 RS-232 interface connector, use a 9-pin D sub (female) screw type
connector.
Use metric screws.
3-4
3.2 RS-232 Interface Specification
3.2.1 RS-232 connector specification
SPECIFICATIONS
1
The RS-232 cable should be based on RS-232 standards and used within 15m(49.2ft).
OVERVIEW
3.2.2 RS-232 cable specification
SYSTEM
CONFIGURATION
2
SPECIFICATIONS
3
MODBUS(R) STANDARD
FUNCTIONS
4
FUNCTION
5
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
3
3.2 RS-232 Interface Specification
3.2.2 RS-232 cable specification
3-5
3
SPECIFICATIONS
3.3 RS-422/485 Interface Specification
This section explains RS-422/485 interface specifications.
3.3.1 RS-422/485 terminal block specification
This section provides the specifications of RS-422/485 terminal block that is connected to
a target device.
Signal
code
SG
(FG)
(FG)
+
SDA
+
SDB
+
RDA
+
RDB
+
+
+
Signal name
SDA
Send data (+)
SDB
Send data (-)
RDA
Receive data (+)
RDB
Receive data (-)
SG
Signal ground
FG
Frame ground
FG
Frame ground
Signal direction
QJ71MB91
Figure 3.2 RS-422/485 terminal block specifications
(1) The following explains control signals.
(a) SDA, SDB signal
Signal for QJ71MB91 to send data to a target device
(b) RDA, RDB signal
Signal for QJ71MB91 to receive data from a target device
(2) Terminating resistor
Connect the terminating resistor according to Section 6.5.2.
3-6
3.3 RS-422/485 Interface Specification
3.3.1 RS-422/485 terminal block specification
Target device
SPECIFICATIONS
1
OVERVIEW
3.3.2 RS-422/485 cable specification
This section explains the specifications of RS-422/485 cable.
(1) RS-422/485 cable to be used
(2) When making a 1:n connection
When connecting to multiple devices (1:n), ensure that the overall distance is within
1200 m(4592.4ft).
3
(3) RS-422/485 cable specifications
Description
Cable type
Shielded cable
Number of pairs
3P
)
88.0
Insulation resistance
10000M
/km or less
-km or more
Dielectric withstand voltage
500VDC, 1 minute
Electrostatic capacitance (1 kHz)
60nF/km or less by an average
5
110±10
FUNCTION
Characteristic impedance (100 kHz)
4
MODBUS(R) STANDARD
FUNCTIONS
Item
SPECIFICATIONS
Table3.2 RS-422/485 cable specifications
Conductor resistance (20
SYSTEM
CONFIGURATION
2
The RS-422/485 cable should meet the following specifications and used within
1200m(4592.4ft).
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
3
3.3 RS-422/485 Interface Specification
3.3.2 RS-422/485 cable specification
3-7
3
SPECIFICATIONS
3.3.3 Precautions when transferring data using RS-422/485 line
Note the following points when performing data communication with a target device
through the RS-422/485 interface of QJ71MB91.
For the target device side, pay attention to the following when sending/receiving data.
(1) Preventive measures against faulty data reception on the target device
side
If the target device receives error data, install a pull-up or pull-down resistor to the
target device as shown below.
Installing a pull-up or pull-down resistor (resistance value: approx. 4.7 k
prevent the reception of error data.
RDA
Terminating
RDB resistor
, 1/4 W) can
+
Receive data
Target
device
Figure 3.3 Preventive measures against faulty data reception
POINT
Error data will not be received if a pull-up or pull-down resistor is connected on the
target device side.
Remark
The case where any pull-up or pull-down resistor is not connected on the target
device is described below.
When any station is not performing transmission, the transmission line is in a high
impedance status and the line status is not stable due to noises, and the target
device may receive error data.
In such a case, parity or framing error may have occurred. Skip data reading for
error data.
3-8
3.3 RS-422/485 Interface Specification
3.3.3 Precautions when transferring data using RS-422/485 line
SPECIFICATIONS
1
(a) RS-422/485 interface configuration
For RS-422/485 interface, the configuration of driver (send)/receiver (receive)
component of the QJ71MB91 is as shown in the following diagram.
Driver
Send data
SDB
RDA
2
SYSTEM
CONFIGURATION
SDR
OVERVIEW
(2) RS-422/485 interface operation
Output Control Input (*1)
Receiver
Receive data
RDB
3
(Output control input)
Data
Target device side
QJ71MB91 side
5
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
(c) QJ71MB91 transmission start timing, transmission process complete timing
• Transmission start timing
After releasing the high impedance status indicated in above (a) and (b), and
outputting two or more character data during data transmission, output the
actual data.
• Transmission process complete timing
Data transmission time for data of 1 bit or less is required as the H/W gate
OFF time to complete the transmission process (high impedance status) after
finishing data transmission.
(Transmission speed set in the QJ71MB91 is targeted.)
4
MODBUS(R) STANDARD
FUNCTIONS
(b) RS-422/485 interface operation
When the "output control input" in the above figure is ON, the impedance status is
low (data transmittable).
In addition, when the "output control input" is OFF, the impedance status is high
(data not transmitted).
FUNCTION
* 1 The "output control input" (also referred to as send gate) of the driver (send) component
determines whether to output data externally from SDA, SDB.
SPECIFICATIONS
Figure 3.4 RS-422/485 interface configuration
Data
Outputs a mark with
2 characters or more
Data transmission
time range
ON time range of output
control input
(Low impedance status)
QJ71MB91 can send data.
H/W gate OFF time
(Refer to explanation above)
OFF time range of
output control input
(High impedance status)
QJ71MB91 can receive data.
Figure 3.5 Transmission process complete timing
3.3 RS-422/485 Interface Specification
3.3.3 Precautions when transferring data using RS-422/485 line
3-9
PARAMETER SETTING
7
(Output control input)
8
UTILITY PACKAGE
(GX Configurator-MB)
3
3
SPECIFICATIONS
3.4 I/O Signals for PLC CPU
This section explains the I/O signals for the PLC CPU of QJ71MB91.
3.4.1 I/O signal list
This section explains the I/O signals for the QJ71MB91.
The assignment of the I/O signals when the QJ71MB91 is mounted on slot 0 of the main
base unit is shown.
Device X represents an input signal from the QJ71MB91 to the PLC CPU, and device Y
means an output signal from the PLC CPU to the QJ71MB91.
The I/O signals for PLC CPU are listed below.
Refer to the reference sections for the details of each signal.
Table3.3 I/O signal list
Signal direction QJ71MB91
Device No.
PLC CPU
Signal name
Module READY *1
X0
Signal direction PLC CPU
Reference Device No.
Section
ON : Accessible
11.1
OFF : Inaccessible
X1
X2
-
X3
Use prohibited
-
Y3
CH1 Automatic communication parameter
setting request/automatic communication
parameter setting, normally completed
Y4
ON : Normally completed
OFF : -
Section
start request
5.2.1,
ON : Being requested
9.1.1
OFF : Not requested
CH1 Automatic communication
X5
Reference
Y2
CH1 Automatic communication
X4
Signal name
Y0
Y1
Use prohibited
QJ71MB91
Section
parameter setting, error completed
5.2.1,
ON : Error completed
9.1.1
Y5
Use prohibited
-
OFF : -
X6
CH1 Automatic communication
CH1 Automatic communication stop
operation status
request
Y6
ON : Operating
OFF : Stopped
ON : Being requested
Section
5.2.1
OFF : Not requested
CH1 Automatic communication error
X7
status
Section
ON : Error occurred
5.2.1
Y7
Use prohibited
-
OFF : No error
* 1 Turns ON when the QJ71MB91 is ready after the PLC is turned from OFF to ON or after the PLC
CPU is reset.
(Continued on next page)
3 - 10
3.4 I/O Signals for PLC CPU
3.4.1 I/O signal list
3
SPECIFICATIONS
1
Device No.
Signal name
MODBUS
X8
PLC CPU
Signal direction PLC CPU
Reference Device No.
device assignment
Y8
ON : Normally completed
OFF : MODBUS
X9
Signal name
MODBUS
parameter setting, normally completed
QJ71MB91
Reference
device assignment parameter
Section
setting request
9.1.2
ON : Being requested
OFF : Not requested
device assignment
parameter setting, error completed
ON : Error completed
Section
9.1.2
Y9
3
OFF : -
XA
Use prohibited
device assignment
parameter setting existence
SPECIFICATIONS
MODBUS
YA
ON : Parameters set
OFF: No parameters set
Use prohibited
-
YB
XC
YC
ON : Normally completed
OFF : -
XD
parameter setting, error completed
ON : Error completed
start request
5.2.1,
ON : Being requested
9.1.1
-
5
setting request/automatic communication
parameter setting, normally completed
CH2 Automatic communication
4
CH2 Automatic communication parameter
CH2 Automatic communication
MODBUS(R) STANDARD
FUNCTIONS
XB
2
SYSTEM
CONFIGURATION
Signal direction QJ71MB91
OVERVIEW
Table3.3 I/O signal list (Continued)
Section
OFF : Not requested
Section
5.2.1,
9.1.1
YD
Use prohibited
CH2 Automatic communication
CH2 Automatic communication stop request
operation status
YE
ON : Operating
ON : Being requested
5.2.1
OFF : Not requested
OFF : Stopped
Section
6
CH2 Automatic communication error
status
ON : Error occurred
Section
5.2.1
YF
Use prohibited
-
OFF : No error
(Continued on next page)
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
XF
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
XE
FUNCTION
OFF : -
3.4 I/O Signals for PLC CPU
3.4.1 I/O signal list
3 - 11
3
SPECIFICATIONS
Table3.3 I/O signal list (Continued)
Signal direction QJ71MB91
Device No.
PLC CPU
Signal name
Signal direction PLC CPU
Reference Device No.
X10
-
Y10
X11
-
Y11
X12
-
Y12
X13
-
Y13
X14
-
Y14
-
Y15
X16
-
Y16
X17
-
Y17
X18
-
Y18
X19
-
Y19
X1A
-
Y1A
X15
Use prohibited
CH Common/CH1 Error
X1B
Y1B
X1C
11.2
Reference
-
ON : Error occurred
ON : Being requested
CH2 Error clear request
Y1C
OFF : No error
Section
11.5
ON : Being requested
OFF : Not requested
X1D
Y1D
Use prohibited
-
X1E
Y1E
Watch dog timer error
X1F
Use prohibited
OFF : Not requested
Section
CH2 Error
Signal name
CH Common/CH1 Error clear request
ON : Error occurred
OFF : No error
QJ71MB91
ON : Module error occurred
OFF : Module operating normally
Section
11.1
Use prohibited
-
Y1F
POINT
Do not output (turn ON) any "Use prohibited" signal among I/O signals for PLC
CPU.
Doing so may cause the PLC system to malfunction.
3 - 12
3.4 I/O Signals for PLC CPU
3.4.1 I/O signal list
3
SPECIFICATIONS
1
OVERVIEW
3.5 Applications and Assignment of Buffer Memory
3.5.1 Buffer memory list
The buffer memory list is shown below.
Address
System area (use prohibited)
Initial
value
-
Read/
Initial
Write
setting
(*1)
(*2)
-
-
Reference
-
3
System area (use prohibited)
(3)
-
R
-
11.4.2
-
-
Error code
0004H
(4)
CH2 side error response code storage area
Status
0H
Section
R
11.4.2
storage
0005H
area
System area (use prohibited)
(5)
0006H
-
CH1 side detailed LED status storage area
(6)
-
0H
-
R
Detailed
Section
LED status
0007H
11.2
CH2 side detailed LED status storage area
(7)
0008H
CH1 side detailed LED clear request storage
Detailed
(8)
area
0H
R
0H
R/W
Section
11.5
CH2 side detailed LED clear request storage
request
(9)
0H
R/W
F000H
R/W
area
000AH
Setting
(10)
area
Device code
Setting
6
Section
error status
(11)
000CH
(12)
7.3.4
read device Head device number
System area (use prohibited)
0H
-
R/W
-
-
-
* 1 Indicates whether the reading (Read)/writing (Write) from the sequence program is enabled or
disabled.
R: Readable
W: Writable
* 2 Indicates whether setting on GX Configurator-MB is enabled or disabled.
: Setting enabled
: Setting disabled
(Continued on next page)
7
8
UTILITY PACKAGE
(GX Configurator-MB)
000BH
4
5
LED clear
0009H
-
SPECIFICATIONS
0003H
0H
MODBUS(R) STANDARD
FUNCTIONS
CH1 side error response code storage area
(2)
Section
FUNCTION
0002H
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
(0 to 1)
Name
PARAMETER SETTING
0000H to 0001H
Application
SYSTEM
CONFIGURATION
2
Table3.4 Buffer memory list
3.5 Applications and Assignment of Buffer Memory
3.5.1 Buffer memory list
3 - 13
3
SPECIFICATIONS
Table3.4 Buffer memory list (Continued)
Address
Application
Initial
Name
value
000DH
CPU response monitoring timer value
(13)
Set time = set value
000EH
(14)
Access target (when mounted to
Setting area
MELSECNET/H remote I/O station)
000FH
Allocated error status area
(15)
0010H to 01FFH
(16 to 511)
500ms
System area (use prohibited)
0200H to 0201H
(512 to 513)
0202H
(514)
Read/
Initial
Write
setting
(*1)
(*2)
AH
R/W
0H
R/W
0H
R/W
-
-
Setting parameter existence
0H
R/W
Target station No.
1H
R/W
0H
R/W
0H
R/W
0000H
R/W
0000H
R/W
0H
R/W
0H
R/W
0000H
R/W
0H
R/W
0H
R/W
0203H
Request interval timer value
(515)
Set time = set value
10ms
Reference
Section
7.3.6
Section
7.3.5
Section
7.3.4
-
-
Response monitoring timer value/Broadcast
0204H
delay value
(516)
Set time = set value
10ms
0205H
Type specification of the target MODBUS
(517)
device
Automatic
CH1 Automatic
0206H
communication
communication
(518)
parameter
parameter 1
R
Head buffer memory address
0207H
Read
Target MODBUS
(519)
setting
head number
0208H
R
device
Access points
(520)
0209H
Head buffer memory address
(521)
020AH
Write
Target MODBUS
(522)
setting
head number
020BH
Access points
(523)
R
device
Section 7.2
* 1 Indicates whether the reading (Read)/writing (Write) from the sequence program is enabled or
disabled.
R: Readable
W: Writable
* 2 Indicates whether setting on GX Configurator-MB is enabled or disabled.
: Setting enabled
: Setting disabled
(Continued on next page)
3 - 14
3.5 Applications and Assignment of Buffer Memory
3.5.1 Buffer memory list
3
SPECIFICATIONS
1
Application
Name
Initial
value
Read/
Initial
Write
setting
(*1)
(*2)
Reference
2
CH1 Automatic
parameter 2 to
Automatic
(Same as CH1 Automatic communication parameter 1)
32
Section
communication
parameter
7.2
CH2 Automatic
0380H to 04FFH
communication
(896 to 1279)
parameter 1 to
(Same as CH1 Automatic communication parameter 1)
3
32
System area (use prohibited)
0900H
(2304)
0901H
(2305)
(2306)
0903H
(2308 to 2367)
Device code
0H
R/W
Head device number
0H
R/W
Head coil number
0H
R/W
-
-
4
Coil
MODBUS
assignment 1
device
Section
7.3.1
assignment
parameter
Assignment points
(2307)
0904H to 093FH
-
0H
R/W
5
Coil
assignment 2
(Same as in Coil assignment 1)
to 16
* 1 Indicates whether the reading (Read)/writing (Write) from the sequence program is enabled or
disabled.
R: Readable
W: Writable
* 2 Indicates whether setting on GX Configurator-MB is enabled or disabled.
: Setting enabled
: Setting disabled
6
(Continued on next page)
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
0902H
-
7
PARAMETER SETTING
(1280 to 2303)
8
UTILITY PACKAGE
(GX Configurator-MB)
0500H to 08FFH
SYSTEM
CONFIGURATION
(524 to 895)
SPECIFICATIONS
communication
MODBUS(R) STANDARD
FUNCTIONS
020CH to 037FH
FUNCTION
Address
OVERVIEW
Table3.4 Buffer memory list (Continued)
3.5 Applications and Assignment of Buffer Memory
3.5.1 Buffer memory list
3 - 15
3
SPECIFICATIONS
Table3.4 Buffer memory list (Continued)
Address
Application
Name
0940H
(2368)
0941H
Input
(2369)
Initial
value
Read/
Initial
Write
setting
(*1)
(*2)
Device code
0H
R/W
Head device number
0H
R/W
Head input number
0H
R/W
Assignment points
0H
R/W
Reference
assignment
0942H
1
(2370)
0943H
(2371)
Input
0944H to 097FH
(2372 to 2431)
assignment (Same as input assignment 1)
MODBUS
2 to 16
Section
device
0980H
assignment
(2432)
parameter
0981H
Input
(2433)
register
0982H
(2434)
Device code
0H
R/W
Head device number
0H
R/W
Head input register number
0H
R/W
Assignment points
0H
R/W
7.3.1
assignment
1
0983H
(2435)
Input
0984H to 09BFH
register
(2436 to 2495)
assignment
(Same as in input register assignment 1)
2 to 16
* 1 Indicates whether the reading (Read)/writing (Write) from the sequence program is enabled or
disabled.
R: Readable
W: Writable
* 2 Indicates whether setting on GX Configurator-MB is enabled or disabled.
: Setting enabled
: Setting disabled
(Continued on next page)
3 - 16
3.5 Applications and Assignment of Buffer Memory
3.5.1 Buffer memory list
3
SPECIFICATIONS
1
(2496)
09C1H
Holding
(2497)
register
09C2H
MODBUS
(2498)
device
09C3H
(2499)
Initial
value
Read/
Initial
Write
setting
(*1)
(*2)
Device code
0H
R/W
Head device number
0H
R/W
Head holding register number
0H
R/W
Assignment points
0H
R/W
Reference
2
assignment
1
Section
7.3.1
assignment
parameter
3
register
(2500 to 2559)
assignment
SPECIFICATIONS
Holding
09C4H to 09FFH
(Same as in holding register assignment 1)
2 to 16
System area (use prohibited)
0C00H
-
Switch 1: CH1 operating mode setting status
(3072)
0C01H
Intelligent
(3073)
Setting
module
(3074)
status
switch
status
(3075)
0C04H
(3076)
0C05H
(3078 to 3090)
Operating
status
R
function
Switch 3: CH2 operation mode setting status
Section
R
module
4
6.6, 11.2
5
Section
6
switch
status
Switch 4: CH2 transmission setting status
R
Switch 5: CH1/CH2 Station No. setting status
R
LED ON status
0H
R
6.3, 11.2
status
System area (use prohibited)
-
-
-
-
* 1 Indicates whether the reading (Read)/writing (Write) from the sequence program is enabled or
disabled.
R: Readable
W: Writable
* 2 Indicates whether setting on GX Configurator-MB is enabled or disabled.
: Setting enabled
: Setting disabled
(Continued on next page)
7
8
UTILITY PACKAGE
(GX Configurator-MB)
0C06H to 0C12H
Module
-
Intelligent
setting
0C03H
-
R
Switch 2: CH1 transmission setting status
function
0C02H
(3077)
-
MODBUS(R) STANDARD
FUNCTIONS
(2560 to 3071)
FUNCTION
0A00H to 0BFFH
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
09C0H
Name
SYSTEM
CONFIGURATION
Application
PARAMETER SETTING
Address
OVERVIEW
Table3.4 Buffer memory list (Continued)
3.5 Applications and Assignment of Buffer Memory
3.5.1 Buffer memory list
3 - 17
3
SPECIFICATIONS
Table3.4 Buffer memory list (Continued)
Address
Application
Name
0C13H
MODBUS
(3091)
code storage area
0C14H
MODBUS
(3092)
device
Initial
value
device assignment parameter error
Error, device type
Read/
Write
(*1)
0H
R
0H
R
0H
R
Initial
setting Reference
(*2)
assignment
parameter
0C15H
(3093)
Parameter
0C16H
(3094)
error
Operating
status
information
setting result Error, assigned group No.
storage area
Section
CH1 Automatic communication parameter error
code storage area
0C17H
CH1 Automatic communication parameter setting
(3095)
result storage area
0C18H
CH2 Automatic communication parameter error
(3096)
code storage area
0C19H
CH2 Automatic communication parameter setting
(3097)
result storage area
0C1AH to 0C1FH
(3098 to 3103)
System area (use prohibited)
-
0H
R
0H
R
0H
R
0H
R
-
11.4.1
-
-
* 1 Indicates whether the reading (Read)/writing (Write) from the sequence program is enabled or
disabled.
R: Readable
W: Writable
* 2 Indicates whether setting on GX Configurator-MB is enabled or disabled.
: Setting enabled
: Setting disabled
(Continued on next page)
3 - 18
3.5 Applications and Assignment of Buffer Memory
3.5.1 Buffer memory list
3
SPECIFICATIONS
1
System area (use prohibited)
-
-
-
0H
R
Section
11.4.1
0H
System area (use prohibited)
condition
-
-
-
-
monitor area
CH1 Automatic communication setting status
storage area
0H
R
(Parameters 1 to 32)
Section
11.4.1
CH2 Automatic communication setting status
storage area
SYSTEM
CONFIGURATION
4
R
Communication
0H
R
-
-
-
0H
R
-
5
System area (use prohibited)
-
6
CH1 Automatic communication ready status
storage area
(Parameters 1 to 32)
Section
9.2.3
CH2 Automatic communication ready status
storage area
0H
R
-
-
-
(Parameters 1 to 32)
System area (use prohibited)
-
-
* 1 Indicates whether the reading (Read)/writing (Write) from the sequence program is enabled or
disabled.
R: Readable
W: Writable
* 2 Indicates whether setting on GX Configurator-MB is enabled or disabled.
: Setting enabled
FUNCTION
(Parameters 1 to 32)
: Setting disabled
(Continued on next page)
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Operating
3
7
8
UTILITY PACKAGE
(GX Configurator-MB)
(3252 to 3325)
R
(Parameters 1 to 32)
status
0CB4H to 0CFDH
-
storage area
0C68H to 0CA7H
(3250 to 3251)
0H
CH2 Automatic communication error code
(3144 to 3175)
0CB2H to 0CB3H
11.4.1
(Parameters 1 to 32)
0C48H to 0C67H
(3248 to 3249)
R
Section
storage area
(3112 to 3143)
0CB0H to 0CB1H
Reference
CH1 Automatic communication error code
0C28H to 0C47H
(3244 to 3247)
(*2)
(Parameters 1 to 32)
(3108 to 3111)
0CACH to 0CAFH
0H
status storage area
0C24H to 0C27H
(3242 to 3243)
(*1)
CH2 Automatic communication operation
(3106 to 3107)
0CAAH to 0CABH
setting
(Parameters 1 to 32)
0C22H to 0C23H
(3240 to 3241)
Initial
Write
2
status storage area
(3104 to 3105)
0CA8H to 0CA9H
value
Read/
CH1 Automatic communication operation
0C20H to 0C21H
(3176 to 3239)
Initial
SPECIFICATIONS
Name
MODBUS(R) STANDARD
FUNCTIONS
Application
PARAMETER SETTING
Address
OVERVIEW
Table3.4 Buffer memory list (Continued)
3.5 Applications and Assignment of Buffer Memory
3.5.1 Buffer memory list
3 - 19
3
SPECIFICATIONS
Table3.4 Buffer memory list (Continued)
Address
Application
Name
0CFEH
(3326)
0CFFH
(3327)
R
Detailed error code
0H
R
Exception code
0H
R
Function code
0H
R
CH
0H
R
Station No.
0H
R
Reference
Section
11.4.1
Error log
Error log 1
(3331)
0D04H
(3332)
0D05H to 0D06H
System area (use prohibited)
(3333 to 3334)
0D07H
-
Function
(3335)
0D08H to 0DFFH
Error log
(3336 to 3583)
2 to 32
(3584 to 3839)
(*2)
0H
0D02H
0E00H to 0EFFH
(*1)
Error log write pointer
(3329)
status
setting
R
0D01H
0D03H
Initial
Write
0H
(3328)
Operating
value
Read/
Number of errors occurred
0D00H
(3330)
Initial
-
0H
-
Section
R
11.4.1
Section
(Same as Error log 1)
System area (use prohibited)
-
11.4.1
-
-
-
-
* 1 Indicates whether the reading (Read)/writing (Write) from the sequence program is enabled or
disabled.
R: Readable
W: Writable
* 2 Indicates whether setting on GX Configurator-MB is enabled or disabled.
: Setting enabled
: Setting disabled
(Continued on next page)
3 - 20
3.5 Applications and Assignment of Buffer Memory
3.5.1 Buffer memory list
3
SPECIFICATIONS
1
Table3.4 Buffer memory list (Continued)
0F00H
(3840)
0F01H
(3841)
0F02H
Diagnostic
(3842)
value
Read/
Write
Initial
setting Reference
(*1)
(*2)
Bus message count
0H
R
2
Bus communication error count
0H
R
Character overrun error count
0H
R
Message discard count
0H
R
Data discard count
0H
R
Failed transmission count
0H
R
Slave message count
0H
R
Slave no-response count
0H
R
Slave NAK count
0H
R
Slave busy count
0H
R
Exception error count
0H
R
Communications event count
0H
R
data for
Master/Slave
(3843)
0F04H
(3844)
0F05H
(3845)
0F06H
status
status
0F08H
(3848)
5
0F09H
(3850)
0F0BH
(3851)
0F0CH
(3852)
0F0DH
(3853)
Diagnostic
data for Slave
2nd byte of end code
Communications mode
0AH
R
0H
R
Section
4.12
6
Section
4.11.4
Section
4.11.5
* 1 Indicates whether the reading (Read)/writing (Write) from the sequence program is enabled or
disabled.
R: Readable
W: Writable
* 2 Indicates whether setting on GX Configurator-MB is enabled or disabled.
: Setting enabled
: Setting disabled
(Continued on next page)
7
8
UTILITY PACKAGE
(GX Configurator-MB)
0F0AH
4
Communication
(3847)
(3849)
11.3
FUNCTION
0F07H
Communication
CH1
Section
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
(3846)
3
MODBUS(R) STANDARD
FUNCTIONS
0F03H
OVERVIEW
Initial
SYSTEM
CONFIGURATION
Name
SPECIFICATIONS
Application
PARAMETER SETTING
Address
3.5 Applications and Assignment of Buffer Memory
3.5.1 Buffer memory list
3 - 21
3
SPECIFICATIONS
Table3.4 Buffer memory list (Continued)
Address
Application
Name
0F0EH
Received exception error
(3854)
count
0F0FH
(3855)
0F10H
Diagnostic data
(3856)
for Master
0F11H
CH1
(3857)
Initial
value
Read/
Initial
Write
setting
(*1)
(*2)
0H
R
No-response count
0H
R
Broadcast count
0H
R
Received NAK count
0H
R
Received busy count
0H
R
Reference
Section
11.3
Communication
0F12H
status
(3858)
Communication
0F13H to 0F1EH status
(3859 to 3870)
System area (use prohibited)
0F1FH
-
Communications event log
Communication count
event log (for
Communications event log
Slave)
(3871)
0F20H to 0F3FH
(3872 to 3903)
-
0H
-
R
Section
4.13
0H
1 to 64
R
CH2
0F40H to 0F7FH
Section
Communication (Same as CH1 communication status)
(3904 to 3967)
4.13
status
0F80H to 0FFDH
System area (use prohibited)
(3968 to 4093)
0FFEH
(4094)
-
-
-
Hardware test result
0H
R
Self-loopback test result
0H
R
-
Section
6.4.1
Unit test result
0FFFH
(4095)
Section
6.4.2
* 1 Indicates whether the reading (Read)/writing (Write) from the sequence program is enabled or
disabled.
R: Readable
W: Writable
* 2 Indicates whether setting on GX Configurator-MB is enabled or disabled.
: Setting enabled
: Setting disabled
(Continued on next page)
3 - 22
3.5 Applications and Assignment of Buffer Memory
3.5.1 Buffer memory list
3
SPECIFICATIONS
1
Name
1000H to 1FFFH
CH1 Automatic communication function buffer input
(4096 to 8191)
area
2000H to 2FFFH
CH2 Automatic communication function buffer input
(8192 to
area
12287)
Automatic
3000H to 3FFFH
communication function
(12288 to
buffer
4000H to 4FFFH
CH1 Automatic communication function buffer output
CH2 Automatic communication function buffer output
(16384 to
area
20479)
value
Read/
Write
Initial
setting Reference
(*1)
0H
R
0H
R
R/W
0H
R/W
0H
R/W
3
Section
7.3.3
4
* 1 Indicates whether the reading (Read)/writing (Write) from the sequence program is enabled or
disabled.
R: Readable
W: Writable
* 2 Indicates whether setting on GX Configurator-MB is enabled or disabled.
: Setting enabled
: Setting disabled
MODBUS(R) STANDARD
FUNCTIONS
User free area
2
5.2.1
0H
5000H to 5FFFH
(20480 to
(*2)
Section
area
16383)
Initial
SYSTEM
CONFIGURATION
Application
SPECIFICATIONS
Address
OVERVIEW
Table3.4 Buffer memory list (Continued)
24575)
FUNCTION
5
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
PARAMETER SETTING
7
UTILITY PACKAGE
(GX Configurator-MB)
8
3.5 Applications and Assignment of Buffer Memory
3.5.1 Buffer memory list
3 - 23
4
MODBUS(R) STANDARD FUNCTIONS
CHAPTER4 MODBUS(R) STANDARD FUNCTIONS
This chapter explains the MODBUS
standard functions supported by the QJ71MB91.
Using the MODBUS standard functions allows you to read/write to PLC CPU devices
and to load the QJ71MB91 status into the master.
4.1 MODBUS(R) Standard Function Support List
(1) MODBUS
standard function support list
The following table indicates a list of the MODBUS
the QJ71MB91.
Table4.1 MODBUS
Function
code
(Sub code)
standard functions supported by
standard function support list
Accessible
Sub-function
code
Function
Description
devices
per
Broadcast Reference
message
Reads the status (ON/OFF) of one or
1 to
Section
2000 points
4.4
01
-
Read coils
02
-
Read discrete inputs
03
-
Read holding registers
04
-
Read input registers
05
-
Write single coil
Writes a value (ON/OFF) to one coil.
1 point
06
-
Write single register
Writes a value to one holding register.
1 point
07
-
Read exception status
Reads error status.
more coils.
Reads the status (ON/OFF) of one or
more inputs.
Reads the values of one or more
holding registers.
Reads the values of one or more input
registers.
1 to
Section
2000 points
4.5
1 to
Section
125 points
4.6
1 to
Section
125 points
4.7
-
Section
4.8
Section
4.9
Section
4.10
(Continued on next page)
4-1
4.1 MODBUS(R) Standard Function Support List
4
MODBUS(R) STANDARD FUNCTIONS
1
Table4.1 MODBUS
per
Broadcast Reference
message
2
Returns the contents of the request
message without change.
Used to check if the network or the
Section
-
4.11.1
target device is operating normally.
(Loopback test)
Initializes the communication port of the
receiving channel side and restarts the
01
Restart communications slave function. (Clears counters such
option
as the message count.)
Section
-
the listen only mode.
03
Return diagnostic
Reads out the detailed LED status of
register
the QJ71MB91 to the master.
Change ASCII input
delimiter
Section
-
4.11.3
Changes the 2nd byte (LF(0AH)) of the
end code in the ASCII mode to a
Section
-
4.11.4
specified data.
Places a slave into the offline mode.
04
Force listen only mode
Used when disconnecting a slave from
Section
-
4.11.5
the network.
08
Clears counters (e.g. message count).
10
Clear counters and
Also, clears the diagnostic register and
diagnostic register
the error of the channel where the
3
4.11.2
Returns to the online mode when it is in
02
SYSTEM
CONFIGURATION
Return query data
Section
-
SPECIFICATIONS
00
OVERVIEW
devices
4
MODBUS(R)
STANDARD FUNCTIONS
Description
5
4.11.6
request message has been received.
11
12
13
Return bus message
Reads out the number of messages
count
detected on the line to the master.
Return bus
Reads out the number of error
communication error
messages detected on the line to the
count
master.
Return bus exception
Reads out the frequency of exception
error count
errors to the master.
Section
-
4.11.7
Section
-
14
message processing to the master.
count
(Including reception of broadcast
Section
-
4.11.9
Section
-
4.11.10
request messages)
Return slave no
response count
Reads out the number of broadcast
request messages received to the
Section
-
4.11.11
master.
(Continued on next page)
7
8
UTILITY PACKAGE
(GX Configurator-MB)
15
6
4.11.8
Reads out the number of the slave
Return slave message
FUNCTION
(Sub code)
Function
code
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
code
Accessible
Sub-function
PARAMETER SETTING
Function
standard function support list (continued)
4.1 MODBUS(R) Standard Function Support List
4-2
4
MODBUS(R) STANDARD FUNCTIONS
Table4.1 MODBUS
Function
code
(Sub code)
Sub-function
code
standard function support list (continued)
Accessible
Function
Description
devices per
Reads out the number of NAK
16
Return slave NAK count responses to the master.
Section
-
4.11.12
The QJ71MB91 always returns "0".
Reads out the number of busy
17
Return slave busy count responses to the master.
Section
-
4.11.13
The QJ71MB91 always returns "0".
18
Broadcast Reference
message
Return bus character
overrun count
08
To the master, reads out the number of
times the request message size
Section
-
4.11.14
exceeds the upper limit.
Reads the IOP overrun error counter
value to the master.
19
Return IOP overrun
error count
The QJ71MB91 returns to the master
the number of times the request
Section
-
4.11.15
message size exceeds the upper limit.
(Same as the Return bus character
overrun count)
Clears the overrun error counter and
20
Clear overrun counter
flag.
and flag
The QJ71MB91 clears the character
Section
-
4.11.16
overrun error counter value.
Acquires the number of messages
whose requested processing (read/
11
-
Get communications
event counter
write, diagnostics, etc.) have been
normally completed.
Section
-
4.12
Whether the action corresponding to the
request message is normally completed
or not can be checked.
12
-
15
-
Get communications
Acquires the communications event log
event log
of the QJ71MB91 into the master.
Write multiple coils
Writes values (ON/OFF) to multiple
coils.
Section
-
4.13
1 to
Section
1968 points
4.14
(Continued on next page)
4-3
4.1 MODBUS(R) Standard Function Support List
4
MODBUS(R) STANDARD FUNCTIONS
1
(Sub code)
Accessible
Sub-function
Function
code
Description
devices per
Broadcast Reference
message
16
-
Write multiple registers
17
-
Report slave ID
Writes values to multiple holding
registers.
1 to
Section
123 points
4.15
Acquires the information of the slave
(QJ71MB91) mounted station into the
Section
-
4.16
master.
Reads values of one or more extended
20(6)
-
Read file record
21(6)
-
Write file record
22
-
Mask write register
file registers.
Writes values to one or more extended
file registers.
1 to
Section
124 points
4.17
1 to
Section
122 points
4.18
Masks the values stored in a single
holding register with AND or OR and
Section
1 point
4.19
writes the value.
Section
Write:
4.20
MODBUS(R)
STANDARD FUNCTIONS
23
-
registers
registers.
5
1 to
121 points
registers in FIFO queue structure.
Read device
Reads the module identification
identification
information of the slave.
-
-
-
-
-
FUNCTION
-
Reads values from the holding
* 1 The slave function of the QJ71MB91 does not support this function.
(
This section (2))
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
43*1
Read FIFO queue
Remark
The usable functions are limited when the QJ71MB91 is installed to a
MELSECNET/H remote I/O station.(
This section (3))
7
PARAMETER SETTING
-
8
UTILITY PACKAGE
(GX Configurator-MB)
24*1
3
125 points
1 to
Reads from or writes to multiple holding
2
4
Read:
Read/Write multiple
OVERVIEW
code
SYSTEM
CONFIGURATION
Function
standard function support list (continued)
SPECIFICATIONS
Table 4.1 MODBUS
4.1 MODBUS(R) Standard Function Support List
4-4
4
MODBUS(R) STANDARD FUNCTIONS
(2) Standard function support list for the master and slave functions
The following table indicates a standard function support list classified by the master
and slave functions of the QJ71MB91.
Table4.2 Standard function support list for the master and slave functions
Master function
Function
code
(Sub code)
Sub-function
Automatic
Function
code
communication
function
01
-
Read coils
02
-
Read discrete inputs
03
-
Read holding registers
04
-
Read input registers
05
-
Write single coil
06
-
Write single register
07
-
Read exception status
00
Return query data
01
Restart communications option
02
Return diagnostic register
03
Change ASCII input delimiter
04
Force listen only mode
10
Clear counters and diagnostic register
11
Return bus message count
12
Return bus communication error count
13
Return bus exception error count
14
Return slave message count
15
Return slave no response count
16
Return slave NAK count
Slave
MBRW
MBREQ
instruction
instruction *1
function
08
: Supported
: Not supported
* 1 Since the MBREQ instruction allows users to create request message frames, function codes other
than the above can be also sent. (
Section 10.3)
(Continued on next page)
4-5
4.1 MODBUS(R) Standard Function Support List
4
MODBUS(R) STANDARD FUNCTIONS
1
Master function
code
(Sub code)
Sub-function
Slave
Automatic
Function
code
communication
MBREQ
instruction
instruction *1
function
2
17
Return slave busy count
18
Return bus character overrun count
19
Return IOP overrun error count
SYSTEM
CONFIGURATION
function
MBRW
20
Clear overrun counter and flag
3
11
-
Get communications event counter
12
-
Get communications event log
15
-
Write multiple coils
16
-
Write multiple registers
17
-
Report slave ID
20(6)
-
Read file record
21(6)
-
Write file record
22
-
Mask write register
23
-
Read/Write multiple registers
24
-
Read FIFO queue
43
-
Read device identification
SPECIFICATIONS
08
MODBUS(R)
STANDARD FUNCTIONS
4
FUNCTION
5
: Supported
: Not supported
* 1 Since the MBREQ instruction allows users to create request message frames, function codes other
than the above can be also sent. (
Section 10.3)
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Function
OVERVIEW
Table4.2 Standard function support list for the master and slave functions (Continued)
7
PARAMETER SETTING
Remark
The usable functions are limited when the QJ71MB91 is installed to a
MELSECNET/H remote I/O station.(
This section (3))
UTILITY PACKAGE
(GX Configurator-MB)
8
4.1 MODBUS(R) Standard Function Support List
4-6
4
MODBUS(R) STANDARD FUNCTIONS
(3) List of MODBUS standard functions supported when accessing a
MELSECNET/H remote I/O station
The following MODBUS standard functions are available when the QJ71MB91
mounted on a MELSECNET/H remote I/O station makes access to the MELSECNET/
H remote I/O station.
Table4.3 MODBUS
standard functions available for access to MELSECNET/H remote I/O station
Master function
Function
code
(Sub code)
Sub-function
Function
Code
Automatic
communication
function
MBRW
MBREQ
instruction
instruction
Slave function*1
01
-
Read coils
*2
02
-
Read discrete inputs
*2
03
-
Read holding registers
*2
04
-
Read input registers
*2
05
-
Write single coil
*2
06
-
Write single register
*2
07
-
Read exception status
*2
: Supported
: Supported with restrictions
: Not supported
* 1 The access target is the MELSECNET/H remote I/O station.
When the MELSECNET/H remote master station is the access target, available functions are the
same as those shown in (2).
* 2 Accessing the MODBUS device that is not supported by the MELSECNET/H remote I/O station
results in error completion. (Exception code: 04H)
If the access target is the MELSECNET/H remote master station, it can be assigned to the control
CPU device of the MELSECNET/H remote master station.
(Continued on next page)
4-7
4.1 MODBUS(R) Standard Function Support List
4
MODBUS(R) STANDARD FUNCTIONS
1
Master function
(Sub code)
Sub-function
Automatic
Function
code
communication
Return query data
01
Restart communications option
02
Return diagnostic register
03
Change ASCII input delimiter
04
Force listen only mode
12
08
13
14
15
3
Clear counters and diagnostic
register
Return bus message count
4
Return bus communication
error count
Return bus exception error
count
Return slave message count
5
Return slave no response
count
16
Return slave NAK count
17
Return slave busy count
18
2
MODBUS(R)
STANDARD FUNCTIONS
11
instruction
FUNCTION
10
instruction
Slave function*1
SPECIFICATIONS
00
MBREQ
SYSTEM
CONFIGURATION
function
MBRW
6
Return bus character overrun
count
19
Return IOP overrun error count
20
Clear overrun counter and flag
: Supported
: Supported with restrictions
: Not supported
* 1 The access target is the MELSECNET/H remote I/O station.
When the MELSECNET/H remote master station is the access target, available functions are the
same as those shown in (2).
* 2 Accessing the MODBUS device that is not supported by the MELSECNET/H remote I/O station
results in error completion. (Exception code: 04H)
If the access target is the MELSECNET/H remote master station, it can be assigned to the control
CPU device of the MELSECNET/H remote master station.
(Continued on next page)
4.1 MODBUS(R) Standard Function Support List
4-8
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
code
7
PARAMETER SETTING
Function
OVERVIEW
standard functions available for access to MELSECNET/H remote I/O station (continued)
8
UTILITY PACKAGE
(GX Configurator-MB)
Table 4.3 MODBUS
4
MODBUS(R) STANDARD FUNCTIONS
Table 4.3 MODBUS
standard functions available for access to MELSECNET/H remote I/O station (continued)
Master function
Function
code
(Sub code)
Sub-function
Automatic
Function
code
communication
function
MBRW
MBREQ
instruction
instruction
Slave function*1
Get communications event
11
-
12
-
Get communications event log
15
-
Write multiple coils
*2
16
-
Write multiple registers
*2
17
-
Report slave ID
20(6)
-
Read file record
21(6)
-
Write file record
22
-
Mask write register
*2
23
-
Read/Write multiple registers
*2
24
-
Read FIFO queue
43
-
Read device identification
counter
: Supported
: Supported with restrictions
: Not supported
* 1 The access target is the MELSECNET/H remote I/O station.
When the MELSECNET/H remote master station is the access target, available functions are the
same as those shown in (2).
* 2 Accessing the MODBUS device that is not supported by the MELSECNET/H remote I/O station
results in error completion. (Exeption code: 04H)
If the access target is the MELSECNET/H remote master station, it can be assigned to the control
CPU device of the MELSECNET/H remote master station.
POINT
When the QJ71MB91 is mounted to a MELSECNET/H remote I/O station, switch
the access target using the Access target (when mounted to MELSECNET/H
remote I/O station) in the buffer memory (address: 000EH).(
4-9
4.1 MODBUS(R) Standard Function Support List
Section 7.3.5)
4
MODBUS(R) STANDARD FUNCTIONS
1
The following shows the frame specifications for the MODBUS
Address field
Function code
Data
OVERVIEW
4.2 Frame Specifications
protocol.
Error check
2
R
SYSTEM
CONFIGURATION
MODBUS Protocol Data Section
Section 4.3 to Section 4.20
Figure 4.1 Frame specifications
Table4.4 Frame specifications
Area name
3
Description
SPECIFICATIONS
[When master sends a request message to slave]
0: Sends a request message to all the slaves. (Broadcast)
1 to 247: Stores the target slave station No.
Address field
[When slave sends a response message to master]
The host station number is stored when sending a response message.
MODBUS(R)
STANDARD FUNCTIONS
4
[When master sends a request message to slave]
The master specifies the number of the action to be taken by the slave.
Function code
[When slave sends a response message to master]
A requested function code is stored in the case of normal completion.
The most significant bit turns ON in the case of error completion.
5
[When master sends a request message to slave]
The information needed to execute the action specified by a function code is stored.
Data
FUNCTION
[When slave sends a response message to master]
The execution result of the action specified by a function code is stored.
An exception code is stored when failed.
The master adds a check code in a request message and transmits the request message.
The slave, which received the request message, recalculates the check code in the request
Error check *1
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
message and determines whether the messageis correct or not.
The message is discarded if it has an error.
* 1 The error check method differs depending on the frame mode.(
6
Section 4.2.1)
7
PARAMETER SETTING
Remark
Refer to the following for the data size of each area.
Section 4.2.1
UTILITY PACKAGE
(GX Configurator-MB)
8
4.2 Frame Specifications
4 - 10
4
MODBUS(R) STANDARD FUNCTIONS
4.2.1 Frame mode
For the QJ71MB91, the following frame modes are available.
The frame mode of the QJ71MB91 must be consistent with that of the target device.
(1) Available frame modes
(a) RTU mode
In this mode, frames are received or sent in binary codes.
The frame specifications are compliant with the MODBUS
specifications.
Start
Address field
Function code
Data
Error check
END
(Start)
3.5 character time
or more
1 byte
1 byte
0 to 252 bytes
2 bytes
3.5 character time
or more
protocol
Address field
1 byte
Error check calculation range
Figure 4.2 Frame in RTU mode
Remark
The error check in the RTU mode is conducted by CRC (Cyclic Redundancy
Check).
The QJ71MB91 calculates the CRC by the following steps.
Please follow the same steps to calculate the CRC when conducting an error
check on the target device.
1) Load the register whose 16 bits are all "1".
2) The CRC is calculated every 8 bits from the upper bit of the frame.
Calculate the 8 bits of the frame and the exclusive logical sum (XOR) of the
bits in the above 1).
3) Shift the result of 2) by 1 bit to the right.
4) If the least significant bit of the above 2) is "1", calculate the exclusive OR
(XOR) from the result in 3) and the generator polynomial (A001H).
If the least significant bit is "0", do not calculate the exclusive OR (XOR), but
shift it by 1 bit to the right.
5) Repeat the above steps 3) and 4) until the bit is shifted up to 8 times.
6) Calculate the exclusive OR (XOR) from the result of 5) and the next 8 bits of
the frame.
7) Repeat steps 3) to 6).
8) Repeat the above operations until the end of the data unit is reached.
The final value is a calculated CRC value.
9) The CRC value is stored in the frame in the order from the lower 8 bits to the
upper 8 bits.
4 - 11
4.2 Frame Specifications
4.2.1 Frame mode
4
MODBUS(R) STANDARD FUNCTIONS
1
Table4.5 CRC calculation procedures
1111
1111
1111
0010
1111
1101
Shift 1
0111
1111
1111
1110
Generator polynomial
1010
0000
0000
0001
Exclusive OR (XOR)
1101
1111
1111
1111
2
1
Shift2
0110
1111
1111
1111
Generator polynomial
1010
0000
0000
0001
Exclusive OR (XOR)
1100
1111
1111
1110
Shift3
0110
0111
1111
1111
0
Shift4
0011
0011
1111
1111
1
Generator polynomial
1010
0000
0000
0001
Exclusive OR (XOR)
1001
0011
1111
1110
Shift5
0100
1001
1111
1111
0
Shift6
0010
0100
1111
1111
1
Generator polynomial
1010
0000
0000
0001
Exclusive OR (XOR)
1000
0100
1111
1110
Shift7
0100
0010
0111
1111
0
Shift8
0010
0001
0011
1111
1
Generator polynomial
1010
0000
0000
0001
Exclusive OR (XOR)
1000
0001
0011
1110
0000
0111
Exclusive OR (XOR)
1000
0001
0011
1001
Shift 1
0100
0000
1001
1100
Generator polynomial
1010
0000
0000
0001
Exclusive OR (XOR)
1110
0000
1001
1101
Shift2
0111
0000
0100
1110
Generator polynomial
1010
0000
0000
0001
Exclusive OR (XOR)
1101
0000
0100
1111
Shift3
0110
1000
0010
0111
Generator polynomial
1010
0000
0000
0001
Exclusive OR (XOR)
1100
1000
0010
0110
Shift4
0110
0100
0001
Shift5
0011
0010
0000
Generator polynomial
1010
0000
0000
0001
Exclusive OR (XOR)
1001
0010
0000
1000
Shift6
0100
1001
0000
0100
0
Shift7
0010
0100
1000
0010
0
Shift8
0001
0010
0100
0001
0
CRC value
12H
3
4
5
1
6
1
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
1
0011
0
7
1001
1
8
41H
UTILITY PACKAGE
(GX Configurator-MB)
07H(Function)
1
SYSTEM
CONFIGURATION
Exclusive OR (XOR)
1111
0000
SPECIFICATIONS
1111
MODBUS(R)
STANDARD FUNCTIONS
1111
02H(Station No.)
Flag
FUNCTION
(Load the register whose 16 bits are all "1")
16-bit register (MSB)
PARAMETER SETTING
CRC error check procedure
OVERVIEW
The following is a calculation example in the case where function code 07H is sent to
station No. 2.
4.2 Frame Specifications
4.2.1 Frame mode
4 - 12
4
MODBUS(R) STANDARD FUNCTIONS
Address field
(02H)
Function code
CRC (Error check)
(07H)
(41H)
(12H)
Figure 4.3 Frame for CRC calculation
(b) ASCII mode
In this mode, frames are received or sent in units of 2 characters (2 bytes) in
ASCII codes.
The frame specifications are compliant with the MODBUS
specifications.
Start
Address field
Function code
:
(3AH)
2 characters
2 characters
Data
n x 2 characters
(n = 0 to 252)
Error check
2 characters
protocol
END
CR + LF
(0DH) (0AH)
Error check calculation range
Figure 4.4 Frame in ASCII mode
Remark
The error check in the ASCII mode is conducted by LRC (Longitudinal
Redundancy Check).
The QJ71MB91 calculates the LRC by the following steps.
Please follow the same steps to calculate the LRC when conducting an error
check on the target device.
1) To calculate the LRC, convert the ASCII codes within the error check range
into the RTU format (binary).
2) Add the figures in units of contiguous 8 bits in the frame. (Excluding carries
during addition.)
3) Change the result of the above 2) to a 2's complement. (Reverse the bits and
add 01H.)
4) Convert the result of 3) to an ASCII code.
4 - 13
4.2 Frame Specifications
4.2.1 Frame mode
4
MODBUS(R) STANDARD FUNCTIONS
1
The following are calculation examples in the case where function code 01H is
sent to station No. 2.
OVERVIEW
Table4.6 LRC calculation procedure (when sending a request message)
Station No. (address field)
02
0000
0010
Function code
01
0000
0001
Head coil number (H)
00
0000
0000
Head coil number(L)
00
0000
0000
Read points (H)
00
0000
0000
Read points (L)
08
+0000
1000
Addition result
0B
0000
1011
Bit reversal 1
F4
1111
0100
+1
1
LRC (Error check)
F5
1111
0101
F
SPECIFICATIONS
F5
5
Table4.7 LRC calculation procedure (when receiving a response message)
4
02
0000
0010
Function code
01
0000
0001
Head coil number(H)
00
0000
0000
Head coil number(L)
00
0000
0000
Read points (H)
00
0000
0000
Read points (L)
08
0000
1000
LRC (Error check)
F5
+1111
0101
Addition result
00
0000
0000
(00H)
30H
32H
30H
31H
30H
30H
30H
30H
(00H)
30H
30H
(08H)
30H
38H
CRC
(Error check)
(F5H)
"CR"
46H
0DH
35H
"LF"
6
0AH
Figure 4.5 Frame for LRC calculation
(2) Frame mode setting
The frame mode is set in the intelligent function module switch setting.
(
7
Section 6.6)
PARAMETER SETTING
3AH
(00H)
Read points
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Head input number
Function code
(01H)
5
8
UTILITY PACKAGE
(GX Configurator-MB)
Address field
(02H)
Station No. (address field)
MODBUS(R)
STANDARD FUNCTIONS
LRC in reception of a response message
Start
:
3
FUNCTION
2's complement
2
SYSTEM
CONFIGURATION
LRC in request message transmission
4.2 Frame Specifications
4.2.1 Frame mode
4 - 14
4
MODBUS(R) STANDARD FUNCTIONS
4.3 Protocol Data Unit Formats by Functions
This section describes MODBUS
protocol data unit formats used in the QJ71MB91.
(1) Precautions
(a) Device number specified in messages
When specifying a device number in a message, specify it as "(Device number) 1".
However, this does not apply to the file and device numbers specified for reading/
writing the extended file register.
(Example) When reading input 32 (100032) with Read Discrete Inputs (FC: 02)
Data
Function code
Function code
Read points
Head input number
001FH
02H
(H)
0001H
(L)
(H)
(L)
Specify 31 (001FH) for the head input number
to read the input 32 (100032) status.
Figure 4.6 Specifying the MODBUS
device number
The device number to be stored in the response message is "(Device number of
actually read/written device) - 1".
(b) When the QJ71MB91 receives a broadcast request message
Although the processing (read/write, diagnostics, etc.) requested by the request
message is performed, no response message is sent to the master.
(c) When the QJ71MB91 receives a request message in the listen only mode
The request message is discarded except for a particular case.
To receive the request message, change it to the online mode.
(
4 - 15
Section 4.11.5)
4.3 Protocol Data Unit Formats by Functions
MODBUS(R) STANDARD FUNCTIONS
1
message is completed in error, an exception code is sent to the master.( (
"Response message formats (when completed with an error)" in Section 4.4 to 4.20.)
(a) Storage location of exception code and error code
The exception code is also stored in the buffer memory of the QJ71MB91.
Furthermore, for identification of detailed causes, an error code is stored in the
QJ71MB91 buffer memory.
The exception code and error codes can be confirmed by the error log area of the
Section 11.4)
3
(3) How to see the request/response message formats provided in Section
4.4 to 4.20
Area name
Data
Function code
Frame contents
[For request message format]
Setting range
[For response message format]
Value stored to the
response message
Function
code
(01H)
Head coil number
(0000H to FFFFH)
(H)
1 byte (8 bits)
1 byte (8 bits) . . .
(L)
Read points
(0001H to 07D0H)
(H)
4
MODBUS(R)
STANDARD FUNCTIONS
(a) Request/Response message format diagram
The following shows how to see the request/response message format diagrams
provided in Section 4.4 to 4.20.
SPECIFICATIONS
buffer memory (address: 0CFEH to 0DFFH).(
2
SYSTEM
CONFIGURATION
When the processing (read/write, diagnostics, etc.) requested by the request
OVERVIEW
(2) When the processing is completed in error at the slave (QJ71MB91)
(L)
When a single data is expressed
by 2 bytes, set the upper byte
(8 bits) as (H) and the lower byte
(8 bits) as (L).
5
FUNCTION
Figure 4.7 Request/Response message format diagram
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
4
4.3 Protocol Data Unit Formats by Functions
4 - 16
4
MODBUS(R) STANDARD FUNCTIONS
(b) Frame mode of the message format
The message formats in Section 4.4 to 4.20 are based on the case in the RTU
mode.
For use in ASCII mode, convert the values into ASCII codes.
(Conversion example)
(RTU mode)
Data
Function code
Head coil number
(006EH)
Function
code
(01H)
(H)
Read points
(003FH)
(H)
(L)
(L)
Convert RTU mode to ASCII mode
(ASCII mode)
Function code
1
0
(31H)
(30H)
(H)
(L)
Data
Data
Function code
Head coil number
0
(30H)
0
(30H)
6
(36H)
(H)
Read points
E
(45H)
0
(30H)
(L)
(H)
0
(30H)
3
(33H)
F
(46H)
(L)
Figure 4.8 Conversion example from RTU mode to ASCII mode
(c) Response message format
The response message formats issued from the slave to the master differs
depending on whether the slave has normally completed or failed to handle the
requested processing (read/write, diagnostics, etc.)
The formats for normal and error completions are shown in Section 4.4 to 4.20.
4 - 17
4.3 Protocol Data Unit Formats by Functions
MODBUS(R) STANDARD FUNCTIONS
1
OVERVIEW
4.4 Read Coils (FC: 01)
Reads the status (ON/OFF) of one or more coils.
(1) Request message format (Master
2
Read points
(0001H to 07D0H)
Head coil number
(0000H to FFFFH)
(L)
(H)
SYSTEM
CONFIGURATION
Data
Function code
Function
code
(01H)
Slave)
(L)
(H)
3
(2) Response message format (Slave
SPECIFICATIONS
Figure 4.9 Read coils (Request message)
Master)
(When completed normally)
Data
Function
code
(01H)
Number of
read bytes
n
Device data
1
4
Device data
n
MODBUS(R)
STANDARD FUNCTIONS
Function code
(Number of read bytes n)
5
(Device data 1 to n)
b7
b6
b5
b4
b3
b2
b1
b0
FUNCTION
Device data 1
Bit device
storage order
Device data n
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
0 : OFF
1 : ON
The read coil statuses are stored in order from low-order to high-order bits.
When the number of read points is not a multiple of 8, the excess bits turn to 0.
Figure 4.10 Read coils (Normal response message)
7
Function code
Function code
(81H)
PARAMETER SETTING
(When completed with an error)
Data
Exception
code*1
8
Figure 4.11 Read coils (Exception message)
* 1 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
4.4 Read Coils (FC: 01)
4 - 18
UTILITY PACKAGE
(GX Configurator-MB)
4
4
MODBUS(R) STANDARD FUNCTIONS
4.5 Read Discrete Inputs (FC: 02)
Reads the status (ON/OFF) of one or more inputs.
(1) Request message format (Master
Function code
Data
Head input number
(0000H to FFFFH)
Function
code
(02H)
Slave)
Read points
(0001H to 07D0H)
(L)
(H)
(L)
(H)
Figure 4.12 Read discrete inputs (Request message)
(2) Response message format (Slave
Master)
(When completed normally)
Data
Function code
Number of
read bytes
n
Function
code
(02H)
Device data
1
Device data
n
(Number of read bytes n)
(Device data 1 to n)
b7
b6
b5
b4
b3
b2
b1
b0
Device data 1
Bit device
storage order
Device data n
0 : OFF
1 : ON
The read input statuses are stored in order from low-order to high-order bits.
When the number of read points is not a multiple of 8, the excess bits turn to 0.
Figure 4.13 Read discrete inputs (Normal response message)
(When completed with an error)
Function code
Function
code
(82H)
Data
Exception
code*1
Figure 4.14 Read discrete inputs (Exception message)
* 1 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
4 - 19
4.5 Read Discrete Inputs (FC: 02)
MODBUS(R) STANDARD FUNCTIONS
1
OVERVIEW
4.6 Read Holding Registers (FC: 03)
Reads the values of one or more holding registers.
(1) Request message format (Master
2
Head holding register number
(0000H to FFFFH)
(H)
SYSTEM
CONFIGURATION
Data
Function code
Function
code
(03H)
Slave)
Read points
(0001H to 007DH)
(L)
(L)
(H)
3
(2) Response message format (Slave
SPECIFICATIONS
Figure 4.15 Read holding registers (Request message)
Master)
(When completed normally)
Function code
Number of
read bytes
n x 2 *1
. . .
Device data
1
(H)
(H)
(L)
4
Device data
n
MODBUS(R)
STANDARD FUNCTIONS
Function
code
(03H)
Data
(L)
(Number of read bytes n x 2)
5
*1 For example, if n = 4, the number of read
bytes is calculated as 4 x 2 = 8 bytes.
FUNCTION
Figure 4.16 Read holding registers (Normal response message)
(When completed with an error)
Function
code
(83H)
Data
6
Exception
code *2
Figure 4.17 Read holding registers (Exception message)
* 2 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
7
PARAMETER SETTING
Section 11.4
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Function code
8
UTILITY PACKAGE
(GX Configurator-MB)
4
4.6 Read Holding Registers (FC: 03)
4 - 20
4
MODBUS(R) STANDARD FUNCTIONS
4.7 Read Input Registers (FC: 04)
Reads the values of one or more input registers.
(1) Request message format (Master
Data
Function code
Function
code
(04H)
Slave)
Head input register number
(0000H to FFFFH)
(H)
Read points
(0001H to 007DH)
(L)
(L)
(H)
Figure 4.18 Read input registers (Request message)
(2) Response message format (Slave
Master)
(When completed normally)
Data
Function code
Function
code
(04H)
Device data
1
Number of
read bytes
n x 2 *1
(H)
. . .
(L)
Device data
n
(H)
(L)
(Number of read bytes n x 2)
*1 For example, if n = 4, the number of read
bytes is calculated as 4 x 2 = 8 bytes.
Figure 4.19 Read input registers (Normal response message)
(When completed with an error)
Function code
Function
code
(84H)
Data
Exception
code *2
Figure 4.20 Read input registers (Exception message)
* 2 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
4 - 21
4.7 Read Input Registers (FC: 04)
MODBUS(R) STANDARD FUNCTIONS
1
OVERVIEW
4.8 Write Single Coil (FC: 05)
Writes a value (ON/OFF) to one coil.
(1) Request message format (Master
2
(H)
(L)
ON/OFF specification
0000H : OFF
FF00H : ON
(H)
(L)
3
Figure 4.21 Write single coil (Request message)
(2) Response message format (Slave
Master)
(When completed normally)
The slave returns the request message received from the master without change.
4
Function
code
(85H)
MODBUS(R)
STANDARD FUNCTIONS
(When completed with an error)
Function code
SPECIFICATIONS
Coil number
(0000H to FFFFH)
SYSTEM
CONFIGURATION
Data
Function code
Function
code
(05H)
Slave)
Data
Exception
code*1
5
Figure 4.22 Write single coil (Exception message)
* 1 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
FUNCTION
Section 11.4
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
4
4.8 Write Single Coil (FC: 05)
4 - 22
4
MODBUS(R) STANDARD FUNCTIONS
4.9 Write Single Register (FC: 06)
Writes a value to one holding register.
(1) Request message format (Master
Function code
Function
code
(06H)
Slave)
Data
Holding register number
(0000H to FFFFH)
(H)
(L)
Write data
(0000H to FFFFH)
(H)
(L)
Figure 4.23 Write single register (Request Message)
(2) Response message format (Slave
Master)
(When completed normally)
The slave returns the request message received from the master without change.
(When completed with an error)
Function code
Function
code
(86H)
Data
Exception
code*1
Figure 4.24 Write single register (Exception message)
* 1 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
4 - 23
4.9 Write Single Register (FC: 06)
MODBUS(R) STANDARD FUNCTIONS
1
OVERVIEW
4.10 Read Exception Status (FC: 07)
Reads error status.
(1) Request message format (Master
Slave)
2
SYSTEM
CONFIGURATION
Function code
Function code
(07H)
3
(2) Response message format (Slave
SPECIFICATIONS
Figure 4.25 Read exception status (Request message)
Master)
(When completed normally)
Data
Function
code
(07H)
Error
information *1
4
Figure 4.26 Read exception status (Normal request message)
* 1 The data of the device specified in the Setting error status read device (address: 000AH to 000BH)
in the buffer memory are stored in the error information area. (
Section 7.3.4)
MODBUS(R)
STANDARD FUNCTIONS
Function code
5
(When completed with an error)
Function
code
(87H)
Data
FUNCTION
Function code
Exception
code *2
Figure 4.27 Read exception status (Exception message)
* 2 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
4
4.10 Read Exception Status (FC: 07)
4 - 24
4
MODBUS(R) STANDARD FUNCTIONS
4.11 Diagnostics (FC:08)
Executes the various diagnostics and checks the QJ71MB91 status and communication
status.
4.11.1 Return query data (sub-function code: 00)
Returns the contents of the request message without change.
Used to check if the network or the target device is operating normally. (Loopback test)
(1) Request message format (Master
Function code
Sub-function code
Function
code
(08H)
Sub-function code
(0000H)
(H)
Slave)
Data
Arbitrary data
(L)
Figure 4.28 Return query data (Request message)
(2) Response message format (Slave
Master)
(When completed normally)
The slave returns the request message received from the master without change.
(When completed with an error)
Function code
Function
code
(88H)
Data
Exception
code*1
Figure 4.29 Return query data (Exception message)
* 1 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
4 - 25
4.11 Diagnostics (FC:08)
4.11.1 Return query data (sub-function code: 00)
MODBUS(R) STANDARD FUNCTIONS
1
The following data are cleared when executing the restart communications option.
• Data being received
• CH1/2 side error response code storage area in the buffer memory (address:
0002H/0004H)*1
• CH1/2 side detailed LED status storage area in the buffer memory (address:
• The ERR. LED OFF
Section 11.3)
*2
• Communications event count (
• Communications event log (
Section 4.12)
4
Section 4.13)*3
* 1 Clears only the receiving channel side area.
* 2 Clears the errors of the channel that has received the request message.
As the errors of other channels are not cleared, the LED will not turn off if an error has occurred on
any other channel.
* 3 Clears the data when the communications event log clear is specified in the request message.
MODBUS(R)
STANDARD FUNCTIONS
• Diagnostic counter (
3
SPECIFICATIONS
0006H/0007H)*1
2
SYSTEM
CONFIGURATION
Initializes the communication port of the receiving channel side and restarts the slave
function.
Restart is performed after returning the response message corresponding to a request
message.
The operation status returns to online mode when it was in the listen only mode.
OVERVIEW
4.11.2 Restart communications option (sub-function code: 01)
FUNCTION
5
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
4
4.11 Diagnostics (FC:08)
4.11.2 Restart communications option (sub-function code: 01)
4 - 26
4
MODBUS(R) STANDARD FUNCTIONS
(1) Request message format (Master
Function code
Function
code
(08H)
Slave)
Sub-function code
Sub-function code
(0001H)
Data
Clear setting of
Communications event log
0000H: Not clear
FF00H: Clear
(H)
(L)
(H)
(L)
Figure 4.30 Restart communications option (Request message)
(2) Response message format (Slave
Master)
(When completed normally)
The slave returns the request message received from the master without change.
However, if a request message is received during listen only mode, the status will only
return to online mode and no response message will be returned.
(When completed with an error)
Function code
Function
code
(88H)
Data
Exception
code*1
Figure 4.31 Restart communications option (Exception message)
* 1 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
4 - 27
4.11 Diagnostics (FC:08)
4.11.2 Restart communications option (sub-function code: 01)
MODBUS(R) STANDARD FUNCTIONS
1
OVERVIEW
4.11.3 Return diagnostic register (sub-function code: 02)
Reads out the detailed LED status of the QJ71MB91 to the master.
(1) Request message format (Master
Sub-function code
Function
code
(08H)
Sub-function code
(0002H)
(0000H)
(L)
(H)
2
Data
SYSTEM
CONFIGURATION
Function code
Slave)
(L)
(H)
3
Figure 4.32 Return diagnostic register (Request message)
Master)
SPECIFICATIONS
(2) Response message format (Slave
(When completed normally)
Function
code
(08H)
Sub-function code
Sub-function code
(0002H)
(L)
(H)
b15 b14 b13 b12 b11 b10 b9 b8
0
0
0 1/0 1/0 1/0 1/0 1/0
b7
0
b6
0
Data
4
Diagnostic register
value
(H)
MODBUS(R)
STANDARD FUNCTIONS
Function code
(L)
5
b5 b4 b3 b2 b1 b0
0 1/0 1/0 1/0 1/0 1/0
CH1 P/S
CH1 PRO.
CH1 SIO
CH1 side Detailed
LED status
(0: OFF, 1: ON)
CH1 ERR.
FUNCTION
CH1 C/N
6
CH2 C/N
CH2 P/S
CH2 PRO.
CH2 SIO
CH2 side Detailed
LED status
(0: OFF, 1: ON)
CH2 ERR.
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Unused (Fixed to 0)
7
PARAMETER SETTING
Unused (Fixed to 0)
The QJ71MB91 stores the lower 8 bits of the buffer memory's
Detailed LED status as a diagnostic register. (address: 0006H/0007H)
Figure 4.33 Return diagnostic register (Normal response message)
8
Remark
UTILITY PACKAGE
(GX Configurator-MB)
4
Refer to the following for each items of the detailed LED status.
Section 11.2
4.11 Diagnostics (FC:08)
4.11.3 Return diagnostic register (sub-function code: 02)
4 - 28
4
MODBUS(R) STANDARD FUNCTIONS
(When completed with an error)
Function code
Function
code
(88H)
Data
Exception
code*1
Figure 4.34 Return diagnostic register (Exception message)
* 1 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
4 - 29
4.11 Diagnostics (FC:08)
4.11.3 Return diagnostic register (sub-function code: 02)
MODBUS(R) STANDARD FUNCTIONS
1
Address field
:
(3AH)
2 characters
Function code
Data
Error check
END
2 characters
n x 2 characters
(n = 0 to 252)
2 characters
CR + LF
(0DH) (0AH)
Change this into a specified data.
3
Figure 4.35 Change part in the end code
Function code
Sub-function code
Function
code
(08H)
Sub-function code
(0003H)
(H)
Slave)
SPECIFICATIONS
(1) Request message format (Master
Data
Input delimiter
setting
(00H to FFH)
4
(00H)
(L)
Figure 4.36 Change ASCII input delimiter (Request message)
(2) Response message format (Slave
2
Master)
(When completed normally)
The slave returns the request message received from the master without change.
MODBUS(R)
STANDARD FUNCTIONS
Start
SYSTEM
CONFIGURATION
Changes the 2nd byte (LF(0AH)) of the end code in the ASCII mode to a specified data.
The specified data is stored in the 2nd byte of end code in the buffer memory. (address:
0F0CH/0F4CH)
OVERVIEW
4.11.4 Change ASCII input delimiter (sub-function code: 03)
5
Function
code
(88H)
Data
Exception
code*1
6
Figure 4.37 Change ASCII input delimiter (Exception message)
* 1 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Function code
FUNCTION
(When completed with an error)
7
PARAMETER SETTING
POINT
This function is used only for 1:1 connections.
Do not use this function for 1:n connections.
8
UTILITY PACKAGE
(GX Configurator-MB)
4
4.11 Diagnostics (FC:08)
4.11.4 Change ASCII input delimiter (sub-function code: 03)
4 - 30
4
MODBUS(R) STANDARD FUNCTIONS
4.11.5 Force listen only mode (sub-function code: 04)
Places a slave into the offline mode.
Used when disconnecting a slave from the network.
When QJ71MB91 is set in the listen only mode, the status is as follows:
• Ignores all request messages except for those of restart communications
option.(
Section 4.11.2)
• Stops counting of the diagnostic counter.(
Section 11.3)
• Continues recording with the communications event log.(
(1) Request message format (Master
Function code
Function
code
(08H)
Slave)
Sub-function code
Data
Sub-function code
(0004H)
(0000H)
(H)
(L)
Section 4.13)
(H)
(L)
Figure 4.38 Force listen only mode (Request message)
(2) Response message format (Slave
Master)
(When completed normally)
No response message is returned because the listen only mode (offline status) is
active.
(When completed with an error)
Function code
Function
code
(88H)
Data
Exception
code*1
Figure 4.39 Force listen only mode (Exception message)
* 1 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
4 - 31
4.11 Diagnostics (FC:08)
4.11.5 Force listen only mode (sub-function code: 04)
MODBUS(R) STANDARD FUNCTIONS
1
• Power OFF
Section 4.11.2)
ON, PLC CPU reset
SYSTEM
CONFIGURATION
• Restart communications option (
2
SPECIFICATIONS
3
MODBUS(R)
STANDARD FUNCTIONS
4
FUNCTION
5
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
2.
Whether the QJ71MB91 has been switched to listen only mode or not can be
checked in the Communications mode of the buffer memory (address: 0F0DH/
0F4DH).
0000H: Online mode
0001H: Listen only mode
The listen only mode can be changed to online mode by either of the
following:
7
PARAMETER SETTING
1.
OVERVIEW
POINT
8
UTILITY PACKAGE
(GX Configurator-MB)
4
4.11 Diagnostics (FC:08)
4.11.5 Force listen only mode (sub-function code: 04)
4 - 32
4
MODBUS(R) STANDARD FUNCTIONS
4.11.6 Clear counters and diagnostic register (sub-function code: 10)
Clears counters (e.g. message count).
Also, clears the diagnostic register and the error of the channel where the request
message has been received.
The following counters will be cleared.(
• Bus message count
• Bus communication error count
• Exception error count
• Slave message count
• Slave no-response count
• Slave NAK count
• Slave busy count
• Character overrun error count
• Communications event count (
Section 11.3)
Section 4.12)
The following diagnostic resisters will be cleared.
• CH1/2 side detailed LED status storage area of the buffer memory (address:
0006H/0007H)*1
• CH1/2 side error response code storage area of the buffer memory (address:
0002H/0004H)*1
* 1 Clears only the receiving channel side area.
4 - 33
4.11 Diagnostics (FC:08)
4.11.6 Clear counters and diagnostic register (sub-function code: 10)
MODBUS(R) STANDARD FUNCTIONS
1
Sub-function code
Data
Function
code
(08H)
Sub-function code
(000AH)
(0000H)
(H)
(L)
(H)
2
(L)
SYSTEM
CONFIGURATION
Function code
OVERVIEW
Slave)
Figure 4.40 Clear counters and diagnostic register (Request message)
(2) Response message format (Slave
Master)
(When completed with an error)
Function code
Function
code
(88H)
3
SPECIFICATIONS
(When completed normally)
The slave returns the request message received from the master without change.
Data
4
Exception
code*1
Figure 4.41 Clear counters and diagnostic register (Exception message)
* 1 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
MODBUS(R)
STANDARD FUNCTIONS
(1) Request message format (Master
FUNCTION
5
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
4
4.11 Diagnostics (FC:08)
4.11.6 Clear counters and diagnostic register (sub-function code: 10)
4 - 34
4
MODBUS(R) STANDARD FUNCTIONS
4.11.7 Return bus message count (sub-function code: 11)
Reads out the number of messages detected on the line to the master.
(1) Request message format (Master
Function code
Slave)
Sub-function code
Function
code
(08H)
Data
Sub-function code
(000BH)
(H)
(0000H)
(L)
(L)
(H)
Figure 4.42 Return bus message count (Request message)
(2) Response message format (Slave
Master)
(When completed normally)
Function code
Sub-function code
Function
code
(08H)
Sub-function code
(000BH)
(H)
Data
Bus message count value
(0000H to FFFFH) *1
(L)
(H)
(L)
The QJ71MB91 returns the bus message count value of the
buffer memory to the master. (address: 0F00H/0F40H)
Figure 4.43 Return bus message count (Normal response message)
* 1 Refer to the following for the relevant counts, count clear methods and precautions.
Section 11.3
(When completed with an error)
Function code
Data
Function
code
(88H)
Exception
code *2
Figure 4.44 Return bus message count (Exception message)
* 2 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
4 - 35
4.11 Diagnostics (FC:08)
4.11.7 Return bus message count (sub-function code: 11)
MODBUS(R) STANDARD FUNCTIONS
1
OVERVIEW
4.11.8 Return bus communication error count (sub-function code: 12)
Reads out the number of error messages detected on the line to the master.
Function code
Slave)
Sub-function code
Sub-function code
(000CH)
Function
code
(08H)
(H)
(L)
2
Data
SYSTEM
CONFIGURATION
(1) Request message format (Master
(0000H)
(L)
(H)
3
(2) Response message format (Slave
SPECIFICATIONS
Figure 4.45 Return bus communication error count (Request message)
Master)
(When completed normally)
Sub-function code
Function
code
(08H)
Sub-function code
(000CH)
(H)
(L)
Data
4
Bus communication
error count value
(0000H to FFFFH) *1
(H)
MODBUS(R)
STANDARD FUNCTIONS
Function code
(L)
The QJ71MB91 returns the bus communication error count value
of the buffer memory to the master. (address: 0F01H/0F41H)
5
Figure 4.46 Return bus communication error count (Normal response message)
* 1 Refer to the following for the relevant counts, count clear methods and precautions.
FUNCTION
Section 11.3
(When completed with an error)
Function
code
(88H)
Data
6
Exception
code *2
Figure 4.47 Return bus communication error count (Exception message)
* 2 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
7
PARAMETER SETTING
Section 11.4
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Function code
8
UTILITY PACKAGE
(GX Configurator-MB)
4
4.11 Diagnostics (FC:08)
4.11.8 Return bus communication error count (sub-function code: 12)
4 - 36
4
MODBUS(R) STANDARD FUNCTIONS
4.11.9 Return bus exception error count (sub-function code: 13)
Reads out the frequency of exception errors to the master.
(1) Request message format (Master
Function code
Function
code
(08H)
Slave)
Sub-function code
Data
Sub-function code
(000DH)
(H)
(0000H)
(L)
(L)
(H)
Figure 4.48 Return bus exception error count (Request message)
(2) Response message format (Slave
Master)
(When completed normally)
Function code
Function
code
(08H)
Sub-function code
Sub-function code
(000DH)
(H)
(L)
Data
Exception error count value
(0000H to FFFFH) *1
(H)
(L)
The QJ71MB91 returns the exception error count value of the
buffer memory to the master. (address: 0F0AH/0F4AH)
Figure 4.49 Return bus exception error count (Normal response message)
* 1 Refer to the following for the relevant counts, count clear methods and precautions.
Section 11.3
(When completed with an error)
Function code
Function
code
(88H)
Data
Exception
code *2
Figure 4.50 Return bus exception error count (Exception message)
* 2 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
4 - 37
4.11 Diagnostics (FC:08)
4.11.9 Return bus exception error count (sub-function code: 13)
MODBUS(R) STANDARD FUNCTIONS
1
Reads out the number of the slave message processing to the master. (Including receive
of request messages from broadcast.)
Function code
Sub-function code
Data
Function
code
(08H)
Sub-function code
(000EH)
(0000H)
(H)
(L)
2
Slave)
SYSTEM
CONFIGURATION
(1) Request message format (Master
3
(L)
(H)
OVERVIEW
4.11.10 Return slave message count (sub-function code: 14)
(2) Response message format (Slave
SPECIFICATIONS
Figure 4.51 Return slave message count (Request message)
Master)
(When completed normally)
Function code
Sub-function code
Data
Function
code
(08H)
Sub-function code
(000EH)
Slave message count value
(0000H to FFFFH) *1
(L)
(H)
MODBUS(R)
STANDARD FUNCTIONS
(H)
4
(L)
The QJ71MB91 returns the slave message count value of the
buffer memory to the master. (address: 0F06H/0F46H)
5
Figure 4.52 Return slave message count (Normal response message)
* 1 Refer to the following for the relevant counts, count clear methods and precautions.
FUNCTION
Section 11.3
(When completed with an error)
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Function
code
(88H)
6
Data
Exception
code *2
Figure 4.53 Return slave message count (Exception message)
* 2 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
7
PARAMETER SETTING
Function code
8
UTILITY PACKAGE
(GX Configurator-MB)
4
4.11 Diagnostics (FC:08)
4.11.10 Return slave message count (sub-function code: 14)
4 - 38
4
MODBUS(R) STANDARD FUNCTIONS
4.11.11 Return slave no response count (sub-function code: 15)
Reads to out the number of broadcast request messages received to the master.
(1) Request message format (Master
Slave)
Function code
Sub-function code
Data
Function
code
(08H)
Sub-function code
(000FH)
(0000H)
(H)
(L)
(L)
(H)
Figure 4.54 Return slave no response count (Request message)
(2) Response message format (Slave
Master)
(When completed normally)
Function code
Sub-function code
Function
code
(08H)
Sub-function code
(000FH)
(H)
(L)
Data
Slave no-response count value
(0000H to FFFFH) *1
(H)
(L)
The QJ71MB91 returns the slave no response count value of the
buffer memory to the master. (address: 0F07H/0F47H)
Figure 4.55 Return slave no response count (Normal response message)
* 1 Refer to the following for the relevant counts, count clear methods and precautions.
Section 11.3
(When completed with an error)
Function code
Function
code
(88H)
Data
Exception
code *2
Figure 4.56 Return slave no response count (Exception message)
* 2 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
4 - 39
4.11 Diagnostics (FC:08)
4.11.11 Return slave no response count (sub-function code: 15)
MODBUS(R) STANDARD FUNCTIONS
1
OVERVIEW
4.11.12 Return slave NAK count (sub-function code: 16)
Reads out the number of NAK responses to the master.
The QJ71MB91 always returns "0".
Function code
Sub-function code
Data
Function
code
(08H)
Sub-function code
(0010H)
(0000H)
(H)
(L)
2
Slave)
SYSTEM
CONFIGURATION
(1) Request message format (Master
3
(L)
(H)
(2) Response message format (Slave
SPECIFICATIONS
Figure 4.57 Return slave NAK count (Request message)
Master)
(When completed normally)
Function code
Sub-function code
Data
Function
code
(08H)
Sub-function code
(0010H)
Slave NAK count value
(0000H) *1
(L)
(H)
MODBUS(R)
STANDARD FUNCTIONS
(H)
4
(L)
The QJ71MB91 returns the slave NAK count value of the buffer
memory to the master. (address: 0F08H/0F48H)
5
Figure 4.58 Return slave NAK count (Normal response message)
* 1 Refer to the following for the relevant counts, count clear methods and precautions.
FUNCTION
Section 11.3
(When completed with an error)
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Function
code
(88H)
6
Data
Exception
code *2
Figure 4.59 Return slave NAK count (Exception message)
* 2 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
7
PARAMETER SETTING
Function code
8
UTILITY PACKAGE
(GX Configurator-MB)
4
4.11 Diagnostics (FC:08)
4.11.12 Return slave NAK count (sub-function code: 16)
4 - 40
4
MODBUS(R) STANDARD FUNCTIONS
4.11.13 Return slave busy count (sub-function code: 17)
Reads out the number of busy responses to the master.
The QJ71MB91 always returns "0".
(1) Request message format (Master
Slave)
Function code
Sub-function code
Data
Function
code
(08H)
Sub-function code
(0011H)
(0000H)
(H)
(L)
(L)
(H)
Figure 4.60 Return slave busy count (Request message)
(2) Response message format (Slave
Master)
(When completed normally)
Function code
Sub-function code
Data
Function
code
(08H)
Sub-function code
(0011H)
Slave busy count value
(0000H) *1
(H)
(L)
(H)
(L)
The QJ71MB91 returns the slave busy count value of the buffer
memory to the master. (address: 0F09H/0F49H)
Figure 4.61 Return slave busy count (Normal response message)
* 1 Refer to the following for the relevant counts, count clear methods and precautions.
Section 11.3
(When completed with an error)
Function code
Function
code
(88H)
Data
Exception
code *2
Figure 4.62 Return slave busy count (Exception message)
* 2 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
4 - 41
4.11 Diagnostics (FC:08)
4.11.13 Return slave busy count (sub-function code: 17)
MODBUS(R) STANDARD FUNCTIONS
1
To the master, reads out the number of times the request message size exceeds the upper
limit.
Function code
Sub-function code
Data
Function
code
(08H)
Sub-function code
(0012H)
(0000H)
(H)
(L)
2
Slave)
SYSTEM
CONFIGURATION
(1) Request message format (Master
3
(L)
(H)
OVERVIEW
4.11.14 Return bus character overrun count (sub-function code: 18)
(2) Response message format (Slave
SPECIFICATIONS
Figure 4.63 Return bus character overrun count (Request message)
Master)
(When completed normally)
Sub-function code
Function
code
(08H)
Sub-function code
(0012H)
(H)
(L)
Data
4
MODBUS(R)
STANDARD FUNCTIONS
Function code
Bus character overrun
count value
(0000H to FFFFH) *1
(H)
(L)
The QJ71MB91 returns the bus character overrun count value
of the buffer memory to the master. (address: 0F02H/0F42H)
5
Figure 4.64 Return bus character overrun count (Normal response message)
* 1 Refer to the following for the relevant counts, count clear methods and precautions.
FUNCTION
Section 11.3
(When completed with an error)
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Function
code
(88H)
6
Data
Exception
code *2
Figure 4.65 Return bus character overrun count (Exception message)
* 2 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
Remark
8
Refer to the following for the size of request messages.
Section 4.2.1
4.11 Diagnostics (FC:08)
4.11.14 Return bus character overrun count (sub-function code: 18)
7
PARAMETER SETTING
Function code
UTILITY PACKAGE
(GX Configurator-MB)
4
4 - 42
4
MODBUS(R) STANDARD FUNCTIONS
4.11.15 Return IOP overrun error count (sub-function code: 19)
Reads the IOP overrun error counter value to the master.
The QJ71MB91 returns to the master the number of times the request message size
exceeds the upper limit.
(Same as the Return bus character overrun count)
(1) Request message format (Master
Slave)
Function code
Sub-function code
Data
Function
code
(08H)
Sub-function code
(0013H)
(0000H)
(H)
(L)
(L)
(H)
Figure 4.66 Return IOP overrun error count (Request message)
(2) Response message format (Slave
Master)
(When completed normally)
Function code
Sub-function code
Function
code
(08H)
Sub-function code
(0013H)
(H)
(L)
Data
Bus character
overrun count value
(0000H to FFFFH) *1
(H)
(L)
The QJ71MB91 returns the bus character overrun count value
of the buffer memory to the master. (address: 0F02H/0F42H)
Figure 4.67 Return IOP overrun error count (Normal response message)
* 1 Refer to the following for the relevant counts, count clear methods and precautions.
Section 11.3
(When completed with an error)
Function code
Function
code
(88H)
Data
Exception
code *2
Figure 4.68 Return IP overrun error count (Exception message)
* 2 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
4 - 43
4.11 Diagnostics (FC:08)
4.11.15 Return IOP overrun error count (sub-function code: 19)
MODBUS(R) STANDARD FUNCTIONS
1
OVERVIEW
4.11.16 Clear overrun counter and flag (sub-function code: 20)
Clears the overrun error counter and flag.
The QJ71MB91 clears the character overrun error counter value.
Function code
Sub-function code
Data
Function
code
(08H)
Sub-function code
(0014H)
(0000H)
(H)
(L)
2
Slave)
(H)
SYSTEM
CONFIGURATION
(1) Request message format (Master
3
(L)
(2) Response message format (Slave
Master)
(When completed normally)
The slave returns the request message received from the master without change.
SPECIFICATIONS
Figure 4.69 Clear overrun counter and flag (Request message)
MODBUS(R)
STANDARD FUNCTIONS
4
(When completed with an error)
Function code
Function
code
(88H)
Data
Exception
code*1
5
* 1 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
FUNCTION
Figure 4.70 Clear overrun counter and flag (Exception message)
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
4
4.11 Diagnostics (FC:08)
4.11.16 Clear overrun counter and flag (sub-function code: 20)
4 - 44
4
MODBUS(R) STANDARD FUNCTIONS
4.12 Get Communications Event Counter (FC: 11)
Acquires the number of messages whose requested actions (read/write, diagnostics, etc.)
have been normally completed.
Whether the action corresponding to the request message is normally completed or not
can be checked.
(1) Request message format (Master
Slave)
Function code
Function
code
(0BH)
Figure 4.71 Get communications event counter (Request message)
(2) Response message format (Slave
Master)
(When completed normally)
Function code
Function
code
(0BH)
Data
Program command status
(0000H) *1
(H)
(L)
Communications
event count value
(0000H to FFFFH) *2
(H)
(L)
The QJ71MB91 stores the communications event count value of the buffer
memory as the communications event count value. (address: 0F0BH/0F4BH)
Figure 4.72 Get communications event counter (Normal response message)
* 1 Since the QJ71MB91 does not support any program commands, 0000H is stored.
* 2 The count is stopped if it has reached FFFFH.
Reset the counter by either of the following methods when restarting the count.
Clearing the counter and diagnostic register (
Restart communications option (
Power OFF
Section 4.11.6)
Section 4.11.2)
ON, or PLC CPU reset
POINT
The communications event counter counts only when the processing (read/write,
diagnostics, etc.) has completed normally.
The communications event counter does not count in the case of the following:
• The processing has completed with an error.
• When receiving a request message containing a function code that the
QJ71MB91 does not support
• When receiving the Get communications event counter (FC: 11) and Get
communications event log (FC: 12)
4 - 45
4.12 Get Communications Event Counter (FC: 11)
MODBUS(R) STANDARD FUNCTIONS
1
Function code
Data
Function
code
(8BH)
Exception
code*1
OVERVIEW
(When completed with an error)
Figure 4.73 Get communications event counter (Exception message)
* 1 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
SYSTEM
CONFIGURATION
2
SPECIFICATIONS
3
MODBUS(R)
STANDARD FUNCTIONS
4
FUNCTION
5
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
4
4.12 Get Communications Event Counter (FC: 11)
4 - 46
4
MODBUS(R) STANDARD FUNCTIONS
4.13 Get Communications Event Log (FC: 12)
Acquires the communications event log of the QJ71MB91 into the master.
(1) Request message format (Master
Slave)
Function code
Function
code
(0CH)
Figure 4.74 Get communications event log (Request message)
(2) Response message format (Slave
Master)
(When completed normally)
Function code
Function
code
(0CH)
Data
Number of
read bytes
Program command
status
(0000H) *1
Communications event
count value
(0000H to FFFFH) *2
(L)
(H)
(H)
(L)
Bus message count value
(0000H to FFFFH) *3
(H)
Communications
event log No. 0 *3
Communications
event log No. 63
(L)
(Number of read bytes)
Figure 4.75 Get communications event log (Normal response message)
* 1 Since the QJ71MB91 does not support any program commands, 0000H is always stored.
* 2 Refer to the following for the relevant counts, count clear methods and precautions.
Section 4.12
* 3 Refer to the following for the relevant counts, count clear methods and precautions.
Section 11.3
* 4 Refer to the following for details of the communications event log.
This section (2) (a), (2) (b)
(When completed with an error)
Function code
Function
code
(8CH)
Data
Exception
code *5
Figure 4.76 Get communications event log (Exception message)
* 5 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
4 - 47
4.13 Get Communications Event Log (FC: 12)
MODBUS(R) STANDARD FUNCTIONS
(a) Communications event log
When the slave (QJ71MB91) receives the Get communications event log (FC: 12)
from the master, it returns the data of the Communications event log area in the
buffer memory to the master.(address: 0F20H to 0F3FH/0F60H to 0F7FH)
2
SYSTEM
CONFIGURATION
QJ71MB91 buffer memory (CH1)
0F1FH
1
(3871) Communications event log count (0 to 64) *
Communications event log 0
0F20H (L)
(3872) (H)
New logs
Communications event log 1
0F21H (L)
(3873) (H)
Communications event log 2
0F3FH (L)
(3903) (H)
Communications event log 62
OVERVIEW
1
Communications event log 3
3
Figure 4.77 Communications event log
* 1 The number of communications event logs can be confirmed only with the buffer memory.
It is different from the communications event counter value in the response message.
* 2 If the number of communications event logs exceeds 64, the oldest log is deleted and the latest log
is stored to Communications event log 0.
Communications event logs are stored in the buffer memory at the following
timing.
1) When receiving a request message
The slave (QJ71MB91) stores the communications event log before executing
the processing of the request message.
For the relevant communications event, "1" is stored.
b2 b1 b0
0 1/0 0
4
5
FUNCTION
b7 b6 b5 b4 b3
1 1/0 1/0 1/0 0
SPECIFICATIONS
Old logs
MODBUS(R)
STANDARD FUNCTIONS
Communications event log 63 *2
Unused (Fixed to 0)
Communication error
6
Unused (Fixed to 0)
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Bus character overrun error
In listen only mode
Broadcast message reception
Fixed to 1
Figure 4.78 Communications event at request message transmission
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
4
4.13 Get Communications Event Log (FC: 12)
4 - 48
4
MODBUS(R) STANDARD FUNCTIONS
2) When sending a response message
The slave (QJ71MB91) stores the communications event log after sending the
response message.
For the relevant communications event, "1" is stored.
b7
0
b6
1
b5
0
b4
0
b3
0
b2 b1 b0
0 1/0 1/0
Message error (Exception code 01H to 03H)
Processing interruption (Exception code 04H)
Unused (Fixed to 0) *1
Fixed to 1
Unused(Fixed to "0")
Figure 4.79 Communications event at response message transmission
* 1 While the occurrence of busy status (exception code 05H to 07H) is stored for the MODBUS
protocol, "0" is stored for the QJ71MB01 because this kind of events does not occur in it.
3) When switching to the listen only mode
The slave (QJ71MB91) stores the communications event log when switching
to the listen only mode.
04H is stored to the communications event log.
b7
0
b6
0
b5
0
b4
0
b3
0
b2
1
b1
0
b0
0
Figure 4.80 Communications event when switching to listen only mode
4) When processing restart communications option
The slave (QJ71MB91) stores the communications event log when processing
the restart communications option.
00H is stored to the communications event log.
b7
0
b6
0
b5
0
b4
0
b3
0
b2
0
b1
0
b0
0
Figure 4.81 Communications event when processing restart communications option
(b) Clearing the communications event log
The communications event can be cleared by either of the following:
Clear setting of the communications event log with the restart communications
option (
Power OFF
4 - 49
Section 4.11.2)
ON, or PLC CPU reset
4.13 Get Communications Event Log (FC: 12)
MODBUS(R) STANDARD FUNCTIONS
1
OVERVIEW
4.14 Write Multiple Coils (FC: 15)
Writes values (ON/OFF) to multiple coils.
(1) Request message format (Master
Function code
2
Head coil number
(0000H to FFFFH)
(L)
Device
data
1
Number of
bytes n*1
(0001H to
00F6H)
. . .
Device
data
n
(L)
(H)
3
(Device data 1 to n )
b7
b6
b5
b4
b3
b2
b1
SPECIFICATIONS
(Number of bytes n)
b0
Device data 1
4
MODBUS(R)
STANDARD FUNCTIONS
Data storage order
Device data n
0 : OFF
1 : ON
The values (ON/OFF) stored into the device data 1 to n are written to
the coils in order from low-order to high-order bits of the device data.
5
Figure 4.82 Write multiple coils (Request message)
* 1 The number of the specified write points must be matched with the number of bits specified as the
number of bytes.
For example, when the write points are set to 16, set the number of bytes to 2 bytes (= 16 bits).
FUNCTION
(H)
Write points*1
(0001H to 07B0H)
SYSTEM
CONFIGURATION
Data
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
7
PARAMETER SETTING
Function
code
(0FH)
Slave)
8
UTILITY PACKAGE
(GX Configurator-MB)
4
4.14 Write Multiple Coils (FC: 15)
4 - 50
4
MODBUS(R) STANDARD FUNCTIONS
(2) Response message format (Slave
Master)
(When completed normally)
Data
Function code
Function
code
(0FH)
Head coil number
Write points
(The same head coil number
value as in the request
message is stored.)
(L)
(H)
(The same write points
value as in the request
message is stored.)
(L)
(H)
Figure 4.83 Write multiple coils (Normal response message)
(When completed with an error)
Function code
Data
Function
code
(8FH)
Exception
code*1
Figure 4.84 Write multiple coils (Exception message)
* 1 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
4 - 51
4.14 Write Multiple Coils (FC: 15)
4
MODBUS(R) STANDARD FUNCTIONS
1
OVERVIEW
4.15 Write Multiple Registers (FC: 16)
Writes values to multiple holding registers.
(1) Request message format (Master
Function code
2
Head holding
register number
(0000H to FFFFH)
(L)
(H)
Device
data
1
Number of
bytes, n x 2 *1
(0001H to
00F6H)
(L)
(L)
(H)
Device
data
n
. . .
(H)
(L)
3
SPECIFICATIONS
(Number of bytes n x 2)
Figure 4.85 Write multiple registers (Request message)
* 1 The number of the specified write points must be matched with the number of bytes.
(2) Response message format (Slave
Master)
4
Function code
Function
code
(10H)
MODBUS(R)
STANDARD FUNCTIONS
(When completed normally)
Data
Head holding register number
(The value same as in the
request message is stored.)
(H)
(L)
Write points
(The value same as in the request
message is stored.)
(H)
5
(L)
Figure 4.86 Write multiple registers (Normal response message)
Data
Function
code
(90H)
Exception
code *2
6
Figure 4.87 Write multiple registers (Exception message)
* 2 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Function code
FUNCTION
(When completed with an error)
7
Section 11.4
PARAMETER SETTING
(H)
Write points
n *1
(0001H to 007BH)
SYSTEM
CONFIGURATION
Data
8
UTILITY PACKAGE
(GX Configurator-MB)
Function
code
(10H)
Slave)
4.15 Write Multiple Registers (FC: 16)
4 - 52
4
MODBUS(R) STANDARD FUNCTIONS
4.16 Report Slave ID (FC: 17)
Acquires the information of the slave (QJ71MB91) mounted station into the master.
(1) Request message format (Master
Slave)
Function code
Function
code
(11H)
Figure 4.88 Report slave ID (Request message)
(2) Response message format (Slave
Master)
(When completed normally)
Function code
Function
code
(11H)
Data
Number of
bytes
(02H)
PLC CPU type
See table below.
PLC CPU
STOP/RUN
state
00H: STOP, PAUSE, or in
initial processing
FFH: RUN, STEP-RUN
Figure 4.89 Report slave ID (Normal response message)
The slave (QJ71MB91) will return any of the following PLC CPU type data.
Table4.8 PLC CPU type data returned to Master
Module type
Q00JCPU
50H
Q00CPU
51H
Q01CPU
52H
Q02CPU
PLC CPU
PLC CPU type data returned to Master
41H
Q02HCPU
Q06HCPU
42H
Q12HCPU
43H
Q25HCPU
44H
Q12PHCPU
49H
Q25PHCPU
4AH
QJ72LP25-25
MELSECNET/H remote
QJ72LP25G
I/O station
QJ72LP25GE
QJ72BR15
4 - 53
4.16 Report Slave ID (FC: 17)
70H
71H
MODBUS(R) STANDARD FUNCTIONS
1
(When completed with an error)
OVERVIEW
Function
code
(91H)
Data
Exception
code*1
2
Figure 4.90 Report slave ID (Exception message)
* 1 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
SYSTEM
CONFIGURATION
Function code
SPECIFICATIONS
3
MODBUS(R)
STANDARD FUNCTIONS
4
FUNCTION
5
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
4
4.16 Report Slave ID (FC: 17)
4 - 54
4
MODBUS(R) STANDARD FUNCTIONS
4.17 Read File Record (FC: 20) (SC: 06)
Reads multiple extended file register values.
(1) Request message format (Master
Data
Function code
Sub-request
Function
code
(14H)
Slave)
Number of
bytes
mx7
Reference
number
(06H)
File number
(0000H to FFFFH) *1
Read head device number
(0000H to 270FH)
(H)
(L)
(H)
1
Read points
n1
(0001H to 007CH)
(L)
(L)
(H)
(Number of bytes m x 7)
Data
Sub-request m
Reference
number
(06H)
File number
(0000H to FFFFH) *1
Read head device number
(0000H to 270FH)
(L)
(H)
(L)
(H)
Read points
nm
(0001H to 007CH)
(H)
(L)
(Number of bytes m x 7)
Figure 4.91 Read file record (Request message)
* 1 The maximum file number available for the QJ71MB91 slave function is dependant on the file
register size of the mounted PLC CPU.(
Section 7.3.2)
(a) Number of sub-requests, m
Specify the number of sub-requests, m, so that the protocol data unit size of the
request message will not exceed 253 bytes.*2
2+m
7
253*2
If the above condition is not satisfied, the request message is discarded.
* 2 When the frame mode is ASCII mode, it is 506 bytes.
(b) Read points of each sub-request
Specify the total points N (n1+...+nm) so that the protocol data unit size of the
response message will not exceed 253 bytes.*3
2+m
2+N
2
253*3
If the above condition is not satisfied, the slave returns an exception response.
* 3 When the frame mode is ASCII mode, it is 506 bytes.
4 - 55
4.17 Read File Record (FC: 20) (SC: 06)
4
MODBUS(R) STANDARD FUNCTIONS
1
(2) Response message format (Slave
Master)
OVERVIEW
(When completed normally)
Data
Function code
2
Sub-request 1
Device
data
1
Device
data
n1
(H)
(L)
(H)
SYSTEM
CONFIGURATION
Reference
number
(06H)
Number of
Read bytes
response data (n1 x 2 + 1)
bytes
(m x 2 + N x 2)
(L)
(Number of read bytes n1 x 2 + 1)
3
SPECIFICATIONS
(Number of response data bytes m x 2 + N x 2)
Data
Sub-request m
Reference
number
(06H)
(H)
4
Device
data
nm
Device
data
1
(L)
(H)
MODBUS(R)
STANDARD FUNCTIONS
Number of
read bytes
(nm x 2 + 1)
(L)
(Number of read bytes nm x 2 + 1)
(Number of response data bytes m x 2 + N x 2)
5
Figure 4.92 Read file record (Normal response message)
"N" in the above diagram represents the total of the device data (n1 +...+ nm).
Function
code
(94H)
Data
6
Exception
code*1
Figure 4.93 Read file record (Exception message)
* 1 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
7
PARAMETER SETTING
Section 11.4
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Function code
FUNCTION
(When completed with an error)
8
UTILITY PACKAGE
(GX Configurator-MB)
Function
code
(14H)
4.17 Read File Record (FC: 20) (SC: 06)
4 - 56
4
MODBUS(R) STANDARD FUNCTIONS
4.18 Write File Record (FC: 21) (SC: 06)
Writes multiple extension file register values.
(1) Request message format (Master
Function
code
Slave)
Data
Sub-request 1
Function
code
(15H)
Number of
bytes
mx7
Reference
number
(06H)
File number
(0000H to FFFFH)
*1
(H)
Write head
device number
(0000H to 270FH)
(H)
(L)
Write points
n1
(0001H to 007AH)
(L)
(L)
(H)
. . .
Device
data
1
Device
data
n1
(H)
(L)
(H)
(L)
(Number of bytes m x 7)
Data
Sub-request m
File number
(0000H to FFFFH)
*1
Reference
number
(06H)
(H)
Write head
device number
(0000H to 270FH)
(L)
(H)
Write points
nm
(0001H to 007AH)
(L)
(H)
. . .
Device
data
1
(L)
(H)
(L)
Device
data
nm
(H)
(L)
(Number of bytes m x 7)
Figure 4.94 Write file record (Request message)
*1
The maximum file number available for the QJ71MB91 slave function is dependant on the file
register size of the mounted PLC CPU. (
Section 7.3.2)
(a) Write points of each sub-request
Specify the total points N (n1+...+nm) so that the protocol data unit size of the
response message will not exceed 253 bytes.*2
2+m
7+N
2
253*2
If the above condition is not satisfied, the request message is discarded.
* 2 When the frame mode is ASCII mode, it is 506 bytes.
4 - 57
4.18 Write File Record (FC: 21) (SC: 06)
MODBUS(R) STANDARD FUNCTIONS
1
Master)
(When completed normally)
The slave returns the request message received from the master without change.
2
(When completed with an error)
SYSTEM
CONFIGURATION
Exception
code*1
3
Figure 4.95 Write file record (Exception message)
* 1 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
SPECIFICATIONS
Function
code
(95H)
Data
4
POINT
5
FUNCTION
Even if the slave (QJ71MB91) receives this function with the PLC CPU file
register (ZR) set as read only (for example, the storage location of the file register
[ZR] is a Flash card), the slave responds normally.
In this case, however, the Write file record is not performed.
When performing the Write file record, previously confirm whether the PLC CPU
file register (ZR) is writable.
MODBUS(R)
STANDARD FUNCTIONS
Function
code
OVERVIEW
(2) Response message format (Slave
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
4
4.18 Write File Record (FC: 21) (SC: 06)
4 - 58
4
MODBUS(R) STANDARD FUNCTIONS
4.19 Mask Write Register (FC: 22)
Masks the values stored in a single holding register with AND or OR and writes the value.
The masked values written to the holding register are as shown below.
(Target register current value
AND mask value)
(OR mask value
AND mask value) = Write value
When the OR mask value is 0000H, only the AND processing of the AND mask value is
performed.
When the AND mask value is 0000H, the OR mask value is the write value.
(1) Request Message Format (Master
Slave)
Function
code
Function
code
(16H)
Data
Target holding register number
(0000H to FFFFH)
(H)
(L)
AND mask value
(0000H to FFFFH)
OR mask value
(0000H to FFFFH)
(H)
(H)
(L)
(L)
Figure 4.96 Mask write register (Request message)
(2) Response message format (Slave
Master)
(When completed normally)
The slave returns the request message received from the master without change.
(When completed with an error)
Function
code
Function
code
(96H)
Data
Exception
code*1
Figure 4.97 Mask write register (Normal response message)
* 1 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
POINT
This function code is used to read the value stored in a specified holding register
from the slave, process the value with AND/OR mask in the master, and then write
the masked value to the holding register of the slave.
Therefore, if the holding register value is changed during the AND/OR operation,
the changed value is overwritten.
4 - 59
4.19 Mask Write Register (FC: 22)
4
MODBUS(R) STANDARD FUNCTIONS
1
OVERVIEW
4.20 Read/Write Multiple Registers (FC: 23)
Reads from or writes to multiple holding registers.
Writing is executed first and reading is then executed.
Function
code
Data
Read head holding
register number
(0000H to FFFFH)
(L)
(H)
(L)
Write head holding
register number
(0000H to FFFFH)
(H)
(L)
Write points
m *1
(0001H to 0079H)
(H)
Number of
bytes
m x 2 *1
(0000H
to 00F2H)
Write
device data
1
(H)
(L)
. . .
Write
device data
m
(H)
(L)
(L)
3
SPECIFICATIONS
(Number of bytes m x 2)
Figure 4.98 Read/Write multiple registers (Request message)
* 1 The number of the specified write points must be matched with the number of bytes.
(2) Response message format (Slave
Master)
4
Function code
Function
code
(17H)
MODBUS(R)
STANDARD FUNCTIONS
(When completed normally)
Data
Number of
bytes
nx2
Read
device data
1
(H)
Read
device data
n
. . .
(L)
(H)
5
(L)
FUNCTION
(Number of bytes n x 2)
Figure 4.99 Read/Write multiple registers (Normal response message)
(When completed with an error)
Function code
(97H)
6
Data
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Function code
Exception
code *2
Figure 4.100 Read/Write multiple registers (Exception message)
* 2 Exception and error codes are stored in the buffer memory in the case of error completion.
Refer to the following for storage location, confirmation methods, and detailed contents.
Section 11.4
7
PARAMETER SETTING
(H)
Read points
n
(0001H to 007DH)
8
UTILITY PACKAGE
(GX Configurator-MB)
Function
code
(17H)
2
Slave)
SYSTEM
CONFIGURATION
(1) Request message format (Master
4.20 Read/Write Multiple Registers (FC: 23)
4 - 60
5
FUNCTION
CHAPTER5 FUNCTION
This chapter explains the functions of the QJ71MB91.
5.1 Function List
The function list of the QJ71MB91 is shown below.
Table5.1 Function list
Function
Description
Automatic communication
Reference
Automatically issues device read/write request messages from the
master (QJ71MB91) to a MODBUS
compatible slave device.
Allows reading/writing of MODBUS
devices at any timing with a
Section 5.2.1
Master function
Dedicated instruction *1
Automatic response function
*2
sequence program.
CHAPTER 10
Automatically performs the processing corresponding to the
function code in the request message received from the master,
Section 5.3.1
and automatically sends a response message.
Automatically converts access from the slave (QJ71MB91) to a
MODBUS
device
assignment function *3
Slave function
MODBUS
device into access to a QCPU device.
Users can assign any access destination.
This allows direct access from the MODBUS
Section 5.3.2
compatible master
device to the PLC CPU device memory.
This function allows the master connected to QJ71MB91’s CH1
(RS-232) communicate with several slave stations connected to
QJ71MB91’s CH2 (RS-422/485).
Link operation function
If the link operation function is used, a RS-232 interface (1-to-1
communication) MODBUS
several MODBUS
Section 5.3.3
master device can communicate with
slave devices.
* 1 The dedicated instructions are unavailable for the QJ71MB91 mounted on a MELSECNET/H
remote I/O station.
* 2 When the QJ71MB91 is mounted on a MELSECNET/H remote I/O station, there are restrictions on
the function codes supported by the automatic response function.(
Section 4.1 (3))
* 3 When the QJ71MB91 is mounted on a MELSECNET/H remote I/O station, there are restrictions on
the assignment range of the MODBUS
device assignment function.(
Section 7.3.1 (2))
(Continued on next page)
5-1
5.1 Function List
5
FUNCTION
1
QJ71MB91 status check function
Hardware test
Self-loopback test
Description
Reference
Checks the operations of the QJ71MB91 itself and the send/
receive functions.
Tests the RAM and ROM of the QJ71MB91.
Section 6.4.1
This test checks the send/receive function of the QJ71MB91 and
communications with the PLC CPU.
Section 6.4.2
By using the utility package (GX Configurator-MB), parameters
such as automatic communication parameters or
MODBUS
device assignment parameters can be set on-screen,
CHAPTER 8
and status monitoring is available.
3
SPECIFICATIONS
This makes the parameter setting and status monitoring easier.
MODBUS(R) STANDARD
FUNCTIONS
4
FUNCTION
5
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
Various settings using utility package
2
SYSTEM
CONFIGURATION
Function
OVERVIEW
Table5.1 Function list (Continued)
5.1 Function List
5-2
5
FUNCTION
5.2 Master Function
This section explains the functions of the QJ71MB91 acting as a MODBUS
master.
5.2.1 Automatic communication function
The automatic communication function is a function by which device read/write request
messages are automatically issued from the QJ71MB91 to the MODBUS compatible
slave devices.
R
MODBUS slave device
(Third party remote I/O,
etc)
RS-485
QJ71MB91
RUN
NEU.
SD
CH1
RD
ERR.
NEU.
SD
CH2
RD
Holding register
CH1
RS-232
SDA
1
SG
SDB
2
3
(FG)
RDA
4
5
(FG)
RDB
CH2
RS-422
/485
6
7
R
MODBUS slave device
(Third party sensor, etc)
QJ71MB91 (Master function)
PLC CPU
Device memory
Buffer memory
Read
Read
Auto Refresh
Holding register
Read
Write
R
MODBUS slave device
(Third party PLC)
Holding register
Automatically issues the
MODBUS R device read/write
request message to Slave.
Figure 5.1 Communication using the automatic communication function
5-3
5.2 Master Function
5.2.1 Automatic communication function
5
FUNCTION
1
(
Section 7.2)
Using the preset automatic communication parameters, communication processing is
performed automatically.
Refer to (2) and subsequent sections to set the automatic communication parameters.
(2) Automatic communication operation flowchart
(a) The Request interval timer
times out, and then restarts.
(b) Request message is issued
to the station.
4
(c) The Response monitoring
timer/ Broadcast delay starts.
MODBUS(R) STANDARD
FUNCTIONS
Station No.0 (broadcast)
3
SPECIFICATIONS
Using the preset automatic communication parameters, the automatic communication
function operates as shown below based on the request interval timer and response
monitoring timer/broadcast delay settings.
Set the automatic communication parameters referring to the following flowchart.
2
SYSTEM
CONFIGURATION
Set the automatic communication parameters to use this function.
OVERVIEW
(1) To use the automatic communication function
Transmitting
request message
5
Station No.1 to 247
Normal
Error
6
(f) The Response monitoring
timer times out
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
(e) Receiving response
message from the slave
(g) The Response monitoring
timer is terminated
7
Turns ON the corresponding bit in Automatic
communication operation status
(1: Automatic communication
error occurred)
PARAMETER SETTING
Turns OFF the corresponding bit in Automatic
communication operation status
(0: Being normally executed)
Wait for Request interval timer timeout
8
Figure 5.2 Automatic communication operation flowchart
Symbols (a) to (g) in the illustration correspond to sections (a) to (g) on subsequent pages.
5.2 Master Function
5.2.1 Automatic communication function
5-4
UTILITY PACKAGE
(GX Configurator-MB)
(d) The Broadcast delay
times out
FUNCTION
Relevant
station status
5
FUNCTION
(a) The Request interval timer times out, and then restarts
The Request interval timer represents the interval between any successive
request message transmissions in the automatic communication function.
(
Section 7.2.1 (3))
Request interval timer times
out, and then restarts
Request interval timer
Master
(QJ71MB91)
Receiving
response
message
Request
message
Request
message
processing
Slave
Receiving
response
message
Request
message
Request
message
processing
Response
message
Response
message
Figure 5.3 Request interval timer operation
(b) Request message is issued to the station
Request messages are issued at the timing shown in the above (a).
(c) The Response monitoring timer/Broadcast delay starts
The Response monitoring timer is used to monitor the time taken between a
response message transmission from QJ71MB91 and reception of a response
message from a slave.
The Broadcast delay monitors the time interval between transmissions when
request messages are broadcast.
The Response monitoring timer/Broadcast delay starts when a request message
is sent.(
Section 7.2.1 (4))
Start Response monitoring
timer/Broadcast delay
Request interval timer
Response monitoring timer
Master
(QJ71MB91)
Slave 1
Receiving
response
message
*1
Request
message
Request
message
processing
Response
Message
Request interval timer
Broadcast delay
*2
Request
message
Request
message
Request
message
processing
Slave 2
Request
message
processing
Slave 3
Request
message
processing
*1 When request message is addressed to station No.1 to 247
*2 When request message is addressed to station No.0 (Broadcast)
Figure 5.4 Response monitoring timer/Broadcast delay operation
5-5
5.2 Master Function
5.2.1 Automatic communication function
FUNCTION
(d) The Broadcast delay times out
When the Broadcast delay times out after transmission of a request message, it
means normal completion, and the corresponding bit in the buffer memory's
automatic communication operating status storage area turns OFF. (address:
0C20H to 0C21H/0C22H to 0C23H)
Broadcast delay
Request
message
Request
message
Slave 1
Request
message
processing
Request
message
processing
Slave 2
Request
message
processing
Request
message
processing
Slave 3
Request
message
processing
Request
message
processing
3
SPECIFICATIONS
Master
(QJ71MB91)
2
SYSTEM
CONFIGURATION
Broadcast delay times out
OVERVIEW
1
4
MODBUS(R) STANDARD
FUNCTIONS
Figure 5.5 Timeout of Broadcast delay
(e) Receiving response message from slave
When slave processing is complete, a response message is received.
Receiving response message
from the slave
5
Response
Message
Request
message
processing
FUNCTION
Request
message
processing
Receiving
response
message
Request
message
Response
Message
Figure 5.6 Reception of response message
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Slave
Receiving
response
message
Request
message
7
PARAMETER SETTING
Master
(QJ71MB91)
8
UTILITY PACKAGE
(GX Configurator-MB)
5
5.2 Master Function
5.2.1 Automatic communication function
5-6
5
FUNCTION
(f) The Response monitoring timer times out
If an error occurs at the relevant station (e.g. PLC CPU), the slave may not be
able to send a response message.
In such a case, the Response monitoring timer times out.
Response monitoring timer
times out
Response monitoring timer
Master
(QJ71MB91)
Slave 1
Receiving
response
message
Request
message
Request
message
processing
Response
Message
Response monitoring timer
Request
message
Because of the error, request message
cannot be processed.
Error occurred at
the station
Figure 5.7 Response monitoring timer operation
If the Response monitoring timer times out, the correstponding bit in the buffer
memory’s automatic communication operating status storage area turns ON.
(address: 0C20H to 0C21H/0C22H to 0C23H)
(g) The Response monitoring timer is terminated
When the master (QJ71MB91) receives a response message, the Response
monitoring timer is terminated.
5-7
5.2 Master Function
5.2.1 Automatic communication function
5
FUNCTION
1
Example: If Automatic communication parameters 1 to 3 are set
Automatic communications are executed in the order: 1 2 3
1
2
3
Request interval timer
Response
message
Request
message
Request interval timer
Response
monitoring timer
Request
message
4
Response
message
MODBUS(R) STANDARD
FUNCTIONS
Automatic
communication
parameter
2
Request interval timer
Broadcast delay
Automatic
communication
parameter
3
Request
message
(Broadcast)
5
Figure 5.8 Automatic communication execution sequence
POINT
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
If no automatic communication parameter is set, no automatic communication is
executed.(
Section 7.2.1 (1))
For example, if Automatic communication parameter 2 has no setting in the Figure
5.8, automatic communication will be executed in the order: 1 3 1 3
FUNCTION
Request
message
SPECIFICATIONS
Response
monitoring timer
Automatic
communication
parameter
1
2
SYSTEM
CONFIGURATION
Automatic communication is executed in order from Automatic communication
parameter 1.
After the final automatic communication parameter is executed, the automatic
communication parameters are executed from automatic communication parameter 1
again.
OVERVIEW
(3) Execution sequence in the automatic communications
PARAMETER SETTING
7
UTILITY PACKAGE
(GX Configurator-MB)
8
5.2 Master Function
5.2.1 Automatic communication function
5-8
5
FUNCTION
(4) Storage location for the data read/written by the automatic
communication
Data to be read or written by the automatic communication function are stored in the
following buffer memory.
Table5.2 Data storage location (buffer memory)
Name
Description
Buffer memory address
CH1: 1000H to 1FFFH
Automatic communication function
Area used for storing data
buffer input area
read from the slave
(4096 to 8191)
CH2: 2000H to 2FFFH
(8192 to 12287)
CH1: 3000H to 3FFFH
Automatic communication function
Area used for storing data
buffer output area
written to the slave
(12288 to 16383)
CH2: 4000H to 4FFFH
(16384 to 20479)
POINT
1.
2.
5-9
Read/write data in the above areas are stored in RTU mode (binary) even if
the frame mode is ASCII mode.
Read/write data consistency is secured in units of one word (16 bits).
5.2 Master Function
5.2.1 Automatic communication function
FUNCTION
(a) Transfer direction of the automatic communication function buffer input/output
area data
The data to be stored into the buffer memory by the automatic communication
function are transferred in the following directions.
R
MODBUS
slave device
QJ71MB91 (Master function)
2
SYSTEM
CONFIGURATION
Buffer memory
OVERVIEW
1
Automatic communication
function buffer input area
CH1: 1000H to 1FFFH
CH2: 2000H to 2FFFH
QJ71MB91
side receive
data write
direction
Response message (data read)
PLC CPU side
write direction
Automatic communication
function buffer output area
CH1: 3000H to 3FFFH
CH2: 4000H to 4FFFH
QJ71MB91
side send
data read
direction
Request message (data write)
3
SPECIFICATIONS
PLC CPU side
read direction
1) Transfer direction of the automatic communication function buffer input area
data
When receiving a response message from a slave, the QJ71MB91 writes data
to the automatic communication function buffer input area in descending order
of the addresses in 1 word (16 bits) unit.
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
2) Transfer direction of the automatic communication function buffer output area
data
When sending a request message to a slave, the QJ71MB91 creates it by
reading data from the automatic communication function buffer output area in
descending order of the addresses in units of one word (16 bits).
5
FUNCTION
RS-232, RS-422 or 485
Figure 5.9 Transfer direction of the automatic communication function buffer input/output area data
MODBUS(R) STANDARD
FUNCTIONS
4
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
5
5.2 Master Function
5.2.1 Automatic communication function
5 - 10
5
FUNCTION
(b) Data transfer timing in the automatic communication buffer area
Data are transferred for each data exchange with the target station.
(c) Data transfer between the automatic communication function buffer areas and
PLC CPU device memory
Data can be transferred between the automatic communication buffer area and
PLC CPU device memory by either of the following methods.
Table5.3 Data transfer between automatic communication function buffer areas and PLC CPU
device memory
Transfer method
Transfer by auto refresh setting
Transfer using the sequence program
Description
Make the auto refresh setting on GX ConfiguratorMB.(
Section 8.5)
Specify the intelligent function module device (Un\G
sequence program to make transfer.*1
* 1 Refer to the following manual for details on the intelligent function module devices.
QCPU User’s Manual (Function Explanation, Program Fundamentals)
5 - 11
5.2 Master Function
5.2.1 Automatic communication function
) in a
FUNCTION
1
2) How to check the activation of the automatic communication function
When the QJ71MB91 starts communication with the slave device with the
automatic communication function, the SD and RD LEDs turn ON. (Only when
communicating)
3) Automatic communication start/stop test
On the "Automatic communication status" screen of GX Configurator-MB, the
start/stop test of the automatic communication function can be performed.
SYSTEM
CONFIGURATION
3
4
5
FUNCTION
Section 8.6.3)
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
7
PARAMETER SETTING
(
2
SPECIFICATIONS
1) Operation timing of the automatic communication function
The automatic communication function is activated by powering ON the PLC
from OFF or by resetting the PLC CPU (with the PLC CPU's RUN/STOP
switch set to RUN).
The automatic communication will not start if the PLC is powered ON from
OFF or if the PLC CPU is reset (with the PLC CPU's RUN/STOP switch set to
STOP).
If the QJ71MB91 is mounted on a MELSECNET/H remote I/O station, the
automatic communication function is activated when the remote I/O station
receives the information notifying the status change (from STOP to RUN) of
the remote master station's PLC CPU.
MODBUS(R) STANDARD
FUNCTIONS
(a) When the automatic communication parameters are set on GX Configurator-MB
When the automatic communication parameters are set on GX Configurator-MB,
no sequence program for start is required.
OVERVIEW
(5) Start and stop of the automatic communication function
8
UTILITY PACKAGE
(GX Configurator-MB)
5
5.2 Master Function
5.2.1 Automatic communication function
5 - 12
5
FUNCTION
(b) When the automatic communication parameters are set with sequence programs
If the automatic communication parameters are set with sequence programs, the
automatic communication function can be started or stopped at any timing.
1) Operation timing of the automatic communication function
To start or stop the automatic communication function from a sequence
program, turn on/off Automatic communication parameter setting request/
Automatic communication start request (Y4/YC) and Automatic
communication stop request (Y6/YE).
Automatic communication
parameter setting, normally
completed/Automatic
communication function start
Automatic
communication
stop
Automatic communication
parameter setting, normally
completed/automatic
communication function start
Automatic
communication
parameter creation
Parameter creation
ON
Module READY
X0
OFF
Automatic communication
parameter setting request/ Y4/YC OFF
Automatic communication
start request
Automatic communication
stop request
Y6/YE OFF
Automatic communication
parameter setting,
normally completed
X4/XC OFF
Automatic communication
parameter setting,
error completed
X5/XD OFF
Automatic communication
operation status
X6/XE OFF
ON
ON
ON
ON
ON
ON
Automatic
communication
function operating
Automatic
communication
function operating
Executed by QJ71MB91
Executed by sequence program
Figure 5.10 Automatic communication time chart
5 - 13
5.2 Master Function
5.2.1 Automatic communication function
FUNCTION
1
(d) Restarting the automatic communication function after issuing Automatic
communication stop request (Y6/YE)
Since Automatic function stop request (Y6/YE) stops the automatic
communication at the time of its execution, depending on the timing, the
automatic communication may be stopped during or immediately after
transmission of a request message.
For this reason, when restarting the automatic communication, allow a sufficient
time for the slave to process the request message that is received before the stop.
Failure to do so may cause an error due to collisions of the QJ71MB91 request
message and slave’s response message when automatic communication is
restarted.
(e) When the automatic communication parameters are set on GX Configurator-MB
When the automatic communication parameters are set on GX Configurator-MB,
the automatic communication function will be automatically started at the timing
shown in (5) (a) 1) of this section.
When the automatic communication function is active, and when the target slave
device is not in normal condition (disconnected, down, not ready for
communication, etc.), perform either of the following:
• After the target slave device is recovered, set automatic communication
parameters on the sequence program and start the automatic communication
function.
• Ignore the error (Exception message reception (error code: 7360H ) or
Response monitoring timer timeout (error code: 7378H ), etc.)
5.2 Master Function
5.2.1 Automatic communication function
5 - 14
SYSTEM
CONFIGURATION
SPECIFICATIONS
4
MODBUS(R) STANDARD
FUNCTIONS
(c) When Automatic communication stop request (Y6/YE) is executed while
automatic communication is stopped
An error (error code: 7370H) will occur if Automatic communication stop request
(Y6/YE) is executed while the automatic communication function is stopped
(Automatic communication operation status (X6/XE) is OFF).
5
FUNCTION
Even if no response is sent from the communication target slave, the automatic
communication function does not stop until Automatic communication stop
request (Y6/YE) turns on.
3
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
(b) Automatic communication function stop by Automatic communication stop request
(Y6/YE)
When using Automatic communication stop request (Y6/YE) to stop the automatic
communication function, satisfy all of the following conditions.
• Condition 1: Module READY (X0) is ON.
• Condition 2: Automatic communication operation status (X6/XE) is ON.
2
7
PARAMETER SETTING
(a) When turning ON the Automatic communication parameter setting request/
Automatic communication start request (Y4/YC)
Before turning ON the Automatic communication parameter setting request/
Automatic communication start request (Y4/YC), turn ON the Module READY
(X0).
OVERVIEW
(6) Precautions for starting/stopping the automatic communication function
8
UTILITY PACKAGE
(GX Configurator-MB)
5
5
FUNCTION
(7) Automatic communication operation status
(a) Checking the automatic communication operation status
Use Automatic communication error status (X6/XE) to confirm the automatic
communication operation status.
(b) Confirming the error occurred
When an error occurs in the automatic communication, Automatic communication
error status (X7/XF) turns ON.
Also, any erroneous part of the parameters and error details can be identified by
the following:
1) Acquisition of the automatic communication parameter number for the error
Check the operation status storage area (0C20H to 0C21H/0C22H to 0C23H) in
the buffer memory to identify the error.
(
Section 11.4.1 (5))
2) Error code check
In the automatic communication error code storage area (0C28H to 0C47H/
0C48H to 0C67H) of the buffer memory, check the error code stored in the area
corresponding to the automatic communication parameter number identified in
the above 1).
(
Section 11.4.1 (8), Section 11.4.3)
POINT
On the "Automatic communication status" screen of GX Configurator-MB, the
operation status and error code for each automatic communication parameter can
be confirmed.(
Section 8.6.3)
(8) Checking presence of the automatic communication function settings
If the automatic communication function does not operate although no error has
occurred regarding (7), check the presence of the settings in the automatic
communication setting status storage area (address: 0CA8H to 0CA9H/0CAAH to
Section 11.4.1 (7))
0CABH) in the buffer memory. (
Check it with Automatic communication operation status (X6/XE) ON.
If there are no settings, make the settings again.
5 - 15
5.2 Master Function
5.2.1 Automatic communication function
FUNCTION
1
R
MODBUS slave device
Holding register
]
Request message (Read request for holding register 400500)
Device memory
Response message (Holding register 400500 = 1234H)
[Z.MBRW
400500
1234H
1234H
3
RS-232, RS-422 or RS-485
Figure 5.11 Communication by dedicated instruction
Dedicated instruction list
The following table indicates a list of dedicated instructions supported by the
QJ71MB91.
Table5.4 Dedicated instruction list
Dedicated
Description
instruction
device read/write request message to a slave.
With this instruction, a request message can be sent to a slave in any
given Protocol Data Unit format.
Section 10.2
Section 10.3
4
FUNCTION
5
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
MBREQ
Issues a MODBUS
Reference
7
PARAMETER SETTING
MBRW
2
SPECIFICATIONS
Command
MODBUS(R) STANDARD
FUNCTIONS
QJ71MB91
(Master function)
PLC CPU
SYSTEM
CONFIGURATION
The dedicated instructions allow reading/writing of MODBUS devices at any timing with a
sequence program.
OVERVIEW
5.2.2 Dedicated instruction
8
UTILITY PACKAGE
(GX Configurator-MB)
5
5.2 Master Function
5.2.2 Dedicated instruction
5 - 16
5
FUNCTION
5.3 Slave Function
This section explains the functions of the QJ71MB91 acting as a MODBUS
slave.
5.3.1 Automatic response function
By the automatic response function, the QJ71MB91 (slave function) automatically
executes the processing requested by the function code (
Section 4.1) of a request
message from the master, and returns a response message to the master.
For device read/write or exception status read, use the MODBUS
function. (
Section 5.3.2)
QJ71MB91
(Slave function)
PLC CPU
1)
No sequence
program
required
2)
Receiving
request message
MODBUS R
master device
Request message (function code)
Function
code
identification
3)
Requested
processing execution
Device memory
4)
Transmitting
response message
Response message
RS-232, RS-422 or RS-485
Figure 5.12 Automatic response function
5 - 17
device assignment
5.3 Slave Function
5.3.1 Automatic response function
5
FUNCTION
1
(QJ71MB91) MODBUS
device into access to a PLC CPU device.
This allows direct access from the MODBUS compatible master device to the PLC CPU
device memory.
Supporting the MODBUS
devices of large capacity, the QJ71MB91 allows all device
memories of the PLC CPU to be assigned.(
(1) MODBUS
Section 7.3.1)
device assignment parameter setting
Set the MODBUS
device assignment parameters to the slave (QJ71MB91).
The following settings are possible for the MODBUS
parameters.
3
device assignment
(a) Correlating the MODBUS device to the PLC CPU device memory.
When a message requesting an action such as write coil is received from the
master, the access to the MODBUS
device is automatically converted into
access to the PLC CPU device.(
Section 7.3.1 to Section 7.3.3)
MODBUS
Master
device
QJ71MB91 (Slave function)
No sequence
program required
4
MODBUS(R) STANDARD
FUNCTIONS
PLC CPU
R
R
MODBUS device assignment parameter
400499
400500
D301
400501
5
Request message (Write 1234H to holding
register 400500)
FUNCTION
D299
D300
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
1234H
MODBUS R device
RS-232, RS-422 or RS-485
Figure 5.13 MODBUS
device and PLC CPU device
7
PARAMETER SETTING
D300
Device memory
8
UTILITY PACKAGE
(GX Configurator-MB)
Device
2
SYSTEM
CONFIGURATION
device assignment function automatically converts access to a slave
SPECIFICATIONS
The MODBUS
OVERVIEW
5.3.2 MODBUS(R) device assignment function
5.3 Slave Function
5.3.2 MODBUS(R) device assignment function
5 - 18
5
FUNCTION
(b) Specifying the error status read device
Users can specify the data to be read out as an exception status when the
QJ71MB91 (slave) receives Read Exception Status (FC:07) from the
master.(
PLC CPU
No sequence
program required
Device
M100
to
M107
01H
Section 7.3.4)
MODBUS
Master
device
QJ71MB91 (Slave function)
R
Error status read device specification
Device memory
M100 to M107
Exception
status
Request message
(Sends Read Exception Status (FC:07))
Receives response message (exception
status 01H)
RS-232, RS-422 or RS-485
Figure 5.14 Error status read device and PLC CPU device
(c) Specifying access target when mounted to MELSECNET/H remote I/O station
For the case where the QJ71MB91 is mounted to a MELSECNET/H remote I/O
station, the access target can be specified.(
Section 7.3.5)
The access target can be selected from the MELSECNET/H remote master
station and the MELSECNET/H remote I/O station.
5 - 19
5.3 Slave Function
5.3.2 MODBUS(R) device assignment function
FUNCTION
1
Request
message
Slave
(QJ71MB91)
Response
message (error
completed)
Because of the error, request
message cannot be processed.
Error occurred at
the station
CPU response
monitoring timer
times out
Response
message (error
completed)
3
If CPU response monitoring
timer times out, response
message (error completion) is
transmitted
SPECIFICATIONS
Master
Figure 5.15 CPU response monitoring timer operation
(2) Setting the MODBUS
Configurator-MB).(
device assignment parameters
4
device assignment parameters by the utility package (GX
MODBUS(R) STANDARD
FUNCTIONS
Set the MODBUS
2
SYSTEM
CONFIGURATION
access target PLC CPU.(
Section 7.3.6)
In the case of an error at the access target PLC CPU and if any response
message cannot be sent, another response message (error complete) can be
sent after a given length of time has elapsed.
This will prevent the master from waiting for a response message that will not be
received.
OVERVIEW
(d) Specifying the CPU response monitoring timer
Specify the timer value so that the QJ71MB91 will monitor the processing of the
Section 8.4.2)
Setting from a sequence program is also available.(
Section 9.1.2)
FUNCTION
5
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
5
5.3 Slave Function
5.3.2 MODBUS(R) device assignment function
5 - 20
5
FUNCTION
5.3.3 Link operation function
(1) The link operation function
The link operation function enables the master connected to CH1 (RS-232) to
communicate with multiple slaves connected to QJ71MB91's CH2 (RS-422/485).
If the link operation function is used, a RS-232 interface (1-to-1 communication)
MODBUS master device can communicate with several MODBUS slave devices.
R
MODBUS master device
Request
message
Response
message
QJ71MB91 (Slave function)
QJ71MB91
CH1
RUN
NEU.
SD
RD
ERR.
NEU.
SD
RD
CH2
CH1
RS-232
SDA
1
SG
SDB
CH1(RS-232)
2
3
(FG)
RDA
4
5
(FG)
RDB
6
CH2
RS-422
/485
7
CH2 (RS-422 or RS-485)
R
R
MODBUS
MODBUS
slave device
slave device
Figure 5.16 Communication using the link operation function
(2) Setting the link operation function
The link operation function can be set with the intelligent function module switch
(
Section 6.6).
(3) Message flow during link operation
A request message received on CH1 is sent to a slave from CH2.
A response message received from CH2 is sent to the master from CH2.
If a request message addressed to the QJ71MB91 is received, the QJ71MB91 will act
as a slave. (The link operation is not performed.)
Operates as a slave
when receiving request
message addressed to
QJ71MB91
MODBUS R
master device
CH1:
RS-232
PLC CPU
CH2:
RS-422
/485
Request
message
Response
message
Messages are relayed
from CH1 to CH2
or from CH2 to CH1.
R
MODBUS
slave device
QJ71MB91
(Slave function)
Figure 5.17 Message flow during link operation
5 - 21
5.3 Slave Function
5.3.3 Link operation function
R
MODBUS
slave device
FUNCTION
1
Connect the MODBUS
master device to CH1 (RS-232) of the QJ71MB91.
While using the link operation function, the MODBUS
connected to CH2 (RS-422/485).
R
master device cannot be
(b) Intelligent function module settings
The intelligent function module switch settings for channels 1 and 2 must be
identical.
3
SPECIFICATIONS
If not, a switch error will be generated. (Except for MODBUS device assignment
parameter starting methods in the transmission speed setting/transmission setting
(switch 2, 4).)
2
SYSTEM
CONFIGURATION
(a) System configuration
OVERVIEW
(4) Precautions for the link operation function
MODBUS(R) STANDARD
FUNCTIONS
4
FUNCTION
5
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
5
5.3 Slave Function
5.3.3 Link operation function
5 - 22
6
PRE-OPERATIONAL PROCEDURES AND SETTINGS
CHAPTER6 PRE-OPERATIONAL PROCEDURES AND
SETTINGS
This chapter explains the procedures and setting method for operating the QJ71MB91 in a
system.
POINT
1.
2.
For use of the QJ71MB91, read the safety precautions provided in the first
pages of this manual.
The QJ71MB91 implementation and installation environment are the same as
those of the PLC CPU.
Refer to the following manual regarding the QJ71MB91 implementation and
installation environment.
QCPU User’s Manual (Hardware Design, Maintenance and Inspection)
6.1 Handling Precautions
This section explains the precautions for handling the QJ71MB91.
1) Since the case of the QJ71MB91 is made of resin, do not drop or give it hard
impact.
2) Before handling modules, touch a grounded metal object to discharge the
static electricity from the body.
Failure to do so may cause failure or malfunctions of the module.
3) Tighten the terminal or fixing screws within the following tightening torque
range.
Table6.1 Tightening torque
Screw
Terminal screw for RS-422/485 terminal block (M3
screw)
Mounting screw for RS-422/485 terminal block
(M3.5 screw)
Tightening torque range
0.42 to 0.58 N
m
0.66 to 0.89 N
m
0.36 to 0.48 N
m
Module fixing screw (Normally not needed) (M3
screw) *1
* 1 The module can be easily fixed to the base unit with the hook at top of the module.
In the operating environment where high vibration and/or strong impact is observed, however, it is
recommended to fix the module with the module fixing screws.
6-1
6.1 Handling Precautions
PRE-OPERATIONAL PROCEDURES AND SETTINGS
1
OVERVIEW
6.2 Pre-Operational Procedures and Settings
A rough procedure for operation is shown below.
Procedure for operation
2
SYSTEM
CONFIGURATION
Confirm the devices to be used and specifications.
Mount the QJ71MB91 on the base unit.
3
Section 6.4.1
Perform the self-loopback test.
Section 6.4.2
Set the I/O assignment with GX Developer.
Section 6.6
Set the intelligent function module switches with GX
Developer.
Section 6.6
5
R
Connect the MODBUS master device/MODBUS slave device
to the QJ71MB91 with a cable.
Section 6.4
Confirm the function parameters to be used.
CHAPTER 7
FUNCTION
R
4
MODBUS(R) STANDARD
FUNCTIONS
Perform the hardware test.
SPECIFICATIONS
Connect GX Developer and PLC CPU via a cable.
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
(To next page)
Figure 6.1 Pre-operational procedures and settings
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
6
6.2 Pre-Operational Procedures and Settings
6-2
6
PRE-OPERATIONAL PROCEDURES AND SETTINGS
(From previous page)
Use utility software
to set parameters?
NO
YES
Set parameters with a
sequence program.
Set parameters with GX
Configurator-MB.
CHAPTER 8
When using the dedicated instructions,
create a sequence program for communication.
CHAPTER 9
CHAPTER 10
Write the parameters, etc. that are set for the PLC CPU,
reset the PLC CPU, and bring it into RUN status.*1
Operation
Figure 6.1 Pre-operational procedures and settings (Continued)
* 1 If parameters are set at the GX Configurator-MB, power OFF and then ON or reset the PLC CPU
with the CPU RUN/STOP switch set at RUN.
POINT
1.
When setting parameters, do not write any data to the "System area (use
2.
prohibited)" in the QJ71MB91 buffer memory.(
Section 3.5.1)
Writing data to the "System area (use prohibited)" may cause malfunction of
the PLC system.
When making any parameter registration request etc., do not output (turn ON)
3.
4.
6-3
any "Use prohibited" output signal.(
Section 3.4.1)
Doing so may cause malfunction of the PLC system.
Use GX Developer to make I/O assignment and intelligent function module
switch setting.
Perform QJ71MB91 automatic communication parameter (
Section 7.2)
settings at the GX Configurator-MB or the sequence program.
To update the parameter settings added/changed on GX Developer, write the
parameters to the PLC CPU, and then reset the PLC CPU.
6.2 Pre-Operational Procedures and Settings
PRE-OPERATIONAL PROCEDURES AND SETTINGS
1
OVERVIEW
6.3 Part Names
This section provides the names of the QJ71MB91 parts.
SYSTEM
CONFIGURATION
2
SPECIFICATIONS
3
MODBUS(R) STANDARD
FUNCTIONS
4
Figure 6.2 QJ71MB91 external diagram
Table6.2 Part names and descriptions
Name
CH1 side RS-232
RS-232 interface for serial communication with target devices
interface
(D-Sub 9P)
CH2 side RS-422/485
RS-422/485 interface for serial communication with target devices
interface
(Detachable terminal block)
This section (1))
5
FUNCTION
3)
Indicator LEDs (
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
2)
Indicator LED
7
PARAMETER SETTING
1)
Description
8
UTILITY PACKAGE
(GX Configurator-MB)
6
6.3 Part Names
6-4
6
PRE-OPERATIONAL PROCEDURES AND SETTINGS
(1) Display LED list
Figure 6.3 QJ71MB91 LEDs
Table6.3 Description of LEDs
Description
LED name
Indication
ON/Flashing
OFF
RUN
Operation status
Hardware normal
Watch dog timer error, hardware fault
ERR.
Error indication *1
Error occurred
Normal
Master function
NEU.
Request message not transmitted
slave
Neutral status
CH1/
Slave function
CH2
Waiting for request message from
master
Request message being processed
SD
Send status
Data being sent
Data not being sent
RD
Receive status
Data being received
Data not being received
* 1 For troubleshooting, refer to the following.
CHAPTER 11
6-5
Waiting for response message from
6.3 Part Names
PRE-OPERATIONAL PROCEDURES AND SETTINGS
1
OVERVIEW
6.4 Unit Tests
This section explains the unit tests performed before operating the QJ71MB91.
6.4.1 Hardware test
2
SYSTEM
CONFIGURATION
The hardware test is a test for checking the RAM and ROM of QJ71MB91.
(1) Hardware test procedure
Perform the hardware test according to the following procedure.
Start
3
Set it to the hardware test mode.
(switch 1, 3 = 000DH)
SPECIFICATIONS
STOP the PLC CPU. Disconnect the communication
cable connected to the target device.
Section 6.6
4
MODBUS(R) STANDARD
FUNCTIONS
Reset the PLC CPU.
Test execution
(approx. 2 seconds)
Normal/Error
5
NEU.LED and ERR.LED ON: Error completion
Monitor the buffer memory and check
This section (3))
the error. (
FUNCTION
NEU.LED ON:
Normal completion
End
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Figure 6.4 Hardware test procedure
(2) Hardware test contents
The QJ71MB91 performs the following tests once.
(a) ROM check
Reads ROM data and perform a sum check.
7
PARAMETER SETTING
(b) RAM check
Writes test data in RAM and read the written data to perform the check.
8
UTILITY PACKAGE
(GX Configurator-MB)
6
6.4 Unit Tests
6.4.1 Hardware test
6-6
6
PRE-OPERATIONAL PROCEDURES AND SETTINGS
(3) Confirmation of hardware test results
When the CH1 NEU.LED turns ON, the test is completed. (Approx. 2 seconds)
(a) When completed normally
The ERR.LED turns OFF at normal completion.
(b) When completed abnormally
The ERR.LED turns ON at abnormal completion.
If the test is completed abnormally, monitor the hardware test results storage area
(0FFEH) of the buffer memory to check the error details.
b15
to
Hardware test results
(0FFEH)
0
b4
b3
0/1
b2
b1 b0
0
0/1 0/1
1: ROM error
1: RAM error
1: Test completion
Figure 6.5 Hardware test results storage details
(4) Hardware test completion
After confirming normal completion/abnormal completion of test results, perform the
following operations.
(a) When completed normally
To start data communication with a target device after completing the test, perform
the following operation to start the data communication.
• Perform the intelligent function module switch settings at GX Developer.
(
Section 6.6)
• Power OFF the station and connect a communication cable to the target
device.
• Power ON the station.
(b) When completed abnormally
If a ROM/RAM error occurs, check the following and re-perform the test.
• The QJ71MB91, power supply module and PLC CPU are mounted correctly
on the base unit.
• The operating environment of the QJ71MB91 meets the general
specifications of the PLC CPU.(
QCPU User's Manual (Hardware
Design, Maintenance and Inspection))
• The power capacity is sufficient.
• The hardware of the PLC CPU and base unit is normal according to the
manual of each module.
If, after checking the above points and re-performing the test, the hardware test is
completed abnormally again, a QJ71MB91 hardware error may have occurred.
Please consult your local Mitsubishi service center or representative, explaining a
detailed description of the problem.
6-7
6.4 Unit Tests
6.4.1 Hardware test
PRE-OPERATIONAL PROCEDURES AND SETTINGS
1
OVERVIEW
6.4.2 Self-loopback test
The self-loopback test checks the send/receive function of the QJ71MB91 and
communications with the PLC CPU.
2
(1) Self-loopback test procedure
SYSTEM
CONFIGURATION
Start
STOP the PLC CPU. Disconnect the communication
cable connected to the target device.
3
Make the communication
speed/transmission settings. (Switch 2, 4)
Section 6.6
Set it to the self-loopback test mode.
(Switch 1, 3 = 000DH, 000EH combination)
Section 6.6
SPECIFICATIONS
Connect a cable for self-loopback test.*1
MODBUS(R) STANDARD
FUNCTIONS
4
Reset the PLC CPU.
Loopback test execution
(approx. 1 second per cycle)
Normal/Error
5
ERR.LED ON: Error completion
FUNCTION
Monitor the buffer memory and check the
error.
ERR.LED OFF:
Normal operation
6
End
Figure 6.6 Self-loopback test procedure
QJ71MB91
CH2 (RS-422/485)
RD
SD
SG
Output for cable
disconnection
detection
Input for cable
disconnection
detection
Pin No.
1
2
3
4
5
6
7
Signal name
SDA
SDB
RDA
RDB
SG
FG
FG
7
PARAMETER SETTING
QJ71MB91
CH1(RS-232)
Signal name
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
* 1 This is the cable wiring for self-loopback test.
8
8
9
Figure 6.7 Cable wirings for self-loopback test
6.4 Unit Tests
6.4.2 Self-loopback test
UTILITY PACKAGE
(GX Configurator-MB)
6
6-8
6
PRE-OPERATIONAL PROCEDURES AND SETTINGS
(2) Self-loopback test details
The QJ71MB91 performs the following test repeatedly. (Test for one cycle is
performed in approximately one second.)
(a) PLC CPU communication check (The CH1 NEU.LED flickers.)
Checks that communication with the PLC CPU is enabled.
(b) Each interface communication function check (The SD/RD LED of the tested
interface flickers.)
Performs data send and receive while changing data.*1
* 1 If the data bit length is set to 7 bits, the 8th bit will be ignored during sending and receiving in the
test.
(3) Self-loopback test results check
This test is performed repeatedly. If the ERR.LED is OFF, the test is being operated
normally.
If the ERR.LED turns ON, the test is completed with an error.
When the test is completed abnormally, monitor the self-loopback test results storage
area (0FFFH) of the buffer memory and check the error details.
b15
to
Self-loopback test results
(0FFFH)
0
b4
b3
b2
b1
b0
0/1 0/1
0
0/1
1: PLC CPU
Communication error
1: CH2 side
Communication error
1: CH1 side
Communication error
Figure 6.8 Self-loopback test results storage details
Table6.4 Error cause and corrective action
Buffer memory
Cause for corresponding bit ON
Address
Corrective action
Bit position
b0
An error has occurred at PLC CPU.
Remove the error cause in the PLC CPU.
The power capacity is not sufficient.
Review the power capacity.
The module is not mounted correctly.
Mount the module correctly.
0FFFH
An error has occurred at the base unit, extension
(4095)
cable, PLC CPU and QJ71MB91.
b2
CH2 communication error
b3
CH1 communication error
Check each module and remove the error cause.
• Connect the cable correctly.
• Mount the module correctly.
Connect the cable correctly.
Review the self-loopback test cable wiring
6-9
6.4 Unit Tests
6.4.2 Self-loopback test
connections.
PRE-OPERATIONAL PROCEDURES AND SETTINGS
1
(b) When completed abnormally
If an error occurs, remove the error cause by following the Table6.4, check the
following, and perform the test again.
• The QJ71MB91, power supply module and PLC CPU are mounted correctly
on the base unit.
• The operating environment of the QJ71MB91 meets the general
specifications of the PLC CPU module.(
QCPU User's Manual
(Hardware Design, Maintenance and Inspection)
• The power capacity is sufficient.
• The hardware of the PLC CPU and base unit is normal according to the
manual of each module.
SYSTEM
CONFIGURATION
4
5
FUNCTION
If, after checking the above points and re-performing the test, the hardware test is
completed abnormally again, a QJ71MB91 hardware error may have occurred.
Please consult your local Mitsubishi service center or representative, explaining a
detailed description of the problem.
3
SPECIFICATIONS
Developer.(
Section 6.6)
• Power OFF the station and connect a communication cable to the target
device.
• Power ON the station.
2
MODBUS(R) STANDARD
FUNCTIONS
(a) When completed normally
To start data communication with a target device after completing the test, perform
the following operation to start the data communication.
• Perform the intelligent function module switch settings at GX
OVERVIEW
(4) Self-loopback test completion
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
6
6.4 Unit Tests
6.4.2 Self-loopback test
6 - 10
6
PRE-OPERATIONAL PROCEDURES AND SETTINGS
6.5 Connection to a Target Device
This section explains the wiring between the QJ71MB91 and target device.
As a wiring precaution and one of the conditions for maximizing the function performance
of QJ71MB91 to ensure the highly reliable system, the wiring must be performed so as not
being influenced by noise.
(1) About shields
Ground the shield at one end.
(2) When connecting to the target device with an RS-232 line
Refer to the following for the connection cable QJ71MB91 side.
Section 3.2.1
(3) When connecting to the target device with an RS-422/485 line
Pay attention to the following when making a connection.
(a) Connection cable
Refer to the following regarding the RS-422/485 cable.
Section 3.3.2
(b) Terminal screws for the terminal block
M3 screws are used on the terminal block for the RS-422/485 interface.
Use a solderless terminal applicable for the terminal.
(4) Connection at the target device side
Make a connection in accordance with the target device’s specifications.
(5) Connection cable bending radius
Refer to the following for the connection cable bending radius.
Appendix 3
6 - 11
6.5 Connection to a Target Device
PRE-OPERATIONAL PROCEDURES AND SETTINGS
1
This section describes connection precautions and a connection example for using the
QJ71MB91 RS-232 interface.
OVERVIEW
6.5.1 How to connect the RS-232 interface
2
(1) Connection precautions
SYSTEM
CONFIGURATION
(a) Connection cable's FG signal line and shield
Connect the connection cable's FG signal line and shield as follows:
Table6.5 Connection cable's FG signal line and shield
Item
Connection on the QJ71MB91 side
Remarks
Connection
Connect to the QJ71MB91 side connector
Do not short-circuit the FG and
cable's FG signal
housing.
SG signal lines of the
3
When the FG and SG signal
Connecting
Connect to the target device's FG terminal or
lines are connected inside the
cable's shield
the QJ71MB91 side connector housing.
target device, do not connect
the FG signal line to the
QJ71MB91 side.
1) Connect the FG terminal on the target device and the QJ71MB91 side using
the shield of the connection cable.
2) Connect each signal line other than SG with the SG signal line in twisted pair.
Shield
Target device side
5
SD
RD
RD
SD
Output for cable
disconnection
detection
FUNCTION
FG
6
Input for cable
disconnection
detection
SG
SG
Figure 6.9 RS-232 cable shield
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
QJ71MB91 side
MODBUS(R) STANDARD
FUNCTIONS
4
(b) Connection diagram
Connect the lines as shown below.
To connector
housing
SPECIFICATIONS
connection cable.
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
6
6.5 Connection to a Target Device
6.5.1 How to connect the RS-232 interface
6 - 12
6
PRE-OPERATIONAL PROCEDURES AND SETTINGS
(2) Connection example
QJ71MB91 (CH1)
Master or Slave
Signal name
RD
SD
SG
Output for cable
disconnection
detection
Input for cable
disconnection
detection
Pin No.
Target device
Slave or Master
Signal name
1
2
3
4
5
6
RD
SD
SG
7
8
9
Figure 6.10 RS-232 cable connection example
POINT
For other signal wirings on the target device, refer to the instruction manual of the
target device.
6 - 13
6.5 Connection to a Target Device
6.5.1 How to connect the RS-232 interface
PRE-OPERATIONAL PROCEDURES AND SETTINGS
1
This section describes connection precautions and a connection example for using the
QJ71MB91 RS-422/485 interface.
2) Connect the (FG) of the QJ71MB91 to the FG terminal of the power supply
module on the station to which the QJ71MB91 is installed, or to the FG
terminal of the control panel on which the QJ71MB91 PLC is installed.
3) Connect nnA and nnB of each signal line of the connection cable in a pair.
QJ71MB91 side
SDA
SDB
FG
RDA
FG
Target device side
SDA
SDB
RDA
RDB
SG
RDA
RDB
SDA
SDB
SG
(FG)*1
RDB
(FG)*1
FG
Shield
SPECIFICATIONS
1) Make connection between the FGs of both stations with the shield of the
connection cable.
For the target device side, follow the instruction manual of the target device.
3
4
MODBUS(R) STANDARD
FUNCTIONS
(b) Connecting cable's shield
Connect the shield of the connection cable to either FG terminal on the connected
device.
If normal data communication is not available due to external noise even with the
above-mentioned wiring, perform the following wiring.
5
FUNCTION
(a) When connecting SG and FG signal lines
When connecting the QJ71MB91 side SG and FG signal lines to the target
device, connect them according to the specifications of the target device.
SYSTEM
CONFIGURATION
2
(1) Connection precautions
SG
OVERVIEW
6.5.2 How to connect the RS-422/485 interface
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Correspondence between RS-422/485 terminal block and signal position
Figure 6.11 RS-422/485 cable shield
* 1 The QJ71MB91's FG terminal can be connected to either one.
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
6
6.5 Connection to a Target Device
6.5.2 How to connect the RS-422/485 interface
6 - 14
6
PRE-OPERATIONAL PROCEDURES AND SETTINGS
(c) Terminating resistor
Terminating resistor setting (or connection) is required for the stations of both line
ends.
For the QJ71MB91 side, connect the terminating resistor (packed with the
QJ71MB91), as described in this section and according to the specifications of the
target device.
For the target device side, connect or set the terminating resistor according to the
instruction manual of the target device.
(Terminating resistor to be connected to the QJ71MB91)
• For RS-422 communications, connect a "330
1/4W" terminating resistor.
• For RS-485 communications, connect a "110
1/2W" terminating resistor.
* How to distinguish terminating resistors
330
110
Orange Orange Brown
Brown
Brown
Brown
Figure 6.12 How to distinguish terminating resistors
(d) When any data communication is not possible
If any data communication with the target device is not possible, check the polarity
of the target device.
If the polarities of the QJ71MB91 and target device do not match, reverse the
polarity of each signal on either device side. This may enable the data
communications.
POINT
Devices connected to the QJ71MB91 RS-422/485 interface must be all RS-422 or
all RS-485.
6 - 15
6.5 Connection to a Target Device
6.5.2 How to connect the RS-422/485 interface
PRE-OPERATIONAL PROCEDURES AND SETTINGS
1
OVERVIEW
(2) Connection examples
(a) Connection for 1:1 communication
Target device
Slave or
Master
Terminating
resistor
R
Signal name
RDA
RDB
SDA
SDB
Signal name
SDA
SDB
RDA
RDB
SG
FG
2
R
Terminating
resistor
SYSTEM
CONFIGURATION
QJ71MB91 (CH2)
Master or Slave
3
SPECIFICATIONS
SG
FG
Figure 6.13 Connection for 1:1 communication
(b) Connection for 1:n communication when host is master
QJ71MB91
R
Terminating
resistor
R
SDA
SDB
RDA
RDB
SG
FG
Third party
slave station
SDA
SDB
RDA
RDB
SG
FG
SDA
SDB
RDA
RDB
SG
FG
R
Terminating
resistor
R
Terminating
resistor
5
FUNCTION
Terminating
resistor
Third party
slave station
MODBUS(R) STANDARD
FUNCTIONS
4
1) For 4-wire communications
Figure 6.14 Connection (for 1:n communication, 4 wire) when host is master
2) For 2-wire communications
6
Third party
slave station
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
QJ71MB91
Third party
slave station
SDA
SDA
SDA
SDB
SDB
SDB
RDA
RDA
RDA
Terminating
R
R
resistor
RDB
RDB
RDB
SG
SG
SG
FG
FG
FG
Figure 6.15 Connection (for 1:n communication, 2 wires) when host is master
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
6
6.5 Connection to a Target Device
6.5.2 How to connect the RS-422/485 interface
6 - 16
6
PRE-OPERATIONAL PROCEDURES AND SETTINGS
(c) Connection for 1:n communications when host is slave
1) When performing 1:n communication with third party master station (RS-422/
485 interface)
< For 4-wire communications >
QJ71MB91
QJ71MB91
Third party
master station
Terminating
resistor
R
Terminating
resistor
R
Third party
slave station
SDA
SDA
SDA
SDA
SDB
SDB
SDB
SDB
RDA
RDA
RDA
RDA
RDB
RDB
RDB
RDB
SG
SG
SG
SG
FG
FG
FG
FG
Figure 6.16 Connection (for 1:n communication, 4 wires) when host is slave
R
Terminating
resistor
R
Terminating
resistor
< For 2-wire communications >
QJ71MB91
Third party
master station
Terminating
resistor
R
SDA
SDB
RDA
RDB
SG
FG
QJ71MB91
Third party
slave station
SDA
SDB
RDA
RDB
SG
FG
SDA
SDB
RDA
RDB
SG
FG
R
Figure 6.17 Connection (for 1:n communication, 2 wires) when host is slave
6 - 17
6.5 Connection to a Target Device
6.5.2 How to connect the RS-422/485 interface
SDA
SDB
RDA
RDB
SG
FG
PRE-OPERATIONAL PROCEDURES AND SETTINGS
2) When performing 1:n communication with a third party master station (RS-232
interface)
(Link operation setting)
< For 4-wire communications >
Third party
master station
2
Output for cable
disconnection
detection
SYSTEM
CONFIGURATION
SD
RD
SG
QJ71MB91
Input for cable
disconnection
detection
Third party
slave station
Link operation
setting
3
SDA
SDA
SDA
Terminating
R
resistor
SDB
SDB
SDB
RDA
RDA
RDA
Terminating R
R Terminating
RDB
RDB
RDB
resistor
resistor
SG
SG
SG
FG
FG
FG
Figure 6.18 Connection (for link operation setting, 1:n communication, 4 wires) when host is slave
R
< For 2-wire communications >
Third party
master station
SD
RD
SG
QJ71MB91
QJ71MB91
RS-232
4
MODBUS(R) STANDARD
FUNCTIONS
Terminating
resistor
SPECIFICATIONS
SD
RD
SG
QJ71MB91
RS-232
OVERVIEW
1
SD
RD
SG
Output for cable
disconnection
detection
QJ71MB91
5
Third party
slave station
SDA
SDA
SDA
SDB
SDB
SDB
RDA
RDA
RDA
Terminating R
R
resistor
RDB
RDB
RDB
SG
SG
SG
FG
FG
FG
Figure 6.19 Connection (for link operation setting, 1:n communication, 2 wires) when host is slave
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Link operation
setting
FUNCTION
Input for cable
disconnection
detection
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
6
6.5 Connection to a Target Device
6.5.2 How to connect the RS-422/485 interface
6 - 18
6
PRE-OPERATIONAL PROCEDURES AND SETTINGS
6.6 Intelligent Function Module Switch Setting
Set the operation mode, transmission speeds, transmission settings and station numbers.
(1) Setting procedures
1.
2.
Start the GX Developer.
Double-click "PLC parameter" in the project
window of GX Developer.
3.
Click the "I/O assignment" tab to display the I/O
assignment setting screen.
Set the following to the slot where the
QJ71MB91 is mounted.
Type
: Select "Intelli".
Model name : Enter the model name of the
module.
Points
: Select 32 points.
Start XY
: Enter the QJ71MB91 head
input/output numbers.
Detailed setting : Specify the control CPU of the
QJ71MB91 in a multiple CPU
system.
4.
Click the I/O assignment settings screen
Switch setting button to display the screen on
the left.
Referring to steps (2) and later in this section,
make switch settings.
Entering the values in hexadecimal makes the
setting easy.
Change the input format into HEX before entering the values.
Figure 6.20 Intelligent function module switch setting procedure
6 - 19
6.6 Intelligent Function Module Switch Setting
5.
After setting, write the data to the PLC, and
power the PLC OFF, then ON or reset the PLC
CPU.
PRE-OPERATIONAL PROCEDURES AND SETTINGS
1
Details of switches 1 to 5 are shown below.
Table6.6 Intelligent function module switch
Switch 1
Mode setting
Default
0000H
Reference
This section
(2) (a)
CH1
Communication speed/transmission
Switch 2
setting
Switch 3
Mode setting
0700H
0000H
This section
(2) (b)
This section
(2) (a)
CH2
Communication speed/transmission
Switch 4
setting
Switch 5
CH1,2 station No. setting
0700H
0000H
2
SYSTEM
CONFIGURATION
Description
3
This section
(2) (b)
This section
(2) (c)
SPECIFICATIONS
Switch No.
OVERVIEW
(2) Setting details
1.
2.
3.
The settings made with the intelligent function module switches become
effective after power is switched OFF and then ON or after the PLC CPU is
reset.
Setting change during operation is not available.
When no intelligent function module switch setting has been made, the initial
values of each switch are used for operation.
If using the link operation function, set two channels to the same settings.
(Except for MODBUS device assignment parameter starting methods in the
transmission speed setting/transmission setting (switch 2, 4).)
5
FUNCTION
POINT
MODBUS(R) STANDARD
FUNCTIONS
4
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
Remark
For the operation method of GX Developer, refer to the following manual.
GX Developer Operating Manual
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
6
6.6 Intelligent Function Module Switch Setting
6 - 20
6
PRE-OPERATIONAL PROCEDURES AND SETTINGS
(a) Mode setting (Switch 1: CH1 side, Switch 3: CH2 side)
Set the operation mode of the QJ71MB91.
Table6.7 Mode setting
Set value *1
Operation mode
Description
Switch 1
Switch 3
CH1
CH2
0000H
0000H
Master function
Master function
0000H
0001H
Master function
Slave function
Master function : Performs communication as master
0001H
0000H
Slave function
Master function
0001H
0001H
Slave function
Slave function
0002H
0002H
Link operation (Slave function) *2
000DH
000DH
Hardware test
000EH
000DH
Self-loopback test
-
000DH
000EH
-
Self-loopback test
000EH
000EH
Self-loopback test
Self-loopback test
station.
Slave function
: Performs communication as slave
station.
Relays data between CH1 and CH2 with the link operation
function. (
Section 5.3.3)
Performs test to check the RAM and ROM of
QJ71MB91.(
Section 6.4.1)
Performs tests to check the send/receive function of the
QJ71MB91 and communications with the PLC CPU.
(
Section 6.4.2)
* 1 Setting a value other than indicated in the table results in a switch error.
* 2 For the link operation (slave function), set "0002H" to both Switch 1 and 3.
Setting the value for only one switch results in a switch error.
6 - 21
6.6 Intelligent Function Module Switch Setting
6
PRE-OPERATIONAL PROCEDURES AND SETTINGS
(b) Communication speed/transmission setting (Switch 2: CH1 side, Switch 4: CH2
side)
Set the transmission speed and other specifications for transmission with the
target device.
b7
b6
Communication speed setting
b5
b4
b3
b2
b1
b0
2
Transmission setting
SYSTEM
CONFIGURATION
Figure 6.21 Structure of communication speed and transmission
settings
1) Transmission setting
Table6.8 Transmission setting
ON (1)
3
Description
The MODBUS
device assignment parameter starting method
must be set only for Switch 2 regardless of the channel used.
When "Start with the default parameters" is set, the module is
device
b0
assignment
Switch 2
parameter
Start with the
Start with the
default
user-set
parameters
parameters *1
started with the parameters assigned by default.(
Section
4
7.3.1 (3))
starting
When "Start with the user-set parameters" is set, the module is
started with the MODBUS
method
device assignment parameters set on
the sequence program or GX Configurator-MB.(
Section
7.3.1 (2))
Switch 4
b1
Data bit *2
b2
Parity bit presence
b3
Even/odd parity
Fixed to OFF(0)
-
8
7
Present
Not present
Even
Odd
5
Set data bits.
Specify whether parity bit is present or not.
In the case of "Present", vertical parity check is performed.
Set even or odd parity.
This setting is valid only when "Parity bit presence" is set to
"Present".
b4
Stop bit
b5
Frame mode
1
2
RTU mode
ASCII mode
6
Set the stop bit.
Set the frame mode.(
Section 4.2.1)
Set whether to enable or disable data writing to the RUN-status
PLC CPU by a request message from the master.
If this is set to "Disable", when a message requesting the device
b6
Online change
Disable
Enable
write is received from the master, the QJ71MB91 returns an error
response.
This setting is valid only when the slave function is set for the
channel.
b7
Not used
Fixed to OFF(0)
FUNCTION
MODBUS
-
* 1 Set the MODBUS device assignment parameters before sending request messages to the
QJ71MB91.
If a request message is sent before the setting, the QJ71MB91 will send a response message
(error completion). (The slave function does not operate.)
* 2 Set it to OFF (8 bits) in RTU mode.
6.6 Intelligent Function Module Switch Setting
6 - 22
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
OFF (0)
7
PARAMETER SETTING
Item
8
UTILITY PACKAGE
(GX Configurator-MB)
Bit
SPECIFICATIONS
b8
MODBUS(R) STANDARD
FUNCTIONS
b15 b14 b13 b12 b11 b10 b9
OVERVIEW
1
6
PRE-OPERATIONAL PROCEDURES AND SETTINGS
POINT
When setting parameters using the GX Configurator-MB, turn the MODBUS
device assignment parameter start method ON.
2) Communication speed setting *1 *2
Table6.9 Communication speed setting
Communication
Bit position
speed
Bit position
Communication
speed
b15 to b8
b15 to b8
300 bps
00H
14400 bps
06H
600 bps
01H
19200 bps
07H
1200 bps
02H
28800 bps
08H
2400 bps
03H
38400 bps
09H
4800 bps
04H
57600 bps
0AH
9600 bps
05H
115200 bps
0BH
* 1 Total communication speed for 2 channels can be set within 115200bps.
* 2 Do not set any value or set “07H” (Initial value) in the communication speed setting for an unused
channel.
(c) CH1, 2 station No. setting (Switch 5)
Set slave station No. of the QJ71MB91.
For the master function, set 00H.
b15 b14 b13 b12 b11 b10 b9
CH2 side Station No.
b8
b7
b6
b5
b4
b3
b2
b1
b0
CH1 side Station No.
Figure 6.22 CH1, 2 station No. setting structure
Table6.10 Station No. setting
Set value *1
Description
1H to F7H
Sets a slave station No. (1 to 247).
* 1 Setting a value other than indicated in the table results in a switch error.
6 - 23
6.6 Intelligent Function Module Switch Setting
PRE-OPERATIONAL PROCEDURES AND SETTINGS
1
OVERVIEW
6.7 Maintenance, Inspection
This section explains maintenance, inspection and removal/installation methods for
QJ71MB91.
1) Check that any poor connection is observed at the terminating resistors or
connection cables.
2) Check that the module fixing screws and the terminal block mounting screws
are tightened securely.
POINT
For the QJ71MB91 maintenance and inspection, read the
provided in the first pages of this manual.
safety precautions
SPECIFICATIONS
(QJ71MB91 inspection items)
3
4
MODBUS(R) STANDARD
FUNCTIONS
For the QJ71MB91, except for the following check items, there are no specific inspection
items.
For other than shown below, in order to have the system run normally in optimal
conditions, perform maintenance as described in the QCPU User's Manual (Hardware
Design, Maintenance and Inspection).
SYSTEM
CONFIGURATION
2
6.7.1 Maintenance, inspection
5
FUNCTION
6.7.2 When removing or installing the module
When removing/installing the module, read "6.1 Handling Precautions" and pay full
attention to safety to handle the product correctly.
The module replacement procedure is shown below.
(Procedure 1) Power OFF the station.
(Procedure 2) Disconnect the cable and remove the module.
(Procedure 3) Replace the module and start it according to "6.2 Pre-operational
procedures and settings".
< PLC CPU replacement operation procedure >
(Procedure 1) Use the GX Developer to read the PLC parameters from the PLC CPU and
save them.
(Procedure 2) Replace the PLC CPU.
(
QCPU
Inspection))
User's
Manual
(Hardware
Design,
Maintenance
and
(Procedure 3) Register the PLC parameters saved with the GX Developer to the PLC
CPU.
6.7 Maintenance, Inspection
6.7.1 Maintenance, inspection
6 - 24
7
PARAMETER SETTING
< QJ71MB91 replacement operation procedure >
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
8
UTILITY PACKAGE
(GX Configurator-MB)
6
7
PARAMETER SETTING
CHAPTER7 PARAMETER SETTING
This chapter explains the setting of the parameters.
7.1 Parameter Settings and Setting Procedure
(1) Parameter types
(a) Automatic communication parameter
Set the automatic communication parameters when using the automatic
communication function with the QJ71MB91 operated as a master.(
Section
7.2)
Up to 32 automatic communication parameters can be set for each channel.
If the automatic communication function is not to be used, setting of these
parameters are not required.
(b) MODBUS
device assignment parameter
Set the MODBUS
device assignment parameters when using the MODBUS
device assignment function with the QJ71MB91 operated as a slave.(
Section 7.3)
When using the initial values preset to the QJ71MB91, no setting is required for
these parameters.
(2) Parameter setting method
Set parameters to the QJ71MB91 by either of the following methods.
(a) Using utility package
Set the parameters from the GX Configurator-MB utility package.
(
CHAPTER 8)
(b) Using sequence program
Set the parameters by a sequence program.(
7-1
7.1 Parameter Settings and Setting Procedure
Section 9.1 to 9.3)
PARAMETER SETTING
1
(3) Parameter setting procedure
OVERVIEW
Set the parameters by the following procedure.
Start
NO
YES
Set the intelligent function module
R
switch's MODBUS device
assignment parameter starting
method (switch 2, bit 0) to ON.
(
Section 6.6)
Set function parameters to be used.
Automatic communication parameters
Change MODBUS R device
assignment?
NO
3
YES
SPECIFICATIONS
Set parameters with
GX Configurator-MB?
(
SYSTEM
CONFIGURATION
2
Set the intelligent function module
switch's MODBUS R device
assignment parameter starting
method (switch 2, bit 0) to ON.
(
Section 6.6)
Section 8.4.1)
4
MODBUS R device assignment parameters
Create a sequence program for parameter
setting of functions to be used.
Section 8.4.2)
Automatic refresh settings
(
MODBUS(R) STANDARD
FUNCTIONS
(
Automatic communication parameters
Section 8.5)
(
Section 9.1.1, 9.2.1)
MODBUS R device assignment parameters
(
Section 9.1.2, 9.2.2)
1)
FUNCTION
With the RUN/STOP switch set to
RUN, reset the PLC CPU.
5
After writing the sequence
program to the PLC CPU,
reset the PLC CPU
Write parameters to the PLC CPU.
Put the PLC CPU into the RUN status
6
SP.PARA ERROR occurred
in the PLC CPU?
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
YES
NO
Check the auto-refresh parameters,
the head input/output numbers, etc.
PARAMETER SETTING
7
(To next page)
Figure 7.1 Parameter setting procedure
8
UTILITY PACKAGE
(GX Configurator-MB)
7
7.1 Parameter Settings and Setting Procedure
7-2
7
PARAMETER SETTING
(From previous page)
NO
ERR.LED is ON?
YES
NO
Use automatic
communication function?
YES
The used channel's
automatic communication operation
status (X6/XE) is ON? *1
NO
Refer to buffer memory's Automatic
communication parameter error code storage
area (address: 0C16H/0C18H) and Automatic
communication parameter setting result
storage area (address: 0C17H/0C19H), and
modify automatic communication parameters.
YES
1)
R
MODBUS device
assignment parameter setting
existence (XA) is ON? *1
NO
R
YES
Parameter setting complete
Refer to buffer memory's MODBUS device
assignment parameter error code storage
area (address:0C13H) and MODBUS R device
assignment parameter setting result storage
area (address: 0C14H to 0C15H), and modify
MODBUS R device assignment parameters.
1)
Figure 7.1 Parameter setting procedure (Continued)
* 1 The X signal status can be confirmed on GX Configurator-MB.(
7-3
7.1 Parameter Settings and Setting Procedure
Section 8.6.1)
7
PARAMETER SETTING
1
Set the automatic communication parameters when using the automatic communication
function with the QJ71MB91 operated as a master.
(
Section 5.2.1)
Up to 32 automatic communication parameters can be set for each channel.
SYSTEM
CONFIGURATION
2
Table7.1 Automatic communication parameter list
CH2
0200H to
0380H to
0201H
0381H
(512 to
(896 to
513)
897)
0202H
0382H
(514)
(898)
Parameter name
Setting range
Setting parameter existence
Default
00000000H: Disabled
00000000H
00000001H: Enabled
0: Broadcast
Target station No.
1
1 to 247: Slave station No.
Reference
This
section (1)
This
section (2)
4
0:
Upon reception of a reply message
from a slave, immediately issues the
next request message.
0203H
0383H
(515)
(899)
Request interval timer value
3
0
2 to 65535:
This
section (3)
The time from when the QJ71MB91
sends a request message until it
5
sends the next request message (Set
time = set value
MODBUS(R) STANDARD
FUNCTIONS
CH1
SPECIFICATIONS
7.2.1 Automatic communication parameter details
Address
OVERVIEW
7.2 Automatic Communication Parameter
10 ms)
Response monitoring timer value
0 : 30 seconds
2 to 65535: Response monitoring
(516)
(900)
parameter 1
Response monitoring timer
timer (Set time = set value
value/Broadcast delay value
10 ms)
Broadcast delay value (Target station
0
This
section (4)
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
No. is 0)
0: 400 ms
2 to 65535: Delay time (set time = set
value
10 ms)
0000H: Not specified
0100H: Read coils
7
0200H: Read discrete inputs
0205H
0385H
Type specification of the
0400H: Read input registers
(517)
(901)
target MODBUS
0500H: Read holding registers
device
0000H
This
section (5)
0001H: Write coils
0005H: Write holding registers
0505H: Read/Write holding registers
0000H: None
1000H to 1FFFH:
0206H
0386H
Read
Head buffer
(518)
(902)
setting
memory address
CH1 read data storage area
6
0000H
2000H to 2FFFH:
This
section (6)
CH2 read data storage area
(Continued on next page)
7.2 Automatic Communication Parameter
7.2.1 Automatic communication parameter details
7-4
PARAMETER SETTING
0384H
8
UTILITY PACKAGE
(GX Configurator-MB)
communication
0204H
FUNCTION
(Target station No. is 1 to 247)
Automatic
7
PARAMETER SETTING
Table7.1 Automatic communication parameter list (Continued)
Address
Parameter name
CH1
CH2
0207H
0387H
(519)
(903)
Read
0208H
0388H
Setting
(520)
(904)
Setting range
Target MODBUS
device head number
Access points
Default
0 to 65535
0
0 to 2000
0
Reference
This
section (7)
This
section (8)
0000H: None
0209H
0389H
(521)
(905)
Automatic
Head buffer memory
communication
address
Parameter 1
020AH
038AH
(522)
(906)
020BH
038BH
(523)
(907)
020CH to
038CH to
037FH
04FFH
communication
(524 to
(896 to
Parameter 2 to
895)
1279)
32
CH1 write data storage area
0000H
4000H to 4FFFH:
Write
setting
3000H to 3FFFH:
This
section (6)
CH2 write data storage area
Target MODBUS
device head number
Access points
0 to 65535
0
0 to 1968
0
This
section (7)
This
section (8)
Automatic
(Same as in automatic communication parameter 1)
(1) Setting parameter existence
Set whether to enable or disable the automatic communication parameters.
(2) Target station No.
Specify a slave to which request messages are sent.
The target station No. is entered in the address field of the request message sent to
the communication target slave device.(
Section 4.2)
(3) Request interval timer value
The Request interval timer represents the interval between any successive request
message transmissions in the automatic communication function.
The time from when the QJ71MB91 sends a request message until it sends the next
request message is measured.
Request interval timer
Master
(QJ71MB91)
Slave
Receiving
response
message
Request
message
Request
Response
message
processing Message
Figure 7.2 Request interval timer
7-5
7.2 Automatic Communication Parameter
7.2.1 Automatic communication parameter details
Receiving
response
message
Request
message
Request
Response
message Message
processing
PARAMETER SETTING
1
Response
Receiving
response
message
3
SPECIFICATIONS
Request
Response
message
processing Message
The following areas can be checked to see if the Response monitoring timer has
timed out.
1) Relevant automatic communication operation status storage area in the buffer
memory (address: 0C20H to 0C21H/0C22H to 0C23H) turns ON.
2) An error code is stored in the automatic communication error code storage
area in the buffer memory (address: 0C28H to 0C47H/0C48H to 0C67H).
5
Section 11.4.1)
POINT
1.
2.
The Response monitoring timer value should be smaller than the Request
interval timer value.
If the Response monitoring timer value is larger than the Request interval
timer value, a request interval timer timeout error (error code: 737BH) will
occur.
Set an adequate response monitoring timer value, taking the processing time
of the target slave device into account.
While the Response monitoring timer is on, request messages cannot be sent
with dedicated instructions.
When the automatic communication function and dedicated instructions are
used on the same channel, set appropriate automatic communication
parameters and create a proper sequence program so that each the
dedicated instructions can be executed in the right timing.(
9.2.3)
Section
FUNCTION
(
4
MODBUS(R) STANDARD
FUNCTIONS
*1 When request message is addressed to any
of station No.1 to 247
Figure 7.3 Response monitoring timer
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Slave 1
*1
Request
message
7
PARAMETER SETTING
Master
(QJ71MB91)
2
SYSTEM
CONFIGURATION
(a) Response monitoring timer value (Target station No. is 1 to 247)
The Response monitoring timer is used to monitor the time from when the
QJ71MB91 sends a response message until it receives a response message from
the slave.
If the QJ71MB91 does not receive any response message from the slave before
the Response monitoring timer times out, it is recognized that the target slave is
faulty.
OVERVIEW
(4) Response monitoring timer value/Broadcast delay value
8
UTILITY PACKAGE
(GX Configurator-MB)
7
7.2 Automatic Communication Parameter
7.2.1 Automatic communication parameter details
7-6
7
PARAMETER SETTING
(b) Broadcast delay value (Target station No. is 0)
The Broadcast delay monitors the time interval between transmissions when
request messages are broadcast.
Request interval timer
Broadcast delay
Master
(QJ71MB91)
*1
Request
message
Request
message
Slave 1
Request
message
processing
Slave 2
Request
message
processing
Slave 3
Request
message
processing
*1 When request message is addressed to station No.0
(broadcast)
Figure 7.4 Broadcast delay
POINT
1.
2.
3.
Since requests are broadcast to all slave devices, an adequate broadcast
delay value must be set in consideration of each processing time of all slave
devices.
If the broadcast delay value is not enough for any of the slave devices, the
next request to the slave device may result in an error.
The Broadcast delay value should be smaller than the Request interval timer
value.
If the Broadcast delay value is greater than the Request interval timer value,
request messages will be sent during at the intervals of the Request interval
timer.
While the Broadcast delay is on, request messages cannot be sent with
dedicated instructions.
When the automatic communication function and dedicated instructions are
used on the same channel, set appropriate automatic communication
parameters and create a proper sequence program so that each of the
dedicated instructions can be executed in the right timing.(
9.2.3)
7-7
7.2 Automatic Communication Parameter
7.2.1 Automatic communication parameter details
Section
PARAMETER SETTING
1
device
Specify the types of the read/write target MODBUS
devices.
b8 b7
b0
Write target
Table7.2 Type specification of the target MODBUS
Setting value
device
Target MODBUS
00H
No specification
01H
Coil
02H
Input
04H
Input register
05H
Holding register
2
device
SYSTEM
CONFIGURATION
Figure 7.5 Structure for Type specification of the target MODBUS
device type
SPECIFICATIONS
3
Table7.3 Setting range for Type specification of the target MODBUS
Type specification of the target MODBUS
device
device
Function code
Read target
value
0100H
Coil
0200H
Input
5
Write target
01
Read coils
02
Read discrete inputs
FUNCTION
Setting
No specification *1
0400H
Input register
04
Read input registers
0500H
Holding register
03
Read holding registers
Coil *3
15
Write multiple coils
Holding register *3
16
Write multiple registers
Holding register
23
Read/write multiple registers
0001H
6
No specification *1
0005H
0505H
Holding register *2
* 1 To perform only read or write, set "0" to each of the following:
Head buffer memory address (
Target MODBUS
Access points (
7
This section (6))
device head number (
4
MODBUS(R) STANDARD
FUNCTIONS
(a) Setting range
Available combinations of the read and write targets are as shown in the table
below.
No other combinations are available.
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Read target
This section (7))
This section (8))
* 2 Reading and writing can be performed simultaneously with one instruction only when 0505H
(Read/write multiple registers) is set.
* 3 Broadcast can be performed with 0001H (Write multiple coils) and 0005H (Write multiple registers)
only.
PARAMETER SETTING
b15
OVERVIEW
(5) Type specification of the target MODBUS
8
UTILITY PACKAGE
(GX Configurator-MB)
7
7.2 Automatic Communication Parameter
7.2.1 Automatic communication parameter details
7-8
7
PARAMETER SETTING
(6) Head buffer memory address (Read/Write setting)
Specify the head address of the buffer memory where the data read from or written to
the slave are stored.
The head buffer memory addresses should not duplicated among Automatic
communication parameters 1 to 32.
(7) Target MODBUS
device head number (Read/Write setting)
Specify the head number of the read or write target MODBUS
device.
(a) Specifying the head number
As the target MODBUS device head number, set "(Last 5 digits of actual device
number) - 1".
Example: Set "17" for the holding register, 400018.
(b) When specifying a value of 32768 (8000H) or more in a sequence program
When specifying a value of 32768 (8000H) or more in a sequence program, set
the value in hexadecimal.
(8) Access points (Read/Write setting)
Set the number of points to be written to the MODBUS
the MODBUS
device and to be read from
device.
The access points vary depending on the type specification of the target MODBUS
device.
Table7.4 Access points
Type specification of the target MODBUS
Setting
Read target
value
0100H
Coil
0200H
Input
device
Write target
Access points setting range
Read points
Write points
1 to 2000 points
-
1 to 2000 points
-
No specification
0400H
Input register
1 to 125 points
-
0500H
Holding register
1 to 125 points
-
Coil
-
1 to 1968 points
Holding register
-
1 to 123 points
Holding register
1 to 125 points
1 to 121 points
0001H
No specification
0005H
0505H
7-9
Holding register
7.2 Automatic Communication Parameter
7.2.1 Automatic communication parameter details
PARAMETER SETTING
1
In the access to a bit device (coil/input) of a slave, the fraction bits are handled as
described below.
• Bit device read
Target MODBUS
device head number
0200H (input)
1000H (4096)
16628
to
35
3
<Target slave device area>
116629
to
b15
<QJ71MB91 buffer memory>
b15
Access points
b0
b0
Read
1000H
1001H
1002H
116640 to 116625
116656 to 116641
116672 to 116657
116663
Remaining area is masked with 0
• Bit device write
4
Automatic communication parameter: Write setting
Head buffer
Target MODBUS
Target MODBUS
Device type setting
Memory address
device head number
0001H (coil)
3000H (12288)
1305
<QJ71MB91 buffer memory>
to
b15
<Target slave device area>
001306 to
b0 Write b15
SPECIFICATIONS
address
Access points
5
MODBUS(R) STANDARD
FUNCTIONS
Head buffer memory
Target MODBUS
SYSTEM
CONFIGURATION
2
Automatic communication parameter: Read setting
device type setting
OVERVIEW
POINT
5
b0
3000H
001312 to 001297
FUNCTION
Remaining area is ignored
001310
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
7
7.2 Automatic Communication Parameter
7.2.1 Automatic communication parameter details
7 - 10
7
PARAMETER SETTING
7.3 MODBUS(R) Device Assignment Parameter
Using MODBUS device assignment parameters, the MODBUS
with the PLC CPU device memory.
devices are correlated
This allows direct access from the MODBUS compatible master device to the PLC CPU
device memory.
PLC CPU
No sequence
program required
MODBUS R
Master device
QJ71MB91 (Slave function)
R
MODBUS device assignment parameter
Device
D300
1234H
Device memory
MODBUS R device
D299
400499
D300
400500
D301
400501
Request message (Write 1234H to
holding register 400500)
RS-232, RS-422 or RS-485
Figure 7.6 MODBUS
7 - 11
device and PLC CPU device
7.3 MODBUS(R) Device Assignment Parameter
7
PARAMETER SETTING
1
MODBUSR device assignment
parameter setting example
MODBUS R device
PLC CPU device
Internal relay (M)
Coil
000001
M0
Coil assignment 1
3500
M1201
003500
3500
Device code
Head device number
004000
M4700
Head coil number
Assignment points
M(0090H)
1201
0
3500
M8191
8192
Coil assignment 2
Output (Y)
Device code
Y0
012191
8192
Head device number
Head coil number
Assignment points
Y(009DH)
0
3999
8192
OVERVIEW
device assignment parameter setting]
2
SYSTEM
CONFIGURATION
[Schematic diagram of MODBUS
3
Y1FFF
5
Head device number
5
065000
065004
065536
Head coil number
Assignment points
L(0092H)
0
64999
5
Special register (SD)
SD0
Holding register
400001
2048
1000
SD2047
402000
Data register (D)
D0
D999
401000
Device code
Head device number
Head holding register number
2048
1000
Holding register assignment 1
404047
Assignment points
SD(00A9H)
0
1999
2048
Holding register assignment 2
Device code
D6000
430000
6288
Head device number
Head holding register number
Assignment points
6288
Holding register assignment 3
Head device number
Head holding register number
Assignment points
D(00A8H)
6000
29999
6288
465536
device assignment parameter setting diagram
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
Figure 7.7 MODBUS
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Device code
5
D(00A8H)
0
0
1000
D12287
436287
MODBUS(R) STANDARD
FUNCTIONS
4
L8191
FUNCTION
L0
L4
Device code
Latch relay (L)
SPECIFICATIONS
Coil assignment 3
7.3 MODBUS(R) Device Assignment Parameter
7 - 12
7
PARAMETER SETTING
7.3.1 MODBUS(R) device assignment to the PLC CPU device memory
(1) MODBUS device size
The MODBUS
devices available for the QJ71MB91 are shown below.
Table7.5 MODBUS
device size
Read/Write
Access points
Coil
Read/Write
65536 points
000001 to 065536
Input
Read
65536 points
100001 to 165536
Input register
Read
65536 points
300001 to 365536
Read/Write
65536 points
400001 to 465536
(*1)
1042432 points *2
MODBUS
device type
Holding register
Extended file register
MODBUS
device number
File No.: 0 to 104 *2
600000 to 609999
* 1 The availability of Extended file register read/write depends on that of the file register (ZR) read/
write to the PLC CPU.
For example, if the file register (ZR) is stored on a Flash card, the extended file register is read only
because the file register (ZR) is read only.
(
QCPU User’s Manual (Function Explanation, Program Fundamentals))
* 2 The maximum access points and maximum file number of the extended file register depend on the
file register (ZR) assignment size of the PLC CPU.(
Explanation, Program Fundamentals))
QCPU User’s Manual (Function
Remark
Refer to the following for assignment of the extended file register and the PLC
CPU file register (ZR).
Section 7.3.2
7 - 13
7.3 MODBUS(R) Device Assignment Parameter
7.3.1 MODBUS(R) device assignment to the PLC CPU device memory
7
PARAMETER SETTING
1
(a) Before performing setting
With the intelligent function module switch, turn ON the MODBUS
device
assignment parameter starting method (switch 2, bit 0).(
Section 6.6)
If this switch is set to OFF, the operation will proceed based on the default
assignment parameters.
2
SYSTEM
CONFIGURATION
(
This section (3))
(b) Setting parameter list
Address
device assignment parameter list
Parameter name
0900H
Device code
(2304)
0901H
Head device number
(2305)
Setting range
Other than 0000H: Device code
0000H to FFFFH
0000H
Head coil number
0000H to FFFFH
Assignment points
0000H to FFFFH
4
(2307)
MODBUS(R) STANDARD
FUNCTIONS
Coil
0903H
0904H to
093FH
Coil assignment 2 to
(2308 to
16
(Same as in Coil assignment 1)
2367)
This section
Device code
(2368)
0941H
Head device number
(2369)
Other than 0000H: Device code
0000H to FFFFH
0000H
Head input number
0000H to FFFFH
Assignment points
0000H to FFFFH
6
Input
0943H
(2371)
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
(2370)
(2) (b) 1) to 4)
0000H: Device code not assigned
Input assignment 1
0942H
5
FUNCTION
0940H
3
0944H to
097FH
Input assignment 2 to
(2372 to
16
(Same as Input assignment 1)
7
2431)
(Continued on next page)
PARAMETER SETTING
(2306)
Reference
0000H: Device code not assigned
Coil assignment 1
0902H
Default
SPECIFICATIONS
Table7.6 MODBUS
OVERVIEW
(2) Setting details
UTILITY PACKAGE
(GX Configurator-MB)
8
7.3 MODBUS(R) Device Assignment Parameter
7.3.1 MODBUS(R) device assignment to the PLC CPU device memory
7 - 14
7
PARAMETER SETTING
Table 7.6 MODBUS
Address
Parameter name
0980H
Device code
(2432)
0981H
Head device number
(2433)
Setting range
assignment 1
Reference
Other than 0000H: Device code
0000H to FFFFH
0000H
Head input register
number
Input
Default
0000H: Device code not assigned
Input register
0982H
(2434)
device association parameter list (continued)
0000H to FFFFH
register
0983H
Assignment points
(2435)
0984H to
Input register
09BFH
assignment
(2436 to
(Same as in Input register assignment 1)
2 to 16
2495)
This section
09C0H
Device code
(2496)
09C1H
Head device number
(2497)
assignment 1
Other than 0000H: Device code
0000H to FFFFH
0000H
Head holding register
number
Holding
0000H to FFFFH
register
09C3H
Assignment points
(2499)
09C4H to
09FFH
(2500 to
2559)
7 - 15
0000H to FFFFH
Holding register
assignment
(2) (b) 1) to 4)
0000H: Device code not assigned
Holding register
09C2H
(2498)
0000H to FFFFH
(Same as in Holding register assignment 1)
2 to 16
7.3 MODBUS(R) Device Assignment Parameter
7.3.1 MODBUS(R) device assignment to the PLC CPU device memory
7
PARAMETER SETTING
1
MODBUS
devices.
The device codes have different setting abilities depending on the MODBUS
devices.
Refer to the following table for the device code setting availabilities.
OVERVIEW
1) Device code
Set PLC CPU devices and QJ71MB91 buffer memory to be assigned to the
2
MODBUS
Device name
Device
Device code
symbol
*5
Special relay
SM *3
0091H
Special register
SD *3
00A9H
Input
X *3
009CH
Output
Y*3
009DH
Internal relay
M*3
0090H
Latch relay
L
0092H
Annunciator
F
0093H
Edge relay
V
0094H
Link relay
B*3*4
00A0H
Data register
D*3
00A8H
Link register
W*3*4
00B4H
Coil
TC
00C0H
Contact
TS
00C1H
Current value
TN
00C2H
Coil
SC
00C6H
Contact
SS
00C7H
Current value
SN
00C8H
Coil
Input
Input
Hold
Register Register
Extension
File
Register
3
SPECIFICATIONS
Classification
device
SYSTEM
CONFIGURATION
Table7.7 Device code list
Internal system device
MODBUS(R) STANDARD
FUNCTIONS
4
Retentive
timer
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
7
(Continued on next page)
PARAMETER SETTING
Timer
6
8
UTILITY PACKAGE
(GX Configurator-MB)
Internal user device
FUNCTION
5
7.3 MODBUS(R) Device Assignment Parameter
7.3.1 MODBUS(R) device assignment to the PLC CPU device memory
7 - 16
7
PARAMETER SETTING
Table7.7 Device code list (Continued)
MODBUS
Classification
Device name
Device
Device
symbol
Code*5
Coil
CC
00C3H
Contact
CS
00C4H
Current value
CN
00C5H
Special link relay
SB*3
00A1H
Special link register
SW*3
00B5H
S
0098H
Direct input
DX
00A2H
Direct output
DY
00A3H
Index register
Index register
Z
00CCH
R
00AFH
File register
File register
ZR*1
00B0H
-
F000H
Counter
Coil
Input
Input
Device
Hold
Register Register
Extension
File
Register
Internal user device
Step relay
Direct device
QJ71MB91 buffer
memory*2*3
User free area
* 1 The assignment to the extended file register is fixed to the file register (ZR).
(
Section 7.3.2)
* 2 Refer to the following for the assignment to the QJ71MB91 buffer memory.
Section 7.3.3
* 3 When the access target is the MELSECNET/H remote I/O station to which the QJ71MB91 is
mounted, only this device is supported.
An error will occur if an access request is received from the master with any other device
assigned.(
Section 7.3.5)
* 4 Equivalent to LB and LW of the MELSECNET/H remote I/O stations.
* 5 When setting with GX Configurator-MB, input the head device.
7 - 17
7.3 MODBUS(R) Device Assignment Parameter
7.3.1 MODBUS(R) device assignment to the PLC CPU device memory
PARAMETER SETTING
1
3) Head MODBUS device number (Head coil number/Head input number/Head
input register number/Head holding register number)
MODBUS
device number, set the head number of the
device of the assignment target (QJ71MB91).
Use the following expression to find a setting value of the head MODBUS
device number:
3
Head MODBUS device number = Last 5 digits of relevant MODBUS
device number - 1
The head MODBUS
Assignment 1 to 16.
device number, 105140.
SPECIFICATIONS
Example: Set "5139" for the MODBUS
device number must not be duplicated among
Set unique head MODBUS device numbers.
The slave function of the QJ71MB91 does not run if any of the device number
settings are duplicated.
4) Assignment points
Set the device points of the PLC CPU device memory or QJ71MB91 buffer
memory to be assigned to the MODBUS
device.
4
MODBUS(R) STANDARD
FUNCTIONS
As the head MODBUS
2
SYSTEM
CONFIGURATION
address of the QJ71MB91 buffer memory to be assigned to the MODBUS
device.
OVERVIEW
2) Head device number
Set the head device number of the PLC CPU device memory or the head
5
If the master requests the QJ71MB91 to access the area outside the valid PLC
CPU device range or the user free area in the QJ71MB91 buffer memory, the
QJ71MB91 will send an exception response to the master.
FUNCTION
POINT
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
7
7.3 MODBUS(R) Device Assignment Parameter
7.3.1 MODBUS(R) device assignment to the PLC CPU device memory
7 - 18
7
PARAMETER SETTING
(3) Default assignment parameters
For assignment between the MODBUS devices and PLC CPU devices, default
assignment parameters are provided as initial values.
(a) Before using default assignment parameters
With the intelligent function module switch, turn OFF the MODBUS
device
assignment parameter starting method (switch 2, bit 0).(
Section 6.6)
If this switch is set to ON, the operation will proceed based on the set assignment
parameters.(
(b) MODBUS
This section (2))
device assignment by default assignment parameters
R
The following shows how the MODBUS devices are assigned by the MODBUS
device assignment parameters and the default values set to the QJ71MB91 buffer
memory.
MODBUS
Coil (000001 to 065536)
device assignment by default assignment parameters
Input (100001 to 165536)
000001
Holding register (400001 to 465536)
400001
300001
100001
X
8192 (0 to 1FFF)
Y
8192
(0 to 1FFF)
Coil assignment 1 008192
008193
8192
Input register (300001 to 365536)
12288
Input assignment 1
108192
D
(0 to 12287)
M
Holding register assignment 1 412288
(0 to 8191)
Coil assignment 2
016384
(Empty)
(Empty)
020481
2048
SM
(0 to 2047)
Coil assignment 3 022528
022529
SD
2048 (0 to 2047)
420481
Holding register assignment 2 422528
QJ71MB91
422529
user free area (5000 to 5FFF)
L
8192 (0 to 8191)
4096
Holding register assignment 3
Coil assignment 4 030720
030721
426624
(Empty)
430721
B
8192(0 to 1FFF)
Coil assignment 5
2048 (0 to F2047)
Coil assignment 6
SB
2048(0 to 7FF)
Coil assignment 7
2048(0 to V
2047)
Coil assignment 8
W
8192 (0 to 1FFF)
038912
038913
040960
040961
(Empty)
Holding register assignment 4
(Empty)
043008
043009
2048
045056
045057
440961
443008
(Empty)
Coil assignment 9
TC
(0 to 2047)
Coil assignment 10
TS
2048
(0 to 2047)
Coil assignment 11
2048 (0 toSC
2047)
Coil assignment 12
SS
2048(0 to 2047)
Coil assignment 13
CC
2048 (0 to 2047)
Coil assignment 14
CS
2048 (0 to 2047)
Coil assignment 15
053248
053249
2048
055296
055297
TN
(0 to 2047)
Holding register assignment 6
453249
455296
(Empty)
057344
057345
SN
2048 (0 to 2047)
059392
059393
Holding register assignment 7
CN
2048 (0 to 2047)
459392
461441
Holding register assignment 8 463488
063488
063489
065536
457345
(Empty)
061440
061441
165536
365536
Figure 7.8 Default assignment parameters
7 - 19
SW
(0 to 7FF)
Holding register assignment 5
S
8192(0 to 1FFF)
2048
438912
(Empty)
7.3 MODBUS(R) Device Assignment Parameter
7.3.1 MODBUS(R) device assignment to the PLC CPU device memory
(Empty)
465536
7
PARAMETER SETTING
1
(c) Setting values for default assignment parameters
OVERVIEW
Table7.8 Setting values for default assignment parameters
Coil assignment 6
Coil assignment 7
Coil assignment 8
Coil assignment 9
Coil assignment 10
Coil assignment 11
Coil assignment 12
Coil assignment 13
Coil assignment 14
Coil assignment 15
Coil assignment 16
(2305 to 2311)
0908H to 090BH
(2312 to 2315)
090CH to 090FH
(2316 to 2319)
0910H to 0913H
(2320 to 2323)
0914H to 0917H
(2324 to 2327)
0918H to 091BH
(2328 to 2331)
091CH to 091FH
(2332 to 2335)
0920H to 0923H
(2336 to 2339)
0924H to 0927H
(2340 to 2343)
0928H to 092BH
(2344 to 2347)
092CH to 092FH
(2348 to 2351)
0930H to 0933H
(2352 to 2355)
0934H to 0937H
(2356 to 2359)
0938H to 093BH
(2360 to 2363)
093CH to 093FH
(2364 to 2367)
Device numbers
device number*1
points
009DH
(Y)
0000H
0
8192
0090H
(M)
0000H
8192
8192
0091H
(SM)
0000H
20480
2048
0092H
(L)
0000H
22528
8192
00A0H
(B)
0000H
30720
8192
2
3
4
0093H
(F)
0000H
38912
2048
00A1H
(SB)
0000H
40960
2048
0094H
(V)
0000H
43008
2048
0098H
(S)
0000H
45056
8192
00C0H
(TC)
0000H
53248
2048
00C1H
(TS)
0000H
55296
2048
00C6H
(SC)
0000H
57344
2048
00C7H
(SS)
0000H
59392
2048
00C3H
(CC)
0000H
61440
2048
00C4H
(CS)
0000H
63488
2048
0000H
-
0000H
0
0
* 1 Use the following expression to find a setting value of the head MODBUS
Head MODBUS
Assignment
MODBUS
SPECIFICATIONS
Coil assignment 5
0904H to 0907H
(Device symbol)
device number = Last 5 digits of relevant MODBUS
device number:
device number - 1
(Continued on next page)
7.3 MODBUS(R) Device Assignment Parameter
7.3.1 MODBUS(R) device assignment to the PLC CPU device memory
7 - 20
MODBUS(R) STANDARD
FUNCTIONS
Coil assignment 4
(2304 to 2307)
Head
5
FUNCTION
Coil assignment 3
0900H to 0903H
Head
Device code
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Coil assignment 2
address
7
PARAMETER SETTING
Coil assignment 1
Buffer memory
8
UTILITY PACKAGE
(GX Configurator-MB)
Name
SYSTEM
CONFIGURATION
Default assignment parameter setting items
7
PARAMETER SETTING
Table7.8 Setting values for default assignment parameters (Continued)
Default Assignment Parameter Setting Items
Buffer memory
Name
Address
0940H to 0943H
Input assignment 1
(2368 to 2371)
Input assignment 2 to 16
0944H to 097FH
(2372 to 2431)
Input register assignment
0980H to 09BFH
1 to 16
(2432 to 2495)
Holding register
assignment 1
Holding register
assignment 2
Holding register
assignment 3
Holding register
assignment 4
Holding register
assignment 5
Holding register
assignment 6
Holding register
assignment 7
Holding register
assignment 8
Holding register
assignment 9 to 16
09C0H to 09C3H
(2496 to 2499)
09C4H to 09C7H
(2500 to 2503)
09C8H to 09CBH
(2504 to 2507)
09CCH to 09CFH
(2508 to 2511)
09D0H to 09D3H
(2512 to 2515)
09D4H to 09D7H
(2516 to 2519)
09D8H to 09DBH
(2520 to 2523)
09DCH to 09DFH
(2524 to 2527)
09E0H to 09FFH
(2528 to 2559)
Head
Device code
Head
(Device symbol)
Device numbers
device number*1
7 - 21
points
009CH
(X)
0000H
0
8192
0000H
-
0000H
0
0
0000H
-
0000H
0
0
00A8H
(D)
0000H
0
12288
00A9H
(SD)
0000H
20480
2048
F000H
-
5000H
22528
4096
00B4H
(W)
0000H
30720
8192
00B5H
(SW)
0000H
40960
2048
00C2H
(TN)
0000H
53248
2048
00C8H
(SN)
0000H
57344
2048
00C5H
(CN)
0000H
61440
2048
0000H
-
0000H
0
0
* 1 Use the following expression to find a setting value of the head MODBUS
Head MODBUS
Assignment
MODBUS
device number = Last 5 digits of relevant MODBUS
7.3 MODBUS(R) Device Assignment Parameter
7.3.1 MODBUS(R) device assignment to the PLC CPU device memory
device number:
device number - 1
PARAMETER SETTING
1
(
QCPU User's Manual (Function Explanation, Program Fundamentals))
Depending on the PLC CPU, some of the default assignment parameter range
may not be usable.
In such a case, observe either of the following not to access the devices outside
the allowable range.
3
SPECIFICATIONS
• Set the MODBUS device assignment parameters.(
This section
(2))
Make the setting within the allowable PLC CPU device range.
• Do not access any device outside the allowable range when using the
default assignment parameters.
2
SYSTEM
CONFIGURATION
The PLC CPU device range varies depending on the PLC CPU.
OVERVIEW
POINT
MODBUS(R) STANDARD
FUNCTIONS
4
FUNCTION
5
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
7
7.3 MODBUS(R) Device Assignment Parameter
7.3.1 MODBUS(R) device assignment to the PLC CPU device memory
7 - 22
7
PARAMETER SETTING
7.3.2 MODBUS(R) extended file register assignment to the PLC CPU file
register
The MODBUS extended file register assignment to the PLC CPU is fixed to the file
register (ZR).
It is assigned to the file register (ZR) of the PLC CPU as shown below.
PLC CPU
file register (ZR)
R
MODBUS
extended file register
600000
ZR0
10000 File number 0
609999
600000
ZR9999
ZR10000
10000 File number 1
609999
600000
ZR19999
ZR20000
10000 File number 2
609999
ZR29999
ZR30000
ZR1039999
ZR1040000
600000
2432 File number 104
602431
ZR1042431
Figure 7.9 Extended file register assignment
(1) Out-of-range read/write request
The QJ71MB91 sends an exception response if the master requests it to read from or
write to a nonexistent file register (ZR) of the PLC CPU on the station where the
QJ71MB91 is mounted.
(2) MODBUS
extended file register size
The MODBUS extended file register size is dependant on the file register (ZR) size
set to the PLC CPU on the QJ71MB91-mounted station.
POINT
Even if the slave (QJ71MB91) receives Write File Record (FC:21) when the PLC
CPU’s file register (ZR) is read-only (for example, when stored on a Flash card), it
will issue a normal response.
In this case, however, the action for Write File Record is not performed.
To write to the extended file register, check that the PLC CPU's file register (ZR) is
writable or not in advance.
Remark
For the PLC CPU's file register (ZR), refer to the following manual:
QCPU User's Manual (Function Explanation, Program Fundamentals)
7 - 23
7.3 MODBUS(R) Device Assignment Parameter
7.3.2 MODBUS(R) extended file register assignment to the PLC CPU file register
PARAMETER SETTING
1
The QJ71MB91 can assign the MODBUS devices to the QJ71MB91 buffer memory.
By this assignment of the QJ71MB91 buffer memory to the MODBUS device, access to
the MODBUS devices will not be affected by sequence scans.
This allows the QJ71MB91 to respond faster to the master.
device assignment parameter
When setting the MODBUS
device code.(
device
device assignment parameter, set F000H for the
SYSTEM
CONFIGURATION
2
(1) To assign the QJ71MB91 buffer memory to the MODBUS
(a) When using the MODBUS
OVERVIEW
7.3.3 QJ71MB91 buffer memory assignment
3
Section 7.3.1 (2))
(
device, 422529 to 426624.
Section 7.3.1 (3))
(2) Assignment range of MODBUS
devices
4
The following QJ71MB91 buffer memory addresses can be assigned to the
MODBUS
devices.
Table7.9 Usable buffer memory
Name
Automatic refresh
4096
User free area
Setting allowed
5
FUNCTION
5000H to 5FFFH
(20480 to 24575)
Size
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Address
7
PARAMETER SETTING
Buffer memory
MODBUS(R) STANDARD
FUNCTIONS
Use any of the MODBUS
SPECIFICATIONS
(b) When using the default assignment parameter
8
UTILITY PACKAGE
(GX Configurator-MB)
7
7.3 MODBUS(R) Device Assignment Parameter
7.3.3 QJ71MB91 buffer memory assignment
7 - 24
7
PARAMETER SETTING
PLC CPU
MODBUS R
Master device
QJ71MB91 (Slave function)
No sequence
program required
R
MODBUS device assignment parameter
Device memory
Auto refresh
D300
1234H
MODBUS R device
Buffer memory
2)
User free area
400499
1)
400500
Request message (Read request for holding register 400500)
400501
3)
Create response
message to master
Response message (Holding register 400500 = 1234H)
RS-232, RS-422 or RS-485
Figure 7.10 MODBUS device and buffer memory
1) The QJ71MB91 receives a "Read holding register 400500" request message
from the master.
2) The QJ71MB91 reads the data from its own buffer memory according to the
value set to the MODBUS device assignment parameter.
At this time, faster processing is executed since access is not affected by any
sequence scan.
3) The QJ71MB91 creates a response message and sends it to the master.
POINT
The PLC CPU device memory value can be stored in the QJ71MB91 buffer
memory, and the QJ71MB91 buffer memory value can be stored in the PLC CPU
device memory.
Data can be stored by either of the following:
• Automatic refresh setting on GX Configurator-MB (
Section 8.5)
• Transfer using intelligent function module devices (Un\G )
(
QCPU User’s Manual (Function Explanation, Program Fundamentals))
7 - 25
7.3 MODBUS(R) Device Assignment Parameter
7.3.3 QJ71MB91 buffer memory assignment
7
PARAMETER SETTING
1
Users can specify the data to be read out as an exception status when the QJ71MB91
(slave) receives Read Exception Status (FC:07) from the master.
PLC CPU
MODBUS R
Master device
QJ71MB91 (Slave function)
No sequence
program required
2
Device memory
Request message
(Sends Read Exception Status (FC:07))
01H
M100 to M107
Exception status
Receives response message (exception
status 01H)
3
SPECIFICATIONS
M100
to
M107
SYSTEM
CONFIGURATION
Error status read device specification
Device
OVERVIEW
7.3.4 Specifying the error status read device
MODBUS(R) STANDARD
FUNCTIONS
4
RS-232, RS-422 or RS-485
Figure 7.11 Relations between error status and error status read device
(1) To specify the error status read device
Specify a read target device to the addresses shown below.
The 8 points from the specified bit device is regarded as a error status read device.
5
Address
Parameter name
000AH
Setting range
Device code
(10)
0000H : Device code not assigned
Other than 0000H: Device code
Default
F000H
6
Error status read device specification
0000H
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
0000H to FFFFH
7
PARAMETER SETTING
(11)
Head device number
8
UTILITY PACKAGE
(GX Configurator-MB)
000BH
FUNCTION
Table7.10 Error status read device specification
7.3 MODBUS(R) Device Assignment Parameter
7.3.4 Specifying the error status read device
7 - 26
7
PARAMETER SETTING
(a) Device code
Set PLC CPU devices and QJ71MB91 buffer memory to be assigned to the
MODBUS devices.
The device codes usable for the error status read devices are indicated below.
Table7.11 Device codes usable for error status read devices
Classification
Internal system device
Device name
Device symbol
Device code
*3
SM *1
0091H
Input
X *1
009CH
Output
Y*1
009DH
Internal relay
M*1
0090H
Latch relay
L
0092H
Annunciator
F
0093H
Edge relay
V
0094H
Link relay
B*1*2
00A0H
Coil
TC
00C0H
Contact
TS
00C1H
Coil
SC
00C6H
Contact
SS
00C7H
Coil
CC
00C3H
Contact
CS
00C4H
SB*1
00A1H
S
0098H
Direct input
DX
00A2H
Direct output
DY
00A3H
-
F000H
Special relay
Internal user device
Timer
Retentive
timer
Counter
Special link relay
Step relay
Direct device
QJ71MB91 buffer memory
Error status read buffer
memory (address: 000FH)
* 1 When the access target is the MELSECNET/H remote I/O station to which the QJ71MB91 is
mounted, only this device is supported.
When a device other than the above is assigned, and if Read Exception Status (FC: 07) is sent
from the master, an error will be generated.(
Section 7.3.5)
* 2 Equivalent to LB of the MELSECNET/H remote I/O stations.
* 3 When setting with GX Configurator-MB, input the head device.
7 - 27
7.3 MODBUS(R) Device Assignment Parameter
7.3.4 Specifying the error status read device
PARAMETER SETTING
1
If F000H (buffer memory) is specified for the device code, the error status read
buffer memory (address: 000FH) will be the error status read target. (No other
buffer memory can be set.)
In this case, make the setting as indicated below.
• Set "0000H" to the head device number (address: 000BH).
• Store the error status data in the error status read buffer memory
(address: 000FH).
SYSTEM
CONFIGURATION
POINT
2
3
SPECIFICATIONS
to the MODBUS device.
The upper limit of the setting is the number resulted from "each device’s upper
limit minus 8 points".
OVERVIEW
(b) Head device number
Specify the head device number of the PLC CPU device memory to be assigned
MODBUS(R) STANDARD
FUNCTIONS
4
FUNCTION
5
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
7
7.3 MODBUS(R) Device Assignment Parameter
7.3.4 Specifying the error status read device
7 - 28
7
PARAMETER SETTING
7.3.5 Specifying access target when mounted to MELSECNET/H remote I/O
station
For the case where the QJ71MB91 is mounted to a MELSECNET/H remote I/O station,
the access target can be specified.
(1) To change the access target
Set the access target as shown below.
Table7.12 Access target when mounted to MELSECNET/H remote I/O station
Address
000EH
(14)
Parameter name
Setting range
Access target (when mounted to MELSECNET/H remote I/O
0000H: Remote I/O station
station)
0001H: Remote master station
Default
0000H
(a) When the access target is a remote I/O station ("0000H" is set.)
When the QJ71MB91 receives a request message from the master, the
MELSECNET/H remote I/O station device is accessed.
(b) When the access target is a remote master station ("0001H" is set.)
When the QJ71MB91 receives a request message from the master, a control CPU
device of the MELSECNET/H remote master station is accessed.
If the QJ71MB91 is not mounted on the MELSECNET/H remote I/O station, do not
make this setting. (An error will occur.)
7 - 29
7.3 MODBUS(R) Device Assignment Parameter
7.3.5 Specifying access target when mounted to MELSECNET/H remote I/O station
PARAMETER SETTING
1
Start
Reset
3
SPECIFICATIONS
2)
Exception message
1)
Request message
Normal response
message
Master device
QJ71MB91
CPU response
monitoring timer
3)
Start
2
SYSTEM
CONFIGURATION
When the QJ71MB91 receives a request message from the master and the PLC CPU
starts its processing, the QJ71MB91 waits for the response from the PLC CPU. The time
allowed for the QJ71MB91 to wait is set by the CPU response monitoring timer value.
This timer allows the QJ71MB91 to cancel the wait status on the master side when a
response to the master is not available due to an error occurred in the PLC CPU.
OVERVIEW
7.3.6 Specifying the CPU response monitoring timer
Request message
Timeout
Error occurring
Figure 7.12 CPU response monitoring timer operation
(1) CPU response monitoring timer processing
(a) Start of the CPU response monitor timer
The QJ71MB91 starts the CPU response monitoring timer when it receives a
request message from the master. (1) in Figure)
The CPU response monitoring timer monitors the PLC CPU processing until the
QJ71MB91 starts sending a response message to the master. (2) in Figure)
(b) If the CPU response monitoring timer has timed out.
When the CPU response monitoring timer has timed out, the QJ71MB91 performs
the following processes. (In figure 3))
1) Issues error code: 7380H.(
Section 11.4.3)
2) Issues the exception code: 04H to the master side.(
Section 11.4.2)
FUNCTION
5
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Processing
7
PARAMETER SETTING
PLC CPU
MODBUS(R) STANDARD
FUNCTIONS
4
8
UTILITY PACKAGE
(GX Configurator-MB)
7
7.3 MODBUS(R) Device Assignment Parameter
7.3.6 Specifying the CPU response monitoring timer
7 - 30
7
PARAMETER SETTING
(2) To set the CPU response monitoring timer value
Set a CPU response monitoring timer value as specified below.
Table7.13 CPU response monitor timer setting
Address
000DH
(13)
Parameter name
Setting range
0
CPU response monitoring timer value
: Limitless wait
1 to 2400 : CPU response monitoring timer value
(Set time = set value x 500ms)
Default
10
(5s)
POINT
When the CPU response monitoring timer value is "0", the QJ71MB91 waits until
the PLC CPU completes its processing. (Limitless wait)
7 - 31
7.3 MODBUS(R) Device Assignment Parameter
7.3.6 Specifying the CPU response monitoring timer
8
UTILITY PACKAGE (GX Configurator-MB)
1
GX Configurator-MB is a tool designed to support parameter setting, auto refresh, and
monitor/test of the QJ71MB91.
Refer to the following for parameter setting or auto-refresh setting with a sequence
program.
2
SYSTEM
CONFIGURATION
CHAPTER 9
OVERVIEW
CHAPTER8 UTILITY PACKAGE (GX Configurator-MB)
8.1 GX Configurator-MB Functions
3
The following table lists the GX Configurator-MB functions.
Description
Reference
Set the following items that require initial setting.
• Automatic communication parameter
Initial setting
• MODBUS
device assignment parameter
Section 8.4
The initially set data are registered as PLC CPU parameters, and are automatically written
to the QJ71MB91 when the PLC CPU enters RUN status.
Set the QJ71MB91 buffer memory areas to be refreshed automatically.
• Automatic communication function buffer input area
• Automatic communication function buffer output area
Auto refresh setting
• Automatic communication operation status storage area
Section 8.5
• User free area (input/output)
4
MODBUS(R) STANDARD
FUNCTIONS
Item
SPECIFICATIONS
Table8.1 GX Configurator-MB function list
5
The QJ71MB91 buffer memory area data set for auto refresh are automatically read from
or written to the specified devices when the END instruction of the PLC CPU is executed.
FUNCTION
Monitor/test the buffer memory and/or I/O signals of the QJ71MB91.
• Operation mode setting status
• Transmission setting status
• Station No. setting status
• Various module statuses
• X/Y Monitor/test
• MODBUS
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Section 8.6
device assignment parameter status
• Automatic communication status
• Error log
• Communication status
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
Monitor/test
8.1 GX Configurator-MB Functions
8-1
8
UTILITY PACKAGE (GX Configurator-MB)
8.2 Installing or Uninstalling GX Configurator-MB
Refer to the GX Developer Operating Manual (Startup) for details about installing and
uninstalling GX Configurator-MB.
8.2.1 Precautions for use
This section explains the precautions for use of GX Configurator-MB.
(1) For safety
Since GX Configurator-MB is add-on software for use with GX Developer, read and
understand the basic operating instructions and safety precautions given in the GX
Developer Operating Manual.
(2) Installation
GX Configurator-MB is added on and started with GX Developer Version 4 or later.
Install GX Configurator-MB into a personal computer that already has GX Developer
Version 4 or later installed.
(3) On-screen display errors during use of GX Configurator-MB
Due to insufficient system resources, a normal screen may not be displayed when GX
Configurator-MB is used.
In this case, close GX Configurator-MB first, and then GX Developer (programs,
comments, etc.) and any other applications, and restart GX Developer and GX
Configurator-MB in this order.
(4) Starting GX Configurator-MB
(a) PLC series set on GX Developer
On GX Developer, select "QCPU (Q mode)" for the PLC series and set a project.
If any other than "QCPU (Q mode)" is selected for the PLC series, or if no project
is set, GX Configurator-MB will not start.
(b) Activating multiple sets of utility software
Multiple sets of utility software can be activated concurrently.
Note that, however, [Open parameter]/[Save parameter] for the intelligent function
module parameters can be used on only one of them.
For other utilities, only the [Monitor/Test] operations are allowed.
8-2
8.2 Installing or Uninstalling GX Configurator-MB
8.2.1 Precautions for use
UTILITY PACKAGE (GX Configurator-MB)
1
When multiple utility software screens cannot be displayed on the same screen, use
the task bar to bring a desired screen to the front-most.
OVERVIEW
(5) Screen switching between utilities
2
For PLC CPUs and MELSECNET/H remote I/O stations in MELSECNET/H network
systems, there are restrictions on the number of intelligent function module
parameters that can be set by GX Configurator.
Table8.2 Maximum number of parameter settings
Initial setting
Auto refresh setting
Q00J/Q00/Q01CPU
512
256
Q02/Q02H/Q06H/Q12H/Q25HCPU
512
256
Q12PH/Q25PHCPU
512
256
MELSECNET/H remote I/O station
512
256
4
For example, if multiple intelligent function modules are installed on a MELSECNET/H
remote I/O station, make GX Configurator-MB settings carefully so that the number of
parameters set for all the intelligent function modules will not exceed the maximum
allowed for the MELSECNET/H remote I/O station.
Calculate the total number of parameter settings separately for each of the initial
setting and the auto refresh setting.
The number of parameters that can be set for one module on GX Configurator-MB is
as shown below.
Table8.3 Number of parameters that can be set per module
QJ71MB91
5
6
Initial setting
Auto refresh setting
3 (Fixed)
8(Maximum)
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Target module
MODBUS(R) STANDARD
FUNCTIONS
function module
Maximum number of parameter settings
FUNCTION
Installation target of intelligent
3
SPECIFICATIONS
(6) Number of parameters set on GX Configurator-MB
SYSTEM
CONFIGURATION
Figure 8.1 Task bar when more than one utility is running
Example) Counting the number of parameters for the auto refresh setting
PARAMETER SETTING
7
This single line is counted as one
setting.
Blank fields are not counted.
All setting items in this setting
screen are added up, and totaled
with number of the other intelligent
function modules.
8
UTILITY PACKAGE
(GX Configurator-MB)
8
Figure 8.2 How to count auto refresh settings
8.2 Installing or Uninstalling GX Configurator-MB
8.2.1 Precautions for use
8-3
8
UTILITY PACKAGE (GX Configurator-MB)
8.2.2 Operating environment
This section explains the operating environment for the personal computer where GX
Configurator-MB is used.
Table8.4 Operating environment
Item
Peripheral devices
Installation (Add-in) destination*1
Add-in to GX Developer Version 4 (English version) or later.*2
Computer
PC running Microsoft
CPU
Windows
Operating System.
Refer to the following table "Available operating systems and performance required for the personal
Required memory computer".
Free hard disk
space
For installation
65MB or more
For operation
10MB or more
Display
Resolution: 800
Microsoft
Operating system
600 pixels or greater
Windows
95 Operating System (English version)
Microsoft
Windows
98 Operating System (English version)
Microsoft
Windows
Millennium Edition Operating System (English version)
Microsoft
Windows NT
Microsoft
Windows
Workstation Operating System Version 4.0 (English version)
2000 Professional Operating System (English version)
Microsoft
Windows
XP Professional Operating System (English version)
Microsoft
Windows
XP Home Edition Operating System (English version)
* 1 Install GX Configurator-MB in GX Developer Version 4 or later in the same language.
Combinations of GX Developer and GX Configurator-MB in versions of different languages are not
allowed.
* 2 GX Configurator-MB is not used with GX Developer Version 3 or earlier versions.
Table8.5 Available operating systems and performance required for the personal computer
Performance required for personal computer
Operating system
CPU
Required memory
Windows
95 (Service Pack 1 or higher)
Pentium
133 MHz or faster
32MB or more
Windows
98
Pentium
133 MHz or faster
32MB or more
Windows
Me
Pentium
150 MHz or faster
32MB or more
Pentium
133 MHz or faster
32MB or more
Windows NT
Workstation 4.0 (Service Pack 3 or higher)
Windows
2000 Professional
Pentium
133 MHz or faster
64MB or more
Windows
XP Professional
Pentium
300 MHz or faster
128MB or more
Windows
XP Home Edition
Pentium
300 MHz or faster
128MB or more
8-4
8.2 Installing or Uninstalling GX Configurator-MB
8.2.2 Operating environment
UTILITY PACKAGE (GX Configurator-MB)
1
New functions of Windows XP
When Microsoft Windows XP Professional Operating System or Microsoft
Windows XP Home Edition Operating System is used, the following new
functions cannot be used.
If any of the following new functions is used, this product may not operate
normally.
SYSTEM
CONFIGURATION
2
Start of application in Windows compatible mode of earlier version
Fast user switching
Remote desktop
Big fonts (Details setting of Screen properties)
SPECIFICATIONS
3
MODBUS(R) STANDARD
FUNCTIONS
4
FUNCTION
5
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
7
PARAMETER SETTING
•
•
•
•
OVERVIEW
POINT
8
UTILITY PACKAGE
(GX Configurator-MB)
8
8.2 Installing or Uninstalling GX Configurator-MB
8.2.2 Operating environment
8-5
8
UTILITY PACKAGE (GX Configurator-MB)
8.3 GX-Configurator-MB Operations
8.3.1 Common operations of GX Configurator-MB
(1) Usable control keys
The following table shows the special keys used for GX Configurator-MB operations
and their applications.
Table8.6 List of control keys used for GX Configurator-MB
Key name
Application
Cancels a value currently entered in a cell.
Esc
Tab
Closes the window.
Moves from a control space to another within a window.
Used in combination with the mouse to make multiple cell
Ctrl
selections in test selection.
Deletes characters from the cursor position.
Delete
Back
Space
When a cell is selected, clears all the setting in the cell.
Deletes characters from the cursor position.
Moves the cursor.
8-6
Page
Up
Moves the cursor 1 page up.
Page
Down
Moves the cursor 1 page down.
Enter
Accepts a value entered in a cell.
8.3 GX-Configurator-MB Operations
8.3.1 Common operations of GX Configurator-MB
UTILITY PACKAGE (GX Configurator-MB)
1
(a) Intelligent function module parameters
Initial settings and auto refresh settings are saved in an intelligent function module
parameter file in a project created with GX Developer.
Project
Program
Parameter
2
SYSTEM
CONFIGURATION
The following data or files created with GX Configurator-MB can also be used for GX
Developer operations.
How to handle the data/files in which operation is shown below.
OVERVIEW
(2) Creating data with GX Configurator-MB
3
PLC parameter
SPECIFICATIONS
Network parameter
Figure 8.3 Data configuration on GX Configurator-MB
(b) Text file
A text file is created using
operation on the initial setting,
Make text file
auto refresh setting or monitor/test screen.
This file can be utilized to create user documents.
Disk
Project
Project
5
1)
A
2)
A
Personal computer
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
B
PLC CPU
FUNCTION
GX Developer/
GX Configurator-MB
4
MODBUS(R) STANDARD
FUNCTIONS
Intelligent function module parameter
3)
7
PARAMETER SETTING
A: Intelligent function module parameters.
B: Data stored after Make text file operation.
A
8
UTILITY PACKAGE
(GX Configurator-MB)
8
Figure 8.4 Flow of GX Configurator-MB data
8.3 GX-Configurator-MB Operations
8.3.1 Common operations of GX Configurator-MB
8-7
8
UTILITY PACKAGE (GX Configurator-MB)
Steps 1 to 3 in the figure are performed as shown below.
1) From GX Developer:
[Project]
[Open project]/[Save project]/[Save as]
2) From the parameter setting module selection screen of GX Configurator-MB.
[Intelligent function module parameter]
parameter]
[Open parameter]
[Save
3) From GX Developer:
[Online]
[Read from PLC]/[Write to PLC]
"Parameter" "Intelligent
module parameter"
The operation is also available from GX Configurator-MB's parameter setting
module selection screen.
[Online]
8-8
[Read from PLC]/[Write to PLC]
8.3 GX-Configurator-MB Operations
8.3.1 Common operations of GX Configurator-MB
8
UTILITY PACKAGE (GX Configurator-MB)
1
OVERVIEW
8.3.2 Operation outline
GX Developer screen
SYSTEM
CONFIGURATION
2
3
SPECIFICATIONS
[Tools] - [Intelligent function utility] - [Start]
Intelligent function module parameter
setting module select screen
MODBUS(R) STANDARD
FUNCTIONS
4
5
Section 8.3.3
Initial setting
Auto refresh
6
Auto refresh setting screen
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Initial setting screen
FUNCTION
Enter "Start I/O No." and select "Module type"
and "Module model name".
PARAMETER SETTING
7
Section 8.4
UTILITY PACKAGE
(GX Configurator-MB)
8
Section 8.5
Figure 8.5 GX Configurator-MB operation outline
8.3 GX-Configurator-MB Operations
8.3.2 Operation outline
8-9
8
UTILITY PACKAGE (GX Configurator-MB)
1)
[Online] - [Monitor/Test]
Select monitor/test module screen
Select the module to be monitored/tested.
Monitor/Test screen
Section 8.6
Figure 8.5 GX Configurator-MB operation outline (Continued)
8 - 10
8.3 GX-Configurator-MB Operations
8.3.2 Operation outline
UTILITY PACKAGE (GX Configurator-MB)
1
[Starting Procedure]
[Tools]
[Intelligent function utility]
2
SYSTEM
CONFIGURATION
[Setting Purpose]
Start Intelligent function utility from GX Developer, and display the intelligent function
module parameter setting module select screen.
From this screen, screens for the initial setting, auto refresh setting and monitor/test
module selection (selection of the module to be monitored/tested) can be activated.
OVERVIEW
8.3.3 Starting Intelligent function utility
[Start]
3
SPECIFICATIONS
[Setting Screen]
MODBUS(R) STANDARD
FUNCTIONS
4
FUNCTION
5
Figure 8.6 Intelligent function module utility
(1) Starting each screen
(a) Starting the initial setting screen
"Module type"
"Module model name"
Initial setting
7
(b) Starting auto refresh setting screen
"Start I/O No.
*1
"
"Module type"
"Module model name"
Auto refresh
(c) Monitor/Test module selection screen
[Online]
[Monitor/Test]
* 1 Enter the start I/O No. in hexadecimal.
8
(2) Explanation of screen command buttons
Delete
Exit
Deletes the initial setting or auto refresh setting of the module selected in
the intelligent function module parameter setting area.
Exits the Intelligent function module utility.
8.3 GX-Configurator-MB Operations
8.3.3 Starting Intelligent function utility
PARAMETER SETTING
"Start I/O No. *1"
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
[Explanation]
8 - 11
UTILITY PACKAGE
(GX Configurator-MB)
8
8
UTILITY PACKAGE (GX Configurator-MB)
(a) File items
File operations are executed for the intelligent function module parameters of the
project opened by GX Developer.
[Open parameter] : Reads a parameter file.
[Close parameter] : Closes the parameter file.
When any corrections have been made, a dialog is
displayed, asking whether or not to save the corrections in
the file.
[Save parameter] : Saves the parameter file.
[Delete parameter] : Deletes the parameter file.
[Exit]
: Closes the parameter setting module selection screen.
(b) Online items
8 - 12
[Monitor/Test]
: Activates the monitor/test module selection screen.
[Read from PLC]
: Reads the intelligent function module parameters from a PLC
CPU.
[Write to PLC]
: Writes the intelligent function module parameters to a PLC
CPU.
8.3 GX-Configurator-MB Operations
8.3.3 Starting Intelligent function utility
UTILITY PACKAGE (GX Configurator-MB)
1
• Set the target PLC CPU by choosing [Online]
[Transfer Setup] on GX
Developer.
In the case of the multiple CPU system, the intelligent function module
parameters must be written only to the control CPU of the QJ71MB91.
• When the QJ71MB91 is mounted on a MELSECNET/H remote I/O
station, read from PLC read or write to PLC must be performed from GX
Developer.
4
5
FUNCTION
Confirmation of required utility
On the intelligent function module utility setting screen, the start I/O may be
displayed with the model name shown as "*".
This indicates that the required utility has not been installed or the installed
utility cannot be started from GX Developer.
By choosing [Tools] - [Intelligent function utility] - [Utility list...] on GX
Developer, check the required utility.
3
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
7
PARAMETER SETTING
3.
SYSTEM
CONFIGURATION
Reading and writing the intelligent function module parameters from and to a
PLC using GX Developer
• After the intelligent function module parameters have been saved into a
file, read from PLC and write to PLC are enabled.
2
SPECIFICATIONS
2.
Saving the intelligent function module parameters into a file
Since the intelligent function module parameters cannot be saved into a file
by the project saving operation of GX Developer, save them into a file on the
parameter setting module selection screen.
MODBUS(R) STANDARD
FUNCTIONS
1.
OVERVIEW
POINT
8
UTILITY PACKAGE
(GX Configurator-MB)
8
8.3 GX-Configurator-MB Operations
8.3.3 Starting Intelligent function utility
8 - 13
8
UTILITY PACKAGE (GX Configurator-MB)
8.4 Initial Setting
[Setting Purpose]
Set parameters on the initial setting screen.
This setting eliminates the need for parameter setting by sequence programs.
The initial setting are as follows:
• Automatic communication parameter
• MODBUS
device assignment parameter
[Starting Procedure]
"Start I/O No. "
"Module type"
"Module model name"
Initial setting
[Setting Screen]
Figure 8.7 Initial setting screen
[Explanation]
(1) Parameter settings
Select a button under the Setting value, and set parameters on the corresponding
screen.
• Automatic communication parameter (
• MODBUS
Section 8.4.1)
device assignment parameter (
Section 8.4.2)
(2) Command buttons
Make text file
End setup
Cancel
8 - 14
8.4 Initial Setting
Creates a file of screen data in the text file format.
Accepts the set values and ends the setting.
Discards the set values and ends the setting.
UTILITY PACKAGE (GX Configurator-MB)
1
4.
If the initial setting data are written using a sequence program, the initial
setting values are written when the PLC CPU is changed from STOP to RUN
status. Therefore, perform programming so that the initial setting will be reexecuted with the sequence program.
The parameter setting by sequence program has priority over the parameter
setting by the initial setting when both of them are used.
SYSTEM
CONFIGURATION
4
5
FUNCTION
3.
device assignment parameter
SPECIFICATIONS
manipulate Y signals until the MODBUS
setting existence (XA) turns ON.
3
MODBUS(R) STANDARD
FUNCTIONS
If the initial settings become effective, the MODBUS device assignment
parameter setting existence (XA) turns ON.
Do not write any data to the buffer memory by sequence programs or
2
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
2.
The initial settings are stored as the intelligent function module parameters.
After the intelligent function module parameters have been written to the PLC
CPU, the initial setting is updated when the PLC is powered ON from OFF or
the PLC CPU is reset (with the PLC CPU's RUN/STOP switch set to RUN).
If the QJ71MB91 is mounted on a MELSECNET/H remote I/O station, the
initial settings become effective when the remote I/O station receives the
information notifying the status change (from STOP to RUN) of the remote
master station's PLC CPU.
7
PARAMETER SETTING
1.
OVERVIEW
POINT
8
UTILITY PACKAGE
(GX Configurator-MB)
8
8.4 Initial Setting
8 - 15
8
UTILITY PACKAGE (GX Configurator-MB)
8.4.1 Automatic communication parameter
[Setting Purpose]
Set the automatic communication parameters on the Automatic communication
parameter screen.
[Starting Procedure]
Initial setting screen
Automatic communication
[Setting Screen]
Figure 8.8 Automatic communication parameter setting screen
8 - 16
8.4 Initial Setting
8.4.1 Automatic communication parameter
8
UTILITY PACKAGE (GX Configurator-MB)
[Setting Item]
For the automatic communication parameter setting, set a value in proper data format
or within the setting range for each item in the Setting value column, and click the
End setup button to save all the set values.
Table8.7 Setting items on Automatic communication parameter setting screen
2
Buffer memory address
Setting parameter existence
CH2
0200H to
0380H to
0201H
0381H
(512 to 513)
(896 to 897)
Target station No.
0202H (514)
0382H (898)
Request interval timer value
0203H (515)
0383H (899)
Response monitoring timer value/Broadcast delay value
0204H (516)
0384H (900)
Type specification of the target MODBUS(R) device
0205H (517)
0385H (901)
Head buffer memory address
0206H (518)
0386H (902)
Target MODBUS(R) device head number
0207H (519)
0387H (903)
Access points
0208H (520)
0388H (904)
Head buffer memory address
0209H (521)
0389H (905)
Target MODBUS(R) device head number
020AH(522)
038AH(906)
Access points
020BH(523)
038BH(907)
3
communication
Automatic
communication
parameter 2 to
(Same as in automatic communication parameter 1)
32
020CH to
038CH to
037FH
04FFH(908 to
(524 to 895)
1279)
MODBUS(R) STANDARD
FUNCTIONS
4
5
FUNCTION
Write setting
Section 7.2
6
POINT
After the automatic communication parameters have been written to the PLC
CPU, the automatic communication function is operated when the PLC is
powered ON from OFF or the PLC CPU is reset (with the PLC CPU’s RUN/STOP
switch set to RUN).
7
PARAMETER SETTING
Read setting
8
UTILITY PACKAGE
(GX Configurator-MB)
parameter 1
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Automatic
CH1
SYSTEM
CONFIGURATION
Reference
SPECIFICATIONS
Setting item
OVERVIEW
1
8.4 Initial Setting
8.4.1 Automatic communication parameter
8 - 17
8
UTILITY PACKAGE (GX Configurator-MB)
8.4.2 MODBUS(R) device assignment parameter
[Setting Purpose]
Set the MODBUS device assignment parameters on the MODBUS(R) device
assignment parameter screen.
[Starting Procedure]
Initial settings screen
MODBUS (R) device assignment
[Setting Screen]
Figure 8.9 MODBUS(R) device assignment parameter setting screen
8 - 18
8.4 Initial Setting
8.4.2 MODBUS(R) device assignment parameter
8
UTILITY PACKAGE (GX Configurator-MB)
1
For the MODBUS device assignment parameter setting, set a value in proper data
format or within the setting range for each item in the Setting value column, and click
the End setup button to save all the set values.
Table8.8 Setting items on the MODBUS(R) device assignment parameter setting screen
Setting item
Buffer memory address
(2304 to 2305)
0902H
Head coil number
(2306)
0904H to 093FH
(Same as in coil assignment 1)
(2308 to 2367)
0940H to 0941H
Device
(2368 to 2369)
0943H
0944H to 097FH
(2372 to 2431)
0980H to 0981H
*1
16
(2434)
0983H
(2435)
(Same as in input register assignment 1)
6
0984H to 09BFH
(2436 to 2495)
09C0H to 09C1H
(2496 to 2497)
09C2H
Holding register assignment 1 Head holding register number
7
(2498)
09C3H
Assignment points
to 16
5
FUNCTION
0982H
Head input register number
Device *1
Holding register assignment 2
Section 7.3.3
(2432 to 2433)
Assignment points
Input register assignment 2 to
Section 7.3.1
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Input register assignment 1
(2371)
(Same as input assignment 1)
Device
MODBUS(R) STANDARD
FUNCTIONS
(2370)
Assignment points
Input assignment 2 to 16
4
0942H
Head input number
PARAMETER SETTING
Input assignment 1
SPECIFICATIONS
(2307)
(2499)
(Same as in holding register assignment 1)
09C4H to 09FFH
(2500 to 2559)
* 1 If the MODBUS device is an input register or holding register, QJ71MB91 buffer memory (user
free area: 5000H to 5FFFH) setting is also possible.
When setting the buffer memory, enter "H*".
For example, when setting buffer memory address 5500H, enter "H5500".
(Continued on next page)
8.4 Initial Setting
8.4.2 MODBUS(R) device assignment parameter
8 - 19
8
UTILITY PACKAGE
(GX Configurator-MB)
Coil assignment 2 to 16
3
0903H
Assignment points
2
SYSTEM
CONFIGURATION
0900H to 0901H
Device
Coil assignment 1
Reference
OVERVIEW
[Setting Item]
8
UTILITY PACKAGE (GX Configurator-MB)
Table8.8 Setting items on the MODBUS(R) device assignment parameter setting screen (Continued)
Setting item
Buffer memory address
Reference
000AH to 000BH
Error status read device *2
(10 to 11)
Section 7.3.4
000FH
Allocated error status area *3
(15)
Access target (when mounted to MELSECNET/H remote I/O station)
000EH
(14)
000DH
CPU response monitoring timer value
(13)
Section 7.3.5
Section 7.3.6
* 2 When setting the QJ71MB91 buffer memory, enter "H0".
(No other value can be set.)
At this time, set the value to be returned to the master in the case of Read Exception Status
(FC:07) into "Allocated error status area".
* 3 "Allocated error status area" is valid only when the QJ71MB91 buffer memory is specified as the
error status read device assignment target.(
8 - 20
8.4 Initial Setting
8.4.2 MODBUS(R) device assignment parameter
Section 7.3.4)
UTILITY PACKAGE (GX Configurator-MB)
1
[Setting Purpose]
Make this setting to store the QJ71MB91 buffer memory data into the specified
devices of the PLC CPU or to store the PLC CPU device data into the QJ71MB91
buffer memory automatically.
"Start I/O No."
"Module type"
"Module model name"
2
SYSTEM
CONFIGURATION
[Starting Procedure]
OVERVIEW
8.5 Auto Refresh Setting
Auto refresh
[Setting Screen]
SPECIFICATIONS
3
MODBUS(R) STANDARD
FUNCTIONS
4
5
FUNCTION
Figure 8.10 Auto refresh setting screen
[Explanation]
6
(a) Setting item
Table8.9 Setting items on the Auto refresh setting screen
Buffer memory address
Automatic communication function buffer input area
Reference
CH1
CH2
1000H to 1FFFH
2000H to 2FFFH
(4096 to 8191)
(8192 to 12287)
3000H to 3FFFH
4000H to 4FFFH
(12288 to 16383)
(16384 to 20479)
0C20H to 0C21H
0C22H to 0C23H
(3104 to 3105)
(3106 to 3107)
7
Section 5.2.1
Automatic communication function buffer output area
Automatic communication operation status (1 to 32)
User free area (input/output)
5000H to 5FFFH
(20480 to 24575)
8.5 Auto Refresh Setting
Section 11.4.1 (5)
Section 7.3.3
8 - 21
PARAMETER SETTING
Setting item
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
(1) Display data
8
UTILITY PACKAGE
(GX Configurator-MB)
8
8
UTILITY PACKAGE (GX Configurator-MB)
(b) Display items
1) Module side buffer size
Displays the buffer memory size available for the setting item.
2) Module side transfer word count
Displays the number of words to be transferred.
3) Module side buffer offset
Displays the offset value of the buffer memory data to be transferred.
4) Transfer direction
"<-" indicates that data are written from the device to the buffer memory.
"->" indicates that data are read from the buffer memory to the device.
5) PLC side device
Enter PLC CPU side devices to be refreshed automatically.
Available devices are X, Y, M, L, B, T, C, ST, D, W, R and ZR.
When using the bit devices such as X, Y, M, L or B, set a number divisible by
16 (e.g. X10, Y120, M16).
Buffer memory data are stored into the devices of 16 points, starting from the
set device number.
For example, when X10 is set, data are stored into X10 to X1F.
The devices available for MELSECNET/H remote I/O modules are X, Y, M, B,
D and W.
(2) Command buttons
Make text file
End setup
Cancel
Creates a file of screen data in the text file format.
Accepts the set values and ends the setting.
Discards the set values and ends the setting.
POINT
1.
2.
8 - 22
The auto refresh settings are stored as the intelligent function module
parameters.
After the intelligent function module parameters have been written to the PLC
CPU, the auto refresh setting is operated when the PLC is powered ON from
OFF or the PLC CPU is reset (with PLC CPU’s RUN/STOP switch set to
RUN).
The auto refresh setting cannot be changed from sequence programs.
However, processing equivalent to the auto refresh can be added by the
FROM/TO instruction of sequence programs.
8.5 Auto Refresh Setting
UTILITY PACKAGE (GX Configurator-MB)
1
[Starting Procedure]
"Start I/O No. *1"
"Module model name"
Monitor/Test
*1
3
Enter the start I/O No. in hexadecimal.
This screen can also be started from System monitor of GX Developer Version 6 or
later.
(
GX Developer Operating Manual)
[Monitor/Test Screen]
SPECIFICATIONS
Monitor/test module selection screen
2
SYSTEM
CONFIGURATION
[Monitor/Test Purpose]
From this screen, start the monitoring or test of the QJ71MB91 operating status, I/O
signals, parameter setting status, automatic communication status, error log or
communication status.
OVERVIEW
8.6 Monitor/Test
MODBUS(R) STANDARD
FUNCTIONS
4
FUNCTION
5
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
Figure 8.11 Monitor/test screen
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
8
8.6 Monitor/Test
8 - 23
8
UTILITY PACKAGE (GX Configurator-MB)
[Monitor/Test Items]
Table8.10 Setting items on the Monitor/test screen
Buffer memory address
Monitor/Test item
Operation mode setting status
Reference
CH1
CH2
0C00H
0C02H
(3072)
(3074)
0C01H
0C03H
(3073)
(3075)
Transmission setting status
MODBUS(R) device assignment parameter starting method
Data bit
Parity bit presence
Even/ odd parity
Section 6.6
Stop bit
Frame mode
Online change
Transmission speed
0C04H
Station No. setting status
(3076)
Module READY
-
Watch dog timer error
-
CH common/CH1 error
-
CH common/CH1 error clear request *1
-
CH2 error
-
CH 2 error clear request *1
-
X/Y Monitor/test *2
-
Section 8.6.1
MODBUS(R) device assignment parameter status *2
-
Section 8.6.2
Automatic communication status *2
-
Section 8.6.3
Error log *2
-
Section 8.6.4
Communication status *2
-
Section 8.6.5
Section 11.5
* 1 For the error clear request, select the corresponding request in the Setting value column.(
Section 11.5)
* 2 To move to each sub screen, click the button in the Setting value column.
8 - 24
8.6 Monitor/Test
UTILITY PACKAGE (GX Configurator-MB)
1
OVERVIEW
[Specifications common to Monitor and Test screens (including sub screens)]
The following explains the specifications common to respective screens.
Current value
: Monitors the current I/O signal statuses and current values of the
buffer memory areas.
Setting value
: Enter or select the data to be written by test operation.
(2) Command buttons
Current value display
Make text file
Displays the current value of the selected item. (This
feature is provided to verify the characters that cannot
be displayed in the Current value column, however, this
package has no such items.)
Creates a file of screen data in the text file format.
Selects whether to monitor the data in the current value
Start monitor / Stop monitor
column or not.
Tests the selected item.
Execute test
Multiple items can be selected by holding down the
Ctrl key.
Closes the currently open screen and returns to the
previous screen.
3
4
FUNCTION
5
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
7
PARAMETER SETTING
Close
2
SYSTEM
CONFIGURATION
: Displays the I/O signals and buffer memory area names.
SPECIFICATIONS
Setting item
MODBUS(R) STANDARD
FUNCTIONS
(1) Display data
8
UTILITY PACKAGE
(GX Configurator-MB)
8
8.6 Monitor/Test
8 - 25
8
UTILITY PACKAGE (GX Configurator-MB)
[Monitor/Test screen - Sub screen shift]
Section 8.6.2
MODBUS(R) device
1)
Automatic communication
X/Y Monitor/test
Section 8.6.1
Section 8.6.3
Figure 8.12 Move from the Monitor/test screen to sub screens
8 - 26
8.6 Monitor/Test
UTILITY PACKAGE (GX Configurator-MB)
OVERVIEW
1
SYSTEM
CONFIGURATION
2
SPECIFICATIONS
3
Section 8.6.4
Error log
1)
Communication
status
MODBUS(R) STANDARD
FUNCTIONS
4
FUNCTION
5
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
Section 8.6.5
Figure 8.12 Move from the Monitor/test screen to sub screens (Continued)
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
8
8.6 Monitor/Test
8 - 27
8
UTILITY PACKAGE (GX Configurator-MB)
8.6.1 X/Y Monitor/test
[Monitor/Test Purpose]
Monitor I/O signals and performs tests on output signals.
[Starting Procedure]
Monitor/test screen
X/Y Monitor/test
[Monitor/Test Screen]
Figure 8.13 X/Y Monitor/test screen
8 - 28
8.6 Monitor/Test
8.6.1 X/Y Monitor/test
8
UTILITY PACKAGE (GX Configurator-MB)
1
(1) X: Input signals
Table8.11 Setting items on the X/Y Monitor/test screen (Input signals)
X05: CH1 Automatic communication parameter setting, error completed
-
X06: CH1 Automatic communication operation status
-
X07: CH1 Automatic communication error status
-
X08: MODBUS(R) device assignment parameter setting, normally completed
-
X09: MODBUS(R) device assignment parameter setting, error completed
-
X0A: MODBUS(R) device assignment parameter setting existence
-
X0C: CH2 Automatic communication parameter setting, normally completed
-
X0D: CH2 Automatic communication parameter setting, error completed
-
Section 9.1.1
3
Section 9.1.2
4
Section 9.1.1
X0E: CH2 Automatic communication operation status
-
X0F: CH2 Automatic communication error status
-
X1B: CH common/CH1 error
-
X1C: CH2 error
-
X1F: Watch dog timer error
-
Section 11.5
5
-
(2) Y: Output signals
To perform a test on output signals, select any item in the Setting value column and
click the
Execute test
button.
Table8.12 Setting items on the X/Y Monitor/test screen (Output signals)
Monitor/test Item
Y04: CH1 Automatic communication parameter setting request/Automatic communication
start request
Buffer memory address
Section 9.1.1
-
Y08: MODBUS(R) device assignment parameter setting request
-
Y0C: CH2 Automatic communication parameter setting request/Automatic communication
start request
Reference
-
Y06: CH1 Automatic communication stop request
Section 9.1.2
Section 9.1.1
-
Y1B: CH common/CH1 error clear request
-
6
7
-
Y0E: CH2 Automatic communication stop request
SYSTEM
CONFIGURATION
-
SPECIFICATIONS
X04: CH1 Automatic communication parameter setting, normally completed
2
MODBUS(R) STANDARD
FUNCTIONS
-
FUNCTION
X00: Module READY
Reference
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Buffer memory address
PARAMETER SETTING
Monitor/test item
OVERVIEW
[Monitor/Test Items]
8
Section 11.5
-
8.6 Monitor/Test
8.6.1 X/Y Monitor/test
UTILITY PACKAGE
(GX Configurator-MB)
Y1C: CH2 error clear request
8 - 29
8
UTILITY PACKAGE (GX Configurator-MB)
8.6.2 MODBUS(R) device assignment parameter status
[Monitor Purpose]
Monitor the setting status of the MODBUS
device assignment parameters.
[Starting Procedure]
Monitor/test screen
MODBUS(R) device
[Monitor Screen]
Figure 8.14 MODBUS(R) device assignment parameter status screen
[Monitor Items]
Table8.13 Setting items on the MODBUS(R) device assignment parameter status screen
Monitor item
MODBUS(R) device assignment parameter setting existence
MODBUS(R) device assignment parameter error code storage area
MODBUS(R) device assignment
Error, device type
Buffer memory address
0C13H
(3091)
0C14H
(3092)
parameter setting result storage
area
8 - 30
Error, assigned group No.
8.6 Monitor/Test
8.6.2 MODBUS(R) device assignment parameter status
Reference
0C15H
(3093)
Section 11.4.1
UTILITY PACKAGE (GX Configurator-MB)
1
OVERVIEW
8.6.3 Automatic communication status
[Monitor/Test Purpose]
Monitor the communication status of the automatic communication function.
[Starting Procedure]
2
Automatic communication
SYSTEM
CONFIGURATION
Monitor/test screen
[Monitor/Test Screen]
SPECIFICATIONS
3
MODBUS(R) STANDARD
FUNCTIONS
4
5
FUNCTION
Figure 8.15 Automatic communication status screen
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
PARAMETER SETTING
7
8
UTILITY PACKAGE
(GX Configurator-MB)
8
8.6 Monitor/Test
8.6.3 Automatic communication status
8 - 31
8
UTILITY PACKAGE (GX Configurator-MB)
[Monitor/Test Items]
Table8.14 Setting items on the Automatic communication status screen
Buffer memory address
Monitor/test items
Reference
CH1
CH2
Automatic communication operation status
-
Automatic communication error status
-
Automatic communication parameter error code storage area
Automatic communication parameter setting result storage area
0C16H
0C18H
(3094)
(3096)
0C17H
0C19H
(3095)
(3097)
Automatic communication parameter setting request/automatic
-
communication start request *1
Automatic communication stop request *1
Automatic communication setting status
storage area
Parameters 1 to 32
Automatic communication operation status
storage area
Automatic communication error code storage
area
Section 11.4.1
0CA8H to 0CA9H
0CAAH to 0CABH
(3240 to 3241)
(3242 to 3243)
0C20H to 0C21H
0C22H to 0C23H
(3104 to 3105)
(3106 to 3107)
0C28H to 0C47H
0C48H to 0C67H
(3112 to 3143)
(3144 to 3175)
* 1 To test the automatic communication start request or the automatic communication stop request,
select the relevant item in the Setting value column and click the
Execute test
button.
POINT
When conducting a test on the automatic communication start request or
automatic communication stop request with "Being requested" set in the Setting
value column, make sure that "Not requested" is displayed in the Current value
column.
When the current value is "Being requested", the test for "Being requested"
setting cannot be performed.
If the current value is "Being requested", change it to "Not requested" and start the
test.
8 - 32
8.6 Monitor/Test
8.6.3 Automatic communication status
8
UTILITY PACKAGE (GX Configurator-MB)
1
[Monitor Purpose]
Display the errors that occurred in the QJ71MB91.
Error logs are displayed in reverse chronological order (the latest error is displayed as
No.1).
Monitor/test Screen
2
SYSTEM
CONFIGURATION
[Starting Procedure]
OVERVIEW
8.6.4 Error log
Error log
[Monitor Screen]
SPECIFICATIONS
3
MODBUS(R) STANDARD
FUNCTIONS
4
FUNCTION
5
Figure 8.16 Error log screen
[Monitor Items]
Number of errors occurred
Buffer memory address
0CFEH
(3326)
Detailed error code
0D00H(3328)
Exception code
0D01H(3329)
Function code
0D02H(3330)
CH
0D03H(3331)
Station No.
0D04H(3332)
Function
0D07H(3335)
7
Section 11.4.1
No. 1
(Same as in No. 1)
8
0D08H to 0DFFH
UTILITY PACKAGE
(GX Configurator-MB)
No.2 to 32
Reference
(3336 to 3583)
8.6 Monitor/Test
8.6.4 Error log
PARAMETER SETTING
Monitor item
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
6
Table8.15 Setting items on the Error log screen
8 - 33
8
UTILITY PACKAGE (GX Configurator-MB)
8.6.5 Communication status
[Monitor Purpose]
Monitor communication status.
[Starting Procedure]
Monitor/test screen
Communication status
[Monitor Screen]
Figure 8.17 Communication status screen
8 - 34
8.6 Monitor/Test
8.6.5 Communication status
8
UTILITY PACKAGE (GX Configurator-MB)
1
[Monitor Items]
Buffer memory address
Reference
Bus communication error count
Character overrun error count
Message discard count
Data discard count
Failed transmission count
0F00H
0F40H
(3840)
(3904)
0F01H
0F41H
(3841)
(3905)
0F02H
0F42H
(3842)
(3906)
0F03H
0F43H
(3843)
(3907)
0F04H
0F44H
(3844)
(3908)
0F05H
0F45H
(3845)
(3909)
Diagnostic data for Master
Received NAK count
Received busy count
0F0EH
0F4EH
(3854)
(3918)
0F0FH
0F4FH
(3855)
(3919)
0F10H
0F50H
(3856)
(3920)
0F11H
0F51H
(3857)
(3921)
0F12H
0F52H
(3858)
(3922)
4
5
(Continued on next page)
6
PRE-OPERATIONAL
PROCEDURES AND
SETTINGS
Broadcast count
Section 11.3
7
PARAMETER SETTING
No-response count
3
8
UTILITY PACKAGE
(GX Configurator-MB)
Received exception error count
2
MODBUS(R) STANDARD
FUNCTIONS
Bus message count
-
SYSTEM
CONFIGURATION
Diagnostic data for Master/Slave
CH2
SPECIFICATIONS
CH1
FUNCTION
Monitor item
OVERVIEW
Table8.16 Setting items on the Communication status screen
8.6 Monitor/Test
8.6.5 Communication status
8 - 35
8
UTILITY PACKAGE (GX Configurator-MB)
Table8.16 Setting items on the Communication status screen (Continued)
Buffer memory address
Monitor item
Reference
CH1
Diagnostic data for Slave
Slave message count
Slave no-response count
Slave NAK count
Slave busy count
Exception error count
Communications event count
2nd byte of end code
Communications mode
Communications event log count
Communications event log 1 to 64
Error response code presence
CH2
-
0F06H
0F46H
(3846)
(3910)
0F07H
0F47H
(3847)
(3911)
0F08H
0F48H
(3848)
(3912)
0F09H
0F49H
(3849)
(3913)
0F0AH
0F4AH
(3850)
(3914)
0F0BH
0F4BH
(3851)
(3915)
0F0CH
0F4CH
(3852)
(3916)
0F0DH
0F4DH
(3853)
(3917)
0F1FH
0F5FH
(3871)
(3935)
0F20H to
0F60H to
0F3FH(3872
0F7FH(3936
to 3903)
to 3967)
0006H
0007H
(6)
(7)
0002H
0004H
(2)
(4)
Section 11.3
Section 4.12
Section 4.11.4
Section 4.11.5
Section 4.13
Section 11.4.2
Error response code storage area
LED status
-
C/N
P/S
PRO.
SIO
NEU.
ACK.
NAK
8 - 36
8.6 Monitor/Test
8.6.5 Communication status
0006H
0007H
(6)
(7)
Section 11.2
9
PROGRAMMING
This chapter explains parameter setting methods and program examples when setting
parameters with a sequence program.
Before using the program examples introduced in this chapter in an actual system, fully
check that there is no problem in control on the target system.
For the QJ71MB91, parameters can be also set on-screen using the utility package (GX
CHAPTER 8)
9.1 Parameter Setting
11
9.1.1 Automatic communication parameter
(1) Automatic communication parameter setting method
Set the automatic communication parameters with sequence program as follows.
TROUBLESHOOTING
Configurator-MB).(
10
DEDICATED
INSTRUCTIONS
CHAPTER9 PROGRAMMING
PROGRAMMING
9
2) Turn ON the Automatic communication parameter setting request/Automatic
communication start request (Y4/YC).
(2) I/O signals used for automatic communication parameter setting
APPENDICES
1) Store parameters in the Automatic communication parameter area of the buffer
memory (address: 0200H to 037FH/0380H to 04FFH).
The automatic communication parameters are set using the following I/O signals.
Table9.1 I/O signals used for automatic communication parameter setting
Signal
Signal name
CH2
INDEX
CH1
Module READY
X0
ON : Accessible
OFF : Not accessible
Automatic communication parameter setting, normally completed
X4
XC
ON : Normally completed
OFF : Automatic communication parameter setting, error completed
X5
XD
ON : Error completed
OFF : Automatic communication operation status
X6
XE
ON : Operating
OFF : Stopped
Automatic communication parameter setting request/Automatic communication start
Y4
YC
request
ON : Being requested
OFF : No requested
9.1 Parameter Setting
9.1.1 Automatic communication parameter
9-1
9
PROGRAMMING
(3) Timing charts for automatic communication parameter setting
(a) When completed normally
Automatic communication parameter setting,
normally completed/Automatic
communication function start
Automatic
communication
parameter
creation
Parameter creation
ON
Module READY
X0
OFF
ON
Automatic communication
parameter setting request/
Automatic communication start request
Y4/YC
OFF
ON
OFF
Automatic communication
parameter setting, normally completed
X4/XC
Automatic communication
parameter setting, error completed
X5/XD OFF
Automatic communication
operation status
X6/XE OFF
ON
0C16H
Automatic communication
parameter error code storage area
/0C18H
Automatic communication
parameter setting result storage area
0C17H
/0C19H
Clear error
code and
setting result
Executed by QJ71MB91
Executed by sequence program
Figure 9.1 Timing chart for automatic communication parameter setting (Normal completion)
(b) When completed with an error
Automatic communication
parameter setting,
error completed
Automatic
communication
parameter creation
(error)
Parameter creation
Automatic communication parameter setting,
normally completed/Automatic
communication function start
Automatic
communication
parameter
correction
ON
X0
Module READY
Automatic communication
parameter setting request/
Automatic communication start request
OFF
ON
ON
Y4/YC
OFF
ON
Automatic communication
parameter setting, normally completed
X4/XC
Automatic communication
parameter setting, error completed
X5/XD
Automatic communication
operation status
OFF
ON
OFF
ON
X6/XE
Automatic communication
parameter error code storage area
0C16H
/0C18H
Automatic communication
parameter setting result storage area
0C17H
/0C19H
OFF
Error code
and setting
result storage
Clear error
code and
setting result
Executed by QJ71MB91
Executed by sequence program
Figure 9.2 Timing chart for automatic communication parameter setting (Error completion)
9-2
9.1 Parameter Setting
9.1.1 Automatic communication parameter
PROGRAMMING
9
PROGRAMMING
(4) Precautions for automatic communication parameter setting
(a) When turning ON the Automatic communication parameter setting request/
Automatic communication start request (Y4/YC)
Be sure to turn ON the Module READY (X0) in advance.
Section 11.4)
APPENDICES
(c) Clearing the automatic communication function buffer
The Automatic communication function buffer input area (address: 1000H to
1FFFH/2000H to 2FFFH) and the Automatic communication function buffer output
area (address: 3000H to 3FFFH/4000H to 4FFFH) used for the buffer memory read/
write setting are not cleared when the automatic communication function is
started.
If necessary, clear these areas by a sequence program.
11
TROUBLESHOOTING
Then make the parameter setting request again.(
DEDICATED
INSTRUCTIONS
10
(b) When automatic communication parameter setting completes with an error
The erroneous automatic communication parameter is stored in the Automatic
communication parameter setting result storage area of the buffer memory
(address: 0C17H/0C19H), and an error code is stored in the Automatic
communication parameter error code storage area (address: 0C16H/0C18H).
Identify the stored parameter, check the error code and take corrective actions.
INDEX
9
9.1 Parameter Setting
9.1.1 Automatic communication parameter
9-3
9
PROGRAMMING
9.1.2 MODBUS(R) device assignment parameter
(1) MODBUS
device assignment parameter setting method
Set the MODBUS device assignment parameters with sequence program as
follows.
1) Store MODBUS
memories.
device assignment parameters in the following buffer
Table9.2 MODBUS
device assignment parameter storage location
Address
000AH to 000BH
(10 to 11)
000DH
(13)
000EH
(14)
0900H to 09FFH
(2304 to 2559)
Name
Setting error status read device
Section 7.3.4
CPU response monitoring timer value
Section 7.3.6
Access target (when mounted to MELSECNET/H remote I/O
station)
MODBUS
2) Turn ON the MODBUS
device assignment parameter
Table9.3 I/O signals used for MODBUS
Signal
device assignment parameter setting.
device assignment parameter setting
Signal name
Module READY
ON : Accessible
OFF : Not accessible
MODBUS
device assignment parameter setting, normally completed
ON : Normally completed
OFF : MODBUS
X9
device assignment parameter setting, error completed
ON : Error completed
OFF : MODBUS
XA
device assignment parameter setting existence
ON : Parameters set
OFF : No parameters set
MODBUS
Y8
device assignment parameter setting request
ON : Being requested
OFF : Not requested
9-4
Section 7.3.1
device assignment parameter setting
Use the following I/O signals for MODBUS
X8
Section 7.3.5
device assignment parameter setting request (Y8).
(2) I/O signals used for MODBUS
X0
Reference
9.1 Parameter Setting
9.1.2 MODBUS(R) device assignment parameter
PROGRAMMING
9
device assignment parameter setting
PROGRAMMING
(3) Timing charts for MODBUS
(a) When completed normally
R
MODBUS device
assignment parameter
setting, normally completed
10
R
ON
MODBUS R device
assignment parameter
setting request
X0
ON
Y8
OFF
X8
OFF
MODBUS R device
assignment parameter
setting, error completed
X9
OFF
ON
R
MODBUS device
assignment parameter
setting existence
XA
MODBUS R device
assignment parameter
error code storage area
0C13H
MODBUS R device
assignment parameter
setting result storage area
11
ON
MODBUS R device
assignment parameter
setting, normally completed
TROUBLESHOOTING
Module READY
OFF
OFF
0C14H to 0C15H
Clear error
code and
setting result
Executed by QJ71MB91
APPENDICES
Parameter creation
DEDICATED
INSTRUCTIONS
MODBUS
device assignment
parameter creation
Executed by sequence
program
Figure 9.3 Timing chart for MODBUS
device assignment parameter setting (Normal completion)
INDEX
9
9.1 Parameter Setting
9.1.2 MODBUS(R) device assignment parameter
9-5
9
PROGRAMMING
(b) When completed with an error
R
R
MODBUS device
assignment parameter
setting, normally
completed
MODBUS device
assignment parameter
setting, error completed
R
R
MODBUS
device assignment
parameter
creation (error)
Parameter creation
MODBUS
device assignment
parameter
correction
ON
Module READY
X0
OFF
ON
ON
MODBUS R device
assignment parameter
setting request
Y8
OFF
ON
MODBUSR device
assignment parameter
setting, normally
completed
X8
ON
R
MODBUS device
assignment parameter
setting, error completed
X9
R
MODBUS device
assignment parameter
error code storage area
OFF
ON
R
MODBUS device
assignment parameter
setting existence
OFF
XA
OFF
0C13H
Error
code and
setting result
storage
MODBUSR device
0C14H to 0C15H
assignment parameter
setting result storage area
Clear
error code
and setting
result
Executed by QJ71MB91
Executed by sequence program
Figure 9.4 Timing chart for MODBUS
9-6
device assignment parameter setting (Error completion)
9.1 Parameter Setting
9.1.2 MODBUS(R) device assignment parameter
PROGRAMMING
device assignment parameters
When using a sequence program to set MODBUS device assignment
parameters, perform the following in the intelligent function module switch setting.
(
Section 6.6)
1) Set the MODBUS device assignment parameter starting method to "User
setting parameter".
2) Set the slave function to either channel 1 or 2 in the mode setting.
If the MODBUS device assignment parameter setting request (Y8) is turned
ON with both channels 1 and 2 set to the master function, the operation mode
error (error code: 7353H) will occur.
(b) When turning ON the MODBUS device assignment parameter setting request
(Y8)
Be sure to turn ON the Module READY (X0) in advance.
10
DEDICATED
INSTRUCTIONS
(a) Before setting MODBUS
device assignment parameter setting
11
TROUBLESHOOTING
(4) Precautions for MODBUS
PROGRAMMING
9
1) Refer to the MODBUS
device assignment parameter setting result storage
area (address: 0C14H to 0C15H) to identify the erroneous parameter.(
Section 11.4.1)
APPENDICES
(c) When the MODBUS device assignment parameter setting, error completed
signal (X9) is turned ON
Correct the parameters by the following procedure.
2) Refer to the MODBUS device assignment parameter error code storage
area (address: 0C13H) to check the error details, and correct the relevant
parameter.(
Section 11.4.1)
3) Execute the MODBUS
(d) MODBUS
device assignment parameter setting request again.
INDEX
9
device assignment parameter setting existence
The MODBUS device assignment parameter setting existence (XA) turns ON
even if some default parameters exist.
(e) When a request message has been received before normal setting completion
The QJ71MB91 sends an error response (exception code: 04H) to the master if it
received from the master the read/write request message to a MODBUS device
before normal completion of the MODBUS
setting.
(f) Resetting MODBUS
device assignment parameter
device assignment parameters
MODBUS device assignment parameters in sequence programs can be reset at
any timing after the QJ71MB91 is powered on.
9.1 Parameter Setting
9.1.2 MODBUS(R) device assignment parameter
9-7
9
PROGRAMMING
9.2 Program Example for Normal System Configuration
9.2.1 Automatic communication parameter
(1) System configuration
The following system configuration is used to explain a program example for setting
the automatic communication parameters.
Setting target
R
MODBUS slave device
(station No.1)
QJ71MB91*1
(master function)
R
MODBUS slave device
(station No.2)
QJ71MB91
CH1
RUN
ERR.
NEU.
SD
NEU.
SD
RD
CH2
RD
CH1
RS-232
SDA
SG
SDB
(FG)
RDA
1
2
3
4
5
(FG)
RDB
CH2
RS-422
/485
6
7
CH2
GX Developer
RS-485
Figure 9.5 System configuration example for the automatic communication parameter setting
* 1 The QJ71MB91 is to be mounted in slot 0 of the base unit with the head I/O number set to "00H".
(2) Communications
Data are exchanged between the QJ71MB91 and MODBUS
No.1 and No.2) using the automatic communication function.
slave devices (station
(a) Automatic communication parameter setting diagram
Set automatic communication parameters to the QJ71MB91.
R
MODBUS slave device
(station No.1)
Setting target
PLC CPU
R
MODBUS slave device
(station No.2)
QJ71MB91
CH2 Automatic
communication function
buffer input area
Device
Coil
2000H
D1200
2100H
64 words
D1263
016024
64 words
213FH
065536
2FFFH
*1
4000H
D1300
100 words
D1399
000001
015001
4A00H
CH2 Automatic
communication
function buffer
output area
*2
Holding register
400001
400100
100 words
4A63H
4FFFH
465536
Figure 9.6 Communications with the automatic communication parameters set
* 1 Data can be transferred between the automatic communication function buffer and the PLC CPU
devices by either of the following methods:
Transfer by the auto refresh setting (
This section (3) (c))
Transfer by using intelligent function module devices (Un\G ) (
This section (4) (b))
* 2 Automatic communication parameters are set from GX Configurator-MB or a sequence program.
9-8
9.2 Program Example for Normal System Configuration
9.2.1 Automatic communication parameter
PROGRAMMING
9
PROGRAMMING
(b) Settings
The following automatic communication parameters are set for the program
example.
Table9.4 Automatic communication parameter settings
Buffer memory address
Setting value
0380H to 0381H (896 to 897)
1H
Target station No.
0382H (898)
2
Request interval timer value
0383H (899)
600 (6s)
Response monitoring timer value
0384H (900)
500 (5s)
Setting parameter existence
10
DEDICATED
INSTRUCTIONS
Setting item
CH2 automatic
0100H
communication Type specification of the target MODBUS
device
parameter 1
0385H (901)
Head buffer memory address
0386H (902)
2100H
0387H (903)
15000
0388H (904)
1024
038CH to 038DH (908 to 909)
1H
Target station No.
038EH (910)
1
Request interval timer value
038FH (911)
Response monitoring timer value
0390H (912)
number
device head
Access points
Setting parameter existence
CH2 automatic
communication
parameter 2
Type specification of the target MODBUS
0391H (913)
device
Head buffer memory address
Write
Target MODBUS
setting
number
Access points
device head
TROUBLESHOOTING
Target MODBUS
setting
0 (Issue request immediately after
receiving response from slave.)
500 (5s)
0005H
(Write holding registers)
0395H (917)
4A00H
0396H (918)
0
0397H (919)
100
9.2 Program Example for Normal System Configuration
9.2.1 Automatic communication parameter
INDEX
Read
11
(Read coils)
APPENDICES
9
9-9
9
PROGRAMMING
(3) Parameter settings
The following setting is required to perform the communication shown in (2).
(a) Intelligent function module switch setting
Set the intelligent function module switches for the setting target, QJ71MB91, as
shown below. (
Section 6.6)
1) When using GX Configurator-MB
Figure 9.7 Intelligent function module switch setting (When using GX Configurator-MB)
2) When not using GX Configurator-MB
Figure 9.8 Intelligent function module switch setting (When not using GX Configurator-MB)
(b) Automatic communication parameter
1) When using GX Configurator-MB
Set CH2 Automatic communication parameters in the Initial setting of GX
Configurator-MB. (
Section 8.4.1)
Set the values shown in the settings. (
This section (2) (b))
Figure 9.9 Automatic communication parameter
2) When not using GX Configurator-MB
Set automatic communication parameters from the sequence program.
(
9 - 10
This section (4) (a))
9.2 Program Example for Normal System Configuration
9.2.1 Automatic communication parameter
PROGRAMMING
9
PROGRAMMING
(c) Auto refresh setting
Configure the following auto refresh setting on GX Configurator-MB.
DEDICATED
INSTRUCTIONS
10
TROUBLESHOOTING
11
Remark
When not using GX Configurator-MB, program the processing equivalent to the
auto refresh setting using intelligent function module devices.
(
APPENDICES
Figure 9.10 Auto refresh setting
This section (4) (b))
INDEX
9
9.2 Program Example for Normal System Configuration
9.2.1 Automatic communication parameter
9 - 11
9
PROGRAMMING
(4) Program example
The following is an example of the sequence program required to perform the
communication shown in (2).
(a) Program example for automatic communication parameter setting
The program example is shown below.
When automatic communication parameters are set from GX Configurator-MB,
this program is not required.
Initializing automatic communication
parameter setting area
Setting
Module
command READY
CH2
Automatic
communication
operation
status
Setting parameter existence (1H)
Target station No. (2)
Request interval timer value (6s)
Response monitoring timer
value (5s)
Type specification of the target
R
MODBUS device (0100H)
CH2 Automatic
communication
parameter 1
Head buffer memory address
(2100H)
R
Target MODBUS device
head number (15000)
Access points (1024 points)
Setting parameter existence (1H)
Target station No. (1)
Request interval timer value (0)
Response monitoring timer value
(5s)
Type specification of the target
R
MODBUS device (0005H)
CH2 Automatic
communication
parameter 2
Head buffer memory address
(4A00H)
Target MODBUS
number (0)
R
device head
Access points (100 points)
CH2 Automatic communication parameter setting
request/Automatic communication start request
CH2 Automatic communication parameter setting,
normally completed
Processing for normal completion
CH2 Automatic communication parameter setting,
error completed
Processing for error completion*1
Figure 9.11 Automatic communication parameter setting program example
9 - 12
9.2 Program Example for Normal System Configuration
9.2.1 Automatic communication parameter
PROGRAMMING
Processing for error
completion
Data to be stored in the PLC CPU are as follows:
D1500: CH2 Automatic communication parameter error code
D1501: CH2 Automatic communication parameter setting result
Figure 9.12 Program example for error completion of automatic communication parameters
(b) Program example for data transfer between QJ71MB91 and PLC CPU
The program example is shown below.
When data transfer between the QJ71MB91 and PLC CPU is set in the Auto
10
DEDICATED
INSTRUCTIONS
Data such as an error
code are fetched into
PLC CPU devices.
11
TROUBLESHOOTING
* 1 The following is a processing example for error completion.
From the QJ71MB91 buffer memory (address: 0C18H to 0C19H), the PLC CPU obtains data such
as an error code identified at the time of automatic communication parameter setting.
PROGRAMMING
9
Refreshes automatic
communication function
buffer input area
Module CH2 Automatic
READY communication
operation status
Refreshes automatic
communication function
buffer output area
Module CH2 Automatic
READY communication
operation status
APPENDICES
refresh setting of GX Configurator-MB, this program is not required.
Figure 9.13 Program example for data transfer between QJ71MB91 and PLC CPU
INDEX
9
9.2 Program Example for Normal System Configuration
9.2.1 Automatic communication parameter
9 - 13
9
PROGRAMMING
9.2.2 MODBUS(R) device assignment parameter
(1) System configuration
The following system configuration is used to explain a program example for setting
the MODBUS device assignment parameters to the QJ71MB91.
Setting target
QJ71MB91*1
(Slave function)
(Station No.1)
R
MODBUS master device
CH2
GX Developer
RS-422/485
Figure 9.14 System configuration example for the MODBUS
device assignment parameter setting
* 1 The QJ71MB91 is to be mounted in slot 0 of the base unit with the head I/O number set to “00H”.
(2) Communications
In the program example shown in this section, the following MODBUS device
assignment parameters are set for the setting target , QJ71MB91.
(a) MODBUS device assignment parameter assignment diagram
R
PLC CPU device memory
Y0
Y100
Y2FF
MODBUS device
Coil
Output (Y)
512 points
512 points
000001
000512
Y1FFF
065536
Data register (D)
Input register
D0
300001
D3500
303500
5500 points
5500 points
D8999
308999
D12287
365536
QJ71MB91 buffer memory
Holding register
400001
User free area
1024 points
5000H
401024
5500H
1024 points
58FFH
5FFFH
465536
Figure 9.15 MODBUS
9 - 14
device assignment diagram
9.2 Program Example for Normal System Configuration
9.2.2 MODBUS(R) device assignment parameter
9
PROGRAMMING
9
Setting item
Input register
Buffer memory address
Setting value
009DH
Device code
0900H (2304)
Head device number
0901H (2305)
0100H
Head coil number
0902H (2306)
0 (000001)
Assignment points
0903H (2307)
512 (points)
Device code
0980H (2432)
Head device number
0981H (2433)
3500
Head input register number
0982H (2434)
3499 (303500)
Assignment points
0983H (2435)
5500 (points)
Device code
09C0H (2496)
Head device number
09C1H (2497)
5500H
Head holding register number
09C2H (2498)
0 (400001)
Assignment points
09C3H (2499)
1024 (points)
10
(Y: Output)
DEDICATED
INSTRUCTIONS
Coil assignment 1
device assignment parameter settings
00A8H
(D: Data register)
assignment 1
Holding register
11
TROUBLESHOOTING
Table9.5 MODBUS
PROGRAMMING
(b) Settings
F000H
(User free area)
INDEX
APPENDICES
assignment 1
9.2 Program Example for Normal System Configuration
9.2.2 MODBUS(R) device assignment parameter
9 - 15
9
PROGRAMMING
(3) Parameter settings
The following setting is required to perform the communication shown in (2).
(a) Intelligent function module switch setting
Set the intelligent function module switches for the setting target, QJ71MB91, as
shown below. (
Section 6.6)
Figure 9.16 Intelligent function module switch setting
(b) MODBUS device assignment parameter
1) When using GX Configurator-MB
Set MODBUS device assignment parameter in the Initial setting of GX
Configurator-MB. (
Section 8.4.2)
Set the values shown in the settings. (
Figure 9.17 MODBUS
This section (2) (b))
device assignment parameter
2) When not using GX Configurator-MB
Set MODBUS device assignment parameter from the sequence program.
(
9 - 16
This section (4))
9.2 Program Example for Normal System Configuration
9.2.2 MODBUS(R) device assignment parameter
9
PROGRAMMING
9
PROGRAMMING
(4) Program example
R
Initializing MODBUS device assignment
parameter setting area
Setting
Module
command READY
Device code (009DH)
10
Head device number (0100H)
Coil assignment 1
DEDICATED
INSTRUCTIONS
Head coil number (0)
Assignment points
(512 points)
Device code (00A8H)
Head input register number
(3499)
Input register
assignment 1
Assignment points
(5500 points)
Device code (F000H)
Head device number (5500H)
Head holding register
number (0)
11
TROUBLESHOOTING
Head device number (3500)
Holding register
assignment 1
Assignment points
(1024 points)
R
APPENDICES
MODBUS device assignment
parameter setting request
R
Processing for normal completion
MODBUS device assignment
parameter setting request,
normally completed
R
MODBUS device assignment
parameter setting request,
error completed
Figure 9.18 MODBUS
INDEX
Processing for error completion*1
device assignment parameter setting program example
* 1 The following is a processing example for error completion.
From the QJ71MB91 buffer memory (address: 0C13H to 0C15H), the PLC CPU obtains data such
as an error code identified at the time of MODBUS
device assignment parameter setting.
Data such as an error
code are fetched into
PLC CPU devices.
Processing for error
completion
Data to be stored in the PLC CPU are as follows:
D2000: MODBUS R device assignment parameter error code
D2001: Error, device type
D2002: Error, assigned group No.
Figure 9.19 Program example for error completion of MODBUS
device assignment parameters
9.2 Program Example for Normal System Configuration
9.2.2 MODBUS(R) device assignment parameter
9 - 17
9
PROGRAMMING
9.2.3 When using the automatic communication function and dedicated
instructions on the same channel
This section explains the setting and programming for the case where the automatic
communication function and dedicated instructions are used on the same channel.
(1) System configuration
In the following system configuration, the automatic communication parameter and
dedicated instructions shall be used on the same channel.
Setting target
R
QJ71MB91*1
(master function)
MODBUS slave device
(station No.1)
QJ71MB91
CH1
RUN
NEU.
SD
RD
ERR.
NEU.
SD
CH2
RD
CH1
RS-23 2
SDA
1
SG
SDB
2
3
(FG)
RDA
4
5
(FG)
RDB
CH2
RS-42 2
/485
GX Developer
6
7
CH2 (RS-422/485)
Communicated by automatic communication function + dedicated instructions
Figure 9.20 System configuration example for use of the automatic
communication function and dedicated instructions on the same channel
* 1 The QJ71MB91 is to be mounted in slot 0 of the base unit with the head I/O No. set to "0".
9 - 18
9.2 Program Example for Normal System Configuration
9.2.3 When using the automatic communication function and dedicated instructions on the same channel
9
PROGRAMMING
(2) Dedicated instruction execution timing
Dedicated instructions can be executed at the timing shown below.
When using the automatic communication function and dedicated instructions on the
same channel, set an appropriate request interval timer value and create a proper
program so that dedicated instructions can be executed in the right timing.(
section (3))
This
Request interval timer
Dedicated
instruction
Response monitoring
executable timing
timer
Request
message
11
Response
message
Request
message
TROUBLESHOOTING
Automatic
communication
parameter
1
Request interval timer
Dedicated
*1 instruction
Response monitoring
executable timing
timer
Automatic
communication
parameter
2
10
DEDICATED
INSTRUCTIONS
Example: When automatic communication parameters 1 to 3 are set
PROGRAMMING
9
Request
message
Broadcast delay
Automatic
communication
parameter
3
APPENDICES
Request interval timer
Dedicated
instruction
executable timing
Request
message
(Broadcast)
(3) Method for normally executing dedicated instructions
(Step 1)
Make setting in at least one of the automatic communication parameters so that
the time for dedicated instruction execution can be ensured. (
(4) (a))
This section
(Step 2)
Design the program so that dedicated instructions will be executed in the standby
status of the automatic communications set in the above (Step 1).(
section (4) (b))
9.2 Program Example for Normal System Configuration
9.2.3 When using the automatic communication function and dedicated instructions on the same channel
This
9 - 19
INDEX
Figure 9.21 Dedicated instruction execution timing
* 1 Shows the case that the response monitoring timer has timed out due to no response from the
target slave
9
PROGRAMMING
(4) Setting and programming for normal execution of dedicated instructions
(a) Setting the request interval timer of the automatic communication parameter
Set the request interval timer to ensure the timing for dedicated instruction
execution.
When setting the request interval timer, the following condition must be satisfied:
Request interval timer[ms]
Tarb + Tdrb + St + 10ms*1
Table9.6 Calculation items for the request interval timer
Setting item
Tarb
Tdrb
St
Description
Response monitoring timer value/Broadcast delay value for the automatic
communication function*2
Response monitoring timer value/Broadcast delay value for dedicated
instructions*3*4
Local station scan time
Unit
ms
ms
ms
* 1 The result of Tarb+Tdrb+St is rounded up in 10ms units.
* 2 Set a value greater than the automatic communication function communication time (Tac).
(
Appendix 2)
* 3 Set a value greater than the dedicated instruction processing time (Trc).(
Appendix 2)
* 4 To execute multiple dedicated instructions consecutively within the reserved time, totalize the
response monitoring timer values/broadcast delay values for the number of the dedicated
instructions to be executed.
9 - 20
9.2 Program Example for Normal System Configuration
9.2.3 When using the automatic communication function and dedicated instructions on the same channel
9
PROGRAMMING
POINT
The request interval timer is set only for the automatic communication parameters
by which dedicated instructions are to be executed at appropriate timing.
All the request interval timers in the automatic communication parameters need not
to satisfy the (4) (a) condition.
PROGRAMMING
9
10
DEDICATED
INSTRUCTIONS
Request interval timer
Dedicated
Response monitoring instruction
executable timing
timer
Automatic
communication
parameter
1
Request
message
Response
message
11
TROUBLESHOOTING
Request interval timer
Dedicated
instruction
Response monitoring executable timing
timer
Automatic
communication
parameter
2
Request
message
INDEX
APPENDICES
To execute a dedicated instruction in this timing,
set only the request interval timer of automatic communication
parameter 1 so that the (4) (a) are satisfied.
9.2 Program Example for Normal System Configuration
9.2.3 When using the automatic communication function and dedicated instructions on the same channel
9 - 21
9
PROGRAMMING
(b) Executing a dedicated instruction during automatic communication function ready
status
Use the Automatic communication ready status storage area of buffer memory
(address: 0CB0H/0CB2H to 0CB1H/0CB3H) to program so that the dedicated
instruction is executed at the rise of the corresponding bit.
1) Automatic communication ready status storage area
The automatic communication ready status can be confirmed.
(CH1 Automatic communication ready status storage area)
b15 b14 b13 b12 b11 b10
b5
b4
b3 b2
b1 b0
0CB0H
16
15
14
13
12
11
6
5
4
2
0CB1H
32 31
30
29
28
27
22
21 20
b15 b14 b13 b12 b11 b10
b5
b4
b3 b2
b1 b0
0CB2H
16
15
14
13
12
11
6
5
4
2
0CB3H
32 31
30
29
28
27
22
21 20
3
1
19 18 17
(CH2 Automatic communication ready status storage area)
3
1
19 18 17
Number indicates that of automatic communication parameter.
0: Communicating by automatic communication function, or
automatic communication function stopped
1: Ready for automatic communication *1
Figure 9.22 Configuration of automatic communication ready status storage area
* 1 "Ready" represents "the time during which dedicated instructions are executable" that is shown in
the figure in (2).
9 - 22
9.2 Program Example for Normal System Configuration
9.2.3 When using the automatic communication function and dedicated instructions on the same channel
9
PROGRAMMING
2) Program example for dedicated instruction
This section provides an program example in which a dedicated instruction
(MBRW) is executed while automatic communication of Automatic
communication parameter 1 on channel 2 is in ready status.
In the program example on the next page, the following device read/write is
executed to the holding register on the slave (Station No. 1) on channel 2.
QJ71MB91
CH1
RUN
NEU.
SD
RD
ERR.
NEU.
SD
CH2
RD
CH1
RS-23 2
11
SDA
1
SG
RDA
2
3
4
5
(FG)
RDB
CH2
RS-42 2
/485
6
7
TROUBLESHOOTING
SDB
(FG)
10
DEDICATED
INSTRUCTIONS
R
MODBUS
slave device
(station No.1)
QJ71MB91
(master)
PROGRAMMING
9
CH2 (RS-422/485)
R
QJ71MB91
(master)
MODBUS
slave device
R
Device memory
MODBUS device
400500
D100
32 points
400531
100 points
r
ite
W
W0000
411000
Re
ad
APPENDICES
D199
100 points
32 points
411099
W001F
Figure 9.23 Processing of program example
INDEX
(Continued on next page)
9.2 Program Example for Normal System Configuration
9.2.3 When using the automatic communication function and dedicated instructions on the same channel
9 - 23
9
PROGRAMMING
CH2 Automatic communication ready status storage area
(Automatic communication parameter 1)
Latch this when the start
command is a rise command.
\
CH2 Automatic CH2 Automatic
communication communication
operation status parameter setting
request/Automatic
communication
start request
Add X0E and Y0C to execute
dedicated instructions even if
automatic communication is
stopped.
Section 10.2,
Section 10.3
Processing for normal completion
Processing for error completion
When the dedicated instruction
completes, reset the latched
start command.
Figure 9.24 Program example for executing dedicated instruction during ready status of automatic communication
parameter 1 on channel 2
POINT
When using the automatic communication function and dedicated instructions on
the same channel, add the above
section to the sequence program.
(Perform the same in the case of the MBREQ instruction)
9 - 24
9.2 Program Example for Normal System Configuration
9.2.3 When using the automatic communication function and dedicated instructions on the same channel
PROGRAMMING
9
PROGRAMMING
9.3 Program Example for Use in MELSECNET/H Remote I/O
Network
9.3.1 Automatic communication parameter
10
This section provides a program example for setting the automatic communication
parameters to the QJ71MB91 on a MELSECNET/H remote I/O station in the following
system configuration.
MELSECNET/H remote master station*1
DEDICATED
INSTRUCTIONS
(1) System configuration
TROUBLESHOOTING
11
GX Developer
MELSECNET/H (remote I/O network)
Setting target
QJ71MB91
RUN
NEU.
SD
RD
CH1
R
MODBUS slave device
(station No.1)
R
MODBUS slave device
(station No.2)
ERR.
NEU.
SD CH2
RD
CH1
RS-232
SDA
1
SG
SDB
2
3
(FG)
RDA
4
5
(FG)
RDB
APPENDICES
MELSECNET/H
remote I/O station
(station No.1)
6
CH2
RS-422
/485
7
CH2
QJ71MB91*2
(master function)
RS-485
Figure 9.25 System configuration example for the automatic communication parameter setting
* 1 The MELSECNET/H remote master station is installed in slot 0 of the base unit with the start I/O
No. set as “00H”.
* 2 The QJ71MB91 is to be mounted in slot 0 of the base unit with the head I/O No. set to "40H".
Remark
For details on construction and parameter setting of the MELSECNET/H remote I/
O network, refer to the following manual.
Q Corresponding MELSECNET/H Network System Reference Manual
(Remote I/O network)
9.3 Program Example for Use in MELSECNET/H Remote I/O Network
9.3.1 Automatic communication parameter
9 - 25
INDEX
9
9
PROGRAMMING
(2) Communications
Data are exchanged between the QJ71MB91 and MODBUS slave devices (station
No. 1 and No. 2) using the automatic communication function.
The following shows communications performed when using and not using GX
Configurator-MB.
(a) Automatic communication parameter setting diagram
1) When using GX Configurator-MB
Communication data in the QJ71MB91 are transferred to the PLC CPU on the
MELSECNET/H remote master station as shown below.
MELSECNET/H remote master station
MELSECNET/H
remote master module
PLC CPU
Device
W1000H
D1000
64 words
64 words
W103FH
D1063
MELSECNET/H
MELSECNET/H
link refresh*1 *1
D1100
W1100H
100 words
100 words
D1199
W1163H
MELSECNET/H link scan*2
MODBUS R slave device
(station No.1)
MELSECNET/H remote I/O station (setting target)
MELSECNET/H
remote I/O module
QJ71MB91
CH2 Automatic communication
function buffer input area
Device
Coil
2000H
W1000H
016024
64 words
W103FH
213FH
2FFFH
065536
CH2 Automatic
communication
function buffer
output area
*3
4000H
*4
100 words
W1163H
4A00H
4A63H
4FFFH
100 words
Holding register
400001
400100
465536
Figure 9.26 Communications (When using GX Configurator-MB)
9 - 26
000001
015001
*4
2100H
64 words
W1100H
R
MODBUS slave device
(station No.2)
9.3 Program Example for Use in MELSECNET/H Remote I/O Network
9.3.1 Automatic communication parameter
PROGRAMMING
9
(
This section (3) (b))
* 2 Set the MELSECNET/H link scan by the network range assignment in the network parameters.
(
This section (3) (b))
* 3 By the auto refresh setting of GX Configurator-MB, transfer the automatic communication function
buffer area data to the MELSECNET/H remote I/O module. (
This section (3) (d))
* 4 Automatic communication parameters are set from GX Configurator-MB.
10
This section (3) (c))
DEDICATED
INSTRUCTIONS
(
PROGRAMMING
* 1 Set the MELSECNET/H link refresh by refresh parameters in the network parameters.
APPENDICES
TROUBLESHOOTING
11
INDEX
9
9.3 Program Example for Use in MELSECNET/H Remote I/O Network
9.3.1 Automatic communication parameter
9 - 27
9
PROGRAMMING
2) When not using GX Configurator-MB
The automatic communication function buffer area data in the QJ71MB91 are
transferred to the PLC CPU on the MELSECNET/H remote master station with
the REMTO/REMFR instruction.
I/O signals are transferred by MELSECNET/H link refresh and MELSECNET/
H link scan.
MELSECNET/H remote master station
MELSECNET/H
remote master module
PLC CPU
Device
MELSECNET/H
link refresh*1
*4
MELSECNET/H link scan*2
R
MODBUS slave device
(station No.1)
MELSECNET/H remote I/O station (setting target)
MELSECNET/H
remote I/O module
Device
R
MODBUS slave device
(station No.2)
QJ71MB91
CH2 Automatic communication
function buffer input area
Coil
000001
015001
2000H
*3
2100H
016024
64 words
213FH
2FFFH
4000H
4A00H
065536
CH2 Automatic
communication
function buffer
output area
*3
100 words
4A63H
4FFFH
Holding register
400001
400100
465536
Figure 9.27 Communications (When not using GX Configurator-MB)
* 1 Set the MELSECNET/H link refresh by refresh parameters in the network parameters.
(
This section (3) (b))
* 2 Set the MELSECNET/H link scan by the network range assignment in the network parameters.
(
This section (3) (b))
* 3 Automatic communication parameters are set from sequence program. (
This section (4))
* 4 The automatic communication function buffer area data in the QJ71MB91 are transferred to the
PLC CPU on the MELSECNET/H remote master station with the REMTO/REMFR instruction.
(
9 - 28
This section (4))
9.3 Program Example for Use in MELSECNET/H Remote I/O Network
9.3.1 Automatic communication parameter
9
PROGRAMMING
9
PROGRAMMING
(b) Settings
Table9.7 Automatic communication parameter settings
Setting value
0380H to 0381H (896 to 897)
1H
Target station No.
0382H (898)
2
Request interval timer value
0383H (899)
600 (6 s)
Response monitoring timer value
0384H (900)
500 (5 s)
Setting parameter existence
10
DEDICATED
INSTRUCTIONS
Buffer memory address
CH2 automatic
0100H
communication Type specification of the target MODBUS
device
parameter 1
0385H (901)
Head buffer memory address
0386H (902)
2100H
0387H (903)
15000
0388H (904)
1024
038CH to 038DH (908 to 909)
1H
Target station No.
038EH (910)
1
Request interval timer value
038FH (911)
Response monitoring timer value
0390H (912)
number
device head
Access points
Setting parameter existence
CH2 automatic
communication
parameter 2
Type specification of the target MODBUS
0391H (913)
device
Head buffer memory address
Write
Target MODBUS
setting
number
Access points
device head
TROUBLESHOOTING
Target MODBUS
setting
11
0 (Issue request immediately after
receiving response from slave.)
500 (5 s)
0005H
(Write holding registers)
0395H (917)
4A00H
0396H (918)
0
0397H (919)
100
9.3 Program Example for Use in MELSECNET/H Remote I/O Network
9.3.1 Automatic communication parameter
INDEX
Read
(Read coils)
APPENDICES
Setting item
9 - 29
9
PROGRAMMING
(3) Parameter settings
The following setting is required to perform the communication shown in (2).
(a) Intelligent function module switch setting
Set the intelligent function module switches for the setting target, QJ71MB91, as
shown below. (
Section 6.6)
1) When using GX Configurator-MB
Figure 9.28 Intelligent function module switch setting (When using GX Configurator-MB)
2) When not using GX Configurator-MB
Figure 9.29 Intelligent function module switch setting (When not using GX Configurator-MB)
(b) Network parameter
Set the following network parameters for the MELSECNET/H remote master
station by GX Developer.
1) Network type
: MNET/H (Remote master)
2) Starting I/O No.
: 0000H
3) Network No.
:1
4) Total stations
:1
5) Mode
: On line
6) Network range assignment
• When using GX Configurator-MB
Figure 9.30 Network range assignment (When using GX Configurator-MB)
9 - 30
9.3 Program Example for Use in MELSECNET/H Remote I/O Network
9.3.1 Automatic communication parameter
PROGRAMMING
9
PROGRAMMING
• When not using GX Configurator-MB
10
Figure 9.31 Network range assignment (When not using GX Configurator-MB)
DEDICATED
INSTRUCTIONS
7) Refresh parameters
• When using GX Configurator-MB
TROUBLESHOOTING
11
Figure 9.32 Refresh parameters (When using GX Configurator-MB)
APPENDICES
• When not using GX Configurator-MB
INDEX
9
Figure 9.33 Refresh parameters (When not using GX Configurator-MB)
9.3 Program Example for Use in MELSECNET/H Remote I/O Network
9.3.1 Automatic communication parameter
9 - 31
9
PROGRAMMING
(c) Automatic communication parameter
1) When using GX Configurator-MB
Set CH2 Automatic communication parameters in the Initial setting of GX
Configurator-MB. (
Section 8.4.1)
Set the values shown in the settings. (
This section (2) (b))
Figure 9.34 CH2 Automatic communication parameter
2) When not using GX Configurator-MB
Set automatic communication parameters from the sequence program.
(
This section (4) (b))
(d) Auto refresh setting
Configure the following auto refresh setting on GX Configurator-MB.
Figure 9.35 Auto refresh setting
Remark
When not using GX Configurator-MB, program the processing equivalent to the
auto refresh setting using REMTO/REMFR instructions.
(
9 - 32
This section (4) (c))
9.3 Program Example for Use in MELSECNET/H Remote I/O Network
9.3.1 Automatic communication parameter
PROGRAMMING
The following is an example of the sequence program required to perform the
communication shown in (2).
(a) Interlock program example for MELSECNET/H
Provide interlocks using the link status of the MELSECNET/H remote master
station (host) and MELSECNET/H remote I/O station (other station).
The example below shows an interlock for a communication program, which uses
the link status (SB47, SB49) of the MELSECNET/H remote master station and the
link status (SW70, SW74, SW78) of the MELSECNET/H remote I/O station
(Station No. 1).
10
DEDICATED
INSTRUCTIONS
(4) Program example
PROGRAMMING
9
SB49: Host station data
link status
SW70: Other station baton
pass status
SW74: Other station data
link status
TROUBLESHOOTING
11
SB47: Host station baton
pass status
SW78: Other station parameter
communication status
APPENDICES
SB20: Network module status
Program for automatic communication: refer to (4) (b) in this section
Figure 9.36 Interlock program example for MELSECNET/H
Set the following value as timer constant K
INDEX
9
.
Table9.8 Value of timer constant K
Baton pass status
(T0, T2)
(Sequence scan time
4) or more
(Sequence scan time
3) or more
Cyclic transmission status
Parameter communication status
(T1, T3, T4)
Reason: To prevent the control from stopping even if the network detects an
instantaneous error due to a cable problem, noise or any other condition
Note that the above "4" and "3" represent standard values.
POINT
For details on interlock programs for the MELSECNET/H remote master station
and MELSECNET/H remote I/O station, refer to the following manual.
Q Corresponding MELSECNET/H Network System Reference Manual
(Remote I/O network)
9.3 Program Example for Use in MELSECNET/H Remote I/O Network
9.3.1 Automatic communication parameter
9 - 33
9
PROGRAMMING
(b) Program example for automatic communication parameter setting
The program example is shown below.
When automatic communication parameters are set from GX Configurator-MB,
this program is not required.
Initializing automatic communication
parameter setting area
Setting CH2 Automatic Module
command communication READY
operation status
Setting parameter
existence(1H)
Target station No. (2)
Request interval timer value
(6s)
Response monitoring timer
value (5s)
Type specification of the target
MODBUS R device
(0100H)
Head buffer memory address
(2100H)
CH2 Automatic
communication
parameter 1
R
Target MODBUS device
head number (15000)
Access points (1024 points)
Setting parameter
existense(1H)
Target station No. (1)
Request interval timer value
(0)
Response monitoring timer
value (5s)
Type specification of the target
MODBUS R device
(0005H)
CH2 Automatic
communication
parameter 2
Head buffer memory address
(4A00H)
R
Target MODBUS device
head number (0)
Access points (100 points)
Writing parameters by REMTO instruction.
When REMTO instruction is
completed normally
Processing when ZP.REMTO instruction is completed in error
When REMTO instruction is
completed with an error
CH2 Automatic communication parameter
setting, normally completed
Processing for Automatic comm. parameter setting, normally completed
CH2 Automatic communication parameter
setting, error completed
Processing for Automatic comm. parameter setting, error completed
*1
Figure 9.37 Program example when mounted to MELSECNET/H remote I/O station
9 - 34
9.3 Program Example for Use in MELSECNET/H Remote I/O Network
9.3.1 Automatic communication parameter
PROGRAMMING
* 1 The following is a processing example for error completion.
The following is a processing example in which, from the QJ71MB91 buffer memory (address:
0C18H to 0C19H), the PLC CPU on the MELSECNET/H remote master station obtains data such
as an error code identified in the automatic communication parameter setting.
Figure 9.38 Program example for error completion of automatic communication parameters
PROGRAMMING
9
10
Processing for
error completion
The following data are stored in the PLC CPU on the MELSECNET/H remote master station:
D250: CH2 Automatic communication parameter error code
D251: CH2 Automatic communication parameter setting result
(c) Program example for data transfer between QJ71MB91 and PLC CPU
The program example is shown below.
When data transfer between the QJ71MB91 and PLC CPU is set in the Auto
refresh setting of GX Configurator-MB and network parameter, this program is not
required.
Module
READY
CH2 Automatic
communication
operation
status
REMFR
instruction
completion
REMFR
REMFR
instruction instruction
completion result
Module CH2 Automatic REMTO
READY communication instruction
operation
completion
REMFR instruction
completion
Refresh of the automatic
communication function buffer
input area
Take corrective action for error completion, referring to Q
Corresponding MELSECNET/H Network System Reference
Manual (Remote I/O Network).
REMTO instruction
completion
Refresh of the automatic
communication function buffer
output area
status
REMTO
REMTO
instruction instruction
completion result
11
TROUBLESHOOTING
Processing on completion
of REMFR instruction
APPENDICES
Processing for error completion
DEDICATED
INSTRUCTIONS
Processing for normal completion
INDEX
9
Take corrective action for error completion, referring to Q
Corresponding MELSECNET/H Network System Reference
Manual (Remote I/O Network).
Figure 9.39 Data transfer program example when mounted to MELSECNET/H remote I/O station
9.3 Program Example for Use in MELSECNET/H Remote I/O Network
9.3.1 Automatic communication parameter
9 - 35
9
PROGRAMMING
POINT
1.
2.
After execution of the REMTO/REMFR instruction, several scans are required
until the read/write of actual data is completed.
Completion of the REMTO/REMFR instruction can be confirmed by the
completion device of the instruction.
To set parameters, write the set values to the buffer memory by the REMTO
instruction, and then execute the parameter setting request after the
completion device of the REMTO instruction turns ON.
Remark
For details of the REMTO instruction and the troubleshooting for error completion
of the instruction, refer to the following manual:
Q Corresponding MELSECNET/H Network System Reference Manual
(Remote I/O network)
9 - 36
9.3 Program Example for Use in MELSECNET/H Remote I/O Network
9.3.1 Automatic communication parameter
PROGRAMMING
9
PROGRAMMING
9.3.2 MODBUS(R) device assignment parameter
(1) System configuration
The following system configuration is used for the program example in which
MODBUS device assignment parameters are set to the QJ71MB91 on a
MELSECNET/H remote I/O station.
10
DEDICATED
INSTRUCTIONS
MELSECNET/H remote master station *1
GX Developer
11
TROUBLESHOOTING
MELSECNET/H (remote I/O network)
Setting target
MELSECNET/H
remote I/O station
(Station No.1)
QJ71MB91
RUN
NEU.
SD
CH1
RD
MODBUS master device
ERR.
NEU.
SD C H2
RD
CH1
RS- 232
SDA
1
SG
RDA
2
3
4
5
( FG)
RDB
CH2
RS- 422
/ 485
6
7
APPENDICES
SDB
( FG)
CH2
QJ71MB91 (Slave function)
(Station No.1)*2
Figure 9.40 System configuration example for the MODBUS
RS-422/485
device assignment parameter setting
* 1 The MELSECNET/H remote master station is installed in slot 0 of the base unit with the Start I/O
No. set as "00H".
* 2 The QJ71MB91 is to be mounted in slot 0 of the base unit with the head I/O number set to “00H”.
INDEX
9
Remark
For details on construction and parameter setting of the MELSECNET/H remote I/
O network, refer to the following manual.
Q Corresponding MELSECNET/H Network System Reference Manual
(Remote I/O network)
9.3 Program Example for Use in MELSECNET/H Remote I/O Network
9.3.2 MODBUS(R) device assignment parameter
9 - 37
9
PROGRAMMING
(2) Communications
In the program example shown in this section, the following MODBUS device
assignment parameters are set for the setting target , QJ71MB91.
(a) MODBUS device assignment parameter assignment diagram
MELSECNET/H remote I/O
station device
Y0
Y100
Y2FF
Output (Y)
R
MODBUS device
Coil
512 points
512 points
000001
000512
Y1FFF
065536
Data register (D)
Input register
D0
300001
D3500
303500
5500 points
5500 points
D8999
308999
D12287
365536
QJ71MB91 buffer memory
User free area
5000H
Holding register
400001
1024 points
401024
5500H
1024 points
58FFH
5FFFH
465536
Figure 9.41 MODBUS
9 - 38
device assignment parameter settings
9.3 Program Example for Use in MELSECNET/H Remote I/O Network
9.3.2 MODBUS(R) device assignment parameter
9
PROGRAMMING
9
Setting item
Input register
Buffer memory address
Setting value
009DH
Device code
0900H (2304)
Head device number
0901H (2305)
0100H
Head coil number
0902H (2306)
0 (000001)
Assignment points
0903H (2307)
512 (points)
Device code
0980H (2432)
Head device number
0981H (2433)
3500
Head input register number
0982H (2434)
3499 (303500)
Assignment points
0983H (2435)
5500 (points)
Device code
09C0H (2496)
Head device number
09C1H (2497)
5500H
Head holding register number
09C2H (2498)
0 (400001)
Assignment points
09C3H (2499)
1024 (points)
10
(Y: Output)
DEDICATED
INSTRUCTIONS
Coil assignment 1
device assignment parameter settings
00A8H
(D: Data register)
assignment 1
F000H
(User free area)
APPENDICES
Holding register
11
TROUBLESHOOTING
Table9.9 MODBUS
PROGRAMMING
(b) Settings
INDEX
assignment 1
9.3 Program Example for Use in MELSECNET/H Remote I/O Network
9.3.2 MODBUS(R) device assignment parameter
9 - 39
9
PROGRAMMING
(3) Parameter settings
The following setting is required to perform the communication shown in (2).
(a) Intelligent function module switch setting
Set the intelligent function module switches for the setting target, QJ71MB91, as
shown below. (
Section 6.6)
Figure 9.42 Intelligent function module switch setting
(b) Network parameter
Set the following network parameters for the MELSECNET/H remote master
station by GX Developer.
1) Network type
: MNET/H (Remote master)
2) Starting I/O No.
: 0000H
3) Network No.
:1
4) Total stations
:1
5) Mode
: On line
6) Network range assignment
Figure 9.43 Network range assignment
7) Refresh parameters
Figure 9.44 Refresh parameters
9 - 40
9.3 Program Example for Use in MELSECNET/H Remote I/O Network
9.3.2 MODBUS(R) device assignment parameter
PROGRAMMING
9
1) When using GX Configurator-MB
Set MODBUS device assignment parameter in the Initial setting of GX
Configurator-MB. (
Section 8.4.2)
10
This section (2) (b))
DEDICATED
INSTRUCTIONS
Set the values shown in the settings. (
PROGRAMMING
(c) MODBUS device assignment parameter
Figure 9.45 MODBUS
device assignment parameter
2) When not using GX Configurator-MB
Set MODBUS device assignment parameter from the sequence program.
(
This section (4))
APPENDICES
TROUBLESHOOTING
11
INDEX
9
9.3 Program Example for Use in MELSECNET/H Remote I/O Network
9.3.2 MODBUS(R) device assignment parameter
9 - 41
9
PROGRAMMING
(4) Program example
The following is an example of the sequence program required to perform the
communication shown in (2).
(a) Interlock program example for MELSECNET/H
Provide interlocks using the link status of the MELSECNET/H remote master
station (host) and MELSECNET/H remote I/O station (other station).
The example below shows an interlock for a communication program, which uses
the link status (SB47, SB49) of the MELSECNET/H remote master station and the
link status (SW70, SW74, SW78) of the MELSECNET/H remote I/O station
(Station No. 1).
SB47: Host station baton
pass status
SB49: Host station data
link status
SW70: Other station baton
pass status
SW74: Other station data
link status
SW78: Other station parameter
communication status
SB20: Network module status
R
Program for MODBUS device assignment : refer to (4) (b) in this section
Figure 9.46 Interlock program example for MELSECNET/H
Set the following value as timer constant K
.
Table9.10 Value of timer constant K
Baton pass status
(T0, T2)
(Sequence scan time
4) or more
(Sequence scan time
3) or more
Cyclic transmission status
Parameter communication status
(T1, T3, T4)
Reason: To prevent the control from stopping even if the network detects an
instantaneous error due to a cable problem, noise or any other condition
Note that the above "4" and "3" represent standard values.
POINT
For details on interlock programs for the MELSECNET/H remote master station
and MELSECNET/H remote I/O station, refer to the following manual.
Q Corresponding MELSECNET/H Network System Reference Manual
(Remote I/O network)
9 - 42
9.3 Program Example for Use in MELSECNET/H Remote I/O Network
9.3.2 MODBUS(R) device assignment parameter
9
PROGRAMMING
(b) Program example for MODBUS device assignment parameter setting
The program example is shown below.
Initializing MODBUS R device assignment
parameter setting area
Setting
Module
command READY
PROGRAMMING
9
10
Head coil number (0)
Coil
assignment1
Assignment points
(512 points)
11
Device code (00A8H)
Head device number (3500)
Head input register number
(3499)
Assignment points
(5500 points)
Input
register
assignment1
TROUBLESHOOTING
Head device number (0100H)
DEDICATED
INSTRUCTIONS
Device code (009DH)
Device code (F000H)
holding
register
Head holding register
assignment1
number (0)
Assignment points
(1024 points)
Writes set values into QJ71MB91
buffer memory with REMTO instruction
Turns ON MODBUS R device assignment
parameter setting request when REMTO
instruction is normally completed.
APPENDICES
Head device number (5500H)
Error completion of REMTO instruction
INDEX
MODBUS R device assignment
parameter setting request,
normally completed
Processing fot normal completion
MODBUS R device assignment
parameter setting request,
error completed
Processing fot error completion *1
Figure 9.47 MODBUS
device assignment parameter setting program example when mounted to MELSECNET/H remote I/O station
9.3 Program Example for Use in MELSECNET/H Remote I/O Network
9.3.2 MODBUS(R) device assignment parameter
9 - 43
9
PROGRAMMING
* 1 The following is a processing example for error completion.
The following is a processing example in which, from the QJ71MB91 buffer memory (address:
0C13H to 0C15H), the PLC CPU on the MELSECNET/H remote master station obtains data such
as an error code identified in the MODBUS
device assignment parameter setting.
Processing for normal completion
Processing for error completion
Processing on completion
of REMFR instruction
Processing for
error completion
The following data are stored in the PLC CPU on the MELSECNET/H remote master station:
D10000: MODBUS R device assignment parameter error code
D10001: Error, device type
D10002: Error, assigned group No.
Figure 9.48 Program example for error completion of MODBUS
device assignment parameters
POINT
1.
2.
After execution of the REMFR/REMTO instruction, several scans are required
until the read/write of actual data is completed.
Completion of the REMFR/REMTO instruction can be confirmed by the
completion device of the instruction.
To set parameters, write the set values to the buffer memory by the REMTO
instruction, and then execute the parameter setting request after the
completion device of the REMTO instruction turns ON.
Remark
For details of the REMTO instruction and the troubleshooting for error completion
of the instruction, refer to the following manual:
Q Corresponding MELSECNET/H Network System Reference Manual
(Remote I/O network)
9 - 44
9.3 Program Example for Use in MELSECNET/H Remote I/O Network
9.3.2 MODBUS(R) device assignment parameter
10
DEDICATED INSTRUCTIONS
CHAPTER10 DEDICATED INSTRUCTIONS
The dedicated instructions make programming easy for use of the intelligent function
module functions.
PROGRAMMING
9
10
DEDICATED
INSTRUCTIONS
10.1 Dedicated Instruction List
Table10.1 Dedicated instruction list
Dedicated
Description
instruction
MBRW
Reads or write MODBUS
device data from or a slave.
Communications with a slave in the request message format
MBREQ
containing any given protocol data unit.
Reference
Section 10.2
Section 10.3
11
TROUBLESHOOTING
The following are the dedicated instructions supported by the QJ71MB91.
(1) Interlock for dedicated instruction execution
Execute dedicated instructions in the following I/O signal status.
Dedicated
instruction
X0: Module READY
APPENDICES
X0
Figure 10.1 Interlock for dedicated instruction execution
POINT
INDEX
Until completion of the dedicated instruction execution, do not change each of the
data used for the dedicated instruction (control data, argument, etc.)
10.1 Dedicated Instruction List
10 - 1
10
DEDICATED INSTRUCTIONS
10.2 MBRW Instruction
This instruction allows reading or writing of MODBUS
device data to a slave.
Table10.2 Devices available for the MBRW instruction
Available device
Setting
Internal device
data
MELSECNET/H direct J
\
Intelligent function
module
File register
Bit
Word
Bit
Word
U
Index register
Constant
Zn
K,H,$
\G
(S1)
-
-
(D1)
-
-
(S2)
-
-
(D2)
Others
-
[Instruction symbol] [Execution condition]
Command
Z.MBRW
Un
(S1)
(D1)
(S2)
(D2)
ZP.MBRW
Un
(S1)
(D1)
(S2)
(D2)
Z.MBRW
Command
ZP.MBRW
Figure 10.2 Configuration of MBRW instruction
(1) Setting data
Table10.3 Setting data of MBRW instruction
Setting data
"Un"
(S1)
Setting details
Head I/O number of the module
(00H to FEH: Upper 2 digits of the I/O number in 3-digit notation)
Head number of the device where control data is stored
Setting side*1
Data type
User
User, system
*2*3
(D1)
Read data storage device
System
(S2)*2*3
Write data storage device
User
BIN 16 bits
The device that is turned ON for one scan on completion of the
(D2)
instruction
System
Bit
(D2)+1 also turns ON when the instruction completes in error.
* 1 The setting side is as described below.
User
: Data are set by the user before dedicated instruction execution.
System: The PLC CPU stores the result of dedicated instruction execution.
* 2 Specify a dummy device if "00H: No specification" is selected in the Type specification of the target
MODBUS device ((S1)+8).
* 3 Data are stored in RTU format (binary) regardless of the frame mode (RTU mode/ASCII mode).
Local devices and program-based file registers are not available as the devices used for
setting data.
10 - 2
10.2 MBRW Instruction
10
DEDICATED INSTRUCTIONS
Table10.4 Control data of the MBRW instruction
(S1)+0
-
(S1)+1
(S1)+2
Completion
status
MODBUS
exception code
Setting data
Specify 0.
The status of the instruction completion is stored.
0 : Normal completion
Other than 0: Error completion (error code) (
(S1)+3
Channel
(S1)+4
-
(S1)+5
(S1)+6
Target station
No.
-
Setting side*1
0
User
-
System
-
System
Section 11.4.3)
An exception code from a slave is stored.
0
:Slave processing normally completed
Other than 0: Slave processing completed in error (exception code)
(
Setting range
11
Section 11.4.2)
Specify the target channel.
1: RS-232
2: RS-422/485
Specify 0.
Specify the station number of the target slave.
0
:Broadcast
1 to 247: Target slave station number
Specify 0.
1, 2
User
0
User
0 to 247
User
0
User
[Response monitoring timer value (Target station No. is 1 to 247)]
Specify the time for monitoring a response from the target device (slave). (Unit: 10ms)
0
:30 seconds
2 to 65535: Set value (Response monitoring timer value = set value x 10ms)
(S1)+7
Response
[Broadcast delay value (Target station No. is 0)]
monitoring timer
Specify the wait time after broadcast transmission. (unit: 10 ms)
value/Broadcast
0
:400 ms
delay value
2 to 65535: Set value (Broadcast delay value = set value x 10ms)
0
2 to 65535*2
User
INDEX
For details on the Response monitoring timer value/Broadcast delay value, refer to
the following.
Section 7.2.1 (4)
Specify the type of the read/write target MODBUS
(
b8 b7
Read target
Setting value
(S1)+8
Type
specification of
the target
MODBUS
device
device.
This section (2) (a))
b15
10
b0
Write target
Target MODBUS
00H
No specification
01H
Coil
02H
Input
04H
Input register
05H
Holding register
07H
Extended file register
device type
TROUBLESHOOTING
Item
APPENDICES
Device
DEDICATED
INSTRUCTIONS
(2) Control data
PROGRAMMING
9
0001H
0005H
0007H
0100H
0200H
0400H
0500H
0505H
0700H
User
(Continued on next page)
10.2 MBRW Instruction
10 - 3
10
DEDICATED INSTRUCTIONS
Table10.4 Control data of the MBRW instruction (Continued)
Setting
Device
Item
(S1)+9
Target file
number
Specify a file number when the target MODBUS
register.
Target
Specify the head number of the read target MODBUS
device.
Specify the lower 5 digits of the device head number.
The device head number is specified as "(Actual device number) - 1".
(Except for the file number and device number of the extended file register)
(Example) Specify "31" when accessing Input 100032.
MODBUS
device head
number
Target MODBUS
device type
specification
Access
points
(S1)+11
device is the extended file
01H: Coil
02H: Input
04H: Input register
05H: Holding register
07H: Extended file register
Unit
side*1
0 to 65535*2*3
User
0 to 65535*2*3
User
0 to 2000*3
User
-
System
0 to 65535*2*4
User
0 to 65535*2*4
User
0 to 1968*4
User
1 to 125
User
Allowable access points
Bit
This section (2) (a)
Word
(S1)+12
Read data
storage size
Set the word size of the read data stored in the argument (D1) and later fields.
(S1)+13
Target file
number
Specify a file number when the target MODBUS
register.
Target
Specify the head number of the write target MODBUS
device.
Specify the lower 5 digits of the device head number.
The device head number is specified as "(Actual device number) - 1".
(Except for the file number and device number of the extended file register)
(Example) Specify "31" when accessing Holding register 400032.
MODBUS
device head
number
(S1)+14
Setting range
Set the read points of the MODBUS
device.
The units used for the setting of access points are as follows:
Read setting
(S1)+10
Setting data
device is the extended file
(S1)+15
Write setting
Set the write points of the MODBUS
device.
The units used for the setting of access points are as follows:
Target MODBUS
device type
specification
Access
points
Unit
01H: Coil
02H: Input
Bit
04H: Input register
05H: Holding register
07H: Extended file register
Word
Allowable access points
This section (2) (a)
Set the word size of the write data stored in the argument (S2) and later fields.
Set "1" for the case of read only.
When the access target MODBUS
(S1)+16
10 - 4
Write data
storage size
device (Type specification of the target
MODBUS
device) is "01H: Coil" or "02H: Input", pay attention to the following.
• Set the "Number of access points/16 (rounded up to the nearest integer)" as the
write data storage size.
• When the number of write points is a number with a fraction, the excess area is
ignored. (Refer to Point.)
10.2 MBRW Instruction
DEDICATED INSTRUCTIONS
9
POINT
When accessing a bit device (coil, input) of a slave, the fraction bit is handled as
described below.
[Read]
When the read access points is 35
<Read data storage device (D1)>
b15
to
11
<Target slave device area>
b15
b0
to
b0
Read
D100
D101
D102
10
DEDICATED
INSTRUCTIONS
: Data are set by the user before dedicated instruction execution.
System: The PLC CPU stores the result of dedicated instruction execution.
* 2 When specifying a value of 32768 (8000H) or more in a sequence program, set the value in
hexadecimal.
* 3 Set "0" for the case of write only.
* 4 Set "0" for the case of read only.
116640 to 116625
116656 to 116641
116672 to 116657
TROUBLESHOOTING
User
PROGRAMMING
* 1 The setting side is as described below.
Remaining area is masked by "0".
<Write data storage device (S2)>
to
b0 Write
b15
<Target slave device area>
to
b15
APPENDICES
[Write]
When the write access points is 5
b0
122544 to 122529
D300
Remaining area is ignored.
INDEX
10
10.2 MBRW Instruction
10 - 5
10
DEDICATED INSTRUCTIONS
(a) Type specification of the target MODBUS
device
The table below shows the possible combinations in the target MODBUS device
type specification ((S1)+8) and the valid ranges of the access points.
Any other combinations are not applicable to the Type specification of the target
MODBUS
device type ((S1)+8).
Table10.5 Possible combinations of target MODBUS
Target MODBUS
device type specification
Valid access point range
device type specification
Function code
Setting
Read target
value
Write target
Read points
1 to 2000
0100H
Coil
01
Read coils
0200H
Input
02
Read discrete inputs
0400H
Input register
04
Read input registers
0500H
Holding register
03
Read holding registers
0700H
Extended file register*1
20
Read file record
Coil
15
Write multiple coils
-
Holding register
16
Write multiple registers
-
Extended file register*1
21
Write file record
-
Holding register
23
Read/Write multiple registers
0001H
*2
0005H
*2
No specification
0007H
*2
0505H
*3
Holding register
No specification
points
1 to 2000
points
1 to 125
points
1 to 125
points
1 to 124
points
Write points
-
-
-
-
1 to 1968
points
1 to 123
points
1 to 122
points
1 to 125
1 to 121
points
points
* 1 Read File Record (FC: 20) and Write File Record (FC: 21) allows access to multiple areas in one
transmission, however, only one area is accessible in one transmission when using this dedicated
instruction.
* 2 In the case of broadcast, only 0001H (Write multiple coils), 0005H (Write multiple registers) and
0007H (Write file record) can be set.
* 3 Simultaneous execution of read and write with a single instruction is allowed only for 0505H (Read/
Write multiple registers).
10 - 6
10.2 MBRW Instruction
DEDICATED INSTRUCTIONS
9
PROGRAMMING
(3) Function
MODBUS device data are read from or written to the slave specified by the
target station number of the control data.
Processing by the automatic communication function can be performed from a
sequence program at any given timing.
(b) Number of simultaneously executable instructions
The number of simultaneously executable dedicated instructions is one instruction
per channel. (Including the MBREQ instruction)
Create a sequence program so that the number of dedicated instructions to be
simultaneously executed will not exceed the limit.
Failure to do so may cause the following:
1) When execution of two or more MBRW instructions are attempted:
The executed instructions are ignored.
10
DEDICATED
INSTRUCTIONS
(a) Processing details
11
TROUBLESHOOTING
The following explains the functions of the MBRW instruction.
(c) Frame mode setting
The frame mode (RTU mode/ASCII mode) is set with the intelligent function
module switch. (
Section 6.6)
APPENDICES
2) When the MBRW instruction execution is attempted during execution of the
MBREQ instruction:
An error occurs when the MBRW instruction is executed.
(d) Start, Address, Error check and END fields of the protocol data unit
The QJ71MB91 automatically enters values in Start, Address, Error check and
END fields of the protocol data unit.(
Section 4.2.1)
(e) Data to be stored in read/write data storage devices
Data are stored in RTU format (binary) regardless of the frame mode (RTU mode/
ASCII mode).
10.2 MBRW Instruction
10 - 7
INDEX
10
10
DEDICATED INSTRUCTIONS
(f) When using the automatic communication function and dedicated instructions on
the same channel
Dedicated instructions are not executed while the Response monitoring timer/
Broadcast delay of the automatic communication function is active.
When the automatic communication function and dedicated instructions are used
on the same channel, set appropriate automatic communication parameters and
create a proper sequence program so that each of dedicated instructions can
executed in the right timing.(
Section 9.2.3)
(g) Confirmation of execution status
Whether the MBRW instruction is being executed, or completed normally or not
can be checked by the MODBUS exception code ((S1)+2), the completion
device (D2) specified as set data, and the error completion device ((D2)+1).
END processing
END processing
END processing
END processing
Sequence program
ON
MBRW instruction
Completion of MBRW
instruction execution
OFF
ON
Completion device (D2) OFF
ON Error
completion
Normal
completion
Error completion device OFF
(D2)+1
1 scan
Figure 10.3 MBRW instruction timing chart
The completion device (D2) turns ON in the END processing of the scan after
completion of the MBRW instruction, and turns OFF in the next END processing.
The error completion device ((D2)+1) turns ON in the END processing of the scan
after error completion of the MBRW instruction, and turns OFF in the next END
processing. (The device remains OFF in the case of normal completion.)
10 - 8
10.2 MBRW Instruction
DEDICATED INSTRUCTIONS
(a) When a dedicated instruction completes in error
When the dedicated instruction completes in error, the error completion device
(D2)+1 turns ON and an error code is stored in the completion status area (S1)+1.
(b) When processing on a slave completes in error
When the processing on a slave completes in error, an exception code is stored in
(S1)+2.
(c) Confirmation of error details
Check the error code and exception code referring to the following, and take
corrective actions.
10
DEDICATED
INSTRUCTIONS
(4) Error
PROGRAMMING
9
11
Item
Error code
7300H or later
Exception code
QCPU User's Manual
(Hardware Design, Maintenance and Inspection)
Section 11.4.3
Section 11.4.2
APPENDICES
03E8H to 4FFFH
Reference
TROUBLESHOOTING
Table10.6 Error code and exception code for the MBRW instruction execution
INDEX
10
10.2 MBRW Instruction
10 - 9
10
DEDICATED INSTRUCTIONS
(5) Program example
This section provides an example program in which device data are read from and
written to the holding register of the slave (Station No. 1) on channel 1 as shown
below.
This frame made shall be the RTU mode.
The I/O signals of the QJ71MB91 are X/Y00 to X/Y1F.
R
MODBUS
slave device
(station No. 1)
QJ71MB91
(master)
QJ71MB91
RUN
NEU.
CH1
SD
RD
ERR.
NEU.
SD
RD
CH2
CH1
RS-232
SDA
SG
SDB
(FG)
RDA
1
2
3
4
5
(FG)
RDB
CH2
RS-422
/485
6
7
CH1(RS-232)
R
QJ71MB91
(master)
MODBUS
slave device
R
Device memory
MODBUS device
400500
D100
32 points
400531
100 points
e
D199
rit
W
W0000
411000
Re
ad
100 points
32 points
W001F
411099
Figure 10.4 Configuration example for MBRW instruction execution
10 - 10
10.2 MBRW Instruction
10
DEDICATED INSTRUCTIONS
Fixed to "0"
Dedicated Module
instruction READY
start
command
Completion status is cleared to "0".
Target channel is specified.
Fixed to "0"
Target station No. (station No. 1)
DEDICATED
INSTRUCTIONS
10
R
MODBUS exception code
is cleared to "0".
Response monitoring timer value
(30s)
Target MODBUS R device type
specification
(0505H: Holding register read/write)
Target file No.
R
Target MODBUS device head
number
TROUBLESHOOTING
11
Fixed to "0"
Read
setting
PROGRAMMING
9
Access points (100 points)
APPENDICES
Read data storage size is cleared
to "0".
Target file No.
R
Target MODBUS device head
number
Write
setting
Access points (32 points)
Write data storage size (32 points)
Processing for normal completion
Processing for error completion
Normal completion (M0: ON, M1: OFF)
Error completion (M0: ON, M1: ON)
Figure 10.5 MBRW instruction program example
10.2 MBRW Instruction
10 - 11
INDEX
Execution of dedicated instruction
Instruction
completion
10
DEDICATED INSTRUCTIONS
Remark
In this sample program, the following MODBUS
communication with the slave.
frames are used for the
Request message format (Master (QJ71MB91)
Address field
Function code
Slave)
Data
Target station Function code
Read head
(17H)
No.
holding register
(01H)
number
(2AF7H)
(H)
(L)
Read points
n
(0064H)
(H)
(L)
(H)
Number
Write device
of bytes
data
mx2
1
(0040H) (value of W0000)
Number of
write points
m
(0020H)
Write head
holding register
number
(01F3H)
(L)
(H)
(L)
(H)
Write device
data
m
(value of W001F)
(H)
(L)
(L)
(Number of bytes m x 2)
Response message format (Slave
Address field
Master (QJ71MB91))
Function code
Host station No. Function code
(17H)
(01H)
Data
Number
of bytes
nx2
(C8H)
Read device data
1
(value of 411000)
(H)
(L)
Read device data
n
(value of 411099)
(H)
(Number of bytes n x 2)
10 - 12
10.2 MBRW Instruction
(L)
10
DEDICATED INSTRUCTIONS
9
PROGRAMMING
10.3 MBREQ Instruction
This instruction allows communications with a slave in the request message format
containing any given protocol data unit.
Table10.7 Devices available for the MBREQ instruction
Internal device
data
MELSECNET/H direct J
\
Intelligent function
module
File resister
Bit
Word
Bit
Word
U
Index register
Constant
Zn
K,H,$
\G
(S1)
-
-
(S2)
-
-
(D1)
-
-
(D2)
Others
11
TROUBLESHOOTING
Setting
DEDICATED
INSTRUCTIONS
10
Available device
-
[Instruction symbol] [Execution condition]
Command
Z.MBREQ
Un
(S1)
(S2)
(D1)
(D2)
ZP.MBREQ
Un
(S1)
(S2)
(D1)
(D2)
APPENDICES
Z.MBREQ
Command
ZP.MBREQ
INDEX
Figure 10.6 Configuration of MBREQ instruction
10.3 MBREQ Instruction
10 - 13
10
DEDICATED INSTRUCTIONS
(1) Setting data
Table10.8 Setting data of MBREQ instruction
Setting data
"Un"
Setting details
Head I/O number of the module
(00H to FEH: Upper 2 digits of the I/O number in 3-digit notation)
(S1)
Head number of the device where control data is stored
(S2)
Request message storage head device*2
(D1)
Response message storage head device*2
Setting side*1
Data type
User
User, system
BIN 16 bits
User
System
The device that is turned ON for one scan on completion of the
(D2)
instruction
System
Bit
(D2)+1 also turns ON when the instruction completes in error.
* 1 The setting side is as described below.
User : Data are set by the user before dedicated instruction execution.
System: The PLC CPU stores the result of dedicated instruction execution.
* 2 Data is stored in RTU format (binary) regardless of the frame mode (RTU mode/ASCII mode).
Local devices and program-based file registers are not available as the devices used for
setting data.
Remark
For details on the protocol data unit, refer to the following:
Section 4.2
10 - 14
10.3 MBREQ Instruction
10
DEDICATED INSTRUCTIONS
(2) Control data
Table10.9 Control data of the MBREQ instruction
(S1)+0
-
(S1)+1
Completion
status
(S1)+2
Setting data
Specify 0.
Setting
range
side*1
0
User
-
System
0
User
0
: Normal completion
Section 11.4.3)
Specify 0.
11
Specify the target channel.
(S1)+3
Channel
1: RS-232
1, 2
User
0
User
0 to 247
User
0
User
2: RS-422/485
(S1)+5
(S1)+6
Target station
No.
Specify 0.
Specify the station number of the target slave.
0
: Broadcast*2
1 to 247: Slave station No.
-
Specify 0.
APPENDICES
(S1)+4
[Response monitoring timer value (Target station No. is 1 to 247)]
Specify the time for monitoring a response from the target device (slave).
(Unit: 10ms)
0
monitoring
timer value/
Broadcast
delay value
: 30 seconds
2 to 65535: Set value (Response monitoring timer value = set value x 10ms)
0
[Broadcast delay value (Target station No. is 0)]
Specify the wait time after broadcast transmission. (Unit: 10ms)
0
2 to 65535
User
*3
: 400ms
2 to 65535: Set value (Broadcast delay value = set value x 10ms)
INDEX
Response
(S1)+7
10
The status of the instruction completion is stored.
Other than 0: Error completion (error code) (
-
Setting
DEDICATED
INSTRUCTIONS
Item
TROUBLESHOOTING
Device
PROGRAMMING
9
For details on the Response monitoring timer value/Broadcast delay value,
refer to the following.
Section 7.2.1 (4)
* 1 The setting side is as described below.
User : Data are set by the user before dedicated instruction execution.
System: The PLC CPU stores the result of dedicated instruction execution.
* 2 For function codes that can be broadcast, refer to the following:
Section 4.1
* 3 When specifying a value of 32768 (8000H) or more in a sequence program, set the value in
hexadecimal.
10.3 MBREQ Instruction
10 - 15
10
DEDICATED INSTRUCTIONS
(3) Request message storage devices
Table10.10 Request message storage devices
Device
Item
Setting data
Setting
Setting
range
side*1
1 to 253
User
Set the size (function code + data) of the request message to be sent in byte
(S2)+0
Request
units.
message size Set the size for transmission in the RTU mode regardless of the frame mode
(RTU mode/ASCII mode).
Set the contents (function code + data) of the request message to be sent.
Data must be stored in RTU format (binary) regardless of the frame mode
(RTU mode/ASCII mode).
(Example) When sending a request message to read the data of holding
registers 440001 and 440002 with Read Holding Registers (FC: 03)
<Frame of request message to be sent (in ASCII mode)>
Function code
Function code
Data
Head holding register number
0
(30H)
3
(33H)
9
(39H)
(H)
(L)
(H)
C
(43H)
4
(34H)
Read points
0
(30H)
0
(30H)
0
(30H)
0
(30H)
2
(32H)
Transmission order
(S2)+1
to
(S2)+n
(L)
5 bytes
(Calculated with the size for transmission in RTU mode regardless of the frame mode)
Request
Figure 10.7 Request message example
message
As shown on
left
<Contents in request message storage devices and their order>
b15
(S2)+0
b8
b15
(S2)+1
b8
b15
b7
Request message
size (=5 bytes)
b0
03H
b8
b7
00H
b15
b0
05H
9CH
(S2)+2
(S2)+3
b7
00H
b0
Request message
40H
b8
00H (ignored)
b7
b0
02H
Send data storage order
(Request message is sent in order from lower-order to
higher-order bytes starting with the smallest device number.)
Figure 10.8 Contents in request message storage devices and their order
* 1 The setting side is as described below.
User : Data are set by the user before dedicated instruction execution.
System: The PLC CPU stores the result of dedicated instruction execution.
10 - 16
10.3 MBREQ Instruction
User
DEDICATED INSTRUCTIONS
POINT
DEDICATED
INSTRUCTIONS
10
11
TROUBLESHOOTING
2.
The request message data stored in request message storage devices
"(S2)+1 to (S2)+n" are sent in order of L (lower) to H (upper) bytes, starting
with the lowest device number.
When the request message size is an odd number, the last upper byte of the
request message storage device is ignored. (The data are not sent.)
APPENDICES
1.
PROGRAMMING
9
INDEX
10
10.3 MBREQ Instruction
10 - 17
10
DEDICATED INSTRUCTIONS
(4) Response message storage devices
Table10.11 Response message storage devices
Device
Item
Setting data
Setting
Setting
range
side*1
-
System
Set the size (function code + data) of the received response message in byte
(D1)+0
Response
units.
message size The size for the RTU mode is stored regardless of the frame mode (RTU mode/
ASCII mode).
Set the contents (function code + data) of the received response message.
Data are stored in RTU format (binary) regardless of the frame mode (RTU mode/
ASCII mode).
(Example) When a response message of Read Holding Registers (FC: 03) is
received
<Received response message frame (in ASCII mode)>
Data
Function code
Function code
Number of
read bytes*2
0
(30H)
3
(33H)
0
(30H)
4
(34H)
(H)
(L)
(H)
(L)
Device data
1
0
(30H)
0
0
(30H) (30H)
Device data
2
5
1
(35H) (31H)
2
(32H)
3
(33H)
4
(34H)
Reception order
(D1)+1
to
(D1)+m
(H)
(L)
6 bytes
(Calculated with the size for reception in RTU mode regardless of frame mode)
Response
Figure 10.9 Response message example
message
As shown
on left
<Contents in response message storage devices and their order>
b15
(D1)+0
b8
b15
(D1)+1
b8
b15
b7
b8
b7
b0
Response message
00H
b8
34H
b0
Response message size
(=6 bytes)
03H
05H
b15
b0
06H
04H
(D1)+2
(D1)+3
b7
00H
b7
b0
12H
Receive data storage order
(Response message is stored in order from lower-order to
higher-order bytes starting with the smallest device number.)
Figure 10.10 Contents in response message storage devices and their order
* 1 The setting side is as described below.
User : Data are set by the user before dedicated instruction execution.
System: The PLC CPU stores the result of dedicated instruction execution.
* 2 The number of read bytes is 4 from "2 (Read points)
2 = 4".
10 - 18
10.3 MBREQ Instruction
System
DEDICATED INSTRUCTIONS
(5) Function
(a) Processing details
This instruction allows communication with a slave specified by the target station
number in the control data, using the request message format containing any
given protocol data unit.
(b) Number of simultaneously executable instructions
The number of simultaneously executable dedicated instructions is one instruction
per channel. (Including the MBRW instruction)
Create a sequence program so that the number of dedicated instructions to be
simultaneously executed will not exceed the limit.
Failure to do so may cause the following:
1) When execution of two or more MBREQ instructions are attempted:
The executed instructions are ignored.
2) When the MBREQ instruction execution is attempted during execution of the
MBRW instruction:
An error occurs when the MBREQ instruction is executed.
10
DEDICATED
INSTRUCTIONS
2.
The received response message is stored in response message storage
devices "(D1)+1 to (D1)+n" in order of L (lower) to H (upper) bytes, starting
with the lowest device number.
When the response message size is an odd number, the last upper byte of
the response message storage device is overwritten with "0".
11
TROUBLESHOOTING
1.
APPENDICES
POINT
PROGRAMMING
9
(c) Frame mode setting
The frame mode (RTU mode/ASCII mode) is set with the intelligent function
module switch. (
INDEX
10
Section 6.6)
(d) Start, Address, Error check and END fields of the protocol data unit
The QJ71MB91 automatically enters values in Start, Address, Error check and
END fields of the protocol data unit. (
Section 4.2.1)
(e) Data to be stored in request/response message storage devices
Data are stored in RTU format (binary) regardless of the frame mode (RTU mode/
ASCII mode).
10.3 MBREQ Instruction
10 - 19
10
DEDICATED INSTRUCTIONS
(f) When using the automatic communication function and dedicated instructions on
the same channel
Dedicated instructions are not executed while the Response monitoring timer/
Broadcast delay of the automatic communication function is active.
When the automatic communication function and dedicated instructions are used
on the same channel, set appropriate automatic communication parameters and
create a proper sequence program so that each of dedicated instructions can be
executed in the right timing.(
Section 9.2.3)
(g) Confirmation of execution status
Whether the MBREQ instruction is being executed, or completed normally or not
can be checked by the completion device (D2) specified as set data, and the error
completion device ((D2)+1).
END processing
END processing
END processing
END processing
Sequence program
Completion of MBREQ
instruction execution
ON
MBREQ instruction
OFF
ON
Completion device (D2) OFF
ON Error
completion
Normal
completion
1 scan
Error completion device OFF
(D2)+1
Figure 10.11 MBREQ instruction timing chart
The completion device (D2) turns ON in END processing of the scan after
completion of the MBREQ instruction, and turns OFF in the next END processing.
The error completion device ((D2)+1) turns ON in the END processing of the scan
after error completion of the MBREQ instruction, and turns OFF in the next END
processing. (The device remains OFF in the case of normal completion.)
(6) Error
(a) When a dedicated instruction completes in error
When the dedicated instruction completes in error, the error completion device
(D2)+1 turns ON and an error code is stored in the completion status area (S1)+1.
(b) Confirmation of error details
Check the error code referring to the following, and take corrective actions.
Table10.12 Error codes for the MBREQ instruction
Item
03E8H to 4FFFH
Error code
7300H or later
10 - 20
10.3 MBREQ Instruction
Reference
QCPU User's Manual
(Hardware Design, Maintenance and Inspection)
Section 11.4.3
DEDICATED INSTRUCTIONS
stored in the response message storage device.(
This section (4))
This instruction completes normally even if the target slave device returns an
exception response.
When the instruction completes normally, check the most significant bit of the
function code in the response message to determine whether the response is
normal or not. (For an error response, the most significant bit in the first byte
of the receive data turns ON.)
In the case of an error response, check the exception code (the second byte
of the receive data) in the response message and take corrective
2.
actions.(
Section 11.4.2)
For the MBREQ instruction, the ACK. and NAK states of the detailed LED
status do not change.
Check whether communication processing completes normally or not by the
3.
response message stored in the response message storage device. (
This section (4))
Pay attention to the following when sending a request message to a slave
with no response message*1 expected. (Excluding the case of broadcast)
• Specify sufficient time in the Response monitoring timer value (S1)+7 for
the slave to process the request message.
• A response monitoring timeout error (error code: 7379H) occurs even if
the instruction is completed normally.
Regard the response monitoring timer timeout error (error code: 7379H)
as normal completion.
4.
* 1 Request messages for which no response message is returned are as follows. (in the case of
MODBUS
standard function)
Switching to the Listen only mode (
Section 4.11.5)
Restart communications option sent to a slave in the Listen only mode
(
Section 4.11.2)
10.3 MBREQ Instruction
10 - 21
10
DEDICATED
INSTRUCTIONS
In the case of the MBREQ instruction, exception codes and function codes
are not stored in the Error log (address: 0CFEH to 0DFFH) of the buffer
memory.
Check the exception and function codes by the response message that is
11
TROUBLESHOOTING
1.
APPENDICES
POINT
PROGRAMMING
9
INDEX
10
10
DEDICATED INSTRUCTIONS
(7) Program example
This section provides a program example for sending a request message (Mask Write
Register (FC: 22)) and writing a value OR-masked with 0008H to holding register
400003 of the slave (Station No. 1) on channel 2.
(a) Operation of the program example
R
MODBUS
slave device
(station No. 1)
QJ71MB91
(master)
QJ71MB91
CH1
RUN
ERR.
NEU.
SD
RD
NEU.
SD
RD
CH2
CH1
RS-232
SDA
SG
SDB
(FG)
RDA
1
2
3
4
5
(FG)
RDB
6
7
CH2
RS-422
/485
CH2 (RS-422 or RS-485)
<OR mask value>
<Holding register 400003>
Mask write (OR)
b15
b5 b3
b0
0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0
b15
b5
b0
b3
1
Figure 10.12 Configuration example for MBREQ instruction execution
(b) Frames to be sent/received with MBREQ instruction (in RTU mode)
1) Request message format (Master (QJ71MB91)
Address field
Function code
Target
station No.
01H
Function code
Slave)
Data
Target holding register number
00H
16H
02H
AND mask value
00H
00H
OR mask value
(0008H)
00H
08H
Transmission order
(H)
(L)
(L)
(H)
(H)
(L)
7 bytes
Figure 10.13 Example of request message format to be sent
2) Response message format
<Normal completion>
Address field
Function code
Host
station No.
01H
Function code
16H
Data
AND mask value
Target holding register number
00H
02H
00H
00H
OR mask value
(0008H)
08H
00H
Reception order
(H)
(L)
(H)
(L)
(H)
7 bytes
Figure 10.14 Response message format to be received (Normal completion)
10 - 22
10.3 MBREQ Instruction
(L)
10
DEDICATED INSTRUCTIONS
9
Function code
Host station No. Function code
01H
Data
Exception
code*1
96H
10
DEDICATED
INSTRUCTIONS
Reception order
2 bytes
Figure 10.15 Response message format to be received (Error completion)
* 1 For details on exception codes, refer to the following:
Section 11.4.2
11
(c) Sequence program
In this program example, the I/O signals of QJ71MB91 are X/Y00 to X/Y1F.
Fixed to "0"
Dedicated Module
instruction READY
start
command
TROUBLESHOOTING
Address field
PROGRAMMING
<Error completion>
Completion status is
cleared to "0".
Target channel is specified.
Fixed to "0"
APPENDICES
Fixed to "0"
Target station No.
(station No. 1)
Fixed to "0"
Response monitoring timer
value (5s)
INDEX
Request message size
Request message
Instruction
completion
*1
Processing for normal completion/response
*1
Execution of dedicated
instruction
Normal completion
(M0: ON, M1: OFF)
Processing for normal completion/error response
Error completion
(M0: ON, M1: ON)
Processing for error completion
* 1 D301.7 is the most significant bit of the function code to be stored in the response message.
The most significant bit of the function code turns ON at the time of error completion.
Figure 10.16 MBREQ instruction program example
10.3 MBREQ Instruction
10 - 23
11
TROUBLESHOOTING
CHAPTER11 TROUBLESHOOTING
This chapter explains the details of errors and corrective actions.
11.1 Troubleshooting
(1) Troubleshooting of errors indicated by LEDs
Table11.1 Troubleshooting list of errors indicated by LEDs
No.
Symptom
Check point
Corrective action
Check the mounting status of the
Switch OFF the power and remount the
QJ71MB91.
QJ71MB91.
Check the power supply capacity.
Replace the power supply module.
Reference
Section 6.1
Section 3.1
If the PLC CPU is faulty, take corrective
Check the PLC CPU for an error.
1
The RUN LED turned off.
actions according to the QCPU User's
Manual (Hardware Design, Maintenance
-
and Inspection).
• Reset the PLC CPU or reapply the
power.
Check for a watch dog timer error (X1F).
• If the problem persists even after the
reset, a possible cause is a hardware
Section 6.4.1
fault. Perform a hardware test, and
replace the QJ71MB91.
Check the operation mode setting value of
the intelligent function module switch.
Check the transmission setting status
Check the setting range of each intelligent
value of the intelligent function module
function module switch, and correct the
switch.
value.
Section 6.6
Check the station number setting value of
the intelligent function module switch.
Check that the QJ71MB91 is not mounted
Mount the QJ71MB91 on a Q-mode
with an A-mode QCPU.
QCPU.
Section 2.1
• Perform the test again after checking
2
The ERR.LED turned on.
Check if the module is in the hardware or
self-loopback test mode.
the mounting status of the QJ71MB91.
• If the ERR.LED turns on again, a
possible cause is a hardware fault.
Section 6.4.1
Section 6.4.2
Replace the QJ71MB91.
This section
Refer to "The RUN LED turned off."
(1)-1
Check if the automatic communication
Refer to "Automatic communication
parameter setting, error compled signal
parameter setting, error completed signal
(X5/XD) is ON.
(X5/XD) turned on."
Check if the MODBUS
device
Refer to "MODBUS
device assignment
assignment parameter setting, error
parameter setting, error completed signal
completed signal (X9) is ON.
(X9) turned on."
This section
(2)-3
This section
(2)-4
(Continued on next page)
11 - 1
11.1 Troubleshooting
11
TROUBLESHOOTING
Table11.1 Troubleshooting list of errors indicated by LEDs (Continued)
Check if the automatic communication
error status signal (X7/XF) is ON.
2
The ERR.LED turned on.
Corrective action
Refer to "Automatic communication error
status signal (X7/XF) turned on."
Turn off the ERR. LED.
When the dedicated instruction is used,
Refer to "Dedicated instruction failed."
check it for an error.
Turn off the ERR. LED.
Check the error code in the error log.
Take corrective actions for the error code.
Turn off the ERR. LED.
Refer to "Communication with target device is not available even if parameter setting
has been completed normally.".
Reference
This section
(2)-7
This section
(3)-2
Section 11.4.1
Section 11.5
This section
(3)-7
Refer to "Automatic communication
When using the automatic communication
operation status signal (X6/XE) does not
function
turn on." or "Automatic communication
This section
(2)-5,(2)-7
error status signal (X7/XF) turned on.".
When using a dedicated instruction
3
The NEU. LED does not
flash.
Refer to "Dedicated instruction is not
executed."
does not return a response message to
the request message."
In use of the slave function, check the
station number in the request message
11
This section
(3)-1
Refer to "The QJ71MB91 slave function
When using the slave function
10
DEDICATED
INSTRUCTIONS
Check point
TROUBLESHOOTING
Symptom
Correct the station number.
that is sent to the QJ71MB91.
This section
(3)-3
CHAPTER 4
APPENDICES
No.
PROGRAMMING
9
Section 6.6
Refer to "Automatic communication
operation status signal (X6/XE) does not
function
turn on." or "Automatic communication
transmission.
The RD LED does not
(2)-5,(2)-7
error status signal (X7/XF) turned on.".
flash during data
4
This section
When using a dedicated instruction
flash during data
reception.
Refer to "Dedicated instruction is not
executed."
(3)-1
Refer to "The QJ71MB91 slave function
When using the slave function
This section
does not return a response message to
the request message."
11.1 Troubleshooting
This section
(3)-3
11 - 2
INDEX
The SD LED does not
When using the automatic communication
11
TROUBLESHOOTING
(2) Troubleshooting of errors indicated by X signals
Table11.2 Troubleshooting of errors indicated by X signals
No.
1
Symptom
Check point
Corrective action
The Module READY
signal (X0) turned off.
This section
Refer to "The RUN LED turned off."
2
4
(1)-1
The Watch dog timer error
signal (X1F) turned on.
The Automatic
3
Reference
Check the Automatic communication
communication parameter parameter error code storage area
setting, error completed
(address: 0C16H/0C18H) in the buffer
signal (X5/XD) turned on.
memory and identify the error code.
The MODBUS
Check the MODBUS
device
Take corrective actions for the error code
and retry.
Section 11.4
device
assignment parameter
assignment parameter error code storage
Take corrective actions for the error code
setting, error completed
area (address: 0C13H) in the buffer
and retry.
signal (X9) turned on.
memory and identify the error code.
Section 11.4
Set the automatic communication
parameters by GX Configurator-MB and
The Automatic
5
Check if the automatic communication
activate them.
function is activated.
Or, set the automatic communication
Section 7.2
communication operation
parameters by a sequence program and
status signal (X6/XE)
activate them.
Section 9.1.1
does not turn on.
Check if the Automatic communication
Refer to "The Automatic communication
parameter setting, error completed signal
parameter setting, error completed signal
(X5/XD) is on.
(X5/XD) turned on."
communication operation
Check if the Automatic communication
Restart the automatic communication
status signal (X6/XE)
stop request (Y6/YE) has been issued.
function.
This section
(2)-3
The Automatic
6
Section 5.2.1
turned off.
Check the Automatic communication
operation status storage area (0C20H to
0C21H/0C22H to 0C23H) in the buffer
memory and identify the parameter
The Automatic
7
communication error
Check if the communication with the target
status signal (X7/XF)
device is possible.
turned on.
number of the error cause.
Take corrective actions according to the
Section 11.4
error code currently stored in the
Automatic communication error storage
area (0C28H to 0C47H/0C48H to 0C67H) or
the exception code sent from the target
slave.
(Continued on next page)
11 - 3
11.1 Troubleshooting
11
TROUBLESHOOTING
Table11.2 Troubleshooting of errors indicated by X signals (Continued)
No.
Symptom
Check point
Corrective action
Reference
• Check the processing time of the target
device.
PROGRAMMING
9
10
• Check if, because of a small request
interval timer value, another request is
from the target device.
• Check if, because of a small response
Check if the timer settings in the automatic
communication parameters are
appropriate.
7
timed out with an error before the target
device returns a response.
Section 7.2.1
For the error, set a larger response
communication function
monitoring timer value.
error status signal (X7/XF)
• Check if the next request was sent
turned on.
11
TROUBLESHOOTING
The Automatic
monitoring timer value, the timer has
DEDICATED
INSTRUCTIONS
transmitted before receiving a response
before completion of the processing of
the target device because of a small
broadcast delay value.
For the error, set a larger broadcast
delay value.
parameters and create a proper sequence
function and dedicated instructions are
program so that each of the dedicated
used on the same channel.
instructions can be executed in the right
Section 9.2.3
timing.
The CH common/CH1
8
error (X1B) or CH2 error
APPENDICES
Set appropriate automatic communication
Check if the automatic communication
This section
Refer to "The ERR. LED turned on."
(1)-2
(X1C) turned on.
Is the slave function used?
MODBUS
device assignment
parameter setting existence signal (XA) is
-
off.
Set the MODBUS
device assignment
parameters by GX Configurator-MB.
Or, set the MODBUS
The MODBUS
9
device
assignment parameter
setting existence signal
(XA) does not turn on.
device
Section 7.3
Section 9.1.2
assignment parameters by a sequence
Is the MODBUS
device assignment
parameter setting completed?
program.
In the setting for the MODBUS
device
assignment parameter starting method on
the intelligent function module switch,
Section 6.6
select "OFF: Start with the default
parameters".
Check if the MODBUS
device
Refer to "MODBUS
device assignment
assignment parameter setting, error
parameter setting, error completed signal
completed signal (X9) is on.
(X9) turned on."
11.1 Troubleshooting
This section
(2)-4
11 - 4
INDEX
When the slave function is not used, the
11
TROUBLESHOOTING
(3) Troubleshooting for other symptoms
Table11.3 Troubleshooting for other symptoms
No.
Symptom
Check point
Check if the dedicated instruction is
started.
Is the PLC CPU in the RUN status?
Check if more than the maximum number
Dedicated instruction is
1
not executed.
of simultaneously executable dedicated
instructions (one per channel) are started.
(The completion device
Check if the dedicated instruction is
(D2) does not turn on.)
completed in error.
Corrective action
Reference
Start the dedicated instruction.
-
Set the PLC CPU to RUN.
-
Complete the dedicated instruction
currently executed, and then retry.
Refer to "Dedicated instruction failed."
CHAPTER 10
This section
(3)-2
• Wait until the response monitoring timer
Check if a dedicated instruction is already
for the dedicated instruction times out.
being executed and the module is waiting
• Check the status of the target device.
for a response from the target device.
• For the error, refer to "Dedicated
This section
(3)-2
instruction failed."
Check the error code and/or exception
code stored in the control data of the
dedicated instruction.
Take corrective actions according to the
error and exception codes, and retry.
CHAPTER 10
Section 11.4
<MBRW instruction>
Modify the device type setting in the
control data so that a function code
Section 10.2
supported by the target device will be
Does the target device support the
issued.
function code?
<MBREQ instruction>
Modify the send data so that a function
code supported by the target device will be
Section 10.3
issued.
In the case of the MBREQ instruction,
2
Dedicated instruction
check if the contents of the request
failed.
message is correct.
Correct the request message and retry.
CHAPTER 4
Section 10.3
• Check the processing time of the target
device.
• Check if, because of a small response
monitoring timer value, the timer has
timed out with an error before the target
Check if the Response monitoring timer/
Broadcast delay of the dedicated
instruction is appropriate.
device returns a response.
For the error, set a larger response
monitoring timer value.
Section 7.2.1
• Check if the next request was sent
before completion of the processing of
the target device because of a small
broadcast delay value.
For the error, set a larger broadcast
delay value.
(Continued on next page)
11 - 5
11.1 Troubleshooting
11
TROUBLESHOOTING
Symptom
Check point
A request message, for which no
response is expected, was sent to a slave
by the MBREQ instruction. (Except for
broadcast)
2
Dedicated instruction
failed.
Corrective action
The response monitoring timer timeout
error (error code: 7379H) may be regarded
as normal completion.
Reference
Section 10.3
(6)
Set appropriate automatic communication
Check if the automatic communication
parameters and create a proper sequence
function and dedicated instructions are
program so that each of the dedicated
used on the same channel.
instructions can be executed in the right
Section 9.2.3
timing.
Refer to "Communication with the target device is not available even if parameter
setting has been completed normally."
Check if the MODBUS
device
This section
(3)-7
Refer to "MODBUS
device assignment
assignment parameter setting existence
parameter setting existence signal (XA)
signal (XA) is on.
does not turn on."
Has the QJ71MB91 returned any
Confirm the exception code and take
exception code?
corrective actions.
This section
(2)-9
10
DEDICATED
INSTRUCTIONS
No.
11
TROUBLESHOOTING
Table11.3 Troubleshooting for other symptoms (Continued)
PROGRAMMING
9
Section 11.4.2
function does not return a
the error code.
response message to the
request message.
Are the contents of the request message
sent from the master to the QJ71MB91
correct?
Take corrective actions for the error code.
Correct the request message to be issued
from the master.
Is the station number in the request
Specify the station number of the
message sent from the master to the
QJ71MB91 in the request message to be
QJ71MB91 correct?
sent from the master.
Refer to "Communication with the target device is not available even if parameter
setting has been completed normally."
Section 11.4.1
CHAPTER 4
CHAPTER 4
This section
(3)-7
Check the Error log (address: 0CFEH to
0DFFH) in the buffer memory and identify
4
An error is found in the
Take corrective actions for the error code.
Section 11.4.3
the error code.
error log.
Refer to "Communication with the target device is not available even if parameter
setting has been completed normally."
This section
(3)-7
(Continued on next page)
11.1 Troubleshooting
11 - 6
INDEX
3
The QJ71MB91's slave
APPENDICES
Check the Error log (address: 0CFEH to
0DFFH) in the buffer memory and identify
11
TROUBLESHOOTING
Table11.3 Troubleshooting for other symptoms (Continued)
No.
Symptom
Check point
Corrective action
Reference
Check the exception code returned from
Received exception error
the slave by the Error log (address: 0CFEH
count
to 0DFFH) in the buffer memory, and
Section 11.3
Section 11.4.1
examine the slave to solve the problem.
Refer to the corrective actions for the
No-response count
response monitoring timer timeout error
(error code: 7378H to 7379H).
Received NAK count
Master
Received busy count
Examine the slave that returned the error,
and solve the problem.
Section 11.3
Section 11.4.3
-
• When there is another master on the
5
same network, disconnect the master.
The diagnostic counter
• When a response is returned after
has counted up.
occurrence of the response monitoring
Message discard count
timer timeout error, refer to the
corrective actions for the error (error
Section 11.3
Section 11.4.3
code: 7378H to 7379H).
• When any of the other stations has sent
a message without receiving a request,
examine the station.
Message discard count
Slave
There is no problem as messages
addressed to other stations are discarded.
Section 11.3
Check the Error log (address: 0CFEH to
Exception error count
0DFFH) in the buffer memory and take
Section 11.4.1
corrective actions for the error code.
(Continued on next page)
11 - 7
11.1 Troubleshooting
11
TROUBLESHOOTING
Symptom
Check point
Bus communication error
count
Corrective action
Check the Error log (address: 0CFEH to
0DFFH) in the buffer memory and take
Section 11.4.1
corrective actions for the error code.
Refer to the corrective actions for the
Character overrun error count
Reference
character overrun error (error code:
7399H)
Section 11.3
Section 11.4.3
• If it is caused by connecting the module
to the online network, powering it on
11
and accessing the network, do not
perform such kind of operation. No
5
The diagnostic counter
Master/
has counted up.
Slave
specific action is necessary if there is no
problem.
• If it is caused by turning off, resetting or
Data discard count
disconnecting the device in
transmission from the line, reset, do not
10
This section
(3)-7
TROUBLESHOOTING
No.
DEDICATED
INSTRUCTIONS
Table11.3 Troubleshooting for other symptoms (Continued)
PROGRAMMING
9
perform such kind of operation during
transmission. No specific action is
necessary if there is no problem.
APPENDICES
• If the message is erroneous, refer to
"Communication with the target device
is not available even if parameter setting
has been completed normally.".
Failed transmission count
Refer to the corrective actions for the CS
signal OFF error (error code: 7403H)
Section 11.4.3
Check the Error log (address: 0CFEH to
Communication error occurred.
0DFFH) in the buffer memory and take
Section 11.4.1
An error is found in the
6
communications event
INDEX
corrective actions for the error code.
Refer to the corrective actions for the
Character overrun error occurred.
character overrun error (error code:
Section 11.4.3
7399H)
log.
Message error occurred.
Check the Error log (address: 0CFEH to
0DFFH) in the buffer memory and take
Processing interrupt occurred.
Section 11.4.1
corrective actions for the error code.
If there is a problem with the setting,
Is the station number setting correct?
correct the intelligent function module
Section 6.6
switch setting and reset the module.
Communication with the
7
target device is not
Check if the transmission settings of the
available even if
QJ71MB91 are consistent with those of
parameter setting has
the target device.
been completed normally.
Is the frame mode setting (RTU mode/
ASCII mode) correct?
Check the settings again and if there is a
problem with the setting, correct the
intelligent function module switch setting
Section 6.6
and reset the module.
If there is a problem with the setting,
correct the intelligent function module
Section 6.6
switch setting and reset the module.
(Continued on next page)
11.1 Troubleshooting
11 - 8
11
TROUBLESHOOTING
Table11.3 Troubleshooting for other symptoms (Continued)
No.
Symptom
Check point
Is the communication cable between the
QJ71MB91 and the target device securely
connected?
Section 3.2
communication cable used.
Section 3.3
Are the specifications of the
Confirm the specifications of the
Section 3.2
communication cable in use correct?
communication cable used.
Section 3.3
Check the specifications of each device,
and examine the wiring.
Section 6.5.2
Check the communication target device.
target device is not
• Check for errors.
available even if
• Check if the device is ready for
been completed normally.
Section 6.5
Check the specifications of the
correct?
parameter setting has
cable.
correct?
are used with RS-422/485, is the wiring
7
Securely connect the communication
Reference
Is the communication cable wiring
When both of 2-wire and 4-wire devices
Communication with the
Corrective action
operation.
• Check if it attempts to communicate with
If a problem is identified on the
communication target device, take
-
corrective actions.
the QJ71MB91.
Check for any other masters if the
QJ71MB91 is the master.
Only one master is allowed on the
MODBUS
system. Disconnect the other
-
master.
When the QJ71MB91 is the master, check
if the communication target device is a
MODBUS
slave device.
Set a MODBUS
slave device as the
communication target.
-
When the QJ71MB91 is a slave, check if
the communication target device is a
MODBUS
master device.
Check the communication target device.
• Check for errors.
• Check if the device is ready for
operation.
Set a MODBUS
master device as the
communication target device.
-
If a problem is identified on the
communication target device, take
-
corrective actions.
The interval of the
communications with the
• It takes time to send concurrently issued
slave in the automatic
communication function is
longer than the time set by
8
the automatic
communication
parameter, Request
requests as they are processed in
Check if some send requests by the
automatic communication function and
dedicated instruction were concurrently
issued on the QJ71MB91 side.
sequence.
Reduce the load on the QJ71MB91.
• Set appropriate automatic
Section 9.2.3
communication parameters and create
a proper sequence program so that
interval timer value.
each of dedicated instructions can be
The time to complete the
executed in the right timing.
dedicated instruction is
• Check the processing performance of
too long.
Check if it takes time for the target device
to respond.
the communication target device.
• If a problem is identified on the
-
communication target device, take
corrective actions.
(Continued on next page)
11 - 9
11.1 Troubleshooting
11
TROUBLESHOOTING
9
Symptom
Check point
Corrective action
Reference
The processing time must be within the
Check the specifications using the
processing time performance expression
of the QJ71MB91 slave function.
The QJ71MB91 responds
performance expression.
The processing time may be slower than
Appendix 2
the result of the performance expression if
two channels are used simultaneously.
slowly.
When accessing the PLC CPU device in
the slave function, check if too many
accesses to the PLC CPU are made from
10
Reduce the load of the PLC CPU.
-
11
APPENDICES
TROUBLESHOOTING
other modules or the sequence program.
INDEX
9
range indicated by the result of the
DEDICATED
INSTRUCTIONS
No.
PROGRAMMING
Table11.3 Troubleshooting for other symptoms (Continued)
11.1 Troubleshooting
11 - 10
11
TROUBLESHOOTING
11.2 Checking QJ71MB91 Status
This section explains how to check the QJ71MB91 status.
Table11.4 Status checking method
Method
Reference
LEDs on QJ71MB91
This section (1)
Monitor/Test screen of GX Configurator-MB
This section (2)
System monitor screen of GX Developer
This section (3)
Input signals (X)
This section (4)
Buffer memory
This section (5)
(1) LEDs on QJ71MB91
Whether an error is occurring or not can be checked by the LEDs on the QJ71MB91.
(
Section 6.3)
Detailed error check is performed as shown in (2) and subsequent sections.
The LED status on the QJ71MB91 can also be confirmed by the LED status area in
the buffer memory. (address: 0C05H)
LED status area (address: 0C05H)
b15 b14 b13 b12 b11 b10 b9
b8
b7
b6
b5
b4
b3
b2
b1
Unused
b0
1/0
0 : Off
1: On
ERR.LED
Figure 11.1 Configuration of LED status area
(2) Monitor/Test screen of GX Configurator-MB
GX Configurator-MB has a monitor/test screen for the status display and testing of the
QJ71MB91.
Check the status of the QJ71MB91 on the Monitor/test screen. (
11 - 11
11.2 Checking QJ71MB91 Status
Section 8.6)
TROUBLESHOOTING
(3) System monitor screen of GX Developer
The module status of the QJ71MB91 can be confirmed on the System monitor screen.
(a) Confirming the status on Module’s Detailed Information of GX Developer
10
1) Starting procedure
[Diagnostics]
[System monitor]
DEDICATED
INSTRUCTIONS
GX Developer
PROGRAMMING
9
Module's Detailed Information
APPENDICES
TROUBLESHOOTING
11
Figure 11.2 Module's Detailed Information
INDEX
11
11.2 Checking QJ71MB91 Status
11 - 12
11
TROUBLESHOOTING
2) Display data
Table11.5 Displayed data of Module's Detailed Information
Item
Module
Description
Module Name
Displays the model name of the target module.
I/O Address
Displays the head I/O number of the target module.
Implementation
Position
Product information
Module access
Displays the slot position where the module is mounted.
Displays the serial No. and function version of the target module.*1
Displays Enable when the Module READY signal (X0) is on and the Watch dog timer error
(X1F) is off.
Module information
Status of I/O Address
Displays whether or not the module parameterized by the user matches the mounted
Verify
module.
Present Error
Displays the error code of the latest error. (
Error Display
Error display
Error contents
- Disposal
Section 11.4)
Displays the latest 16 error codes that are stored in the Error log (address: 0CFEH to
0DFFH) of the buffer memory.
Contents
Displays the error contents and disposal for the error code selected in Error Display.*2
Disposal
* 1 The alphabet at the end of the Product information indicates the function version of the module.
The function version of the QJ71MB91 is available from B.
Example: The end character of "B" indicates that the module is of function version B.
* 2 Display of the contents and disposal is available on GX Developer Version 8.29F or later.
11 - 13
11.2 Checking QJ71MB91 Status
TROUBLESHOOTING
9
PROGRAMMING
(b) Confirming the status on H/W Information of GX Developer
The H/W Information can be confirmed on GX Developer 8.29F or later.
1) Starting procedure
GX Developer
[Diagnostics]
[System monitor]
10
H/W Information
DEDICATED
INSTRUCTIONS
Module's Detailed Information
Figure 11.3 H/W information
2) Display data
(H/W LED Information)
The detailed LED status of the QJ71MB91 is displayed.
The displayed values correspond to those in the Detailed LED status storage
area (address: 0006H /0007H) of the buffer memory.
CH1 side Detailed LED status storage area (address: 0006H)
b15 b14 b13 b12 b11 b10 b9 b8
1/0 Unused (Fixed to 0) 1/0 1/0 1/0
b7
b6
b5
Unused (Fixed to 0)
b4 b3 b2 b1 b0
1/0 1/0 1/0 1/0 1/0
0: Off
1: On
CH1 ACK.
CH1 C/N
CH1 NAK
CH1 P/S
CH1 NEU.
CH1 PRO.
CH1 Exception
code presence
CH1 SIO
C/1 ERR.
CH2 side Detailed LED status storage area (address: 0007H)
b15 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0
1/0 Unused (Fixed to 0) 1/0 1/0 1/0 Unused (Fixed to 0) 1/0 1/0 1/0 1/0 1/0
0: Off
1: On
CH2 ACK.
CH2 C/N
CH2 NAK
CH2 P/S
CH2 NEU.
CH2 PRO.
CH2 Exception
code presence
CH2 SIO
CH2 ERR.
Figure 11.4 Detailed LED status storage area
11.2 Checking QJ71MB91 Status
APPENDICES
TROUBLESHOOTING
11
INDEX
11
11 - 14
11
TROUBLESHOOTING
Table11.6 Display data of H/W information
No.
Status signal
Description
name
Lit
Unlit
When it is ON (1)
When it is OFF (0)
0
C/N*2
Status of access with PLC CPU
1
P/S*2
Parity error or sum check error status Error occurred
Normal
2
PRO.*2
Communication protocol error status
Normal
3
SIO*2
SIO error status
C/1 ERR.*2
4
(*1)
Normal
Request message analysis error
Framing error or overrun error
occurred
CH common or CH1 side error
Intelligent function module switch
occurred
setting error, parameter error, etc.
CH2 ERR.*2
Normal
Normal
CH2 side error occurred
5
6
(Unused)
7
Master : Communication not
Master : Communication processing
processed/Communication
normally completed
8
ACK.
Normal completion
Slave : Request message
processing completed in error
Slave : Request message not
processing normally
processed/Request
completed
message processing
completed in error
Master : Communication not
Master : Communication processing
processed/Communication
completed in error
9
NAK
Error completion
processing normally
Slave : Request message
processing completed in
completed
Slave : Request message not
error
processed/Request
message normally completed
Master : Communication not
A
NEU.
Neutral status
processed
Slave
Master : Communication in processing
Slave : Request message in
: Wait for request message
processing
B
C
(Unused)
D
E
F
n E-RES.
Presence of error response
Error response occurred
Normal
* 1 This status signal turns on if data write is requested to the PLC CPU while online change is
disabled in the intelligent function module switch setting (
Section 6.6) of GX Developer.
It also turns on when an error occurs in access between the QJ71MB91 and the PLC CPU.
* 2 This status signal does not automatically turn off even if the cause of the error is removed.
To turn this off, perform the processing for turning off the LED after removing the error cause.
(
11 - 15
Section 11.5)
11.2 Checking QJ71MB91 Status
TROUBLESHOOTING
(H/W SW Information)
The intelligent function module switch status of the QJ71MB91 is displayed.
The displayed values correspond to those in the intelligent function module switch setting
status (address:0C00H to 0C04H) of the buffer memory.
10
Table11.7 Display of H/W SW information
Reference
1
CH1 MODE
Switch 1: CH1 operation mode setting status
2
1 CONFIG
Switch 2: CH1 transmission setting status
3
CH2 MODE
Switch 3: CH2 operation mode setting status
4
2 CONFIG
Switch 4: CH2 transmission setting status
5
ST NO.
DEDICATED
INSTRUCTIONS
Description
name
Section 6.6
11
TROUBLESHOOTING
No.
Status signal
PROGRAMMING
9
Switch 5: CH1/CH2 Station No. setting status
(4) Input signals (X)
The status of the QJ71MB91 can be confirmed by the input signals shown below.
Input
Description
signal
X1B
CH common/CH1 error
X1C
CH2 error
X1F
Watch dog timer error
Error type
Reference
APPENDICES
Table11.8 Input signals for status check
General
X5
XD
H / W error
CH1 Automatic communication parameter setting,
error completed
Section 11.1
CH2 Automatic communication parameter setting,
Automatic
error completed
communication
function
X7
CH1 Automatic communication error status
XF
CH2 Automatic communication error status
X9
MODBUS
device assignment parameter setting,
error completed
MODBUS
device
assignment function
(5) Buffer memory
The QJ71MB91 status can be confirmed with the buffer memory.
• Detailed LED status (
This section(3)(b))
• Error confirmation (
Section 11.4)
11.2 Checking QJ71MB91 Status
11 - 16
INDEX
11
11
TROUBLESHOOTING
11.3 Checking the Communication Status of QJ71MB91
The QJ71MB91 counts the number of times that errors occur during communication.
The communication status of QJ71MB91 can be checked by this counter (diagnostic
counter).
(1) Diagnostic counter
(a) Master function
Table11.9 List of diagnostic counters (Master function)
Buffer memory
Item
Description
CH1
Counts the number of messages sensed on the line.
Bus message count
The bus message count is in an exclusive relationship with the bus
communication error count.
CH2
0F00H
0F40H
(3840)
(3904)
Counts the number of error messages sensed on the line.
"Error messages" include the following:
• CRC/LRC error message
• Overrun/parity error
Bus communication error count
• Short frame (less than 3 bytes)
0F01H
0F41H
• Character overrun (256 bytes or more)
(3841)
(3905)
Counts the number of times that exception errors are received.
0F0EH
0F4EH
(excluding the case of broadcast)
(3854)
(3918)
Messages other than the above are counted by the bus message count.
(The bus communication error count is in an exclusive relationship with
the bus message count.)
Received exception error count
Received NAK count*1*2
Received busy count*2
Character overrun error count
Counts the number of times that NAK responses were received from
0F11H
0F51H
slaves.
(3857)
(3921)
Counts the number of times that busy responses were received from
0F12H
0F52H
slaves.
(3858)
(3922)
Counts the number of times that the request message size exceeded the
0F02H
0F42H
upper limit.
(3842)
(3906)
Counts the number of times that a response message was discarded, for
Message discard count
example, when a message from an unexpected station number was
received.
Data discard count
Failed transmission count
0F03H
0F43H
(3843)
(3907)
Counts the number of times that illegal data (e.g. frames not configured in
0F04H
0F44H
the stipulated response message format) was discarded.
(3844)
(3908)
Counts the number of times that transmission of request messages
0F05H
0F45H
failed. (e.g. when no cable is connected)
(3845)
(3909)
Counts the number of times that there was no response from a slave
No-response count
after request message transmission. (Number of response monitoring
0F0FH
0F4FH
timer timeouts)
(3855)
(3919)
It does not count for broadcast request messages.
Broadcast count
11 - 17
Counts the number of times that request messages were broadcast.
11.3 Checking the Communication Status of QJ71MB91
0F10H
0F50H
(3856)
(3920)
TROUBLESHOOTING
PROGRAMMING
9
* 1 The NAK count defined by the MODBUS protocol is stored in the Received NAK count.
Note that this count is different from the NAK LED on the QJ71MB91.
* 2 It does not count when the request message is sent by the MBREQ instruction.
DEDICATED
INSTRUCTIONS
10
APPENDICES
TROUBLESHOOTING
11
INDEX
11
11.3 Checking the Communication Status of QJ71MB91
11 - 18
11
TROUBLESHOOTING
(b) Slave function
Table11.10 List of diagnostic counters (Slave function)
Buffer memory
SubItem
Description
function*1
Counts the number of messages sensed on the line.
Bus message count
The bus message count is in an exclusive relationship with
0011
the bus communication error count.
CH1
CH2
0F00H
0F40H
(3840)
(3904)
Counts the number of error messages sensed on the line.
"Error messages" include the following:
• CRC/LRC error message
• Overrun/parity error
Bus communication error
count
• Short frame (less than 3 bytes)
0012
• Character overrun (256 bytes or more)
0F01H
0F41H
(3841)
(3905)
0F0AH
0F4AH
(3850)
(3914)
Messages other than the above are counted by the bus
message count. (The bus communication error count is in
an exclusive relationship with the bus message count.)
Exception error count
Counts the number of times that exception errors are
occurred. (excluding broadcast communication messages)
0013
Counts the number of times that messages addressed to
Slave message count
the host were processed.
0014
(Including when reception of broadcast request messages)
Slave no-response count
Counts the number of times that broadcast request
messages were received.
0015
Counts the number of times that the slave returned the
*2
NAK response to the master.
Slave NAK count
0016
The QJ71MB91 always stores "0".
Counts the number of times that the slave returned a busy
Slave busy count
response to the master.
0017
The QJ71MB91always stores "0".
Character overrun error count
Counts the number of times that the request message size
exceeded the upper limit.
0018
0F06H
0F46H
(3846)
(3910)
0F07H
0F47H
(3847)
(3911)
0F08H
0F48H
(3848)
(3912)
0F09H
0F49H
(3849)
(3913)
0F02H
0F42H
(3842)
(3906)
Counts the number of times that request messages are
discarded, for example, due to reasons such as
Message discard count
processing of another request message on a slave or
-
reception of a request message addressed to another
0F03H
0F43H
(3843)
(3907)
station.
Counts the number of times that illegal data (e.g. frames
Data discard count
not configured in the stipulated request message format)
-
was discarded.
Failed transmission count
Counts the number of times that transmission of response
messages failed. (e.g. when no cable is connected)
-
0F04H
0F44H
(3844)
(3908)
0F05H
0F45H
(3845)
(3909)
* 1 Sub-functions in the table show sub-function codes of function code 8.(
Section 4.11)
* 2 The NAK count defined by the MODBUS protocol is stored in the Slave NAK count.
Note that this count is different from the NAK LED on the QJ71MB91.
11 - 19
11.3 Checking the Communication Status of QJ71MB91
TROUBLESHOOTING
9
PROGRAMMING
(2) Count range
Counting is performed up to FFFFH.
Counting is stopped when the count reaches FFFFH.
To continue counting, clear the diagnostic counter.
10
This section (3))
DEDICATED
INSTRUCTIONS
(3) Clearing the diagnostic counters
The diagnostic counters can be cleared by any of the following methods:
(a) Diagnostic counters for Master function (
ThisSection (1)(a))
• Power OFF
ON
• Resetting the PLC CPU
(b) Diagnostic counters for Slave function (
11
ThisSection (1)(b))
• When receiving the Clear Counters and Diagnostic Register *1 (
4.11.6)
• When receiving the Restart communications option *1 (
• When receiving the Clear Overrun Counter and Flag
Section
Section 4.11.2)
TROUBLESHOOTING
(
*2
APPENDICES
(
Section 4.11.6)
• Clearing the buffer memory to "0" by sequence program
• Power OFF
ON
• By resetting the PLC CPU
* 1 The Message discard count, Data discard count and Failed transmission count are not cleared.
* 2 Only the Character overrun error count is cleared.
(4) Cautions
Diagnostic counters are not cleared while the QJ71MB91 is sending data.
Use the values of the diagnostic counters for checking the communication status.
11.3 Checking the Communication Status of QJ71MB91
11 - 20
INDEX
11
11
TROUBLESHOOTING
11.4 Error Codes
11.4.1 Error code storage area
Each error code is stored in any of the following buffer memory areas.
Table11.11 Error code storage area
Buffer memory
Error type
Automatic
Area name
Reference
CH1
CH2
Automatic communication parameter error code storage
0C16H
0C18H
This section
area
(3094)
(3096)
(1)
Automatic communication parameter setting result
0C17H
0C19H
This section
storage area
(3095)
(3097)
(2)
communication
parameter
Parameter
MODBUS
error
information
device assignment parameter error code
storage area
This section
(3091)
(3)
MODBUS
device
assignment
MODBUS
device
parameter
assignment parameter
setting result storage area
0C14H
Error, device type
(3092)
Automatic communication error code storage area
Automatic
(parameters 1 to 32)
communication
(4)
(3093)
0C20H to
(parameters 1 to 32)
This section
0C15H
Error, assigned group No.
Automatic communication operation status storage area
Master
0C13H
0C22H to
0C21H
0C23H
This section
(3104 to
(3106 to
(5)
3105)
3107)
0C28H to
0C48H to
0C47H
0C67H
This section
(3112 to
(3144 to
(6)
3143)
3175)
0CA8H to
0CAAH to
function
function
Automatic communication setting status storage area
(parameters 1 to 32)
Error log
Dedicated
instruction
Error log
Error response code storage area
0CA9H
0CABH
This section
(3240 to
(3242 to
(7)
3241)
3243)
0CFEH to 0DFFH
This section
(3326 to 3583)
(8)
0CFEH to 0DFFH
This section
(3326 to 3583)
(8)
0002H
0004H
(2)
(4)
Section 11.4.2
Slave function
Error log
11 - 21
11.4 Error Codes
11.4.1 Error code storage area
0CFEH to 0DFFH
This section
(3326 to 3583)
(8)
TROUBLESHOOTING
(b) Clear timing
The error code is cleared when the Automatic communication parameter setting,
normally completed (X4/XC) signal turns ON.
(2) Automatic communication parameter setting result storage area
When an automatic communication parameter error occurs with the Automatic
communication parameter setting request/Automatic communication function start
request (Y4/YC) signal ON, the automatic communication parameter number
corresponding to the error is stored in this area.
(a) Storage timing
The automatic communication parameter number is stored when the Automatic
communication parameter setting, error completed (X5/XD) signal turns ON.
(b) Clear timing
The automatic communication parameter number is cleared when the Automatic
communication parameter setting, normally completed (X4/XC) signal turns ON.
(3) MODBUS
10
DEDICATED
INSTRUCTIONS
(a) Storage timing
The error code is stored when the Automatic communication parameter setting,
error completed (X5/XD) signal turns ON.
11
TROUBLESHOOTING
When an error occurs with the Automatic communication parameter setting request/
Automatic communication start request (Y4/YC) signal ON, the corresponding error
code is stored in this area.
APPENDICES
(1) Automatic communication parameter error code storage area
PROGRAMMING
9
device assignment parameter error code storage area
When an occurs with the MODBUS device assignment parameter setting request
(Y8) signal ON, the corresponding error code is stored in this area.
INDEX
11
(a) Storage timing
The error code is stored when the MODBUS device assignment parameter
setting, error completed (X9) signal turns ON.
(b) Clear timing
The error code is cleared when the MODBUS device assignment parameter
setting, normally completed (X8) signal turns ON.
(4) MODBUS
device assignment parameter setting result storage area
When a MODBUS device assignment parameter error occurs with the MODBUS
device assignment parameter setting request (Y8) ON, the device type and assigned
group No. of the error device are stored in this area.
(a) Storage timing
The device type and assigned group No. are stored when the MODBUS
assignment parameter setting, error completed (X9) signal turns ON.
R
device
R
device
(b) Clear timing
The device type and assigned group No. are cleared when the MODBUS
assignment parameter setting, error completed (X8) signal turns ON.
11.4 Error Codes
11.4.1 Error code storage area
11 - 22
11
TROUBLESHOOTING
(c) Error device type to be stored
The following values are stored to show the error device type when the
MODBUS
turns ON.
device assignment parameter setting, error completed (X9) signal
Table11.12 Device type to be stored
Error, device type
Value to be stored
Coil
0001H (1)
Input
0002H (2)
Input register
0004H (4)
Holding register
0005H (5)
(5) Automatic communication operation status storage area
The operation statuses of the automatic communication function are stored in bit
format in correspondence with automatic communication parameters 1 to 32.
The operation statuses are stored in the relevant bit positions, from low-order to highorder bits, in order of automatic communication parameters 1 to 32.
(CH1 Automatic communication operation status storage area)
b15 b14 b13 b12 b11 b10
. . .
b5
b4
5
b3 b2
0C20H
16
15
14
13
12
11
. . .
6
0C21H
32
31
30
29
28
27
. . .
22
21 20
. . .
b5
b4
5
4
3
b1 b0
2
1
19 18 17
(CH2 Automatic communication operation status storage area)
b15 b14 b13 b12 b11 b10
0C22H
16
15
14
13
12
11
. . .
6
0C23H
32
31
30
29
28
27
. . .
22
b3 b2
4
21 20
3
b1 b0
2
1
19 18 17
Number indicates number of automatic
communication parameter.
0: Operating normally/automatic communication parameter not
set/automatic communication function stopped
1: Automatic communication error occurred
Figure 11.5 Configuration of automatic communication function operation status storage area
11 - 23
11.4 Error Codes
11.4.1 Error code storage area
TROUBLESHOOTING
(b) Clear timing
The operation status is cleared at the following timing.
1) When a response message (normal completion) is received from a slave (Only
the corresponding bit turns ON)
2) When the automatic communication function stops (All bits turn OFF.)
3) When the power is turned off and then on again, or when the PLC CPU is reset
(All bits turn OFF)
(c) Interlock with a communication target device
The automatic communication operation status storage area can be utilized as an
area of an interlock signal for errors at a communication target device.
The following shows a program example.
1) Program conditions
The QJ71MB91 is mounted in slot 0 of the base unit with the head I/O No. set
to "0" and automatic communication parameter 1 used.
2) Program example
Command
signal
\
Processing that uses data read from
target device by automatic
communication parameter 1
10
DEDICATED
INSTRUCTIONS
2) When a communication error occurs (Only the corresponding bit turns ON.)
11
TROUBLESHOOTING
1) When a response message (error completion) is received from a slave (Only
the corresponding bit turns ON.)
APPENDICES
(a) Storage timing
The operation status is set at the following timing.
PROGRAMMING
9
Figure 11.6 Interlock with communication target device
(6) Automatic communication error code storage area
When an error occurs in the automatic communication function, the error code
corresponding to automatic communication parameters 1 to 32 is stored in this area.
(a) Storage timing
When the automatic communication operation status bit turns ON, an error code
is stored in the corresponding area.
(b) Clear timing
The automatic communication error code storage area is not cleared.
The error code is overwritten when a new error occurs.
11.4 Error Codes
11.4.1 Error code storage area
11 - 24
INDEX
11
11
TROUBLESHOOTING
(7) Automatic communication setting status storage area
Whether automatic communication parameter settings are present or not is stored in
this area.
(CH1 Automatic communication setting status storage area)
b15 b14 b13 b12 b11 b10
0CA8H
0CA9H
. . .
b5 b4
b3 b2
b1
b0
4
2
1
15
14
13
12
11
. . .
6
32 31
30
29
28
27
. . .
22
21 20
19 18 17
. . .
b5
b4
b3
b2
b1 b0
5
4
3
2
16
5
3
(CH2 Automatic communication setting status storage area)
b15 b14 b13 b12 b11 b10
0CAAH
16
15
14
13
12
11
. . .
6
0CABH
32 31
30
29
28
27
. . .
22
21 20
1
19 18 17
Number indicates that of automatic
communication parameter.
0: Automatic communication parameter
not set
1: Automatic communication parameter set
Figure 11.7 Configuration of automatic communication setting status storage area
(a) Storage timing
Data are stored when the automatic communication function is started. (Only the
corresponding bit turns ON.)
(b) Clear timing
The setting status is cleared at the following timing.
1) When the automatic communication function stops (All bits turn OFF.)
2) When the power is turned off and then on again, or when the PLC CPU is reset
(All bits turn OFF.)
11 - 25
11.4 Error Codes
11.4.1 Error code storage area
TROUBLESHOOTING
9
PROGRAMMING
(8) Error log
Error log area name
Address
Number of errors occurred
0CFEH (3326)
Error log write pointer
0CFFH (3327)
0D00H (3328)
Exception code
0D01H (3329)
Function code
0D02H (3330)
CH
0D03H (3331)
Station No.
Function
Error logs 2 to 32 (same as Error log 1)
0D04H
(3332)
0D07H
(3335)
11
0D08H to 0DFFH
(3336 to 3583)
(a) Number of errors occurred
The number of errors entered to the error log is stored.
If 65536 or more errors have occurred, the count stops at FFFFH (65535).
APPENDICES
Error log 1
Detailed error code
10
DEDICATED
INSTRUCTIONS
Table11.13 Configuration of the Error log area
TROUBLESHOOTING
Up to 32 latest errors are stored in the Error log area as an error history.
(b) Error log write pointer
The number of the latest error log is stored.
0
: No error (No error log entry)
1 to 32 : Error log number where the latest error log was entered
INDEX
11
11.4 Error Codes
11.4.1 Error code storage area
11 - 26
11
TROUBLESHOOTING
(c) Error log (Error logs 1 to 32)
The error log area stores 32 latest errors.
The errors are stored in the chronological order, starting from Error log 1.
If 33 or more errors have occurred, the old error logs are overwritten, starting from
Error log 1 area.
Table11.14 Contents of error log
Function
Master function
Item
Slave function
Automatic
communication function
Others
Dedicated instruction
Stores an error code corresponding to the error that occurred at any timing, such as during processing of a
Detailed error code
request from the master, at power-on or when changing a MODBUS
device assignment parameter.(
Section 11.4.3)
Stores the exception code
Exception code
Stores the exception code that was returned from a
returned to the master
slave in reply to a request message sent by the
when an error occurs for a
automatic communication function or dedicated
request message from the
instruction. (
master. (
Section 11.4.2)
Stores "0".
Section
11.4.2)
Function code
CH
Station No.
Stores the function code from which the error was originated.
Stores "0".
Stores the channel number (1/2) where the error occurred.
Stores "0" is if the channel is not identified.
Stores the station No. of the target station when an error occurred.
Stores "0" is if the station No. is not identified.
Stores the function in which the error occurred:
0:No error
Function
1: Automatic communication function
2: Dedicated instruction
3: Slave function
4: Other
(9) Exception code storage area
When processing requested from the master is completed in error, an exception code
that was returned to the master is stored.(
11 - 27
11.4 Error Codes
11.4.1 Error code storage area
Section 11.4.2)
11
TROUBLESHOOTING
9
"Exception code" is an error code common to the MODBUS protocol, which is
embedded in a response message when a slave returns an error response in reply to a
request message sent from the master.
PROGRAMMING
11.4.2 Exception code list
10
(2) When the QJ71MB91 is a slave
When the target device (master) has received an exception code from the QJ71MB91
(slave), take corrective actions referring to the following.
(a) Exception code storage location
When processing on a slave (QJ71MB91) has completed in error, the exception
code can be confirmed by the Error log area (address: 0CFEH to 0DFFH) in the
buffer memory.
11
TROUBLESHOOTING
When the QJ71MB91 (master) has received an exception code from the target device
(slave), take corrective actions referring to the manual for the target device (slave).
DEDICATED
INSTRUCTIONS
(1) When the QJ71MB91 is a master
(b) Exception code list
The following is a list of exception codes used when the QJ71MB91 is a slave
code
01H
(1)
Corrective action
Error name
Description
Target device (Master side)
Illegal Function
The slave (QJ71MB91) received
an unsupported function code.
Check function codes supported
by the QJ71MB91, and modify the
Illegal Data
The specified address of the
(2)
Address
MODBUS
device is erroneous.
-
request message to be sent.
Check the MODBUS
02H
QJ71MB91 (Slave side)
device
type and size supported by the
INDEX
Exception
-
QJ71MB91, and correct the
specified address in the request
message to be sent.
03H
(3)
A value contained in the data unit
Illegal Data Value of the request message is
incorrect.
Review the data unit of the
-
request message.
Remove the cause of the error
occurred on the QJ71MB91 side.
An unrecoverable error occurred
04H
Slave Device
while the slave (QJ71MB91) was
Review the data unit of the
(4)
Failure
attempting to perform the
request message.
requested action.
APPENDICES
Table11.15 Exception code list
If the QJ71MB91 issued this code,
check the error code in the Error
log area and take corrective
actions.
(
Section 11.4.1 (8))
(Continued on next page)
11.4 Error Codes
11.4.2 Exception code list
11 - 28
11
TROUBLESHOOTING
Table11.15 Exception code list (Continued)
Exception
code
Corrective action
Error name
Description
Target device (Master side)
QJ71MB91 (Slave side)
As the slave is executing another
05H
(5)
Acknowledge
processing, a long duration of time
is required to complete the
requested processing.
06H
Slave Device
(6)
Busy
07H
(7)
As the slave is executing another
processing, the requested
processing cannot be executed.
NAK Error
The requested program function
cannot be executed on a slave.
Not issued by the slave function of the QJ71MB91.
A parity error was detected on a
08H
Memory Parity
(8)
Error
0AH
Gateway Path
(MODBUS
/TCP
(10)
Unavailable
MODBUS
protocol) is not
slave during access to the
extension file register.
The gateway device
available for use.
0BH
(11)
Gateway Target
There is no response from the
Device Failed To
slave devices connected ahead of
Respond
the gateway device.
(c) Error code issued when processing on the slave (QJ71MB91) was completed in
error
If processing on the slave (QJ71MB91) was completed in error, an exception code
is stored in the buffer memory. On the QJ71MB91, an error code is also stored in
the buffer memory to identify the detailed cause. (
Section 11.4.3)
The error code can be checked by the Error log (address: 0CFEH to 0DFFH) in the
buffer memory.(
11 - 29
11.4 Error Codes
11.4.2 Exception code list
Section 11.4.1 (8))
11
TROUBLESHOOTING
9
The "Occurrence" field of the following error code table indicates the cases where each of
the errors may occur:
1) When powering on the PLC or writing parameters, or when errors are common
to master/slave functions or are not included in 2) to 5) below
11
2) When using the master function (Automatic communication function)
TROUBLESHOOTING
3) When using the master function (Dedicated instruction communication
function)
4) When using the slave functions (including entry of MODBUS
assignment parameters)
10
DEDICATED
INSTRUCTIONS
When an error occurs in each processing on the QJ71MB91, the ERR.LED on the
QJ71MB91 lights up, and an error code is stored to the buffer memory of the QJ71MB91.
This section explains respective error details and corrective actions to be taken when an
error occurred.
PROGRAMMING
11.4.3 Error code list
device
5) When performing unit tests (Hardware test/Self-loopback test)
Table11.16 Error code list
Occurrence
Error Name
Description
Corrective Action
1)
2)
3)
4)
5)
Refer to the following manual.
(1000 to 20479)
7301H
(29441)
7302H
(29442)
7303H
(29443)
7304H
(29444)
7305H
(29445)
7307H
(29447)
-
Error code issued by the PLC CPU
QCPU User's Manual
(Hardware Design, Maintenance and
Inspection)
Switch 1 error
The setting of the intelligent function
module switch 1 (CH1 mode setting) is
incorrect.
Review the setting of the intelligent
function module switch 1.
Switch 2 error
The setting of the intelligent function
module switch 2 (CH1 Communication
speed setting / transmission setting) is
incorrect.
Review the setting of the intelligent
function module switch 2.
Switch 3 error
The setting of the intelligent function
module switch 3 (CH2 mode setting) is
incorrect.
Review the setting of the intelligent
function module switch 3.
Switch 4 error
The setting of the intelligent function
module switch 4 (CH2 communication
speed / transmission setting) is
incorrect.
Review the setting of the intelligent
function module switch 4.
Switch 5 error
The setting of the intelligent function
module switch 5 (CH1, 2 station No.
setting) is incorrect.
Review the setting of the intelligent
function module switch 5.
RAM check error
An error was detected by the RAM
check made at power-on.
Any of the QJ71MB91, PLC CPU or
base unit may be faulty.
Perform unit tests.
INDEX
3E8H to 4FFFH
APPENDICES
Error Code
(Continued on next page)
11.4 Error Codes
11.4.3 Error code list
11 - 30
11
TROUBLESHOOTING
Table11.16 Error code list (Continued)
Occurrence
Error Code
Error Name
Description
Corrective Action
1)
Parameter setting using GX
Configurator-MB was applied to the
R
730AH
(29450)
7327H
(29479)
7330H
(29488)
Parameter starting
method error
CPU response
monitoring timer
setting error
PLC CPU while the MODBUS
device assignment parameter starting
method specified by the intelligent
function module switch was set to
"Start with the default parameters".
The CPU response monitoring timer
value in the buffer memory (address:
000DH) is incorrect.
(29489)
MODBUS
device assignment
parameter is incorrect.
MODBUS
device
upper limit value
over error
(29490)
7333H
(29491)
4)
5)
• When using the default parameter
setting, delete the QJ71MB91
parameters entered to the PLC CPU.
• When starting the QJ71MB91 with
parameters set from GX
Configurator-MB or the sequence
program, turn ON the MODBUS
device assignment parameter
starting method of the intelligent
function module switch.
Review the CPU response monitoring
timer value.
MODBUS
device
assigned range
overlap error
MODBUS
Review the device code value.
device number
+ assigned points in the MODBUS
device assignment parameter exceeds
the maximum value (65535) allowed for
the MODBUS
7332H
3)
The device code value specified as a
Device code error
The head MODBUS
7331H
2)
Review the head MODBUS
device
number and the number of assigned
points.
device.
device ranges set with
the MODBUS
device assignment
parameters are overlapped.
The assigned range of the QJ71MB91
buffer memory set with the
Buffer memory
MODBUS
device assignment
assigned range error
parameter exceeds the range of the
user free area.
Review the head MODBUS
device
number and the number of assigned
points.
Review the head device number and
the number of assigned points.
The head device number + assigned
7334H
(29492)
7335H
(29493)
7336H
(29494)
7337H
(29495)
7338H
(29496)
Device upper limit
value over error
points in the MODBUS
device
assignment parameter exceeds the
maximum value (65535) allowed for the
CPU device.
Review the head device number and
the number of assigned points.
Error status read
device setting error
The specification of the error status
read device is incorrect.
Review the setting of the error status
read device.
MELSECNET/H
remote access target
value error
The access target specification value is
other than 0 and 1 when the
QJ71MB91 is mounted on the
MELSECNET/H remote I/O station.
Set the access target specification
value to 0 or 1 when the QJ71MB91 is
mounted on the MELSECNET/H
remote I/O station.
MELSECNET/H
remote access target
error
The access target (when mounted to
MELSECNET/H remote I/O station)
(address: 000EH) was set when the
QJ71MB91 is not mounted on the
MELSECNET/H remote I/O station.
Review the access target station or the
specified access target value (when
mounted to MELSECNET/H remote I/O
station).
Buffer memory
setting error
Data were written to the system area
(use prohibited) in the buffer memory.
Check whether or not writing to the
system area (use prohibited) in the
buffer memory was executed by the
sequence program.
(Continued on next page)
11 - 31
11.4 Error Codes
11.4.3 Error code list
11
TROUBLESHOOTING
9
Occurrence
Error Code
Error Name
Description
Corrective Action
1)
2)
3)
4)
5)
The set value of the target
7343H
(29507)
7345H
(29509)
7346H
(29510)
7347H
(29511)
7348H
(29512)
7349H
(29513)
734AH
(29514)
734CH
(29516)
734EH
(29518)
734FH
(29519)
device
Request interval
timer value setting
error
The set value of the request interval
timer in the automatic communication
parameter is incorrect.
Review the request interval timer value.
Response
monitoring timer
setting error
The set value of the response
monitoring timer in the automatic
communication parameter is outside
the allowable range.
Correct the response monitoring timer
value so that it falls within the allowable
range.
Buffer memory
address overlap
error
The buffer memory setting ranges
overlap between several automatic
communication parameters.
Review the overlapping buffer memory
settings and correct them.
Buffer memory
address range error
The buffer memory setting range in the
automatic communication parameter is
outside the range for the automatic
communication function buffer input/
output area.
Correct the invalid buffer memory
setting.
Automatic
communication
setting range error
Other than 0 and 1 is set in the
automatic communication parameter
setting existence.
Review the setting of the automatic
communication parameter setting
existence.
MODBUS
device
number setting
range error
The MODBUS
device range for the
read/write target set in the automatic
communication parameter or dedicated
instruction's control data exceeds the
maximum value (65536).
MODBUS
device
points setting error
The MODBUS
device range of the
read/write target set as an automatic
communication parameter or in
dedicated instruction's control data
exceeds the allowable range.
Target station
number setting error
The target station number set as an
automatic communication parameter or
in dedicated instruction's control data is
incorrect.
Review the target station number.
Response
monitoring timer
setting error
The set value of the response
monitoring timer in the dedicated
instruction's control data is outside the
allowable range.
Correct the response monitoring timer
setting so that it falls within the
allowable range.
Write data storage
size setting error
The set value of the write data storage
size in the dedicated instruction's
control data is incorrect.
Review the write data storage size
value.
Request message
size setting error
The request message size specified as
an argument ((S2)+0) of the MBREQ
instruction is incorrect.
Review the request message size
value.
10
DEDICATED
INSTRUCTIONS
(29506)
Review the target MODBUS
type specification value.
11
TROUBLESHOOTING
7342H
MODBUS
device type specification
in the automatic communication
parameter is incorrect.
APPENDICES
(29504)
Target MODBUS
device type
specification error
Review the setting range of the
MODBUS
device.
Review the setting range of the
MODBUS
INDEX
7340H
PROGRAMMING
Table11.16 Error code list (Continued)
device.
(Continued on next page)
11.4 Error Codes
11.4.3 Error code list
11 - 32
11
TROUBLESHOOTING
Table11.16 Error code list (Continued)
Occurrence
Error code
Error Name
Error definition
Corrective Action
1)
7350H
(29520)
7353H
(29523)
7355H
(29525)
7360H
(29536)
7361H
(29537)
7362H
(29538)
7365H
(29541)
7366H
(29542)
7367H
(29543)
2)
3)
4)
5)
• Wait for the automatic
communication parameters to be
activated by GX Configurator-MB,
and start the automatic
communication function after
stopping automatic communication.
Automatic
communication
function start
interruption
Failed to activate the automatic
communication function because the
GX Configurator-MB parameters were
being entered at power-on.
Operation mode
error
Any slave function was attempted
during master operation.
Or, any master function was attempted
during slave operation.
Check the mode or the operation.
Channel No. error
The channel No. specification is wrong.
Review the channel No. specification.
Exception message
reception
When the automatic communication
function or dedicated instruction was
used, the target slave device returned
an exception code in reply to the
request message sent by the
QJ71MB91.
Refer to the exception code returned
from the target slave device, and solve
the problem.
Byte count error
In the automatic communication
function or dedicated instruction, the
number of bytes in the received
response message is too small or
large.
Reference number
error
The reference number value in the
response message received by the
dedicated instruction is incorrect.
Station No.
mismatch error
In the automatic communication
function or dedicated instruction, the
station number in the received
response message does not match the
one in the corresponding request
message.
Function code
mismatch error
In the automatic communication
function or dedicated instruction, the
function code in the received response
message does not match the one in the
corresponding request message.
Response message
contents mismatch
error
In the automatic communication or
dedicated instruction, the contents of
the received response message are
not consistent with those of the
corresponding request message.
(FC: 15, FC: 16, FC: 21)
• Wait for MODBUS
device
assignment parameter setting
existence (XA) to turn ON, and start
the automatic communication
function.
• Retry after a little while.
On the target slave device, check if the
contents of the returned response
message are correct or not.
(Continued on next page)
11 - 33
11.4 Error Codes
11.4.3 Error code list
11
TROUBLESHOOTING
9
Occurrence
Error code
Error Name
Error definition
Corrective Action
1)
Automatic
communication
parameter setting
request error
The automatic communication
parameter setting request (Y4, YC)
was made with the automatic
communication function active.
Stop the automatic communication
function before making the automatic
communication parameter setting
request (Y4, YC).
The response monitoring timer timed
out in the automatic communication
function.
In the case of broadcast, the broadcast
delay has expired before completion of
the request message transmission.
When broadcast was performed
beforehand, response is not possible
because the slave is currently
executing the processing requested by
the broadcast.
7378H
(29560)
Response
monitoring timer
timeout error
7379H
(29561)
737BH
(29563)
737CH
(29564)
7380H
(29568)
7381H
(29569)
7382H
(29570)
Request interval
timer timeout error
The response monitoring timer timed
out when using the dedicated
instruction.
In the case of broadcast, the broadcast
delay has expired before completion of
the request message transmission.
When broadcast was performed
beforehand, response is not possible
because the slave is currently
executing the processing requested by
the broadcast.
A request message, for which no
response is expected, was sent to a
slave by the MBREQ instruction.
(excluding the case of broadcast)
The time for issuing the next request
was reached before the current request
is completed.
10
DEDICATED
INSTRUCTIONS
(29553)
Prevent the automatic communication
stop request (Y6, YE) from being
issued with the automatic
communication function stopped.
5)
• Check if the target device is
operating normally.
• If an error has occurred in the target
device, remove the error.
• Confirm the line connections (cables,
wiring, etc.) with the target device.
• Check the processing time of the
target device. (Is the set value too
small? Does the timeout error occur
before response of the target device
or before completion of the request
message transmission?)
• Set a larger value.
• When the automatic communication
function and dedicated instructions
are used on the same channel, set
appropriate automatic
communication parameters and
create a proper sequence program
so that each of the dedicated
instructions can be executed in the
11
TROUBLESHOOTING
7371H
The automatic communication stop
request (Y6, YE) was made with the
automatic communication function
stopped.
4)
APPENDICES
(29552)
Automatic
communication
function stop request
error
3)
Section 9.2.3)
right timing.(
• When broadcast delay was
performed beforehand, check if the
broadcast delay value is sufficient.
• If this error occurs when a request
message, for which no response is
expected, is sent to a slave by the
MBREQ instruction, this error may
be regarded as a normal completion.
(
INDEX
7370H
2)
Section 10.3 (6))
Simultaneous
execution error
Two kinds of dedicated instructions
were executed simultaneously on the
same channel.
Execute the next instruction after
completion of the currently executing
instruction.
CPU response
monitoring timer
timeout
The CPU response monitoring timer
timed out in the slave function.
• If an error has occurred in the PLC
CPU, remove the error.
• Set a larger value for the CPU
response monitoring timer.
Function code error
A request message with a function
code that is not supported by the
QJ71MB91 slave function was
received.
Confirm the function codes supported
by the QJ71MB91 slave function, and
review the request message to be sent.
Sub-code error
The request message with a sub-code
that is not supported by the QJ71MB91
slave function was received.
Confirm the sub-codes supported by
the QJ71MB91 slave function, and
review the request message to be sent.
PROGRAMMING
Table11.16 Error code list (Continued)
(Continued on next page)
11.4 Error Codes
11.4.3 Error code list
11 - 34
11
TROUBLESHOOTING
Table11.16 Error code list (Continued)
Occurrence
Error code
Error Name
Error definition
Corrective Action
1)
2)
3)
4)
5)
• Set the MODBUS
device
assignment parameters for the
The MODBUS
device assignment
parameters have not been set for the
7383H
(29571)
MODBUS
device
specification error
MODBUS
device specified in the
received request message.
The MODBUS
device assignment
parameter setting is in process.
The range of the MODBUS
device
specified in the received request
message exceeds the valid range of
7384H
(29572)
the MODBUS
parameter.
device assignment
The range of the MODBUS
device
specified in the received request
7385H
(29573)
MODBUS
device
specification error
message exceeds the maximum value*
for the MODBUS
device.
* The maximum value for the extension
file register is "10000", and that for any
other MODBUS
(29584)
7391H
(29585)
7392H
(29586)
7393H
(29587)
satisfy the MODBUS
device range
specified in the received request
message.
Check the specification of the
MODBUS
device on the master side
from which the request message was
sent.
Check the specification of the
MODBUS
device on the master side
from which the request message was
sent.
No setting for error
status read device
No error status read device was set for
Read exception status (FC: 07).
Set an error status read device.
Byte count
specification error
The number of write points in the
received request message does not
match the specified number of bytes.
Review the number of write points and
the number of bytes on the master side
from which the request message was
sent.
Received data size
error
The write device data size in the
received request message is not
consistent with the specified number of
bytes.
Review the specified contents of the
write device data size and number of
bytes on the master side that sent the
request message.
(29574)
7390H
Set an adequate MODBUS
device
assignment parameter so that it will
MODBUS
device specified in the
received request message exceeds the
maximum access points allowed for the
relevant function.
7386H
(29576)
after the MODBUS
device
assignment parameter setting
existence (XA) turns ON.
device is "65536".
The number of access points for the
7388H
MODBUS
device specified in the
request message.
• Adjust the timing for the request
message transmission on the master
side so that communication is started
The reference number value specified
Reference type error in the received request message (FC:
20, FC: 21) is incorrect.
Data unit error
• The contents of the data unit in the
received request message are
incorrect.
• The size of the received request
message is smaller than the
minimum size or greater than the
maximum size required for the
relevant function code.
Review the specification of the
reference number on the master side
from which the request message was
sent.
Review the contents of the request
message on the master side from
which the request message was sent.
(Continued on next page)
11 - 35
11.4 Error Codes
11.4.3 Error code list
11
TROUBLESHOOTING
9
Occurrence
Error code
Error Name
Error definition
Corrective Action
1)
(29591)
7398H
(29592)
7399H
(29593)
739AH
(29594)
739BH
(29595)
Non-reception
monitoring timeout
No reception for a 1.5 character time or
1 second or more was detected during
message reception, and the message
was discarded.
• Review the setting of the device from
which the relevant message was
sent.
• Check the relevant device.
• Disconnect an erroneous device if
any.
Short frame error
The received message size (excluding
the start character in the ASCII mode)
was less than 4 or 8 bytes.
Character overrun
error
The received message size (excluding
the start character in the ASCII mode)
exceeded 256 or 512 bytes.
ASCII-binary
conversion error
An ASCII code that cannot be
converted to binary was received.
End code error
An illegal character was received after
the end code CR.
739CH
to
739EH
(29596 to
29598)
System error
The OS of the QJ71MB91 detected a
fault.
10
DEDICATED
INSTRUCTIONS
A write request message was received
with online change disabled.
5)
11
TROUBLESHOOTING
7397H
Online change error
4)
Review the contents of the message
issued by the station that sent the
relevant message.
• Check the relevant device.
• Disconnect an erroneous device if
any.
• Review the contents of the message
issued by the station that sent the
relevant message.
Check the relevant device.
• Disconnect an erroneous device if
any.
APPENDICES
(29588)
3)
Take the following steps:
• Check that the power supply
module, PLC CPU and QJ71MB91
are correctly mounted on the base
unit.
• Confirm that the system is operated
within the general specifications of
the PLC CPU.
• Check if the power capacity is
sufficient.
• It can be a hardware error.
Check if the PLC CPU, base unit and
QJ71MB91 are normal referring to
the manual for each module.
Or, replace a module or a unit to
check the operation.
• If the above does not solve the
problem, please consult your local
Mitsubishi system service center or
representative, explaining a detailed
description of the error occurrence,
the GX Developer project and/or the
error code.
INDEX
7394H
• Do not issue a write request
message while online change is
disabled.
• Turn ON the online change with the
intelligent function module switch to
enable the online change.
2)
PROGRAMMING
Table11.16 Error code list (Continued)
(Continued on next page)
11.4 Error Codes
11.4.3 Error code list
11 - 36
11
TROUBLESHOOTING
Table11.16 Error code list (Continued)
Occurrence
Error code
Error Name
Error definition
Corrective Action
1)
73C0H
(29632)
73C1H
(29633)
73C2H
(29634)
7400H
(29696)
RAM error
ROM error
Self-loopback test
error
Framing error
2)
3)
4)
5)
Take the following steps:
• Check that the power supply module,
PLC CPU and QJ71MB91 are
correctly mounted on the base unit.
• Confirm that the system is operated
within the general specifications of
the PLC CPU.
An error was detected in the RAM test.
• Check if the power capacity is
sufficient.
• Perform the test again.
• If the above does not solve the
problem, a probable cause is a
hardware error.
Check if the PLC CPU and base unit
are normal referring to the manual
for each module.
Or, replace either of the modules to
check the operation.
An error was detected in the ROM test.
In case of failure, please consult your
local Mitsubishi system service
center or representative, explaining a
detailed description of the problem.
An error was detected in the selfloopback test.
• The stop bit position is incorrect.
• The stop bit setting is incorrect.
• The transmission setting is
inconsistent.
• Turning ON/OFF the equipment
produced a disturbance on the line.
• Electric noise was generated on the
line.
• There are two or more masters.
• Data transmission occurred
simultaneously.
Take the following steps:
• Check if the loopback connector is
attached and if the wiring is correct.
• Check that the power supply module,
PLC CPU and QJ71MB91 are
correctly mounted on the base unit.
• Confirm that the system is operated
within the general specifications of
the PLC CPU.
• Check if the power capacity is
sufficient.
• Perform the test again.
• If the above does not solve the
problem, a probable cause is a
hardware error.
Check if the PLC CPU and base unit
are normal referring to the manual
for each module.
Or, replace either of the modules to
check the operation.
In case of failure, please consult your
local Mitsubishi system service
center or representative, explaining a
detailed description of the problem.
• Match the stop bit setting on the
QJ71MB91 with that on the target
device.
• Match the transmission setting on
the QJ71MB91 with that on the
target device.
• Take preventive measures against
noise.
• Use one master in the system.
• Adjust the transmission timing to
prevent simultaneous data
transmission.
(Continued on next page)
11 - 37
11.4 Error Codes
11.4.3 Error code list
11
TROUBLESHOOTING
9
Occurrence
Error code
Error Name
Error definition
Corrective Action
1)
(29698)
7403H
(29699)
7404H
(29700)
7411H
(29713)
CS signal OFF
• The CS signal was OFF at the time
of request or response message
transmission, resulting in failure of
the transmission.
• A cable is disconnected.
• A cable is faulty.
• Confirm that the cables are not
disconnected.
• Check the cable connection and
correct the wiring so that the CS
signal on the CH1 (RS-232) side will
be always ON.
Buffer full error
CRC/LRC error
The OS buffer (the buffer provided
inside the module) is full.
• If the PLC CPU has any problem,
remove it.
• Check if the transmission speed is
within the limit of the QJ71MB91.
• Check if no instantaneous power
failure is occurring on the station.
(This can be checked with special
register SD1005 of the PLC CPU.)
Remove the cause of the
instantaneous power failure if it is
occurring.
• Reduce the transmission speed.
• Reduce the frequency of requests
from the target device.
The CRC/LRC in the received
message does not match the CRC/
LRC calculated by the QJ71MB91.
• Do not turn OFF or disconnect the
device from the network while it is
sending a message. (If this is the
cause of t he error, no action is
required as long as there is no
particular problem.)
• Review the contents of the message
issued by the relevant station.
• Check the relevant device.
• Disconnect the erroneous device if
any.
• Review the line status.
• Take preventive measures against
noise.
10
DEDICATED
INSTRUCTIONS
Overrun error
5)
11
TROUBLESHOOTING
7402H
• The next data was received before
completion of the current reception
processing.
• The transmission speed exceeds the
limit of the QJ71MB91.
• An instantaneous power failure
occurred.
• Check if the transmission speed is
within the limit of the QJ71MB91.
• Check if no instantaneous power
failure is occurring on the station.
(This can be checked with special
register SD1005 of the PLC CPU.)
Remove the cause of the
instantaneous power failure if it is
occurring.
• Reduce the transmission speed.
Parity error
4)
APPENDICES
(29697)
• Match the parity bit setting on the
QJ71MB91 with that on the target
device.
• Match the transmission setting on
the QJ71MB91 with that on the
target device.
• Take preventive measures against
noise.
• Use one master in the system.
• Adjust the transmission timing to
prevent simultaneous data
transmission.
3)
INDEX
7401H
• The parity bit check ended in error.
• The parity bit setting is incorrect.
• The transmission setting is
inconsistent.
• There is fluctuation on the line
caused by a device turning on and
off.
• Electric noise was generated on the
line.
• There are two or more masters.
• Data transmission occurred
simultaneously.
2)
PROGRAMMING
Table11.16 Error code list (Continued)
(Continued on next page)
11.4 Error Codes
11.4.3 Error code list
11 - 38
11
TROUBLESHOOTING
Table11.16 Error code list (Continued)
Occurrence
Error code
Error Name
Description
Corrective Action
1)
7412H
(29714)
Transmission
monitoring timer
timeout
7480H to 75FFH
(29824 to
30207)
System error
The transmission monitoring timer
timed out.
(61440 to
65535)
-
3)
4)
• Confirm that the cables are not
disconnected.
• Check the cable connection and
correct the wiring so that the CS
signal on the CH1 (RS-232) side will
be always ON.
The OS of the QJ71MB91 detected a
fault.
Take the following steps:
• Check if the power supply module,
PLC CPU and QJ71MB91 are
correctly mounted on the base unit.
• Confirm that the system is operated
within the general specifications of
the PLC CPU.
• Check if the power capacity is
sufficient.
• A probable cause is a hardware
error.
Check if the PLC CPU, base unit and
QJ71MB91 are normal referring to
the manual for each module.
Or, replace any of the modules to
check the operation.
• If the above does not solve the
problem, please consult your local
Mitsubishi system service center or
representative, explaining a detailed
description of the error occurrence,
the GX Developer project and/or the
error code.
Errors detected by MELSECNET/H or
MELSECNET/10 network module
Refer to the troubleshooting section in
the MELSECNET/H or MELSECNET/
10 Network System Reference Manual,
and take the corrective actions.
F000H to
FFFFH
2)
Remark
1. For details of areas to which error codes are stored, refer to Section 11.4.1
2. For details of parameter setting ranges and other information, refer to
CHAPTER 7
11 - 39
11.4 Error Codes
11.4.3 Error code list
5)
11
TROUBLESHOOTING
9
This section explains how to turn off the ERR.LED of the QJ71MB91 when it is lit.
10
POINT
(
Section 11.1, Section 11.4)
If not, the following operation will not turn off the ERR. LED.
The ERR. LED turns on when an error occurs.
Once the ERR. LED has turned on, it does not turn off automatically even if
the status returns to normal.
Perform the following to turn off the ERR. LED.
Table11.17 List of methods for turning off the ERR. LED
Reference
Turning off by GX Configurator-MB
Section 11.5.1
Turning off by sequence program
Section 11.5.2
Turning off by request message from master
Section 11.5.3
(when the QJ71MB91 is a slave)
11
APPENDICES
Method
DEDICATED
INSTRUCTIONS
2.
Remove possible error cause before turning off the ERR. LED.
TROUBLESHOOTING
1.
PROGRAMMING
11.5 Turning Off the ERR. LED
11.5.1 Turning off the ERR. LED by GX Configurator-MB
INDEX
This section explains how to turn off the ERR. LED from GX Configurator-MB.
(1) Making the Monitor/test screen active
Make the Monitor/test screen active.(
Section 8.6)
Figure 11.8 Monitor/test screen
11.5 Turning Off the ERR. LED
11.5.1 Turning off the ERR. LED by GX Configurator-MB
11 - 40
11
TROUBLESHOOTING
(2) Turning off the ERR. LED
Select "Being requested" in the Setting value field of the "CH Common/CH1 Error
clear request".
Click the Execute test button.
Perform the same operation for "CH2 Error clear request".
Select
"Being requested"
Click.
Figure 11.9 Turning off the ERR. LED on the Monitor/test screen
11 - 41
11.5 Turning Off the ERR. LED
11.5.1 Turning off the ERR. LED by GX Configurator-MB
TROUBLESHOOTING
(a) LEDs that will be cleared
When error clear requests are made by "CH Common/CH1 Error clear request"
and "CH2 Error clear request" on the Monitor/test screen (
Section 8.6), all
the LEDs and the Exception code storage area (0002H/0004H) in the buffer
memory are cleared.*1
PROGRAMMING
9
10
CH1 side Detailed LED clear request storage area (address: 0008H)
b15 b14 b13 b12 b11 b10 b9 b8 b7
Unused (Fixed to 0)
1/0
b6
b5
b4 b3 b2 b1 b0
1/0 1/0 1/0 1/0 1/0
0: Not cleared
1: Clear request
CH1 C/N
CH1 P/S
11
TROUBLESHOOTING
request" on the X/Y monitor/test screen (
Section 8.6.1), only the LED, whose clear is
requested in the Detailed LED clear request storage area (address: 0008H/0009H) in the buffer
memory, is cleared.
When the LED was turned off by "Y1B: CH common/CH1 error clear request" and "Y1C: CH2 error
clear request", turn on the corresponding bit in the Detailed LED clear request storage area by the
device test on GX Developer.
DEDICATED
INSTRUCTIONS
* 1 For the execution of "Y1B: CH common/CH1 error clear request" and "Y1C: CH2 error clear
CH1 PRO.
CH1 error response code
storage area (0002H)
CH1 SIO
CH2 side Detailed LED clear request storage area (address: 0009H)
b15 b14 b13 b12 b11 b10 b9 b8 b7
Unused (Fixed to 0)
1/0
b6
b5
b4 b3 b2 b1 b0
1/0 1/0 1/0 1/0 1/0
0: Not cleared
1: Clear request
APPENDICES
C/1 ERR.
CH2 C/N
CH2 P/S
CH2 PRO.
CH2 error response code
storage area (0004H)
CH2 SIO
CH2 ERR.
Figure 11.10 Configuration of the Detailed LED clear request storage area
11.5 Turning Off the ERR. LED
11.5.1 Turning off the ERR. LED by GX Configurator-MB
11 - 42
INDEX
11
11
TROUBLESHOOTING
(3) Confirming the ERR. LED turned off
When the processing is completed, the "Completed." message is displayed.
Check that the current value fields of "CH Common/CH1 Error" and "CH2 Error" have
changed from "Error occurred" to "No error".
Figure 11.11 Monitor/test screen (after the ERR.LED turned off)
11 - 43
11.5 Turning Off the ERR. LED
11.5.1 Turning off the ERR. LED by GX Configurator-MB
TROUBLESHOOTING
9
PROGRAMMING
11.5.2 Turning off the ERR. LED by sequence program
This section explains how to turn off the ERR. LED from a sequence program.
(1) Procedure for turning off the ERR. LED
CH common/CHn error clear request
(Y1B/Y1C)
(LED On)
ON1)
(LED Off)
2)
(LED On)
ON1)
3)
CH common/CHn error
(X1B/X1C)
Error occurred
Error
occurred
Error
occurred
Error
occurred
11
TROUBLESHOOTING
(a) I/O signals when the ERR.LED is lit
When an error occurs, the ERR. LED on the front of the QJ71MB91 module lights
up, and the CH common/CHn error (X1B/X1C) turns on. ((1) in the figure)
DEDICATED
INSTRUCTIONS
10
The following is the procedure for turning off the ERR. LED.
(b) Turning on the corresponding bit in the Detailed LED clear request storage area
Turn on all the relevant bits of the Detailed LED clear request storage area
(0008H/0009H) in the buffer memory.
CH1 side Detailed LED clear request storage area (address: 0008H)
b15 b14 b13 b12 b11 b10 b9 b8 b7
Unused (Fixed to 0)
1/0
b6
b5
b4 b3 b2 b1 b0
1/0 1/0 1/0 1/0 1/0
APPENDICES
Figure 11.12 I/O signal behavior when the ERR. LED is lit
0: Not cleared
1: Clear request
CH1 C/N
CH1 P/S
CH1 PRO.
CH1 SIO
CH1 error response code
storage area (0002H)
C/1 ERR.
CH2 side Detailed LED clear request storage area (address: 0009H)
b15 b14 b13 b12 b11 b10 b9 b8 b7
Unused (Fixed to 0)
1/0
b6
b5
b4 b3 b2 b1 b0
1/0 1/0 1/0 1/0 1/0
0: Not cleared
1: Clear request
CH2 C/N
CH2 P/S
CH2 PRO.
CH2 error response code
storage area (0004H)
CH2 SIO
CH2 ERR.
Figure 11.13 Configuration of the Detailed LED clear request storage area
The above area is cleared when an error clear request described in (1)(c) of this
section is made after the clear request (turning on the corresponding bit).
When the above exception code storage area is turned on, the Exception code
storage error (address: 0002H/0004H) in the buffer memory is cleared.
11.5 Turning Off the ERR. LED
11.5.2 Turning off the ERR. LED by sequence program
11 - 44
INDEX
11
11
TROUBLESHOOTING
(c) Turning on the CH common/CHn error clear request
Turning on the CH common/CHn error clear request (Y1B/Y1C) turns off the ERR.
LED. ((2) in the figure)
Clear request will be processed all the time while the CH common/CHn error clear
request (Y1B/Y1C) is on. ((3) in the figure)
CH common/CHn error clear request
(Y1B/Y1C)
(LED On)
ON1)
(LED Off)
2)
(LED On)
ON1)
3)
CH common/CHn error
(X1B/X1C)
Error occurred
Error
occurred
Error
occurred
Error
occurred
Figure 11.14 I/O signal behavior when turning off the ERR.LED is requested
(2) Program conditions
The following program executes turning off the ERR. LED when communications are
performed on the CH2 side.
(a) Devices used
Table11.18 Devices used for turning off the ERR. LED
Device name
Device
X0
QJ71MB91 input/output
Application
Module READY
Input
External input (command)
Y1C
CH2 error clear request
X20
ERR.LED OFF command
(b) Buffer memory used
Table11.19 Buffer memory used for turning off the ERR. LED
Device name
QJ71MB91 buffer memory
Address
0009H
(9)
Application
CH2 side Detailed LED clear request
storage area
(3) Program example
(When the I/O signals of the QJ71MB91 are X/Y0 to X/Y1F)
\
ERR.LED Module
Off
READY
command
CH2 error clear request
After the CH2 side Detailed
LED clear request storage area
is initialized, the CH2 error
clear request is reset.
\
Figure 11.15 ERR. LED OFF program example
11 - 45
All error LEDs are specified
to the CH2 side Detailed LED
clear request storage area.
11.5 Turning Off the ERR. LED
11.5.2 Turning off the ERR. LED by sequence program
TROUBLESHOOTING
9
(1) Procedure for turning off the ERR. LED
Send a request message containing the following to the slave (QJ71MB91) from the
master after removing possible error causes.
Restart communications option (
Section 4.11.2)
11
Section 4.11.6)
APPENDICES
TROUBLESHOOTING
Clear Counters and Diagnostic Register (
10
DEDICATED
INSTRUCTIONS
When the QJ71MB91 is a slave, the ERR.LED can be turned off by a request message
from the master.
The following explains how to turn off the ERR. LED by issuing a request message from
the master.
PROGRAMMING
11.5.3 Turning off the ERR. LED by request message from the master
INDEX
11
11.5 Turning Off the ERR. LED
11.5.3 Turning off the ERR. LED by request message from the master
11 - 46
APPENDICES
APPENDICES
Appendix 1 A Series Modules
This section presents comparisons in performance and functions between the QJ71MB91
and A Series modules, and utilization of existing programs.
Appendix 1.1 Comparisons in performance specifications
TableApp.1 Comparisons in performance specifications
Specifications
Item
RS-232
Interface
RS-422/485
Transmission
Transmission speed
specifications
Transmission
RS-232
distance
(Overall
RS-422/485
distance)
AJ71UC24-S2
A1SJ71UC24-R2-S2
A1SJ71UC24-R4-S2
QJ71MB91
RS-232 compliant (D-Sub 25-pin)
or, RS-232 compliant (D-Sub 9-pin)
RS-232 compliant (D-Sub 9-pin)
RS-422/485 compliant
RS-422/485 compliant
(Detachable terminal block)
300 to 19200 bps
300 to 115200 bps
Max. 500m (3936.9 ft.) (Overall
distance)
Max. 1200m (3936.9 ft.) (Overall
distance)
32 per channel
Function (for send)
7 functions
Input area size
4k words
Output area size
Master
function
No. of simultaneously
executable instructions
Dedicated
instruction
Automatic
response
function
Slave
function
MODBUS
device size
4k words
(None)
MBRW instruction: 9 functions
MBREQ instruction: 19 functions
Input area size
Max. 253 bytes per instruction
Output area size
Max. 253 bytes per instruction
Function (for receive)
13 functions
17 functions
Coil
10000 points
64k points
Input
0 points
64k points
Input register
0 points
64k points
Extended file register
10000 points
64k points
8192 points (1 file)
Max. 1018k points (105 files)
No. of simultaneously acceptable request
messages
Max. access points per message
Station No.
Number of occupied I/O points
1 request per channel
256 points
Max. points prescribed by
MODBUS
protocol
1 to 99
1 to 247
32 points per slot
(I/O assignment: Special 32 points)
32 points per slot
(I/O assignment: Intelli. 32 points)
: Compatible
* 1 The connector of the cable must be changed.
App - 1
-
1 instruction per channel
Function (for send)
Holding register
*1
Max. 15m (49.2 ft.)
Number of slaves
Automatic
communication
function
Compatibility
Appendix 1 A Series Modules
Appendix 1.1 Comparisons in performance specifications
: Partially changed
: Incompatible
APPENDICES
9
PROGRAMMING
Appendix 1.2 Functional comparisons
Table App.2 Functional comparisons
AJ71UC24-S2
Function
A1SJ71UC24-R2-S2
QJ71MB91
10
A1SJ71UC24-R4-S2
Master function
DEDICATED
INSTRUCTIONS
Automatic
communication function
Dedicated instruction
Automatic response
function
Slave
function*2
MODBUS
device
11
*1
Link operation function
Various settings using utility package
Computer link function
: Available
: Not available
TROUBLESHOOTING
assignment function
(Sub code)
AJ71UC24-S2
Function
Read coils
02
Read discrete inputs
03
Read holding registers
04
Read input registers
05
Write single coil
06
Write single register
07
Read exception status
08
Diagnostics
12
Get communications
event counter
Get communications
event log
15
Write multiple coils
16
Write multiple registers
17
Report slave ID
20(6)
Read file record
21(6)
Write file record
22
23
24
43
QJ71MB91
A1SJ71UC24-R4-S2
01
11
A1SJ71UC24-R2-S2
INDEX
Function code
APPENDICES
* 1 MODBUS devices cannot be assigned to the buffer memory.
* 2 The following is a list of standard functions available in the slave function.
Mask write register
Read/Write multiple
registers
Read FIFO queue
Read device
identification
: Supported
Appendix 1 A Series Modules
Appendix 1.2 Functional comparisons
: Not supported
App - 2
APPENDICES
Appendix 1.3 Utilization of existing programs
TableApp.3 Comparisons of sequence programs
Compatibility
Item
Target device side program
(Master)
Automatic
Sequence program
(Program not required)
response function
device
function
assignment
programs since the I/O signals and buffer
(Program not required)
memory assignments are different.
Modify the sequence program, or make
function
Link operation
function
the setting again on GX Configurator-MB.
(Program not required)
(Program not required)
module switch setting.
for the QJ71MB91.
: Compatible
Appendix 1 A Series Modules
Appendix 1.3 Utilization of existing programs
Make the setting in the intelligent function
The computer link function is not available
Computer link function
App - 3
There is no compatibility in sequence
MODBUS
Slave
Precautions for replacement
: Partially changed
: Incompatible
APPENDICES
(1) Switch setting
The mode, station No. and transmission specifications are set in the intelligent
function module switch setting of GX Developer on the QJ71MB91 while they are set
with switches on A Series modules.(
Section 6.6)
PROGRAMMING
9
10
There is no compatibility in I/O signal assignment between the QJ71MB91 and A
Series modules.
Create a new sequence program.
TableApp.4 Comparisons of I/O signals
Compatibility
AJ71UC24-S2, A1SJ71UC24-R2-S2,
Precautions for replacement
A1SJ71UC24-R4-S2
X0
Error occurrence on CH1 side
X1B is used on the QJ71MB91.
X1
Error occurrence on CH2 side
X1C is used on the QJ71MB91.
Use prohibited
X7
Module ready
X8
X9 to XC
XD
XE to X1F
MODBUS
-
X0 is used on the QJ71MB91.
device assignment parameter setting,
X9 is used on the QJ71MB91.*1
error completed
Use prohibited
-
Watch dog timer error (WDT error)
X1F is used on the QJ71MB91.
Use prohibited
-
: Compatible
: Partially changed
: Incompatible
APPENDICES
X2 to X6
TROUBLESHOOTING
11
Signal name
Input signal
DEDICATED
INSTRUCTIONS
(2) I/O signals
TableApp.5 Comparisons of output signals
Signal name
Output signal
Compatibility
AJ71UC24-S2, A1SJ71UC24-R2-S2,
Precautions for replacement
A1SJ71UC24-R4-S2
Use prohibited
-
Y10
CH1 side communication error cancel request
Y11
CH2 side communication error cancel request
Y12 to Y16
Y17
Y18 to Y1F
Y1B is used on the QJ71MB91.
Y1C is used on the QJ71MB91.
Use prohibited
MODBUS
-
device assignment parameter setting
Y8 is used on the QJ71MB91.*1
request
Use prohibited
-
: Compatible
* 1 Because the QJ71MB91 has the MODBUS
completed (X8) and MODBUS
: Partially changed
device assignment parameter setting, normally
device assignment parameter setting existence (XA) in addition
to the signals provided for A Series modules, the MODBUS
setting procedure is partially different.
For the MODBUS
: Incompatible
device assignment parameter
device assignment parameter setting, refer to the following:
Section 9.1.2
Appendix 1 A Series Modules
Appendix 1.3 Utilization of existing programs
App - 4
INDEX
Y0 to YF
APPENDICES
(3) Buffer memory
There is no compatibility in buffer memory assignment between the QJ71MB91 and A
Series modules.
Create a new sequence program.
TableApp.6 Comparison of buffer memories
Buffer memory name
AJ71UC24-S2
Buffer memory address
Compatibility
A1SJ71UC24-R2-S2
Precautions for replacement
A1SJ71UC24-R4-S2
0000H (0)
Mode setting status storage area
On the QJ71MB91, 0C00H to 0C04H (3072
0001H (1)
Station No. setting status storage area
to 3076) are used.
0002H (2)
CH1 side error response code storage area
0003H (3)
CH1 side detailed error code storage area
0004H (4)
CH2 side exception code storage area
0005H (5)
CH2 side detailed error code storage area
0006H (6)
CH1 side detailed LED status storage area
0007H (7)
CH2 side detailed LED status storage area
0008H (8)
Check Error log 0CFEH to 0DFFH (3326 to
3583).
Check Error log 0CFEH to 0DFFH (3326 to
3583).
CH1 side detailed LED clear request storage
On the QJ71MB91, some data are partially
area
added.
CH2 side detailed LED clear request storage
0009H (9)
area
000AH (10)
Error status read device code
000BH (11)
Head error status read device No.
000CH (12)
Computer link function FC value setting
000DH to 000FH
(13 to 15)
0010H to 0023H
(16 to 35)
0024H to 002FH
(36 to 47)
0030H to 0043H
(48 to 67)
Check the specified device code value.
Not used on the QJ71MB91.
System area (use prohibited)
On the QJ71MB91, 900H to 9FFH (2304 to
MODBUS
device assignment parameter (Coil)
System area (use prohibited)
MODBUS
2559) are used.*1
(68 to 3567)
0DF0H to 0DFFH
(3568 to 3583)
On the QJ71MB91, 900H to 9FFH (2304 to
device assignment parameter
2559) are used.*1
On the QJ71MB91, 5000H to 5FFFH
User free area
System area (use prohibited)
-
-
(Holding register)
0044H to 0DEFH
-
-
(20480 to 24575) are used.
-
: Compatible
-
: Partially changed
: Incompatible
* 1 The MODBUS device assignment parameter setting area and setting contents are different
between the QJ71MB91 and A Series modules.
Modify the sequence program, or make the setting again on GX Configurator-MB.
App - 5
Appendix 1 A Series Modules
Appendix 1.3 Utilization of existing programs
APPENDICES
9
This section explains the QJ71MB91 processing time for each function.
The processing times obtained by the expressions in this section can be regarded as the
times showing performance in communication with a single device.
PROGRAMMING
Appendix 2 Processing Time
10
1) Automatic communication function communication time [unit: ms]
The automatic communication function communication time is the time from
the start of request message processing to the end of response message
processing.
Tac=Km+Ta+Ktq+Ktr+Ts+Ti
3+Gt
2) Calculation items
TableApp.7 Processing time calculation items for the automatic communication function
Item
Km
Unit
ms
communication time
9 (Constant)
APPENDICES
Tac
Description
Automatic communication function
11
TROUBLESHOOTING
(a) Performance of the automatic communication function
DEDICATED
INSTRUCTIONS
(1) Performance of master functions
Message conversion time
Ta
RTU mode : 0
Ktq
Request message transmission time*1
ms
ASCII mode: 1 to 2
ms
time*2
Ktr
Response message transmission
Ts
Target slave device processing time
ms
ms
Message interval
INDEX
RTU mode:
When the transmission speed is 19200 bps or
Ti
less, "1 character time *3
ms
3.5"
When the transmission speed exceeds 19200
bps, "1.75ms"
ASCII mode: 0
Data transmission delay time
Gt
RS-232
: 0 ms
ms
RS-422/485: 1 character time *3
2
* 1 Request message transmission time [ms]:
Ktq = Request message size [bytes] Bits of 1 character / Transmission speed [bps]
* 2 Response message transmission time [ms]:
Ktr = Response message size [bytes]
1000
Bits of 1 character / Transmission speed [bps]
* 3 1 character time = Bits of 1 character / Transmission speed [bps]
1000
1000
Appendix 2 Processing Time
App - 6
APPENDICES
Request interval timer
Automatic
communication function
communication time
Master
(QJ71MB91)
Request
message
Response
message
Request
message
Request Response
message message
Request Response
message message
Enlarged
Slave
Response
message
Automatic communication function communication time
QJ71MB91
Processing time (Km+Ta)
Message
interval
(Ti)
Master
(QJ71MB91)
Data
transmission
delay time
(Gt)
Processing
time
Request
message
Message
transmission interval
time (Ktq)
(Ti)
Target slave
device processing
time (Ts)
Processing
time
Request
message
Processing
time
Slave
Response
message
Message
transmission interval
time (Ktr)
(Ti)
Response
message
FigureApp.1 Processing time configuration of the automatic communication function
App - 7
Appendix 2 Processing Time
APPENDICES
9
1) Dedicated instruction processing time [unit: ms]
The dedicated instruction processing time is the time from the start of a
dedicated instruction until the completion device turns on.
Trc = Km + Ta + St + (Ttq + Ts + Ttr + Ti
3 + Gt or St, whichever is greater)
PROGRAMMING
(b) Performance of dedicated instructions (MBRW/MBREQ instruction)
10
TableApp.8 Calculation items for the dedicated instruction processing time
Item
Description
Unit
Trc
Dedicated instruction processing time
ms
St
Local station scan time
ms
Km
9 (Constant)
-
11
TROUBLESHOOTING
Message conversion time
Ta
ms
RTU mode : 0
DEDICATED
INSTRUCTIONS
2) Calculation items
ASCII mode: 1 to 2
Ttq
Request message transmission time*1
ms
Ts
Message processing time of target slave device
ms
Ttr
Response message transmission time*2
ms
Message interval
RTU mode :
less, "1 character time *3
APPENDICES
When the transmission speed is 19200 bps or
Ti
ms
3.5"
When the transmission speed exceeds 19200
bps, "1.75ms"
ASCII mode: 0
Data transmission delay time
Gt
RS-232
: 0 ms
ms
RS-422/485: 1 character time *3
2
Ttq = Request message size [bytes] Bits of 1 character / Transmission speed [bps]
* 2 Response message transmission time [ms]:
Ttr = Response message size [bytes]
1000
Bits of 1 character / Transmission speed [bps]
* 3 1 character time = Bits of 1 character / Transmission speed [bps]
1000
1000
Appendix 2 Processing Time
App - 8
INDEX
* 1 Request message transmission time [ms]:
APPENDICES
(2) Performance of the slave function
Request
message
Master
Request
message
Slave
(QJ71MB91)
Ti
Ttq
Ti
Response
message
Processing
time
QJ71MB91+CPU
Processing time
(Ta+Ks1+Ks2 n1+St n2)
Gt
Ttr
Ti
Tsl
FigureApp.2 Processing time configuration of the slave function
(a) When mounted with a PLC CPU
1) Request message processing time [unit: ms]
The request message processing time is the time from when the QJ71MB91
receives a request message from the master until it sends a response
message after completion of the requested processing.
Tsl = Ttq + Ta + Ks1 + Ks2
n1 + St
n2 +Ttr + Ti
2 + Gt
2) Calculation items
TableApp.9 Processing time calculation items used when mounted with a PLC CPU
Item
Description
Unit
Tsl
Request message processing time
ms
St
Local station scan time
ms
Ks1
6 (Constant)
-
Ks2
8 (Constant)
-
Message conversion time
Ta
RTU mode
:0
ms
ASCII mode : 1 to 2
Ttq
Request message transmission time*1
ms
Ttr
Response message transmission time*2
ms
Message interval
RTU mode:
Ti
When the transmission speed is 19200 bps or less, "1
character time *3
ms
3.5"
When the transmission speed exceeds 19200 bps, "1.75ms"
ASCII mode: 0
Data transmission delay time
Gt
RS-232
: 0 ms
RS-422/485: 1 character time
ms
*3
2
(Continued on next page)
App - 9
Appendix 2 Processing Time
APPENDICES
TableApp.9 Processing time calculation items used when mounted with a PLC CPU (Continued)
Item
Description
Unit
Any of the following values are applied depending on the
function code and assignment status.
assigned
When buffer
10
memory is
01
1
0
02
1
0
03
1
0
04
1
0
05
1
0
06
1
0
07
1
0
08
0
0
11
0
0
12
0
0
15
1
0
16
1
0
17
0
0
20
1
0
21
1
0
22
2
0
23
2
0
DEDICATED
INSTRUCTIONS
assigned
-
Any of the following values are applied depending on the
When PLC CPU device is
When buffer
assigned
memory is
n2
Normal case
Worst case
assigned
01
1
2
0
02
1
2
0
03
1
2
0
04
1
2
0
05
1
2
0
06
1
2
0
07
1
2
0
08
0
0
0
11
0
0
0
12
0
0
0
15
1
2
0
16
1
2
0
17
0
0
0
20
1
2
0
21
1
2
0
22
2
4
0
23
2
4
0
INDEX
function code and assignment status.
Function code
-
* 1 Request message transmission time [ms]:
Ttq = Request message size [bytes] Bits of 1 character / Transmission speed [bps] 1000
* 2 Response message transmission time [ms]:
Ttr = Response message size [bytes] Bits of 1 character / Transmission speed [bps] 1000
* 3 1 character time = Bits of 1 character / Transmission speed [bps] 1000
Appendix 2 Processing Time
11
TROUBLESHOOTING
n1
When PLC CPU device is
APPENDICES
Function code
PROGRAMMING
9
App - 10
APPENDICES
(b) When mounted on a MELSECNET/H remote I/O station
1) Request message processing time [unit: ms]
Tsl = Ttq + Ta + Ks1 + Ks2 n1 + (Sm + LS 4 + TRIOR + TRBF) n2 + Ttr +Ti 2
+ Gt
2) Calculation items
TableApp.10 Processing time calculation time used when mounted on a MELSECNET/H remote I/O station
Item
Description
Sm
Remote master station scan time
LS
TRIOR
TRBF
Other than the above
Link scan
time*1
*1
I/O refresh time
Time of refresh with buffer memory of intelligent
function module*1
Refer to(2) (a) in this appendix.
Unit
ms
ms
ms
ms
-
* 1 Refer to the Q Corresponding MELSECNET/H Network System Reference Manual (Remote I/O
network).
App - 11
Appendix 2 Processing Time
APPENDICES
9
4+10
QJ71MB91
RUN
NEU.
SD
RD
CH1
ERR.
NEU.
SD
RD
CH2
10
98 (3.86)
CH1
RS-232
R2
(*2)
1
SDB
2
3
(FG)
4
RDA
r1
(*3)
4.5 (0.18)
RDB
6
CH2
RS-422
/485
7
27.4 (1.08)
Unit : mm (inch)
FigureApp.3 External dimensions
APPENDICES
90 (3.54)
5
(FG)
R1
(*1)
11
TROUBLESHOOTING
SDA
SG
DEDICATED
INSTRUCTIONS
Cable diameter
PROGRAMMING
Appendix 3 External Dimensions
INDEX
* 1 R1 (Bending radius near terminal block) : Outer cable diameter 4
* 2 R2 (Bending radius near connector)
: Outer cable diameter 4
* 3 r1 (Bending radius near crimp contact) : Connectable as long as not bended extremely
Appendix 3 External Dimensions
App - 12
APPENDICES
Memo
App - 13
Appendix 3 External Dimensions
[C]
Change ASCII input delimiter (sub-function code: 03)
••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4-30
Checking QJ71MB91 status•••••••••••••••••••••••• 11-11
CH1, 2 station No. setting (Switch 5) ••••••••••••••• 6-23
Clear counters and diagnostic register (sub-function
code: 10) ••••••••••••••••••••••••••••••••••••••••••••••••• 4-33
Clear overrun counter and flag (sub-function code: 20)
••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4-44
Communication speed/transmission setting (Switch 2,
4)••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 6-22
Communication status ••••••••••••••••••••••••••••••••• 8-34
Communication status of QJ71MB91••••••••••••• 11-17
[D]
Dedicated instruction •••••••••••••••••••••••••••••••••• 5-16
Dedicated instructions ••••••••••••••••••••••••••••••••• 10-1
Default assignment parameters ••••••••••••••••••••• 7-19
Diagnostics (FC: 08) ••••••••••••••••••••••••••••••••••• 4-25
[E]
Error code•••••••••••••••••••••••••••••••••••••••••••••• 11-21
Error code list ••••••••••••••••••••••••••••••••••••••••• 11-30
Error code storage area ••••••••••••••••••••••••••••• 11-21
Error log ••••••••••••••••••••••••••••••••••••••••••8-33,11-26
Exception code list ••••••••••••••••••••••••••••••••••• 11-28
External dimensions ••••••••••••••••••••••••••••••• App-12
[F]
Force listen only mode (sub-function code: 04) •• 4-31
Frame mode ••••••••••••••••••••••••••••••••••••••••••••• 4-11
Frame Specifications •••••••••••••••••••••••••••••••••• 4-10
Function version ••••••••••••••••••••••••••••••••••••••••• 2-7
[G]
Get Communications Event Counter (FC: 11) •••• 4-45
Get Communications Event Log (FC: 12) ••••••••• 4-47
[H]
Hardware test •••••••••••••••••••••••••••••••••••••••••••• 6-6
Link operation function •••••••••••••••••••••••••••••••• 5-21
Listen only mode•••••••••••••••••••••••••••••••••••••••• 4-31
[M]
Mask Write Register (FC: 22) •••••••••••••••••••••••• 4-59
Master function•••••••••••••••••••••••••••••••••••••A-14,5-3
MBREQ instruction ••••••••••••••••••••••••••••••••••• 10-13
MBRW instruction •••••••••••••••••••••••••••••••••••••• 10-2
MODBUS(R) device assignment function ••••••••• 5-18
MODBUS(R) device assignment parameter
••••••••••••••••••••••••••••••••••••••••••••••••• 7-11,8-18,9-4
MODBUS(R) device assignment parameter status
••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 8-30
MODBUS(R) Protocol •••••••••••••••••••••••••••••••• A-14
MODBUS(R) protocol data unit formats•••••••••••• 4-15
MODBUS(R) standard functions•••••••••••••••••••••• 4-1
Mode setting (Switch 1, 3) •••••••••••••••••••••••••••• 6-21
Monitor/test •••••••••••••••••••••••••••••••••••••••••••••• 8-23
DEDICATED
INSTRUCTIONS
Buffer memory list •••••••••••••••••••••••••••••••••••••• 3-13
10
[L]
11
TROUBLESHOOTING
[B]
Initial Setting ••••••••••••••••••••••••••••••••••••••••••••• 8-14
Intelligent Function Module Switch Setting •••••••• 6-19
I/O signal list ••••••••••••••••••••••••••••••••••••••••••••• 3-10
APPENDICES
A Series Module •••••••••••••••••••••••••••••••••••••• App-1
Auto refresh setting •••••••••••••••••••••••••••••••••••• 8-21
Automatic communication function••••••••••••••••••• 5-3
Automatic communication parameter••••• 7-4,8-16,9-1
Automatic communication status •••••••••••••••••••• 8-31
Automatic response function ••••••••••••••••••••••••• 5-17
[I]
[P]
Parameter setting•••••••••••••••••••••••••••••••••••••••• 9-1
Performance of master functions •••••••••••••••••• App-6
Performance of the slave function••••••••••••••••• App-9
Processing time ••••••••••••••••••••••••••••••••••••••• App-6
Program Example
For Normal System Configuration ••••••••••••••••• 9-8
Program example for use in MELSECNET/H remote
I/O network•••••••••••••••••••••••••••••••••••••••••••• 9-25
[R]
Read Coils (FC: 01) •••••••••••••••••••••••••••••••••••• 4-18
Read Discrete Inputs (FC: 02) ••••••••••••••••••••••• 4-19
Read Exception Status (FC: 07) ••••••••••••••••••••• 4-24
Read File Record (FC: 20) (SC: 06) •••••••••••••••• 4-55
Read Holding Registers (FC: 03)•••••••••••••••••••• 4-20
Read input registers (FC: 04) •••••••••••••••••••••••• 4-21
Read/Write Multiple Registers (FC: 23) •••••••••••• 4-60
Report Slave ID (FC: 17)•••••••••••••••••••••••••••••• 4-53
Restart communications option (sub-function code:
01) ••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4-26
Return bus character overrun count (sub-function
code: 18) ••••••••••••••••••••••••••••••••••••••••••••••••• 4-42
Return bus communication error count (sub-function
code: 12) ••••••••••••••••••••••••••••••••••••••••••••••••• 4-36
Return bus exception error count (sub-function code:
13) ••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4-37
Return bus message count (sub-function code: 11)
••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4-35
Index - 1
INDEX
[A]
PROGRAMMING
9
INDEX
Return diagnostic register (sub-function code: 02)
••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4-28
Return IOP overrun error count (sub-function code:
19) ••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4-43
Return query data (sub-function code: 00) •••••••• 4-25
Return slave busy count (sub-function code: 17) 4-41
Return slave message count (sub-function code: 14)
••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4-38
Return slave NAK count (sub-function code: 16)• 4-40
Return slave no response count (sub-function code:
15) ••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 4-39
[S]
Self-loopback test ••••••••••••••••••••••••••••••••••••••• 6-8
Slave function •••••••••••••••••••••••••••••••••••• A-14,5-17
Software Version •••••••••••••••••••••••••••••••••••••••• 2-8
[T]
Troubleshooting••••••••••••••••••••••••••••••••••••••••• 11-1
Turning off the ERR. LED••••••••••••••••••••••••••• 11-40
[U]
Unit test•••••••••••••••••••••••••••••••••••••••••••••••••••• 6-6
Utility package•••••••••••••••••••••••••••••••••••••••••••• 8-1
[W]
Write File Record (FC: 21) (SC: 06) •••••••••••••••• 4-57
Write Multiple Coils (FC: 15) ••••••••••••••••••••••••• 4-50
Write Multiple Registers (FC: 16)•••••••••••••••••••• 4-52
Write Single Coil (FC: 05)••••••••••••••••••••••••••••• 4-22
Write Single Register (FC: 06) ••••••••••••••••••••••• 4-23
[X]
X/Y Monitor/test ••••••••••••••••••••••••••••••••••••••••• 8-28
Index - 2
WARRANTY
Please confirm the following product warranty details before using this product.
1. Gratis Warranty Term and Gratis Warranty Range
If a.ny 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 logic 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 logic 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 logic 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 logic 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 logic 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 are registered trademarks of Microsoft Corporation in the United States and other
countries.
Adobe and Acrobat are registered trademarks of Adobe Systems Incorporated.
Pentium and Celeron are trademarks of Intel Corporation in the United States and other countries.
MODBUS is the registered trademark of Schneider Electric SA.
Other company names and product names used in this document are trademarks or registered trademarks of respective
owners.
MITSUBISHI ELECTRIC
HEADQUARTERS
EUROPEAN REPRESENTATIVES
EUROPEAN REPRESENTATIVES
EUROPEAN REPRESENTATIVES
MITSUBISHI ELECTRIC
EUROPE
EUROPE B.V.
German Branch
Gothaer Straße 8
D-40880 Ratingen
Phone: +49 (0) 2102 / 486-0
Fax: +49 (0) 2102 / 486-1120
e mail: [email protected]
MITSUBISHI ELECTRIC
FRANCE
EUROPE B.V.
French Branch
25, Boulevard des Bouvets
F-92741 Nanterre Cedex
Phone: +33 1 55 68 55 68
Fax: +33 1 55 68 56 85
e mail: [email protected]
MITSUBISHI ELECTRIC
IRELAND
EUROPE B.V.
Irish Branch
Westgate Business Park, Ballymount
IRL-Dublin 24
Phone: +353 (0) 1 / 419 88 00
Fax: +353 (0) 1 / 419 88 90
e mail: [email protected]
MITSUBISHI ELECTRIC
ITALY
EUROPE B.V.
Italian Branch
Via Paracelso 12
I-20041 Agrate Brianza (MI)
Phone: +39 039 6053 1
Fax: +39 039 6053 312
e mail: [email protected]
MITSUBISHI ELECTRIC
SPAIN
EUROPE B.V.
Spanish Branch
Carretera de Rubí 76-80
E-08190 Sant Cugat del Vallés
Phone: +34 9 3 / 565 3131
Fax: +34 9 3 / 589 2948
e mail: [email protected]
MITSUBISHI ELECTRIC
UK
EUROPE B.V.
UK Branch
Travellers Lane
GB-Hatfield Herts. AL10 8 XB
Phone: +44 (0) 1707 / 27 61 00
Fax: +44 (0) 1707 / 27 86 95
e mail: [email protected]
MITSUBISHI ELECTRIC
JAPAN
CORPORATION
Office Tower “Z” 14 F
8-12,1 chome, Harumi Chuo-Ku
Tokyo 104-6212
Phone: +81 3 6221 6060
Fax: +81 3 6221 6075
MITSUBISHI ELECTRIC
USA
AUTOMATION
500 Corporate Woods Parkway
Vernon Hills, IL 60061
Phone: +1 847 / 478 21 00
Fax: +1 847 / 478 22 83
GEVA
AUSTRIA
Wiener Straße 89
AT-2500 Baden
Phone: +43 (0) 2252 / 85 55 20
Fax: +43 (0) 2252 / 488 60
e mail: [email protected]
TEHNIKON
BELARUS
Oktjabrskaya 16/5, Ap 704
BY-220030 Minsk
Phone: +375 (0)17 / 22 75 704
Fax: +375 (0)17 / 22 76 669
e mail: [email protected]
Getronics b.v.
BELGIUM
Control Systems
Pontbeeklaan 43
B-1731 Asse-Zellik
Phone: +32 (0) 2 / 467 17 51
Fax: +32 (0) 2 / 467 17 45
e mail: [email protected]
TELECON CO.
BULGARIA
4, A. Ljapchev Blvd.
BG-1756 Sofia
Phone: +359 (0) 2 / 97 44 05 8
Fax: +359 (0) 2 / 97 44 06 1
e mail: —
INEA CR d.o.o.
CROATIA
Drvinje 63
HR-10000 Zagreb
Phone: +385 (0) 1 / 36 67 140
Fax: +385 (0) 1 / 36 67 140
e mail: —
AutoCont
CZECH REPUBLIC
Control Systems s.r.o.
Nemocnicni 12
CZ-702 00 Ostrava 2
Phone: +420 59 / 6152 111
Fax: +420 59 / 6152 562
e mail: [email protected]
louis poulsen
DENMARK
industri & automation
Geminivej 32
DK-2670 Greve
Phone: +45 (0) 70 / 10 15 35
Fax: +45 (0) 43 / 95 95 91
e mail: [email protected]
UTU Elektrotehnika AS
ESTONIA
Pärnu mnt.160i
EE-11317 Tallinn
Phone: +372 (0) 6 / 51 72 80
Fax: +372 (0) 6 / 51 72 88
e mail: [email protected]
Beijer Electronics OY
FINLAND
Ansatie 6a
FIN-01740 Vantaa
Phone: +358 (0) 9 / 886 77 500
Fax: +358 (0) 9 / 886 77 555
e mail: [email protected]
UTECO A.B.E.E.
GREECE
5, Mavrogenous Str.
GR-18542 Piraeus
Phone: +302 (0) 10 / 42 10 050
Fax: +302 (0) 10 / 42 12 033
e mail: [email protected]
Meltrade Automatika Kft. HUNGARY
55, Harmat St.
HU-1105 Budapest
Phone: +36 (0)1 / 2605 602
Fax: +36 (0)1 / 2605 602
e mail: [email protected]
SIA POWEL
LATVIA
Lienes iela 28
LV-1009 Riga
Phone: +371 784 / 22 80
Fax: +371 784 / 22 81
e mail: [email protected]
UAB UTU POWEL
LITHUANIA
Savanoriu pr. 187
LT-2053 Vilnius
Phone: +370 (0) 52323-101
Fax: +370 (0) 52322-980
e mail: [email protected]
INTEHSIS SRL
MOLDOVA
Cuza-Voda 36/1-81
MD-2061 Chisinau
Phone: +373 (0)2 / 562 263
Fax: +373 (0)2 / 562 263
e mail: [email protected]
Getronics b.v.
NETHERLANDS
Control Systems
Donauweg 2 B
NL-1043 AJ Amsterdam
Phone: +31 (0) 20 / 587 67 00
Fax: +31 (0) 20 / 587 68 39
e mail: [email protected]
Beijer Electronics AS
NORWAY
Teglverksveien 1
N-3002 Drammen
Phone: +47 (0) 32 / 24 30 00
Fax: +47 (0) 32 / 84 85 77
e mail: [email protected]
MPL Technology Sp. z o.o. POLAND
ul. Sliczna 36
PL-31-444 Kraków
Phone: +48 (0) 12 / 632 28 85
Fax: +48 (0) 12 / 632 47 82
e mail: [email protected]
Sirius Trading & Services srl ROMANIA
Str. Biharia No. 67-77
RO-013981 Bucuresti 1
Phone: +40 (0) 21 / 201 1146
Fax: +40 (0) 21 / 201 1148
e mail: [email protected]
INEA d.o.o.
SLOVENIA
Stegne 11
SI-1000 Ljubljana
Phone: +386 (0) 1-513 8100
Fax: +386 (0) 1-513 8170
e mail: [email protected]
Beijer Electronics AB
SWEDEN
Box 426
S-20124 Malmö
Phone: +46 (0) 40 / 35 86 00
Fax: +46 (0) 40 / 35 86 02
e mail: [email protected]
ECONOTEC AG
SWITZERLAND
Postfach 282
CH-8309 Nürensdorf
Phone: +41 (0) 1 / 838 48 11
Fax: +41 (0) 1 / 838 48 12
e mail: [email protected]
GTS
TURKEY
Darülaceze Cad. No. 43 Kat. 2
TR-80270 Okmeydani-Istanbul
Phone: +90 (0) 212 / 320 1640
Fax: +90 (0) 212 / 320 1649
e mail: [email protected]
CSC Automation Ltd.
UKRAINE
15, M. Raskova St., Fl. 10, Office 1010
UA-02002 Kiev
Phone: +380 (0) 44 / 238-83-16
Fax: +380 (0) 44 / 238-83-17
e mail: [email protected]
Avtomatika Sever Ltd.
RUSSIA
Lva Tolstogo St. 7, Off. 311
RU-197376 St Petersburg
Phone: +7 812 / 11 83 238
Fax: +7 812 / 11 83 239
e mail: [email protected]
CONSYS
RUSSIA
Promyshlennaya St. 42
RU-198099 St Petersburg
Phone: +7 812 / 325 36 53
Fax: +7 812 / 147 20 55
e mail: [email protected]
Electrotechnical
RUSSIA
Systems Siberia
Partizanskaya St. 27, Office 306
RU-121355 Moscow
Phone: +7 095/ 416-4321
Fax: +7 095/ 416-4321
e mail: [email protected]
Electrotechnical
RUSSIA
Systems Siberia
Shetinkina St. 33, Office 116
RU-630088 Novosibirsk
Phone: +7 3832 / 22-03-05
Fax: +7 3832 / 22-03-05
e mail: [email protected]
Elektrostyle
RUSSIA
ul. Garschina 11
RU-140070 Moscow
Phone: +7 095 / 514 9316
Fax: +7 095 / 514 9317
e mail: [email protected]
Elektrostyle
RUSSIA
Krasnij Prospekt 220-1
Office No. 312
RU-630049 Novosibirsk
Phone: +7 3832 / 10 66 18
Fax: +7 3832 / 10 66 26
e mail: [email protected]
ICOS
RUSSIA
Industrial Computer Systems Zao
Ryazanskij Prospekt 8a, Office 100
RU-109428 Moscow
Phone: +7 095 / 232 - 0207
Fax: +7 095 / 232 - 0327
e mail: [email protected]
NPP Uralelektra
RUSSIA
ul. Sverdlova 11a
RU-620027 Ekaterinburg
Phone: +7 34 32 / 53 27 45
Fax: +7 34 32 / 53 27 45
e mail: [email protected]
SSMP Rosgidromontazh Ltd. RUSSIA
23, Lesoparkovaya Str.
RU-344041 Rostov On Don
Phone: +7 8632 / 36 00 22
Fax: +7 8632 / 36 00 26
e mail: —
STC Drive Technique
RUSSIA
ul. Bajkalskaja 239, Office 2 - 23
RU-664075 Irkutsk
Phone: +7 3952 / 24 38 16
Fax: +7 3952 / 23 02 98
e mail: [email protected]
STC Drive Technique
RUSSIA
Poslannikov Per. 9, str.1
RU-107005 Moscow
Phone: +7 095 / 790-72-10
Fax: +7 095 / 790-72-12
e mail: [email protected]
MIDDLE EAST REPRESENTATIVE
TEXEL Electronics Ltd.
ISRAEL
Box 6272
IL-42160 Netanya
Phone: +972 (0) 9 / 863 08 91
Fax: +972 (0) 9 / 885 24 30
e mail: [email protected]
MITSUBISHI ELECTRIC
Gothaer Strasse 8 Phone: +49 2102 486-0
D-40880 Ratingen Hotline: +49 1805 000-765
AFRICAN REPRESENTATIVE
CBI Ltd.
SOUTH AFRICA
Private Bag 2016
ZA-1600 Isando
Phone: +27 (0) 11/ 928 2000
Fax: +27 (0) 11/ 392 2354
e mail: [email protected]
INDUSTRIAL AUTOMATION
Fax: +49 2102 486-7170 www.mitsubishi-automation.de
[email protected] www.mitsubishi-automation.com