- No category
advertisement
MITSUBISHI ELECTRIC
MELSEC System Q
Programmable Logic Controllers
User's Manual
(Application)
Serial Communications Modules
QJ71C24(-R2),
QJ71C24N(-R2)/(-R4)
Art. no.: 130025
01 12 2003
SH(NA)-080007
Version E
MITSUBISHI ELECTRIC
INDUSTRIAL AUTOMATION
• SAFETY PRECAUTIONS •
(Always read these instructions before using this equipment.)
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 for the PLC module to use.
In this manual, the safety instructions are ranked as "DANGER" and "CAUTION".
!
DANGER
!
CAUTION
Indicates that incorrect handling may cause hazardous conditions, resulting in death or severe injury.
Indicates that incorrect handling may cause hazardous conditions, resulting in medium or slight personal injury or physical damage.
Note that the
!
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
•
See manuals of each data link for the operating status of each station when there is a communication error in the data link.
There is the risk of an accident occurring due to output error or malfunctioning.
•
When using the notification function, the pager receiver may not be contacted due to the frequency transmission status from the system setup environment and error on the receiver side.
To ensure the safety of the PLC system, install a call circuit with a lamp display or buzzer sound.
•
When performing the control of the PLC in operation (changing data) by connecting a peripheral devices to the CPU module or personal computer, etc. to the intelligent device module, configure an interlock circuit in a sequence program so the safety of the overall system is always maintained.
Also when performing other controls of the PLC in operation (changing program and operation status (status control)), read this manual carefully and confirm if the overall safety is maintained.
Especially, when this control is performed to a remote PLC from an external device, troubles that have occurred on the PLC side may not be able to immediately be handled if there is a data communication error.
Define a troubleshooting agreement between external devices and the PLC CPU for data communication error occurrences, as well as construct an interlock circuit in the sequence program.
•
Do not write data into the "system area" of the buffer memory of intelligent function modules.
Also, do not use any "prohibited to use" signals as an output signal to an intelligent function module from the PLC CPU.
Writing data into the "system area" or outputting a signal for "prohibited to use" may cause a
PLC system malfunction.
A - 1 A - 1
[Design Precautions]
!
CAUTION
•
Do not bunch the control wires or communication cables with the main circuit or power wires, or install them close to each other.
They should be installed 100mm(3.9inch) or more from each other.
Not doing so could result in noise that may cause malfunction.
•
When using the module while values, such as buffer memory set values, are registered in the
Flash ROM, do not turn off the power supply for the module loading station nor reset the PLC
CPU.
If the power supply for the module loading station is turned off or the PLC CPU is reset while any values are registered, the data contents in the Flash ROM become inconsistent and as a result the values must be set again in the buffer memory, etc. and reregistered to the Flash ROM.
Also, this may cause failure and malfunction of the module.
[Installation Precautions]
!
CAUTION
•
Use the PLC in an environment that meets the general specifications contained in the user's manual for the CPU module to use.
Using this PLC in an environment outside the range of the general specifications may cause electric shock, fire, malfunction, and damage to or deterioration of the product.
•
When installing the module, securely insert the module fixing tabs into the mounting holes of the base unit while pressing the installation lever located a t the bottom of the module downward.
Securely fix the module with screws if it is subject to vibration during use.
•
Tighten the screws within the range of specified torque.
If the screws are loose, it may cause the module to fallout, short circuits, or malfunction.
If the screws are tightened too much, it may cause damage to the screw and/or the module, resulting in fallout, short circuits or malfunction.
•
Switch all phases of the external power supply off when mounting or removing the module.
Not doing so may cause damage to the module.
•
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 A - 2
[Wiring Precautions]
!
CAUTION
•
When turning on the power and operating the module after installation and wiring are completed, always attach the terminal cover that comes with the product.
There is a risk of electric shock if the terminal cover is not attached.
•
Perform correct pressure-displacement, crimp-contact or soldering for external wire connections using the tools specified by the manufactures.
Incorrect connection may cause short circuits, fire, or malfunction.
•
Attach connectors to the module securely.
•
Be sure to fix communication cables or power supply cables leading from the module by placing them in the duct or clamping them.
Cables not placed in the duct or without clamping may hang or shift, allowing them to be accidentally pulled, which may cause a module malfunction and cable damage.
•
Before connecting the cables, check the type o f interface to be connected.
Connecting or erroneous wiring to the wrong interface may cause failure to the module and external devices.
•
Tighten the terminal screws within the range of specified torque.
If the terminal screws are loose, it may result in short circuits or malfunction.
If the screws are tightened too much, it may cause damage to the screw and/or the module, resulting in fallout, short circuits or malfunction.
•
When removing the communication cable or power supply cable from the module, do not pull the cable. When removing the cable with a connector, hold the connector on the side that is connected to the module.
When removing the cable connected to the terminal block, first loosen the screws on the part that is connected to the terminal block.
Pulling the cable that is still connected to the module may cause malfunction or damage to the module or cable.
• Be careful not to let foreign matters such as sawdust or wire chips get inside the module.
They may cause fires, failure or malfunction.
•
The top surface of the module is covered with protective film to prevent foreign objects such as cable offcuts from entering the module when wiring.
Do not remove this film until the wiring is complete.
Before operating the system, be sure to remove the film to provide adequate heat ventilation.
A - 3 A - 3
[Starting and Maintenance Precautions]
!
CAUTION
• Do not disassemble or modify each module.
Doing so could cause failure, malfunction injury or fire.
•
Switch all phases of the external power supply off when mounting or removing the module.
Not doing so may cause failure or malfunction of the module.
•
Do not touch the connector while the power is on.
Doing so may cause malfunction.
•
Switch all phases of the external power supply off when cleaning or retightening terminal screws and module installing screws.
Not doing so may cause failure or malfunction of the module.
If the screws are loose, it may cause the module to fallout, short circuits, or malfunction.
If the screws are tightened too much, it may cause damages to the screws and/or the module, resulting in the module falling out, short circuits or malfunction.
•
Always make sure to touch the grounded metal to discharge the electricity charged in the body, etc., before touching the module.
Failure to do so may cause a failure or malfunctions of the module.
[Operation Precautions]
!
CAUTION
•
When performing the control of the PLC in operation (especially changing data, program, and operation status (status control)) by connecting a personal computer, etc. to the intelligent function module, read this manual carefully and confirm if the overall safety is maintained.
Failure to perform correct operation s to change data, program, or the status may result in system malfunction, machine damage, or an accident.
[Disposal Precautions]
!
CAUTION
•
When disposing of this product, treat it as industrial waste.
A - 4 A - 4
REVISIONS
Print Date Manual Number
Dec., 1999 SH (NA)-080007-A First Printing
The manual number is given on the bottom left of the back cover.
Revision
Oct., 2000 SH (NA)-080007-B Add the contents of the function version B.
Put Windows
®
base software products together from Mitsubishi
Programmable Logic Controller MELSEC series to Mitsubishi integrated
FA software MELSOFT series.
Standardize the name from software package (GPP function) to product name (GX Developer).
Correction
Entire manual (change MELSECNET/10H to MELSECNET/H), Contents,
About the Manuals, About the Generic Terms and Abbreviations, Section
1.1, 1.2 POINT, Section 2.1, 2.2.1, 2.2.3, 2.2.5, 2.2.6, 2.3.1, 2.3.2,
Section 3.1.1, 3.2.3, 3.2.4, 3.3.1, 3.3.4, 3.3.5, 3.3.6, 3.4 (entire), Section
4.3, Chapter 9 (entire), Chapter 11 (entire), Section 12.2, 12.3, 12.4
(entire), 12.6 (entire), Section 13.3, 13.4, 13.6 (entire), Section 15.3,
Section 16.2 (entire) to 16.7
Addition
Section 2.4(9), Section 3.2.3 POINT
Jun., 2001 SH (NA)-080007-C Standardize the name from utility package (QSCU) to product name (GX
Configurator-SC).
Correction
About the Manuals, The Manual's Use and Structure, About the Generic
Terms and Abbreviations, Program example (Section 9.4.1, 9.4.2, 9.4.3,
Section 11.5 (1) (2), Section 16.5, 16.6, 16.7), Section 1.1 (2) (diagram),
1.2, Chapter 3 (entire), Section 4.1 (2), Section 9.1.1 (4) 5), Section
11.3.2 (3), 11.3.3 (3), Section 13.6.1 (diagram)
Jan., 2003 SH(NA)-080007-D
Addition
Section 3.3.4, 3.3.6 (4), 3.4.5 (4)
Additional model
QJ71C24N,QJ71C24N-R2, QJ71C24N-R4
Correction
SAFETY PRECAUTIONS, About the Manuals, The Manual's Use and
Structure, About the Generic Terms and Abbreviations, Section 1.2,
Section 2.2.4 (2) (c), Section 3.3.1, 3.3.5, 3.3.6, 3.4.2, 3.4.3, 3.4.7,
3.4.8 (3), 3.5, Section 6.1, Section 7.1, 7.2, Section 9.1.1 (4), Section
10.4.1 (2) 1), Section 11.2.4 (2), 11.4.3 (a), 11.5, Section 15.1, 15.2,
15.3, 15.4.2, Section 17.1, 17.3, 17.4
Dec., 2003 SH(NA)-080007-E
Addition
Section 4.4.2 (6), Chapter 16 (entire)
Correction
About the Generic Terms and Abbreviations, Section 3.4.6 (4), Section
6.1, 6.3 (1) (b), Section 9.1.1 (4), Section 11.2.4 (2)
Japanese Manual Version SH-080002-H
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.
1999 MITSUBISHI ELECTRIC CORPORATION
A - 5 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.
Please forward a copy of this manual to the end user.
CONTENTS (This manual)
SAFETY PRECAUTIONS..............................................................................................................................A- 1
REVISIONS....................................................................................................................................................A- 5
CONTENTS....................................................................................................................................................A- 6
About the Manuals .........................................................................................................................................A-13
The Manual's Use and Structure ...................................................................................................................A-14
About The Generic Terms and Abbreviations...............................................................................................A-16
Definitions and Descriptions of Terminology.................................................................................................A-18
1 OVERVIEW 1- 1 to 1- 6
1.1 Overview.................................................................................................................................................. 1- 1
1.2 Functions Added/Changed by Function Version B................................................................................ 1- 6
2 Using the PLC CPU Monitoring Function 2- 1 to 2-29
2.1 Overview.................................................................................................................................................. 2- 1
2.2 About the PLC CPU Monitoring Function............................................................................................... 2- 3
2.2.1 Data registration for using the PLC CPU monitoring function ........................................................ 2- 3
2.2.2 PLC CPU monitoring information .................................................................................................... 2- 3
2.2.3 Timing for PLC CPU monitoring ...................................................................................................... 2- 5
2.2.4 Timings of transmission and notification of monitoring results to the external device................... 2- 6
2.2.5 Transmission methods of monitoring results and transmission data to the external device..................... 2- 9
2.2.6 Execution sequence for using the PLC CPU monitoring function.................................................. 2-20
2.3 Settings for Using the PLC CPU Monitoring Function........................................................................... 2-21
2.3.1 System setting items for the PLC CPU monitoring function ........................................................... 2-21
2.3.2 How to register and cancel the PLC CPU monitoring function....................................................... 2-26
2.4 Precautionary Notes for Using the PLC CPU Monitoring Function....................................................... 2-28
3 COMMUNICATIONS BY THE MODEM FUNCTION 3- 1 to 3-105
3.1 Overview.................................................................................................................................................. 3- 1
3.1.1 Features............................................................................................................................................ 3- 2
3.1.2 Function list....................................................................................................................................... 3- 5
3.1.3 Comparisons with related devices................................................................................................... 3- 6
3.2 System Configuration.............................................................................................................................. 3- 7
3.2.1 System configuration when performing data communication with an external device.................. 3- 7
3.2.2 System configuration when using the notification function............................................................. 3- 8
3.2.3 System configuration when connecting GX Developer .................................................................. 3- 9
3.2.4 Precautions for system configurations ............................................................................................ 3-10
3.3 Specifications .......................................................................................................................................... 3-12
3.3.1 Transmission specifications............................................................................................................. 3-12
3.3.2 Specification of connectable modems/terminal adapters ............................................................... 3-13
3.3.3 Compatibility with the QCPU remote password function................................................................ 3-16
A - 6 A - 6
3.3.4 Compatibility with the callback function........................................................................................... 3-22
3.3.5 I/O signals with the PLC CPU.......................................................................................................... 3-31
3.3.6 Buffer memory.................................................................................................................................. 3-33
3.3.7 Precautions when using the modem function ................................................................................. 3-46
3.4 Start-up of the Modem Function............................................................................................................. 3-52
3.4.1 Start-up procedures when communicating data with external devices.......................................... 3-52
3.4.2 Initial settings of the serial communication module......................................................................... 3-55
3.4.3 Register/read/delete of the initialization data .................................................................................. 3-58
3.4.4 Register/read/delete of the data for connection .............................................................................. 3-63
3.4.5 Initialization of modem/terminal adapter.......................................................................................... 3-68
3.4.6 Line connection ................................................................................................................................ 3-72
3.4.7 Data communication and notification............................................................................................... 3-78
3.4.8 Line disconnection............................................................................................................................ 3-84
3.5 Sample Programs ................................................................................................................................... 3-87
3.5.1 Sample program for data communication-1.................................................................................... 3-88
3.5.2 Sample program for data communication-2.................................................................................... 3-94
3.5.3 Sample program for notification.....................................................................................................3-103
4 RECEIVING DATA WITH AN INTERRUPT PROGRAM 4- 1 to 4- 6
4.1 Settings for Receiving Data Using an Interrupt Program ...................................................................... 4- 2
4.2 Interrupt Program Startup Timing........................................................................................................... 4- 2
4.3 Reception Control Method Using an Interrupt Program ........................................................................ 4- 3
4.4 Programming........................................................................................................................................... 4- 4
4.4.1 Program example............................................................................................................................. 4- 4
4.4.2 Precautions when receiving data with an interrupt program .......................................................... 4- 5
5 CHANGING SEND AND RECEIVE DATA LENGTH UNITS TO BYTE UNITS
(WORD/BYTES UNITS SETTING) 5- 1 to 5- 2
6 CHANGING THE DATA COMMUNICATIONS MONITORING TIMES 6- 1 to 6-13
6.1 No-Reception Monitoring Time (timer 0) Setting ................................................................................... 6- 2
6.2 Response Monitoring Time (timer 1) Setting ......................................................................................... 6- 7
6.3 Transmission Monitoring Time (timer 2) Setting .................................................................................... 6-10
6.4 Message Wait Time Setting.................................................................................................................... 6-13
7 DATA COMMUNICATIONS USING DC CODE TRANSMISSION CONTROL 7- 1 to 7- 8
7.1 Control Contents of DTR/DSR (ER/DR) Signal Control ........................................................................ 7- 2
7.2 Control Contents of DC Code Control.................................................................................................... 7- 4
7.3 Precautions when Using the Transmission Control Functions.............................................................. 7- 7
8 DATA COMMUNICATIONS USING HALF-DUPLEX COMMUNICATIONS 8- 1 to 8- 8
8.1 Half-duplex Communications.................................................................................................................. 8- 1
8.2 Data Transmission and Reception Timing............................................................................................. 8- 2
8.3 Changing the Communication System................................................................................................... 8- 6
8.4 Connector Connections for Half-duplex Communications..................................................................... 8- 7
8.5 Half-duplex Communications Precautions ............................................................................................. 8- 8
A - 7 A - 7
9 CONTENTS AND REGISTRATION OF THE USER FRAMES
FOR DATA COMMUNICATION 9- 1 to 9-18
9.1 User Frame Types and Contents During Communication .................................................................... 9- 1
9.1.1 User frames to be registered and used by the user........................................................................ 9- 1
9.1.2 Default registration frame (read only).............................................................................................. 9- 7
9.2 Transmission/Reception Processing Using User Frame Register Data ............................................... 9- 8
9.3 Precautions when Registering, Reading, Deleting and Using User Frames ........................................ 9-11
9.4 Register/Read/Delete User Frames ....................................................................................................... 9-13
9.4.1 Registering user frames................................................................................................................... 9-16
9.4.2 Reading user frames........................................................................................................................ 9-17
9.4.3 Deleting user frames........................................................................................................................ 9-18
10 ON-DEMAND DATA COMMUNICATIONS USING USER FRAMES 10- 1 to 10- 9
10.1 User Frame Data Communications Function.....................................................................................10- 1
10.2 User Frame Types and Registration ..................................................................................................10- 2
10.3 User Frame On-Demand Data Transmission and Buffer Memory Used..........................................10- 2
10.4 On-Demand Function Control Procedure During User Frame Use ..................................................10- 4
10.4.1 Data communication using the ASCII code ................................................................................ 10- 4
10.4.2 Data communications using the binary code ..............................................................................10- 6
10.5 Example of an On-Demand Data Transmission Program Using User Frames................................10- 8
11 DATA COMMUNICATIONS USING USER FRAMES 11- 1 to 11-39
11.1 Overview of Data Communication Procedure....................................................................................11- 2
11.2 Data Reception ...................................................................................................................................11- 3
11.2.1 About reception data....................................................................................................................11- 3
11.2.2 Timing for start/completion of data reception..............................................................................11-10
11.2.3 Receive procedure.......................................................................................................................11-14
11.2.4 User frame setting for reception ..................................................................................................11-15
11.3 Receive Program ................................................................................................................................11-21
11.3.1 Sequence program example........................................................................................................11-21
11.3.2 Application example for data reception using a combination that specifies the first frame.......11-22
11.3.3 Application example for data reception using a combination that does not specify the first frame................................................................................................................................11-28
11.4 Data Transmission..............................................................................................................................11-30
11.4.1 Send data .....................................................................................................................................11-30
11.4.2 Transmission procedure ..............................................................................................................11-32
11.4.3 Settings for transmission user frames.........................................................................................11-33
11.5 Transmission program ........................................................................................................................11-37
12 Transparent Codes and Additional Codes 12- 1 to 12-20
12.1 Handling the Transparent Code and Additional Code Data..............................................................12- 1
12.2 Registering Transparent Codes and Additional Codes .....................................................................12- 2
12.3 Handling Transparent Codes and Additional Codes During Non Procedure Protocol Data
Communication...................................................................................................................................12- 3
12.4 Example of Data Communication Using the Non Procedure Protocol .............................................12- 8
A - 8 A - 8
12.4.1 Example of data reception ...........................................................................................................12- 9
12.4.2 Example of data transmission......................................................................................................12-11
12.5 Handling Transparent Codes and Additional Codes During Bidirectional Protocol Data
Communication...................................................................................................................................12-13
12.6 Example of Data Communication Using the Bidirectional Protocol ..................................................12-16
12.6.1 Example of data reception ...........................................................................................................12-17
12.6.2 Example of data transmission......................................................................................................12-19
13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION) 13- 1 to 13-14
13.1 ASCII-BIN Conversion........................................................................................................................13- 1
13.2 Settings for ASCII-BIN Conversion ....................................................................................................13- 1
13.3 Performing ASCII-BIN Conversion for Data Communicated via Non Procedure Protocol ..............13- 2
13.4 Example of Data Communication Using the Non Procedure Protocol .............................................13- 4
13.4.1 Example of data reception ...........................................................................................................13- 5
13.4.2 Example of data transmission......................................................................................................13- 8
13.5 Performing ASCII-BIN Conversion for Data Communicated Via the Bidirectional Protocol ............13-10
13.6 Example of Data Communication Using the Bidirectional Protocol ..................................................13-12
13.6.1 Example of data reception ...........................................................................................................13-13
13.6.2 Example of data transmission......................................................................................................13-14
14 DATA COMMUNICATIONS USING EXTERNAL DEVICE AND PLC CPU M :
N CONFIGURATION 14- 1 to 14-11
14.1 Data Communications Precautions....................................................................................................14- 1
14.2 External Devices Interlock Conditions................................................................................................14- 3
14.2.1 Maximum communications time per external device station......................................................14- 3
14.2.2 Message structure when communicating data between external devices.................................14- 4
14.3 Examples of Procedure for Data Communications with the PLC CPU.............................................14- 6
14.3.1 Sequential data communications between external devices and the PLC CPU .......................14- 6
14.3.2 Data communications between PLC CPU and external devices by designating a master station and slave stations .............................................................................................14- 9
15 SWITCHING THE MODE AFTER STARTING 15- 1 to 15-10
15.1 Mode Switching Operation and Contents that can be Changed.......................................................15- 2
15.1.1 Settings that can be changed with mode switching....................................................................15- 2
15.1.2 Operation for mode switching......................................................................................................15- 2
15.2 Mode Switching Precautions ..............................................................................................................15- 3
15.3 I/O Signals for Handshake with PLC CPU and Buffer Memory ........................................................15- 5
15.4 Switching the Mode from the PLC CPU.............................................................................................15- 7
15.4.1 Mode switching procedure...........................................................................................................15- 7
15.4.2 Mode switching sample program.................................................................................................15- 8
15.5 Switching the Mode from an External Device ....................................................................................15- 9
15.5.1 Mode switching procedure...........................................................................................................15- 9
15.5.2 Mode switching sample program.................................................................................................15-10
16 USING COMMUNICATION DATA MONITORING FUNCTION 16- 1 to 16-10
16.1 Communication Data Monitoring Function.........................................................................................16- 1
16.1.1 Outline ..........................................................................................................................................16- 1
A - 9 A - 9
16.1.2 Communication data monitoring operation .................................................................................16- 2
16.2 Communication Data Monitoring Function Settings ..........................................................................16- 4
16.3 Communication Data Monitoring Example.........................................................................................16- 8
17 Dedicated Instructions 17- 1 to 17-25
17.1 Dedicated Instruction List ...................................................................................................................17- 1
17.2 BUFRCVS Instruction.........................................................................................................................17- 2
17.3 CSET Instruction (PLC CPU Monitoring Register/Cancel)................................................................17- 5
17.4 CSET Instruction (Initial Settings).......................................................................................................17-11
17.5 GETE Instruction.................................................................................................................................17-15
17.6 PRR Instruction...................................................................................................................................17-18
17.7 PUTE Instruction.................................................................................................................................17-21
INDEX Index- 1 to Index- 2
A - 10 A - 10
(Related Manual-1) … Q Corresponding Serial Communication Module User's Manual (Basic)
1 OVERVIEW
1.1 Overview of the Serial Communication
Module
1.2 Features of the Serial Communication Module
1.3 About Added/Changed Functions in Function
Version B
SH-080006-F
6 DATA COMMUNICATION USING THE NON
PROCEDURE PROTOCOL
6.1 Data Reception from the External Device
6.2 Sending Data to the External Device
6.3 Data Communications Precautions
2 SYSTEM CONFIGURATION AND AVAILABLE
FUNCTIONS
2.1 Applicable Systems
2.2 Combinations of PLC CPU and External
Device, and Available Functions
2.3 When Using the Remote Password Function of the QCPU
2.4 When Using the Q Series C24 at a Remote
I/O Station
2.5 When Using the Q Series C24 under the
Multiple CPU System with Several QCPUs
(Function Version B)
2.6 When Using the Q Series C24 with the
Q00J/Q00/Q01CPU
2.7 Checking the Function Version, Serial No., and Software Version
7 DATA COMMUNICATION USING THE
BIDIRECTIONAL PROTOCOL
7.1 Data Reception from the External Device
7.2 Sending Data to the External Device
7.3 Processing when Simultaneous Transmission
Performed During Full-Duplex
Communications
7.4 Data Communications Precautions
8 UTILITY PACKAGE (GX Configurator-SC)
8.1 Functions Available with Utility Package
8.2 Installing and Uninstalling Utility Package
8.3 Explanation of Utility Package Operation
8.4 System Registration to Flash ROM
8.5 Auto Refresh Setting
8.6 Monitor/Test
8.7 Non Procedure Protocol Receive Data Clear
3 SPECIFICATIONS
3.1 Performance Specifications
3.2 RS-232 Interface Specification
3.3 RS-422/485 Interface Specifications
3.4 Serial Communication Module Function List
3.5 Dedicated Instruction List
3.6 Utility Package (GX Configurator-SC)
Function List
3.7 List of GX Developer Setting Items for Serial
Communication Modules
3.8 List of Input/Output Signals for the PLC CPU
3.9 List of Applications and Assignments of the
Buffer Memory
4 SETTINGS AND PROCEDURES PRIOR TO
OPERATION
4.1 Handling Precautions
4.2 Settings and Procedures Prior to Operation
4.3 Part Names and Functions
4.4 External Wiring
4.5 Settings for GX Developer
4.6 Settings with the Utility Package (GX
Configurator-SC)
4.7 Individual Station Test
4.8 Loopback Test
4.9 Maintenance and Inspection
5 DATA COMMUNICATION USING THE MELSEC
COMMUNICATION PROTOCOL
5.1 Data Communication Functions
5.2 Utilizing the MX Component
9 DEDICATED INSTRUCTIONS
9.1 Dedicated Instruction List
9.2 ONDEMAND Instruction
9.3 OUTPUT Instruction
9.4 INPUT Instruction
9.5 BIDOUT Instruction
9.6 BIDIN Instruction
9.7 SPBUSY Instruction
9.8 CSET (Receive data clear)
10 TROUBLESHOOTING
10.1 Checking the Status of the Serial
Communication Module
10.2 Error Code Tables
10.3 Troubleshooting by Symptom
APPENDIX
Appendix 1 Functional Improvements of the Q
Series C24
Appendix 2 QnA/A Series Module
Appendix 3 Processing Time
Appendix 4 ASCII-Code Table
Appendix 5 External Dimensions
Appendix 6 Example of Connection when a
Converter is Used
Appendix 7 Communication Support Tool (MX
Component)
Appendix 8 Example of Clear Process Program for Receive Data
Appendix 9 Setting Value Recording Sheet
A - 11 A - 11
(Related Manual-2) … Q Corresponding MELSEC Communication Protocol Reference Manual
SH-080008-E
1 OVERVIEW
1.1 Overview of the MELSEC Communication
Protocol
1.2 Features of the MELSEC Communication
Protocol
2 DATA COMMUNICATION USING THE MELSEC
COMMUNICATION PROTOCOL
2.1 Types and Applications of Data
Communication Frames
2.2 Accessible Range of Each Data
Communication Frames
2.3 How to Read the Control Procedures of the
MC Protocol
2.4 Access Timing of the PLC CPU Side
2.5 Setting Method for Writing to the PLC CPU during RUN
2.6 Accessing Other Stations
2.7 Precautions on Data Communication
2.8 Time Chart and Communication Time of the
Transmission Sequence of the Serial
Communication Module
2.9 Transmission Time When Accessing Other
Stations Via MELSECNET/H, MELSECNET/10
2.10 Compatibility with Multiple CPU Systems
2.11 Compatibility with the Q00CPU, Q01CPU
Serial Communication Function
3 WHEN COMMUNICATING USING THE QnA
COMPATIBLE 3E/3C/4C FRAMES
3.1 Message Formats
3.2 List of Commands and Functions for the QnA
Compatible 3E/3C/4C Frames
3.3 Device Memory Read/Write
3.4 Buffer Memory Read/Write
3.5 Reading from and Writing to the Buffer
Memory of an Intelligent Function Module
3.6 PLC CPU Status Control
3.7 Drive Memory Defragmentation (for Other
Station QnACPU)
3.8 File Control
3.9 Registering, Deleting and Reading User
Frames: for Serial Communication Modules
3.10 Global Function: for Serial Communication
Modules
3.11 Data Transmission to an External device
(On-Demand Function): for Serial
Communication Modules
3.12 Initializing the Transmission Sequence: for
Serial Communication Modules
3.13 Mode Switching: for Serial Communication
Module
3.14 Turning Off Displayed LEDs and Initializing
Communication Error Information and Error
Code: for Serial Communication Module
3.15 Turning Off the COM.ERR LED: for Ethernet
Modules
3.16 Loopback Test
3.17 Registering or Canceling PLC CPU
Monitoring: for Serial Communication
Modules
3.18 Remote Password Unlock/Lock
4 WHEN COMMUNICATING USING THE QnA
COMPATIBLE 2C FRAMES
4.1 Control Procedures and Message Formats
4.2 Contents of the Data Designation Items
4.3 List of Commands and Functions for QnA
Compatible 2C Frames
4.4 Precautions on the Data Communication
4.5 Example of Data Communication Using QnA
Compatible 2C Frames
5 WHEN COMMUNICATING USING THE A
COMPATIBLE 1C FRAMES
5.1 Control Procedures and Message Formats
5.2 Device Memory Read/Write
5.3 Extension File Register Read and Write
5.4 Reading and Writing in the Buffer Memory of an Intelligent Function Module
5.5 Loopback Test
6 WHEN COMMUNICATING USING THE A
COMPATIBLE 1E FRAMES
6.1 Message Formats and Control Procedures
6.2 List of Commands and Functions for A
Compatible 1E Frames
6.3 Device Memory Read/Write
6.4 Extension File Register Read and Write
6.5 Reading and Writing in the Buffer Memory of an Intelligent Function Module
APPENDIX
Appendix-1 Reading and Writing by Designation of the Device Memory Extension
Appendix 2 Reading from and Writing to the
Buffer Memory
Appendix-3 Processing Time of the PLC CPU
Side While Communicating Using the MC Protocol
A - 12 A - 12
About the Manuals
The following manuals are available for this product.
Please order the desired manuals using the chart below.
Related Manuals
Manual name
Q Corresponding Serial Communication Module User's Manual (Basic)
This manual explains an overview of the module and describes the applicable system configuration, the specifications, the procedures prior to operations, the basic methods of communicating with the external device, maintenance and inspection, and the troubleshooting of the Q-series serial communication module.
(Sold separately)
Q Corresponding MELSEC Communication Protocol Reference Manual
This manual explains information on how the external device reads data from and writes data to the PLC
CPU through communication using the MC protocol by utilizing the Q series C24/Q series E71.
(Sold separately)
GX Configurator-SC Version 2 Operating Manual (Protocol FB support function)
This manual explains the function and usage of the protocol FB support function that supports the creation of the data communication program of the module and set up of each parameter.
(Sold separately)
Manual number
(Model code)
SH-080006
(13JL86)
SH-080008
(13JF89)
SH-080393E
(13JU46)
A - 13 A - 13
The Manual's Use and Structure
How to use this manual
This manual describes the use of special functions for the Q series C24
(QJ71C24N, QJ71C24N-R2, QJ71C24N-R4, QJ71C24, QJ71C24-R2), with each chapter covering a specific function. Please read this manual and use the contents below as a reference.
(1) To read an overview of special functions
• An overview of the major special functions is describes in Chapter 1.
(2) To use the function that monitors errors in the PLC CPU
• Chapter 2 describes the PLC CPU monitoring function, which monitors the
PLC CPU status and devices and automatically sends status information to the opposite communicating device upon the occurrence of an error.
To use the PLC CPU monitoring function from the external device using the MC protocol, refer to the reference manual for details on how to start and cancel PLC CPU monitoring.
(3) To use the data communication function for the exchange of data with an external device at a remote location
• Chapter 3 describes the specifications, procedures and other items regarding communication using a modem function in order to exchange of data with an external device at a remote location.
(4) To use the function for reading received data from the external device using an interrupt program in order to reduce the scan time
• Chapter 4 describes the programming for execution of a receiving program only when data from the external device is received.
(5) To use the function for monitoring the data communication time with the external device
• Chapter 6 describes the function that monitors the data communication time with the external device, along with the reception-interval time and the response-reception time for transmission.
(6) To use the transmission control function to control data transmission/reception with the external device.
• Chapter 7 describes the DTR/DSR control and the DC code function to control the data communication with the external device.
(7) To use the function for simplifying the data communication program with the registration data when preregistering the fixed-format section of the communication message
• Chapters 9 to 11 describe the data transmission/reception function with user frames in which the fixed-format section of the communication message has been preregistered.
A - 14 A - 14
(8) To use the function that performs the data communication in ASCII code with the external device
• Chapter 13 describes the handling of binary code on the PLC CPU and ASCII-
BIN conversion function for communicating ASCII code data for an external device.
(9) To use dedicated instructions
• Chapter 17 describes the dedicated instructions that are used to execute the functions explained in this manual.
Structure of this manual
This manual describes how to use the utility package for the Q series C24 (GX
Configurator-SC) in order to perform the initial settings used to execute special functions.
For details on the screens used for entering setting values, see Chapter 8 of
User's Manual (Basic).
A - 15 A - 15
About the Generic Terms and Abbreviations
This manual uses the following generic terms and abbreviations to describe the Q series C24 unless otherwise specified.
Generic term/abbreviation
Ethernet modules
Q series E71 (E71)
Q series C24 (C24)
QC24
QC24N
QC24(N)
QCPU
QCPU station
QnACPU
QnACPU station
Q/QnACPU
UC24
Computer link modules
Serial communication modules
(1) Generic terms and abbreviations
In this manual, the following generic terms and abbreviations are used to indicate the PLC CPU and the Q series C24 used for the data-communication functions of the serial communication modules. The model names of serial communication modules are used to identify the specific models.
Description of generic term/abbreviation
Abbreviations for Q series Ethernet interface modules QJ71E71-100, QJ71E71-B5, QJ71E71-B2
(Indicated as "E71" in the diagrams)
Abbreviations for Q series serial communication modules QJ71C24N, QJ71C24N-R2, QJ71C24N-
R4, QJ71C24, QJ71C24-R2 (Indicated as "C24" in the diagrams)
Generic term for AJ71QC24, AJ71QC24-R2, AJ71QC24-R4, A1SJ71QC24, A1SJ71QC24-R2
Generic term for AJ71QC24N, AJ71QC24N-R2, AJ71QC24N-R4, A1SJ71QC24N, A1SJ71QC24N-
R2
Generic term for QC24, QC24N
Q mode
Generic term for Q00JPUC, Q00CPU, Q01CPU, Q02CPU, Q02HCPU, Q06HCPU,
Q12HCPU, Q25HCPU, Q12PHCPU, Q25PHCPU
Abbreviation for PLC installed QCPU.
Generic term for Q2ACPU, Q2ACPU-S1, Q2ASCPU, Q2ASCPU-S1, Q2ASHCPU, Q2ASHCPU-S1,
Q3ACPU, Q4ACPU, Q4ARCPU
Abbreviation for PLC installed QnACPU.
Generic term for QCPU, QnACPU
Generic term for AJ71UC24, A1SJ71UC24-R2, A1SJ71UC24-R4, A1SJ71UC24-PRF,
A1SJ71C24-R2, A1SJ71C24-R4, A1SJ71C24-PRF, A2CCPUC24, A2CCPUC24-PRF
A series computer link modules
Generic term for the module below.
QnA series
Q series
AJ71QC24, AJ71QC24-R2, AJ71QC24-R4, A1SJ71QC24, A1SJ71QC24-R2,
AJ71QC24N, AJ71QC24N-R2, AJ71QC24N-R4, A1SJ71QC24N, A1SJ71QC24N-R2
QJ71C24N, QJ71C24N-R2, QJ71C24N-R4, QJ71C24, QJ71C24-R2
A - 16 A - 16
Generic term/abbreviation
Buffer memory
Computer
Data communication functions
GX Configurator-SC
GX Developer
I/F
Intelligent function modules
Intelligent function module devices
MELSECNET/10
MELSECNET/H
MX Component
Operating Manual
(Protocol FB support function)
Opposite devices
External devices
Reference manual
RS-232 (Interface)
RS-422/485 (Interface)
Special function modules
Switch setting
User's manual (Basic) or Basic
User's manual (Application) or
Application
(2) Other generic terms and abbreviations
This manual uses the following generic terms and abbreviations to explain the data-communication devices for the Q series C24. The names/model names are provided when it is necessary to explicitly identify the model being discussed.
Description of generic term/abbreviation
Generic term for buffer memory of the intelligent function modules/special function modules used for storing data sent to or received from the PLC CPU (setting values, monitor values, etc.)
Generic term for the external devices with which data can be sent/received using the MC protocol or the bidirectional protocol.
Generic term for MC protocol, non procedure protocol, and bidirectional protocol
Abbreviation for GX Configurator-SC (SW0D5C-QSCU-E or later).
• Initial settings for the module, monitoring and testing can be performed without using a sequence program and without considering I/O signals or buffer memory. (Intelligent function utility)
• Converting sequence programs necessary for data communication processing into FB can shorten program production man-hours.
In addition, the monitoring and analysis of the transmitted/received data by the communication network can shorten the system start-up time. (Protocol FB support function)
Abbreviation for GX Developer (SWnD5C-GPPW-E) (n in the model should be 4 or greater)
Abbreviation for Interface
Generic terms for the Q series PLC modules that are operated by commands from the PLC CPU
(equivalent to the A series PLC special function modules).
Examples:
• CC-Link interface module
• A/D and D/A conversion modules
• Ethernet interface module
• Serial communication module
Generic terms for buffer memory of the intelligent function modules used for storing data sent to or received from the PLC CPU (setting values, monitor values, etc.)
Abbreviation for MELSECNET/10 network system
Abbreviation for MELSECNET/H network system
Abbreviation for MX Component (SWnD5C-ACT-E or later)
GX Configurator-SC Version 2 Operating Manual (Protocol FB support function)
Generic term for Computers, indicators, measuring instruments, ID modules, bar code readers, regulators, other serial communication modules, C24, etc. that are connected to the Q series C24 for data communication.
Q corresponding MELSEC communication protocol reference manual
Abbreviation for Interface conforming to RS-232
Abbreviation for Interface conforming to RS-422 and RS-485
Generic term for the A/QnA series PLC modules that are operated by commands from the PLC
CPU (equivalent to the Q series PLC intelligent function modules).
Examples:
• CC-Link interface module
• A/D and D/A conversion modules
• High-speed counter module
• Ethernet interface module
• Computer link module and serial communication module
Generic term for intelligent function module switch setting
Q corresponding serial communication module user's manual (Basic)
Q corresponding serial communication module user's manual (Application)
A - 17 A - 17
Definitions and Descriptions of Terminology
The following table lists the definitions and descriptions of terminology used in this manual and related manuals for the Q series C24.
Terminology Description
A compatible 1C frame
Bidirectional protocol
Multidrop connection
Non procedure protocol
(Formats 1 to 4)
One of the message formats for the serial communication modules for performing communication using the MC protocol and ASCII code data.
This is the same message format as when communicating using the protocol for the A series computer link modules. Device memory read/write operations for the QCPU are allowed within the device range of the AnACPU.
Details are explained in Chapter 5 of the Reference Manual.
A communication procedure for the serial communication modules and one of the data communication functions for communicating any data between the PLC CPU and an opposite device. Details are explained in Chapter 7.
Independent operation
Linked operation
MELSEC communication protocol
(MC protocol)
Message send function
(Printer function)
A mode of interface operation to communicate data with external devices using a function specified in each communication protocol setting. Two interfaces of serial communication modules do not interact.
The operation mode of each of the two interfaces for a serial communication modules that are connected to external devices and linked to one another in order to communicate data to/from the external devices.
The two interfaces communicate data using the identical data-communication function (MC protocol (identical format) or non procedure protocol) and the identical transmission specifications.
(Linked operation using the bidirectional protocol is not allowed.)
A communication procedure for the Q series serial communication modules or the Ethernet interface modules, and a name of communication method for accessing to the PLC CPU from an external device. (This is called the MC protocol in this manual.)
There are two communication methods; one uses ASCII code data and the other uses binary code data.
Details are explained in the Reference Manual.
This function registers character data (messages) to be sent to external devices (mainly printers) in the serial communication modules as an user frame in advance, and sends the registered data for multiple user frames using the non procedure protocol (sent by an instruction from the PLC
CPU).
A name of the connection when multiple external devices or other serial communication modules are connected in a 1:n or m:n mode using the serial communication module's RS-422/485 interface.
An user's communication procedure and one of the data communication functions for communicating any data between the PLC CPU and an external device. Details are explained in
Chapter 6.
QnA compatible 2C frame
(Formats 1 to 4)
QnA compatible 3C frame
(Formats 1 to 4)
QnA compatible 4C frame
(Formats 1 to 4)
One of the message formats for the serial communication modules for performing communication using the MC protocol and ASCII code data.
This is the same message format as the communication frame using the protocol for the QnA series serial communication modules.
• QnA compatible 2C frame (Formats 1 to 4): QnA simplified frame (Formats 1 to 4)
Details are explained in Chapter 4 of the Reference Manual.
One of the message formats for the serial communication modules for performing communication using the MC protocol and ASCII code data.
This is the same message format as the communication frame using the protocol for the QnA series serial communication modules.
• QnA compatible 3C frame (Formats 1 to 4): QnA frame (Formats 1 to 4)
• QnA compatible 4C frame (Formats 1 to 4): QnA extension frame (Formats 1 to 4)
Details are explained in Chapter 3 of the Reference Manual.
A - 18 A - 18
User frame
Terminology
QnA compatible 4C frame
Description
(Format 5)
One of the message formats for the serial communication modules for performing communication using the MC protocol and binary code data.
This is the same message format as the communication frame using the protocol for the QnA series serial communication modules.
• QnA compatible 4C frame (Format 5): QnA extension frame (Format 5)
Details are explained in Chapter 3 of the Reference Manual.
Data name when the fixed format portion of messages to be sent or received between a serial communication module and an external device is registered in the module and used for sending and receiving data with the functions listed below. (The contents of a user frame data should conform to the specifications of the external device.)
The data array of the head and tail sections of a message (transmission control code, C24 station number, sum check, fixed data, etc.) to be sent and received is registered in the serial communication module before use.
• MC protocol on-demand function.
• Data-communication function using the non procedure protocol.
Details are explained in Chapter 9 of the User's Manual (Applications).
A - 19 A - 19
1 OVERVIEW
MELSEC-Q
1
1 OVERVIEW
1.1 Overview
This manual explains special functions of the MELSEC-Q series C24.
This chapter provides an overview of these special functions. The primary special functions of the Q series C24 and a functional overview are indicated below.
(1) Monitoring the PLC CPU (detailed explanation in Chapter 2)
(a) The local station PLC CPU can be monitored at time intervals set by the user without a sequence program.
1) The following information can be registered as items to be monitored.
(Monitoring a device for the local station PLC CPU)
• A numeric value stored in a word device
• The ON/OFF status of a bit device
(Monitoring the status of the local station PLC CPU)
• Monitoring the status of the local station CPU module
2) For the results of the PLC CPU monitoring, the following monitored information can be transmitted/notified.
• Transmission of information on the device to be monitored and status of the PLC CPU (Monitoring information obtained through combined use of the modem function can also be transmitted.)
• Notification of notification messages (character string data) registered for connecting the modem function when using with the modem function together
3) The user can select one of the following as transmission timing for the
PLC CPU monitoring results to the external device.
• Transmission/notification each time the PLC CPU is monitored.
(Constant cycle transmission)
• Transmission/notification when the information read from the PLC
CPU agrees with conditions set by the user. (Condition agreement transmission)
(b) The PLC CPU monitoring function can be used in communication using MC protocol or non procedure protocol.
(c) Using the PLC CPU monitoring function makes it possible to do the following:
• Sends device data without using a sequence program
• Simplifies the device monitor procedure
• Sends CPU module error information
MELSEC
POWER
Q25HCPU
MODE
RUN
ERR.
USER
BAT.
BOOT
QJ71C24
CH1.
CH1.
CH2.
RS-232
CPU error information
Monitoring device information
External device
PULL
MITSUBISHI
USB
RS-232
CH.2
SDA
SG
SDB
(FG)
RDA
(FG)
RDB
RS-422
/485
2
4
6
1
3
7
5
Abnormal detection
Error occurrence
1 - 1 1 - 1
1 OVERVIEW
MELSEC-Q
(2) Communicating with the external device at a remote location via a modem (detailed explanation in Chapter 3)
1) Connecting a modem or TA (terminal adapter) to the RS-232 interface facilitates communication via a public line/private line/digital line (ISDN), such as data communication with a device at a remote location (listed below) and calling a pager device.
• Data communication using the MC protocol
• Data sending and receiving using the non procedure protocol
• Data communication using the bidirectional protocol
• PLC access using the GX Developer
2) Initialization of a modem or TA, line connection (dialing), and line disconnection are performed by the PLC CPU.
3) When a remote password is set in the QCPU with the GX Developer, the following access from the external device to QCPU using the Q series C24 modem function can be performed by executing the unlock processing to the remote password.
• Data communication using MC protocol
• Accessing the PLC using the GX Developer
The remote password function is a QCPU function designed to prevent improper access to the QCPU by users.
The QCPU remote password function can be used by setting a remote password in the QCPU with the GX Developer.
1
Q series C24
Modem/TA ( 1)
Modem/TA ( 1) External device
RS-232
1 TA is an abbreviation for Terminal Adapter.
Pager receiver
1 - 2 1 - 2
1 OVERVIEW
MELSEC-Q
(3) Receiving data with an interrupt program (detailed explanation in
Chapter 4)
1) In data communication between the Q series C24 and the external device, data can be received using an interrupt program with the following data communication functions.
• Data reception during communication using the non procedure protocol
• Data reception during communication using the bidirectional protocol
2) Receiving data using an interrupt program expedites data reception by the
PLC CPU.
Data transmission
Q series C24
Receive
Interrupt issued
Main program Main program
PLC CPU
Interrupt program executed
I
FEND
SM400
BUFRCVS
External device side
PLC CPU side
(4) Controlling data communication in accordance with the external device (detailed explanation in Chapter 7)
1) The Q series C24 controls data communication with the external device by turning ON/OFF the DTR/DSR signal and sending/receiving the DC code.
2) DTR/DSR signal control
Using the DTR (ER) and DSR (DR) signals, the external device is notified of whether or not data communication can be performed.
3) DC code control
By sending/receiving the DC1 and DC3 code data, the external device is notified of whether or not data can be received. By enclosing the user data with the DC2 and DC4 code data, the external device is notified of the valid transmission data range.
Data 1-1
(Interruption) (Restart)...From the succeeding data
Data 1-2
Data 2-1
(Interruption)
Data 2-2
(Restart)...From the
succeeding
data
DTR signal
DSR signal
External device side
PLC CPU side
Data 1-1
D
C
3
(Interruption)
D
C
1
(Restart)...From the succeeding data
Data 1-2
D
C
3
Data 2-1
D
C
1
(Interruption)
Data 2-2
(Restart)...From the
succeeding
data
1 - 3 1 - 3
1 OVERVIEW
MELSEC-Q
(5) Converting binary code data to ASCII code data to communicate with the external device specification (detailed explanation in
Chapter 13)
1) Binary code data that is processed by the PLC CPU can be converted to
ASCII code data for communication.
2) ASCII-BIN conversion is performed by the Q series C24 according to user settings.
Q series C24
External device
Head data
L H
Buffer memory
H L
1234
H
(12
H
) (34
H
)
34
H
12
H
L H
(3) (4) (1) (2)
33
H
34
H
31
H
32
H
(6) Sending/receiving data in a message format tailored to the external device (detailed explanation in Chapters 9 to 11)
1) By preregistering the data arrangement (user frames) of the messages to be sent and received by the external device, to the Q series C24, the following data communications can be performed using registered frames.
• MC protocol: Data transmission from the PLC CPU to the external device using the on-demand function
• Non procedure protocol: Data communication between the PLC CPU and the external device
2) For example, multiple first frames and last frames (called user frames) with the definition shown in the diagram below can be preregistered in the Q series C24. When sending data to the external device, the data that is arranged as shown in the diagram below can be sent by designating the preregistered user frame numbers and arbitrary data. When receiving data from the external device, by setting the preregistered user frame numbers for reception at the startup of the Q series C24, the arbitrary data section can be read to the PLC CPU when the message with the registered content is received.
ENQ Arbitrary data CR LF
First frame
Last frame
Before sending data, the Q series C24 adds the first frame and last frame to arbitrary data. When data is received, the arbitrary data section is stored in the buffer memory as receive data.
3) User frames and various setting values for data communication with the external device can be preregistered to the Q series C24 flash ROM.
1 - 4 1 - 4
1 OVERVIEW
MELSEC-Q
The following table shows which special functions are available for the main data communication functions of the Q series C24.
Main data communication functions
Special functions
Monitoring of the PLC CPU using the PLC CPU monitoring function
Data communication to a remote location using the modem function
Reading received data using an interrupt program
Changing the unit of the data length for communication data
Changing the monitoring time for data communication
Transmission control for data communication
• DC code control (Including Xon/Xoff control)
• DTR/DSR (ER/DR) control
Data communication using half-duplex communication
Data communication using user frames Registration
Transmission, reception
Data communication using the transparent code
Communication using ASCII code data by ASCII-BIN conversion
Data communication with multiple external devices using a multidrop connection (m:n connection)
Changing the interface mode after starting data communication
(Changes to communication protocol and transmission specifications)
MC protocol
Non procedure protocol
Bidirectional protocol
Reference section
Chapter 2
Chapter 3
Chapter 4
Chapter 5
Chapter 6
Chapter 7
Chapter 8
Chapter 9
Chapter 10
Chapter 11
Chapter 12
Chapter 13
Chapter 14
Chapter 15
: Available : Not available
1 - 5 1 - 5
1 OVERVIEW
MELSEC-Q
1.2 Functions Added/Changed by Function Version B
Function
Of the special functions for the Q series C24 described in this manual, functions added/changed in the Q series C24 of the function version B and communication functions that can use those functions are listed below.
See Section 2.7 for the function version, serial NO. and software version of products
(CPU module, GX Developer, GX Configurator-SC) related to the Q Series C24 which can use added/changed functions.
See Appendix 1.1 concerning a comparison of functions in the different Q Series 24 function versions.
Description of function MC
Non procedure
Bidirectional
Explanation chapter
Transmission of PLC CPU monitoring information through combined use of the modem function
In the PLC CPU monitoring function, PLC CPU monitoring information is transmitted to the external device via a modem.
Remote password check
When accessing the QCPU from a remote location for the following data communication using the Q series C24 modem function, data communication is enabled after the unlock processing to a remote password set in the QCPU is completed normally from the external device.
• Communication using MC protocol
• Communication using the GX Developer
Initializes the modem automatically when Q Series C24 starts up.
Automatic initialization for modem
Callback
Addition of non reception monitoring time format in non procedure protocol
Transmission control start/end free area designation
Adding changeable user frame data
Adding the receive function using user frames
Multiple designations of send transparent codes
Switching to the GX Developer connection mode by switching the mode
Communication data monitoring function
After line connection from the GX Developer, access to the QCPU from the
GX Developer is made possible through line reconnection from the Q Series
C24 (callback). Transmission costs after line connection from the Q Series
C24 side are borne by the Q Series C24 side.
This function allows messages to be received in the non reception protocol by time-out in non reception monitoring time (timer 0) if the received complete code and received data count have been not determined.
This function allows the designation of the available capacity of the OS area that notifies the data reception failure at the time of transmission control
(DTR/DSR signal control and DC code control).
The following codes can be registered as changeable data for user frames for data communication:
• Horizontal parity code
• Sum check code of two’s-complement number
When specifying the first frame and executing data reception, a message comprised of the first frame and arbitrary data can be received.
For each combination of receiving user frame that the user has set, any data length can be specified for the arbitrary data.
(Setting the data length for the arbitrary data to "0" makes it possible to receive 1 byte only such as ACK/NAK).
When executing data transmission using the following protocol, it is possible to designate a maximum of 10 types of sending transparent codes for each interface.
• Non procedure protocol
• Bidirectional protocol
This functions allows the GX Developer connection mode to be switched by an external device or the PLC CPU.
This function allows the monitoring of communication data transmitted on the communication network of the Q series C24 and an external device.
Chapter 2
Chapter 3
Chapter 6
Chapter 7
Chapter 9
Chapter
11
Chapter
12
Chapter
15
Chapter
16
: Can be used : Cannot be used
1 - 6 1 - 6
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
2 USING THE PLC CPU MONITORING FUNCTION
This chapter explains the PLC CPU monitoring function with which the Q series C24 monitors the PLC CPU based on the monitoring information reregistered by the user.
2
2.1 Overview
Data transmission
Notification
The following explains an overview of the PLC CPU monitoring function:
(1) Transmission without using a sequence program
1) The PLC CPU monitoring function enables the Q series C24 to monitor the local station's PLC CPU at time intervals set by the user by reregistering data to be used for the PLC CPU monitoring function.
Data transmission and notification to the external device is possible by communication using the MC or non procedure protocol without using a sequence program.
2) The following monitoring information selected by the user can be sent or notified to the external device as the PLC CPU monitoring results.
Monitoring result
Without the modem function
Combined use of the modem function (modem communication)
Local station PLC CPU device (information on the device to be monitored)
Numeric value stored in a word device
ON/OFF status for a bit device
Status of the local station PLC CPU module
Notification message registered in data for connection
(character string data)
3) Two separate timings--constant-cycle transmission and condition-agreement transmission--are used to transmit and notify the PLC CPU monitoring results to the external device.
• In the constant cycle transmission, transmission and notification are performed each time the PLC CPU is monitored.
• In the condition agreement transmission, transmission and notification are performed when the information read from the PLC CPU satisfies the userdefined conditions and an error is detected in the PLC CPU.
(2) Simplifying the device monitoring procedure
When device monitoring is performed by communication using the MC protocol, the external device must repeatedly perform monitor request transmission and monitor data reception processing after it executes monitor registration.
By designating the constant cycle transmission for the PLC CPU monitoring function, the device data can be monitored without performing the monitor request reception processing.
2 - 1 2 - 1
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
MELSEC
PULL
MITSUBISHI
(3) Notification of an error in the PLC CPU
In the condition agreement transmission and notification, error information can be sent to the external device without a sequence program whenever a PLC CPU error occurs.
POWER
Q25HCPU
MODE
RUN
ERR.
USER
BAT.
BOOT
QJ71C24
CH1.
CH1.
CH2.
External device
RS-232
CPU error information
Monitoring device information
USB
RS-232
CH.2
SDA
SG
SDB
(FG)
RDA
(FG)
RDB
RS-422
/485
2
4
6
1
3
5
7
Abnormal detection
Error occurrence
2
2 - 2 2 - 2
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
2.2 About the PLC CPU Monitoring Function
This section explains the PLC CPU monitoring function.
2.2.1 Data registration for using the PLC CPU monitoring function
The following explains the data registration by the user to use the PLC CPU monitoring function.
(1) PLC CPU monitor registration for the Q series C24 that is required to use the PLC
CPU monitoring function is described in the following sections. The registration can be performed using one of the following methods:
1) Registration using the Q series C24 dedicated utility package (GX
Configurator-SC)
(Detailed explanation is found in Chapter 8 of the User's Manual (Basic))
2) Registration using the PLC CPU monitoring registration command (0630) for communication with the MC protocol
(Detailed explanation is found in Section 3.17 of the Reference Manual)
3) Registration using the PLC CPU "CSET" instruction
(Detailed explanation found in Chapter 17 of the User's Manual (Application))
(2) When this function is used with the modem function and data is transmitted or a notification message is notified as a PLC CPU monitoring result, register the connection data for the modem function on the "PLC CPU monitoring system setting" screen of the GX Configurator-SC.
(3) By registering the data for using the above PLC CPU monitoring function, the Q series C24 begins monitoring the PLC CPU.
2.2.2 PLC CPU monitoring information
This section explains the monitoring target information used to execute the PLC CPU monitoring function.
(1) The following information can be registered as the target of the PLC CPU monitoring function.
1) Device monitoring for the local station's PLC CPU
• Monitoring of the numeric values stored in the word device
• Monitoring of the bit device ON/OFF status
2) Monitoring of the local station's PLC CPU status
(2) In monitoring word and bit devices, a maximum total device point value of 960
(equivalent to a maximum of 15360 bits for only bit devices), or a total of 10 blocks when any continuous device range comprises one block, can be registered.
Since monitoring of the local station's PLC CPU status will also be registered as a one-block portion, up to 11 blocks can be registered.
11 ≥ (Number of word device blocks registered + number of bit device blocks registered)
+ CPU status monitoring (1 block)
960 points ≥ (Total number of all word device block points + total number of all bit device block points)
(1 point = 1 word) (1 point = 16 bits)
(3) With device monitoring of the blocks for which the word and bit devices are registered, the head device of each block becomes the monitoring target.
2 - 3 2 - 3
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
Classification
Internal system
Internal user
Register
Special relay
Special register
Input
Output
Internal relay
Latch relay
Annunciator
Edge relay
Link relay
Data register
Link register
Timer
Contact
Coil
Current value
Retentive timer
Contact
Coil
Current value
Contact
Counter
Link special relay
Link special register
Coil
Current value
Step relay
Direct input
Direct output
Index register
File register
(Example1) For a block in which 10 points of word devices from D100 to D109 are registered
Monitoring target: Numeric value stored in D100
Data transmitted: Numeric values stored in D100 to D109
(Example2) For a block in which two points of bit devices from M100 to M131 are registered
Monitoring target: ON/OFF status of M100
Data transmitted: ON/OFF status of M100 to M131
(4) The word and bit devices that can be designated as the monitoring targets and the device codes that are used to register the monitoring devices are shown in the table below.
Register the devices using the existing device ranges.
Device
Device type
Bit Word
CC
CN
SB
SW
SS
SC
SN
CS
W
TS
TC
TN
B
D
F
V
S
DX
DY
Z
R
ZR
ASCII
Device code
Binary
M
L
X
Y
SM
SD
91
H
A9
H
9C
H
9D
H
90
H
92
H
98
H
A2
H
A3
H
CC
H
AF
H
B0
H
C3
H
C5
H
A1
H
B5
H
C7
H
C6
H
C8
H
C4
H
B4
H
C1
H
C0
H
C2
H
93
H
94
H
A0
H
A8
H
Device range
(Default)
0 to 2047
0 to 1FFF
H
0 to 8191
0 to 2047
0 to 1FFF
H
0 to 12287
0 to 1FFF
H
0 to 2047
0 to 1023
0 to 7FF
H
0 to 8191
0 to 1FFF
H
0 to 15
0 to 32767
0 to FE7FF
H
POINT
(1) Designating a non-existent device code will result in an error.
(2) When the device range in the parameter setting has been changed, the new device range can be set as the PLC CPU's monitoring target.
2 - 4 2 - 4
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
2.2.3 Timing for PLC CPU monitoring
The following explains the timing for PLC CPU monitoring when the PLC CPU monitoring function is executed.
(1) PLC CPU monitoring using the Q series C24 is performed continuously at cycle time intervals registered by the user.
(2) Values from 1 to 65535 (unit: 100ms/s/min) can be registered as the cycle time.
Use the following expressions as a reference when registering the cycle time.
(a) When sending device data or the PLC CPU status
Cycle time designation > K + sequence scan time + processing time
+ data transmission time
(b) When notifying through combined use of the modem function
(when notifying)
Cycle time designation > K + sequence scan time + processing time
+ data transmission time
+ data transmission delay time of the modem
+ modem connection and disconnection time
(when sending data)
Cycle time designation > K + sequence scan time + processing time
+ data transmission time
+ data transmission delay time of the modem
+ modem connection and disconnection time
+ circuit disconnection wait time
When modem initialization has not been performed, the modem initialization time will be added. (We recommend that the modem initialization be performed in advance.)
The items that appear in the above expressions are explained below:
• K : 60 ms constant (internal processing time of the Q series C24)
• Processing time: Processing time for the "Multiple block batch read word unit command 0406"
For 1 point : 11.3 ms
For 480 points: 23.4 ms
For 960 points: 36.2 ms
• Data transmission time = 1 / transmission rate × bit count for one byte portion during transmission
× byte count for transmission data
• Bit count for one byte portion during transmission =
1 + data bit count + parity bit + stop bit count
(parity bit = 1, no parity bit = 0)
• Data transmission delay time by the modem: Depends on the modem specifications, line specifications and line status.
• Modem connection and disconnection time: Depends on the modem specifications, line specifications and line status.
• Modem initialization time: Depends on the modem specifications.
2 - 5 2 - 5
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
(3) To monitor the PLC CPU, the Q series C24 reads monitoring information (device information, PLC CPU status information) from the PLC CPU at time intervals set by the user.
POINT
(1) Since the Q series C24 reads the monitoring information (device data, PLC
CPU status) at the time of the next PLC CPU END process after the cycle time elapses, make the cycle time as long as possible.
(2) The following should be considered if the cycle time is short.
• The scan time of the PLC CPU is longer and the number of scan cycles has increased.
• The increase in the processing time of the Q Series C24 PLC CPU monitoring function has increased causing an increase in the processing time of other data communication functions.
• The load on the external device has increased.
2.2.4 Timings of transmission and notification of monitoring results to the external device
Constant cycle transmission
The following explains the timings for the transmission and notification of the PLC CPU monitoring results.
There are two transmission methods for transmitting and notifying the monitoring results of the local station PLC CPU to the external device. These include constant cycle transmission and condition agreement transmission. One of these methods must be selected by the user during PLC CPU monitoring registration.
(1) Constant cycle transmission
The monitoring results are transmitted and notified each time monitoring information is read from the PLC CPU.
(Timing to transmit data)
Monitoring information
One-block portion
• • •
One-block portion
Cycle time
External device
Sequence program
END
END END END
2 - 6 2 - 6
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
Condition agreement transmission
Cycle time
(2) Condition agreement transmission
(a) For device monitoring, the monitoring conditions registered by the user
(conditions for sending monitoring results), the monitoring condition values and the monitoring information read from the PLC CPU are compared. The monitoring results are sent or notified when there is a block where the monitoring conditions match.
For PLC CPU status monitoring, the monitoring results are sent or notified only once when an error is detected for the first time from the status information read from the PLC CPU. (This corresponds to the edge triggered transmission noted below).
(b) Two transmission methods of the monitoring results are available for the condition agreement transmission for device monitoring. These include edge triggered transmission and level triggered transmission.
1) Edge triggered transmission
The monitoring conditions registered by the user (conditions for sending monitoring results), the monitoring condition values and the monitoring information read from the PLC CPU are compared. The monitoring results are sent or notified only once when an agreement of the monitoring conditions is detected for the first time. After that, when the monitoring information read from the PLC CPU does not match the monitoring conditions and then it matches the monitoring conditions once again, the monitoring results are sent or notified.
2) Level triggered transmission
The monitoring conditions registered by the user (conditions for sending monitoring results), the monitoring condition values and the monitoring information read from the PLC CPU are compared. While the monitoring conditions agree, the monitoring results are sent or notified at each cycle time.
(Timing to transmit data)
Monitoring information
One-block
portion
• • •
One-block portion
External device
Sequence program
(conditions matched/not matched)
Matched
END
Not matched
END
Matched
END
2 - 7 2 - 7
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
(c) In the condition agreement transmission for device monitoring, the head device for each block is the monitoring target for condition monitoring of each block device.
For the condition agreement transmission, the monitoring conditions that can be designated for the device to be registered by the user and the registration values when designating the monitoring condition are shown in the table below.
Register the monitoring conditions for the head device of each block using the following table.
Monitoring condition (item to be judged)
Registration value
Valid designated device
Device value or status = device monitoring condition value or status
Device value or status
Unsigned
Signed
≠
device monitoring condition value or status
Monitoring device < monitoring condition value
Monitoring device < monitoring condition value
Monitoring device > monitoring condition value
Monitoring device > monitoring condition value
Monitoring device < monitoring condition value
Monitoring device < monitoring condition value
Monitoring device > monitoring condition value
Monitoring device > monitoring condition value
For edge triggered transmissions
0001
H
0002
H
0003
H
0004
H
0005
H
0006
H
0007
H
0008
H
0009
H
000A
H
For level triggered transmissions
0101
H
0102
H
0103
H
0104
H
0105
H
0106
H
0107
H
0108
H
0109
H
010A
H
Bit Word
(d) In device monitoring, register the monitoring condition value or status when the Q series C24 judges that the numeric value/status of the monitoring device for condition agreement transmission (head device of each block) agrees with the condition using the registration values shown below.
Type of monitoring device
Bit device
Word device
Monitoring condition value or status
OFF
ON
Numerical value
Registration value
0000
H
0001
H
0000
H to FFFF
H
(Example 1) When M0 = ON is the condition agreement
Monitoring condition registration value : 0001
H
Registration value for the monitoring condition value or status: 0001
H
(Example 2) When D0 > 100 (signed) is the condition agreement
Monitoring condition registration value : 000A
H
Registration value for the monitoring condition value or status: 100(64
H
)
REMARK
In status monitoring for the PLC CPU, the monitoring conditions and condition values for condition agreement transmission are not registered. Instead, it is registered as whether or not PLC CPU status monitoring will be performed.
Monitoring results in condition agreement transmission are sent or notified only once when an error is detected by the status information read from the PLC CPU for the first time.
2 - 8 2 - 8
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
2.2.5 Transmission methods of monitoring results and transmission data to the external device
The following explain the method of transmitting the PLC CPU monitoring results and data to the external device.
(1) Data transmission to the external device while performing communication using the MC protocol
(a) The same format as for the messages sent with the on-demand function is used to transmit data, except that the on-demand data section is replaced with the device information and PLC CPU status information. The data is sent as explained in (c) and (d) below.
(Detailed explanation is found in Section 3.17 of the Reference Manual)
When the interface that is to use the modem function is set in the MC protocol, connection processing and disconnection processing to the modem are performed when the PLC CPU monitoring results are transmitted.
(Example) Data transmission by MC protocol with modem function (condition agreement transmission)
Dial
Registration information for PLC CPU monitoring
Disconnection
Cycle time
External device
Sequence program
(conditions matched/ not match)
END
Matched
END
Not matched
END
Matched
(b) When the transmission of on-demand data using user frames is designated, the same format as for sending on-demand data using user frames is used to transmit data, except that the on-demand data section is replaced with the device information and PLC CPU status information. The data is sent as explained in (c) and (d) below.
See the following explanatory items for data reception by the external device side.
• Device information, PLC CPU status information arrangement: Section
3.17 of the Reference Manual
• Arrangement of data in the user frame section to be sent: Chapter 10
(c) When sending the monitoring results as data during constant cycle transmission, the entire block portion of the monitoring target device information and PLC CPU status information is transmitted in batch mode.
2 - 9 2 - 9
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
(d) When sending the monitoring results as data during condition agreement transmission, head data (header) and end data (footer) for the on-demand function are added to the device information for a block with matched monitoring conditions and the PLC CPU status information upon the occurrence of an error. The header and footer are added to each clock, and then the monitoring result data is transmitted.
Transmission is performed in the following order: the PLC CPU status information, then the device information registered in the word block, and then the device information registered in the bit block.
POINT
When there is communication using the MC protocol form 1) to 4), all of the device monitoring head device number will be converted to hexadecimal ASCII data and sent. (The same conversion is performed during either constant cycle transmission or condition agreement transmission.)
(2) Data transmission to the external device while performing communication using the non procedure protocol
(a) The device information and CPU information are sent by the word/byte unit designations.
When the communication data ASCII-BIN conversion is designated, it is converted to ASCII code data and sent. (Examples are shown in (f)).
1) When the word/byte unit designation is word unit, the device information a and CPU information are each sent in one-word segments in a (H) (L) sequence.
2) When the word/byte unit designation is byte, the device information and
CPU information are each sent in one-word segments in a (L) (H) sequence.
When the interface that is to use the modem function is set in the non procedure protocol, connection processing and disconnection processing to the modem are performed when the PLC CPU monitoring results are transmitted.
(Example) Data transmission by non procedure protocol with modem function
(condition agreement transmission)
Monitoring information
Dial 1 block
•••
1 block
Disconnection
Cycle time
External device
Sequence program
(conditions matched/ not matched)
END
Matched
END
Not matched
END
Matched
(b) When sending monitoring results as data during constant cycle transmission, the device information of two or more user frame No. and PLC CPU status information that have been currently designated for the constant cycle transmission by the Q series C24.
2 - 10 2 - 10
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
Frame number
B001
H
B002
H
B003
H
B004
H
B005
H
B006
H
B007
H
B008
H
B009
H
B00A
H
B061
H
B080
H
B081
H
B082
H
(c) When sending the monitoring results as data during condition agreement transmission, the device information of two or more user frame No. and PLC
CPU status information that have been currently designated by the Q series
C24 for the condition agreement transmission of the block where the monitoring conditions match are transmitted in batch mode.
When the monitoring conditions of two or more block match, the device information and PLC CPU status information are transmitted for each block.
POINT
When there is an ASCII-BIN conversion of communication data using non procedure protocol, all of the device monitoring head device number will be converted to hexadecimal ASCII data and sent. (The same conversion is performed during either constant cycle transmission or condition agreement transmission.)
(d) The user frame numbers that can be designated for data transmission of
PLC CPU monitoring results are listed below.
• 1
H
to 3E7
H
(Default registration frame numbers)
• 3E8
H
to 4AF
H
(Frame numbers registered by the user in the flash ROM)
• 8001
H
to 801F
H
(Frame numbers registered by the user in the buffer memory)
• B001
H
to B01F
H
(Dedicated frame numbers for this function listed in (e) below)
For details on how to designate user frame numbers, see Transmission using user frames in Chapter 11.
(e) For instructing to transmit the device information and PLC CPU status information when sending monitoring results as data, use the following dedicated user frame numbers.
Information to be transmitted
Valid function
Constant cycle transmission
Condition agreement transmission
Device information for the block registered in number n
Number 1
Number 2
Number 3
Number 4
Number 5
Number 6
Number 7
Number 8
Number 9
Number 10
PLC CPU status information
(CPU abnormal monitoring data)
Number of blocks sent
Monitoring result information for all blocks
Monitoring result information for blocks satisfying the conditions
2 - 11 2 - 11
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
(f) Device information and PLC CPU status information are sent using the data arrangement shown below.
The ASCII-BIN conversion designation is designated in buffer memory address 121
H
/1C1
H
. Note that when the user frame has been designated by setting to on the value for bit 14, which indicates the user frame No., there will be ASCII-BIN conversion of corresponding send data. It will be sent as binary data. (See Section 13.3 )
1) When user frame numbers B001
H
to B00A
H
are designated (example of a one-block portion)
• When word device data (W100 to W103, (4 points)) is sent
When the word/byte unit designation is word unit, the device data will be sent in a (H) (L) sequence.
The number of registered points is the number of points in word units.
(When ASCII-BIN conversion is not performed)
The total number of bytes for the device data section is the number of device points 2.
When the word/byte unit designation is byte When the word/byte unit designation is word
L H
(W)
L H L H L H L H L H L H
(W)
L H H L H L H L H L
00
H
01
H
00
H
B4
H
04
H
00
H
00
H
00
H
01
H
00
H
02
H
00
H
03
H
00
H
00
H
01
H
00
H
B4
H
04
H
00
H
00
H
00
H
00
H
01
H
00
H
02
H
00
H
03
H
W100 W101 W102 W103 W100 W101 W102 W103
(When ASCII-BIN conversion is performed)
The total number of bytes for the device data section is the number of device points 4.
When the word/byte unit designation is byte
H
W
L H
0 0 0 1 0
L
0
L
0
0
0
H
4
L
0 0 0
H
0
L
0 1 0
H
0
L
0 2 0
H
0
L
0 3 0
H
0
57
H
2A
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
30
H
30
H
34
H
30
H
30
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
32
H
30
H
30
H
30
H
33
H
30
H
30
H
W100 W101 W102 W103
When the word/byte unit designations word
H
W
L H
0 0 0 1 0
L
0
H
0 0 0
L
4
H
0 0 0
L
0
H
0
0 0
L
1
H
0
0 0
L
2
H
0 0 0
L
3
57
H
2A
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
30
H
30
H
34
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
32
H
30
H
30
H
30
H
33
H
W100 W101 W102 W103
2 - 12 2 - 12
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
• When data for bit device (M16 to M175, (10 point)) is sent
When the word/device unit designation is word unit, the device data will be sent in a (H) (L) sequence.
The number of registered points is the number of points in word units.
(When ASCII-BIN conversion is not performed)
The total number of bytes for the device data section is the number of device points 2.
When the word/byte unit designation is byte When the word/byte unit designation is word
L H
(M)
L H L H L H
L H
(M)
L H H L H L
10
H
00
H
00
H
90
H
0A
H
00
H
30
H
11
H
12
H
34
H
10
H
00
H
00
H
90
H
0A
H
00
H
11
H
30
H
34
H
12
H
3 0 1 1
0
M
2
3
0 1
M
2
2
M
2
1
1
M
2
0
0 0
M
1
9
M
1
8
0
M
1
7
0
M
1
6
0
M
3
1
M
3
0
0 0
M
2
9
1
M
2
8
0 0 0
M
2
7
M
2
6
M
2
5
1
M
2
4
1 1 3 0
0
M
3
1
0 0
M
3
0
M
2
9
1
M
2
8
0 0
M
2
7
M
2
6
0
M
2
5
1
M
2
4
0
M
2
3
M
2
2
0 1
M
2
1
1
M
2
0
0 0 0
M
1
9
M
1
8
M
1
7
0
M
1
6
(When ASCII-BIN conversion is performed)
The total number of bytes for the device data section is the number of device points 4.
When the word/byte unit designation is byte
H
M
L H
0 0 0 0 1
L
0
H
0 0
0
L
A
L
3 0
1
H
1
L
1 2
3
H
4
4D
H
2A
H
30
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
30
H
41
H
33
H
30
H
31
H
31
H
3 0
1
1
0
M
2
3
0
M
2
2
1
M
2
1
1
M
2
0
0 0
M
1
9
M
1
8
0
M
1
7
0
M
1
6
0
M
3
1
0
M
3
0
0
M
2
9
1
M
2
8
0 0 0
M
2
7
M
2
6
M
2
5
1
M
2
4
When the word/byte unit designation is word
31
H
32
H
33
H
34
H
H
M
L H
0 0 0 0 1
L
0
H
0 0 0
L
A
H
1 1 3
L
0
H
3 4 1
L
2
4D
H
2A
H
30
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
30
H
41
H
31
H
31
H
33
H
30
H
1 1
3
0
0
M
3
1
0
M
3
0
0
M
2
9
1
M
2
8
0 0
M
2
7
M
2
6
0
M
2
5
1
M
2
4
0
M
2
3
0
M
2
2
1
M
2
1
1
M
2
0
0 0 0
M
1
9
M
1
8
M
1
7
0
M
1
6
33
H
34
H
31
H
32
H
2 - 13 2 - 13
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
2) When user frame No. B061
H
is designated
PLC CPU status information (for one block) is sent as the following data: when communicating with
ASCII code when communicating with binary code
Remark
Device code
Number of registered points
Monitoring head device
During normal operation
Device data
Module warning occurring
Module error/module system error occurring
"01"
"0001"
"000000"
"0000"
"0001"
"0002"
01
H
0001
H
000000
H
0000
H
0001
H
0002
H
All fixed value
(When ASCII-BIN conversion is not performed)
The total number of bytes for the device data section is the number of device points 2.
When the word/byte unit designation is byte When the word/byte unit designation is word
L H L H
L H
L H L H
H L
01
H
00
H
00
H
00
H
01
H
00
H
01
H
00
H
01
H
00
H
00
H
00
H
01
H
00
H
00
H
01
H
(When ASCII-BIN conversion is performed)
The total number of bytes for the device data section is the number of device points 4.
When the word/byte unit designation is byte When the word/byte unit designation is word
H
0 1
L H
0 0 0 0 0
L
0
H
0 0 0
L
1
H
0 1 0
L
0
H
0
L
1
H
0 0 0 0 0
L
0
H
0 0 0
L
1
H
0 0 0
L
1
30
H
31
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
31
H
30
H
31
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
31
H
3) When user frame No. B080
H
is designated
The transmission block count will be sent as follows:
(Example)
Number of registered word blocks: 2 (D0 to D3 (4 points), W100 to W107 (8 points))
Number of registered bit blocks : 1 (M0 to M31 (2 points))
(When ASCII-BIN conversion is not performed) (When ASCII-BIN conversion is performed)
02
H
01
H
00
H
H
0
L
2
H
0
L
1
H
0
L
0
30
H
32
H
30
H
31
H
30
H
30
H
2 - 14 2 - 14
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
4) When user frame No. B081
H
is designated
Information on monitoring results for all blocks are sent as follows:
Results are sent in the following order: the device information registered in the word block, the device information registered in the bit block and then PLC
CPU status information.
(Example)
Number of registered word blocks: 1 (W100 to W103 (4 points))
Number of registered bit blocks : 1 (M0 to M15 (1 point))
Perform CPU status monitoring : 1 (1 point)
(When ASCII-BIN conversion is not performed)
The total number of bytes for the device data section is the number of device points 2.
When the word/byte unit designation is byte g head device g head device g head device
L H
(W)
L H L H L H L H L H
L H
(M)
L H L H
L H L H L H
00
H
01
H
00
H
B4
H
04
H
00
H
00
H
00
H
01
H
00
H
02
H
00
H
03
H
00
H
00
H
00
H
00
H
90
H
01
H
00
H
30
H
11
H
00
H
00
H
00
H
01
H
01
H
00
H
00
H
00
H
W100 W101 W102 W103
3 0 1 1
0
M
0
7
0 1
M
0
6
M
0
5
1
M
0
4
0 0
M
0
3
M
0
2
0
M
0
1
0
M
0
0
0
M
1
5
M
1
4
0 0
M
1
3
1
M
1
2
0 0 0
M
1
1
M
1
0
M
0
9
1
M
0
8
When the word/byte unit designation is word
L H
(W)
L H H L H L H L H L L H
(M)
L H H L L H L H H L
00
H
01
H
00
H
B4
H
04
H
00
H
00
H
00
H
00
H
01
H
00
H
02
H
00
H
03
H
00
H
00
H
00
H
90
H
01
H
00
H
11
H
30
H
00
H
00
H
00
H
01
H
01
H
00
H
00
H
00
H
W100 W101 W102 W103
1 1 3 0
0
M
1
5
0 0
M
1
4
M
1
3
1
M
1
2
0 0
M
1
1
M
1
0
0
M
0
9
0
M
0
8
0
M
0
7
M
0
6
0 1
M
0
5
1
M
0
4
0 0 0
M
0
3
M
0
2
M
0
1
0
M
0
0
2 - 15 2 - 15
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
(When ASCII-BIN conversion is performed)
The total number of bytes for the device data section is the number of device points 4.
When the word/byte unit designation is byte
H
W
L H
0 0 0 1 0
L
0
H
0 0 0
L
4
L
0 0 0
H
0
L
0 1 0
H
0
L
0 2 0
H
0
L
0 3 0
H
0
H
M
L H
0 0 0 0 0
L
0
H
0 0 0
L
1
L
3 0 1
H
1
57
H
2A
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
30
H
30
H
34
H
30
H
30
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
32
H
30
H
30
H
30
H
33
H
30
H
30
H
4D
H
2A
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
31
H
33
H
30
H
31
H
31
H
W100 W101 W102 W103
3 0 1 1
0
M
0
7
0
M
0
8
1
M
0
5
1
M
0
4
0 0
M
0
3
M
0
2
0
M
0
1
0
M
0
0
0
M
1
5
0
M
1
4
0
M
1
3
1
M
1
2
0 0 0
M
1
1
M
1
0
M
0
9
1
M
0
8
H
0
L
1
H
0 0 0 0 0
L
0
H
0 0 0
L
1
L
0 0 0
H
0
30
H
31
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
30
H
When the word/byte unit designation is word
H
W
L H
0 0 0 1 0
L
0
H
0 0 0
L
4
H
0 0 0
L
0
H
0 0 0
L
1
H
0 0 0
L
2
H
0 0 0
L
3
H
M
L H
0 0 0 0 0
L
0
H
0 0 0
L
1
H
1 1 3
L
0
57
H
2A
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
30
H
30
H
34
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
32
H
30
H
30
H
30
H
33
H
4D
H
2A
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
31
H
31
H
31
H
33
H
30
H
W100 W101 W102 W103
1 1 3 0
0
M
1
5
0
M
1
4
0
M
1
3
1
M
1
2
0 0
M
1
1
M
1
0
0
M
0
9
1
M
0
8
0
M
0
7
0
M
0
6
1
M
0
5
1
M
0
4
0 0 0
M
0
3
M
0
2
M
0
1
0
M
0
0
H
0
L
1
H
0 0 0 0 0
L
0
H
0 0 0
L
1
H
0 0 0
L
0
30
H
31
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
30
H
2 - 16 2 - 16
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
5) When user frame No. B082
H
is designated
Information on the monitoring results for the condition agreement blocks are sent for each block.
Results are sent in the following order: The PLC CPU status information, the device information registered in the word block and then the device information registered in the bit block.
(Example)
Number of registered word blocks: 2 (D0 to D3 (4 points), W100 to W103 (4 points))
Number of registered bit blocks : 1 (M0 to M15 (1 point))
When the condition satisfied monitoring device is W100 = 0 and M0
≠
ON
(When ASCII-BIN conversion is not performed)
The total number of bytes the device data section is the number of device points
2.
When the word/byte unit designation is byte
For W100 to W103 block data For M0 to M15 block data
L H
(W)
L H L H L H L H L H L H
(M)
L H L H
00
H
01
H
00
H
B4
H
04
H
00
H
00
H
00
H
01
H
00
H
02
H
00
H
03
H
00
H
W100 W101 W102 W103
00
H
00
H
00
H
90
H
01
H
00
H
30
H
11
H
3 0 1 1
0
M
0
7
0 1
M
0
6
M
0
5
1
M
0
4
0 0
M
0
3
M
0
2
0
M
0
1
0
M
0
0
0
M
1
5
M
1
4
0 0
M
1
3
1
M
1
2
0 0 0
M
1
1
M
1
0
M
0
9
1
M
0
8
When the word/byte unit designation is word
For W100 to W103 block data For M0 to M15 block data
L H
(W)
L H H L H L H L H L L H
(M)
L H H L
00
H
01
H
00
H
B4
H
04
H
00
H
00
H
00
H
00
H
01
H
00
H
02
H
00
H
03
H
W100 W101 W102 W103
00
H
00
H
00
H
90
H
01
H
00
H
11
H
30
H
1 1 3 0
0
M
1
5
0 0
M
1
4
M
1
3
1
M
1
2
0 0
M
1
1
M
1
0
0
M
0
9
1
M
0
8
0
M
0
7
M
0
6
0 1
M
0
5
1
M
0
4
0 0 0
M
0
3
M
0
2
M
0
1
0
M
0
0
2 - 17 2 - 17
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
(When ASCII-BIN conversion is performed)
The total number of bytes for the device data section is the number of device points 4.
When the word/byte unit designation is byte
For W100 to W103 block data For M0 to M15 block data
H
W
L H
0 0 0 1 0
L
0
H
0 0 0
L
4
L
0 0 0
H
0
L
0 1 0
H
0
L
0 2 0
H
0
L
0 3 0
H
0
H
M
L
0
H
0 0 0 0
L
0
H
0 0 0
L
1
L
3 0 1
H
1
57
H
2A
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
30
H
30
H
34
H
30
H
30
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
32
H
30
H
30
H
30
H
33
H
30
H
30
H
4D
H
2A
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
31
H
33
H
30
H
31
H
31
H
W100 W101 W102 W103
3 0 1 1
When the word/byte unit designation is word
For W100 to W103 block data For M0 to M15 block data
0
M
0
7
0
M
0
6
1
M
0
5
1
M
0
4
0 0
M
0
3
M
0
2
0
M
0
1
0
M
0
0
0
M
0
1
5
M
1
4
0
M
1
3
1
M
1
2
0 0 0
M
1
1
M
1
0
M
0
9
1
M
0
8
H
W
L H
0 0 0 1 0
L
0
H
0 0 0
L
4
H
0 0 0
L
0
H
0 0 0
L
1
H
0 0 0
L
2
H
0 0 0
L
3
H
M
L
0
H
0 0 0 0
L
0
H
0 0 0
L
1
H
1 1 3
L
0
57
H
2A
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
30
H
30
H
34
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
32
H
30
H
30
H
30
H
33
H
W100 W101 W102 W103
4D
H
2A
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
31
H
33
H
30
H
31
H
31
H
1 1 3 0
1
5
0
M
1
4
0
M
1
M
1
3
1
2
1
M
1
1
0 0
M M
1
0
0
M
0
9
0
M
0
8
0
M
0
0
7
M
0
6
0
5
0
M
0
4
1
M
0 0 0
M
0
3
M
0
2
M
0
1
0
0
1
M
2 - 18 2 - 18
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
(3) Notification to the interface side using the modem function
(a) The notification message (text string data) contained in the user registered data for connecting the modem function is conveyed using the modem function.
The device information and the CPU status information read from the
PLC CPU are not sent to the external device in the notification message.
Include the device information and the CPU status information by which the PLC CPU status can be checked in the preregistered notification message.
(b) The method for message notification is functionally the same as the notification using the modem function described in Chapter 3.
The difference is that notification is performed with Y14 OFF when using the modem, whereas for notification using PLC CPU monitoring, notification is performed for whenever the PLC CPU error is detected or the designated device status is matched with the monitoring conditions (see Section 2.2.4).
(c) During constant-cycle transmission, a notification message for one connection data registered for notifying constant-cycle transmission is sent.
(d) During condition agreement transmission, a notification message for connection data registered in the block where the monitoring conditions match is sent in block units.
When there are multiple blocks where the monitoring conditions match, notification is performed at the "Wait time of notification" interval (notification interval) set by the user for use with the modem function. The PLC CPU monitoring stops until notification has been performed to all blocks where the monitoring conditions match.
POINT
(1) When performing message notification using the PLC CPU monitoring function, set the corresponding interface side as the target of the modem function.
(2) When setting data for the PLC CPU monitoring function with GX Configurator-
SC, PLC CPU monitoring begins immediately when the Q series C24 starts up.
2 - 19 2 - 19
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
2.2.6 Execution sequence for using the PLC CPU monitoring function
The following explains the execution sequence for using the PLC CPU monitoring function.
(1) When transmitting the monitoring results through data transmission/notification messages using the modem function, perform the following settings in order to use the modem function.
Setting item Explanation section
Initial setting using the GX Configurator-SC Section 3.4.2
Registration of data No. for initialization and data No. for connection Sections 3.4.3 and 3.4.4
Initialization of the Q series C 24 modem/TA Section 3.4.5
(2) Register PLC CPU monitoring for the Q series C24 using one of the methods described in Section 2.2.1.
(3) By registering PLC CPU monitoring, the Q series C24 monitors the local station's
PLC CPU regardless of the RUN/STOP status and sends the monitoring information to the external device.
(4) When reregistering PLC CPU monitoring in order to change the registration data for the PLC CPU monitoring, reregister after canceling the PLC CPU monitoring.
1) When registering with communication using the MC protocol (detailed explanation found in Section 3.17 of Reference Manual)
2) When registering with the PLC CPU's "CSET" instruction (detailed explanation found in Chapter 17 of User's Manual (Application))
To cancel when using GX Configurator-SC, change the PLC CPU to the STOP status, redo the settings, and then restart the QCPU.
2 - 20 2 - 20
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
2.3 Settings for Using the PLC CPU Monitoring Function
This section describes system settings required for constant cycle transmission and condition agreement transmission.
2.3.1 System setting items for the PLC CPU monitoring function
The following explains system setting items for the PLC CPU monitoring function.
POINT
The PLC CPU monitoring function setting screens from the GX Configurator-SC are shown.
(1) For the PLC CPU monitoring system settings, perform the settings on the screens shown in Section 8.4.9 of the User's Manual (Basic).
(2) Register transmission user frames on the screens shown in Section 8.4.10 of the User's Manual (Basic) after checking the specifications and setting methods explained in Chapters 9 to 11 of this manual.
(3) Register the data for connecting the modem function on the screens shown in
Section 8.4.3 of the User's Manual (Basic) after checking the specifications described in Section 3.4.4 of this manual.
(1) Setting items and requirement when performing communication using the MC protocol
Setting item
Cycle time units
Cycle time
PLC CPU monitoring function
PLC CPU monitoring transmission measure
Constant cycle transmission Transmission pointer
Output count
Data No. for connection
Number of registered word blocks
Number of registered bit blocks
PLC CPU abnormal monitoring
No. n block monitoring device Monitoring device
Head device No.
Read point
Condition agreement transmission
Monitoring condition
Monitoring condition value
Transmission pointer
Output count
Data No. for connection
PLC CPU abnormal monitoring designation
Condition agreement transmission Transmission pointer
Output count
Data No. for connection
Constant cycle transmission
Data transmission
Notification
(1
H
: Constant cycle)
(Data) (Notification)
Condition agreement transmission
Data transmission
Notification
Reference section
(3) (a) of this section
(3) (b) of this section
(2
H
: Condition agreement) (3) (c) of this section
(Data) (Notification) (3) (d) of this section
(4) of this section
Section 11.4.2 (2)
Section 2.2.5 (3)
Section 3.4.4
(3) (e) of this section
(3) (f) of this section
(3) (g) of this section
(3) (h) of this section
(3) (i) of this section
(4) of this section
Section 11.4.2 (2)
Section 2.2.5 (3)
Section 3.4.4
(4) of this section
Section 11.4.2 (2)
Section 2.2.5 (3)
Section 3.4.4
: Setting required : Setting not required
POINT
While using the notification function, the device information and the CPU status information cannot be transmitted.
2 - 21 2 - 21
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
(2) Setting items and requirement when performing communication using the non procedure protocol
Setting item
Cycle time units
Cycle time
PLC CPU monitoring function
PLC CPU monitoring transmission measure
Constant cycle transmission Transmission pointer
Output count
Data No. for connection
Number of registered word blocks
Number of registered bit blocks
PLC CPU abnormal monitoring
No. n block monitoring device Monitoring device
Head device No.
Read point
Condition agreement transmission
Monitoring condition
Monitoring condition value
Transmission pointer
Output count
Data No. for connection
PLC CPU abnormal monitoring designation
Condition agreement transmission Transmission pointer
Output count
Data No. for connection
Constant cycle transmission
Data transmission
Notification
(1
H
: Constant cycle)
(Data) (Notification)
Condition agreement transmission
Data transmission
Notification
Reference section
(3) (a) of this section
(3) (b) of this section
(2
H
: Condition agreement) (3) (c) of this section
(Data) (Notification) (3) (d) of this section
(4) of this section
Section 11.4.2 (2)
Section 2.2.5 (3)
Section 3.4.4
(3) (e) of this section
(3) (f) of this section
(3) (g) of this section
(3) (h) of this section
(3) (i) of this section
(4) of this section
Section 11.4.2 (2)
Section 2.2.5 (3)
Section 3.4.4
(4) of this section
Section 11.4.2 (2)
Section 2.2.5 (3)
Section 3.4.4
: Setting required : Setting not required
POINT
While using the notification function, the device information and the CPU status information cannot be transmitted.
2 - 22 2 - 22
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
(3) Contents of setting items
The data items to be set by the GX Configurator-SC in order to use the PLC CPU monitoring function and the setting contents are explained below.
(a) Cycle time units
• Designates the unit for "(b) cycle time" below for reading information from the PLC CPU using the PLC CPU monitoring function.
• The cycle time units and the cycle time designated using this unit can also be used as the transmission time interval for constant cycle communication.
(b) Cycle time
Designates the time for one cycle when reading information from the PLC
CPU in order to perform PLC CPU monitoring.
(c) PLC CPU monitoring function
Designates the timing (constant cycle transmission or condition agreement transmission) when sending/notifying information on the PLC CPU monitoring results (device information/CPU status information) to the external device.
• The time interval designated in data items (a) and (b) above for reading information from the PLC CPU can also be used as the transmission time interval for constant cycle communication.
• The conditions for condition agreement transmission are designated using data items (h) and (i) below.
(d) PLC CPU monitoring transmission measure
Designates the means by which the PLC CPU monitoring results are conveyed to the external device.
• Data transmission
The device information and the PLC CPU status information are sent as the monitoring results.
• Notification
Notification message is sent as the monitoring results.
(e) Number of registered word blocks, number of registered bit blocks
Designates the number of word device blocks (number of registered word blocks) and the number of bit device blocks (number of registered bit blocks) registered in the Q series C24 as the target when performing device data monitoring or transmission.
(f) CPU abnormal monitoring
Designates whether or not the Q series C24 monitors abnormality of the local station PLC CPU (status monitoring) in the PLC CPU monitoring.
2 - 23 2 - 23
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
(g) Monitoring device, head device No., read point (Number of registered points)
When performing device data monitoring or transmission, designate the device range for each block for the number of blocks designated by setting item (e), number of registered word blocks and number of registered bit blocks.
The target of device data monitoring for condition agreement transmission is the head device for each block.
Word device designated block: Head word device (for one word)
Bit device designated block : Head bit device (for one bit)
1) The monitored device is the item that indicates the target device of the corresponding block and designated with the codes listed in Section
2.2.2 (4).
2) The head device is the data that designates the head of the target device range for the corresponding block.
3) The read point is the item that indicates the target device range for the corresponding block which designate points from the head device No..
The bit device designates points in word units (1 point = 16 bits)
4) The methods for designating these data are the same as the designation methods when reading from or writing to the device memory described in Section 3.3 of the Reference Manual. Designate according to the explanations of items 2) through 4) in Section 3.3.1 (2) (c) of the
Reference Manual.
REMARK
When the user performs the PLC CPU monitoring registration, the device will designate either a decimal or hexadecimal device No.. The read points (registration points) are designated as hexadecimal. However, if this is done by either MC protocol communication (form 1) to 4)) or non procedure protocol communication, when ASCII-BIN conversion of the communication data has been designated, the head device No. for all devices to be sent to external devices as the monitoring results will be converted to hexadecimal ASCII data and sent.
(h) Monitoring condition
When condition agreement transmission is designated with the PLC CPU monitoring function (c), designate the conditions for transmitting information for the monitoring condition value (i).
(i) Monitoring condition value
When condition agreement transmission is designated with the PLC CPU monitoring function (c), this item designates the status/numeric value of the monitoring condition (h).
• When the monitoring device is a word device: Designate the monitoring condition value with a numeric value
• When the monitoring device is a bit device : Designate the monitoring condition with a numeric value (1/0) corresponding to
ON/OFF.
2 - 24 2 - 24
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
(4) The following is an example of setting items and data transmission when sending the monitoring results of the PLC CPU monitoring function execution to the external device using the non procedure protocol.
(Example)
This example shows a case in which the D0 to D3 device information and user frame data are sent by the edge trigger method using a condition of D0 = 0.
Perform the settings on the "PLC CPU monitoring system setting" screen and the "Transmission user frame No. designation monitor" screen described in
Sections 8.4.9 and 8.4.10 of the User's Manual (Basic).
1) PLC CPU monitoring system setting
Setting item
Cycle time units
Cycle time
PLC CPU monitoring function
PLC CPU monitoring transmission measure
Number of registered word blocks
Number of registered bit blocks
PLC CPU abnormal monitoring
No. 1 block monitoring device Monitoring device
Head device No.
Read point
Condition agreement transmission
Monitoring condition
Monitoring condition value
Transmission pointer
Output count
Set data min
3
Condition agreement
Data transmission
0
D
1
0
0
4
Remarks
Settings other than those listed at left are not required
Edge =
0
49
3
2) Setting the transmission user frames
Output frame No. designation 46th
Output frame No. designation 47th
Output frame No. designation 48th
Output frame No. designation 49th
Output frame No. designation 50th
Output frame No. designation 51st
Output frame No. designation 52nd
Output frame No. designation 53rd
Output frame No. designation 54th
Output frame No. designation 55th
Output frame No. designation 56th
Output frame No. designation 57th
User frame number
User frame number
User frame number
User frame number (02
H
)
User frame number (B001
H
)
User frame number (03
H
)
User frame number
User frame number
User frame number
User frame number
User frame number
User frame number
Set the user frame data (STX)
Set the first block (from D0 to D3)
Set the user frame data (ETX)
Data sent when the condition D = 0 is satisfied
E
T
X
Device data
(D3)
Device data
(D2)
Device data
(D1)
Device data
(D0)
E
T
X
External device
2 - 25 2 - 25
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
2.3.2 How to register and cancel the PLC CPU monitoring function
The following describes the method for registering and canceling the PLC CPU monitoring function from the PLC CPU.
POINT
(1) For details on the method for registering and canceling the PLC CPU monitoring function with the GX Configurator-SC, see Section 8.4.9 of the
User's Manual (Basic).
(2) For details on the method for registering and canceling the PLC CPU monitoring function with an MC protocol command, see Section 3.17 of the
Reference Manual.
(When registering or canceling from the PLC CPU)
For details on the CSET command, see Section 17.3.
Registering PLC
CPU monitoring
M0 M1
M1
Create control code data from D0
ZP.CSET
"Un" K1 D0 D200 M0
Processing for normal completion
Processing for abnormal completion
Sequence program
CSET instruction
Completion device
Completion device +1
PLC CPU
Scan
END processing
Instruction execution
Scan
END
processing
Scan
At abnormal completion
END
processing
Setting processing
1) Stores the data for PLC CPU monitoring registration in the device that designates the control data for the CSET instruction.
2) Executes the CSET instruction.
At the end of the scan in which the CSET instruction was completed, the completion device (M0) designated by (D2) turns ON and then turns OFF at the next END processing.
3) When there is an error, (D2) + 1 turns ON and the error code in stored in the completion status (S2) + 1.
2 - 26 2 - 26
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
(a) Example of a program for performing PLC CPU monitoring registration
This example shows a program that registers PLC CPU monitoring for the
CH1 side interface.
This registration is for transmitting the contents of M0 to M15 and D100 to
D109 to the external device using constant cycle transmission (cycle time is 3 min).
Converts registration command to pulses
Sets execution type
Sets request type (PLC CPU monitoring registration)
Sets cycle time unit to minutes
Sets cycle time to 3 (min)
Sets the monitoring function to constant cycle transmission
Sets the means of transmission to data transmission
Sets the output head pointer
Sets the transmission count of the user frame
Sets data set complete flag -1
Sets the number of registered word blocks to 1
Sets the number of registered bit blocks to 1
Registers the devices for
D100 to D109 as the first block
Registers the devices for M0 to M15 as the second block
Sets data setting complete flag -2
Executes PLC CPU monitoring registration
Normal completion
Abnormal completion
(b) Example of a program for executing PLC CPU monitoring cancellation
This example shows a program that cancels PLC CPU monitoring for the
CH1 side interface.
Sets pulse command
Executes PLC CPU monitoring registration reset
Normal completion
Abnormal completion
2 - 27 2 - 27
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
2.4 Precautionary Notes for Using the PLC CPU Monitoring Function
(1) The cycle time will be affected by the following factors.
Keep these in mind when setting the cycle time.
1) When the PLC CPU is accessed by a module other than the Q series C24.
2) When a data communication function other than the PLC CPU monitoring function is used.
3) When transmission stops by DTR/DSR control.
(2) Both the constant cycle transmission and the condition agreement transmission cannot be designated together for the same interface.
(3) Only the local station's PLC CPU can be the target for the PLC CPU monitoring function.
(4) A new PLC CPU monitoring registration cannot be performed while the PLC CPU monitoring function is in operation. In this case,
1) Perform the new PLC CPU monitoring registration after canceling the PLC
CPU monitoring.
2) If the new PLC CPU monitoring registration is performed without canceling the
PLC CPU monitoring, an error will occur.
Also, for PLC CPU monitoring registration using GX Configurator-SC, perform the registration after placing the PLC CPU in the STOP status, and then restart
QCPU.
(5) While the PLC CPU monitoring function is in operation, even if an error occurs with transmission/notification of the PLC CPU monitoring results or reading of data from the PLC CPU, the PLC CPU monitoring function operation will not stop.
(6) The PLC CPU monitoring function can only be used when the system configuration is 1:1.
(7) The following describes how the Q series C24 operates when the PLC CPU monitoring result information cannot be sent to the external device due to line disconnection or other reason.
Even if an error occurs while the PLC CPU monitoring function is in operation, the ERR LED does not light up. (This is the same as when using the ondemand function of the MC protocol).
(a) When the setting for the transmission monitoring time designation (timer 2) is an infinite wait (0
H
)
1) Reading of monitoring data from the PLC CPU stops until the transmission of monitoring data completes.
2) When transmission resumes, reading of monitoring data from the PLC
CPU resumes and monitoring data and information are transmitted.
(b) When the setting for the transmission monitoring time designation (timer 2) is other than an infinite wait (0
H
)
1) A transmission timeout error occurs, monitoring information read from the
PLC CPU, and transmission of monitoring information resumes.
2) The error code is stored in the PLC CPU monitoring function error code storage area (address: 2205
H
).
(8) When device data for the PLC CPU cannot be read because of a PLC CPU error
(hardware failure, etc.), the error code is stored in the PLC CPU monitoring function error code storage area and the Q series C24 performs the monitoring processing based on previously read data.
2 - 28 2 - 28
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
(9) When transmitting the monitoring information as data using the modem function, a modem connection error will occur if a modem connection is requested for the following reasons.
• A connection request by Y11
• A notification-issued request by Y14
If possible, provide a dedicated Q series C24 for using the PLC CPU monitoring function.
When using both the PLC CPU monitoring function and data communication function with a single Q series C24 and one of the above modem connection errors occurs, re-execute a connection request in consideration of the transmission timing set by the user for the PLC CPU monitoring function.
2 - 29 2 - 29
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3 COMMUNICATIONS BY THE MODEM FUNCTION
This chapter explains the overview and how to use the modem function, which can be used for data communication with remote external devices and paging pager terminals.
3.1 Overview
The overview of the modem function is described below:
(1) The modem function easily performs data transmission/reception to remote devices via public lines/office telephone systems/digital lines (ISDN) by connecting a modem or TA (terminal adapter) to the Q series C24's RS-232 interface.
1) Communicating arbitrary data with an external device
2) Call pager receiver (beeper) to notify the PLC’s system maintenance information.
3
(2) Initialization of the modem or TA, line connection (dialing), and line disconnection are performed using the PLC CPU.
(3) Once the line is connected, data communication with the external device via public line/office telephone system/digital line, or a call to pager receiver can be made.
Q series C24
Modem/TA ( 1)
Modem/TA ( 1)
External device
RS-232
Pager receiver
1 TA: terminal adapter
3 - 1 3 - 1
3
3 COMMUNICATIONS BY THE MODEM FUNCTION
3.1.1 Features
MELSEC-Q
The following explains the features of the modem function.
(1) Interface that can use the modem function
1) The modem function can be used with the Q series C24 using an RS-232 interface.
2) For the QJ71C24(N)-R2, the modem function can only be used by one of the two existing RS-232 interfaces.
With the interface of the Q series C24, which does not use the modem function, direct data communication with an external device can be performed using an MC protocol, non procedure protocol or bidirectional protocol (independent operation).
QJ71C24-R2
CH1.
CH2.
CH1.
CH2.
Communication using the modem function
Communication without using the modem function
(2) Initialization, line connection and disconnection of the modem or TA
1) The following set values for line connection can be used by storing to the Q series C24 Flash ROM in multiple sets.
• Modem/TA initialization data (AT command)
User setup: 30 sets (78 bytes/set); default value: 13 sets
• Connection data
User setup: 30 sets (80 bytes/set)
(Telephone number of the connection destination and display message to the pager receiver.)
2) By registering the above data to the Q series C24 ahead of time, the modem/TA (terminal adapter) initialization, line connection (dialing), and line disconnection can be performed with ease.
3) When the no-communication interval time (1 min to 120 min) is set, the Q series C24 disconnects the line when a no-communication condition has occurred for the set period of time following the line connection.
(3) Communication between a remote external device and PLC CPU
1) Data communication can be performed via full-duplex communication.
2) From the external device to the PLC CPU, communication using the MC protocol, non procedure protocol and bidirectional protocol can be performed.
3) From the PLC CPU to the external device, communication using the MC protocol (transmission by the on-demand dedicated-protocol function only), the non procedure protocol and bidirectional protocol can be performed.
3 - 2 3 - 2
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(4) Notification to the pager receiver
1) In order to notify to the pager receiver of the PLC system maintenance information, the Q series C24 performs calling and message transmission according to the user-designated connection data when the output signal from
PLC CPU is turned from ON to OFF.
2) Because Q series C24 notification processing is performed while the output signals from PLC CPU are turned OFF from ON, dedicated notification can be performed when the PLC CPU enters the STOP state due to an error, etc.
Q25HCPU
MODE
RUN
ERR.
USER
BAT.
BOOT
QJ71C24-R2
CH1.
CH2.
CH1.
Modem
Notification
USB
RS-232
CH2.
Out of material detection
Notification-issued request Y14
Notification execution direction
Data number for connection
0
0
1 n
Q25HCPU
MODE
RUN
ERR.
USER
BAT.
BOOT
QJ71C24-R
CH1.
CH2.
CH1.
RS-232 cable
USB
RS-232
CH2.
(5) Communication from the GX Developer
1) Access from the GX Developer to the remote PLC CPU can be made. (read and write from/to the device data and sequence program)
2) The QCPU can be accessed after reconnection from the Q Series C24 side using the callback function.
GX Developer
Modem
Public line
Modem
RS-232 cable
Transmission costs after line connection by callback from the Q Series C24 side are borne by the Q Series C24 side.
3 - 3 3 - 3
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
GX Developer parameter setting
• Remote password
• Module subject to the remote
password check
(6) Remote password check
If the remote password check has been set for the Q series C24 installed in the
QCPU, the Q series C24 executes a remote password check when the PLC is accessed from an external device using the Q series C24 modem function.
The following is an overview of the QCPU remote password function. See
Section 3.3.3 for more details.
(a) Remote password function
The remote password function allows / prohibits access to the
QCPU from an external device via the following modules.
• Q Series C24
• Ethernet module
In the case of the Ethernet module, the remote password function can be used for data communications connections with an external device. For details, see the User’s Manual (Basic) for the Ethernet module.
(b) Station where the remote password and remote password check are set
1) In the case of a PLC system with one QCPU station
QCPU Q series C24
Public line
Modem
Remote password
Remote password check
Modem
External device access source
Communication executing the remote password check
• Communication using MC protocol
• Communication using the GX Developer
2) In the case of a PLC system consisted of multiple QCPU stations
Set in the QCPU station which is the entrance of the PLC system as viewed from the external device (the local station QCPU in the diagram below).
Set in the local station to allow/prohibit access to the network System 1 from the external device.
(Local station)
Remote password
QCPU
Ethernet module
Remote password check
Q series C24
Ethernet
(Relay station)
QCPU
Ethernet module
Ethernet module
QCPU
Ethernet module
(Access station)
Ethernet
Modem
Public line
Modem
External device access source
Not set in the relay station or access station. ( )
Network System 1
When set in a station other than the QCPU which is the entrance of the PLC system (relay station or access station in the above diagram), access to other stations beyond the set station is prohibited.
3 - 4 3 - 4
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3.1.2 Function list
Function
Modem/TA initialization
Line connection (dialing)
Data communication
Notification
Line disconnection
Flash ROM reading, writing (registration) and deletion
The following describes the overview of the modem function:
Overview
Initializes the modem/TA using the user-designated initialization data (AT command). (Auto initialization of the modem / TA is possible.)
Dials the partner telephone number according to the user-designated connection data and enables data communication after establishing the line connection. When the modem/TA is not initialized, performs initialization.
Performs communication with an external device using the MC protocol, non procedure protocol or bidirectional protocol.
Performs communication with the partner Q series C24-installed station by modem/TA connection using non procedure protocol or bidirectional protocol. (Station-to-station communication.)
Enables the communication between GX Developer and PLC via Q series C24.
Communication method: full-duplex communication
Synchronization method: start-stop synchronous system
(asynchronous)
Calls and transmits messages to the pager receiver.
Forcefully disconnects the line from the connected destination device.
Reads, writes (registers) and deletes the initialization data (AT command) and data for connection from/to the Flash ROM in the Q series C24 according to the request from PLC CPU.
Remote password check
Callback
Allows the Q series C24 to execute the remote password check set in the QCPU when there is communication from the external device to the Q series C24 using MC protocol or the PLC is accessed using the GX Developer.
After line connection from the GX Developer, access to the QCPU from the GX Developer is made possible through line reconnection from the Q Series C24 (callback). Transmission costs after line connection from the Q Series C24 side are borne by the Q Series C24 side.
3 - 5 3 - 5
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3.1.3 Comparisons with related devices
The following shows a comparison with the related products which supports data communication with the PLC using the modem and public line, etc., similarly to the communication performed via the modem function.
Communication function name
Q series C24
(modem function)
B A
QC24N
(modem function)
Q6TEL
(for QnACPU/ACPU)
A6TEL
(for ACPU)
Modem/TA initialization
Sequence program
GX Configurator-SC
Line connection (dialing)
Communication between same products (such as
C24-C24)
MC protocol
Non procedure protocol
Bidirectional protocol
Communication between Q series C24 and other products
Remote communication from GX Developer
Callback function
Remote communication from peripheral device for GPPQ
Remote communication from peripheral device for GPPA
Notification Pager receiver
( 1
)
—
— —
(Performed on the external device side)
— —
Remote password check
Line disconnection
Data setting
• Data for modem
Sequence program
GX Developer
GPPQ initialization
• Data for connection
GPPA
GX Configurator-SC
Number of connectable modems/TAs
Transmission type
Connectable lines
Analog 2-line method
Analog 4-line method
Digital line (ISDN)
(
3
)
—
(Performed on the external device side)
1
Pulse/tone
— —
: enable
: disable
1 Modem initialization is executed automatically when the Q Series C24 starts up.
2 The internal modem is automatically initialized.
3 Prior to data communication, the Q series C24 checks whether the remote password specified by the user and the remote password set in the QCPU agree or not. If they agree, it allows access to the specified station.
4 When starting data communication, designate the connection data with the buffer memory.
3 - 6 3 - 6
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3.2 System Configuration
This section describes system configurations when the modem function is used to call a pager receiver or to perform data communication with an external device via public lines.
3.2.1 System configuration when performing data communication with an external device
The following describes the system configuration examples used when performing data communication between the external device and PLC using the Q series C24's
MC protocol/non procedure protocol/bidirectional protocol.
(1) Connection example with an external device
Q25HCPU
MODE
RUN
ERR.
USER
BAT.
BOOT
QJ71C24-R2
CH1.
CH2.
CH1.
RS-232 cable
USB
CH2.
RS-232
Modem
Public line
Modem
RS-232 cable
External device
(2) Connection example with a Q series C24
Q25HCPU
MODE
RUN
ERR.
USER
BAT.
BOOT
QJ71C24-R2
CH1.
CH2.
CH1.
RS-232 cable
USB
CH2.
RS-232
Modem
Public line
Modem
RS-232 cable
Q25HCPU
MODE
RUN
ERR.
USER
BAT.
BOOT
QJ71C24-R2
CH1.
CH2.
CH1.
USB
RS-232
CH2.
Q25HCPU
MODE
RUN
ERR.
USER
BAT.
BOOT
USB
RS-232
QJ71C24-R2
CH1.
CH1.
CH2.
(3) Connection example with a Q series C24 via cellular phone
QJ71C24-R2
Q25HCPU
MODE
RUN
ERR.
USER
BAT.
BOOT
CH1.
Public line
Modem
CH1.
CH2.
RS-232 cable
Cellular
Phone
USB
CH2.
CH2.
RS-232
Cellular phone connection adapter
The public lines indicated in (1) to (3) above are compatible with the office telephone system as well.
In the system configurations shown in (1) and (2) above, the digital line (ISDN) can replace the public line.
When connecting via a digital line, a TA (terminal adapter) and a DSU (digital service module) are used instead of a modem.
3 - 7 3 - 7
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3.2.2 System configuration when using the notification function
The following describes the system configuration example when calling the pager receiver by the notification function.
Q25HCPU
MODE
RUN
ERR.
USER
BAT.
BOOT
QJ71C24-R2
CH1.
CH2.
CH1.
RS-232 cable
USB
CH2.
RS-232
Modem
Public line
Pager receiver
The public line indicated above is compatible with the office telephone system as well.
3 - 8 3 - 8
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3.2.3 System configuration when connecting GX Developer
The following describes the system configuration when GX Developer performs data communication with a remote station PLC via Q series C24.
GX Developer
Q25HCPU
MODE
RUN
ERR.
USER
BAT.
BOOT
QJ71C24-R2
CH1.
CH2.
CH1.
RS-232 cable
USB
RS-232
CH2.
Modem
Public line
Modem
RS-232 cable
The above public lines is compatible with the office telephone system as well.
The following settings are performed in the items below when setting the connection destination using the GX Developer. See the GX Developer manual for details.
Personal computer-side interface
PLC-side interface
Telephone line connection (Q/A6TEL, C24) : Data for line connection
For other items, settings are performed according to the access destination station.
: Serial
: C24
POINT
When the GX Developer is connected, perform the settings and operations described in Section 3.3.7 to prevent a line to the modem from disconnecting even if communication between the GX Developer and PLC is interrupted.
3 - 9 3 - 9
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3.2.4 Precautions for system configurations
The following describes the precautionary items when configuring the system to perform data communication with an external device or call a pager receiver via public line, an office telephone system or digital line (ISDN) using the Q series C24 modem function.
(1) Usable Q series C24 interface
1) The modem function can be used with the RS-232 interface only.
2) For QJ71QC24(N)-R2, the modem function can only be used with one of the two existing RS-232 interfaces.
3) It is not possible to perform data communication via two interface of Q series
C24 (linked operation).
(2) Connectable modem/TA
Only the modems/TA indicated in Section 3.3.2 can be used for the Q series C24
RS-232 interface using the modem function.
(3) Number of connectable modems/TA's
Only one modem/TA can be connected to the Q series C24 RS-232 interface that uses the modem function.
(4) Modem/TA connection cables
1) The RS-232 cable supplied with the modem/TA or the designated modem/TA cable can be used for connection between the Q series C24 and modem/TA.
2) RS-232 interface connector of the Q series C24 has D-sub 9 pins (female).
For the Q series C24 side of the connection cable, use the connector shell indicated in Section 3.2.1 (3) of the User's Manual (Basic).
3 - 10 3 - 10
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(5) Modem/TA installation
1) Install the modem/TA according to the modem/TA manual.
When installed in an area in which a lot of noises exists, malfunctions may occur.
2) In order to prevent the effects of noise and power surges, do not connect near or tie the cable together with a main circuit line, high-voltage line or load line other than for the PLC with the modem/TA connection cable.
(6) Connectable lines
1) The connections can be made with the following lines.
Perform connection tests beforehand and confirm that connection is possible.
• Public line or office telephone system of analog two-line method
• Digital line (ISDN)
2) It is not possible to connect to call-waiting lines, in order to avoid data errors or automatic line disconnection due to the call-waiting interrupt tone.
3) Avoid connections with party-line telephones to avoid interrupted calls during communication.
4) If an alert sound is sent at fixed intervals from the communication machine to prevent long-term calls, data may experience errors.
It is recommended to check the normality/abnormality of data reception between devices, and perform transmission-retry processing when an abnormality is detected.
5) See the modem/TA manual regarding the connection from a modem to public line/office telephone system, or from a TA (terminal adapter) to a digital line.
(7) Communication system
Communication via the modem function is performed using full-duplex communication.
Connections cannot be made devices designed for half-duplex communication.
(8) Data communication and notification to external devices
1) Data communication with external devices and notification to a pager receiver are performed using the public line or electric wave transmitted from the electric wave transmission base.
There might occur a condition in which correct data communication or notification cannot be carried out due to an error from the system's setup environment, electric-wave transmission status, error in the partner device, etc.
Perform a connection test beforehand, and confirm that connection is possible.
2) In notification processing via electric-wave transmission, errors from the pager receiver cannot be detected.
Setup a separate call circuit with a lamp display or buzzer to ensure the safety of the PLC system.
3 - 11 3 - 11
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3.3 Specifications
This section explains the transmission specification on the Q series C24 side, connectable modems/TA's (terminal adapter), I/O signals related to the modem function, and buffer memory for the usage of the modem function.
3.3.1 Transmission specifications
The transmission specifications on the Q series C24 side for use of the modem function are as shown below.
The transmission specifications between Q series C24 and a modem/TA (local station
Q series C24) that are not provided in this table are shown in User’s Manual (Basic).
Modem function
Interface that can use the modem function
Linked operation between CH1 and CH2 of the Q series C24
Communication method
Synchronization method
Transmission speed (Unit: bps)
Data format
Error detection
Item
Start bit
Data bit
Parity bit
Stop bit
Parity check
Sum check code
QJ71C24N
QJ71C24
Available
RS-232
QJ71C24N-R2
QJ71C24-R2
Not available
Full duplex communication
Asynchronous method
1200, 2400, 4800, 9600, 14400, 19200, 28800,
38400, 57600, 115200, 230400 (selectable)
1
7 / 8
1 (On) / 0 (Off)
1 / 2
On (odd/even selectable) / Off
On / Off
QJ71C24N-R4
Not available
—
Transmission control
Data communication
No procedure protocol
Bidirectional protocol
MC protocol
RS · CS control / not-control (selectable)
Available
Available
Available
Line connection (Q series C24: modem) 1:1
1 When the first five digits of the serial No. are 03042 or earlier, the transmission speed cannot be set to 115200 bps for connection between the Q series C24 and the GX Developer via a modem.
3 - 12 3 - 12
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3.3.2 Specification of connectable modems/terminal adapters
Modem-tomodem communication specification
Q series C24-to modem communication specification
The specification of modems/TA's that can be connected to the Q series C24 side when using the modem function is shown below.
(1) Specification and precautions for the connectable modems
(a) Modem specification
Item
Connection line
Initialization
Telephone line
Specification
When using the subscriber's telephone line/office telephone system
When using a manual line connection/cellular phone
Analog 2-line
Hayes AT command compatible
A line compatible with NTT communication protocol
Remarks
—
See Section 3.4.3
See Section 3.2.4 regarding the restrictions
Communication standard
Error correction
( 1)
Data compression
ITU-T
Bell
MNP
ITU-T
MNP
( 1)
ITU-T
ANS-ORG mode switch
Q series C24-side connector
(RS-232)
DR signal control
Other
V. 34/V.32bis/V.32/V. 22bis/V. 22/V. 21/V. fc
212A/103
Class 4 and 10 compliant
V.42 compliant
—
Class 5 compliant
V.42bis compliant
Mode switching required
—
9-pin (female) D sub
Only the DR (DSR) signal must be able to turn on
Compatible with the Q series C24 specification
See Section 3.2 of User's
Manual (Basic)
( 2)
See Chapter 3, Section 3.3.1
of User's Manual (Basic)
1 The following are the functions of the modem itself that become available by issuing the AT commands to the modem. See the modem manual for details.
(1) Error correction
1) When a noise occurs on the line, scrambled data may appear due to interrupted communication data.
The error correction function is intended to suppress effects from such noises.
2) If an error such as scrambled data is detected by the error correction, the modem retries the transmission.
When the number of retries has exceeded the modem's limit, the modem determines that communication cannot be performed in that environment and disconnects the line.
3) Both modems must support the MNP4 or V.42 protocol.
(2) Data compression
1) This function compresses data to be sent prior to transmission, and inflates the compressed data upon reception, then forwards to the terminal.
2) The data compression is effective for the execution speed at a maximum of 200 % for the MNP5 and 300 % for the V.42bis.
3) Both modems must support the MNP5 or V.42bis protocol.
(3) Flow control (RS · CS control)
When communication between a modem and terminal is faster than between two modems, the flow control is performed in the following order:
3 - 13 3 - 13
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
1) The modem transmits data to the partner by storing the data from the terminal in the modem buffer.
2) When the buffer in the modem becomes almost full, the modem outputs a data-transmission temporary stop request (CS signal =
OFF) to the terminal.
The terminal then stops data transmission to the modem when the data-transmission temporary stop request (CS signal = OFF) is received.
Even while the terminal pauses data transmission, the modem continues to send data to the partner.
3) When a free space is present in the modem buffer, the modem outputs the data-transmission resume request (CS signal = ON) to the terminal.
The terminal then resumes data transmission to the modem when the data-transmission resume request (CS signal = ON) is received.
2 Modems that turn on the CD signal simultaneously cannot be used.
(b) Precautions for selecting a modem
1) When using a cellular phone
A modem with the error correction function of MNP class-10 is recommended. However, note that communication may not be established depending on the line condition.
2) Modem setting
• Set the modem on the Q series C24 side as shown below:
Setting item
Communication rate
Modem command
SI/SO control
Communication method
Data bit
Data format Stop bit
Parity bit
Setting range
Depends on the modem in use ( 1)
Hayes AT command
None
No procedure
Match the Q series C24 ( 2) ( 3)
1 When using different modems, the slower communication rate will be in effect.
2 Some modems may transmit one character as 10 bits.
Check the modem specifications when setting the Q series C24 transmission specifications.
3 Some modems may switch the communication rate following the start of data communication.
Since the Q series C24 cannot switch the communication rate, set the modem side so that its communication rate does not switch.
• When using a modem whose DR terminal (signal) is set by a switch, set the DR-terminal (modem output) switch level to high.
When using a modem whose DR terminal is set by a software, write the command that turns on the DR terminal into the data for initialization.
Set the "Modem initialization time DR signal valid/invalid designation" to "Invalid" during modem function system settings with GX
Configurator-SC.
3 - 14 3 - 14
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(2) Specification and precautions for the connectable TA's (terminal adapters)
(a) TA specification
TA-to-TA communication specification
Q series C24-to-
TA communication specification
Item
Connection line
Initialization
Communication standard
Specification
ISDN (INS net 64) equivalent
High-speed digital dedicated line
Hayes AT command compatible
B-channel line exchange (V.110)
D-channel packet exchange
V.28 compliant
V.24 compliant
Remarks
DSU and TA are required
See Section 3.4.3
Electrical condition
Circuit definition
Q series C24-side connector
(RS-232)
DR signal control
Other
9-pin (female) D sub
Only the DR (DSR) signal must be able to turn on
—
See Section 3.2 of User's
Manual (Basic)
(
1
)
Compatible with the Q series C24 specification
See Chapter 3, Section
3.3.1 of User's Manual
(Basic)
1 TA's that turn on the CD signal simultaneously cannot be used.
Use a TA capable of flow control as described in (1) (a) in this section also for the communication between the TA and terminal.
control is a function of the TA itself that becomes available by issuing the AT commands to the modem. See the TA manual for details.
(b) Precautions for selecting a TA
1) Set the TA on the Q series C24 side as shown below:
Setting item
Communication rate
TA command
SI/SO control
Communication method
Data bit
Data format Stop bit
Parity bit
Setting range
Depends on the TA in use
Hayes AT command
None
No procedure
Match the Q series C24 (
1
) (
2
)
1 Some TAs may transmit one character as 10 bits.
Check the TA specifications when setting the Q series C24 transmission specifications.
2 Some TAs may switch the communication rate following the start of data communication.
Since the Q series C24 cannot switch the communication rate, set the TA side so that its communication rate does not switch.
2) When using a TA whose DR terminal (signal) is set by a switch, set the
DR-terminal (TA output) switch level to high.
When using a TA whose DR terminal is set by a software, write the command that turns on the DR terminal into the data for initialization.
Set the "Modem initialization time DR signal valid/invalid designation" to
"Invalid" during modem function system settings with GX Configurator-
SC.
3 - 15 3 - 15
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3.3.3 Compatibility with the QCPU remote password function
This section explains the Q series C24 data communication for the QCPU remote password function.
See Section 3.1.1 (6) for an overview of the Q series C24 check function for the QCPU remote password.
The remote password function is a function that has been added to the QCPU as a means of preventing improper access (such as destroying a program or data) from an external device. However, this function cannot completely prevent improper access.
The user should incorporate his/her own safeguards when it is necessary to protect the security of the PLC system from improper access from an external device.
The company cannot assume any responsibility for any problems that may arise from system troubles caused by improper access.
An example of a safeguard on the PLC CPU with respect to improper access
One example is shown in Section 3.3.6, in which the PLC CPU disconnects a line to the external device when the number of times a "remote password mismatch" is detected exceeds the number set by the user with regard to the Q series C 24 remote password check explained in this section.
(1) Data communication during remote password setting
This section explains the use and setting of the QCPU remote password function and data communication between the external device and the QCPU when a remote password has been set.
(a) Allowing/prohibiting access to the PLC from the external device
1) Access allow processing (unlock processing)
• To access the specified QCPU, the external device performs the remote password unlock processing with respect to the Q series C24
( ) of the directly connected station (local station) after line connection for the modem function.
• If the unlock processing has not been performed, the remote password check performed by the Q series C24 ( ) that has received a communication request prohibits access to the specified station. (See
(2).)
• All data communication before the unlock processing is performed will be processed as an error.
The Q series C24 of the QCPU station for which a remote password is set will be indicated.
2) Access processing
Normal completion of the remote password unlock processing allows the specified station to be accessed.
• Perform communication using MC protocol.
(Perform on-line operation when the GX Developer is connected.)
3) Access prohibition processing (lock processing)
• When the specified station access is completed, the process for disconnecting the line for the modem function is performed in order to disable further access.
• When line disconnection is completed, the remote password lock processing is performed automatically.
3 - 16 3 - 16
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(When accessing the local station QCPU) (When accessing other station QCPU)
Modem
2) Access
1) Unlock processing
3) Lock processing ( 2)
A station
( 1)
Modem Modem
1) Unlock processing
3) Lock processing ( 2)
A station
( 1)
Modem
Remote password
QCPU
Remote password check
Q series C24
(Local station)
Remote password
QCPU
Remote password check
Q series C24
( 3)
Ethernet module
(Local station)
Ethernet
1 Unlock and lock processing for the local station
remote password is possible.
Remote password unlock and lock processing for
the relay station and access station cannot be performed
2 Lock processing is performed when a line for the modem
function is disconnected.
3 Even if the Ethernet module that transmits a communication
request to other Ethernet is set as a module subject to
the remote password check, unlock and lock processing
is not necessary.
QCPU
Ethernet module
Ethernet module
(Relay station)
Ethernet
2) Access
QCPU
Ethernet module
(Access station)
POINT
(1) The remote password unlock and lock processing can be performed only for the Q series C24 of the local station directly connected to the external device.
The remote password unlock and lock processing cannot be performed for the
Ethernet module of the other stations (relay station and access station).
(2) The remote password unlock processing from the external device is performed using dedicated commands for MC protocol communication.
(3) See Section 3.3.7 (8) for what to do when the remote password unlock processing is completed abnormally.
3 - 17 3 - 17
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(2) Remote password check processing performed by the Q series
C24
(a) Communication in which a remote password check is performed
1) When the following parameters are set for the Q series C24 installed in the QCPU station, the Q series C24 performs a remote password check for communication requests listed below.
• When a remote password is set in the QCPU
• When the Q series C24 that is communicating data with the external device has been set as a module subject to the remote password check
2) The Q series C24 performs a remote password check with respect to a communication request to the local station/other station received from the external device.
3) The Q series C24 does not perform a remote password check for the following communication requests.
• Transmission request from the local station QCPU (such as transmission using non procedure protocol)
• Communication request from the external device (including the GX
Developer connected to the local station QCPU) transmitted to other station upon request from the QCPU
Modem
QCPU
Q series
C24
Remote password
(Local station)
(Other station)
Remote password check
1)
2)
Ethernet module
3)
Modem
Path for items subject to remote password check
Path for items not subject to remote password check
GX Developer
3)
QCPU
Remote password
Remote password check
( 1)
Ethernet module
1 In the above diagram, a communication request from the external device cannot be received since the remote password check setting has been executed.
If the remote password check setting has not been executed, a communication request can be received and data communication from the external device is possible.
(b) Selecting modules subject to the remote password check
The user can select any Q series C24 to perform the remote password check and set this using QCPU parameters.
(This is set on the GX Developer remote password setting screen.)
3 - 18 3 - 18
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(c) Stations that can be accessed when the remote password check is performed
1) If the external device performs the remote password unlock processing with respect to the Q series C24 of the directly connected station (local station) after line connection for the modem function, it can access the local station QCPU.
2) When accessing the PLC of other station via the Ethernet module of a relay station or access station, the following settings determine whether access is allowed/prohibited.
• To prohibit access to other station from an external device using the
MELSECNET/H or MELSECNET/10 relay communication function of the Ethernet module, place a check mark at the following setting items in the remote password setting for the relay station or access station.
"GX Developer communication port (UDP/IP) ( ), dedicated commands, MELSECNET/H, MELSECNET/10 relay communication port"
Set on the GX Developer remote password setting screen.
If a check mark is not placed at the above setting items, access to other station will be allowed.
3) See the user's manual (basic) for the Ethernet module for stations that can be accessed when accessing other station PLCs via the Ethernet module. (When reading the manual, substitute the Q series C24 with the station connected to the external device).
(3) Data communication procedure
This section explains the procedure when the external device performs data communication via the Q series C24 in which the remote password check is performed.
1) Initialization of the modem of the Q series C24 side and external device side is performed at each device sides.
2) The line is connected from the external device.
3) The external device performs the remote password unlock (release) processing for the QCPU of the station where the Q series C24 is installed using dedicated commands for MC protocol communication. (The unlock processing cannot be performed for the QCPU of other station.)
See Section 3.3.7 (8) for what to do when the remote password unlock processing is completed abnormally.
4) Data communication is performed from the external device using MC protocol.
5) When data communication using MC protocol is completed, a line for the modem is disconnected from the external device.
When line disconnection is completed, the remote password lock processing is performed automatically.
REMARK
(1) See Section 3.18 of Reference Manual for the unlock processing for the remote password.
(2) When accessing the PLC from the GX Developer connected to the Q series
C24, the remote password unlock processing is performed when on-line operation begins.
3 - 19 3 - 19
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(4) How to set the remote password
On the screen below for setting parameters (remote password) using the GX
Developer, set the remote password in the QCPU and specify the Q series C24 that performs the check.
Set the remote password as the following instructions.
[Start procedure]
"GX Developer" Remote password "Remote password setting" screen
[Setting screen]
Item name
Password settings
Model name
Password active module settings Start XY
Conditions
[Setting item]
Set data
Enter the remote password to be set in the QCPU (
Select the type of module that checks the remote password set in the QCPU
Set the head address of the module that checks the remote password
(No setting required)
1
)
Setting range/choices
4 bytes
QJ71C24/CMO
0000
H
to 0FE0
H
—
1 Consider the following when setting the remote password.
• Avoid using a character string of simple numbers or letters only.
• Mix numbers, letters and special characters (?, ., !, &, %, etc.).
• Avoid using a character string that represents the user's name or date of birth.
POINT
(1) When using the Q series C24 in a multiple CPU system, write the remote password setting in the control PLC of the Q series C24.
(2) After setting the remote password in the QCPU, reboot the QCPU (PLC No. 1 in a multiple CPU system). (Reset/power reset using the RESET/L.CLR switch)
By rebooting the QCPU, the remote password becomes valid.
(3) The password supported by the QCPU function version A is used to prohibit reading/writing of file data in the QCPU using the GX Developer.
Dual access control can be provided by using the remote password described in this section and password for file access.
3 - 20 3 - 20
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(5) Setting from the GX Configurator-SC
When the Q series C24 performs a remote password check for the remote password set in the QCPU, the remote password check setting as well as the present check results can be monitored with respect to the screen items listed in the table below.
See Section 3.3.6 for an explanation of each area.
GX Configurator-SC setting/monitor screen
"Modem function system setting" screen
"Modem function monitor/test" screen
Setting/monitor items for the remote password check
Remote password mismatch notification count designation
Remote password mismatch notification accumulated count designation
Remote password mismatch notification count designation
Remote password mismatch notification accumulated count designation
Accumulated count of unlock process normal completion
Accumulated count of unlock process abnormal completion
Accumulated count of lock process based on circuit disconnection
Buffer memory address
8204 (200C
H
)
8205 (200D
H
)
8204 (200C
H
)
8205 (200D
H
)
8955 (22FB
H
)
8956 (22FC
H
)
8959 (22FF
H
)
3 - 21 3 - 21
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3.3.4 Compatibility with the callback function
The following describes the Q Series C24 callback function that can be used when accessing the QCPU from the GX Developer connected to the Q Series C24.
(1) About the Callback function
(a) What is the Callback function
The callback function is a function that makes it possible to access the
QCPU from the GX Developer by reconnection (callback) of the line from the Q Series C24. Transmission costs after line connection from the Q
Series C24 side are borne by the Q Series C24 side.
(b) Settings in order to use the callback function
The callback function can be used by setting it through the GX
Configurator-SC, then registering it in the Q Series C24. (See (4).)
(c) Selecting the callback destination GX Developer
The GX Developer that can be called back in accordance with the settings in the Q Series C24 can be selected as shown below.
1) If the callback destination GX Developer is fixed (1 module)
(Callback connection (during fixed))
Connection can be made to only the fixed GX Developer (1 module) registered in the Q Series C24.
2) If it is being made possible to change the callback destination GX
Developer (Callback connection (during designated number))
It is possible to connect to the GX Developer when the callback destination telephone number (Call number) is specified.
3) If the maximum number of callback destination GX Developers is limited to 10 modules.
(Callback connection (during max. designated number is 10))
Connection is possible with only those GX Developers (max. 10 modules) with a callback destination telephone No. registered in the Q
Series C24.
A description of the callback operation in 1) to 3) is shown in (4) (b).
Setting of callback function designation settings by the
GX Configurator-SC
1) Line Connection
2) Temporary line disconnection
3) Line connection
4) Access to the QCPU
5) Line disconnection
Selection of the connection system and line connections
Modem
Modem
GX Developer
Q Series C24
Processing for the GX Developer to access the QCPU
Processing by the callback function
POINT
See Section 2.7 of the User’s Manual (Basic) for Q Series C24 and GX Developer versions that are compatible with the callback function.
3 - 22 3 - 22
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(2) Data communications procedure
Here, the procedure for data communications when using the callback function is shown.
(a) Q series C24 side procedure
Carry out procedure of starting the modem function and data communications in accordance with Section 3.4.1.
1) Set the callback function by the GX Configurator-SC. (See (4).)
2) Initialize the Q Series C24 side modem. (See Section 3.4.)
3) The modem’s initialization completed signal (X10) goes On when modem initialization is completed.
Wait for the line connection from the GX Developer.
Select the connection system (connect way) from the GX
Developer, then make line connection.
When the Q Series C24 callback processing is completed normally, the line connection signal (X12) is in the ON state.
POINT
See the GX Developer’s Operating Manual for details of the line connection screen from the GX Developer when using the callback function.
(3) Cautions during data communications
(a) Set the GX Developer side modem which the Q Series C24 is to reconnect to (callback) on "with Auto Reception. " (With Auto Reception: This setting enables line connection from the external device.)
(b) When a request is issued for a line connection from another GX Developer during a temporary line disconnection from the GX Developer side by callback processing, the Q Series C24 executes a callback operation for the latter connection request.
The Q Series C24 terminates callback processing to the GX Developer that it received a connection request from earlier.
(c) If you are making a line connection to the GX Developer by the following connection system, select "callback reception waiting" as the connection system for the GX Developer that the Q Series C24 is reconnecting to
(callback) and make the connection.
• Callback request (during fixed/during designated number)
(Example) In the case of line connections with "Callback request (during designated number)" as the connection system.
Setting of callback function designation settings by the
GX Configurator-SC
Select "Callback request (during designation number)", input the telephone No. 2) and make the line connection.
Callback request
(during designated number)
Modem
GX Developer
Telephone No. 1)
Modem
Select "Callback reception waiting" and make the line connection.
Registration in the Q Series C24
Callback data No. 1 Telephone No. 1)
Callback data No. 2
Callback data No. 3 to
Telephone No. 2)
Telephone No. 3) to
Callback data No. 10 Telephone No. 10)
Line connection
Modem
"Callback reception waiting"
GX Developer
Telephone No. 2)
3 - 23 3 - 23
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(d) If callback processing was not executed normally, an error message screen is displayed on the GX Developer side. Perform the processing operation
(reconnection operation, etc.) corresponding to the displayed message.
The operating state on the Q Series C24 side can be confirmed by the following items in the GX Configurator-SC monitor/test screen.
GX Configurator-SC
Monitor / test screen
X•Y monitor/test
Monitor item
X10: Modem initialization completion
X12: Connection in progress
Buffer memory address
—
—
Description
Section 3.3.5
Modem function monitor/test
Modem function sequence status 222
H
Section 3.3.6
(e) Set the settings related to the callback function in the following areas of the
GX Developer.
[Starting Procedure]
GX Developer [Tools] [Options] TEL
1) Line callback cancel wait time
(Setting range: 1 to 180 s. (Default: 90 s.))
This specifies the waiting time after sending a response to a callback request from the Q Series C24, until the line is disconnected from the
GX Developer.
If the line is not disconnected from the GX Developer within the specified time in this area, the Q Series C24 forcibly disconnects the line, terminating callback processing.
2) Callback delay time
(Setting range: 1 to 999 s. (Default: 20 s.))
This specifies the time from the temporary line disconnect on the GX
Developer side until the Q Series C24 reconnects (callback).
POINT
See the troubleshooting section of the User’s Manual (Basic) for the symptoms of trouble that may occur during access from the GX Developer to the QCPU using the callback function, the causes and remedies.
3 - 24 3 - 24
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(4) Setting and monitoring by the GX Configurator-SC for use of the callback function
(a) Setting, monitoring / test items
Carry out setting, monitoring and testing of the callback function using the following GX Configurator-SC screen.
1) Setting items through the "modem function system setting" screen
This shows the callback function setting items.
See Section 3.3.6 for the modem function setting items, including the following items.
Setting Item Setting value
GX Developer connection designation
Callback function designation
Callback denial notification accumulated count designation
Data No. for Callback designation 1 to
10
Connect
Settings 1 to 6 (See (b).)
0 to 65535
BB8
H
to 801F
H
Setting possible / impossible
Description
Be sure so specify “Connect” when using the callback function.
Select according to the callback operation.
Specify the accumulated count value informed to the user.
Specify the connection data No. See
Section 3.4.4 for setting values.
: Must be set : Set as necessary
2) Monitoring / Testing through the "modem function monitor / test" screen
This shows the callback function monitoring and testing.
See Section 3.3.6 for monitoring and testing of the modem function, including the following items.
Callback function monitoring / test items
Callback permit accumulated count
Callback denial accumulated count
Auto (callback) connection permit accumulated count
Auto (callback) connection denial accumulated count
Accumulated count of callback receive procedure cancel
Buffer memory address
8944 (22F0
H
)
8945 (22F1
H
)
8946 (22F2
H
)
8947 (22F3
H
)
8948 (22F4
H
)
3 - 25 3 - 25
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(b) Callback function designation and callback operation outline
Here the setting values for "Callback function designation" items in the
"Modem function system setting" screen and an outline of the corresponding Q Series C24 callback operation are explained.
Values in parentheses are values when the set values are stored in buffer memory (Address: 2001
H
).
If the connection system is set on "Auto (Callback: during fixed/Callback : during designated number)" and line connection is executed, (Setting 1 to
Setting 3) are explained in 5).
Function
1) If the callback function is not used.
2) If the callback destination GX Developer is fixed (1 module)
(Callback connection (during fixed))
3) If it is being made possible to change the callback destination GX Developer
(Callback connection (during designated number))
4) If the maximum number of callback destination GX
Developers is limited to 10 modules.
(Callback connection (during max. designated number is
10)
Setting values for "Callback function designation" items.
If you desire to set the connection system on
"auto" and carry out line connection.
If you set the connection system on "auto" and do not carry out line connection.
Auto (0
H
) —
Setting 1 (9
Setting 2 (B
Setting 3 (F
H
H
H
)
)
)
Setting 4 (1
Setting 5 (3
Setting 6 (7
H
H
H
)
)
)
1) If the callback function is not used (Auto (0
H
): (Default Value)
• Select this if the callback function is not being used.
• Data communications becomes possible after line connection from the GX Developer.
2) If the callback destination GX Developer is fixed (1 module)
(Setting 1 (9
H
) or setting 4 (1
H
))
• Select this if the Q Series C24 fixes the telephone No. (1 module) of the GX Developer side that is being called back.
• The Q Series C24 executes callback to the GX Developer side using connection data set in the following data No. 1 for callback, shown below. At this time, the external line dialing, line types and telephone number in the connection data become valid.
• Set callback data number 1 in the "Modem function system settings" screen.
(Example) If line connections are being made with "Callback connection (during fixed)" as the connection system
1) Line Connection
(Callback connection (during fixed))
Setting of callback function designation settings by the
GX Configurator-SC
2) Temporary line disconnection
3) Line connection to Telephone No. 1
Selection of the connection system and line connections
4) Access to the QCPU
5) Line disconnection
Modem
Modem
GX Developer
Registration in the
Q Series C24
Callback data No. 1 Telephone No. 1)
Callback data No. 2 Telephone No. 2)
Callback data No. 3 to
Telephone No. 3) to
Callback data No. 10 Telephone No. 10)
Not used
Processing for the GX Developer to access the QCPU
Processing by the callback function
3 - 26 3 - 26
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
Setting of callback function designation settings by the
GX Configurator-SC
3) If it is being made possible to change the callback destination GX
Developer
(Setting 2 (B
H
) or Setting 5 (3
H
))
• Select the callback destination telephone No. if it is being specified at the time when line connections are being made from the initial GX
Developer side.
• The Q Series C24 calls back the GX Developer with the callback destination telephone No. received from the GX Developer side.
At this time, the external line dialing, line types and the connection data set in the following callback data No. 1 are used.
• If the callback destination is not specified when line connections are made from the initial GX Developer side, the connection data set in the following callback data No. 1 are used to call back the GX
Developer side.
At this time, the external line dialing, line types and telephone number in the connection data become valid.
• Set callback data No. 1 in the "Modem function system setting" screen.
(Example) If line connections are being made with "Callback connection (during designated number)" as the connection system
Input the telephone No. 1) for the callback destination telephone No. and make line connections.
Line Connection
(Callback connection
(during designated number))
Modem
GX Developer telephone No. 1)
Callback
Modem
Line Connection
(Callback connection
(during designated number))
Input the telephone No. n) for the callback destination telephone No. and make line connections.
Registration in the Q Series C24
Callback data No. 1
Telephone No. 1)
Callback data No. 2
Telephone No. 2)
Callback data No. 3 to
Telephone No. 3) to
Callback data No. 10
Telephone No. 10)
Not used
Callback
Modem
GX Developer telephone No. n)
3 - 27 3 - 27
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
4) If the maximum number of callback destination GX Developer is limited to 10 modules.
(Setting 3 (F
H
) or Setting 6 (7
H
))
• Select the GX Developer to be called back if the Q Series C24 limits the callback destination to a maximum of 10 modules.
• Specify the callback destination telephone No. when making line connection from the initial GX Developer side.
• If the Q Series C24 checks the callback destination telephone No.
received from the GX Developer side and it is a telephone No. that is registered in the Q Series C24, callback is executed.
If a telephone No. that is not registered in the Q Series C24 is received from the GX Developer side, the Q Series C24 disconnects the line and does not execute callback.
• Data for checking the callback destination telephone No. by the Q
Series C24 are registered in callback Data No. 1 to 10.
Set the data registered in callback data No. 1 to 10 in the "Modem function system setting" screen.
Set the Callback function designation by the GX Configurator-SC.
Check the received telephone No. If it is
registered, make the line connection.
(Example) If line connections are being made with "Callback connection (during designated number)" as the connection system
Input the telephone No. 1) for the callback destination telephone No. and make line connections.
Line Connection
(Callback connection
(during designated number))
Modem
GX Developer telephone No. 1)
Callback
Modem
Line Connection
(Callback connection
(during designated number))
Input the telephone No. 2) for the callback destination telephone No. and make line connections.
Registration in the Q Series C24
Callback data No. 1
Telephone No. 1)
Callback data No. 2
Telephone No. 2)
Callback data No. 3
Telephone No. 3) to to
Callback data No. 10
Telephone No. 10)
Callback
Modem
GX Developer telephone No. 2)
3 - 28 3 - 28
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
5) If line connections from the GX Developer are made with "Auto
(Callback: during fixed/Callback: during designated number)" as the connection system
(Setting 1 (9
H
) to Setting 3 (F
H
))
• When accessing the QCPU from the GX Developer, select whether to use the callback function to make line connections or to make line connections without using the callback function.
• If the following is selected for the GX Developer connection system and line connections made, it is possible to access the QCPU from the GX Developer by that method only on that occasion.
Auto (Callback: during fixed)
Auto (Callback: during designated number)
The procedure is the same as when accessing the QCPU by selecting "Auto" for the connection system and making line connections.
• If line connections are made with the callback destination GX
Developer limited to a maximum of 10 modules set, (setting 3 (F
H
)), select "Auto (Callback : during designated number)" as the connection system and specify the telephone No.
The Q Series C24 checks the telephone No. received from the GX
Developer side and if it is registered in the Q Series C24, the line connection status is held and it becomes possible to access the
QCPU from the GX Developer.
If a telephone No. is received from the GX Developer that is not registered in the Q Series C24, the Q Series C24 disconnects the line.
• Data for checking the callback destination telephone No. by the Q
Series C24 are registered in callback Data No. 1 to 10.
Set the data registered in callback data No. 1 to 10 in the "Modem function system setting" screen.
(Example) If line connections are being made with "Auto (Callback: during designated number)" as the connection system
1) Line Connection
(Auto (callback: during
designated number))
Setting of callback function designation settings by the
GX Configurator-SC
2) Temporary line disconnection
3) Line connection
4) Access to the QCPU
5) Line disconnection
Selection of the connection system and line connections
Modem
Modem
GX Developer telephone No. 1)
Registration in the Q Series C24
Callback data No. 1
Telephone No. 1)
Callback data No. 2
Telephone No. 2)
Callback data No. 3
Telephone No. 3)
Callback data No. 10
Telephone No. 10)
Processing for the GX Developer to access the QCPU
Processing by the callback function
3 - 29 3 - 29
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
REMARK
If the GX Configurator-SC’s "Callback function designation" setting is performed in the Q Series C24, line connections to the GX Developer are possible by the connection system shown below.
The correspondence between the GX Configurator-SC "Callback function designation" setting items and the GX Developer connection system setting items is shown.
Q Series C24 Side
Callback function specification
Auto
GX Developer connection system (
1
)
Setting 1: Auto/Callback connection (during fixed)
Setting 2: Auto/Callback connection (during designated number)
Setting 3: Auto/Callback connection (during max.
designated number is 10)
Setting 4: Callback connection (during fixed)
Setting 5: Callback connection (during designated number)
Setting 6: Callback connection (during max.
designated number is 10)
1) 2) 3) 4) 5) 6) 7) 8) 9)
: Connection possible
1 This shows the GX Developer connection system. See the GX Developer
Operating Manual for details about line connection from the GX Developer.
1) Auto
2) Auto (callback: during fixed)
6) Callbak request (during fixed)
7) Callbak request (during
3) Auto (callback: during designated number)
4) Callback connection (during fixed)
5) Callback connection (during designated number) designated number)
8) Callback reception waiting
9) Manual
3 - 30 3 - 30
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3.3.5 I/O signals with the PLC CPU
The I/O signals with the PLC CPU for the modem function are described. See Section
3.8 of User's Manual (Basic) for the I/O signals not related to the modem function.
(1) I/O signal list
X4
X5
X6
X7
X8
X9
XA
XB
XC
XD
XE
XF
Device number
X0
X1
X2
X3
X10
X11
X12
X13
X14
X15
X16
X17
X18
X19
X1A
X1B
X1C
X1D
X1E
X1F
1
Signal description
Device number
CH1 Transmission normal completion ON: Normal completion Y0
CH1 Transmission abnormal completion ON: Abnormal completion Y1
CH1 Transmission processing ON: Transmission in progress
CH1 Reception data read request ON: Requesting read
Y2
Y3
Signal description
CH1 Transmission request ON: Requesting transmission
CH1 Reception data read completion ON: Data read completed
CH1 Mode switching request ON: Requesting switch
CH1 Reception abnormal detection ON: Abnormal detection
(For system)
CH1 Mode switching ON: Switching
CH2 Transmission normal completion ON: Normal completion
Y4
Y5
Y6
Y7
CH2 Transmission abnormal completion ON: Abnormal completion Y8
CH2 Transmission processing ON: Transmission in progress Y9
CH2 Reception data read request ON: Requesting read YA
CH2 Abnormal reception detection ON: Abnormal detection
(For system)
CH2 Mode switching ON: Switching
CH1 ERR occurrence ON: Error occurring
CH2 ERR occurrence ON: Error occurring
YB
YC
YD
YE
YF
(Use prohibited)
CH2 Transmission request ON: Requesting transmission
CH2 Reception data read completion ON: Data read completed
CH2 Mode switching request ON: Requesting switch
(Use prohibited)
Modem initialization completion ON: Initialization completed
Y10
Y11
Y12
1
1
CH1 ERR. information clear request ON: Requesting error clear
CH2 ERR. information clear request ON: Requesting error clear
Modem initialization request (standby request) ON: Requesting initialization
Connection request ON: Requesting connection
1
Modem disconnection request ON: Requesting disconnection
1
Dialing ON: Dial in progress
1
Connection ON: Connection in progress
1
Initialization/connection abnormal completion
ON: Initialization/connection abnormal completed
1
Modem disconnection completion ON: Disconnection completed
1
Notification normal completion ON: Normal completion
1
Notification abnormal completion ON: Abnormal completion
Flash ROM read completion ON: Completed
Flash ROM write completion ON: Completed
Flash ROM system setting write completion ON: Completed
CH1 Global signal ON: Output directed
CH2 Global signal ON: Output directed
System setting default completion ON: Completed
(For system)
Q series C24 ready ON: Accessible
Watchdog timer error (WDT error)
ON: Module error occurred
OFF: Module being normally operated
Y13
Y14
Y15
Y16
Y17
Y18
Y19
Y1A
Y1B
Y1C
Y1D
Y1E
Y1F
1
(Use prohibited)
Notification-issued request OFF: Requesting notification issuance
(Use prohibited)
Flash ROM read request ON: Requesting
Flash ROM write request ON: Requesting
Flash ROM system setting write request ON: Requesting
(Use prohibited)
System setting default request ON: Requesting
(Use prohibited)
The signals shown with are the I/O signals for the modem function.
1 QJ71C24N-R4 cannot be used. (Related to modem function signal.)
• X10 to X16: For system
• Y10 to Y16: Not usable
IMPORTANT
(1) Of the input/output signals to the PLC CPU, the signals marked with "Use prohibited" must not be output (ON).
If any of the "Use prohibited" signals is output, the PLC system may malfunction.
(2) When the modem function is not used or the QJ71C24N-R4 is used, X10 to
X16 are used for the system and Y10 to Y16 cannot be used.
3 - 31 3 - 31
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(2) Function and description of each I/O signal
I/O signal
X10
X11
X12
X13
X14
X15
X16
Y10
Y11
Y12
Y14
Signal name Function/description
Modem initialization completion
Dial in progress
Connection in progress
Initialization/ connection abnormal completion
Indicates normal completion of the Q series C24's initialization of the modem/TA connected to itself according to the initialization data designated.
Indicates that the Q series C24 is dialing (connection processing) the partner side according to the data for connection designated.
1) Indicates normal completion of the line-connection processing from or to the partner side.
2) When this signal is on, data communication with the destination is possible
(notification is not possible).
1) Indicates abnormal completion of the modem/TA initialization or line connection processing (dialing) to the destination.
2) Check the cause of the abnormal completion in the modem-error code storage area
(address: 221
H
) and remove the cause.
Modem disconnection completion
Notification normal completion
Notification abnormal completion
Modem initialization request (standby request)
Connection request
Indicates that the line for data communication with the destination has been disconnected.
Indicates the normal completion when performing the notification processing to the destination.
1) Indicates abnormal completion when the notification processing is performed with the destination.
2) Check the cause of the abnormal completion in the modem error code storage area
(address: 221
H
) and remove the cause.
1) Indicates the initialization request to the modem connected to the local station Q series C24.
2) Turn on the initialization-request signal after designating the initialization data to the buffer memory when it is not set with GX Configurator-SC.
1) Indicates the connection request (dialing) to enable data communication with the destination.
2) Turn on the connection request signal after designating the data for connection to the buffer memory when it is not set with GX Configurator-SC.
3) If the modem/TA connected to the local station is not initialized, the Q series C24side modem is initialized as well prior to dialing, according to the initialization data designated.
Modem disconnection request
Indicates a line-disconnection request from the partner side upon completion of data communication.
Notification-issued request
1) Indicates the notification request to the partner side.
2) Turns on before completing the Q series C24-side modem/TA initialization is complete.
3) Turns off the notification-issued request signal after designating the data for connection in the buffer memory when it is not set with GX Configurator-SC.
Description
Section 3.4.5
Section 3.4.6
Section 3.4.5
Section 3.4.8
Section 3.4.7
Section 3.4.5
Section 3.4.6
Section 3.4.8
Section 3.4.7
POINT
In the descriptions hereafter, I/O signal numbers between QCPU and Q series C24 are indicated assuming that the Q series C24 is installed to slot 0 of the basic base unit.
3 - 32 3 - 32
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3.3.6 Buffer memory
The buffer memory (area shown with ) that can be used with modem function is described.
See Section 3.9 for the buffer memory not related to the modem function.
POINT
The writing and reading of setting values to and from the buffer memory are performed using the special utility package ("GX Configurator-SC") of the Q series
C24.
Perform settings and monitoring according to Chapter 8 of the User's Manual
(Basic). This section provides supplementary explanations on setting values used to perform settings and monitoring with GX Configurator-SC.
Address Dec. (Hex.)
CH1 CH2
0 (0
H
)
1 (1
H
)
2 (2
H
)
3 (3
H
)
4 (4
H
)
5 (5
H
)
6 to 45 (6
H
to 2D
H
)
46 (2E
H
)
47 (2F
H
)
48 (30
H
)
49 (31
H
)
50 (32
H
)
51 (33
H
)
52 (34
H
)
53 (35
H
)
54 (36
H
)
55 (37
H
)
56 (38
H
)
(1) Buffer memory list
Application Name
Default value
Correspondence protocol
MC Non Bi
For LED and communication error clear
Communication error clear request for CH1 and to turn LED off
Communication error clear request for CH2 and to turn LED off
0
For Flash ROM access
For modem functions designation-1
Register/read/delete directions
Frame No. direction
Register/read/delete result storage
Number of data bytes registration designation
User frame
Modem connection channel directions
0: None 1: CH1 2: CH2
Notification execution designation
0: Does not execute
Number of connection retries designation
1 to 5: Number of retries
1: Execute
Connection retry interval designation
90 to 300: Connection retry interval (unit: s)
Initialization/connection timeout designation
1 to 60: Time out (unit: s)
Number of initialization retries designation
1 to 5: Number of retries
Data number for initialization designation
0
H
: Sends initialization data designated by the transmission user frame designation area
7D0
H
to 801F
H
: Data No. for initialization
Data number for connection designation
BB8
H
to 801F
H
: Data number for connection
GX Developer connection designation
0: Does not connect 1: Connects
No-communication interval time designation
0 : Waits infinitely
1 to 120: Non-communication interval time (Line disconnection wait time)
(Unit: min)
RS · CS control yes/no designation
0: Does not control 1: Controls
0
0
3
180
60
3
7D0
H
(2000)
0
30
1
RW
RW
RW
—
3 - 33 3 - 33
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
Address Dec. (Hex.)
CH1 CH2
57 to 143 (39
H
to 8F
H
)
144 (90
H
) 304 (130
H
)
145 (91
H
) 305 (131
H
)
146 (92
H
) 306 (132
H
)
Application Name
Use prohibited System area
For modem switching
Switching mode number designation
Transmission specification designation after switching
Signal setting
( 1)
RS and DTR signal status designation
183 (B7
H
) 343 (157
H
)
184 (B8
H
) 344 (158
H
)
185 (B9
H
) 345 (159
H
)
186 to 285
(BA
H
to
11D
H
)
346 to 445
(15A
544 (220
H
)
H
1BD
H
to
)
545 (221
546 (222
547 (223
H
H
H
)
)
)
548 to 549
(224
550 (226
H
)
551 to 552
(227
H
to 228
553 (229
554 (22A
H
H
)
)
555 to 557
(22B
H
570 (23A
571 to 573
(23B
H
H
to 225
to 22D
:
H
)
H
H
H
to 23D
H
)
)
)
)
574 to 591
(23E
H
to 24F
H
)
Transmission user frame
CR/LF output designation
Output head pointer designation
Output count designation
Flash ROM
For modem function confirmation
Flash ROM system parameters write result
Modem function error code
0 : Normal completion
1 or more: Abnormal completion
(error code)
Modem function sequence status
0: Idle status
1: Waiting for initialization
2: Initializing modem
3: Standby in progress
4: Checking password
5: Communication in progress
6: Notification in progress
7: Modem disconnection
8: Callback Request reception waiting
9: Callback Modem disconnect waiting
10: Callback Delay time waiting
11: Callback Reconnecting
12: Callback Rechecking password
Number of data registrations for connection
0: No registration 1 or more: Number of registration
Data registration status for connection (for conformation of registration No.)
0: No registration 1: Registered
Bits for registration number are 0 (ON)/1 (OFF)
Registration number BB8
H
(3000): Address 224
H
(b0) to
Registration number BD5
H
(3029): Address 225
H
(b13)
Number of data registrations for initialization
0: No registration 1 or more: Number of registration
Data registration status for initialization
0: No registration 1: Registered
Bits for registration number are 0 (ON)/1 (OFF)
Registration number 9C4
H
(2500): Address 227
H
(b0) to
Registration number 9E1
H
(2529): Address 228
H
(b13)
Number of notification executions
0: Not executed
Data storage area 1
1 or more: Number of executions
Notification execution data number
0 : No notification execution
BB8
H
or more: Notification executed (Notification executions number)
Notification status confirmation
System area (Use prohibited)
Data storage area 5
:
Notification execution data number
0 : No notification execution
BB8
H
or more: Notification executed (Notification execution number)
System area (Use prohibited)
Use prohibited
Transmission frame No. designation (A maximum of 100 frames can be designated.)
System area
3072 to 6911
(C00
H
to 1AFF
H
)
For user
User free area (3840 words)
Application is determined by the user.
Default value
Correspondence protocol
MC Non Bi
0
0005
0
0
0
0
0
0
0
H
—
RW
RW
RW
RW
R
R
R
—
R
—
RW
—
3 - 34 3 - 34
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
Address Dec. (Hex.)
CH1 CH2
6912 to 6952
(1B00
H
to 1B28
H
)
(For registration No.
8001
H
)
:
:
8142 to 8182
(1FCE
H
to 1FF6
H
)
(For registration No.
801F
H
)
8183 to 8191
(1FF7
H
to 1FFF
H
)
8192 (2000
H
)
8193 (2001
8194 (2002
H
H
)
)
8195 to 8198
(2003
H
to 2006
H
)
3199 (2007
H
)
8200 (2008
8201 (2009
8202 (200A
8203
(200B
H
)
8204 (200C
8205 (200D
8206 (200E
H
H
H
H
H
H
)
)
)
)
)
)
Application Name
User registration area (Registration No. 8001
H
to 801F
H
)
The user registration area has the following combined uses, with data written by the user according to the purpose of use by the TO instruction, etc.
See each explanation item concerning the configuration of each area, the data written, etc.
For user registration
1) If data communications is being carried out by user registration frame.
• User registration frame (See Chapter 9)
2) If data communications is being carried out by the modem function.
• Initialization Data (See Section 3.4.3)
• Connection Data (See Section 3.4.4)
Use prohibited System area
System designation
For callback function
Flash ROM writing allow/prohibit designation
0: Write prohibited
Callback function designation
0
H
: Auto
1: Write allowed
1
H
: Callback connection (during fixed)··············································(Setting 4)
3
H
: Callback connection (during designated number)······················(Setting 5)
7
H
: Callback connection (during max. designated number is 10)····(Setting 6)
9
H
: Auto/Callback connection (during fixed)·····································(Setting 1)
B
H
: Auto/Callback connection (during designated number)·············(Setting 2)
F
H
: Auto/Callback connection
(during max. designated number is 10)·····································(Setting 3)
Callback denial notification accumulated count designation
0
H
: Not specified
1
H
to FFFF
H
: Notification accumulated number count
Use prohibited System area
For modem function designation-2
Auto modem initialization specification
0: No auto initialization 1: Auto initialization
Modem initialization time DR (DSR) signal valid/invalid designation
0: DR signal is not ignored.
1: DR signal is ignored.
Complete signal handling designation for modem function
0: Does not turn ON/OFF from X13 to X16
1: Turns ON/OFF from X13 to X16
Wait time of notification designation
0
H
: No waiting time
1
H
to FFFF
H
: Wait time of notification (Notification interval time)
(Unit: s)
Use prohibited System area
For remote password function
Remote password mismatch notification count designation
0
H
: No designation
1
H
to FFFF
H
: Count for notification
Remote password mismatch notification accumulated count designation
0
H
: No designation
1
H
to FFFF
H
: Accumulated count for notification
For modem function designation - 3
Circuit disconnect wait time (PLC CPU watch use)
0000
H
to FFF
H
: Wait time (Unit: s)
Default value
Correspondence protocol
MC Non Bi
0
0
0
1
0
1
1
10
0
1
0
RW
RW
RW
RW
RW
RW
—
—
—
—
3 - 35 3 - 35
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
8944 (22F0
H
)
8945 (22F1
H
)
8946 (22F2
H
)
8947 (22F3
H
)
8978 (22F4
H
)
8949 to 8954
(22F5
H
to 22FA
H
)
8955 (22FB
H
)
8956 (22FC
H
)
8957 to 8958
(22FD
H
to 22FE
H
)
8959 (22FF
H
)
9216 (2400
H
)
Address Dec. (Hex.)
CH1 CH2
8207 (200F
H
)
8449 to 8458
(2101
H
to 210A
H
)
9728 to 16383
(2600
H
to 3FFF
H
)
Application
Use prohibited System area
Name
For callback
Function
Data No. for callback designation 1 to 10
BB8
H
to 801F
H
: Data number for callback
For callback function
Callback permit accumulated count
0 or more : Accumulated count
Callback denial accumulated count
0 or more : Accumulated count
Auto (callback) connection permit accumulated count
0 or more : Accumulated count
Auto (callback) connection denial accumulated count
0 or more : Accumulated count
Accumulated count of callback receive procedure cancel
0 or more : Accumulated count
Use prohibited System area
For remote password function
Accumulated count of unlock process normal completion
0 or greater: Accumulated count of normal completion
Accumulated count of unlock process abnormal completion
0 or greater: Accumulated count of abnormal completion
Use prohibited System area
For remote password function
Accumulated count of lock process based on circuit line disconnection
0 or greater: Accumulated count of lock process based on circuit line disconnection
Use prohibited System area
For user ( 1)
User free area 2 (6656 words)
(Communication data monitoring function default buffer)
Usage is determined by the user.
1 Only QJ71C24N (-R2/R4) is usable. (System area when using QJ71C24 (-R2))
Default value
Correspondence protocol
MC Non Bi
0
0
0
0
0
RW
RW
RW
RW
RW
—
—
—
—
IMPORTANT
Do not write data in the system area of the buffer memory.
If data is written in the system area, the PLC system may operate abnormally.
There is also a partial system area in the user's area. Be careful when reading and writing from and to the buffer memory.
POINT
The writing and reading of setting values to and from the buffer memory are performed using the special utility package (GX Configurator-SC) of the Q series
C24.
Perform settings and monitoring according to Chapter 8 of the User's Manual
(Basic). This section provides supplementary explanations on setting values used to perform settings and monitoring with GX Configurator-SC.
3 - 36 3 - 36
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(2) Details of the buffer memory (for modern function)
(a) Modem connection channel designation area (address 46 (2E
H
))
The interface on the Q series C24 side to which a modem/TA is connected is designated.
(b) Notification execution designation area (address 47 (2F
H
))
Whether or not to perform notification (message transmission) to the pager receiver during the fall of the notification-issued request signal Y14 is designated.
(c) Number of connection retries designation area (address 48 (30
H
))
1) Designates the number of retries for the notification/connection request when the connection could not be made to the partner device by the notification request/connection request.
2) The default value is recommended to use for the number of connection retries.
(d) Connection retry interval designation area (address 49 (31
H
))
1) Designates the interval time of the retry processing for the notification/connection request when the connection could not be made to the partner device by the notification request/connection request.
2) The default value is recommended to use for the connection retry interval.
(e) Initialization/connection timeout time designation area (address 50 (32
H
))
1) The following wait times are designated.
• Wait time until the modem/TA initialization is complete.
• Wait time per wait when the connection could not be made to the destination by the notification/connection request.
2) The default value is recommended to use for the initialization/connection retry timeout.
Shown below is the relationship of the number of connection retries designation, connection retry interval designation and the time for initialization/connection timeout time designation used for the notification/connection request to the partner device.
• Number of connection retries : 3 times
• Connection retry interval : 180 s
• Initialization/connection retry timeout: 60 s
Notification
(1st retry)
Notification
(2nd retry)
Notification
(3rd retry)
Notification
60 s 180 s 60 s 180 s 60 s 180 s 60 s
Notification abnormal completion signal X16
Notification-issued request signal X14
Q series C24 ready signal
X1E
(f) Number of initialization retries designation area (address 51 (33
H
))
The number of retries when the initialization per the initialization request to the modem on to the Q series C24 side has failed.
3 - 37 3 - 37
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(g) Data number for initialization designation area (address 52 (34
H
))
1) The registration number for the initialization data transmitted with the initialization request to the modem on the Q series C24 side is designated.
The registration number for the Q series C24 is used.
2) For details on the designation using GX Configurator-SC, see Section
8.4.4 of the User's Manual (Basic). An example of designations using the program is shown in Section 3.4.5.
(h) Data number for connection designation area (address 53 (35
H
))
1) Designates the registration number of the data for connection used by the Q series C24 for the connection processing to the partner device in order to perform data communication/notification.
The registration number for the Q series C24 is used.
2) For details on the designation using GX Configurator-SC, see Section
8.4.4 of the User's Manual (Basic). An example of designations using the program is shown in Section 3.4.6.
(i) GX Developer connection designation area (address 54 (36
H
))
1) Whether to access the PLC from GX Developer by connecting the Q series C24 and GX Developer using the Q series C24 modem function is designated.
2) When connecting the Q series C24 and GX Developer using the Q series C24 modem function, select "personal computer-side interface = via telephone line connection (Q/A6TEL, C24) ". (When connecting direct shown in Section 3.2.3).
When this GX Developer designation is performed, designate "1" in this area on the Q series C24 side.
(j) No-communication interval time designation area (address 55 (37
H
))
1) Designates the wait time until the line is closed when the data communication has ceased with the destination device after the line connection.
2) The Q series C24 automatically performs the line disconnection processing when no data communication is performed with the destination device for a designated time.
(The connection in progress signals (X12) and initialization complete signals (X10) turn off.)
(k) RS · CS control yes/no designation area (address 56 (38
H
))
1) Designates whether to use the RS · CS signals for controls to notify local station-side data reception capability to the partner side during data transmission between the Q series C24 and modem/TA.
2) This setting is for the interface designated by the modem connection channel indicated in (a).
The control of the other interface that does not use the modem function is performed by the settings in the buffer memory DTR/DSR and DC control designation area (address: 93
H
/133
H
).
3 - 38 3 - 38
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
REMARK
The overview of the RS · CS controls are described.
(1) When transmission data
1) The Q series C24 detects the modem/TA data reception capability from on/off of the CS signal.
2) When the CS signal is on, data transmission from the Q series C24 starts or continues.
When the CS signal is off, data transmission from the Q series C24 is interrupted.
(2) When reception data
1) The Q series C24 side reception capability is notified to the modem/TA by the on/off of the RS signal.
2) When the RS signal is on, the Q series C24 can receive data.
Start/continue data transmission from the modem/TA to the Q series
C24.
When the RS signal is off, the Q series C24 cannot receive data.
Cancel data transmission from the modem/TA to the Q series C24.
3) The on/off of the RS signal is controlled by the following conditions of the Q series C24:
• ON OFF control of the RS signal
Performed when the OS area for reception data storage in the Q series C24 becomes 64 bytes (default) or less.
• OFF ON control of the RS signal
Performed when the OS area for reception data storage in the Q series C24 becomes 263 bytes (default) or more.
(l) Modem function error code storage area (address 545 (221
H
))
1) Stores the error code when an error occurs during the modem function or abnormal signal (such as the initialization/connection abnormal completion signal X13) turns on.
2) See Section 10.2 of User's Manual (Basic) for the error codes.
(m) Modem function sequence status storage area (address 546 (222
H
))
1) The current status during use of the modem function is stored as a number.
2) See Section 3.4.1 for storage values for the modem function sequence status when using the modem.
3 - 39 3 - 39
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(n) Number of data registrations for connection storage area (address 547
(223
H
))
1) Stores in Flash ROM the number of registered data for connection used by the Q series C24 for the connection processing with the partner device in order to perform data communication/notification.
The number of registrations is the number of data for connection registered to the Flash ROM by the user.
2) The registration of data for connection is described in Section 3.4.4.
(o) Data registration status for connection storage area (address 548 to 549
(224
H
to 225
H
))
1) Stores in Flash ROM registration status of data for connection used by the Q series C24 in the connection processing with the partner device in order to perform data communication/notification.
2) The registration status of each data for connection with registration numbers of No.BB8
H
to BD5
H
(3000 to 3029) is indicated in the corresponding bit in the range shown in the figure below.
Registration status of data for connection number BB8
H
(3000)
Registration status of data for connection number BC7
H
(3015)
Buffer memory address 548 (224
H
)
549 (225
H
) b15 b14 b13 b12
0 0 to b2 b1 b0
Registration status of data for connection number BD5
H
(3029)
Registration status of data for connection number BC8
H
(3016)
0 (OFF) : No registration
1 (ON) : Registration exists
(p) Number of data registrations for initialization storage area (address 550
(226
H
))
1) Stores in Flash ROM the number of data registrations for initialization, sent to the modem on the Q series C24 side with the initialization request.
The number of registrations indicates the number of data for initialization registered to the Flash ROM by the user.
(q) Data registration status for initialization storage area (address 551 to 552
(227
H
to 228
H
))
1) Stores in Flash ROM registration status for initialization of data for initialization transmitted with the initialization request to the modem on the Q series C24 side.
2) The registration status of each data for initialization with registration numbers of No.9C4
H
to 9E1
H
(2500 to 2529) is indicated in the corresponding bit in the range shown in the figure below.
3) The registration of data for initialization is described in Section 3.4.3.
Registration status of the data for initialization number 9C4
H
(2500)
Registration status of the data for initialization number 9D3
H
(2515)
Buffer memory address
551 (227
H
)
552 (228
H
) b15 b14 b13 b12
0 0
Registration status of the data for initialization number 9E1
H
(2529)
Registration status of the data for connection number 9D4
H
(2516) to to to b2 b1 b0
0 (OFF) : No registration
1(ON) : Registration exists
3 - 40 3 - 40
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(r) Number of notification execution storage area (address 553 (229
H
))
1) Stores the number of execution of the Q series C24 notification
(message transmission) processing for the pager receiver.
2) The storage value when the number of notification execution exceeds
32767 remains at 32767.
3) The value for this area can be changed by the user in the range of 0 to
32767.
When the storage value is changed by the user, the number of execution is stored according to the changed value.
(s) For notification execution data storage: Notification execution data number storage area (address 554, 558... (22A
H
, 22E
H
...))
1) Stores the registration number of the data for connection used in the Q series C24 notification (message transmission) processing to the pager receiver as log information.
2) The latest five data is stored in order at the corresponding areas (data 1, data 2, ....). (The latest information is stored in the data 1 notification execution data number storage area.)
The old notification execution data number other than the latest five are deleted in order.
Buffer memory address 554(22A
H
) b15 to
0
H
, BB8
H
to BD5
H
, 8001
H
to 801F
H
(Data 1) b0
570(23A
H
) 0
H
, BB8
H
to BD5
H
, 8001
H
to 801F
H
(Data 1)
0: Notification not executed
BB8
H
or more: Notification executed
(execution number)
BB8
H
to BD5
H
(3000 to 3029)
(t) For user registration frame registration: Number of bytes in registration data designation area (address 6912, 6953... (1B00
H
, 1B29
H
...))
1) The initialization data or data for connection can be stored into the buffer memory as well as the Q series C24's Flash ROM.
Data type
Initialization data
Data for connection
Registration destination
Flash ROM
Data registered by the OS
User-registered data
Buffer memory
Flash ROM
Buffer memory
(All registered by user)
(All registered by user)
(All registered by user)
Registration number (Decimal (Hex.))
2000 to 2013 (7D0
H
to 7DD
H
)
2500 to 2529 (9C4
H
to 9E1
H
)
–32767 to –32737 (8001
H
to 801F
H
)
3000 to 3029 (BB8
H
to BD5
H
)
–32767 to –32737 (8001
H
to 801F
H
)
A registration number for the initialization data or data for connection to the buffer memory is in the range of -32767 to 32737 (8001
H
to 801F
H
), and determined by the used area.
3 - 41 3 - 41
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
2) In this area, the number of bytes for the initialization data or data for connection (for 1 data) to be registered to the buffer memory is designated.
3) The registration of data for initialization is described in Section 3.4.3.
The registration of data for connection is described in Section 3.4.4.
Buffer memory address 6912 (1B00
H
) b15 to
0 to 78/80 b0
8142 (1FCE
H
) 0 to 78/80 (Number of bytes)
0: No registration data
1 to 78: Registration data exists (for initialization)
80: Registration data exists (for connection)
(u) For user frame registration: User frame designation area (address 6913 to
6952, 6954 to 6993... (1B01
H
to 1B28
H
, 1B2A
H
to 1B51
H
...))
1) When registering the initialization data or data for connection to the buffer memory, the number of registration data bytes (for 1 data) is designated.
2) The registration of data for initialization is described in Section 3.4.3.
The registration of data for connection is described in Section 3.4.4.
Buffer memory address 6913 (1B01
H
) to
6952 (1B28
H
) b15 to
Data for initialization or data for connection
(Area for registration number 8001
H
) b0 to
8143 (1FCF
H
) to
8182 (1FF6
H
)
Data for initialization or data for connection
(Area for registration number 801F
H
)
(v) Auto modem initialization designation area (Address 8199 (2007
H
)
1) This designates whether the Q Series C24 side modem is initialized automatically or not.
2) Registration of this area is done through the GX Configurator-SC. The modem is initialized automatically when the Q Series C24 starts up after the QCPU restarts.
(w) DR (DSR) signal valid/invalid designation area during modem initialization
(address 8200 (2008
H
))
Set this setting to "DR signal valid."
This setting is used to designate how the DR signal is treated when only modem initialization is performed. Following the completion of modem initialization, data is sent according to the status of the DR signal.
(x) Modem function completed signal handling designation area (address 8201
(2009
H
))
Set this setting to "turn ON/OFF X13 to X16" (default value).
(y) Wait time of notification designation area (address 8202 (200A
H
))
1) Designates the waiting time from the moment the present notification is executed until the next notification is executed
(Unit: s), when performing more than one notification continuously.
2) Designates wait time of notification after checking the time required during debugging.
3 - 42 3 - 42
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(z) Circuit disconnect wait time designation area (PLC CPU watch use)
(address 8206 (200E
H
))
1) When sending data using the PLC CPU monitoring function, designates the time it takes to complete data transmission from the local station side modem to the external device after data transmission from the Q series
C24 (wait time until the circuit is disconnected).
2) Specify the circuit disconnect wait time to match the specifications of the modem that is being used.
(3) Details of buffer memory (for the remote password function)
Each of the areas described below is valid when the Q series C24 performs the remote password check.
(a) Remote password mismatch notification count designation area (address
8204 (200C
H
))
1) Use 0 to FFFF
H
to designate the count that will be the notification timing to the QCPU when a remote password mismatch occurs during the user/external device unlock processing after the modem line has been connected.
2) It cannot confirm the accumulated number of times a remote password mismatch occurred up to the present after the line connection.
(b) Remote password mismatch notification accumulated count designation
(address 8205 (200D
H
))
1) Use 0 to FFFF
H
to designate the accumulated count that will be the notification timing to the QCPU when a remote password mismatch occurs during the user/external device unlock processing after the Q series C24 has been started up.
2) The accumulated number of times up to the present a remote password mismatch occurred (accumulated count value in the Q series C24) after starting up can be checked in the area where the accumulated count of unlock process abnormal completion is stored (address 8956 (22FC
H
)).
(c) Storage area for accumulated count of unlock process normal completion
(address 8955 (22FB
H
))
The accumulated number of times the remote password unlock process has been completed normally is stored.
(d) Storage area for accumulated count of unlock process abnormal completion
(address 8956 (22FC
H
))
The accumulated number of times the remote password unlock process has been completed abnormally is stored.
(e) Storage area for accumulated count of lock process based on circuit line disconnection (address 8959 (22FF
H
))
The accumulated number of times the Q series C24 has automatically performed the lock process due to a modem line disconnection is stored.
POINT
Each of the accumulated count values stored in (c) to (e) above are further explained below:
1) The user can clear the values using either of the following:
• Set the accumulated count to "0" using the GX Configurator-SC modem function monitor/test screen.
• Write "0" to the applicable area of the buffer memory.
2) The accumulated count will be stored as 0
H
1
H
2
H
··· FFFF
H
0
H
1
H
···.
3 - 43 3 - 43
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(4) Details of buffer memory (for the callback function)
The areas shown below are valid if the Q Series C24 uses the callback function.
(a) Callback function designation area (Address 8193 (2001
H
))
1) If communications are done by connecting to the GX Developer via a modem, specify whether the callback function is to be used or not. Also specify the callback operation in the case that the callback function is used.
2) This specification becomes valid if "Connection" is entered in the GX
Developer connection designation area (Address 54 (36
H
).
3) Show the setting value (the value stored in this area) in the GX
Configurator-SC and show the corresponding Q Series C24’s callback operation. This becomes invalid if any setting values other than those shown below are specified, and the callback function does not operate.
• When the callback function is not to be used : Auto (0
H
)
• When the callback function is to be used : Setting 1 (9
H
) to setting 6 (7
H
)
Setting 1 (9
H
): Auto/Callback connection (during fixed)
Setting 2 (B
H
): Auto/Callback connection (during designation number)
Setting 3 (F
H
): Auto/Callback connection (during max. designation number is 10))
Setting 4 (1
H
): Callback connection (during fixed)
Setting 5 (3
H
): Callback connection (during designation number)
Setting 6 (7
H
): Callback connection (during max. designation number is 10))
(b) Callback denial notification accumulated count designation area (Address
8194 (2002
H
))
1) Use 0 to FFFF
H
to designate the accumulated count that will be the notification timing to the QCPU when a denial of the callback occurs during access from the GX Developer after the Q series C24 has been started up.
2) The accumulated number of times up to the present a denial of the callback occurred (accumulated count value in the Q series C24) after starting up can be checked in the area where the accumulated count of denial of the callback is stored (address 8945 (22F1
H
)).
(c) Data No. for Callback designation area (Addresses 8449 to 8458 (2101
H
to
210A
H
))
1) This specifies the connection data registration No. where the callback destination GX Developer side’s telephone No. is registered.
Connection data are data that have been registered in the Q Series
C24’s flash ROM or buffer memory.
See Section 3.4.4 for connection data registration.
2) In the following case, the connection data telephone No. specified in callback data No. 1 becomes the callback destination.
• If the callback destination GX Developer is fixed (1 module).
The external line dialing, line types and telephone number in the connection data become valid.
3) In the following cases, when the callback destination telephone No. from the GX Developer is specified and connection made, callback is performed using the external line dialing and line types in the connection data for the registration No. specified in callback data No. 1.
• If it is being made possible to change the callback destination GX
Developer.
• If the maximum number of callback destination GX Developer is limited to 10 modules.
3 - 44 3 - 44
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
4) If the callback destination GX Developer is limited to a maximum of 10 modules, specify the connection data registration No. that specify the callback destination telephone No. for a maximum of 10 modules.
• The external line dialing, line types and telephone number in callback data No. 1 become valid.
• The telephone No. only becomes valid in callback data No. 2 to 10.
The external line dialing and line types in the connection data for callback data No. 1 are used for these.
5) If "0
H
" is specified in this specification, the callback data No. after that become "unspecified."
(Example) If callback data No. 4 is specified as "0
H
," the callback data
No. 4 to 10 registrations become invalid.
(d) Callback permit accumulated count storage area (Address 8944 (22F0
H
))
The accumulated count value when the Q Series C24 executed callback is stored here.
(e) Callback denial accumulated count storage area (Address 8945 (22F1
H
))
The accumulated count value for callbacks which the Q Series C24 did not executed due to callback error detection is stored here.
(f) Auto (callback) connection permit accumulated count storage area (Address
8946 (22F2
H
))
The accumulated count value for normal line connections from the GX
Developer by the connection system shown below is stored here.
1) Auto (callback: during fixed)
2) Auto (callback: during designated number)
(g) Auto (callback) connection denial accumulated count storage area (Address
8947 (22F3
H
))
The accumulated count value for line connections from the GX Developer by the connection system shown below that were not connected normally is stored here.
1) Auto (callback: during fixed)
2) Auto (callback: during designated number)
(h) Accumulated count of callback receive procedure cancel storage area
(Address 8948 (22F4
H
))
The accumulated count value for the number of callback procedures that were terminated from the initial GX Developer by the Q Series C24 when a line connection request by another GX Developer was executed during temporary line disconnect from the GX Developer side through callback specification is stored here.
The Q Series C24 performs the callback operation with respect to the latest connection request.
POINT
Each of the accumulated count values stored in (d) to (h) above are further explained below:
1) The user can clear the values using either of the following:
• Set the accumulated count to "0" using the GX Configurator-SC modem function monitor/test screen.
• Write "0" to the applicable area of the buffer memory.
2) The accumulated count will be stored as 0
H
1
H
2
H
··· FFFF
H
0
H
1
H
···.
3 - 45 3 - 45
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3.3.7 Precautions when using the modem function
Precautions when using the modem function to perform data communication with an external device via public line or call to the pager receiver are described.
(1) Line connection and disconnection
When performing data communication with an external device, it must be predetermined which station is to perform the line connection (dialing) and disconnection processing with the partner device as well as the timings.
(2) Reception data before connection completion
Before the connection processing to the modem is completed the reception data other than modem commands is ignored (read and disposed) at the interface that uses the modem function.
(Example) The Q series C24 will ignore the data even when an MC protocol command message is received.
(3) Transmission control
Delays may occur in transmission controls to notify the data reception capability at the local station to the partner device.
In order not to have a state in which the partner device cannot receive the transmission data, the amount of transmission/reception data and intervals should be determined beforehand.
When transmission/reception data in the non procedure protocol, the procedure must also be predetermined.
(4) Priority of data communication and notification
After line connection is established, the data transmission/reception processing with the partner device is performed in the order of the processing request occurrence.
At the same time, when the line disconnect processing or data transmission reception (including data transmission processing, reception processing and
Flash ROM access processing) occurs, the line disconnect processing has the priority.
(5) Data communication time
The data transmission/reception time after line connection has been established with the partner device is the total time of the transmission time between the Q series C24 and modem/TA, between modem and TA, and between modem/TA and partner device.
When communicating via the MC protocol, the transmission time (such as T0 and
T3) indicated in Chapter 2 of Reference Manual must include the transmission time between the Q series C24-side modem/TA and the destination device.
3 - 46 3 - 46
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(6) Initial Settings
The connection data used for modem functions can be registered as follows using setting procedures.
Set the telephone number and message within the permissible number of registration characters for modem/TA.
1) If registered using GX Configurator-SC
• Comments can be set to a maximum of 256 bytes. (These are not used for control.)
• Telephone numbers can be set to a maximum of 64 bytes.
• Messages can be set to a maximum of 256 bytes.
2) If registered from the PLC CPU (sequence program)
• Comments cannot be set.
• Telephone numbers can be set to a maximum of 18 bytes.
• Messages can be set to a maximum of 30 bytes.
(7) PLC CPU monitoring function
See Section 2.4 for precautions when transmitting monitoring results using the modem function.
(8) Remote password check
(a) How to unlock the remote password
1) When the Q series C24 has been set as a module subject to the remote password check with the QCPU parameter, a remote password unlock processing must be performed from the external device after line connection before starting data communication.
2) The unlock processing for the QCPU remote password is performed as follows:
• When communicating using MC protocol
Perform the unlock processing from the external device using dedicated commands.
• When accessing the PLC from the GX Developer
Perform the unlock processing on the GX Developer screen when access begins.
(b) When the remote password unlock processing is completed abnormally
1) Repeat the unlock processing after checking the remote password set in the QCPU.
2) Start with the line connect processing again if the Q series C24 line connect signal (X12) turns OFF due to the unlock processing abnormal completion.
3) The user should clear the accumulated count stored in the following buffer memory before repeating the line connect processing if the Q series C24 CHn side ERR occurrence signal (XE/XF) turns ON and the
ERR LED lights up due to the unlock processing abnormal completion.
(Applicable buffer memory)
Storage area for accumulated count of unlock process abnormal completion accumulated : Address 8756 (22FC
H
)
(How to clear)
Cleared by the user using one of the following:
• Set the accumulated count to "0" on the GX Configurator-SC modem function monitor/test screen.
• Write "0" to the applicable area of the buffer memory.
3 - 47 3 - 47
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(c) When the number of times remote password mismatch occurs is large
1) When the number of times notification of a remote password mismatch is received exceeds the number of times specified in buffer memory address 8204 (200C
H
), the Q Series C24 disconnects the line automatically. (The connection signal (X12) turns OFF.)
After confirming the remote password registered in the QCPU and the remote password specified in the external device execute line connection again.
2) When the number of times notification of a remote password mismatch is received exceeds the accumulated count value (buffer memory address 8205 (200D
H
)), the Q Series C24 executes the following processing. (The line and modem are not disconnected.)
(when communicating using MC protocol)
• An error code (7FE8
H
) is stored in the buffer memory’s MC protocol transmission error code storage area (address 602/618 (25A
H
/26A
H
).
• The CHn side error occurrence signal (XE/XF) turns ON and the ERR
LED lights up.
(When communicating using the GX Developer)
• An error code (7FE8
H
) is stored in the buffer memory’s modem function error code storage area (address 545 (221
H
).
• The CHn side error occurrence signal (XE/XF) turns ON and the ERR
LED lights up.
3) The accumulated number of times up to the present a remote password mismatch occurred (accumulated count value in the Q series C24) can be checked in the area where the accumulated count of unlock process abnormal completion is stored (address 8956 (22FC
H
)).
4) The user should clear the accumulated number of times up to the present a remote password mismatch occurred using one of the following methods.
• Set the accumulated count of unlock processing abnormal completion to "0" on the GX Configurator-SC's modem function monitor/test screen.
• Write "0" in the buffer memory area where the accumulated count of unlock process abnormal completion is stored (address 8956
(22FC
H
)).
POINT
If the CHn side ERR occurrence signal (XE/XF) for the Q series C24 turns ON and the ERR LED lights up, this could indicate improper access from the external device.
See also an example of measures taken on the PLC CPU side described in (12).
REMARK
See Section 10.1.2 of User's Manual (Basic) on how to turn off the Q series C24
ERR LED after it has lit up.
3 - 48 3 - 48
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(9) Number of modules for which the remote password check can be set
A maximum of eight modules can be registered with remote passwords in the
QCPU.
1
To set the remote password in a module, use the GX Developer remote password setting screen.
1 The remote password modules are as follows:
• Q series C24
• Q series Ethernet module
(10) Callback Function
(a) When the number of callback processing denials exceeds callback denial notification accumulated count (buffer memory address 8194 (2002
H
), the following processing is executed each time the Q Series C24 issues another refusal.
• An error code (7FE9
H
) is stored in the buffer memory's modem function error code storage area (address 545 (221
H
).
• The CHn side error occurrence signal (XE/XF) turns ON and the ERR
LED lights up.
(b) When the number of callback processing refusals exceeds callback denial notification accumulated count, after performing the following checks and clearing processing, make the line connection again from the GX
Developer.
• Check the setting contents of the callback function set in the Q Series
C24.
• Check the setting contents of the callback function set in the GX
Developer.
• The user should clear the accumulated counts stored in the following buffer memory areas.
(Affected buffer memory)
Callback denial accumulted count: Address 8945 (22F1
H
)
(Clearing method) ···The user should clear this area by either of the following methods.
• Set the accumulated count value in the GX Configurator-SC's modem function monitoring / test screen to "0."
• Write "0" to the affected storage area in the buffer memory.
REMARK
See Section 10.1.2 of the User's Manual (Basic) for the method for turning off the Q
Series C24's ERR LED when it lights up.
3 - 49 3 - 49
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(11) Preventing a line disconnect when the GX Developer is connected
Perform the following settings and operations to prevent a line to the modem from disconnecting even if communication between the GX Developer and PLC is interrupted.
(a) Initial setting using the GX Configurator-SC (See Section 8.4.4 of User's
Manual (Basic).)
1) Setting screen: Modem function system setting screen
2) Setting item: No-communication interval time designation
3) Setting value: 0 (infinite wait)
(b) Operation using the GX Developer
Always perform the line disconnect operation when the GX Developer online operation is completed after the line to the Q series C24 side is connected.
(12) An example of what to do on the PLC CPU side for improper access from the external device
The following is an example of performing, on the PLC CPU side, the line disconnect processing with respect to the opposite device and prohibiting receive via a modem when the number of "remote password mismatch" detected by the
Q series C24 remote password check function exceeds the number set by the user.
1) The user should determine the count and accumulated count of notification given when a remote password mismatch occurs during the unlock processing from the external device with respect to the remote password set in the QCPU. (See Section 3.3.6 (3) (a) and (b).)
2) In the GX Configurator-SC system settings, in order for the Q series C24 to operate, set the count determined above in the following item on the "Modem function system setting" screen and register this to the Q series C24. (See
Section 8.4.4 of User's Manual (Basic).)
• Set in the item "Remote password mismatch notification count."
• Set in the item "Remote password mismatch notification accumulated count."
3) In addition to initialization commands used in normal modem initialization, specify "No automatic receive" and additionally register the modem initialization command for this step to the Q series C24. (No automatic receive: This is the setting to prohibit line connection from the opposite device.) Use the "Modem function initialization data" screen to set. (See
Section 8.4.2 of User's Manual (Basic).)
4) Constantly monitor the rise (OFF ON) of the ERR occurrence signal (XE or
XF) when connecting the line to the opposite device using the modem function after the system begins operating.
5) Monitor the following buffer memory when the ERR occurrence signal turns
ON.
Storage area for MC protocol transmission error codes (address: 602 (25A
H
))
6) Perform the line disconnect processing with respect to the opposite device when the error code stored in the above buffer memory is 7FE8
H
.
(Use the modem disconnection request signal (Y12).)
7) After the above line disconnect processing is completed, specify the modem initialization command for which "No automatic receive" has been specified and perform modem initialization only. (See Section 3.4.7.)
8) Describe the above occurrence to the system manager and take necessary measures.
3 - 50 3 - 50
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(Example) When the number of times a remote password mismatch occurred exceeds the notification accumulated count setting value during the remote password unlock processing in communication using MC protocol with the Q series C24 CH1 side interface used.
Access enabled flag is turned ON
Register initialization data for
"No automatic receive" to the buffer memory
CH1 side ERR occurrence is detected
Read the CH1-side error code
If the error code indicates that the accumulated count of remote password mismatch is exceeded, the modem disconnect request signal is set
Modem disconnection completed
When the modem disconnection completed signal turns
OFF, the No. for the modem initialization data
(for "No automatic receive") is specified and initialization requested
The modem initialization data setting flag is set
The modem initialization normal completion flag is set
The modem initialization request signal is reset
Error code is read if the modem initialization completes abnormally
The modem initialization ERR occurrence flag is set
The modem initialization request signal is reset
The unlock processing accumulated count is cleared
The modem initialization processing normal completion flag is set
An instruction from the user resets the flag
3 - 51 3 - 51
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3.4 Start-up of the Modem Function
This section explains the start-up procedures, processing methods and programming when the modem function of the Q series C24 is to be used.
3.4.1 Start-up procedures when communicating data with external devices
This section shows the procedure for starting the modem function and up to the point when data communications is started.
(1) Procedure up to initialization of the Q Series C24's modem / TA
This initializes the modem / TA connected to the Q Series C24 in order to use the modem function. It becomes possible to carry out all kinds of communications when the modem / TA is initialized.
Parameter setting of the Q series C24 to QCPU
Initial setting of Q series C24
(Setting with
GX Configuration-SC)
Start
• Determine the configuration of the system
• Verify the Q series C24 specification
• Installation to the base unit
• Suppling power to the Q series C24 loading
station
Individual testing of the Q series C24
Connecting the Q series C24 and modem/TA
.....
See Section 4.7 of User's Manual (Basic)
After inidividual station testing, turn off the power
supply to the Q series C24 loading station
.....
After setting the modem/TA switch, connect to modem/TA using the included RS-232 cable or any designated cables
• Suppling power to the modem/TA
• Supplying power to the Q series C24 loading
station
.....
Supply power from the modem/TA
Setting and registration with GX Developer
• Switch setting of Q series C24
Registration to QCPU (Write to PLC)
.....
Transmission setting
(Other than operation setting (OFF) should be set accordingly with the modem/TA)
Stasion number setting (set to 0 to 31)
See Section 4.5 of User's Manual (Basic)
Initial setting of Q series C24
Registration of the data for initialization
Registration of data for connection
.....
See Section 3.4.2 for setting the modem functions
See Section 8.4.4 of User's Manual (Basic)
.....
See Sections 3.4.3, 8.4.2 of User's Manual (Basic)
.....
See Sections 3.4.4, 8.4.3 of User's Manual (Basic)
Initialization of the modem/TA
(modem function system setting)
.....
See Sections 3.4.5, 8.4.4 of User's Manual (Basic)
(2) In case of data
communication
(3) In case of notification (4) Access from GX Developer
to QCPU
3 - 52 3 - 52
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
Line connection wait side
(2) Procedure when executing data communications indicates processing performed by the user.
Line Connection Side
Perform the processing up to the point where the modem/TA is initialized by the procedure in (1).
Q Series C24
0
1
Modem initialization
2
Line connection wait state
Modem initialization completion signal (X10 = ON)
3
Line connection completed normally.
Connection in progress signal (X12)=ON
Execute data communications.
Modem Modem
Line Connection
(See Section 3.4.6.)
Q Series C24 or
External Device
Perform the processing up to the point where the modem/TA is initialized by the procedure in (1).
Modem initialization
Modem initialization completion signal
(X10)=ON
Execute line connection.
Connection request signal (Y11)=ON
Line connection completed normally.
Connection in progress signal (X12)=ON
Execute data communications.
5
Remote password unlock processing
(See Section 3.3.3 and the Reference Manual,
Section 3.18.)
Data communications
(See Section 3.4.7.)
If communications are carried out using an external device and the MC protocol, when a remote password is set in the QCPU, unlock processing with respect to the remote password is executed.
Line disconnect completed
Connection in progress signal (X12)=OFF
Line disconnect
(See Section 3.4.8.)
Remote password lock processing
The line is disconnected after data communications are completed.
Modem disconnection request signal (Y12)=ON
Line disconnect completed
Modem disconnection completion signal (X14)=ON
Connection in progress signal (X12)=OFF
Modem initialization completion signal (X10)=OFF
By completing the line disconnection, lock processing of the remote password is executed automatically.
Line connection wait state
Modem initialization completion signal (X10)=ON
If data communications is being executed again, carry out communications after line connection from the external device.
3
Shows the value stored for the modem function sequence status (Address 546 (221
H
)).
If data communications are executed again, proceed from the modem initialization stage.
3 - 53 3 - 53
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(3) If notification is made
Pager receiver Modem indicates processing performed by the user.
Q Series C24 (Line connection side)
0
1
(1) Perform the processing up to the point where the modem/TA is initialized by the procedure in (1).
Modem initialization
2
Modem initialization completion signal
(X10)=ON.
3
Make notification
Line connection
Line connection normally completed
Notification
(See Section 3.4.7.)
Notification-issued request signal (Y14)=OFF
Line connection normally completed
Connection in progress signal (X12)=ON
Notification data reception
Line disconnect completed
Line disconnect
6
3
Line disconnect completed
Notification-issued request (Y14)=ON
Modem initialization completion signal
(X10)=ON
Shows the value stored for the modem function sequence status (address 546 (221
H
))
(4) If accessing the QCPU from the GX Developer
Q Series C24
Perform the processing up to the point where the modem/TA is initialized by the procedure in (1).
0
1
Modem initialization
2
Line connection wait state
Modem initialization completion signal (X10) = ON
3
Modem Modem
Line connection indicates processing performed by the user
GX Developer (Line connection side)
Initialize the personal computer side modem.
Registration of the modem connected to the personal computer
Registration complete
Execute line connection.
Line connection normal response
Connection in progress signal (X12)=ON
Connect to the line after setting the necessary items in the line connection screen.
Line connection normal response
Password check (for the system)
Normal response
4
Remote password check (See Section 3.3.3.)
If the callback function is used (See Section 3.3.4.)
When setting the remote password in the QCPU, the remote password input dialog box is displayed
Access to the QCPU
Access to the QCPU.
5
Execute line disconnect.
Line Disconnect
Line disconnect processing by the line disconnect screen
Line disconnect response
Line disconnect response
Connection in progress signal (X12)=OFF
Line connection wait state
Modem initialization completion signal (X10)=ON
3
Shows the value stored for the modem function sequence status
(address 546 (221
H
))
3 - 54 3 - 54
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3.4.2 Initial settings of the serial communication module
This section explains the initial settings of the Q series C24 when data communicating with external device, remotely notifying a pager receiver and accessing from GX
Developer using the modem function.
(1) Switch settings by GX Developer
Switch setting by GX Developer
Communication protocol setting
Operation setting
Data bit setting
Parity/non-parity setting
Transmission specification communication rate setting
Even/odd parity setting
Stop bit setting
Sum check enable/disable setting
Write during RUN enable/disable setting
Setting modification enable/disable setting
Transmission rate setting
Station number setting
Data communication
1 to 7
Notification
1 to 7
GX Developer
OFF (Independent operation) access
5
(Set according to modem/
TA on local station)
ON
OFF
OFF
OFF
(Set according to system specification)
OFF/ON
OFF/ON
OFF/ON
ON
ON
OFF/ON
(Set according to modem/TA on local station) (
00 to 31
1
)
Remarks
—
Set both CH1 and CH2 OFF
OFF=7 bits, ON=8 bits
OFF = Non-parity, ON = Parity
OFF = Odd, ON = Even
OFF = 1 bit, ON = 2 bits
OFF = Disabled, ON = Enabled
OFF = Disabled, ON = Enabled
OFF = Disabled, ON = Enabled
(bps)
—
1 When the first five digits of the serial No. are 03042 or earlier, the transmission speed cannot be set to
115200 bps for connection between the Q series C24 and the GX Developer via a modem.
REMARK
This gives an example of the switch setting when the modem function is used to connect the GX Developer to the Q series C24 CH1 side and the PLC is accessed.
Perform the switch setting similar to this example also when performing data communication or notification.
(See Section 4.5.2 of User's Manual (Basic) for more detail on switch setting.)
[Start procedure]
"GX Developer" "PLC parameters" "I/O assignment setting" Switch setting
[Setting example]
3 - 55 3 - 55
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
Switch number
Switch 1
Switch 2
Switch 5
Bit
Position b0 b1 b2 b3 b4 b5 b6 b7 b8 to b15
―
―
Specified value
OFF
ON
OFF
OFF
OFF
ON
ON
ON
―
Description
CH1 transmission setting
Operation setting
Data bit
Parity bit
Odd/even parity
Stop bit
Sum check code
Write during RUN
Setting modification
CH1 communication rate setting
CH1 communication protocol setting
Station number setting
Independent
8 bits
No
Odd
1 bit
Yes
Allowed
Enable
19200 bps
5
0th station
Setting value
07E2
0005
0000
(2) Initial settings by GX Configurator-SC (set in the setting screen for modem function system)
(a) Perform initial settings on the interface side that use the modem function as described in Section 3.3.6:
The following table shows the default settings in the “Modem function system setting" screen and whether setting is possible or impossible in each type of communications.
"Modem function system setting" screen setting item
Data communications
(MC non procedure, bidirectional)
Notification GX Developer Buffer memory address
Modem connection channel designation
Notification execution designation
Number of connection retries
Connection retry interval designation (unit: s)
Initialization/connection timeout time designation (Unit: s)
Number of initialization retries designation
Data No. for initialization designation (
1
)
Data No. for connection designation (
1
)
GX Developer connection designation
No-communication interval time designation (
2
)
RS · CS control yes/no designation
Modem initialization time DR signal valid/invalid designation (
3
)
Wait time of notification (Unit: s)
Circuit disconnect wait time (PLC CPU watch use) Unit: s
Remote password mismatch notification count designation
Remote password mismatch notification accumulated count designation
Auto modem initialization designation
Callback function designation
Callback denial notification accumulated count designation
Data No. for Callback designation 1 to 10
46 (2E
H
)
47 (2F
H
)
48 (30
H
)
49 (31
H
)
50 (32
H
)
51 (33
H
)
52 (34
H
)
53 (35
H
)
54 (36
H
)
55 (37
H
)
56 (38
H
)
8200 (2008
H
)
8202 (200A
H
)
8206 (200E
H
)
8204 (200C
H
)
8205 (200D
H
)
8199 (2007
H
)
8193 (2001
H
)
8194 (2002
H
)
8449 to 8458
(2101
H to 210A
H
)
: Required item : Setting possible : Setting not required
1 For details on how to register the data No. for initialization, see Section
3.4.3. For details on how to register the data No. for connection, see
Section 3.4.4.
2 Even if the PLC CPU on the Q series C24 loading station (local station) becomes STOP status under the following circumstances, the line
(telephone) with the partner devices will be left connected. In order to prevent the line from being left connected when the line is not in use, be sure to make the appropriate settings.
3 - 56 3 - 56
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
1) When the PLC CPU is stopped when the connected signal (X12) is at the ON status.
This occurs because the program write after remote stop is enabled.
2) When the PLC CPU performs an error stop during self-diagnosis, etc.
POINT
When setting the No-communication interval time as infinite wait (set value = 0), be sure to perform line disconnection processing after the data has been communicated.
If the line is left connected for long periods of time without performing line disconnection after data has been communicated, not only will telephone bills be applied, but it may violate electronic communication business laws.
3 The "Modem initialization time DR signal valid/invalid designation" designates whether the status of the DR signal output is valid or invalid at the startup of the Q series C24 .
When the DR signal = ON is output from the modem, register "valid" for this item.
When the DR signal = ON is not output from the modem, register
"invalid" for this item.
(b) All transmissions using the modem function are transmitted in full-duplex.
Leave the following initial settings for the interface side that uses the modem function as default.
1) CD terminal check
2) Communication system
(Default value)
: Not checked
: Full-duplex communication
(c) The processes that correspond to the following output signals may not be aborted.
Output signal Requesting process name
Y10
Y11
Y12
Initialization request (standby request)
Connection request
Disconnection request
Y14 Notification-issued request
It is recommended to leave the following initial settings for the modem functions as default. (Upon error, it will end due to time out.)
1) Number of connection retries
2) Connection retry intervals
(Default value)
: 3 times
: 180 s
3) Initialization/connection time out : 60 s
POINT
Also perform the settings for a remote password check described in Section 3.3.5
(3) (a) and (b) when a remote password check is executed with respect to the remote password set in the QCPU.
3 - 57 3 - 57
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3.4.3 Register/read/delete of the initialization data
The section explains the register/read/delete of the data for initialization such as initialization commands for the modem/TA connected to the Q series C24 side for data communication with the external device, pager receiver notification and accessing from
GX Developer using the modem functions.
(1) Registration destination of the data for initialization
1) The data for initialization may be used by registering to the Q series C24
Flash ROM or buffer memory.
2) The buffer memory may register the data for connection shown in Section
3.4.4 and will register the data for initialization or data for connection in the designated area.
3) It is recommended that the data for initialization during the debug process is stored in the buffer memory. The registration data in the buffer memory will be erased after starting up the Q series C24 loading station again. It is necessary to register the data for initialization in the buffer memory after each start-up of the Q series C24.
4) It is recommended to store the data for initialization to the Flash ROM after completing the debug process.
By registering it to the Flash ROM, the registration process of the data for initialization will be unnecessary thereafter.
(2) Types of data for initialization
1) There are data for initialization that are registered in the Flash ROM of the Q series C24 upon shipping and data for initialization that are set by the user.
2) The number of times registered/number of possible registrations are shown in the chart below.
(3) Data for initialization registration number
1) The registration numbers shown in the table below are used from the memory of the registration destination.
2) The registration number of the data for initialization is determined by the area of registration.
Registration data
Data for initialization
Flash ROM
Registration destination
Buffer memory
Data registered by the OS
Data registered by the user
(All are set by the user)
Registration number (Decimal (hexadecimal))
2000 to 2013 (7D0
H
to 7DD
H
)
2500 to 2529 (9C4
H
to 9E1
H
)
–32767 to –32737 (8001
H
to 801F
H
)
Number of registrations
13
30
31
(4) Precautions during the registration of data for initialization
1) The maximum size of the initialization commands that may be registered as one data for initialization is 78 bytes
2) Do not include CR/LF (data code : 0D
H
/0A
H
) in the data for initialization to be registered to the Q series C24. The CR/LF is output at the end of the AT command by the Q series C24 when processing initialization (automatically added).
3) The registration status of the data for initialization stored in the Flash ROM may be checked in "data registration for modem initialization" screen for GX
Configurator-SC or the buffer memory (address : 226
H
to 228
H
(550 to 552).
When newly registering, register by designating an unregistered number.
3 - 58 3 - 58
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
When designating a registration number that has already been registered, first delete the registration data in the preoccupied registration number prior to registration.
4) When connecting the Q series C24 to an external device using a cellular phone and a modem, set the transmission rate supported by the cellular communication module on the modem side.
(5) Registration contents at shipment
1) The data for initialization registered in the Flash ROM of the Q series C24 are shown below:
Registration number
Hexadecimal Decimal
7D0
H
7D1
H
7D2
H
7D3
H
7D4
H
7D5
H
7D6
H
7D7
H
7D8
H
7D9
H
7DA
H
7DC
H
7DD
H
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2012
2013
Initialization command
ATQ0V1E1X1\J0\Q2\V2\N3S0=1
ATQ0V1E1X1\Q2\V2\N3S0=1
ATQ0V1E1X1&K3\N3S0=1
ATQ0V1E1X1&H1&R2&A3&D2S0=1
ATQ0V1E1X1\J0\Q2\N3S0=1
ATE1Q0V1&C1&D2&H1&I0&R2&S0S0=1
ATE1Q0V1&C1&D2&K3&S0S0=1
ATE1Q0V1&C1&D2&K3&S1S0=1
ATE1Q0V1&C1&D2&K3&S0S0=1
ATE1Q0V1&C1&D1&Q2&S0S0=1
ATE1Q0V1&C1&D2&Q3&S0S0=1
AT&S0S0=1
ATX1&S0S0=1
2) If initialization commands other than listed above are needed, the data for initialization needs to be registered to the Flash ROM or the buffer memory of the Q series C24.
REMARK
• Perform the following setting in respect to the modem/TA connected to the Q series C24 side.
For settings other than listed below, perform the setting as designated by the modem/TA.
Setting contents
—
Display the result code (or, return the result code).
Set the result code as a word.
Perform character echo.
Dial tone and busy tone detection + X1
Set register 0 at 2
The modem and the serial speed are not equal.
Control RTS/CTS.
Control DSR.
Control DTR.
Enable extension result code (display MNP class).
MNP mode/normal mode auto selection
Setting command example
AT
Qn
Vn
En
Xn
Sr=n
\Jn
\Qn
&Sn
&Dn
\Vn
\N3
• The following shows an specification example of the transmission rate supported by the cellular communication module using the modem initialization command, when connecting the Q series C24 to an external device using a cellular phone and a modem. (Transmission rate = 9600 bps is set)
For the details, see the manual of the modem used.
(Setting example for the initialization command of the registration No.7D3
H
)
ATQ0V1E1X1&H1&R2&A3&D0S0=1&N6
(Setting example for the initialization command of the registration No.7D4
H
)
ATQ0V1E1X1\J0\Q2\N3&D0+MS=, 9600, 9600S0=1
3 - 59 3 - 59
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(6) Procedures for register/read/delete of the initialization data
(a) For the Flash ROM in the Q series C24
1) Register/read/delete operations are executed on the GX Configurator-
SC's "Data registration for modem initialization" screen.
2) Display and operate the screen according to Section 8.4.2 of the User's
Manual (Basic).
The factory setting of initialization data stored in the Flash ROM of the Q series C24 cannot be deleted.
(Registration example)
REMARK
Use \\ code to specify a field to register "\" if GX Configurator-SC is used for data for modem initialization.
(Example) To register the \Q2 of data: \\Q2
3 - 60 3 - 60
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
Address
Hexadecimal Decimal
1B00
H
1B01
H
1B02
H
to
1B28
H
1B29
H
1B2A
H
1B2B
H
to
1B51
H
6912
6913
6914 to 6952
6953
6954
6955 to 6993
(b) For the buffer memory of the Q series C24
1) The initialization data write (registration) and read operations are performed by designating an applicable area that corresponds to registration numbers 8001
H
to 801F
H
for the user frame registration area
(addresses: 1B00
H
to 1FF6
H
).
When deleting the initialization data, write "0" to the number of registration data bytes designation area.
2) The table below shows an overview of the buffer memory used in the write, read, and delete operations of the initialization data as well as the designated values for each area.
For more details, see Chapter 9.
(Use the table by replacing the user frame with the initialization data.)
Name Designated/stored value
Specification required ( )/not required ( )
Write Read Delete
Registration
No.8001
H
Registration
No. 8002
H
Registration data byte number designation
User controlled data
Initialization command
Registration data byte number designation
User controlled data
Initialization command
0 : When deleting
1 to 78: Number of bytes in the registration data
(Only for the initialization command section)
Any data used by the user to manage the registration data (manufacturer code, control number, etc.)
Data code for the initialization command for registration
0 : When deleting
1 to 78: Number of bytes in the registration data
(Only for the initialization command section)
Any data used by the user to manage the registration data (manufacturer code, control number, etc.)
Data code for the initialization command for registration
(Read processing not required)
(Read processing not required)
1FCE
H
1FCF
H
1FD0
H
to
1FF6
H
8142
8143
8144 to 8182
Registration
No. 801F
H
Registration data byte number designation
User controlled data
Initialization command
0 : When deleting
1 to 78: Number of bytes in the registration data
(Only for the initialization command section)
Any data used by the user to manage the registration data (manufacturer code, control number, etc.)
Data code for the initialization command for registration
(Read processing not required)
3) The contents of the data to be written into the designated area that corresponds to registration numbers 8001
H
to 801F
H
are the same as those for the Flash ROM.
3 - 61 3 - 61
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(Item name)
4) The following shows an example of a sequence program used to write the initialization data (registration).
• Example of writing the initialization data to the area having registration number 8001
H
X1E: Q series C24 ready signal
X1F: WDT error signal
Turns the ready flag ON
Data registration for initialization instruction
Sets the number of registration data bytes
Sets the user control data
(control number)
Sets the AT command for initialization
Data register
Number of registration data bytes
User control data
Initialization command
D0
D1
D2 to
D13
30
1
Initialization command
(Address)
1B00
H
1B01
H
1B02
H to
1B0D
H to
1B28
H
Sets the AT command for initialization to the buffer memory
Sets the initialization completed flag
Buffer memory
Area for registration
No. 8001
H
30
1
Data for initialization
Initialization command
3 - 62 3 - 62
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3.4.4 Register/read/delete of the data for connection
This section explains the registration/reading/deletion of data for connection such as the telephone number of the partner device and notification messages that are used for communicating data with external devices, notify pager receivers and accessing from GX Developer using the modem functions.
(1) Registration destination of data for connection
1) The data for connection can be used by registering to the Q series C24's
Flash ROM or buffer memory.
2) The buffer memory can register the data for initialization shown in Section
3.4.3. The data for initialization or data for connection will be registered in the applicable area.
3) It is recommended to store the data for connection during the debug process in the buffer memory. The registration data in the buffer memory will be erased after the starting up the Q series C24 loading station again. It is necessary to register the data for connection in the buffer memory after each start-up of the Q series C24.
4) It is recommended to store the data for connection to the Flash ROM after completing the debug process.
By registering it to the Flash ROM, the registration process of the data for connection will be unnecessary thereafter.
(2) Types of data for connection
1) All data for connection are registered and used as defined by the user.
2) The number of possible registrations are shown in the table below.
(3) Data for connection registration number
1) The registration numbers shown in the table below are used by the memory of the registration destination.
2) The registration number of the data-for-connection is determined by the area of registration.
Registration data
Data for connection
Registration destination
Flash ROM
Buffer memory
(All are set by user)
Registration number (Decimal (hexadecimal))
3000 to 3029 (BB8
H
to BD5
H
)
–32767 to –32737 (8001
H
to 801F
H
)
Number of registrations
30
31
(4) Precautions during the registration of data for connection
1) The maximum size of data that can be registered as one data for connection is
80 bytes. Do not deviate from the following data sizes for the following items:
Message area for notification = 36 bytes, data-for-connection area = 44 bytes
2) Designate the messages for notification accordingly with the display designation of the partner devices.
3) The registration status of the data for initialization stored in the Flash ROM can be checked in "data registration for modem connection" screen for GX
Configurator-SC or the buffer memory (address : 223
H
to 225
H
(547 to 549)
When newly registering, register by designating an unregistered number.
When designating a number which is already registered, delete the registered data for that number first, then perform the registration.
3 - 63 3 - 63
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(5) Procedures for register/read/delete of the data for connection
(a) For the flash ROM in the Q series C24
1) Register/read/delete operations are executed on the GX Configurator-
SC's "Data for modem connection" screen.
2) Display and operate the screen according to Section 8.4.3 of the User's
Manual (Basic).
3) Set the required items with the table below.
"Data for modem connection" screen setting item
Data communication
(MC, non procedure, bidirections)
Notification GX Developer
Data for modem connection 1 to
30
Pager receiver designation
Telephone number
External line dialing
Line types
Wait time for message transmission unit: s
Message
Comment
(for callback)
(for callback)
(for callback)
: Required item : Setting possible : Setting not required
(Registration example) Setting example to perform data communication
3 - 64 3 - 64
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(b) For the buffer memory of the Q series C24
1) The connection data write (registration) and read operations are performed by designating an applicable area that corresponds to registration numbers 8001
H
to 801F
H
for the user frame registration area
(addresses: 1B00
H
to 1FF6
H
).
When deleting the connection data, write "0" to the number of registration data bytes designation area.
2) The table below shows an overview of the buffer memory used in the write, read, and delete operations of the connection data as well as the designated values for each area are.
For more details, see Chapter 9.
(Use the table by replacing the user frame with the connection data.)
Specification required ( )/not required ( )
Write Read Delete
Address
Hexadecimal Decimal
1B00
1B01
1B28
1B29
1B2A
H
H
1B51
H
to
H
H
to
H
Name Designated/stored value
6912
6913 to 6952
6953
6954 to 6993
Registration
No.8001
H
Registration
No.8002
H
Registration data byte number designation
0 : When deleting
80: Number of registration data bytes
Connection data
Notification message for connection data to be registered, and connection data
Registration data byte number designation
0 : When deleting
80: Number of registration data bytes
Connection data
Notification message for connection data to be registered, and connection data
(Read processing not required)
(Read processing not required)
1FCE
H
1FCF
H
to
1FF6
H
8142
8143 to 8182
Registration
No.801F
H
Registration data byte number designation
0 : When deleting
80: Number of registration data bytes
Connection data
Notification message for connection data to be registered, and connection data
(Read processing not required)
3) The following shows the data arrangement of the connection area data
(area corresponding to registration numbers 8001
H
to 801F
H
) in the buffer memory that is used for the register, read and delete operations of the connection data, as well as the designated values and stored values.
Data for connection
(H)
Message area for notification (36 bytes) Connection data area (44 bytes)
(L)
Message (30)
Message length (2)
(Open) (2)
Pager receiver designation (2)
Telephone number (18)
External line dialing (2)
Line types (2)
(Open) (20)
Wait time for Message transmission (2)
(Data name (number of bytes))
3 - 65 3 - 65
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(Data for connection area) … 44 bytes
Data name
Pager receiver designation
Telephone number
External line dialing number
Line type
(Open)
Designated/stored value and contents
Whether or not notification is performed, and the notification target module are designated.
0 : No notification
3 : Notification performed
In the case of 3 above, the wait time for message transmission in the notification message must be designated.
• The other party's phone number used to establish line connection when communicating data or performing notification is designated.
• When phone number is less than 18 characters, a space (code:
20
H
) must be entered for the remainder.
The external-line access number on Q series C24 side when performing data communication/notification to the partner device is designated.
0 to 9
10( ) : External-line access number on the Q series C24 side
11(#)
255 : No external-line access number required on the Q series
C24 side
The line type used to perform data communication/notification with the partner device is designated.
0 : Pulse
1 : Tone
2 : ISDN
Designate "0" .
Number of bytes
2
18
2
2
20
Data type
Binary
ASCII
Binary
Binary
Binary
Data name
Wait time for message transmission
Message
Message length
(Open)
(Notifying message area) … 36 bytes (Designated when performing notification)
Designated/stored value and contents
The wait time after line connection until message transmission is designated. (Unit: s)
0 to 255 : Wait time
Valid when the pager receiver designation in data connection is "3".
Designate the notification message according to the display specification on the other party's device.
The number of designated message bytes shown above is designated.
0 : No message designation
1 to 30 : Number of message bytes
Designate "0".
Number of bytes
2
30
2
2
Data type
Binary
Binary
Binary
Binary
3 - 66 3 - 66
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(4) An example of a sequence program used for writing (registering) of data for connection is shown below.
• Example of writing data for connection to the registration number 8002
H
area
X1E: ready signal
X1F: WDT error signal
Turns the ready flag ON.
Connection data registration command
Set the number of registration data bytes
Clear the data storage device for connection
Set the pager receiver designation
(Notification is not executed)
Set the telephone number to be connected
(Item name)
Number of registration data bytes
Data for connection
D0
D1 to
D22
D23 to
D40
Data register
80
(Connection data)
(Data for notification)
Set the external line dialing number (0)
Sets the line type to tone.
Writes the connection data in the buffer memory.
Sets the connection data registration completion flag.
(Address)
1B29
H
1B2A
H to
1B3F
H
1B40
H to
1B51
H
Buffer memory
Area for registration
No. 8002
H
80
(Connection data)
(Data for notification)
3 - 67 3 - 67
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3.4.5 Initialization of modem/terminal adapter
This section explains the initialization of the modem/TA connected to the Q series C24, used for communicating data with the external device, performing notifications to pager receivers and accessing from GX Developer using the modem function.
(1) Requirements for initialization
Perform the following setting and registration:
1) The Q series C24 initial settings as shown in Section 3.4.2.
2) The data for initialization registration shown in Section 3.4.3, when initializing the modem/TA with the data for initialization set by the user.
REMARK
It is possible to initialize and connect at the same time by performing the connection process by designating the data for initialization and data for connection. (See
Section 3.4.6.)
1
Name
(2) Registering initialization data using GX Configurator-SC (Settings on the modem function system setting screen)
The number of the initialization data used to initialize the modem connected to the Q series C24 is registered on the GX Configurator-SC's "Modem function system setting" screen.
The following explains the number designated by the "Initialization data number" item on the GX Configurator-SC's "modem function system setting" screen and the related buffer memory when the initialization data number = 0 is designated.
Used buffer memory
Address (CH1/CH2)
Hexadecimal Decimal
Data number for initialization designation
2
User frame being transmitted number
3 CR/LF output designation
4 Output head pointer designation
5 Output count designation
First
6
Output frame number designation
Second to
Hundredth
34
H
B6H
H
/156
H
B7
H
/157
H
B8
H
/158
H
B9
H
/159
H
BA
H
/15A
H
BB
H
/15B
H to
11D
H
/1BD
H
52
182/338
183/339
184/340
185/341
186/342
187/343 to
285/445
The number of data for initialization used and buffer memory designated value
When number used = 1
(
7D0
H
to 801F
H
:
Data for initialization registration number
1
)
When number used = 2 or more
0
H
(Unused)
(During initialization, the data registration number currently being sent is stored.)
0 (default value)
1 to 100 (See 1))
1 to 100 (See 2))
(
7D0
H
to 801F
H
:
Data for initialization registration number
1
)
1 The data for initialization registration number to be used is designated.
7D0
H
to 7DD
H
(2000 to 2013) : Data registered by the OS
9C4
H
to 9E1
H
(2500 to 2529) : Data registered in the Flash ROM by the user
8001
H
to 801F
H
(–32767 to –32737): Data registered in the buffer memory by the user
1) Output head pointer designation area (address: 184/344 (B8
H
/158
H
))
Designate the location of the head position (n-th unit) in the output frame number designation area to which the registration number of the data for initialization to be sent is written.
1 : Transmitted form the first unit
to
100: Transmitted from the 100th unit
3 - 68 3 - 68
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
2) Output count designation area (address: 185/345 (B9
H
/159
H
))
The number of data for initialization units to be transmitted starting from the location set by the output head pointer designation area is designated here.
1 : 1 data will be transmitted
to
100: 100 data will be transmitted
(3) Precautions during modem/TA initialization
If the DSR signal from the modem/ TA goes OFF when modem/TA initialization is completed (X10 goes ON), the Q Series C24 executes initialization processing automatically in accordance with the following.
1) If the auto modem initialization is specified
Modem / TA initialization processing is executed in the initialization / connection timeout time interval while the DSR signal is OFF without relation to the ON/OFF status of the modem initialization request signal Y10.
2) If the auto modem initialization is not specified
The modem / TA initialization processing is executed when the DSR signal restarts without relation to the ON/OFF status of the modem initialization request signal Y10.
(4) If modem / TA initialization is executed automatically (Set by the
GX Configurator-SC)
By having the GX Configurator-SC perform the settings for automatic modem initialization, modem initialization is executed automatically when the Q Series
C24 starts up.
The modem initialization completion signal (X10) goes On.
(a) Settings for auto initialization of the modem / TA
Select "auto initialize" for the auto modem initialization designation in the
GX Configurator-SC’s "Modem function system setting" screen.
(b) Cautions when initializing the modem / TA automatically
1) If the modem's initialization processing is completed abnormally, the Q
Series C24 executes the following processing.
• The initialization / connection abnormal completion signal (X13) does not go ON.
• An error code is stored in the buffer memory's modem function error code storage area (Address: 545 (221
H
)).
• Modem initialization is retried automatically using the initialization / connection timeout time stored in the buffer memory (address: 50
(32
H
), and is repeated until initialization is completed normally.
When modem initialization is not completed normally, the user should perform the following, and restart the station where the Q
Series C24 is installed.
• Check the set initialization data No.
• Check the registered contents of the initialization data corresponding to the set initialization data No. (If they are abnormal, correct them and register them again.)
• Check if the modem’s power is turned on.
3 - 69 3 - 69
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
2) When the line is disconnected from the Q Series C24 side (using Y12), the initialization completion signal (X10) goes off together with the connection in progress signal (X12).
When connecting to the line again, do so after first initializing the modem.
POINT
When the line to the Q Series C24 is disconnected from the external device side, the Q Series C24’s initialization completion signal (X10) does not go OFF.
When desiring to disable reception by the Q Series C24 side’s modem, execute line disconnect by the modem disconnection request signal (Y12).
Address
B6
H
B7
H
B8
H
B9
H
BA
H
BB
H
BC
H
BD
H
BE
H
BF
H
(5) If the modem/TA is initialized by a sequence program
(a) I/O signals used in initialization
The initialization request signal (Y10), initialization complete signal (X10) and initialization/connection abnormal complete signal (X13) are used.
(Example) When initializing the modem connected to CH1 of the Q series
C24 using two set of data for initialization (registration numbers
8001
H
and 8002
H
) that are registered in the buffer memory
Buffer memory
Frame number being transmitted
CR/LF output designation
(Designated value)
0
0
Output head pointer designation
3
Number of outputs
2
1st unit
2nd unit
9C4
9C5
H
H
Output frame number
3rd unit
4th unit
5th unit
6th unit
8001
8002
9D0
9D1
H
H
H
H
….…
….…
Out of the output frame numbers, from which one the transmission will be initiated is designated.
Out of the output frame numbers, the number of units to be transmitted is designated.
….…
Data for initialization registration number is designated.
The Q series C24 will transmit the data for initialization in the designated order.
Must be designated prior to the modem initialization request.
Initialization request
Y10
Initialization completion X10
Initialization/connection abnormal completion X13
Q series C24
(Normal completion)
(Abnormal completion)
After the designated number of initialization retries have been executed
Initialization data
Registration No.8002
H
Initialization data
Registration No.8001
H
Modem
3 - 70 3 - 70
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(b) Modem/TA initialization program example
An example of the modem/TA initialization program on the Q series C24 side by the PLC CPU is shown below.
When the initialization data has been registered from GX Configurator-SC or from the PLC CPU.
X12: Connection in progress signal
X1E: Ready signal
X1F: WDT error signal
M0 : Accessible flag
M1 : Data registration complete
flag for initialization
M30: Initialization enabled flag
Turns the ready flag ON
Turns the modem initialization enabled flag ON
Modem initialization command
Sets the initialization request signal
Sets the initialization request flag
Sets the initialization completed flag
Reads the error code at initialization abnormal completion
Resets the flag with the clear command
3 - 71 3 - 71
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3.4.6 Line connection
This section explains the connection (dialing) with the partner devices for the purpose of data communication with external devices using the modem functions.
In case of notification to a pager receiver, the line is connected while the notification is being processed. The connection processing such as a connection request (Y11) to
I/O signal is, therefore, unnecessary.
The data for connection indicated in this section should be set to perform the notification processing
(1) Requirements for connection
Complete the following settings and registrations in advance.
1) The initial settings for the Q series C24 as shown in Section 3.4.2
2) The registration of the data for initialization as shown in Section 3.4.3
3) The registration of the data for connection as shown in Section 3.4.4
4) The initialization of the modem/TA connected to the Q series C24 side as shown in Section 3.4.5
In addition, both the initialization and line connection can be conducted simultaneously by designating the data for initialization and data for connection to perform connection processing.
For the data setting for initialization to perform initialization and line connection simultaneously, see Section 3.4.2, 3.4.5. Explanation on the above-mentioned setting is omitted in this section.
(2) Registering the data for connection using GX Configurator-SC
(Settings on the modem function system setting screen)
The number of the data for connection that is used for line connection in order to perform data communication with the external device is registered on the GX
Configurator-SC's "Modem function system setting" screen.
The following explains the number designated by the "Connection data number" item on the GX Configurator-SC's "Modem function system setting" screen.
The addresses shown in parentheses below indicate the addresses of the buffer memory where the setting values for this item on the "Modem function system setting" screen are stored.
1) When line connecting from the Q series C24 side
• Data number for connection designation area (address : 35
H
(53))
The data for connection registration number is designated.
BB8
H
to BD5
H
(3000 to 3029) : Data registered to the Flash ROM by the user
8001
H
to 801F
H
(–32767 to –32737): Data registered to the buffer memory by the user
2) When line connecting from the external device
Since the line connection processing is not necessary on the Q series C24 side, connecting data registration for line connection and data number setting for connection are not needed.
3 - 72 3 - 72
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
Buffer memory for connection
Address: 35
H
(53)
Normal completion
Connection request
Y11
Initialization completion
Y10
Dial in progress
X11
Connection in progress X12
(ON)
(3) I/O signals used in line connection
Connection request signal (Y11), dial in progress signal (X11), connection in progress signal (X12) and initialization/connection abnormal completion signal
(X13) are used.
(Example1) When performing the line connection from the Q series C24 side only following the completion of initialization
0 3000
RS-232 CD terminal
Dial
Result code receive
Set "Display a result code using the AT command" in the local station side modem.
Abnormal completion
Connection request
Y11
Initialization completion
Y10
Dial in progress
X11
Connection in progress
X12
Initialization/ connection
X13 abnormal completion
RS-232 CD terminal
(ON)
(OFF)
(OFF)
Dial Dial Dial Dial
Retry (In case of three times)
(Dialing)
Connection channel and retry operation are performed using the buffer memory setting.
3 - 73 3 - 73
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(Example2) When performing the initialization and the line connection from the Q series C24 side simultaneously
Buffer memory for initialization
Buffer memory for connection
Address: 35
H
(53)
Normal completion
Connection request
Y11
Initialization completion
Y10
Dial in progress
X11
Connection in progress
X12
0
RS-232 CD terminal
Abnormal completion
Connection request
Y11
Initialization completion
Y10
Set "Display a result code using the AT command" in the local station side modem.
Modem initialization
(See section 3.4.5)
Dial in progress
X11
Connection in progress
X12
Initialization/ connection
X13 abnormal completion
(OFF)
RS-232 CD terminal
(OFF)
(See Section 3.4.5)
3000
Dial
Result code receive
Modem initialization
(See section 3.4.5)
Dialing
Dial Dial Dial Dial
Retry (In case of three times)
Connection channel and retry operation are performed using the buffer memory setting.
3 - 74 3 - 74
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
Buffer memory for connection
Address: 35
H
(53)
Connection request
Initialization completion
Y11
Y10
Dial in progress
X11
Connection in progress
X12
(OFF)
(ON)
(OFF)
(Example) When initiating the line connection from the partner device after the completion of initialization
0
(Normal connection)
(Normal connection)
RS-232 CD terminal
Reception
Result code receive
Unlock processing for the remote password
Set "Display a result code using the AT command" in the local station side modem.
Password
(for system)
Response
Remote password
Response
Communication only when connected with
GX Developer
Communication using MC protocol
When connecting to the GX Developer
POINT
(1) The connection channel on the Q series C24 side is set in the "modem function system setting" screen of GX Configurator-SC.
(2) Abnormal processing when the partner device initiate the line connection is left entirely to the partner device.
There is no method on the Q series C24 side to check a line connection error occurrence at the partner device.
(3) When a remote password check is performed for the QCPU, normal completion of the unlock processing allows access to data communication/PLC thereafter.
(4) Precautions during the line connection
1) Prior to data communication with external devices, determine when and which station will perform the line connection (dialing) and line disconnection processing to the external device.
2) Use the following method to perform the unlock processing for the QCPU remote password from the opposite device.
• During communication using MC protocol, transmit the dedicated command to the Q series C24 side.
• When accessing the PLC using the GX Developer, perform the unlock processing on the GX Developer screen when access begins.
See Section 3.3.7 (8) for what to do when the unlock processing is completed abnormally.
3 - 75 3 - 75
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3) When reconnecting the line after disconnection, allow several seconds for the modem before turning on the Connection request (Y11). If it (Y11) is turned on immediately after line disconnection, the modem may not accept the first connection request, resulting in connection failure, and the user may be forced to wait for the retry time to elapse.
(5) Line connection program example
An example of a line connection program is shown below.
• Example of initiating line connection from the Q series C24 side following the initialization completion
When the data for connection has been registered from GX Configurator-
SC or from the PLC CPU.
X10 : Initialization complete signal
X1E : Ready signal
X1F : WDT error signal
M0 : Accessible flag
M2 : Data registration complete
flag for connection
See Section 3.4.4
M3 : Initialization complete flag
M40: Connectable flag
Turns the ready flag ON
Turns the line connectable flag ON.
• Data for initialization registration
• Data for connection registration
• Modem/TA initialization
See Section 3.4.3
See Section 3.4.4
See Section 3.4.5
Line connection command
Sets connection request signals
When the connection in progress signal ON (normal completion), sets the connection complete flag.
Reads the error code at connection abnormal completion.
Resets the flag with the clear command.
3 - 76 3 - 76
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
• Example of simultaneous execution of initialization and line connection from the
Q series C24 side
When the initialization and connection data have been registered from the
GX Configurator-SC or from the PLC CPU.
X10 : Initialization complete signal
X1E : Ready signal
X1F : WDT error signal
M0 : Accessible flag
M1 : Data registration complete
flag for initialization
M2 : Data registration complete
flag for connection
See Section 3.4.4
M3 : Initialization complete flag
M40: Connectable flag
Turns the ready flag ON
Turns the line connectable flag ON.
• Data for initialization registration
• Data for connection registration
See Section 3.4.3
See Section 3.4.4
Line connection command
Sets connection request signals
When the connection in progress signal ON (normal completion), sets the connection complete flag.
Reads the error code at connection abnormal completion.
Resets the flag with the clear command.
REMARK
When the line connection is initiated from the partner device, neither registration, setting nor connection processing is necessary.
As shown in example 3) of this section's (3), data communication is possible if the connection in progress signal ( 12) turns ON after the completion of Q series C24 modem/TA initialization.
For an example of the modem/TA program for initialization, see Section 3.4.7.
3 - 77 3 - 77
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3.4.7 Data communication and notification
This section explains the cautions for data communication with the partner device using modem function and procedures for notification to pager receivers.
(1) Requirements for data communication and notification a) When communicating data with external devices
Perform the appropriate processing up to line connection or modem/TA initialization, depending on whether or not the line connection is initiated from the Q series C24 side.
After line connection, data communication can be performed using an MC protocol/non procedure protocol/bidirectional protocol in full-duplex communication.
1) When line connecting from the Q series C24 side
Processing up to line connection as shown in Section 3.4.6.
2) When line connecting from the external device
Processing up to the initialization of the modem/TA as shown in Section
3.4.5.
b) When notifying to pager receivers
Perform processing up to the initialization of the modem/TA as shown in
Section 3.4.5.
In notification to pager receiver, since the line connection is performed during notification processing, line connection processing is unnecessary.
However, be sure to register data for connection.
(2) Buffer memory used and I/O signals a) When communicating data with the external device
Only buffer memory and I/O signals the user uses for data communication
(MC protocol/non procedure protocol/bidirectional protocol).
Communicate data using the connection in progress signal (X12) ON as the interlock signal.
X12
Program for data communication
There is no I/O signal or buffer memory for modem functions used in data communication.
Initialization request
Initialization completion
Connection request
Connection in progress
Y10
X10
Y11
X12
(ON)
(ON)
RS-232 CD terminal
(ON)
Set "Display a result code using the AT command" in the local station side modem.
Initialization Dial
Result code receive
Data communication is possible
3 - 78 3 - 78
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
REMARK
Station A
Q25HCPU
MODE
RUN
ERR.
USER
BAT.
BOOT
QJ71C24-R2
CH1.
CH2.
This section explains the general procedure for non procedure protocol/bidirectional protocol (executed in full-duplex communication) data communication using the modem function between the PLC CPU with Q series C24 installed.
Station B
Public line
Q25HCPU
MODE
RUN
ERR.
USER
BAT.
BOOT
QJ71C24-R2
CH1.
CH2.
CH1.
Modem
CH1.
RS-232 cable
Modem
USB
RS-232
CH2.
RS-232 cable
USB
RS-232
CH2.
Station A
(connection request side)
Connection request
Y11
Initialization completion
X10
Connection in progress
Disconnection request
Disconnection completion
X12
Y12
X14
(General Procedure)
1) Perform initial setting for Q series C24 at both station A and station B.
2) Perform modem/TA initialization in station B.
3) Perform modem/TA initialization and line connection in station A.
4) Communicate data using the non procedure protocol/bidirectional protocol.
5) In order to end the communication, disconnect line from station A that initiated the line connection.
Connection Communication Disconnection
RS-232 CD terminal
Station B
(connection reception side)
Initialization completion
X10
Connection in progress
Disconnection request
X12
Y12
Disconnection completion
X14
RS-232 CD terminal
(ON)
(OFF)
(OFF)
It is possible to disconnect line from Station B, as well.
3 - 79 3 - 79
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q b) When notifying to pager receiver
1) Initial setting by GX Configurator-SC
Register the data number registration area for connection below in the
"Modem function system setting" screen.
BB8
H
to BD5
H
(3000 to 3029) : Data registered to the Flash ROM by the user
8001
H
to 801F
H
(–32767 to –32737): Data registered to the buffer memory by the user
2) I/O signal
Use notification-issued request signal (Y14), notification normal complete signal (X15), notification abnormal complete signal (X16).
(Example 1) When normal completion
Buffer memory for Q series C24 initial setting
Notification execution designation area
0
(Address: 2F
H
(47))
1
Buffer memory for notification
Data number for connection designation area
(Address: 35
H
(53))
0 3000
Modem function error code storage area
(Address: 221
H
(545))
Notification execution data storage area
(Address: 22A
H
(554))
0
0
3000
Initialization completion
Connection in progress
X10
X12
Notification
X15 normal completion
Notification X16 abnormal completion
Notificationissued request
Y14
(ON)
(OFF)
RS-232 CD terminal
(OFF)
Dial
Notification Disconnection
3 - 80 3 - 80
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(Example 2) When abnormal completion
Buffer memory for Q series C24 initial setting
Notification execution designation area
0
(Address: 2F
H
(47))
1
Buffer memory for notification
Data number designation area for connection
(Address: 35
H
(53))
0 3000
Modem function error code storage area
(Address: 221
H
(545))
Notification execution data storage area
(Address: 22A
H
(554))
0
0
Initialization completion
Connection in progress
X10
X12
Notification
X15 normal completion
Notification X16 abnormal completion
Notificationissued request
Y14
(ON)
(OFF)
(OFF)
RS-232 CD terminal
(OFF)
(Error code)
Dial Dial Dial Dial
Retry (In the case of three times)
(Dialing)
Retry processing is conducted according to the values for the connection retry number to initialization/connection timeout registered in the initial setting for GX Configurator-SC.
3 - 81 3 - 81
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(3) Precautions for performing data communication and notification a) When communicating data with the external device
1) When setting the no-communication interval time to infinite wait (set value=0) in the initial setting of Q series C24, be sure to perform line disconnection after the completion of data communication.
2) Only the no procedure protocol/bidirectional protocol data communication can be performed in the PLC CPU with Q series C24 installed.
3) The Q series C24 automatically performs line disconnection processing if no data exchange is performed during the no-communication interval time.
(The connection in progress signals (X12) and initialization complete signals (X10) turn off.) b) When notifying to pager receivers
1) Turn on the notification-issued request signal (Y14) before the Q series
C24 modem/TA initialization is completed.
2) Notification processing is conducted when the notification-issued request signal (Y14) turns from ON to OFF after the completion of modem/TA initialization.
Therefore, notification processing is conducted when the PLC CPU of the station with Q series C24 installed is in stop status, or the PLC CPU stops due to error, since the notification-issued request signal (Y14) is turned off in either case.
Write the data number for connection in the initial setting for GX
Configurator-SC.
3) When the notification-issued request signal (Y14) is turned OFF from ON before initialization of the Q series C24 modem/TA, the processing will end abnormally.
4) When the notification-issued request signal (Y14) is turned OFF from ON during initialization of the Q series C24 modem/TA, notification processing will be conducted after the completion of the modem/TA initialization.
5) Notification processing is completed in the order of line connection, message transmission, and line disconnection from Q series C24 for the transmission station of the radio wave to the notification destination.
Therefore, even if the power to the notification destination equipment is off, the notification processing will end normally as long as the above processing is completed.
6) When the notification-issued request signal (Y14=ON) is turned ON before notification processing is complete, some messages may not be sent.
POINT
Turn on the notification-issued request signal (Y14) before the initialization processing of the Q series C24 modem/TA is completed, and turn it off after the initialization complete signal (X10) is turned ON (notification request).
3 - 82 3 - 82
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(4) Program for notification example
An example of program for notification is shown below.
When the initialization and connection data have been registered from the GX
Configurator-SC or from the PLC CPU.
X10: Initialization complete signal
X1E: Ready signal
X1F: WDT error signal
M0 : Accessible flag
M2 : Data registration complete
flag for connection
See Section 3.4.4
M3 : Initialization complete flag
M40: Notification enable flag
Turns the ready flag ON.
Turns the notification enable flag ON.
• Data for initialization registration
• Data for connection registration
See Section 3.4.3
See Section 3.4.4
• Modem/TA initialization
Sets the notification-issued request signal.
See Section 3.4.5
Notification command
Resets the notification-issued request signal (notification-issued).
Sets the notification-issued request flag.
Sets the flag at notification normal completion.
Reads the error code at notification completion.
Resets the flag with the clear command.
3 - 83 3 - 83
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3.4.8 Line disconnection
This section explains the line disconnection upon communication completion when communicating data with the external device using the modem functions.
In case of notification to pager receivers, since the line will be disconnected at the end of the notification processing, the disconnection processing such as I/O signal disconnection request (Y12) is unnecessary.
(1) I/O signal used
Uses modem disconnection request signal (Y12) and modem disconnection complete signal (Y14).
Host station
Initialization completion
Communication
X10
Connection in progress
X12
Modem
Y12 disconnection request
Modem disconnection completion
X14
RS-232 CD terminal
Disconnection
External station (Q series C24)
Initialization completion
Connection in progress
X10
X12
Modem
Y12 disconnection request
Modem disconnection completion
X14
RS-232 CD terminal
(ON)
(OFF)
(OFF)
This is the procedure to take in order to turn off the initialization complete signal (X10).
In the case of Q series C24, when the line is disconnected from the external device,
the initialization complete signal (X10) at the local station is not turned OFF.
3 - 84 3 - 84
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
POINT
(1) Line disconnection processing can be conducted from either device as long as the connection is in progress.
(2) The line disconnection processing disconnects the line connection with the external device as well as the connection with the Q series C24 modem.
(3) Even when an error occurs during the line disconnection, the disconnection processing will be forced.
(4) If data communication is to be resumed after line disconnection, either one of the following processing will be initiated depending on the initialization complete signal (X10).
1) If the initialization complete signal is OFF
Start from the initialization of the modem/TA.
2) If the initialization complete signal is ON
Start from the line connection with the external device.
REMARK
There is no buffer memory for line disconnection processing.
(2) Precautions during the line disconnection
1) Prior to data communication with external devices, determine when and which station will perform the line connection (dialing) and line disconnection processing to the external device.
2) If the line is disconnected during data transmission, transmission processing will be performed depending on the signal status of the Q series C24 RS-
232C interface.
3) If the line is disconnected during data reception, data reception will be disabled. This may cause an error occurrence such as a reception time out.
3 - 85 3 - 85
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(3) Program example for line disconnection
A program example for line disconnection is shown below.
X0: Normal transmission completion signal
X1: Abnormal transmission completion signal
X3: Reception data read request signal
X4: Abnormal reception detection signal
X10: Initialization complete signal
X12: Connection signal
X1E: Ready signal
X1F: WDT error signal
•
Registration of data for initialization
•
Registration of data for connection
•
Modem/TA initialization
•
Line connection
•
Data communication
Y0: Transmission request signal
Y1: Reception data read complete signal
M0: Accessible flag
M50: Data communication enable flag
M70: Line disconnection enable flag
See Section 3.4.3
See Section 3.4.4
See Section 3.4.5
See Section 3.4.6
See Section 3.4.7
Ready flag is ON
Data communication enable flag is ON
The line disconnection enable flag is
ON
Line disconnection command
Modem disconnection request signal is set
When the modem disconnection completion signal is ON, the error code is read.
Line disconnection completion flag is set upon normal completion
Performs error handling when D105 is other than 0 (error code)
Modem disconnection request signal is reset
Line disconnection processing
(Line disconnection from external device)
Various request signals are reset
When any connection signal or completion signal is ON, the modem disconnection request signal is set.
When the modem disconnection completion signal is ON, the request signal is reset.
When the modem disconnection completion signal is OFF, the line disconnection request signal is reset.
3 - 86 3 - 86
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3.5 Sample Programs
This section shows sample programs to test the connection with the remote station's
PLC CPU to which Q series C24 is installed.
Each program contains a minimum set of processing necessary for performing a exchange test.
Modify the data for initialization and data for connection to match each system environment.
When adding error-handling procedures, add them separately by seeing the explanation in this chapter.
X21
X22
X23
X24
Y14
Y60
Y61
Y62
Y63
Device
X3
X4
X10
X11
X12
X13
X14
X15
X16
X1E
X1F
X20
Y10
Y11
Y12
The uses of major devices that are used in these sample programs are listed below.
Application
Reception data read request
Reception abnormal detection
Initialization completion
Dial in progress
Connection in progress
Initialization/connection abnormal completion
Device
Application of device (comment list)
Application
Y64 Line connection completion
Y66
Y67
M0
M1
Notification completion
Line disconnection completion
Q series C24 accessible
Device Application
M100 Initialization request execution
M101
Connection request execution
Notification execution
M102 Transmission execution in progress
M103 Reception data read execution in progress
Initialization data registration completion SM400 Always ON
Modem disconnection completion
Notification normal completion
M2
M3
Data registration completion for connection
Initialization completion D0
Notification abnormal completion
Q series C24 ready
WDT error
M4
M6
M7
Line connection completion
Notification completion
D1
D2
D11
Number of registration data bytes
Control number designation
Receiver designation
Initialization command/telephone number
External line dialing number, etc.
Initialization command
Line connection command
Data communication command
Line disconnection command
Notification command
Initialization request
Connection request
Modem disconnection request
Notification-issued request
Q series C24 accessible
Initialization data registration completion
Data registration completion for connection
Initialization completion
M10
M20
M30
M31
M40
M41
M50
M51
M52
M60
M70
M71
M80
M91
M92
Line disconnection completion
Convert the registration command into pulse
Convert the registration command into pulse
Initialization enabled
Convert the initialization command into pulse
Connectable
Convert the connection command into pulse
Data communication enabled
Transmission enabled
Convert the transmission command into pulse
Convert the notification command into pulse
Line disconnection enabled
Convert the line disconnection command into pulse
Line disconnection (request) occurrence
Reception processing in progress flag
Transmission processing in progress flag
D12
D23
D24
D39
D50
D51
D60
D61
Line type, etc.
Wait time for message transmission
Message
Message length
Number of transmission data
Transmission data
Number of reception data
Reception data
D100 Initialization error code
D101 Line connection error code
D102 Notification error code
D103 Data transmission error code
D104 Data reception error code
D105 Line disconnection error code
3 - 87 3 - 87
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3.5.1 Sample program for data communication-1
(1) Sample program system configuration
The configuration of a system using this sample program is shown below.
1) Line connection
2) Communications by
the non-procedure protocol
3) Line disconnection
Modem Modem
QJ71C24-R2 2) QJ71C24-R2 1)
(2) Connection request station side (QJ71C24-R2 1)) sample program
The modem connected to the CH1 side interface is initialized, the line is connected, data are transmitted by the non-procedure protocol and the line is disconnected through commands from the user.
Perform the following settings before running this program.
(a) GX Developer switch settings (See Section 3.4.2.)
Switch No.
Switch 1
Switch 2
Switch 5
Setting value
07E2
0006
0000
(b) Settings by the GX Configurator-SC (See Section 3.4.2.)
Perform the following settings in each setting screen.
Use the default settings in screens and setting items other than those shown below.
1) Modem function system settings
"Modem function system setting" screen setting items
Modem connection channel designation
Data No. for initlaization designation
Data No. for connection designation
Setting value
1CH
07D5
0BB8
2) Modem connection data registration
"Data for modem connection" screen setting items
Data for modem connection
1 (H0BB8)
Telephone
No. (
1
)
Setting value
0123456789
1 Specify the external party's telephone No.
3 - 88 3 - 88
3 COMMUNICATIONS BY THE MODEM FUNCTION
<Status confirmation>
<Modem initialization, line connection processing>
<Data transmission processing (non procedure protocol)>
<Data reception processing (non procedure protocol)>
<Line disconnect processing>
MELSEC-Q
Access possible
Modem initialization, line connection possible
Data communications possible
Data transmission possible
Line disconnect possible
Conversion of modem initialization, line connection commands to pulses
Modem initialization, line connection processing to sub routine
Conversion of data communications
(transmission) commands to pulses
To the data transmission processing sub routine
Setting of the receive data reading request
To the data reception processing rub routine
Conversion of line disconnect commands to pulses
Conversion of turning connected signals OFF to pulses
To the line disconnect processing sub routine
3 - 89 3 - 89
3 COMMUNICATIONS BY THE MODEM FUNCTION
[Modem initialization, line connection processing]
[Data transmission processing]
[Data reception processing]
MELSEC-Q
Set the connection request signal
With the initialization completed signal ON and the connected signal
ON, reset the request signal
With the initialization/connection abnormally completed signal ON, read the error code and reset the request signal
Set the transmission data
Set the transmission channel on CH1
Set the transmission data count
Execute the transmission request
Transmission normally completed
Transmission abnormally completed
Set the data reception channel on CH1
Execute reading of receive data
Reading of receive data normally completed
Reading of receive data abnormally completed
3 - 90 3 - 90
3 COMMUNICATIONS BY THE MODEM FUNCTION
[Line disconnection processing]
MELSEC-Q
Modem disconnection request signal is set
When the modem disconnection completion signal is ON, the error code is read.
When the normal completion signal is
ON, the line disconnection completion flag is set.
Modem disconnection request signal is reset
3 - 91 3 - 91
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(3) Sample program for a connection receiving station side (QJ71C24-
R2 2))
After the connection in progress signal (x12) = ON, data communications are carried out by the non procedure protocol through a command from the user.
Perform the following settings before running this program.
(a) GX Developer switch settings (See Section 3.4.2.)
Switch No.
Switch 1
Switch 2
Switch 5
Setting value
07E2
0006
0000
(b) Settings by the GX Configurator-SC (See Section 3.4.2.)
Perform the following settings in each setting screen.
Use the default settings in screens and setting items other than those shown below
1) Modem function system settings
"Modem function system setting" screen setting items
Modem connection channel designation
Data No. for initialization designation
Auto modem initialization designation
Setting value
1CH
07D5
Auto initialize
3 - 92 3 - 92
3 COMMUNICATIONS BY THE MODEM FUNCTION
<Status confirmation>
<Data transmission processing (non procedure protocol)>
<Data reception processing (non procedure protocol)>
MELSEC-Q
Access possible
Data transmission possible
Set the transmission data
Set the transmission channel on CH1
Set the transmission data count
Execute transmission request
Transmission normally completed
Transmission abnormally completed
Set the data reception channel on CH1
Execute reading of receive data
Reading of receive data normally completed
Reading of receive data abnormally completed
3 - 93 3 - 93
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3.5.2 Sample program for data communication-2
(1) Sample program on the connection request station side
Initialization for the modem connected to CH1 interface, line connection, data communication by the non procedure protocol and line disconnection are executed by commands from the user.
Before executing this program, perform the following settings (changing the default values) on the GX Configurator-SC's "Modem function system setting/registration" screen and register them in the Q series C24. (Settings other than the items shown below are not required).
Settings on the GX Configurator-SC's "Modem function system setting" screen
(For more details, see Section 8.4.4 of User's Manual (Basic).)
Setting item
Modem connection channel designation
No-communication interval time designation
Data No. for initialization designation
Data No. for connection designation
Setting value
CH1
2 (min)
8001
H
8002
H
REMARK
Registration of the modem's initialization data and line connection data, modem initialization, line connection, data communications by the non procedure protocol and line disconnection are all performed by the sequence program.
3 - 94 3 - 94
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
Accessible flag is turned ON
Modem initialization enabled flag is turned ON
Line connectable flag with the remote station is turned ON
Exchangeable flag with the partner station is turned ON
Data transmission enabled flag to the partner station turned ON
Line disconnection enabled flag with the partner station is turned ON
To the data registration processing for initialization subroutine
To the data registration processing for connection subroutine
Convert the initialization command into pulse
Various complete flags after the modem initialization processing is reset
To the modem initialization processing subroutine
Convert the line connection command into pulse
Various complete flags after the line connection processing is reset
To the line connection processing subroutine
Convert the data communication
(transmission) command into pulse
To the data transmission processing subroutine
Convert the reception data read request into pulse
To the reception data read processing subroutine
Convert the line disconnection command into pulse
(Line disconnection from local station)
Line disconnection complete flag is reset
To the line disconnection processing subroutine
Convert the connection in progress signal OFF into pulse
(Line disconnection from partner side)
3 - 95 3 - 95
3 COMMUNICATIONS BY THE MODEM FUNCTION
P1
P2
P3
MELSEC-Q
Convert the reset command of various requestb signal into pulse
To the various request signal and the complete signal OFF subroutine
Output the various complete flag status
(LED display)
Data registration processing for initialization subroutine
• Set the number of bytes of the
registration data
• Set the user control data
(control number)
• Set the initialization command
• Write the data for initialization
(Data No. 8001
H
)
(Registration to buffer memory)
• Data registration complete flag for
initialization is set
Data registration processing for connection subroutine
• Set the number of bytes of the
registration data
• Clear the data storage device for
connection
• Set the pager receiver designation
(Notification is not executed)
• Set the telephone number
• Set the space to the remainder of the
telephone number designation area
• Set the rxternal line dialing number (0)
• Set the line type (tone)
• Write the data for connection
(Data No.8002
H
)
(Registration to buffer memory)
• Data registration complete flag for
connection set
Modem initialization processing subroutine
• Set the initialization request signal
• Initialization request execution flag is set
• When the initialization complete signal
ON, the initialization complete flag is
set and the request signal is reset
• When the initialization/connection
abnormal complete signal ON, the
error code is read and the request
signal is reset
3 - 96 3 - 96
3 COMMUNICATIONS BY THE MODEM FUNCTION
P4
P51
MELSEC-Q
Line connection processing subroutine
• Connection request signal is set
• Connection requestr execution flag is set
• When the connection in progress signal
ON, the connection complete flag is set
and the request signal is reset
• When the initialization/connection
abnormal complete signal ON, the error
code is read and request signalis is reset
Data communication processing subroutine
(Non procedure protocol, transmission)
• Set the transmission data
• Sets the transmission channel to CH1
• Set the number of transmission data
• Sets the transmitting flag
• Executes the transmission request
• Transmission request execution flag
is set
• Transmission normal completion
• Transmission abnormal completion
P52 Data reception processing subroutine
• Sets the data reception channel to CH1
• Reception data read execution flag
is set
• Executes the reception data reading
3 - 97 3 - 97
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
•
Received data read normally completed
•
Received data read abnormally completed
Line disconnection processing subroutine
(Line disconnection from local station)
•
Modem disconnection request signal is set
• When the modem disconnection completion signal is ON, the error code
• is read.
When the normal completion signal is
ON, the line disconnection completion flag is set.
•
Modem disconnection request signal is reset
Subroutine resetting various request signals and completion signals
•
Various request signals are reset
• When any completion signal is ON, the modem disconnection request signal is set.
•
When the initialization complete signal is OFF and the modem disconnection completion signal is ON, the request signal is reset.
•
When the related signals are OFF, the flag is reset.
3 - 98 3 - 98
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
(2) Sample program on the connection reception station side
The modem initialization and data communication by the non procedure protocol are executed by commands from the user.
Before executing this program, perform the following settings (changing the default values) on the GX Configurator-SC's "Modem function system setting" screen and register them in the Q series C24. (Settings other than the items shown below are not required).
Settings on the GX Configurator-SC's "Modem function system setting/registration" screen
(For more details, see Section 8.4.4 of User's Manual (Basic).)
Setting item
Modem connection channel designation
No-communication interval time designation
Data No. for initialization designation
Setting value
CH1
2 (min)
8001
H
3 - 99 3 - 99
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
Accessible flag is turned ON
Modem initialization enabled flag is turned ON
Exchangeable flag with the partner station is turned ON
Data transmission enabled flag to the partner station turned ON
To the data registration processing for initialization subroutine
Convert the initialization command into pulse
Various complete flags after the modem initialization processing is reset
To the modem initialization processing subroutine
Convert the data communication
(transmission) command into pulse
To the data transmission processing subroutine
Convert the reception data read request into pulse
To the reception data read processing subroutine
Convert the connection in progress signal OFF into pulse
(Line disconnection from partner side)
Convert the reset command of various request signal into pulse
To the various request signal and the complete signal reset subroutine
Output the various complete flag status
(LED display)
3 - 100 3 - 100
3 COMMUNICATIONS BY THE MODEM FUNCTION
P1
P3
P51
MELSEC-Q
Data registration processing for initialization subroutine
• Sets the number of bytes of the
registration data
• Sets the user control data
(control number)
• Sets the initialization command
• Write the data for initialization
(Data No. 8001
H
)
(Registration to buffer memory)
• Data registration complete flag for
initialization is set
Modem initialization processing subroutine
• Initialization request signal is set
• Initialization request execution flag is set
• When the initialization complete signal
ON, the initialization complete flag is
set and the request signal is reset
• When the initialization/connection
abnormal complete signal ON, the error
code is read and the request signal
is reset
Data communication processing subroutine
(Non procedure protocol, transmission)
• Set the transmission data
• Sets the number of transmission data
(words)
• Transmission request execution flag
is set
• Transmission request execution
• Transmission request normal
completion
• Transmission request abnormal
completion
3 - 101 3 - 101
3 COMMUNICATIONS BY THE MODEM FUNCTION
P52
MELSEC-Q
Data reception processing subroutine
• Sets the data reception channel to
CH1
• Sets the data setting completion flag
for reading the receive data.
• Executes the receive data reading.
• Receive data read execution flag
is set
• Receive data normal completion
• Receive data abnormal completion
P8
Resets subroutine of various request signal and complete signal
• Various request signal is reset
• When any complete signal ON, the
modem disconnection request signal is set
• When the initialization complete signal OFF
and the modem disconnection complete
signal ON, the request signal is reset
• When the relation various signal OFF,
the flag is reset
3 - 102 3 - 102
3 COMMUNICATIONS BY THE MODEM FUNCTION
MELSEC-Q
3.5.3 Sample program for notification
Modem initialization and notification are executed by commands from the user.
Before executing this program, perform the following settings (changing the default values) on the GX Configurator-SC's "Modem function system setting" screen and register them in the Q series C24. (Settings other than the items shown below are not required.)
Settings on the GX Configurator-SC's "Modem function system setting/registration" screen
(For more details, see Section 8.4.4 of User's Manual (Basic).)
Setting item
Modem connection channel designation
Notification execution designation
No-communication interval time destination
Data No. for initialization designation
Data No. for connection designation
Setting value
CH1
Perform notification
2 (min)
8001
H
8002
H
REMARK
Registration of the modem's initialization data and line connection data, modem initialization, line connection and notifications are all performed by the sequence program.
3 - 103 3 - 103
3 COMMUNICATIONS BY THE MODEM FUNCTION
P1
MELSEC-Q
Accessible flag is turned ON
Modem initialization enabled flag is turned ON
Line connectable flag with the remote station is turned ON
To the data registration processing for initialization subroutine
To the data registration processing for connection subroutine
Converts the initialization command into pulse
Various complete flags after the modem initialization processing is reset
To the modem initialization processing subroutine
Converts the notification command into pulse
To the notification processing subroutine
When the reset command, the complete flag is reset
Output the various complete flag status
(LED display)
Data registration processing for initialization subroutine
• Sets the number of bytes of the registration
data
• Sets the user control data (control number)
• Sets the initialization command
• Write the data for initialization
(Data No.8001
H
) (Registration to buffer memory)
• Data registration complete flag for
initialization is set
3 - 104 3 - 104
3 COMMUNICATIONS BY THE MODEM FUNCTION
P2
P3
P6
MELSEC-Q
Data registration processing for connection subroutine
• Set the number of bytes of the
registration data
• Clear the data storage device for
connection
• Set the pager receiver designation
(Notification is executed)
• Set the telephone number
• Set the space to the remainder of the
telephone number designation area
• Set the external line dialing number (0)
• Set the line type (tone)
• Set the waiting time for the message
transmission
• Set the message
• Set the message length
• Write the data for connection
(Data No. 8002
H
)
(Registration to buffer memory)
• Data registration complete flag for
connection is set
• Notification-issued request signal is set
(Initial status)
Modem initialization processing subroutine
• Initialization request signal is set
• Initialization request execution flag is set
• When the initialization complete signal
ON, the initialization complete flag is
set and the request signal is reset
• When the initialization/connection
abnormal complete signal ON, the
error code is read and the request
signal is reset
Notification processing subroutine
• Notification-issued request signal
is reset (Issue request)
• Notification execution flag is set
• When the notification normal complete
signal ON, the notification complete flag is
set and the request signal is set (Initial status)
• When the notification abnormal complete
signal ON, the error code is read and the
request signal is set (Initial status)
3 - 105 3 - 105
4
4 RECEIVING DATA WITH AN INTERRUPT PROGRAM
MELSEC-Q
4 RECEIVING DATA WITH AN INTERRUPT PROGRAM
In data communication between the Q series C24 and the external device, an interrupt program can be used to receive data for the following data communication functions.
• Data reception during communication using the non procedure protocol
• Data reception during communication using the bidirectional protocol
This chapter explains a case in which data reception using the following data communication functions is performed with an interrupt program.
External device
Q series C24
Data transmission
Receive
Interrupt-issued
PLC CPU
Main program Main program
Interrupt program execution
FEND
I
SM400
BUFRCVS
POINT
Receiving data with an interrupt program expedites data reception by the PLC
CPU.
4 - 1 4 - 1
4 RECEIVING DATA WITH AN INTERRUPT PROGRAM
MELSEC-Q
4.1 Settings for Receiving Data Using an Interrupt Program
The following explains the settings for performing data reception with an interrupt program during communication using the non procedure protocol or bidirectional protocol.
(1) Setting by GX Developer
1) The following settings are performed with the interrupt pointer No. of module screen.
• The interrupt pointer number and quantity (quantity is fixed at 2) for the
PLC CPU used for the Q series C24.
• Assigning correspondence between the PLC CPU interrupt pointer number and the Q series C24 control number (fixed at 0).
2) Set the interrupt pointer No. of modules according to the explanation in
Section 4.5.3 of the User's Manual (Basic).
(2) Setting by GX Configurator-SC
1) Perform the following settings in the transmission control and other system setting screens.
• Specify "Interrupt-issued" in Receive interrupt-issued designation.
2) Display the screen in accordance with Section 8.4.5 of the User's Manual
(Basic) and perform the system settings.
POINT
To start the interrupt program, the settings of the "Interrupt pointer No. of module" in GX Developer and the "System setting" in GX Configurator-SC are required.
4
4.2 Interrupt Program Startup Timing
The following explains the startup timing for interrupt program when performing data reception with an interrupt program during communication using the non procedure protocol or bidirectional protocol.
(1) The startup timing is the same for communication using either the non procedure protocol or bidirectional protocol.
(2) Receive data from the external device is stored in the reception area of the buffer memory. When the next input signal rises, the interrupt program is started.
Input signal name
CHn reception data read request signal
CHn reception abnormal detection signal
CH1 side
X3
X4
CH2 side
XA
XB
4 - 2 4 - 2
4 RECEIVING DATA WITH AN INTERRUPT PROGRAM
MELSEC-Q
4.3 Reception Control Method Using an Interrupt Program
The following explains the reception control method when receiving data with an interrupt program during communication using the non procedure protocol or bidirectional protocol.
<Data reception using the dedicated instruction,
BUFRCVS instruction (interrupt program)>
FEND
SM400
I50
Z.BUFRCVS
"U0" K1 D200
Control data
• [D200]: Word count for stored receive data
• [D201]: Receive data
IRET
2) 5)
Main program execution
Interrupt program execution
BUFRCVS instruction
X3
Reception abnormal detection signal
Buffer memory reception area
X4
1)
3)
4)
Reception using bidirectional protocol
Data reception Response transmission
1) When data is received from the external device, the receive data is stored in the buffer memory and the reception data read request signal turns ON.
2) The main program stops executing and the interrupt program starts.
3) The data reception dedicated instruction, BUFRCVS, for the interrupt program is executed and data is received. ( 1)
4) When execution of the BUFRCVS instruction is complete, the reception data read request signal turns OFF.
5) When execution of the interrupt program is finished, execution of the main program restarts.
1 When the reading of receive data using the BUFRCVS instruction is finished, the following processes are performed.
At normal completion: PLC CPU error flag (SM0) turns OFF.
At abnormal completion: PLC CPU error flag (SM0) turns ON.
The error code is stored in the PLC CPU error code (SD0).
For more details on the PLC CPU error flag
(SM0) and error codes (SD0), see the PLC CPU
Manual.
4 - 3 4 - 3
4 RECEIVING DATA WITH AN INTERRUPT PROGRAM
MELSEC-Q
4.4 Programming
This section explains the programming when data reception is performed with an interrupt program during communication using the non procedure protocol or bidirectional protocol.
4.4.1 Program example
The following shows a program example for receiving data using an interrupt program.
(Program condition)
• Interrupt pointer No. of module set by GX Developer
CPU side: Interrupt pointer. Start No. = 50,
Interrupt pointer No. of units = 2 (fixed)
CH1 side interrupt pointer = I50,
CH2 side interrupt pointer = I51
Intelli. module side: Start I/O No. = 0, Start SI No. = 0 (fixed)
• Setting for whether the interrupt program is started by GX Configurator-SC
CH1 side: Issues interrupt (Communication is performed using the non procedure protocol.)
CH2 side: Does not issue interrupt.
(Program example)
When the Q series C24 I/O signals are X/Y00 to X/Y1F
Interrupt program enabled
For CH1 side
Normal reception
Abnormal reception
Sets the flag for confirming normal reception/abnormal reception in the main program.
Resets by the main program.
Reception interrupt program executed
Receives data and stores it in D200 and succeeding addresses.
D200 : No. of receive data
From D201 : Receive data
4 - 4 4 - 4
4 RECEIVING DATA WITH AN INTERRUPT PROGRAM
D200
D201
Data register
MELSEC-Q
Buffer memory
Reception area
No. of receive data
Receive data
D2nn
POINT
(1) When data reception is performed with an interrupt program, the dedicated
BUFRCVS instruction is used regardless of whether the communication uses the non procedure protocol or bidirectional protocol. For more details on the
BUFRCVS instruction, see Section 17.2.
(2) Create a program that enables/disables interrupts during execution of the main program in order to start the interrupt program.
Use the EI, DI and IMASK instructions.
4.4.2 Precautions when receiving data with an interrupt program
The following shows the precautionary notes when receiving data with an interrupt program.
(1) Create an interrupt program for data reception for each interface.
(2) Use GX Configurator-SC to set whether or not the interrupt program is started.
Whether or not the interrupt program is started can also be set with direct writing to the buffer memory . However, if it is specified during data reception, the interrupt program will not start.
(3) Do not use the INPUT and BIDIN instructions during execution of the interrupt program. Always use the BUFRCVS instruction to receive data.
(4) Do not turn the reception data read completion signal (Y1/Y8) ON/OFF during execution of the interrupt program.
(5) Use always ON (SM400) or direct input signal (DX3, DX4) as the contact signal when executing the BUFRCVS instruction. (See Section 4.4)
4 - 5 4 - 5
4 RECEIVING DATA WITH AN INTERRUPT PROGRAM
MELSEC-Q
(6) After the power supply turns from OFF to ON or the CPU module is reset, data cannot be received because the interrupt program is invalidated during the initial processing of the CPU module. For asynchronous data communication with the Q series C24 from the external device without communication procedure setting, read the data as shown in the following program.
Q series C24 I/O signals are from X/Y00 to X/Y1F
Normal completion processing
Abnormal completion processing
After RUN, 1 scan only INPUT instruction execution
CH1 error information is initialized
Received interrupt program execution
4 - 6 4 - 6
5 CHANGING SEND AND RECEIVE DATA LENGTH UNITS TO BYTE
UNITS (WORD/BYTES UNITS SETTING)
MELSEC-Q
5
5 CHANGING SEND AND RECEIVE DATA LENGTH UNITS TO BYTE UNITS
(WORD/BYTES UNITS SETTING)
The word units are used for the data length (count) of the amount of data sent/received using the following data communication functions in data communication between the
Q series C24 and the external device.
This chapter explains how to change the units (word to byte, byte to word) of the data length (count) sent/received with the following data communication functions.
The data length units can be set for each Q series C24 interface. The Q series C24 controls the number of data to be transmitted to the external unit and the number of data when it requests the PLC CPU to read the data received from the external device according to the units set by the user.
(1) Data communication functions and buffer memory related to data length units
The following shows the data communications functions and buffer memory related to the data length units.
(The buffer memory addresses in the table are the default value.)
Data communications function
MC protocol
Non procedure protocol
Bidirectional protocol
On-demand function
Data transmit function
Data receive function
Data transmit function
Data receive function
Name of buffer memory related to data length units (Address CH1, CH2)
Reference section
On-demand data length designation area
(A1
H
, 141
H
)
Send data count storage area
Reference manual Section 3.11
(400
H
, 800
H
)
Received data count designation area
(A4
H
, 144
H
)
Receive data count storage area
(600
H
, A00
H
)
Send data count storage area
User's manual (Basic) Chapter 6
Receive data count storage area
(400
H
, 800
H
)
User's manual (Basic) Chapter 7
(600
H
, A00
H
)
(2) How to change the units of the data length (count)
The units of the data length (count) can be changed using one of the following procedures.
1) Changing via GX Configurator-SC
The units can be changed on the GX Configurator-SC's system setting screen.
Change the units of the data length (count) according to the explanation in
Section 8.4.5 of the User's Manual (Basic).
2) Changing via the PLC CPU
The units can be changed with the CSET instruction.
Change the units of the data length (count) according to the explanation in
Section 17.4 of this manual.
5 - 1 5 - 1
5 CHANGING SEND AND RECEIVE DATA LENGTH UNITS TO BYTE
UNITS (WORD/BYTES UNITS SETTING)
MELSEC-Q
MEMO
5
5 - 2 5 - 2
6 CHANGING THE DATA COMMUNICATIONS MONITORING TIMES
MELSEC-Q
6
6 CHANGING THE DATA COMMUNICATIONS MONITORING TIMES
The monitoring times are timers used by the Q series C24 to monitor the receiving interval time between each byte when receiving data from the external device, the PLC
CPU processing time, and the time it takes to transmit to the external device.
The monitoring times can be set for each interface. The Q series C24 uses the monitoring time set by the user to control data transmission to and reception from the external device.
Set the monitoring times to match the specifications of the external device.
The Q series C24 monitoring times are shown below.
Monitoring time
Q series C24 default value
Protocol that can monitor the time
MC
Non procedure
Bidirectional
1)
No-reception
Format 0 monitoring time (timer 0) Format 1
2)
3)
Response monitoring time
(timer 1)
Transmission monitoring time (timer 2)
4) Message wait time
0 bytes
(Infinite wait)
5 s
3 min
0 ms
(Example) Data communications using an MC protocol
No wait time
Notes
Transmission time for the set number of bytes. (depends on the transmission rate)
For bidirectional protocol, this is valid for transmission only.
Command message
1 byte
External device
PLC CPU
First data Last data
First data Last data
Response message
Q series C24 ready to receive data state
Timer 0 monitoring time
Timer 0 elapsed time reset
Timer 1 monitoring time
Message wait time
Timer 2 monitoring time
H/W gate OFF time
Timer 1 elapsed time reset
Timer 2 elapsed time reset
6 - 1 6 - 1
6 CHANGING THE DATA COMMUNICATIONS MONITORING TIMES
MELSEC-Q
6.1 No-Reception Monitoring Time (timer 0) Setting
The no-reception monitoring time (timer 0) is the time for clearing the Q series C24 state when the Q series C24 was placed into the data receive wait state by trouble in the external device.
The Q series C24 monitors the reception interval in byte units at the start of data reception from the external device and ends monitoring when the preset last data is received and repeats this operation.
The following explains the no-reception monitoring time (timer 0) operation.
External device
PLC CPU
Data 1 Data 2 Data n-1
Monitoring time
1 byte
Data n
Data receive interval
(depends on the transmission rate, etc.)
Elapsed time reset
POINT
When changing the no-reception monitoring time (timer 0) default value by the sequence program and checking timer 0 with the new value at the Q series C24, after changing the default value, switch the mode as described in Chapter 15.
(1) Q series C24 operation by no reception monitoring time (timer 0)
Monitors the receive interval in byte units and returns the elapsed time to 0 each time one byte is received.
At time-out, the Q series C24 performs the following processing.
(a) Data communication using MC protocol
• Stores the error code to the MC protocol transmission error code storage area (buffer memory addresses 25A
H
, 26A
H
) for the target interface.
• Transmits a NAK message to the external device and enters the command message receive wait state.
6
6 - 2 6 - 2
6 CHANGING THE DATA COMMUNICATIONS MONITORING TIMES
MELSEC-Q
(b) Data communications using non procedure protocol (Format 0)
1) Data communications not using user frames
• Passes the receive data up to time-out to the Q series C24.
• Stores the error code to the data receive result storage area (buffer memory addresses 258
H
, 268
H
) for the target interface and turns on the reception abnormal detection signal (X4, XB) and waits to receive the next data.
(Example) Receiving according to the received complete code
(Received complete code: CR + LF (0D0A
H
))
When the LF is not received within the set time for timer 0 after reception of the CR, the abnormal reception detection signal to the PLC CPU turns ON and the received data at the CR is stored in the received data storage area of the buffer memory.
External device
Q series C24
C
R
( 1)
Timer 0
Set time
Abnormal reception detection signal
(X4/XB)
1 CR is treated as 1 byte of data included in the message.
2) Data communications using user frames
• When designating the last frame, an arbitrary part of data in the area starting from the start of the reception of the current message until time-out is read into the Q series C24, and the data in the last frame area is ignored (deleted).
• Stores the error code to the data receive result storage area (buffer memory addresses 258
H
, 268
H
) for the target interface and turns on the reception abnormal detection signal (X4, XB) and waits to receive the next data.
6 - 3 6 - 3
6 CHANGING THE DATA COMMUNICATIONS MONITORING TIMES
MELSEC-Q
(c) Data communication using non procedure protocol (Format 1)
The reception monitoring format 1 of the no-reception monitoring time (timer
0) is used for receiving a message for which the receive complete code and receive data count has not been preset. This occurs when the no-reception monitoring time (timer 0) runs out on the non procedure protocol.
• Data is received by the Q series C24 until the time is out, the receive data read request signal (X3, XA) turns ON, and the following data reception waiting condition occurs.
(Example) When receiving using the receive data count (Receive data count: 4 bytes)
After 3 bytes of data is received, the 3-byte data is stored in the received data storage area of the buffer memory by the time out
(timer 0) and the receive data read request signal to the PLC
CPU turns ON.
A B C
Timer 0
Set time
External device
Q series C24
Receive data read request signal
(X3/XA)
(d) Data communications using bidirectional protocol
• Ignores (deletes) the receive data from the start of reception of the current message to time-out.
• Stores the error code to the data receive result storage area (buffer memory addresses 258
H
, 268
H
) for the target interface.
• When the receive data complete, transmits a NAK message to the external device and waits to receive the next data.
6 - 4 6 - 4
6 CHANGING THE DATA COMMUNICATIONS MONITORING TIMES
MELSEC-Q
(2) Changing the no-reception monitoring time (timer 0)
(a) Changing the no-reception monitoring time (timer 0)
The no-reception monitoring time (timer 0) is designated by the number of transmitted characters (byte count) corresponding to the data communication rate set in the interface, and then it is registered on the GX
Configurator-SC's "Transmission control and others system setting" screen.
Adjust or set the value based on the specifications of the external device.
For details on the registration method of the no-reception monitoring time, see Section 8.4.5 of the User's Manual (Basic).
(b) No-reception monitoring time format specification in non procedure protocol
(Format 0/Format 1)
The no-reception monitoring time format in non procedure protocol is specified to use the no-reception monitoring time (timer 0) by the non procedure protocol and is registered on the "Transmission control and others system setting" screen.
For details on the registration method, see the User’s Manual (Basic)
Section 8.4.5.
REMARK
1) When changing the no-reception monitoring time (timer 0)
Find the result using the following expression and set the number of bytes or greater for the no-reception monitoring time (timer 0).
No-reception monitoring time (timer 0) = 1 +
Td Vbps
12000
(Round up fractions below decimal point.)
Td : Maximum delay time for external device output processing (ms)
Vbps: Transmission rate (bps)
(Example) Calculation of no-reception monitoring time (timer 0)
• Transmission rate (Vbps) : 9600bps
• Maximum delay time for external device output processing (Td)
: 50ms
No-reception monitoring time (timer 0) = 1 +
50 9600
12000
= 41 bytes
In this case, actual monitoring time is as follows:
41 bytes 12
1
/ 9600 1000 = 51.25ms
1 Number of transmit bits per byte (Fixed)
6 - 5 6 - 5
6 CHANGING THE DATA COMMUNICATIONS MONITORING TIMES
MELSEC-Q
2) When exchanging data with the external device through the Q series C24 RS-
422/485 interface and changing the no-reception monitoring time (timer 0)
No-reception monitoring time (timer 0) = 1 +
(Td + T1) Vbps
12000
(Round up fractions below decimal point.)
Td : Maximum delay time for external device output processing (ms)
T1 : External device side H/W gate OFF time (ms)
Vbps: Transmission rate (bps)
6 - 6 6 - 6
6 CHANGING THE DATA COMMUNICATIONS MONITORING TIMES
MELSEC-Q
6.2 Response Monitoring Time (timer 1) Setting
The response monitoring time (timer 1) clears the receive wait state of the device that receives the response message when trouble in the device that received the message does not return a response message (result) to the external device.
When the Q series C24 receives a message from the external device, it monitors the
PLC CPU processing time up to the start of transmission of the response message to the external device.
When a message was received, it monitors the external device processing time up to the start of reception of the response message from the external device.
The following describes the response monitoring time (timer 1) operation.
1 b yte
E xte rnal device
P L C C P U
D ata 1 D ata 2 D ata n-1 D ata n
D ata receive interval
(dep end s o n the tran sm ission rate, etc.)
M o nito ring tim e
E lap sed tim e re set
If on-demand data is transmitted before a response message during data communications using a MC protocol, the time up to the start of transmission of the on-demand data is monitored.
External device
Command message
PLC CPU On-demand data
Response message
Monitoring time
Elapsed time reset
(1) Q series C24 operation by response monitoring time (timer 1)
(a) When response monitoring time (timer 1) set to 0ms
After receiving a message, the Q series C24 does not monitor the time up to the start of transmission of a response message to the external device, but waits infinitely.
After transmitting a message, the Q series C24 does not monitor the time up to the start of reception of the response message from the external device, but waits infinitely.
(b) When response monitoring time (timer 1) is set to 100 ms or longer
After receiving a message, the Q series C24 monitors the time up to the start of transmission of a response message to the external device and returns the elapsed time to 0 at the start of transmission.
After transmitting a message, the Q series C24 monitors the time up to the start of reception of the response message from the external device and returns the elapsed time to 0 at the start of reception.
At time-out, the Q series C24 performs the following processing.
1) Data communications using a MC protocol
• Stores the error code to the MC protocol transmit error code storage area (buffer memory addresses 25AH, 26AH) for the target interface.
• Transmits a response message (NAK message) to the external device and waits to receive the next command message.
6 - 7 6 - 7
6 CHANGING THE DATA COMMUNICATIONS MONITORING TIMES
MELSEC-Q
2) Data communications using bidirectional protocol
• Stores the error code to the data transmission result storage area
(buffer memory addresses 257
H
, 267
H
) for the target interface and performs transmission processing abnormal completion.
• While waiting to transmit a response message, the Q series C24 does not check the response monitoring time.
(2) Changing the response monitoring time (timer 1)
The response monitoring time (timer 1) is registered on the GX Configurator-SC's
"Transmission control and others system setting" screen. For data communication using the MC protocol, set the response monitoring time so that it is longer than the message wait time. ( 1)
For details on the registration method of the response monitoring time, see
Section 8.4.5 of the User's Manual (Basic).
1 The message wait time is designated at the following locations.
• A compatible 1C frame: Designate in a command message
• QnA compatible 2C/3C/4C frame: GX Configurator-SC "MC protocol system setting" screen
POINT
When changing the response monitoring time (timer 1) default value (5 s), observe the following precautions.
(1) Data communications using an MC protocol
In any of the following cases make the default value the message wait time described in Section 6.4, or longer.
(a) When designating the monitor conditions with the following functions, set the maximum time matched to system operation.
• Word units random read (See Section 3.3.8 of Reference Manual.)
• Device memory monitor (See Section 3.3.9 of Reference Manual.)
(b) Access other than (a) above
1) When accessing a station connected (including multidrop link) to an external device, set the following value, or longer.
Response monitoring time > = Maximum number of scans required to process the command used connected station scan time
2) When accessing another station over a network system, set the default value to infinity or the following time, or longer.
Response monitoring time > = Maximum number of scans required to process the command used communications time
When setting the default value to infinity, check the external device response wait time and initialize the Q series C24 transmission sequence when time-out is generated. (See Reference Manual "Data designation item description" for each frame.)
See Appendix 3 of Reference Manual for the number of scans required by processing.
See Chapter 2 of Reference Manual for the communications time.
6 - 8 6 - 8
6 CHANGING THE DATA COMMUNICATIONS MONITORING TIMES
MELSEC-Q
POINT
(2) Data communications using bidirectional protocol
Set the default value to the following time, or longer.
(Sequence scan time 2) + 100 ms
6 - 9 6 - 9
6 CHANGING THE DATA COMMUNICATIONS MONITORING TIMES
MELSEC-Q
6.3 Transmission Monitoring Time (timer 2) Setting
The transmission monitoring time (timer 2) clears the wait state when the Q series C24 that is to transmit a message or response message (result) has entered the transmission end wait state due to trouble in the external device.
When the Q series C24 transmits a message, it monitors the wait time up to the end of transmission of the message.
When the Q series C24 received a message from the external device, it monitors the wait time up to the end of transmission of the response message.
The following explains the transmission monitoring time (timer 2) operation.
External device
PLC CPU
Message
Response message
Message
Response message
Monitoring time
Monitoring time
Elapsed time reset
If on-demand data is transmitted before a response message during data communications using an MC protocol, each time is monitored.
External device
PLC CPU
Command message
On-demand data
Response message
Monitoring time Monitoring time
Elapsed time reset
(1) Q series C24 operation by transmission monitoring time (timer 2)
(a) When transmission monitoring time (timer 2) is set to 0ms
The time until transmission of the message or response message is not monitored.
If the Q series C24 cannot transmit, it waits infinitely.
(b) When transmission monitoring time (timer 2) is set to 100 ms or longer
Monitors the time from completion of message or response message transmission preparations to the end of transmission and returns the elapsed time to 0 at the end of transmission.
At time-out, the Q series C24 performs the following processing.
1) Data communications using MC protocol
• While waiting for the end of transmission of the response message, the Q series C24 stores the error code to the data transmission result storage area (buffer memory addresses 257
H
, 267
H
) for the target interface.
The Q series C24 enters the state in which it waits to receive the next command message without sending a response message (NAK message) to the external device.
• During on-demand data transmission, the Q series C24 stores the error code to the on-demand execution result storage area (buffer memory addresses 256
H
, 266
H
) for the target interface.
• If transmission was terminated midway in either of the cases above, the Q series C24 does not transmit the remaining data.
6 - 10 6 - 10
6 CHANGING THE DATA COMMUNICATIONS MONITORING TIMES
MELSEC-Q
2) Data communications using non procedure protocol or bidirectional protocol
• While waiting for the end of transmission of a message, the Q series
C24 stores the error code to the data transmission result storage area
(buffer memory addresses 257
H
, 267
H
) for the target interface and performs transmission processing abnormal completion.
If message transmission was terminated midway, the Q series C24 does not transmit the remaining data.
• If waiting for the end of transmission of a response message, the Q series C24 stores the error code to the data receive result storage area (buffer memory addresses 258
H
, 268
H
) for the target device and turns on the reception abnormal detection signal (X4, XB). ( 1)
When the receive data read complete, the Q series C24 turns off the reception abnormal detection signal (X4, XB) and waits to receive the next command.
If transmission of the response message was terminated midway, the
Q series C24 does not transmit the remaining data.
1 When communicating using bidirectional protocol, it stores the error code in the data receive result storage area for the target interface. (The reception abnormal detection signal does not turn on.)
(2) Changing the transmission monitoring time (timer 2)
The transmission monitoring time (timer 2) is registered on the GX Configurator-
SC's "Transmission control and others system setting" screen.
For details on the registration method of the transmission monitoring time, see
Section 8.4.5 of the User's Manual (Basic).
POINT
The transmission monitoring time (timer 2) monitors the transmission termination time when the following states are generated.
• When DTR/DSR signal control is used and the DSR signal is turned off
(See Section 7.1.)
• When DC1/DC3 receive control is used and DC3 is received (See Section 7.2.)
• When the RS-232 interface CS signal is turned off (See Section 3.2.1 of User's
Manual (Basic).)
6 - 11 6 - 11
6 CHANGING THE DATA COMMUNICATIONS MONITORING TIMES
MELSEC-Q
REMARK
Criteria when changing the transmission monitoring time (time 2) setting
Find the transmission monitoring time (timer 2) time from the maximum delay time of external device message receive processing or response message transmission processing and the transmission time/byte (t) and change the set value.
• Number of bytes transmitted/second (n) = Transmission rate/number of transmit bits/byte
• Transmission time/byte (t) = 1000 (ms)/number of bytes transmitted/s (n)
• Transmission monitoring time (timer 2) = (Maximum external device processing delay time) + (transmission time/byte
(t) transmit byte count)
......100 ms units truncated
Under the following conditions, the transmission monitoring time (timer 2) is set to
300 ms
• Transmission rate
• Number of transmit bits/byte
: 9600 bps
• Maximum processing delay time : 200 ms
• Transmit byte count
: 11 (start bit: 1, data bits: 8, stop bits: 2)
: 3 bytes
6 - 12 6 - 12
6 CHANGING THE DATA COMMUNICATIONS MONITORING TIMES
MELSEC-Q
6.4 Message Wait Time Setting
The message wait time is used during data communications using a MC protocol.
It is the time for an external device that cannot receive the data immediately after it has been transmitted.
When the Q series C24 transmits a response message in reply to a command message received from the external device, transmission of the response message is delayed by the message wait time, or longer.
The following explains the message wait time operation for data communications using
QnA compatible 2C/3C/4C frame. (For A compatible 1C frames, the message wait time is designated in the command message.)
External device
PLC CPU
Command message
Response message
Message wait time
(1) Q series C24 operation by message wait time
1) When message wait time is 0 ms
If a response message can be transmitted, the Q series C24 immediately transmits the response message. A transmission wait time is not set.
2) When the message wait time is 10 ms or longer
If a response message can be transmitted, and the message wait time after reception of the command message has elapsed, the Q series C24 transmits the response message.
(2) Changing the transmission wait time
The transmission wait time is registered on the GX Configurator-SC's "MC protocol system setting" screen
For details on the registration method of the transmission wait time, see Section
8.4.6 of the User's Manual (Basic).
POINT
(1) If the external device that must wait a certain time before it can receive a response message after a command message was transmitted, set the message wait time as explained above.
Especially, for data communications with an external device connected to the
Q series C24 RS-422/485 interface, set the message wait time to the external device hardware gate OFF time or longer.
(2) The message wait time described here is the time for data communications using QnA compatible 2C/3C/4C frame.
6 - 13 6 - 13
7 DATA COMMUNICATIONS USING DC CODE TRANSMISSION
CONTROL
MELSEC-Q
7 DATA COMMUNICATIONS USING DC CODE TRANSMISSION CONTROL
The transmission control function controls (termination, restart) the transmission and reception of data between the Q series C24 and external device by turning transmission control signals on and off, or by transmitting and receiving DC codes (DC1, DC2, DC3,
DC4), or informs the range of validity for the data to the external device.
The transmission control function can be set for each Q series C24 interface. The Q series C24 uses the transmission control function set by the user to control data communications with external devices.
Set the transmission control function to match the specifications of the external device .
The table below shows the Q series C24 transmission control functions.
Transmission control function
Interface that can be controlled
Protocol that can be controlled
Kind of control
232 422/485 MC
Non procedure
Bidirectional
Note
DTR/DSR signal control
1
RS/CS signal control
CD signal control
DC code control
1
2
DTR control
DSR control
2
(Ignored)
Cannot be used simultaneously with DC control.
One is selected.
Normal control.
The cable wiring depends on whether or not control is used.
With half-duplex communications, control is necessary.
DC1/DC3 transmission control
DC1/DC3 reception control
DC2/DC4 transmission control
DC2/DC4 reception control
Cannot be used simultaneously with
DTR/DSR signal control.
One is selected.
: Possible (transmission control used)
: Invalid
1 When using full-duplex communications with bidirectional protocol data communications, see Section 7.3 of User's Manual (Basic).
2 See Section 3.2.1 (1) of User's Manual (Basic) and check Q series C24 operation according to the RS and CS signal control contents and CD terminal check designation.
POINT
When the Q series C24 is started, DTR/DSR signal control and RS/CS signal control are enabled.
7
7 - 1 7 - 1
7 DATA COMMUNICATIONS USING DC CODE TRANSMISSION
CONTROL
MELSEC-Q
7
7.1 Control Contents of DTR/DSR (ER/DR) Signal Control
This control uses the RS-232 interface DTR/DSR signals to inform the external device whether or not the local station is ready to receive data.
The Q series C24 uses the DTR (ER) signal to inform the external device whether or not the local station is ready to receive data and uses the DSR (DR) signal to check if the external device is ready to receive data.
(Example)
(Terminate) (Restart)...Continue
External device
PLC CPU
Data 1-1
Data 1-2
Data 1-2
(Terminate)
Data 2-2
(Restart)...Continue
DTR signal
DSR signal
(1) Q series C24 DTR control
(a) Q series C24 DTR control
The Q series C24 uses the DTR signal to inform the external device whether or not it is ready to receive data.
The data transmitted from the external device by non procedure protocol is stored to the buffer memory receive data storage area through the OS area. (See User's Manual (basic) Section 6.1.2 1.)
For the following conditions, the receive data is temporarily stored to the
OS area and is transferred to the receive data storage area when the present receive data read processing is complete.
1) Receive data size exceeds the size of the buffer memory area when
"receive data storage area < receive data length data" was received.
2) The data was received before the sequence program read the previously received data.
The Q series C24 turns the DTR signal on/off as shown below, depending on the size of the vacant OS area.
• Vacant area 64 bytes (default) or less ......... OFF
• Vacant area 263 bytes (default) or more ..... ON
ON ON
DTR signal
OFF
ON : Ready to receive
OFF : Not ready to receive
Receive preparations complete
OFF
Q series C24
(OS area)
Q series C24
(OS area)
8448 bytes
(Data storage)
Vacant area
8448 bytes
64 bytes or less
(default)
(Data storage)
Vacant area
263 bytes or more
(default)
After read complete from sequence program
7 - 2 7 - 2
7 DATA COMMUNICATIONS USING DC CODE TRANSMISSION
CONTROL
MELSEC-Q
(b) Specification of free OS area
The limit of free OS area for data reception under the DTR/DSR (ER/DR) signal control is specified in GX Configurator-SC's "Transmission control and others system setting" (See User's Manual (Basic), Section 8.4.5.).
When it reaches the limit, this status is notified to disable data reception.
The set values must satisfy the following condition.
"Transmission control start free area < Transmission control end free area"
1) Transmission control start free area specification (Address:
2012
H
/2112
H
)
Specifies an available capacity in the OS area so that the full status is notified to disable the data reception (DTR signal is OFF).
• Transmission control start free area: 64 to 4095 (Default: 64)
2) Transmission control end free area specification (Address:
2013
H
/2113
H
)
Specifies an available capacity in the OS area so that data reception is enabled by notification (DTR signal is ON).
• Transmission control end free area: 263 to 4096 (Default: 263)
REMARK
• Receive data clear described in Section 6.1.4 of User's Manual (Basic) clears the
OS area simultaneously with clearing of the receive data storage area.
• If more data is received when the OS area mentioned above are 0 bytes, an SIO error is generated and the data received until the OS area becomes vacant is ignored. At this time, the SIO signal is turned on. (See User's Manual (Basic)
Section 10.1.1.)
(2) Q series C24 DSR control
The Q series C24 uses the DSR signal to detect whether or not the external device is ready to receive data and to control data transmission to the external device as shown below, depending on whether the DSR is on/off.
1) If the DSR signal is ON and there is send data, the Q series C24 transmits it to the external device.
2) If the DSR signal is OFF, even if there is send data, the Q series C24 does not transmit it to the external device.
When the DSR signal is turned on, the Q series C24 transmits the send data to the external device.
7 - 3 7 - 3
7 DATA COMMUNICATIONS USING DC CODE TRANSMISSION
CONTROL
MELSEC-Q
7.2 Control Contents of DC Code Control
This control uses the Q series C24 transmission control data to inform the external device whether or not local station is ready to receive data and the valid range of the send and receive data.
The four kinds of Q series C24 DC code control shown below are available. These control functions can be used simultaneously.
(1) DC1/DC3 transmission control, DC1/DC3 reception control
The Q series C24 informs the external device whether or not local station is ready to receive data by transmitting the DC1 and DC3 signals and checks whether or not the external device is ready to receive data by receiving the DC1 and DC3 signals.
DC1 Control data that informs the external device that the Q series C24 is ready to receive data
DC3 Control data that informs the external device that the Q series C24 is not ready to receive data
(Example)
External device
PLC CPU
(Terminate)
(Restart)...Continue
Data 1-1
D
C
3
D
C
1
Data 1-2
D
C
3
D
C
1
Data 2-1 Data 2-2
(Terminate) (Restart)...Continue
(a) Q Series C24 DC1/DC3 transmission control and free OS area specification
The control is performed in the same as those described in Section 7.1 (1)
DTR control and the free OS area specification are the same as those described in Section 7.1 (1) (b).
The Q series C24 transmits DC1 or DC3 to the external device instead of turning the DTR signal on/off.
For the DC1 and DC3 transmit timing, replace DTR signal ON/OFF as shown below.
(DTR control) (DC1, DC3 transmission control)
DTR signal OFF= DC3 transmit .......Transmitted when the vacant OS area drops to 64 bytes (default) or less
DTR signal ON = DC1 transmit.........Transmitted when the vacant OS area reaches 263 bytes (default) or more
External device
PLC CPU
Data
D
C
3
D
C
1
Data
7 - 4 7 - 4
7 DATA COMMUNICATIONS USING DC CODE TRANSMISSION
CONTROL
MELSEC-Q
REMARK
• Receive data clear described in Section 6.1.4 of User's Manual (Basic) clears the
OS area simultaneously with clearing of the receive data save area.
• If more data is received when the vacant OS area mentioned above is 0 bytes, an
SIO error is generated and the data received until the OS area becomes vacant is ignored. At this time, the SIO LED is turned on. (See Section 10.1.1 of User's
Manual (Basic).)
(b) Q series C24 DC1/DC3 reception control contents
1) When the Q series C24 receives DC3 from the external device, it terminates data transmission.
The sequence program cannot read the received DC3 signal.
2) When the Q series C24 receives DC1 from the external device, it restarts data transmission.
(The Q series C24 resumes transmission from the data terminated on
DC3 reception.)
The sequence program cannot read the received DC1 signal.
External device
D
C
3
D
C
1
Q series C24
Data Data
3) Once DC1 is received, subsequent DC1 are ignored and are removed from the receive data.
POINT
(1) The following describes the state of the Q series C24 when the power is turned on, the CPU is reset, or the mode is switched during DC1, DC3 transmission control and DC1/DC3 reception control.
(2) DC1 is not transmitted to the external device.
• This is the same state as when DC1 was transmitted.
• The same state as when DC1 was received even if DC1 is not received from the external device.
(2) DC2/DC4 transmission control, DC2/DC4 reception control
The Q series C24 encloses the send data from the local station in the DC2 and
DC4 codes and transmits it to the external device and processes the data received from an external device enclosed in the DC2 and DC4 codes as valid data.
DC2...Control data that informs the external device that the data following it is the start of the valid data
DC4...Control data that informs the external device that the data immediately preceding it is the end of the valid data
(Example)
External device
PLC CPU
DC2
Data
DC4
DC2 Data DC4
DC2 Data
7 - 5 7 - 5
7 DATA COMMUNICATIONS USING DC CODE TRANSMISSION
CONTROL
MELSEC-Q
(a) Q series C24 DC2/DC4 transmission control contents
When transmitting data to an external device, the Q series C24 adds the
DC2 code to the head of the send data and the DC4 code to the end of the send data.
External device
PLC CPU
D
C
2
Data
D
C
4
D
C
2
E
N
Q
Data
D
C
4
Transmit order
(Non procedure protocol)
The DC2 and DC4 code are also added when MC protocol is used.
(b) Q series C24 DC2/DC4 reception control contents
1) When the Q series C24 receives DC2 from the external device, it processes the receive data up to DC4 as valid data.
The sequence program cannot read the received DC2 code.
2) When the Q series C24 receives DC4, it ignores the receive data up to immediately before DC2 as invalid data.
The sequence program cannot read the received DC4 code.
(Non procedure protocol)
1
D
C
2
Data
D
C
4
Arbitrary data
Transmit order
(Bidirectional protocol)
D
C
2
Data
D
C
4
External device
PLC CPU
Stored to Q series C24 buffer memory or OS area
Ignored by the Q series C24
Stored to Q series C24 buffer memory or OS area
3) Once DC2 is received, subsequent DC2 are ignored and are removed from the receive data.
1 MC protocol A
comoatible 1C frame
format 1
External device
D
C
2
E
N
Q
D
C
4
(3) The transmission control method and changing the DC code
Switching between DC code control method and DTR/DSR control as well as changing of the DC code are registered on the GX Configurator-SC's
"Transmission control and others system setting" screen.
For details on the registration method, see Section 8.4.5 of the User's Manual
(Basic).
7 - 6 7 - 6
7 DATA COMMUNICATIONS USING DC CODE TRANSMISSION
CONTROL
MELSEC-Q
7.3 Precautions when Using the Transmission Control Functions
The following describes the precautions to be observed when using the Q series C24 transmission control functions.
(1) Agreement between external device and PLC CPU
The external device and PLC CPU must agree to the following.
1) Whether or not a transmission control function is to be used. If a control function is used, which control is to be used for data communications.
2) Control timing.
3) DC1 to DC4 codes when DC control is performed.
(The DC1 to DC4 codes used can be arbitrarily changed.)
(2) Transmission control function usage conditions
1) DTR/DSR control and DC code control cannot be used at the same time.
Select one of them using the GX Configurator-SC registration.
2) When using DTR/DSR control, connect the Q series C24 DTR and DSR signals to the external device.
(3) Transmission control function setting
Set a transmission control function that can control the target interface.
If a function that cannot control the target interface is set, the set contents are invalid.
(4) Setting of transmission control function during linked operation
When the two Q series C24 interfaces are linked (see Section 4.4.2 of User's
Manual (Basic), set the transmission control function of only the interface that must be controlled.
Set the other interface to "Do not use transmission control function" (set value when directly set to the buffer memory: 0001
H
).
(5) DC code control
1) DC1/DC3 transmission control and DC1/DC3 reception control are possible when full-duplex communications is used to communicate data between the
Q series C24 and external devices.
Do not use DC1/DC3 control with half-duplex communications.
2) The same data as the DC1 to DC4 codes cannot be included in the user data.
To handle the same data as a DC code as user data, do the following.
• Use DTR/DSR control.
• Change the DC code.
• Do not use the transmission control functions.
7 - 7 7 - 7
7 DATA COMMUNICATIONS USING DC CODE TRANSMISSION
CONTROL
MELSEC-Q
POINT
If the user data received from the external device includes the relevant DC code when DC1/DC3 reception control and DC2/DC4 reception control are used, the Q series C24 uses the corresponding DC code control.
If the user data transmitted from the PLC CPU includes a DC code, it is sent unchanged.
(6) Handling of DTR and DSR signals when DTR/DSR control is not used
When the DTR/DSR control function is not used, the Q series C24 handles the
DTR and DSR signals as described below.
1) Leaves the DTR signal ON.
2) Ignores the DSR signal ON/OFF state.
7 - 8 7 - 8
8 DATA COMMUNICATIONS USING HALF-DUPLEX
COMMUNICATIONS
MELSEC-Q
8 DATA COMMUNICATIONS USING HALF-DUPLEX COMMUNICATIONS
For data communications between the Q series C24 and an external device using the
RS-232 interface, it is set so that the Q series C24 and the external device do not transmit data at the same time.
The QJ71C24 (N)-R2 can be set for each interface.
When the Q series C24 is started, full-duplex communications is set. The user can change the communications method to match the specifications of the external device.
POINT
Since half-duplex communications does not have to be set in the following cases, you do not have to read this section.
(1) When data is only transmitted or receive during non procedure protocol data communications.
(2) When it is designated in the external device that no data transmission is performed from the external device to the Q series C24 unless so directed by the Q series C24.
8.1 Half-duplex Communications
The following describes the differences between full-duplex communications and halfduplex communications.
Since the Q series C24 uses the communications method designated by the user to control PLC CPU communications, control by sequence program is unnecessary.
(1) Full-duplex communications
This communication method uses telephone conversation format image to communicate data with the external device.
The Q series C24 can receive data while transmitting data to the external device.
It can also transmit data while receiving data from the external device.
External device
PLC CPU
Data A-1
Data B-1
Data B-2
Data A-2
(2) Half-duplex communications
This communications method uses transceiver conversation format image to communicate data with the external device.
If the Q series C24 receives data from the external device while transmitting data to the external device, it controls data transmission and reception according to
"Simultaneous transmission priority/non-priority designation".
The Q series C24 does not transmit data while it is receiving data from the external device.
External device
PLC CPU
Data A-1
Data B-1 Data B-2
Data A-2
8
8 - 1 8 - 1
8 DATA COMMUNICATIONS USING HALF-DUPLEX
COMMUNICATIONS
MELSEC-Q
8
8.2 Data Transmission and Reception Timing
Half-duplex communications uses the Q series C24 RS-232 interface CD and RS signals to control communications.
If the external device can transmit and receive data according to ON/OFF of the Q series C24 RS and CD signals as shown below, half-duplex communications is possible.
RS signal............. Turned ON/OFF by the Q series C24 as shown below.
When data is transmitted from the Q series C24, this signal is turned
ON. When transmission is complete, turn this signal OFF.
CD signal............. Turned ON/OFF by at the external device as shown below.
When data is transmitted from the external device, this signal is turned ON. When transmission is complete, turn this signal OFF.
The following describes the half-duplex communications data transmission and reception timings by Q series C24 CD signal and RS signal.
(1) Timing when transmitting data from external device
Transmit data by controlling the Q series C24 CD signal according to the
"simultaneous transmission priority/non-priority designation" registered in
"Transmission control and others system setting" screen of the GX Configurator-
SC (See Section 8.4.5 of User’s Manual (Basic))
(a) When Q series C24 is designated "priority"
External device
Data A
Data B
Terminate data transmission.
Retransmission
Data B
PLC CPU
Data C
Since the Q series C24 has priority, it continues to transmit even if the DC signal is turned ON.
Data C
SD (Send Data)
Store this data at the external device.
RS (Send Request)
1)
4)
5)
CS (Send possible)
CD (Receive Carrier
Detect)
2)
The Q series C24 ignores the receive data. ( 1)
RD (Receive Data)
Data A
3)
Data B
Data B
1) When transmit data, check the RS signal. If the RS signal is OFF, turn on the CD signal. If the RS signal is ON, wait until it is turned OFF, then turn ON the CD signal.
2) Transmit data after the CD signal is turned ON.
3) After data transmission is complete, turn off the CD signal.
4) If the RS signal was turned ON during data transmission, terminate data transmission and turn OFF the CD signal and perform data transmission processing. (Simultaneous transmission generated)
5) After transmission from the Q series C24 is complete, retransmit all the data terminated at step 4.
1 Take the following measures between the communicating devices as a countermeasure against ignoring of the receive data by the Q series C24.
• Transmit and receive a response message in reply to data transmission
• Retransmit the data due to response message time-out check or generation of a timeout error (external device side)
8 - 2 8 - 2
8 DATA COMMUNICATIONS USING HALF-DUPLEX
COMMUNICATIONS
MELSEC-Q
(b) When Q series C24 is designated "non-priority"
External device
PLC CPU
SD (Send Data)
Data A
Continue data transmission.
Data B
Data C-1
Data C-1
Data C-2
Since the Q series C24 does not have priority, when the CD signal is turned
ON, it terminates transmission.
Retransmission
See (2) for the transmission contents.
Data C-2
RS (Send Request)
1)
4)
CS (Send Possible)
CD (Receive Carrier
Detect)
2)
5)
The Q series C24 stores the receive data.
RD (Receive Data)
Data A
3)
Data B
The contents of steps 4 and 5 below are different from those of item (a).
1) When transmitting data, check the RS signal. If the RS signal is OFF, turn ON the CD signal. If the RS signal is ON, wait until it is turned OFF, then turn ON the CD signal.
2) After the CD signal is turned ON, transmit the data.
3) After data transmission is complete, turn OFF the CD signal.
4) The external device will continue to transmit data to the Q series C24 even if the RS signal is turned ON during data transmission.
(Simultaneous transmission generated)
5) After transmission from the external device is complete, data is transmitted from the Q series C24 to the external device. (See (2).)
REMARK
When using the DTR/DSR transmission control function described in Chapter 7, transmit data from the external device to the Q series C24 as shown below in both cases (a) and (b) above.
• When the Q series C24 DTR signal is turned OFF, terminate data transmission.
• When the Q series C24 DTR signal is turned ON after data transmission was terminated, restart data transmission (transmit from the terminated data).
8 - 3 8 - 3
8 DATA COMMUNICATIONS USING HALF-DUPLEX
COMMUNICATIONS
MELSEC-Q
(2) Timing when data is transmitted from the Q series C24
The Q series C24 RS signal is controlled and data is transmitted according to the
"simultaneous transmission priority/non-priority" value registered in
"Transmission control and others system setting" screen of the GX Configurator-
SC. (See Section 8.4.5 of User's Manual (Basic)).
(a) When Q series C24 is designated "priority"
Data C-1
Terminate data transmission
External decvice
PLC CPU
Data A
Retransmission
Data C
SD (Send data)
Send request
1) 2)
Within 1 ms
Approx 2 ms to
128 ms
( 1)
Data A
3)
Send request
Data B
Since the Q series C24 has prioriry, it continues to transmit even if the
CD signal is turned
ON.
Store thie data at the external device.
Data B
RS (Send Request)
5)
CS (Send Possible)
4)
CD check
CD (Receive Carrier
Detect)
CD check CD check
RD (Receive Data)
Data C-1 Data C
The Q series C24 ignores the receive data.( 2)
The Q series C24 stores the receive data.
1) When transmitting data, check the Q series C24 CD signal. If the CD signal is OFF, turn on the Q series C24 RS signal.
If the CD signal is ON, wait until it is turned OFF, then turn ON the RS signal.
2) After the RS signal is turned ON, transmit the data.
3) After data transmission is complete, turn off the RS signal.
4) If the CD signal is turned ON during data transmission, the Q series
C24 continues to transmit data to the external device. (Simultaneous transmission generated)
5) After transmission from the Q series C24 is complete, transmit all the data terminated at step 4 from the external device to the Q series C24.
1 The time from RS signal ON to the start of transmission depends on the data transmission rate.
The higher the transmission rate, the shorter the time up to the start of transmission.
2 Do the following between the communicating devices as a countermeasure against ignoring of the receive data by the Q series
C24.
• Transmit and receive a response message in reply to data transmission.
• Time-out check of the response message and data transmission due to time-out error (external device side).
8 - 4 8 - 4
8 DATA COMMUNICATIONS USING HALF-DUPLEX
COMMUNICATIONS
MELSEC-Q
(b) When Q series C24 designated "non-priority"
External device
PLC CPU
SD (Send Data)
Send request
1)
Data A
Within 1 ms
2)
( 1)
Data A
3)
Send request
Data C
Data B
Since the Q series C24 does not have priority, when the CD signal is turned ON it terminates transmission.
Data B
Continue data transmission.
Data B
Transmission wait time
( 1)
( 2)
Data B
RS (Send Request)
CS (Send Possible)
CD (Receive Carrier
Detect)
CD check CD check
4)
CD check 5)
CD check
RD (Receive Data)
Data C
The Q series C24 stores the receive data.
The contents of steps 4 and 5 below are different from those of item (a).
1) When transmitting data, check the Q series C24 CD signal. If the CD signal is off, turn on the Q series C24 RS signal.
If the CD signal is on, wait until it is turned off, then turn on the RS signal.
2) After the RS signal is turned on, transmit the data.
3) After data transmission is complete, turn off the RS signal.
4) If the CD signal is turned on during data transmission, terminate data transmission and turn off the RS signal and perform the data receive processing. (Simultaneous transmission generated)
5) After transmission from the external device is complete, transmit the data terminated at step 4 from the beginning or from the last data transmitted.
2
1 The data size set to "Simultaneous transmission priority/non-priority" by
GX Configurator-SC is not transmitted.
2 Transmit from the beginning or from the data transmitted immediately before transmission was terminated, according to the contents set to
"Retransmission time transmission method by GX Configurator-SC".
REMARK
When using the DTR/DSR transmission control function described in Chapter 7, transmit data from the Q series C24 to the external device as shown below in both cases (a) and (b) above.
• When the Q series C24 DSR signal is turned OFF, terminate data transmission.
• When the Q series C24 DSR signal is turned on after data transmission was terminated, restart data transmission (transmit from the terminated data).
8 - 5 8 - 5
8 DATA COMMUNICATIONS USING HALF-DUPLEX
COMMUNICATIONS
MELSEC-Q
8.3 Changing the Communication System
To change the data communication mode from full-duplex communication to halfduplex communication, registration on the GX Configurator-SC's "Transmission control and others system setting" screen is required.
The following explains setting items for changing the communication system.
For more details on the registration method of the communication system, see Section
8.4.5 of User's Manual (Basic).
(1) RS-232 communication system designation
Designate either full-duplex or half-duplex communication.
(2) Simultaneous transmission priority/non-priority designation
When the Q series C24 and the external device start data transmission simultaneously in half-duplex mode, designate whether to continue (priority) or stop (non-priority) transmission from the Q series C24.
Designated values "1" to "255" for setting "non-priority" will be the transmission wait time that elapses from when the resumption of data transmission becomes available until data is actually sent.
(3) Retransmission time transmission method designation
When "half-duplex communication" and "non-priority" are set as indicated above, this setting becomes valid. When the Q series C24 and the external device begin transmission simultaneously, if the Q series C24 stops and then restarts transmitting, designate whether the stopped message will be transmitted from the beginning ("resend") or whether transmission will continue after the stopped message ("not resend").
(4) RS-232 CD terminal check designation
When using half-duplex communication, set the "CD terminal check designation" to on.
8 - 6 8 - 6
8 DATA COMMUNICATIONS USING HALF-DUPLEX
COMMUNICATIONS
MELSEC-Q
8.4 Connector Connections for Half-duplex Communications
The following explains the functions of the connector that connects the Q series C24 and external device when half-duplex communications is used.
Connect the Q series C24 and external device based on (1) and (2) below.
(1) Connect the Q series C24 RS signal to one of the external device half-duplex communications signals (CS, DSR, or CD signal).
(2) Connect the Q series C24 CD signal to one of the external device half-duplex communications signals (RS or DTR signal).
(3) The half-duplex communications described in this section cannot be performed when an RS-232 and RS-422 converter is used.
(Connection example)
Q series C24
Signal name Pin No.
CD
RD(RXD)
SD(TXD)
DTR(ER)
SG
DSR(DR)
1
2
3
4
5
6
RS(RTS)
CS(CTS)
RI(CI)
7
8
9
Cable connection and signal direction
External device
Signal name
CD
RD(RXD)
SD(TXD)
DTR(ER)
SG
DSR(DR)
RS(RTS)
CS(CTS)
8 - 7 8 - 7
8 DATA COMMUNICATIONS USING HALF-DUPLEX
COMMUNICATIONS
MELSEC-Q
8.5 Half-duplex Communications Precautions
The following describes the precautions to be observed when using half-duplex communications.
(1) Half-duplex communications system configuration and functions
Half-duplex communications is possible only with a system that connects the
PLC CPU and external device in a 1: 1 configuration.
(Half-duplex communications can be dedignated)
External device
(Half-duplex communications cannot be designated)
External device
RS-232 RS-232
CPU CPU CPU CPU
QC24
RS-422/485
(2) Agreement and confirmation between external device and PLC
CPU
Agree and confirm the following items between the external device and the PLC
CPU.
1) Whether or not half-duplex communications can be performed by Q series
C24 RS signal and CD signal.
2) Q series C24 RS signal and CD signal ON/OFF timing.
3) Q series C24 and external device data transmission timing.
4) RS-232 cable connection method.
(3) Transmission control
When the transmission control functions described in Chapter 7 are used, DC code control DC1/DC3 transmission control and DC1/DC3 reception control cannot be used with half-duplex communications. Therefore, do not designate them.
8 - 8 8 - 8
9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA
COMMUNICATION
MELSEC-Q
9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA
COMMUNICATION
User frames are used to register some, or all, of the messages exchanged between an external device and the Q series C24 in advance and use them to check the send data or receive data.
The following functions can use Q series C24 user frames to transmit and receive data.
• MC protocol on-demand function. (See Chapter 10)
• Non procedure protocol data transmit and receive functions. (See Chapter 11)
Data can be transmitted and received by registering the corresponding user frames to the Q series C24 in advance to match the data contents that are transmitted and received between the external device and the Q series C24.
This chapter explains the data that can be registered, the data contents that are transmitted and received, and registering to the Q series C24 of user frames that can be used in data communications with the external device.
See Chapters 10 and 11 for a description of how each data communications function uses the user frames.
9.1 User Frame Types and Contents During Communication
This section explains the kinds of user frames handled by the Q series C24 and the data contents that are transmitted and received.
The following two kinds of user frames are available. Either kind can be used.
User frame (Frame described in Section 9.1.1)
User frame
(Generic term)
Default registration frame (Frame described in Section 9.1.2)
9.1.1 User frames to be registered and used by the user
The following explains the registered data, data contents that are transmitted and received, and how the Q series C24 handles user frames registered the Q series C24
Flash ROM or buffer memory by the user.
(1) General description
User frames registered by the user are frames that contain arbitrary data that matches the specifications of the external device. The data contents are selected by the user.
(2) User frame registering
(a) Up to 231 user frames can be registered, read, and deleted at the Q series C24.
1) Q series C24 Flash ROM
(number that can be registered : Maximum 200, frame No.: 3E8
H
to 4AF
H
)
2) Q series C24 buffer memory
(number that can be registered : Maximum 31, frame No.: 8001
H
to 801F
H
)
(b) Up to 80 bytes (80 en characters) of data can be registered as 1 user frame.
9
9 - 1 9 - 1
9
9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA
COMMUNICATION
MELSEC-Q
(c) User frames can include data for handling the variable data (sum check code, Q series C24 station No., etc.) shown in (4) as a part of user frames.
(d) User frames can be overwritten to the Q series C24 buffer memory. (The old contents are destroyed.)
(e) The registration destination for the user frame can be divided into the following usage.
• After data communication has started, register the user frames without changes to buffer memory and use. (Frame No: 3E8
H
to 4AF
H
)
• After data communication has started, register the user frames with changes to buffer memory and use. (Frame No: 8001
H
to 801F
H
)
(3) Data that can be registered as user frame
Up to 80 bytes of data can be registered by combining 1 byte of register code
01
H
to FE
H
data and 2 bytes of register code FF
H
+ 00
H
to FF
H
+ FF
H data.
(a) One byte of register code (01
H
to FE
H
) data
This is the register code for transmitting and receiving the register code (01
H to FE
H
) data.
(b) Two bytes of register code (FF
H
+ 00
H
) to (FF
H
+ FF
H
) data
This is the register code for transmitting and receiving the variable data
(Sum check code, Q series C24 station No., etc.) shown in (4) as part of the user frame.
FF
H
is the register code of the first byte for handling variable data.
(4) Variable data
"Variable data" is the generic term for the following data.
These variable data can be handled as part of a user frame.
• Sum check code whose objective is an arbitrary range in the transmit and receive messages.
• Horizontal parity code whose objective is a determined range in the transmit and receive messages.
• Two's complement sum check code whose objective is a determined range in the transmit and receive messages.
• Q series C24 station No.
• One byte data in data transmission (NULL: Code 00
H
)
One byte of arbitrary data in data reception. (Used to handle an arbitrary byte of data as part of the user frame during receiving check by the Q series C24.)
(a) Variable data designation method
Variable data is designated by combining write code FF
H
and the data codes shown in the table below.
The sum check code, Q series C24 station No., and other variable data can be handled according to FF
H
of the first byte and 00
H
to FF
H
of the second byte.
FF
H
00
H to
FF
H
2nd byte
1st byte
(b) Variable data designation contents, data contents transmitted and received, and handling by the Q series C24
The table below shows the register codes (FF
H
+00
H
) to (FF
H
+ FF
H
) combinations for handling variable data, the data contents that are transmitted and received, and how the Q series C24 handles the data.
Combinations other than those shown in the table cannot be registered.
9 - 2 9 - 2
9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA
COMMUNICATION
MELSEC-Q
Changeable data register code
1st byte 2nd byte
Data contents transmitted and received/Q series C24 handling
00
01
H
H
Transmission: Transmits the data code 00
H
(NUL) data (1 byte).
Reception: Skips the given part (1 byte) of the receive user frame. (Skips the check and performs receive processing.)
Transmits and receives the station No. set in the GX Developer switch setting as 1-byte binary code data
(00
H
to 1F
H
).
04
H
( 1) Transmits and receives the horizontal parity code in the calculation range using 1 byte of binary code data
05
H
( 1) Transmits and receives the horizontal parity code in the calculation range using 2-byte ASCII code data
0A
H
( 1) Transmits and receives the horizontal parity code in the calculation range using 1 byte of binary code data
FF
H
0B
H
( 1) Transmits and receives the horizontal parity code in the calculation range using 2-byte ASCII code data
11
H
( 1)
17
H
( 1)
Transmits and receives the two's complement sum check code in the calculation range.
EE
H
F0
H
F1
H
F3
H
F4
H
F6
H
Transmits and receives the sum check code in the calculation range. ( 2)
F7
H
F9
H
FF
H
Transmits and receives the register code FF
H
data (1 byte).
User frame
(specified as the first one)
;
Calculation range ( 3)
—
Range 1
Range 2
Range 1
Range 2
Range 1
Range 2
—
Detailed explana-tion
1)
2)
3)
4)
5)
(specified as the second one)
1 For usage of the register code, there are restrictions on versions of the Q series
C24.
Refer to the User’s Manual (Basic) Section 2.7 for how to check the version.
2 During data communication using a user frame that handles the last frame, the contents of the "sum check code" set in the transmission setting using the GX
Developer switch setting will be ignored.
3 Calculation ranges for the register codes
(specified as the third one)
(specified as the fourth one)
User frame
(first frame) Arbitrary data
User frame
(last frame)
A 1 (12AB
H
) 5 6 7 8
C
R
L
F
;
A 1 (12AB
H
)
C
R
L
F
02
H
00
H
3B
H
41
H
31
H
AB
H
12
H
35
H
36
H
37
H
38
H
03
H
0C
H
02
H
0D
H
0A
H
Range 1
02
H
00
H
3B
H
41
H
31
H
AB
H
12
H
03
H
32
H
01
H
0D
H
0A
H
Range 1
Range 2
Range 2
(Calculation range when receiving data)
(Calculation range when transmitting data)
Range 1
When transmitting: Calculation includes everything from the data following the first frame (first one frame only when multiple user frames have been specified) to immediately before the register code. (Except the transparent code designation additional code data shown in
Chapter 12)
When receiving: Calculation includes everything from the data following the first frame to immediately before the register code. (Except the transparent code designation additional code data shown in Chapter 12)
Range 2
When transmitting and receiving: Calculation includes everything from the head of the message to immediately before the register code.
(Except the transparent code designation additional code data shown in Chapter 12)
9 - 3 9 - 3
9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA
COMMUNICATION
MELSEC-Q
1) Q series C24 processing corresponding to register codes FF
H
and 00
H
The following uses an example to describe the processing performed by the Q series C24 when it receives a user frame part corresponding to register codes FF
H
and 00
H
.
Assume that a user frame containing the data codes 02
H
, FF
H
, 00
H
, and
3B
H
was set as receive user frame No. 3EA
H
.
• When the Q series C24 receives the 3 bytes of data "STX, arbitrary data
(1 byte), ; ", it processes them as if user frame No. 3EA
H
was received.
• The Q series C24 does not check the 2 bytes described above.
Receive data
S
T
X
1
:
A B
02
H
31
H
3B
H
41
H
42
H
Receive data code
Check
If the 02
H
and 3B
H
data parts match, they are processed as if user frame No. 3EA
H
mentioned above was received
2) Transmission/reception data corresponding to register codes FF
H
and 01
H
The Q series C24 transmits and receives the user frame part corresponding to register codes FF
H
and 01
H
by representing the station
No. set in the GX Developer switch setting as 1-byte binary data. See the first frame part shown in the illustration in item 3 for an example.
3) Transmission/reception data corresponding to register codes FF
H
+
04
H
, FF
H
+ 05
H
, FF
H
+ 0A
H
, and FF
H
+ 0B
H
.
• For FF
H
+ 04
H
and FF
H
+ 0A
H
The horizontal parity code that calculates the range for the transmission/reception data (message) is expressed as 1 byte of binary data and then transmitted and received.
The difference between FF
H
+ 04
H
and FF
H
+ 0A
H
is the difference in the calculation range.
• For FF
H
+ 05
H
and FF
H
+ 0B
H
The horizontal parity code that calculates the range for the transmission/reception data (message) is expressed as 2-byte
ASCII code data and then transmitted and received from the upper digit. The difference between FF
H
+ 05
H
and FF
H
+ 0B
H
is the difference in the calculation range.
Examples of the transmission and reception data arrangement of the horizontal parity codes are shown below. (One first frame and one last frame each)
(Example 1) For register code FF
H
+ 04
H
User frame
(first frame)
Arbitrary data User frame
(last frame)
(Example 2) For register code FF
H
+ 05
H
User frame
(first frame)
Arbitrary data User frame
(last frame)
User frame register code
02
H
FF
H
+01
H
3B
H
S
X
Station
No.
;
1 2 3 4
03
H
FF
H
+04
H
0D
H
0A
H
T
X
Horizontal parity code
C
R
L
F
User frame register code
02
H
FF
H
+01
H
3B
H
S
X
Station
No.
;
1 2 3 4
03
H
FF
H
+05
H
0D
H
0A
H
T
X
Horizontal parity code
C
R
L
F
Transmission/ reception data code
02
H
00
H
3B
H
31
H
32
H
33
H
34
H
03
H
Calculation range
07
H
0D
H
0A
H
Transmission/ reception data code
02
H
00
H
3B
H
31
H
32
H
33
H
34
H
03
H
30
H
37
H
0D
H
0A
H
Calculation range
9 - 4 9 - 4
9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA
COMMUNICATION
MELSEC-Q
• How to calculate the horizontal parity code
This is a numeric value obtained by calculating the XOR for the subject data and then converting it to ASCII code. (In the case of the example)
"1" (31
H
) 0011 0001
XOR
"2" (32
H)
0011 0010 = 0000 0011
XOR
"3" (33
H
)
0011 0011 = 0011 0000
XOR
"4" (34
H
)
0011 0100 = 0000 0100
XOR
"ETX" (03
H
)
0000 0011 = 0000 0111
ASCII code
"0" "7"
(30
H
) (37
H
)
4) Transmission/reception data corresponding to register codes FF
H
+11
H and FF
H
+17
H
The two's complement sum check code that calculates the subject range for transmission/reception data (message) is expressed as twocharacter data in ASCII code, then transmitted and received from the upper digit.
The difference between (FF
H
+11
H
) and (FF
H
+17
H
) is the difference between the calculation ranges.
An example of the contents (arrangement) of the transmission and reception of the two's complement sum check code is shown below.
(Example) Arrangement of data transmitted and received with the register code FF
H
+17
H
(one first frame and one last frame)
User frame
(first frame)
Arbitrary data User frame
(last frame)
User frame register code
02
H
S
T
X
FF
H
+01
H
3B
H
Station
No.
;
1 2 3 4
03
H
E
T
X
FF
H
+17
H
0D
H
0A
H
C L
R F
Transmission/reception data code
02
H
00
H
3B
H
31
H
32
H
33
H
34
H
03
H
46
H
36
H
0D
H
0A
H
Calculation range
• How to calculate the two's complement sum check code
The lower 1 byte of the value obtained by adding the subject data as binary data is converted to a two's complement, then converted to a hexadecimal ASCII code.
(In the case of the example)
02
H
+00
H
+3B
H
+31
H
+32
H
+33
H
+34
H
+03
H
=10A
H
Data in the subject rangeare added as binary data (hexadecimal)
00001010
11110110
The lower 1 byte of the above numeric value is expressed as a binary number
Reversed, then converted to a two's complement
F6
H
Converted to a hexadecimal ASCII code
"F" "6"
(46
H
) (36
H
)
9 - 5 9 - 5
9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA
COMMUNICATION
MELSEC-Q
5) Transmission/reception data corresponding to register codes FF
H
+EE
H to FF
H
+F9
H
The sum check code that calculates the subject range for transmission/reception data (message) is expressed as the binary code/ ASCII code data shown below, then transmitted and received.
FF
FF
FF
FF
H
H
H
H
Register code
+ EE
+ F0
+ F1
+ F3
H
H
H
H
or FF
or FF
or FF
or FF
H
H
H
H
+ F4
+ F6
+ F7
+ F9
H
H
H
H
Data contents transmitted and received
The lower 2 bytes of the calculated sum check code are transmitted and received as 2-byte binary code data.
The lower byte of the calculated sum check code is transmitted and received as 1-byte binary code data.
The lower byte of the calculated sum check code is converted to 2digit ASCII code, then transmitted and received.
The lower 4 bits of the calculated sum check code is converted to 1digit ASCII code, then transmitted and received.
An example of the contents (arrangement) of the transmission and reception of the sum check code is given below.
(Example) Arrangement of data transmitted and received (one first frame and one last frame)
User frame
(first frame)
Arbitrary data User frame
(last frame)
User frame register code
02
H
FF
H
+01
H
3B
H
S
T
X
Station
No.
;
A 1 (12AB
H
)
03
H
FF
H
+F1
H
0D
H
0A
H
E
T
X
Sum check code
C
R
L
F
Transmission/reception data code
02
H
00
H
3B
H
41
H
31
H
AB
H
12
H
03
H
32
H
01
H
0D
H
0A
H
Range 1
Range 2
Register code
FF
H
+ EE
H
FF
H
+ F0
H
FF
H
+ F1
H
FF
H
+ F3
H
• How to calculate the sum check code and data contents transmitted and received
This is a numeric value obtained by adding data in the above range as binary data.
(In the case of the example Range 1 ) (H) (L)
41
H
+ 31
H
+ AB
H
+ 12
H
+ 03
H
= 0132
H
Data contents transmitted and received (arrangement)
01
H
and 32
H
are transmitted and received, beginning from 32
H
.
32
H
is transmitted and received.
"3" and "2" are transmitted and received, beginning from "3."
"2" is transmitted and received.
Register code
FF
H
, F4
H
FF
H
, F6
H
FF
H
, F7
H
FF
H
, F9
H
(In the case of the example Range 2 ) (H) (L)
02
H
+ 00
H
+ 3B
H
+ 41
H
+ 31
H
+ AB
H
+ 12
H
+ 03
H
= 016F
H
Data contents transmitted and received (arrangement)
01
H
and 6F
H
are transmitted and received, beginning from 6F
H
.
6F
H
is transmitted and received.
"6" and "F" are transmitted and received, beginning from "6."
"F" is transmitted and received.
9 - 6 9 - 6
9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA
COMMUNICATION
MELSEC-Q
9.1.2 Default registration frame (read only)
Default registration frame No.
(Hexadecimal (decimal))
108
H
(264)
109
H
(265) to
10D
H
(269)
10E
H
(270) to
11F
H
(287)
120
H
(288) to
3E7
H
(999)
1
H
( 1)
2
H
( 2) to
FE
H
(254)
FF
H
(255)
100
H
(256)
101
H
(257)
102
H
(258)
103
H
(259)
104
H
(260)
105
H
(261)
106
H
(262)
107
H
(263)
This frame is registered to the Q series C24 in advance and can be used in the same way as the other user frames.
(1) Overview
The default registration frame is registered in the OS ROM of the Q series C24.
The following table lists one-byte data (codes: 01
H
to FE
H
) to a maximum of fivebyte data, which is registered in the frames and can be used for read-only (frame numbers: 1
H
to 3E7
H
). Each of these frames is treated as an user frame.
(2) Default registration frame write data and data contents that are transmitted and received
The following shows the codes of the register data and the data contents that are transmitted and received.
Register data code
(1st byte to nth byte)
01
H
02
H to
FE
H
—
00
H
FF
H
0D
H
, 0A
H
10
H
, 02
H
10
H
, 03
H
00
H
, FE
H
00
H
, 00
H
, FE
H
03
H
, FF
H
, F1
H
03
H
, FF
H
, F1
H
, 0D
H
, 0A
H
Register byte count
1
1
1
2
2
3
3
5
Frame byte count
1
—
1
2
2
3
2
4
Data contents that are transmitted and received data contents
(Data codes shown at the left)
STX to
(Data codes shown at the left)
(For variable data designation)
NUL
(Data codes shown at the left)
CR, LF
DLE, STX
DLE, ETX
(Data codes shown at the left)
(Data codes shown at the left)
ETX, sum check code
1
ETX, sum check code, CR, LF
1
(None)
FF
H
, EE
H to
FF
H
, FF
H
(None)
—
2
—
—
1
—
—
Sum check code
1
—
1 The combination of FF
H
,
H
in the register code is used to handle variable data (sum check code, Q series C24 station No., etc.) as part of the user frame.
The data contents that are transmitted and received and the byte count depend on the code combined with register code FF
H
.
See Section 9.1.1 (4) for the register code combinations that can be handled as variable data and the data contents that are transmitted and received.
9 - 7 9 - 7
9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA
COMMUNICATION
MELSEC-Q
9.2 Transmission/Reception Processing Using User Frame Register Data
The following explains how the Q series C24 transmits and receives using user frame register data.
The Q series C24 checks the transmission/reception of following data, using registered data.
(1) Transmission
(a) If user frame transmission is designated, the user frame is converted, or not converted, from ASCII to BIN data and transmitted, depending on the data communications protocol, ASCII-BIN conversion designation, and user frame
No. designation, based on the following data as the send data of the given part.
1) Register code 01
H
to FE
H
1-byte data register part
Q series C24 transmission is based on the register code (01
H
to FE
H
) data.
(Example) Register the data codes 03
H
, 0D
H
, and 0A
H
as user frame
No. 3E8
H
When user frame No. 3E8
H
is designated during data transmission, if ASCII-BIN conversion is disabled, the Q series
C24 transmits the data codes 03
H
, 0D
H
, 0A
H
(ETX, CR, LF) as the send data of the given user frame part.
If ASCII-BIN conversion is enabled, the Q series C24 converts each of the data above to 2-character ASCII code data and transmits.
Part that designated user frame
No. 3E8
H
(Added by the Q series C24)
(When ASII-BIN conversion disabled)
A
41
H
Data designated by sequence program
B
42
H
1
31
H
2
32
H to
E
T
X
C
R
L
F
(89AB
H
)
AB
H
89
H
03
H
0D
H
0A
H
2) Register data codes FF
H
+00
H
to FF
H
2-byte data register part
The Q series C24 transmission is based on the variable data corresponding to the combination of the register codes FF
H
and 00
H
to
FF
H
.
For example, if sum check code is registered, the Q series C24 will calculate and transmit the sum check code.
If the Q series C24 station No. is registered, the station No. set in the Q series C24 is transmitted.
(Example) Register the data codes 03
H
, FF
H
, F0
H
, 0D
H
, 0A
H
as user frame No. 3E9
H
When user frame No. 3E9
H
is designated during data transmission, the Q series C24 calculates the sum check code as the send data of the given user registration frame part. If
ASCII-BIN conversion is disabled, the Q series C24 transmits the calculated sum check code as the send data of that user frame part.
If ASCII-BIN conversion is enabled, the Q series C24 converts the calculated sum check code to 2 characters/byte ASCII code data and transmits.
Part that designated user frame
No. 3E9
H
(Added by the Q series C24.)
Data designated by sequence program
E
T
X
Sum check code
C
R F
L
(When ASCII-BIN conversion disabled)
A
41
H
B
42
H
1
31
H
2
32
H to (89AB
H
)
AB
H
89
H
03
H
12
H
0D
H
0A
H
Calculated by the Q series C24
9 - 8 9 - 8
9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA
COMMUNICATION
MELSEC-Q
REMARK
With a multidrop link, the user frame includes data that identifies which station transmitted the message to the external device to facilitate generation of arbitrary send data.
External device
Data that identifies the transmitting staion to the external device
S
T
X
1 A ; A B C 1 2 3 ;
Arbitarary data
User frame
C
R
L
F
When message transmitted from the staion
No.1 Q series C24
"ABC123" Data designated to the station
No.1 Q series C24 send data designation area.
CPU C24
(0)
CPU C24
(1)
CPU C24
(5)
( ): Station No.
Data when transmitting a frame written to each
Q series C24 for transmission
S
T
X
0 A ;
L
F
S
T
X
1 A ;
L
F
S
T
X
5 A ;
L
F
C24: Q series C24, QC24(N)
(2) Reception
(a) When setting for reception by user frame is performed, and the first frame is set, the Q series C24 receives the message when it receives data with the same contents as the designated first frame.
If the last frame is set, when the Q series C24 receives data with the same contents as the designated last frame, it sends a reception data read request to the PLC CPU.
(b) The following describes the Q series C24 receive processing using register data.
1) Register data code 01
H
to FE
H
1-byte data register part
The Q series C24 receives and checks if the received data is data of the same code (01
H
to FE
H
) as the registered code.
(Example) Register the data codes 03
H
, 0D
H
, 0A
H
as user frame No.
3E8
H
When user frame No. 3E8
H
is set as data receive, the Q series C24 receives and checks data codes 03
H
, 0D
H
, 0A
H
(ETX, CR, LF) as the receive data of that user frame part.
Artbitrary data area
E
T
X
C
R
L
F
A
41
H
B
42
H
1 2
31
H
32
H
3 4
33
H
34
H
(1234
H
)
34
H
12
H
(89AB
H
)
AB
H
89
H
03
H
0D
H
0A
H
PLC CPU
Reception data read request
Q series C24
Buffer memory
4241
H
(Receive data storage area)
89AB
H
When the Q series C24 receives the data, it performs a Reception data read request to the PLC CPU
9 - 9 9 - 9
9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA
COMMUNICATION
MELSEC-Q
2) Register data code FF
H
+ 00
H
to FF
H
2-byte data register part
The Q series C24 receives and checks if the received data is variable data corresponding to the combination of the register codes FF
H
and
00
H
to FF
H
.
For example, if a sum check code is registered, the Q series C24 calculates the sum check code from the receive data and checks if it is the same as the received sum check code. If the two codes are not the same, the Q series C24 performs error processing.
If the Q series C24 station No. is registered, the Q series C24 checks if the received station No. is the same as the station No. set in the Q series C24. If the station Nos. are not the same, the Q series C24 processes the data as if normal data was received instead of an user frame.
(Example) Register the data codes 03
H
, FF
H
, F0
H
, 0D
H
, 0A
H
as user frame No. 3E9
H
When user frame No. 3E9
H
is set as a data receive frame, the Q series C24 calculates, receives, and checks the sum check code as the receive data of that user frame part.
(c) The Q series C24 removes the user frame data from the received message.
(The PLC CPU cannot read this data.)
REMARK
With a multidrop link, if the receive user frame inherent to each Q series C24 is connected to the link in advance, the Q series C24 of a given station will store only the arbitrary data area of the message transmitted by the external device to the receive data storage area.
External device
S
T
X
5 A ;
Data used by the external device to indicate the transmission destination
Arbitrary data area
L
F
Received by the station No.5 Q series C24.
Data when a receive frame is received at each Q series C24
(First frame)
(Last frame)
CPU C24
(0)
S
T
X
0 A ;
L
F
CPU C24
(1)
S
T
X
1 A ;
L
F
CPU C24
(5)
( ): Station No.
S
T
X
5 A ;
L
F
C24:Q series C24, QC24(N)
9 - 10 9 - 10
9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA
COMMUNICATION
MELSEC-Q
9.3 Precautions when Registering, Reading, Deleting and Using User Frames
The following shows the precautions which should be observed when registering user frames and using registered user frames to transmit data to and receive data correctly from the external device.
(1) Precautions when registering, reading or deleting user frames
(a) User frames can be registered using one of the following methods. However, an user frame to be registered to the flash ROM could be registered by the utility package (GX Configurator-SC) dedicated to the Q series C24 as much as possible.
1) Registering via the utility package (GX Configurator-SC) for the Q series
C24.
2) Registering with the dedicated instruction "PUTE" from the PLC CPU.
3) Registering from an external device with command "1610" through communication using the MC protocol.
(b) The following settings are required when registering or deleting user frames.
1) Switch setting via GX Developer
Set the setting modification to Enable in the transmission setting.
2) Setting via GX Configurator-SC
Set the flash ROM write allow/prohibit setting to Allow on the monitor/test screen.
To set from the PLC CPU, write "1" in the following buffer memory at the startup of the Q series C24 (when the ready signal rises).
Flash ROM write allow/prohibit designation area (address: 2000
H
)
(c) To register, read or delete user frames from the PLC CPU, perform the operation while there is no data communication in progress with the external device.
(d) An user frame having only a sum check code as changeable data cannot be registered. To register a sum check code, add arbitrary data.
(e) Register a receive user frame in the Q series C24 flash ROM.
(f) The changeable data (05
H
to F9
H
) can be specified at only one place in the last frame.
9 - 11 9 - 11
9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA
COMMUNICATION
MELSEC-Q
(2) Precautions when using user frames
(a) To send/receive data using the user frames, it is necessary to set the user frame number to be used in the buffer memory prior to data transmission/reception (receive user frames must be set at the startup of the
Q series C24).
The user frame number to be used can be set from the PLC CPU. However, please try to register frames using the utility package (GX Configurator-SC) of the Q series C24.
(b) Set the receive user frame number by the PLC CPU to show the procedure to receive data.
Receive user frame data by performing the following operations sequentially.
(chapter 11 explains steps 2) and 3).)
1) If an user frame used in data reception was registered from PLC CPU, restart PLC CPU.
2) When starting the Q series C24, set the receive user frame No. to the buffer memory and write [1] to buffer memory user frame use enable/disable designation area (addresses: AD
H
/14D
H
).
3) After the value of the buffer memory user frame use enable/disable designation area changes to [2], start receiving data.
4) Check if the data from the external device was received normally.
(c) If the Q series C24 receives additional code data while receiving data with the non procedure protocol, it does not assume that the last byte of data is the following control data.
• Data received as user frame first frame, last frame (See Sections 9.1 and
9.2.)
• Receive complete code data
Therefore, do not set a user frame containing data receive additional code data as a non procedure protocol receive user frame.
(d) The arbitrary data area of a message received from an external device cannot include data with the same contents (same code) as the last frame.
(Example)
User frame
(first frame)
Arbitrary dat area
User frame
(last frame)
(e) In the following cases, set the data bit length of the transmission specification to 8 bits.
(It is set in the "transmission setting" of switch setting by GX Developer on the Q series C24 side.)
1) When transmitting and receiving the sum check code of the variable data as binary data
(Write code: FF
H
, EE
H
/FF
H
, F0
H
/FF
H
, F4
H
/FF
H
, F6
H
)
2) When transmitting and receiving a user frame containing data codes 80
H to FF
H
9 - 12 9 - 12
9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA
COMMUNICATION
MELSEC-Q
9.4 Register/Read/Delete User Frames
The following explains registering, reading, and deleting user frames in the Q series
C24 flash ROM or buffer memory.
POINT
When registering, reading and deleting the user frames in the flash ROM, try to register them using the utility package (GX Configurator-SC) of the Q series C24.
Registering, reading and deleting operations from GX Configurator-SC are explained in Section 8.4.1 of the User's Manual (Basic).
This section explains how to register, read, or delete user frames from the PLC
CPU.
(1) Type of user frames
Data communication function
Type
Default registration frames
User frame
User frame for the PLC CPU monitoring function
User frame No.
1
H
to 3E7
H
(1 to 999)
3E8
H
to 4AF
H
(
(100 to 1199) (
8001
H
to 801F
H
(-32767 to -32737) (
B001
H
to B00A
H
, B061
H
,
B080
H
to B082
H
Registration destination Remarks
ROM for the Q series C24 OS Read enabled
2
)
3
)
Q series C24 flash ROM
1
)
Q series C24 buffer memory
(Addresses: 1B00
H
to 1FF6
H
)
Register/read/delete enabled
ROM for the Q series C24 OS Register/read/delete disabled
Type
Default registration frame
User frame
User frame for PLC CPU monitoring function
1 Data contained in user frames used for registering and reading is arranged in the same way as data in user frames used for registering in or reading to the flash ROM.
Use the arrangement described in this section as a reference, and register and read user frames.
User frames can also be registered in the buffer memory, but the user frame for the fixed format section should be registered in the flash ROM whenever possible.
2 A user frame cannot be overwritten for registration. To reregister a user frame having the same number, first delete the current user frame and then reregister.
3 Check the registration status of the user frame number from GX Configurator-SC.
(2) Devices that can register/read/delete user frames
User frame No.
PLC CPU
Device that can register/read/delete
External device GX Configurator-SC
Register Read Delete Register Read Delete Register Read Delete
1
H
to 3E7
H
3E8
H
to 4AF
H
8001
H
to 801F
H
B001 to B00A
H
,
B061
H
,
B080
H
to B082
H
(FROM/TO)
9 - 13 9 - 13
9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA
COMMUNICATION
MELSEC-Q
POINT
Conduct registering, reading, and deletion of the user frame from the sequence program when data communication is not being conducted with external device.
5
H
( 5)
6
H
( 6) to
2D
H
( 45)
204
H
( 516)
205
H
( 517) to
21D
H
( 541)
21E
H
( 542)
1B00
H
(6912)
1B01
H
(6913) to
1B28
H
(6952)
1B29
H
(6953)
1B2A
H
(6954) to
1B51
H
(6993)
1B52
H
(6994) to
1FCD
H
(8141)
1FCE
H
(8142)
1FCF
H
(8143) to
1FF6
H
(8182)
Address (Hexadecimal
(decimal))
2
H
( 2)
3
H
( 3)
4
H
( 4)
(3) Buffer memory to use
Flash ROM access
Name
Register/read/delete direction
Frame No. direction
Register /read/delete result storage
Write data byte count designation (See 1).)
Stored value
0: No request
1: Register request
2: Read request
3: Delete request
0: No frame No.
1000 to 1199 (3E8
H
to 4AF
H
)
: Register/read/delete frame No.
0: Normal completion
One or higher: Abnormal completion
(error code)
0: Delete
1 to 80 (1
H
to C8
H
)
: Register data byte count
Processing
Register Read
Registration No.
80F1
H
User frame (See 2).)
Register data byte count designation
User frame storage
40 words
Data code of frame to be registered/ deleted
Number of registered user frame storage
User frame registration status storage (See 3).)
(For registration No. check)
Number of registered default registration frames storage (OS ROM)
Register data byte count designation
Registration No.
8001
H
User frame storage
40 words
Register data byte count designation
Registration No.
8002
H
User frame storage
40 words
0: Not registered to Flash ROM
1 to 200 (1
H
to C8
H
)
: Number registered to Flash ROM
0: Given range not registered
One or higher : Registration status n: Registration count
(See Section 9.1.2.)
(Register data byte count designation.
See 1).)
1 to 80 (1
H
to C8
H
)
: Register data byte count
(User frame storage. See 2).)
Register frame data code to
Register area for 31 frames
Read/write from PLC CPU
: Always performed
: Performed as required
: Unnecessary
Delete
9 - 14 9 - 14
9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA
COMMUNICATION
MELSEC-Q
1) Registration data byte count designation area (Addresses: 5
H
, 1B00
H
,
1B29
H
,..., 1FCE
H
)
• Indicates the total number of bytes of register data of the user frame to be registered/read.
• Flash ROM access
During the register operation, the user registers the total number of bytes of register data.
During the read operation, the total number of bytes of registered data is stored.
• Buffer memory access
During the register operation, the user registers the total number of bytes of register data.
2) User frame storage area
(Addresses: 6
H
to 2D
H
, 1B01
H
to 1B28
H
, 1B2A
H
to 1B51
H
,...1FCF
H
to 1FF6
H
)
• During the register operation, the user sequentially stores the register data of the user frame to be registered in (L) (H) order, beginning from the head area of the given area range.
• During the read operation, the register data of the registered user frame is stored with the same contents as when registering.
(Example) Contents stored to user frame storage area when a user frame to transmit and receive ETX, sum check code,
CR, and LF (register codes: 03
H
, FF
H
, F1
H
, 0D
H
, 0A
H
) is registered to the Flash ROM.
Address
6
H
7
H
8
H
Buffer memory
(H) (L)
FF
H
to 03
H
0D
H
00
H
to F1
H
to 0A
H
Head data
Last data
(Part corresponding to write frame above)
(Data contents transmitted and received)
User frame
(first frame)
Arbitarary data User frame
(last frame)
User frame register code reception data corresponding to register code
02
H
S
T
X
FF
H
,01
H
3B
H
Station
No.
;
A 1
(12AB
H
)
03
H
E
T
X
FF
H
,F1
H
Sum code
0D
H
C
0A
H
L
R F
Transmission/ reception data code
02
H
00
H
3B
H
41
H
31
H
AB
H
12
H
03
H
32
H
01
H
0D
H
0A
H
3) User frame registration status storage area (Addresses: 205
H
to 21D
H
)
• The registration status of user frames to the Flash ROM is stored as the values shown below.
• The contents of each area that indicates the registration status are shown below. The contents of the area are indicated in one user frame No./1 bit form.
(Example)
0: Not registered
1: Rgistered
User frame No. 1015 (3F9
H registration status
) User frame No. 1000 (3E8 registration status
(H) Buffer memory (L)
H
)
Address
205
H b15
0 0 0 0 to
0 0 1 b8b7
1 0 0 0 0 to
1 1 1 b0
1 to 030F
H
206
H
0 0 0 0 0 0 1 1 0 0 0 0 0 0 1 1 to 0303
H
211
H
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 to 0000
H
User frame No. 1199 (4AF
H
) registration status
(Subsequent bits are spares)
9 - 15 9 - 15
9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA
COMMUNICATION
MELSEC-Q
9.4.1 Registering user frames
The following shows an example of a sequence program when registering user frames in the Q series C24 flash ROM.
For details on the PUTE instruction, see Section 17.7.
(When the Q series C24 I/O signals are X/Y80 to X/Y9F)
Registration request
Sets the registration request
Sets the frame number to be registered
Sets the number of registration data bytes
Sets the registration data for the frame to be registered in D4 to D8
Sets the flash ROM write allow
Executes user frame registration
Normal completion
Abnormal completion
POINT
(1) When registering a user frame in the flash ROM, to designate an user frame number that has already been registered, delete the previously registered number and then reregister.
(2) The user should manage the number of total bytes for registered data.
(3) To check unregistered user frames, read the buffer memory (addresses: 205
H to 21D
H
) indicated in Section 9.4 (3).
(4) The SPBUSY instruction can be used to read the communication status by the dedicated instruction.
9 - 16 9 - 16
9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA
COMMUNICATION
MELSEC-Q
9.4.2 Reading user frames
The following shows an example of a sequence program when reading user frames registered in the Q series C24 flash ROM.
For details on the GETE instruction, see Section 17.5.
(When the Q series C24 I/O signals are X/Y80 to X/Y9F)
Read request
Sets the frame No. to be read
Sets the allowable number of data to be read
Clears the device in which to store the read user frame data
Executes user frame reading
Normal completion
Abnormal completion
POINT
(1) When an unregistered user frame number is designated, the operation will complete abnormally.
(2) When the total bytes of data registered in the frame to be read is unknown, read 40 words (80 bytes) by the dedicated instruction.
(3) The SPBUSY instruction can be used to read the communication status by the dedicated instruction.
9 - 17 9 - 17
9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA
COMMUNICATION
MELSEC-Q
9.4.3 Deleting user frames
The following shows an example of a sequence program when deleting user frames registered in the Q series C24 flash ROM.
For details on the PUTE instruction, see Section 17.7.
(When the Q series C24 I/O signals are X/Y80 to X/Y9F)
Deletes request
Sets the delete request
Sets the No. of the user frame to be deleted
Sets a dummy number for the allowable number of deletions
Set the flash ROM write allow.
Executes user frame deletion
Normal completion
Abnormal completion
POINT
(1) When an unregistered user frame number is designated, the operation will complete abnormally.
(2) The SPBUSY instruction can be used to read the communication status by the dedicated instruction.
9 - 18 9 - 18
10 ON-DEMAND DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
10 ON-DEMAND DATA COMMUNICATIONS USING USER FRAMES
During communications between external device and PLC CPU using an MC protocol, on-demand data can be transmitted from the PLC CPU to the external device by ondemand function using user frames.
This chapter describes the transmission of designated send data by the PLC CPU using a message format other than the message formats (A compatible 1C frame formats 1 to 4, QnA compatible 4C frame format 5) described in Section 3.11.2.
10.1 User Frame Data Communications Function
S
T
X
The user frame data communications transmits and receives the message first and last parts in the format selected by the user during data communications between PLC
CPU and external device via the Q series C24.
By using the function described in this chapter, on-demand data listed as shown below can be transmitted from the Q series C24 to an external device.
(Transmitting in QnA compatible 3C frame format 1)
On-demand data
E
T
X
Lists other than the "send data" part of the message format described in Section 3.11.2 are selected by the user as shown at the left. The "send data" part is the same as the list given in Section 3.11.2.
H L H L H L H L H L character area B
H L
Range that is transmitted by user frame.
1 User frame data communications can be carried out by registering (registered by the data code) the message format to be transmitted by the external device and the message format to be received by the external device according to the specifications of the external device to the Q series C24 as user frames.
For the illustration above, the Q series C24 transmits the on-demand data as described below.
• User frame sum check code
Calculates the sum check code according to the contents registered in advance by the user and transmits the result as ASCII code or binary code data.
• Other than user frame sum check code
Transmits data of the code registered in advance by the user. (No conversion)
• Send data (character area B)
This is the data that the sequence program requested for a transmission with ondemand instruction.
The same contents and list as when transmitted without using a user frame described in Section 3.11.3 of Reference Manual by communication protocol by
GX Developer switch setting and word/byte designation.
10
10 - 1 10 - 1
10 ON-DEMAND DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
10
10.2 User Frame Types and Registration
Data communications using user frames can be performed by registering the user frames to the Q series C24 from an external device and the PLC CPU.
Chapter 9 explains the types of user frames and the data that can be used.
To register a user frame from the PLC CPU, see Chapter 9.
To register a user frame from an external device, first see Chapter 9 and check the precautions, etc., then register the user frame using the function described in Section
3.9 of Reference Manual.
10.3 User Frame On-Demand Data Transmission and Buffer Memory Used
This section describes user frame on-demand data transmission processing and the on-demand data list by user frame setting to Q series C24 buffer memory.
(1) Transmission of on-demand data using user frames
The following describes the transmission of on-demand data using user frame.
1) PLC CPU processing
• Before issuing a transmission request to the Q series C24, set the No. of the user frame registered in the Q series C24 to the buffer memory shown below.
• Except for the above, the PLC CPU execution procedure and control procedure are the same as when transmitting on-demand data without user frames described in Section 3.11 of Reference Manual.
2) External device processing
• When the external device receives the user frame transmitted by the Q series C24 as the first frame, receive it as on-demand data.
(2) Buffer memory used and on-demand data list
1) Buffer memory used
During on-demand data transmission by user frame, the user frame to be transmitted is designated by the buffer memories shown below.
CH1
Address
CH2
Name Description
A9
AA
AB
H
H
H
(169)
(170)
(171)
149
14A
14B
H
H
H
(329)
(330)
(331)
AC
H
(172) 14C
H
(332)
On-demand user frame designation
First frame No.
designation
Last frame No.
designation
(1st)
(2nd)
(1st)
(2nd)
Designates the No. of the user frame that is transmitted as the first frame.
0
H
: Do not transmit
Others : Transmit (
1
)
Other than 0 is always designated for the 1st frame.
When designating the 1st frame, the 2nd frame can also be designated.
Designates the No. of the user frame to be transmitted as the last frame.
0
H
: Do not transmit
Others : Transmit (
1
)
When designating the 1st frame, the 2nd frame can also be designated.
1 Designates the registration No. (shown below) of the user frame to be transmitted from among the user frames registered in the Q series C24.
1
H
to 3E7
H
( 1 to 999) : Default registration frame
3E8
H
to 4AF
H
( 1000 to 1199) : User frame (registered in flash ROM)
8001
H
to 801F
H
(-32767 to -32737) : User frame (registered in buffer memory)
10 - 2 10 - 2
10 ON-DEMAND DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
2) On-demand data list
The following shows the user frame designation on-demand data list.
On-demand data
User frame User frame Send data User frame User frame
Transmitted when last frame (2nd) designated.
Transmitted when last frame (1st) designated.
On-demand instruction/transmitted when send data designated in buffer memory.
Transmitted when first frame (2nd) designated.
First frame (1st).
POINT
(1) Only the on-demand data list combinations shown below can be used.
: Designation data
Data name
Combination
5)
6)
7)
3)
4)
1)
2)
8)
First frame
(1st)
First frame
(2nd)
Send data
Last frame
(1st)
(2) The send data for on-demand data transmission by user frame is outlined below.
(See Chapter 9 for a detailed description of user frame.)
Last frame
(2nd)
User frame
First frame (1st)
Last frame
(Last frame)
Contents of send data
Codes registered from 00
H
to
FE
H
Combination of codes registered in FF
H
and 00
H
to
FF
H
User frame
First frame (2nd)
Last frame
(Other than last frame)
Codes registered from 00
FE
H
H
to
Send data
(See Section 3.11.3 of
Reference Manual for details.)
Combination of codes registered in FF
FF
H
—
H
and 00
H
to
ASCII mode Binary mode
Transmit the data of the code registered in the Q series C24.
(No conversion)
Transmit the data according to the user-designated contents, code, and byte count.
Converts the data code registered in the Q series C24 to ASCII data and transmits.
Converts data of the contents, code, and byte count designated by the user to ASCII data and transmits.
Converts the designated send data to ASCII data and transmits.
Transmits data code registered in the Q series
C24.
For 10
H
data, transmits 10
H
+
10
H
.
Transmits the data of the contents, code, and byte count designated by the user.
For 10
H
data, transmits 10
H
+
10
H
.
Transmits the designated data unchanged.
(No conversion)
For 10
H
data, transmits 10
H
+
10
H
.
10 - 3 10 - 3
10 ON-DEMAND DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
10.4 On-Demand Function Control Procedure During User Frame Use
The following uses examples to explain the control procedure when using the ondemand function to frame to transmit on-demand data to an external device by user frame.
10.4.1 Data communication using the ASCII code
The following shows the control procedure when performing switch settings via GX
Developer and registration via GX Configurator-SC.
(1) Switch settings via GX Developer
1) Set the "Communication protocol setting" to any one of the "MC protocol (formats 1 to 4) ".
2) Set the "Station number" to "0".
(2) Registration via GX Configurator-SC
Register as follows when transmitting a user frame, user selected transmission data ( 1) or a combination of user frames.
1) "User frame registration" screen
User frame No.
02
H
( 2)
3EB
H
(1003)
401
H
(1025)
User frame
(Registration code)
02
H
F9
H
, 00
H
, 00
H
, FF
H
, FF
H
, 00
H
03
H
, FF
H
, F1
H
Contents of user frame registration
STX to host station No. data code matched to QnA compatible 3C frame format 1
QnA compatible 3C frame format
1 corresponding ETX, sum check code data code
2) "Transmission control and others system setting" screen, "MC protocol system setting" screen
• Set the "Word/byte units designation" to word units.
• Set the "On-demand user frame designation" items to the following:
First frame No. 1st: 02
H
First frame No. 2nd: 3EB
H
Last frame No. 1st: 401
H
Last frame No. 2nd: 0
H
(No specification)
1 Use the ONDEMAND instruction to designate the transmission data to two words (1234
H
, 5678
H
).
10 - 4 10 - 4
10 ON-DEMAND DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
External device
(Data name)
PLC CPU
(Example)
[Control procedure]
Added by Q series C24
First frame (1st)
First frame (2nd)
Send data
Last frame (1st)
User frame User frame
02
H
F9
H
S
X
F 9 0
00
H
0
00
H FF
H
, FF
H
00
H
0 0 F F 0 0 1 2 3 4 5 6 7 8
03
H FFH,F1H
E
X
H L
02
H
46
H
39
H
30
H
30
H
30
H
30
H
46
H
46
H
30
H
30
H
31
H
32
H
33
H
34
H
35
H
36
H
37
H
38
H
03
H
44
H
32
H
User frame registration code
Send data corresponding to registration code
Send data code
ONDEMAND command
ONDEMAND command complete bit
ONDEMAND command abnormal complete bit
1 scan
(Word units)
(First address)
(Data lenghth)
(1st first frame No.)
(2nd first frame No.)
(1st last frame No.)
(2nd last frame No.)
96
H
Buffer memory
0
A0
A1
H
H
C00
H
2
A9
AA
AB
AC
H
H
H
H
02
H
3EB
H
401
H
0
H
(Result of execution) 256
H
(Send data)
(CH1 side)
C00
H
C01
H
0
1234
H
5678
H
When a transmission error is generated, other than 0 is stored.
Sequentially transmits the data in 4-bit units, begining from the most significant bit.
10 - 5 10 - 5
10 ON-DEMAND DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
10.4.2 Data communications using the binary code
The following shows the control procedure when performing switch settings via GX
Developer and registration via GX Configurator-SC.
(1) Switch settings via GX Developer
1) Set the "Communication protocol setting" to "MC protocol (format 5)."
2) Set the "Station number" to "0."
(2) Registration via GX Configurator-SC
Register as follows when transmitting a user frame, user selected transmission data ( 1) or a combination of user frames.
1) "User frame registration" screen
User frame No.
3EC
H
(1004)
User frame
(Registration code)
02
H
, FF
H
, 01
H
, 3B
H
User frame registration contents
402
H
(1026) 03
H
, FF
H
, F0
H
, 0D
H
, 0A
H
STX + Q series C24 station No. + ;
ETX + sum check code + CR + LF
Sum check code is designated by a 1 byte binary code.
2) "Transmission control and others system setting" screen, "MC protocol system setting" screen
• Set the "Word/byte units designation" to word units.
• Set the "On-demand user frame designation" items to the following:
First frame No. 1st: 3EC
H
First frame No. 2nd: 0
H
(No designation)
Last frame No. 1st: 402
H
Last frame No. 2nd: 0
H
(No designation)
1 Use the ONDEMAND instruction to designate the transmission data to two words (1234
H
, 5678
H
).
10 - 6 10 - 6
10 ON-DEMAND DATA COMMUNICATIONS USING USER FRAMES
External device
(Data name)
PLC CPU
(Example)
MELSEC-Q
[Control procedure]
Added by Q series C24
First frame (1st)
Last frame (1st)
User frame Send data User frame
02
H
FF
H,
01
H
3B
H
S
T
X
;
03
H
FF
H,
F0
H
0D
H
0A
H
E
T
X
C
R
L
F
02
H
00
H
3B
H
12
H
34
H
56
H
78
H
03
H
17
H
0D
H
0A
H
User frame registration code
Send data corresponding to registration code
Send data code
ONDEMAND command
ONDEMAND command complete bit
ONDEMAND command abnormal completion bit
1 scan
(Word units)
(First address)
(Data length)
(1st first frame No.)
(2nd first frame No.)
(1st last frame No.)
(2nd last frame No.)
96
H
Buffer memory
0
A0
A1
H
H
C00
H
2
A9
H
AA
H
AB
H
AC
H
3EC
H
0
H
402
H
0
H
(Result of execution) 256
H
(Send data)
(CH1 side)
C00
H
C01
H
0
1234
H
5678
H
When a transmission error is generated, other than 0 is stored.
Sequentially transmits the data in 4-bit units, begining from the most significant bit.
10 - 7 10 - 7
10 ON-DEMAND DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
10.5 Example of an On-Demand Data Transmission Program Using User Frames
Switch 1
Switch 2
Switch 3
Switch 4
Switch 5
The following shows an example of a sequence program when sending on-demand data including user frames.
Perform the following settings via GX Developer and registration using GX
Configurator-SC in advance.
The sequence program for sending on-demand data when performing the following settings using GX Developer and registration using GX Configurator-SC is the same as the sequence program indicated in Section 11.4 of Reference Manual.
(The Q series C24 I/O signals are X/Y00 to X/Y1F and are sent from the CH1 side interface)
(1) Switch settings via GX Developer
To set the following setting values on the "intelligent functional module switch setting" screen, see Section 4.5 of the User's Manual (Basic).
Remarks Setting item
CH1 Transmission setting
CH1 Communication rate setting
CH1 Communication protocol setting
CH2 Transmission setting
CH2 Communication rate setting
CH2 Communication protocol setting
Station No. setting
Setting value
Set according to the external device.
0001
H
0000
H
0000
H
0001
H
0000
H
MC protocol form 1
Not used
—
Q series C24 station No.
(2) Registration via GX Configurator-SC
1) Registering the user frame to be transmitted
To register the user frame data to be transmitted on the "User frame registration" screen, see Chapter 9 of this manual.
For more details on the "User frame registration" screen, see Section 8.4.1 of
User's Manual (Basic).
2) Registering the user frame No. to be transmitted and the unit of the data length.
Using the screens listed below, register the user frame No. and the unit of the length of data to be transmitted, which have been registered on the "User frame registration" screen.
For more details on the "Transmission control and others system setting" screen, see Section 8.4.5 of User's Manual (Basic).
For more details on the "MC protocol system setting" screen, see Section
8.4.6 of User's Manual (Basic).
Registration screen Setting item
Setting value
0000
H
Remarks
Word unit "Transmission control and others system setting" screen Word/byte units designation
On-demand buffer memory head address designation
"MC protocol system setting" screen
On-demand data length designation
First frame No. designation 1st
On-demand user frame designation
First frame No. designation 2nd
Last frame No. designation 1st
Last frame No. designation 2nd
Message wait time designation
0400
H
—
0000
H
0002
H
03EB
H
0401
H
—
—
0000
H
(No designation)
0000
H
—
10 - 8 10 - 8
10 ON-DEMAND DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
(3) Program example
The following program example shows the transmission of on-demand data using the on-demand function.
Designate two words of transmission data with the ONDEMAND instruction.
The data for the user frame section of on-demand data to be sent is the registered data for the user frame No. that was registered with GX Configurator-
SC.
On-demand transmission instruction
Sets the transmission channel to the
CH1 side
Sets the transmission data count to two words
Sets the transmitting data in D10 to D11
Resets the normal completion flag
Resets the abnormal completion flag
Sets the transmission preparation completion flag
Executes on-demand transmission
Normal completion
Abnormal completion
Resets the transmission preparation completion flag
POINT
(1) The SPBUSY instruction can be used to read the communication status by the dedicated instruction.
(2) For details on the dedicated instructions, see Chapter 9 of User's Manual
(Basic).
(3) Designate the storage capacity for transmission data (stored in D10 to D11 in the above program example) and data length (stored in D2 in the above program example) so that they do not exceed the range of buffer memory assigned by the user for the on-demand function.
10 - 9 10 - 9
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
11
11 DATA COMMUNICATIONS USING USER FRAMES
Registering the fixed format portion of the message transmitted/received by the opposite device and the Q series C24 as a user frame beforehand allows data transmission/reception using a user frame.
The use of the user frame to perform data transmission/reception facilitates the creation of transmission data on the PLC CPU side and a simplified sequence program for checking the reception data.
This Chapter explains the data transmission/reception method and procedure when performing data communication with the Q series C24 non procedure protocol using a user frame.
User frame
Data transmission
Arbitrary data
Q series C24
Arbitrary data
Data transmission
User frame
Opposite device such as a bar code reader or ID controller personal computer
POINT
For more details on the "Transparent code" and "ASCII-BIN conversion" used in the explanations of this chapter, see the chapters listed below. When using transparent codes or performing data communication using ASCII-BIN conversion, please read the following chapters, as well.
• When using transparent codes: See Chapter 12.
• When performing data communication using ASCII-BIN conversion: See Chapter
13.
11 - 1 11 - 1
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
11.1 Overview of Data Communication Procedure
The following is an overview of the procedure when performing data communication between the opposite device and PLC CPU using a user frame.
Start
Switch setting by GX Developer.
Initial setting by GX Configurator-SC .
• • • See Section 4.5 and Chapter 8 of User's Manual (Basic).
(When only default registration frame used)
(When registering user frames)
• Register to the Q series C24 Flash ROM.
• Register to the Q series C24 buffer memory.
• • • See Section 8.4.1 of User's Manual (Basic).
See this manual Chapter 9.
(When receiving data)
Set user frame Nos., etc. to receive user frame designation area
(addresses AD
H
to B5
H
, 14D
H
to 155
H,
2020
H
to 2027
H
, 2120
H
to 2127
H
) of the
Q series C24 buffer memory
Must be set by GX Configurator-SC
after debugging is completed.
• • • See Section 11.2.4 of this manual.
Start data communications
(Reception) (Transmission)
Designate user frame No. to transmission user frame designation area (address B7
H
to 11D
H
,157
H
to 1BD
H
) of the Q series C24 buffer memory.
Read receive data • • • See Section 11.2.1, 11.2.2.
11
Designate transmission data
(arbitrary data area in transmit message) to transmit area of the Q series C24 buffer memory.
•• See Section 11.4.
Data transmission
11 - 2 11 - 2
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
11.2 Data Reception
In data reception using the user frame, the reception method on the Q series C24 side includes format 0 and format 1.
This section explains data reception for each format.
11.2.1 About reception data
In reception using the user frame, data arranged as indicated below can be received.
User frame
(first frame)
Arbitrary data
User frame
(last frame)
With the first frame (
1
)
Without the first frame (
1
)
Reception method
Combination
(1-A)
Format-0 (1-B)
(1-C)
Format-1
Format-0
(1-D)
(1-E)
(2-A)
(2-B)
User frame
(first frame)
—
—
Arbitrary data
—
—
—
User frame
(last frame)
Explanation section
Remarks
—
—
This section
(1)
This section
(2)
For data reception, mixed settings are possible.
—
This section
(3)
: Specified data exists.
(When ASCII-BIN conversion is set to "Disable")
Codes that can be received
00
H
to FF
H
00
H
to FF
H
Codes stored to receive area
3
(Not stored)
00
H
to FF
H
2
(When ASCII-BIN conversion is set to "Enable")
Codes that can be received
00
H
to FF
H
30
H
to 39
H
,
41
H
to 46
H
0
Codes stored to receive area
3
(Not stored)
H
to 9
H
, A
H
to F
H
1 User frames for reception
1) The user frame for data reception can set up to a maximum of four combinations of the first frame and the last frame, regardless of whether there is a specification.
2) For a combination that specifies the first frame (with the first frame), it is necessary to specify the first frame even in other combinations.
3) For a combination that does not specify the first frame (without the first frame), the first frame cannot be specified even in other combinations.
4) A combination with the first frame and a combination without the first frame cannot be combined.
11 - 3 11 - 3
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
2 If data of other than 30
H
to 39
H
and 41
H
to 46
H
are received as the data code of the arbitrary data area (including the transparent code data), the Q series C24 ASCII-BIN conversion will generate an error.
3 Receive data arbitrary data area
1) When the arbitrary data area is stored to the receive area, and the storage byte count is an odd number of bytes, the receive data count shown below is stored to the receive data count storage area.
(When ASCII-BIN conversion is enabled, receive data count is the storage byte count when the arbitrary data area is converted to binary code and stored to the receive area.)
• Word units
Receive data count = Number of bytes stored to receive area ÷ 2....Fractions are truncated
• Byte units
Receive data count = Number of bytes stored to receive area
(00
H
is stored to the upper byte of the last data storage location of the receive area.)
2) When ASCII-BIN conversion enabled, make the arbitrary data area of the receive data an even number of bytes excluding the additional code.
11 - 4 11 - 4
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
(1) Reception with the first frame (combination 1-A to C) (reception using Format-0)
(a) Reception of combination (1-A)
1) In this method, any data section of the reception message that can be handled by the PLC CPU side is enclosed by the first frame and the last frame and transmitted from the external device.
2) Any reception data prior to the first frame will be ignored.
3) The Q series C24 will begin reception processing when data of the same arrangement as the first frame is received.
When data of the same arrangement as the last frame is received, arbitrary data is stored in the reception area of the buffer memory and a read request is performed to the PLC CPU.
4) The received data count initially set in the Q series C24 should be a data count that exceeds the size of the arbitrary data to be received.
5) Reception processing via the receive complete code initially set in the Q series C24 will not be performed. The reception data for the receive complete code will be treated as arbitrary data.
(Example) When data transmitted from a bar code reader is received
STX will be registered in the first frame and ETX registered in the last frame according to the message format of the bar code reader.
(Data format transmitted from the bar code reader)
Reception data
S
T
X
02
H
Data (arbitrary data)
E
T
X
03
H
First frame : STX
Last frame : ETX
Ignored Stored in the reception area
: Reception start timing
: Receive complete timing
(read timing)
(b) Reception of combination (1-B)
1) In this method, messages to be received by the PLC CPU side are all transmitted from the external device as fixed format data.
2) Any reception data prior to the first frame will be ignored.
3) The Q series C24 will begin reception processing when data of the same arrangement as the first frame is received.
When data of the same arrangement as the last frame is received, a read request is performed to the PLC CPU.
4) Since there is no arbitrary data, the reception data count will be "0" when a read request is performed to the PLC CPU.
5) The received data count initially set in the Q series C24 uses the default value.
Reception data
A
C
K
C
R
L
F
06
H
0D
H
0A
H
First frame : ACK
Last frame : CR, LF
Ignored
Stored in the reception area
The received data count is "0."
: Reception start timing
: Receive complete timing
(read timing)
11 - 5 11 - 5
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
(c) Reception of combination (1-C)
1) In this method, start of data transmission from the external device to the
PLC CPU side is notified by the first frame, after which arbitrary data of a fixed length is repeatedly transmitted from the external device.
2) Any reception data prior to the first frame will be ignored.
After the first frame is received, all later reception data is treated as arbitrary data.
3) The Q series C24 will begin reception processing when data of the same arrangement as the first frame is received.
A read request will be repeatedly performed to the PLC CPU when arbitrary data equaling the received data count initially set in the Q series
C24 is received.
4) The received data count initially set in the Q series C24 should be a data count for arbitrary data (fixed length) transmitted from the external device.
5) Reception processing via the receive complete code initially set in the Q series C24 will not be performed. The reception data for the receive complete code will be treated as arbitrary data.
Reception data
First frame Arbitrary data
Equaling the received data count
Equaling the received data count
Ignored
Stored in the reception area
Stored in the reception area
: Reception start timing
: Receive complete timing
(read timing)
(2) Reception with the first frame (combination 1-D, 1-E) (reception using Format-1)
1) In this method, arbitrary data of exclusive format-1 received data count initially set in the Q series C24 is transmitted from the external device together with the first frame.
The data length for the arbitrary data in the reception message that can be handled by the PLC CPU side ( 1) can be specified for each data reception frame combination (up to four combinations).
2) Any reception data prior to the first frame will be ignored.
3) The Q series C24 will begin reception processing when data of the same arrangement as the first frame is received.
When arbitrary data equaling the exclusive format-1 received data count is received, the arbitrary data is stored in the reception area of the buffer memory and a read request is performed to the PLC CPU.
4) Exclusive format-1 received data count initially set in the Q series C24 should be a data count for arbitrary data to be received.
The received data count initially set in the Q series C24 is not used.
5) Reception processing via the receive complete code initially set in the Q series C24 will not be performed. The reception data for the receive complete code will be treated as arbitrary data.
(Example 1) By specifying a user frame, in which only ACK (06
H
) is registered, as the first frame and also exclusive format-1 received data count for arbitrary data as 0 bytes, a read request will be performed to the PLC CPU upon the reception of a 1byte ACK.
11 - 6 11 - 6
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
(Example 2) By specifying a user frame, in which only NAK (15
H
) is registered, as the first frame and also specifying exclusive format-1 received data count for arbitrary data as 2 bytes, a read request will be performed to the PLC CPU upon the reception of NAK + 2-byte data.
Reception data
N
A
K
(1234
H
)
15
H
34
H
12
H
First frame: NAK
Equaling exclusive format-1 receive data count
: Reception start timing
: Receive complete timing
(read timing)
Ignored Stored in the reception area
1 The data length for arbitrary data can be specified as a word/byte count of 0 or greater (the unit depends on word/byte units designation) for each combination of the first frame and the last frame specifying format-
1.
The received data count for data reception using format-1 is referred to as exclusive format-1 received data count.
(3) Reception without the first frame (combination 2-A, 2-B) (reception using Format-0)
(a) Reception of combination (2-A)
1) In this method, a user frame is used as the last frame in place of the non procedure protocol data receive complete code and is transmitted from the external device together with arbitrary data.
2) Any reception data prior to the last frame are all treated as arbitrary data.
3) The Q series C24 will begin reception processing when arbitrary data is received.
When data of the same arrangement as the last frame is received, arbitrary data is stored in the reception area of the buffer memory and a read request is performed to the PLC CPU.
4) The received data count initially set in the Q series C24 is a data count that exceeds the size of the arbitrary data to be received.
5) The Q series C24 performs the following processing with respect to the reception data that is the same as the receive complete code initially set in the Q series C24.
When the reception data is included in the arbitrary data:
Reception is processed via the receive complete code.
When the reception data is included in the last frame:
Reception is not processed via the receive complete code.
(Example) By registering ETX + CR + LF as the last frame, a read request is performed to the PLC CPU when the end of the reception data receives a message of ETX + CR+ LF.
Arbitrary data
E
T
X
C
R
L
F
03
H
0D
H
0A
H
Last frame: ETX, CR, LF
Stored in the reception area
: Reception start timing
: Receive complete timing
(read timing)
11 - 7 11 - 7
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
(b) Reception of combination (2-B)
1) In this method, a user frame is used as the last frame in place of the non procedure protocol data receive complete code, and fixed format data is transmitted from the external device.
2) Any reception data prior to the last frame are all treated as arbitrary data.
3) When data of the same arrangement as the last frame is received, the Q series C24 performs a read request to the PLC CPU.
4) Upon the reception of data from this combination that contains no arbitrary data, the reception data count will be "0" when a read request is performed to the PLC CPU.
5) The received data count initially set in the Q series C24 uses the default value.
6) The Q series C24 performs the following processing with respect to the reception data that is the same as the receive complete code initially set in the Q series C24.
When included in the last frame:
Reception is not processed via the receive complete code.
(Example) By registering ACK + CR + LF as the last frame, a read request is performed to the PLC CPU when the end of the reception data receives a message of ACK + CR + LF.
A
C
K
C
R
L
F
06
H
0D
H
0A
H
Last frame: ACK, CR, LF
: Reception start timing
: Receive complete timing
(read timing)
Stored in the reception area
The received data count is "0."
POINT
Handling of the Q series C24 receive data
(1) When an user frame (first frame, last frame) of a code registered in the Q series C24 is received, receive processing by user frame is performed.
(2) Of the first frame No. and last frame No. (maximum 4 sets) initialized by the user at the buffer memory receive user frame designation area, the set No.
( th) of the user frame received from the external device is stored to the receive user frame storage area.
(3) If receive transparent code is designated, the data of the additional code included in the arbitrary data area is removed immediately after reception
(before conversion when the receive data is converted from ASCII code to binary code).
11 - 8 11 - 8
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
REMARK
The following shows the difference in how reception data for each reception method
(Format-0 and Format-1) is treated when data is received using the combination of
(first frame + arbitrary data).
(1) When data is received using Format-0 (combination (1-C))
1) The Q series C24 regards all arbitrary data after the first frame as valid data and stores it sequentially in the reception area.
2) A read request is performed to the PLC CPU each time arbitrary data equaling the received data count is received, and this process is repeated.
Reception data
First frame
Arbitrary data
Equaling the received data count
Equaling the received data count
Ignored
: Reception start timing
: Receive complete timing
(read timing)
Stored in the reception area
Stored in the reception area
(2) When data is received using Format-1 (combination (1-D, 1-E))
1) After the first frame is received, the Q series C24 regards all arbitrary data equaling exclusive format-1 received data count specified for the received first frame combination as valid data and stores it in the reception area. It then performs a read request to the PLC CPU.
2) After data equaling exclusive format-1 received data count is received, any data until the next first frame will be ignored. (Data will not be stored in the reception area.)
Reception data
Ignored
First frame
Arbitrary data
Equaling exclusive format-1 received data count
Reception data
First frame Arbitrary data
Equaling exclusive format-1 received data count
Stored in the reception area
Ignored
Stored in the reception area
: Reception start timing
: Receive complete timing
(read timing)
11 - 9 11 - 9
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
11.2.2 Timing for start/completion of data reception
Reception start
Receive complete
This section explains the reading of reception data based on the user frame and other factors (such as the receive complete code and received data count) during data reception using a user frame.
—
(1) Timing for start/completion of data reception
The following describes the timing for start/completion of the data reception processing with the Q series C24.
• Data reception using a user frame
• Data reception using the receive complete code and received data count initially set in the Q series C24
• Data reception using exclusive format-1 received data count
Setting the user frame for reception
With the first frame
Without the first frame
When using format-0
(See (2) for each timing)
When using Format-1
(See (2) for each timing)
When the first frame is received.
When the first data of arbitrary data is received.
—
When the factor of receive complete (timing of reception data reading to the PLC
CPU) is one of the following:
(Depends on prior settings. See (2).)
• When the last frame is received.
• When data of the receive complete code is received. (In the case of a combination without the first frame)
• When data equaling the received data count is received.
• When a receive error (time out for the no-reception monitoring time (timer 0))
• When exclusive format-1 received data count is specified as 0 and the first frame is received.
• When exclusive format-1 received data count is specified as 1 or more and data equaling this count is received.
• When a receive error (time out for the no-reception monitoring time (timer 0)) occurs.
occurs.
All arbitrary data received up to the point when one of the above occurs or a receive error is generated is stored in the reception area.
11 - 10 11 - 10
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
(2) Timing chart for reception processing using the Q series C24
The following is a timing chart for the reception processing when data reception is performed using the user frame, which includes the reception processing using the received data count.
The numbers in the table indicate the timing of a reception data read request to the PLC CPU (see next page).
[Combination with the first frame]
—
Reception data
Combination
1-A
Amount of reception data of arbitrary data
Reception data count < Received data count
Reception data count > Received data count
Reception data prior to the reception of the first frame
1-B Reception data count = 0
1-C
Reception data count < Received data count
1-D
1-E
Reception data count > Received data count
Reception data count (exclusive format-1 received data count > 0)
Reception data count (exclusive format-1 received data count = 0)
Deleted
Timing pattern number (see next page)
When
When receiving the first frame receiving arbitrary data in the reception message
When receiving the last frame
—
—
1-A 2)
1-A 1)
1-B
When receiving the complete code (
1
)
Data of the complete code is treated as part of arbitrary data.
—
Reception start
1-C 1)
1-C 2)
1-D
Data of the complete code is treated as part of arbitrary data.
1-E — —
[Combination without the first frame]
2-A (
2-B (
2
)
Reception data count < Received data count
Reception start
2-A 1)
2-A 3)
Reception data count > Received data count data
— —
2-A 2) 2-A 4)
2
) Reception data count = 0
—
Reception start
2-B —
1 The reception processing via the receive complete code is not performed when the same data as the receive complete code has been registered in the last frame.
2 The data reception interval is not monitored with the no-reception monitoring time (timer 0) when only the last frame is set.
POINT
When a receive error is detected, the Q series C24 stores arbitrary data of the reception data received immediately before the error in the reception area of the buffer memory, then turns the reception error detection signal (X4) ON.
11 - 11 11 - 11
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
[Combination with the first frame] Timing patterns for reception start and receive complete (read)
(For data reception with format-0)
Pattern No. 1-A 1) Pattern No. 1-A 2)
External device side
PLC CPU side
Arbitrary data Arbitrary data
Equaling the received data count
Equaling the received data count
Pattern No. 1-B
External device side
PLC CPU side
Pattern No. 1-C 1) Pattern No. 1-C 2)
External device side
PLC CPU side
Arbitrary data
Equaling the received data count
Arbitrary data
Equaling the received data count
Equaling the received data count
(For data reception with format-1)
Pattern No. 1-D
External device side
PLC CPU side
Arbitrary data
Equaling exclusive format-1 received data count
Pattern No. 1-E
Reception data
Ignored
Arbitrary data
Equaling exclusive format-1 received data count
External device side
PLC CPU side
Reception data
: Reception start timing
: Receive complete timing
(read timing)
Ignored
When exclusive format-1 received data count is 0
POINT
When data is received using Format-1, the Q series C24 checks again whether the first frame has been received after receiving data equaling the exclusive format-1 received data count. Reception data during that time is ignored.
11 - 12 11 - 12
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
[Combination without the first frame] Timing patterns for reception start and receive complete (read)
Pattern No. 2-A 1) Pattern No. 2-A 2)
External device side
PLC CPU side
Arbitrary data
Pattern No. 2-A 3)
External device side
PLC CPU side
Arbitrary data
Pattern No. 2-B
External device side
PLC CPU side
Arbitrary data
Arbitrary data
Equaling the received data count
Pattern No. 2-A 4)
Arbitrary data
Equaling the received data count
: Reception start timing
: Receive complete timing
(read timing)
Arbitrary data
11 - 13 11 - 13
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
11.2.3 Receive procedure
The following shows the receive procedure when a message, including data with the same arrangement as the specified user frame, is received and the arbitrary data is read to the PLC CPU.
Procedure
(When the CH1 side interface of the Q series C24 receives data)
Reception data with the user frame ( 1)
External device
User frame
(first frame)
Arbitary data area
User frame
(last frame)
PLC CPU ( 2)
Reception data read request signal
X3
( 1)
PLC CPU
Completion device
Status display device at completion
( 3 2))
INPUT
ON
ON
Abnormal completion
Normal completion
1 scan
( 3 1))
FROM
1 See Sections 11.2.1 and 11.2.2 regarding the reading of reception data using a user frame and the timing of reception data reading to the PLC CPU.
2 Sets the receive user frame registration No., etc. in the "non procedure system setting" screen for GX Configurator-SC.
During debugging, the initial setting value for data reception shall be set prior to data receiving, but after debugging is completed, it shall be set when the Q series C24 starts up. (See Section 11.2.4.)
3 Reading ((1) below) for checking which user frame was received by the Q series
C24 from the PLC CPU and reading of the receive data (2) below).
1) Reads which of the user frames set in the receiver user frame designation area was received from the receive user frame storage area (address: 25B
H
).
2) Reads the arbitrary data area of the receive message from the receive area
(default addresses: 600
H
to 7FF
H
).
11 - 14 11 - 14
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
11.2.4 User frame setting for reception
(1) About user frame setting for reception
This setting is to receive data from the opposite device using non procedure protocol through the use of a user frame. Everything is set on the GX
Configurator-SC "Non procedure system setting" screen. The setting items are listed below. (See Section 8.4.7 of User's Manual (Basic).)
[Setting screen] Non procedure system setting screen
GX Configurator-SC setting items
(Non procedure system setting screen)
Received data count designation
Receive complete code designation
User frame use enable/disable designation
First frame No. designation 1st to 4th
Last frame No. designation 1st to 4th
User frame receive format designation
1st to 4th
Exclusive format-1 received data count
1st to 4th
Description of setting values
Format-0 Format-1
Designates the data count that exceeds the size of the arbitrary data to be received or the data count of the received data size.
(Reception of combination with the first frame)
The specified value is invalid.
(Reception of combination without the first frame)
Designates the code for the last data in the reception message for performing a read request to the PLC CPU.
Designates "Enable."
Designates the user frame No.
(0 or 1 or higher).
Designates the user frame No.
(0 or 1 or higher).
The specified value is invalid.
(Exclusive format-1 received data count becomes valid.)
Designates the user frame No.
(1 or higher).
Designates 0
H
for everything.
Designates "Format-0." Designates "Format-1."
Remarks
See Chapter 6 of
User's Manual
(Basic).
See (2) of this section for the contents of each setting.
The specified value is invalid.
Designates the data count for the arbitrary data to be received.
11 - 15 11 - 15
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
(2) Initial settings via GX Configurator-SC ("Non procedure system setting" screen)
This section explains the buffer memory when setting various setting data for data reception using a user frame in a sequence program. (Numbers in the parentheses indicate the buffer memory address.)
(a) User frame use enable/disable designation (addresses: AD
H
/14D
H
)
Designate "Enable" when using user frames to receive data.
b15 to b0
Buffer memory address AD
H
/14D
H
(Default 0
H
)
Write 1
H
0: Do not use.
1: Use.
2: Data communication enable
(Q series C24 is set)
1) "1" is written in the user frame use enable/disable designation area.
2) After the preparation for the data reception using the user frames is completed, "2" is written in the user frame use enable/disable designation area. (Q series C24 is set)
3) After the value in the user frame use enable/disable designation area is changed from "1" to "2," start receiving data used by the user frame.
Until "2" is written in the user frame use enable/disable designation area, data transmission is also not available.
(b) First frame No. designation area and last frame No. designation area
(addresses: AE
H
to B5
H
/14E
H
to 155
H
)
From among the user frames registered in the Q series C24, designate the frame numbers of the user frames you wish to use in the combination and order of priority as described in (1).
b15 to
Buffer memory address AE
H
/14E
H to
B1
H
/151
H
B2
H
/152
H to
B5
H
/155
H to to b0 (Default All 0
H
)
First frame (1st) to
First frame (4th)
Last frame (1st) to
Last frame (4th)
First combination
Fourth combination
Write 0
H
to 801F
H
0
H
( 0): No designation
1
H
to 3E7
H
(1 to 999): Designate the default registration frame (for
OS ROM registration).
3E8
H
to 4AF
H
(1000 to 1199): Designate the user frame (for flash ROM registration).
8001
H
to 801F
H
(–32767 to –32737): Designate the user frame (for buffer memory registration).
11 - 16 11 - 16
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
[How to specify the first frame No. and the last frame No.]
Set the frame numbers using the following setting method.
(1) For the receive user frames, the first frame and last frame are set as a pair, regardless of whether the external device transmits these frames.
(If the external device does not transmit either one of the frames, the unsent frame
No. is set to "0" (no setting)).
(2) A maximum of four combinations of first and last frames can be set for the non procedure protocol. (See Section 11.2.1.)
Of the maximum four combinations to be set, if there is a combination that specifies the first frame, specify the first frame for all other combinations. In addition, set in the following order starting from the first buffer memory (AE
H
to
B5
H
/14E
H
to 155
H
).
(When specifying the first frame)
(i) Each frame No. for combinations that specify the first frame and the last frame
(ii) Each frame No. for combinations that specify the first frame but not the last frame
Of the maximum four combinations to be set, if there is a combination that specifies the last frame only without specifying the first frame, the first frame cannot be specified in any of the combinations. Set the number of the last frame to be used in order starting from the first area of the buffer memory (AE
H to B5
H
/14E
H
to 155
H
).
(3) When setting more than one combination, the first frame having the registered data in the same arrangement or the same frame number cannot be designated.
However, the last frame can be designated.
(4) Use the user frame numbers of the following user frames to set the receive user frames. (See Section 9.1.)
1) Default registration frame numbers: 1
H
to 3E7
H
2) User frame numbers registered in the Q series C24 flash ROM : 3E8
H
to 4AF
H
3) User frame numbers registered in the Q series C24 buffer memory: 8001
H
to
801F
H
(5) Do not specify (set) the frame No. of a user frame that includes the receive transparent code designation additional code data shown in Chapter 12 as a user frame for data reception using non procedure protocol.
11 - 17 11 - 17
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
(c) User frame receive format designation (address: 2020
H
to 2023
H
/2120
H
to
2123
H
)
In data reception using a user frame, specify the reception method for each combination of receive user frames. This setting is valid in a setting shown in
(2) (b) when it is set using a combination that specifies a user frame.
Buffer memory address
2020
H
/2120 to
H
2023
H
/2123
H b15 to
Setting for the first combination b0
Setting for the second combination
Setting for the third combination
Setting for the fourth combination
(Default 0
H
)
Specify the reception method
0
H
: Format-0
1
H
: Format-1
POINT
For combinations other than those with the first frame only, data reception is performed using Format-0 even if Format-1 is specified through the above reception method setting.
(d) Exclusive format-1 received data count designation (address: 2024
H
to
2027
H
/2124
H
to 2127
H
)
• For a combination specifying Format-1 in the user frame receive format designation, specify the arbitrary data word/byte count (size for performing a reception data read request to the PLC CPU) when the applicable first frame is received. Specify this for each combination specifying Format-1.
• Specify a size within the size of the storage area for the reception data in the buffer memory.
• The unit for the setting value depends on the setting value given in the word/byte units designation.
Buffer memory address
2024
H
/2124
H to
2027
H
/2127
H b15 to
Setting for the first combination
Setting for the second combination
Setting for the third combination
Setting for the fourth combination b0 (Default 0
H
)
Exclusive format-1 received data count
Write 0
H
to FFFF
H
11 - 18 11 - 18
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
(3) Examples of registering a receive user frame
The following are examples of pre-registering a receive user frame on the CH1 side with the GX Configurator-SC.
(a) When the first frame is specified
In the example, the following three combinations are registered for the receive user frame.
[Setting conditions]
User frame
User frame receive format designation
Exclusive format-1 received data count
Remarks
1st combination
2nd combination
3rd combination
(First frame + last frame)
(First frame only)
(First frame only)
Format-0
Format-1
Format-1
—
0
H
2
H
The received data count becomes valid.
Exclusive format-1 received data count becomes valid.
See Section 8.4.7 of User's Manual (Basic) for registration using the GX
Configurator-SC.
[Setting value]
Setting item
Received data count designation
Receive complete code designation
Setting value
1FF
H
FFFF
H
Remarks
For Format-0
Set to "No receive complete code."
Always specify
"Enable."
User frame use enable/disable designation
Receive user frame designation
First frame No. designation
Receive user frame designation
Last frame No. designation
1st
2nd
3rd
4th
1st
2nd
3rd
4th
1st
Enable
3E8
H
3E9
H
3EA
H
0
H
41D
H
0
H
0
H
0
H
Foramt-0
0
H
: No designation
1
H
or higher: There is a designation.
In this setting, only three combinations become valid.
User frame receive format designation
2nd
3rd
Foramt-1
Foramt-1
The received data count becomes valid.
Exclusive format-1 received data count becomes valid.
Exclusive format-1 received data count designation
4th
1st
2nd
3rd
4th
Foramt-0
0
H
0
H
2
H
0
H
—
For Format-1
11 - 19 11 - 19
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
(b) When the first frame is not specified
In the example, the following three combinations are registered for the receive user frame.
[Setting conditions]
User frame
User frame receive format designation
Exclusive format-1 received data count
Remarks
1st combination
2nd combination
3rd combination
(Last frame only)
(Last frame only)
(Last frame only)
Format-0 —
The received data count becomes valid.
See Section 8.4.7 of User's Manual (Basic) for registration using the GX
Configurator-SC.
[Setting value]
Setting item
Received data count designation
Receive complete code designation
Setting value
1FF
H
00
H
Remarks
For Format-0
Designate any received complete code.
Always specify
"Enable."
User frame use enable/disable designation
Receive user frame designation
First frame No. designation
1st
2nd
3rd
4th
1st
Receive user frame designation
Last frame No. designation
2nd
3rd
User frame receive format designation
Exclusive format-1 received data count designation
4th
1st
2nd
3rd
4th
1st
2nd
3rd
4th
Enable
0
H
0
H
0
H
0
H
41D
H
41E
H
41F
H
0
H
Format-0
Format-0
Format-0
Format-0
0
H
0
H
0
H
0
H
0H: No designation
0H: No designation
1H or higher: There is a designation.
In this setting, only three combinations become valid.
Everything is set to
Format-0 since the first frame is not designated.
Setting value for
Format-1.
This setting is not required since everything is set to
Format-0.
11 - 20 11 - 20
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
11.3 Receive Program
This section shows examples of the sequence program to read the reception data stored in the Q series C24 buffer memory to the PLC CPU, when data including the use frame is received.
11.3.1 Sequence program example
The following example shows a sequence program that stores the received user frame setting number (combination number) in D0 and the received data in addresses beginning with D10.
For details on the INPUT instruction, see Section 9.4 of the User's Manual
(Basic).
Reception data read request
Reads combinations of user frames received.
Sets the reception channel to CH1.
Sets the allowable number of reception data to 6.
Executes reception.
Sets the normal completion flag.
Sets the abnormal completion flag.
D0
D1
D2
D3
D10
D11
Receive user frame
Data receive result
Receive data count
Receive data
Dn
(Sequence program)
Sets the receive user frame regitration No.(See Section 11.2.4.)
Q series C24
Address
AD
H
AE
H to
B1
H
B2
H to
B5
H
Buffer memory
User frame use control designation
(1st)
First frame
No. designation to
(4th)
(1st)
Last frame
No. designation to
(4th)
258
H
Data reception result
25B
H
Receive user frame ( th set)
600
H
601
H
Receive data count storage to
Receive area
Receive data storage
7FF
H
1st set
4th set
(Sequence program)
Sets the receive user frame registration No.
(See Section 11.2.4.)
2020
H to
2023
H
2024
H to
2027
H
User frame receive format designation
Exclusive format-1 received data count designation
(1st) to
(4th)
(1st) to
(4th)
1st set
4th set
11 - 21 11 - 21
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
11.3.2 Application example for data reception using a combination that specifies the first frame
In the description of this program example, conditions for data reception using a user frame are as follows.
(1) The Q series C24 I/O signal
The Q series C24 is installed at QCPU I/O signal addresses X/Y80 to X/Y9F.
(2) Q series C24 interface used in data communications with the external device
The Q series C24 CH1 side RS-232 interface is used.
Item
Word/byte units designation
Receive transparent code designation
ASCII-BIN conversion designation
Received data count
Receive complete code
User frame use control designation
First frame No. designation
Last frame No. designation (
1
)
User frame receive format designation
Exclusive format-1 received data count designation
(3) Data to be registered on the GX Configurator-SC "Transmission control and other system settings" screen and "Non procedure system settings" screen used for data communication using a user frame.
Change default values for the items listed in the table below.
Use default values for other items.
Set contents
Buffer memory address to store registration value
Remarks
Explanation section
Word/byte
Yes/No
Do not convert
6 to 511
None
Use
Yes
Format-0/ Format-1
0
H
to
FFFF
H
96
H
120
H
121
H
A4
H
A5
H
AD
H
AE
H
to
B5
H
2020
H
to
2023
H
2024
H
to
2027
H
Set to either one according to the example.
When Yes,
Additional code: 10
H
(DLE)
Transparent code: 02
H
(STX)
Select "Do not convert" in the example.
Set according to the example.
—
See the diagram in the application example.
Section 8.4.5 of
User's Manual
(Basic)
Section 8.4.7 of
User's Manual
(Basic)
1 This program example gives the registered contents of the user frame No. specified as the first frame No.
and the last frame No.
[When receiving with a combination that specifies the first frame]
First frame No.
Last frame No.
1st
2nd
3rd
4th
1st
2nd
3rd
4th
User frame No.
3E8
H
3E9
H
6
H
15
H
41B
H
0
H
(none)
0
H
(none)
0
H
(none)
Registered code
02
H
, 51
H
, 20
H
, 0A
H
, 3B
H
,
02
H
, 41
H
, 3B
H
06
H
,
03
15
H
,
H
, FF
H
, F0
H
—
—
—
Registered data contents
STX, Q, (SP),
External device station No.,;
STX, A, ;
ACK
NAK
ETX, Sum check code
11 - 22 11 - 22
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
Reception data read request
(a) When receiving with a combination of the first frame, arbitrary data and last frame (reception using Format-0)
When STX handled as transparent code.
Additional code (Removed by Q series C24.)
Transparent code
D
L
E
S
T
X
External device
PLC CPU
10
H
02
H
Head data
S
T
X
Q
;
0 1 2 3
S
T
X
C
A B C
(1234
H
)
R
L
F
E
T
X
02
H
51
H
20
H
0A
H
3B
H
30
H
31
H
32
H
33
H
02
H
41
H
42
H
43
H
34
H
12
H
0D
H
0A
H
03
H
EE
H
First frame
(corresponds to register No. 3E8
H
)
Arbitrary data area
Last frame
(corresponds to register
No.41B
H
)
1)
Reception data read request
PLC CPU
X83
INPUT
ON
Completion device M0
Status display device at completion
M1
ON
Abnormal completion
Nomal completion
1 scan
2020
H
0
H
2021
H
0
H
2022
H
1
H
2023
H
1
H
2024
H
0
H
2025
H
0
H
2026
H
0
H
2027
H
2
H
Buffer memory
User frame receive format designation
(1st = Format-0)
(2nd = Format-0)
(3rd = Format-1)
(4th = Format-1)
Exclusive format-1 received data count
(1st)
(2nd)
(3rd)
(4th)
Receive data count
Word units
Receive byte count excluding frame and
additional code (12)/2=6
Byte units
Receive byte count excluding frame and
additional code (12)
The figure shown below is for word units.
AD
H
2
H
AE
H
3E8
H
AF
H
3E9
H
B0
H
6
H
B1
H
15
H
B2
B3
B4
B5
120
121
H
H
H
H
H
H
41B
H
(None)
0
H
(None)
0
H
(None)
0
H
(YES) (NO)
1002
H
/ 0
H
(Disable)
0
H
25B
H
1
H
600
H
601
H
602
H
603
H
604
H
605
H
606
H
00
H
, 06
H
(1) (0)
31
H
, 30
H
(3) (2)
33
H
, 32
H
(A) (STX)
41
H
, 02
H
(C) (B)
43
H
, 42
H
(1234
H
)
12
H
, 34
H
(LF) (CR)
0A
H
, 0D
H
Buffer memory
User frame use control designation
First frame No. designation
(1st)
(2nd)
(3rd)
(4th)
Last frame No. designation
(1st)
(2rd)
(3rd)
(4th)
Receive transparent code designation
ASCII-BIN conversion designation
Receive user frame
2)
( th)
Receive data count
3)
Receive data
(arbitrary data area)
4) to D0 to D3 to D10 or after
Reads combinations of user frames received.
Sets to CH1 the reception channel.
Sets the allowable number of reception data to 6.
Executes reception.
Sets the normal completion flag.
Sets the abnormal completion flag.
11 - 23 11 - 23
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
(b) When receiving with a combination of the first frame and arbitrary data
(reception using Format-0)
When STX handled as transparent code.
Additional code (Removed by Qseries C24.)
Transparent code
D
L
E
S
T
X
Reception data read request
PLC CPU
X83
Completion device M0
Status diaplay device at completion
M1
Reception data read request
1)
10
H
02
H
Head data
External device
PLC CPU
S
T
X
A
;
0 1 2
3
S
T
X
A B C
C
R
L
F
(1234
H
)
02
H
41
H
3B
H
30
H
31
H
32
H
33
H
02
H
41
H
42
H
43
H
34
H
12
H
0D
H
0A
H
First flame
(corresponds to register
No.3E9
H
)
Arbitrary data are (Received data count)
INPUT
ON
ON
1 scan
Abnormal completion
Normal completion
2020
H
0
H
User frame receive format designation
(1st = Format-0)
2021
H
0
H
(2nd = Format-0)
2022
H
1
H
(3rd = Format-1)
2023
2024
H
H
1
H
0
H
2025
H
0
H
2026
H
0
H
2027
H
2
H
Buffer memory
(4th = Format-1)
Exclusive format-1 received data count designation
(1st)
(2nd)
(3rd)
(4th)
Receive data count
Word units
Receive byte count excluding frame and
additional code (12)/2=6
Byte units
Receive byte count excluding frame and
additional code (12)
The figure shown below is for word units.
A4
H
AD
H
AE
H
AF
H
B0
H
B1
H
B2
H
B3
H
B4
H
B5
H
120
H
121
H
25B
H
600
H
601
H
602
H
603
H
604
H
605
H
606
H
6
2
3E8
H
H
H
Receive data count
User frame use control designation
First frame No. designation
(1st)
(2nd)
3E9
H
6
H
(3rd)
15
H
41B
H
(None)
0
H
(None)
0
H
(None)
0
H
(YES)
1002
H
/ 0
H
(Disable)
0
H
2
(NO)
H
00
H
, 06
H
(1) (0)
31
H
, 30
H
(3) (2)
33
H
, 32
H
(A) (STX)
41
H
, 02
H
(C) (B)
43
H
, 42
H
(1234
H
)
12
H
, 34
H
(LF) (CR)
0A
H
, 0D
H
Buffer memory
(4th)
Last frame No.designation
(1st)
(2nd)
(3rd)
(4rth)
Receive transparent code designation
ASCII-BIN conversion designation
Receive user frame
2)
( th)
Receive data count
3)
Receive data
(arbitary data area) 4) to D0 to D3
D10 or after
Reads combinations of user frames received.
Sets CH1 to the reception channel.
Sets the allowable number of reception data to 6.
Executes reception.
Sets the normal completion flag.
Sets the abnormal completion flag.
11 - 24 11 - 24
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
(c) When receiving with user frame only (reception using Format-0)
External device
PLC CPU
Reception data read request
PLC CPU
Completion device
Status display device at completion
Head data
X83
M0
M1
S
T
X
02
H
Q
51
H
Nos. 3E8
20
H
0A
1)
(For reception using first frame and last frame combination)
H
First frame
H
and 41B
H
)
;
3B
H
(Correspond to register
E
T
X
03
H
03
H
Last frame
INPUT
ON
ON
1 scan
Abnormal completion
Normal completion
Since there is no arbitrary data area, the receive data count is [0].
The illustration below is for reception using first frame and last frame combination.
AD
AE
H
H
2
3E8
H
H
User frame use control designation
First frame No. designation
(1st)
AF
H
3E9
H
(2nd)
B0
H
6
H
(3rd)
B1
H
B2
H
15
H
(4th)
Last frame No. designation
(1st)
B3
B4
B5
120
121
H
H
H
H
H
41B
H
(None)
0
H
(None)
0
H
(None)
0
H
(YES) (NO)
1002
H
/ 0
H
(Disable)
0
H
(2nd)
(3rd)
(4th)
Receive transparent code designation
25B
600
2020
2021
H
H
H
H
00
H
1
, 00
0
0
H
H
H
H
ASCII-BIN conversion designation
Receive user frame
( th)
2)
Receive data count
3) to D0 to D3
User frame receive format designation
(1st = Format-0)
(2nd = Format-0)
2022
H
1
H
(3rd = Format-1)
2023
H
1
H
2024
H
0
H
(4th = Format-1)
Exclusive format-1 received data count
(1st)
2025
H
0
H (2nd)
2026
H
0
H (3rd)
2027
H
2
H
Buffer memory
(4th)
Reception data read request
Reads combinations of user frames received.
Sets CH1 to the reception channel.
Sets the allowable number of reception data to 6.
Executes reception.
Sets the normal completion flag.
Sets the abnormal completion flag.
11 - 25 11 - 25
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
Head data
A
C
K
External device
PLC CPU
Reception data read request
X83
PLC CPU
06
H
First frame
(Correspond to register No. 6
H
)
1)
(d) When receiving with first frame only (reception using Format-1)
INPUT
Completion device M0
Status display device at completion
M1
ON
ON
1 scan
Abnormal completion
Normal completion
Since it is designated to system 1 received data count "0", the receive data count is [0].
The illustration below is for byte unit.
AD
AE
H
H
2
3E8
H
H
User frame use control designation
First frame No. designation
(1st)
AF
H
3E9
H
(2nd)
B0
H
6
H
(3rd)
B1
H
B2
H
15
H
(4th)
Last frame No. designation
(1st)
B3
B4
B5
120
121
H
H
H
H
H
41B
H
(None)
0
H
(None)
0
H
(None)
0
H
(YES) (NO)
1002
H
/ 0
H
(Disable)
0
H
(2nd)
(3rd)
(4th)
Receive transparent code designation
25B
600
2020
2021
H
H
H
H
00
H
3
H
, 00
0
0
H
H
H
ASCII-BIN conversion designation
Receive user frame
( th)
2)
Receive data count
3) to D0 to D3
User frame receive format designation
(1st = Format-0)
(2nd = Format-0)
2022
H
1
H
(3rd = Format-1)
2023
H
1
H
2024
2025
H
H
0
0
H
H
(4th = Format-1)
Exclusive format-1 received data count
(1st)
(2nd)
2026
H
0
H (3rd)
2027
H
2
H
Buffer memory
(4th)
Reception data read request
Reads combinations of user frames received.
Sets CH1 to the reception channel.
Sets the allowable number of reception data to 6.
Executes reception.
Sets the normal completion flag.
Sets the abnormal completion flag.
11 - 26 11 - 26
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
(e) When receiving with a combination of the first frame and arbitrary data
(Exclusive format-1 dedicated received data count) (reception using
Format-1)
Receive data count
Word units
Receive byte count excluding frame and
additional code (2)/2=1
Byte units
Receive byte count excluding frame and
additional code (2)
Head data
External device
N
A
K
(0022)
15
H
22
H
00
H
PLC CPU
Reception data read request
Arbitrary data area
First frame
(Correspond to register No. 15
H
)
1)
X83
PLC CPU INPUT
Completion device M0
Status display device at completion
M1
ON
ON
1 scan
Abnormal completion
Normal completion
The illustration below is for byte unit.
AD
AE
H
H
2
3E8
H
H
User frame use control designation
First frame No. designation
(1st)
AF
H
3E9
H
(2nd)
B0
H
6
H
(3rd)
B1
H
B2
H
15
H
(4th)
Last frame No. designation
(1st)
B3
B4
B5
120
121
H
H
H
H
H
41B
H
(None)
0
H
(None)
0
H
(None)
0
H
(YES)
1002
H
(NO)
/ 0
H
(Disable)
0
H
(2nd)
(3rd)
(4th)
Receive transparent code designation
25B
600
601
2020
2021
H
H
H
H
H
00
H
00
4
H
, 02
(0022
H
H
, 22
0
0
H
H
)
H
H
ASCII-BIN conversion designation
Receive user frame
( th)
2)
Receive data count
3)
Receive data
(arbitrary data area)
User frame receive format designation
(1st = Format-0)
4)
(2nd = Format-0) to D0 to D3 to D10
2022
H
1
H
(3rd = Format-1)
2023
H
1
H
2024
H
0
H
(4th = Format-1)
Exclusive format-1 received data count
(1st)
2025
H
0
H (2nd)
2026
H
0
H
(3rd)
2027
H
2
H
Buffer memory
(4th)
Reception data read request
Reads combinations of user frames received.
Sets CH1 to the reception channel.
Sets the allowable number of reception data to 6.
Executes reception.
Sets the normal completion flag.
Sets the abnormal completion flag.
11 - 27 11 - 27
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
11.3.3 Application example for data reception using a combination that does not specify the first frame
In the description of this program example, conditions for data reception using a user frame are as follows.
(1) The Q series C24 I/O signal
The Q series C24 is installed at QCPU I/O signal addresses X/Y80 to X/Y9F.
(2) Q series C24 interface used in data communications with the external device
The Q series C24 CH1 side RS-232 interface is used.
(3) Data to be registered on the GX Configurator-SC "Transmission control and other system settings" screen and "Non procedure system settings" screen used for data communication using a user frame.
Change default values for the items listed in the table below.
Use default values for other items.
Item
Word/byte units designation
Receive transparent code designation
ASCII-BIN conversion designation
Received data count
Receive complete code
User frame use control designation
First frame No. designation (
1
)
Last frame No. designation (
1
)
User frame receive format designation
Exclusive format-1 received data count designation
Set contents
Buffer memory address to store registration value
Remarks
Explanation section
Word/byte
Yes
Do not convert
6 to 511
None
Use
None
96
H
120
H
121
H
The unit is set to "Word" in the example.
Specify as follows:
Additional code: 10
H
(DLE)
Transparent code: 02
H
(STX)
Select "Do not convert" in the example.
Set according to the example.
—
Section 8.4.5 of
User's Manual
(Basic)
Yes
AE
H
B2
H
A4
H
A5
H
AD
H
to
B1
H
to
B5
H
See the diagram in the application example.
Section 8.4.7 of
User's Manual
(Basic)
Format-0
0
H
2020
H
2024
H
to
2023
H
to
2027
H
See the diagram in the application example.
Specify Format-0 for a combination that does not specify the first frame.
1 This program example gives the registered contents of the user frame No. specified as the first frame No.
and the last frame No.
First frame No.
Last frame No.
1st
2nd
3rd
4th
1st
2nd
3rd
4th
User frame No.
0
H
(none)
0
H
(none)
0
H
(none)
0
H
(none)
419
H
0
H
(none)
0
H
(none)
0
H
(none)
Registered code
3B
H
, 04
H
—
—
—
—
—
—
—
Registered data contents
;, E0T
11 - 28 11 - 28
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
When STX is handled as transparent code.
(d) When receiving using arbitrary data and last frame combination. (reception using Format-0)
Addtional code (Removed by the Q series C24.)
Transparent code
D
L
E
S
T
X
External device
PLC CPU
Reception data read request
PLC CPU
Completion device
Status display device at completion
Head data
X3
M0
M1
Reception data read request
0 1 2
10
3
H
1)
02
S
T
X
H
A B C
Arbitrary data area
INPUT
C
R
L
F
;
(1234
H
)
30
H
31
H
32
H
33
H
02
H
41
H
42
H
43
H
34
H
12
H
0D
H
0A
H
3B
H
04
H
E
O
T
Last frame
(Corresponds to register
No.419
ON
ON
H
)
1 scan
2020
H
0
H
2021
H
0
H
2022
H
0
H
2023
H
0
H
2024
H
0
H
2025
H
0
H
2026
H
0
H
2027
H
0
H
Buffer memory
Abnormal completion
Normal completion
User frame receive format designation
(1st = Format-0)
(2nd = Format-0)
(3rd = Format-1)
(4th = Format-1)
Exclusive Format-1 received data count
(1st)
(2nd)
(3rd)
(4th)
Receive data count
Word units
Receive byte count excluding frame and
additional code (12)/2=6
Byte units
Receive byte count excluding frame and
additional code (12)
The illustration below is for word units.
AD
H
AE
H
AF
H
B0
H
B1
H
B2
H
B3
H
B4
H
B5
H
120
H
121
H
25B
H
600
H
601
H
602
H
603
H
604
H
605
H
606
H
2
H
(None)
0
H
(None)
0
H
(None)
0
H
(None)
0
H
User frame use control designation
First frame No. designation
(1st)
(2nd)
(3rd)
419
H
(None)
0
H
(None)
0
H
(None)
0
1002
(Disable)
0
1
H
(YES)
H
H
H
00
H
, 06
H
(1) (0)
31
H
, 30
H
(3) (2)
33
H
, 32
H
(A) (STX)
41
H
, 02
H
(C) (B)
43
H
, 42
H
(1234
H
)
12
H
, 34
H
(LF) (CR)
0A
H
, 0D
H
Buffer memory
(4th)
Last frame No. designation
(1st)
(2nd)
(3rd)
(4th)
Receive transparent code designation
ASCII-BIN conversion designation
Receive user frame
( th)
2)
3)
Rceive data count
Receive data
(arbitrary data area)
4)
To D0
To D3
To D10 or after
Reads combinations of user frames received.
Sets CH1 to the reception channel.
Sets the allowable number of reception data to 6.
Executes reception.
Sets the normal completion flag.
Sets the abnormal completion flag.
11 - 29 11 - 29
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
11.4 Data Transmission
This section explains the arrangement of the transmission data and transmission procedure when transmitting data using a user frame.
11.4.1 Send data
The following describes the data list, codes, and handling of the Q series C24 send data during user frame data transmission.
(1) Send data list
Only the data list combinations shown below are allowed during user frame data transmission.
User frame (first n frames)
Arbitrary data area
(Send data designation area data)
User frame (last m frames)
Data name
Combination
1)
2)
3)
4)
User frame
(first n frames)
Arbitrary data area
2
User frame
(last m frames)
Note
Total 99 frames
Total 100 frames
: Designated data exists
(When ASCII-BIN conversion disabled)
Codes that can be designated
00
H to FF
H
00
H
to FF
H
Codes when transmitting
Note
Added by the Q series C24.
Transmission area data.
1
(When ASCII-BIN conversion enabled)
Codes that can be designated
Codes when transmitting
0
0
H
H
to 9
to 9
H
H
,A
,A
H
H to F
to F
H
H
30
41
30
41
H
H
H
H
to 39
to 46
to 39
to 46
H
H
H
H
,
,
Note
Added by the Q series C24.
The codes shown at the left are 4-bit codes.
Transmission area data.
The codes shown at the left at are 4-bit codes.
1 Four bits of 0
H
to F
H
data are converted to 30
H
to 39
H
and 41
H
to 46
H
ASCII data and transmitted as the data codes of the data to be transmitted
(including the transparent code data).
2 Send data arbitrary data area
1) When the send data count designated by the PLC CPU during transmission in byte units is an odd number of bytes, the data of the lower byte of the last send data storage location of the send data storage area are transmitted.
2) When ASCII-BIN conversion is enabled, the data to be transmitted is transmitted as 2 characters/byte.
11 - 30 11 - 30
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
POINT
Handling of the Q series C24 send data
(1) The data of the user frame and the data of the transmission area designated from the PLC CPU are transmitted in the contents and order set in the buffer memory send user frame designation area.
(2) For the user frame section and arbitrary data section, the data can be sent as
ASCII code using the ASCII-BIN conversion.
For more details on the ASCII-BIN conversion, see Chapter 13.
(3) If send transparent code is designated, the additional code data is added in front of the transparent code/additional code in the data of the designated area during transmission and transmitted.
11 - 31 11 - 31
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
11.4.2 Transmission procedure
The following describes the transmission procedure when transmitting a message containing user frames to the external device.
Procedure
External device
PLC CPU
( 1)
User frame
(1st)
User frame
(nth)
Arbitrary data area
User frame
(mth)
User frame
( th)
( 2)
TO
PLC CPU PRR
ON
Completion device
Status display device at completion
( 3)
ON
Abnormal completion
Normal completion
1 scan
1 Designates the data of the user frame number to send.
2 PLC CPU processing
Before issuing a send request to the Q series C24, designate (write) the following data.
• Transmission user frame designation area
User frame No., transmission method and transmission order registered in the
Q series C24
• Transmission area (Buffer memory)
User data corresponding to transmit message arbitrary data area
3 When a transmission data count error or data transmission error is generated, the
Q series C24 stores the error code to the data transmission result storage area and turns on the transmission abnormal end signal (Xn1).
11 - 32 11 - 32
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
11.4.3 Settings for transmission user frames
These settings are required for sending data to an external device via user frames and the non procedure protocol.
These settings are made from the GX Configurator-SC or the PLC CPU.
(1) Settings via the GX Configurator-SC
Perform settings on the following screen to send data using user frames.
• "Non procedure system settings" screen
• "Transmission user frame No. designation system settings" screen
For setting contents on each screen, see (2).
(2) Settings via the PLC CPU
(a) How to designate and write transmission data when transmitting via user frames
For arbitrary data section when sending a combination of user frames and arbitrary data section, the transmission data count and transmission data are written in the transmission area (the same as when sending them in an arbitrary format.)
User frames are registered using the GX Configurator-SC. Or, the user frame registration number to be sent is written from the PLC CPU to the transmission user frame designation area of the buffer memory as shown in the diagram below.
After executing registration/write, the Q series C24 transmits the designated data in the designated order upon execution of the PRR instruction.
11 - 33 11 - 33
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
To the external device
(Example) Sending data in the following sequence
Sending sequence
1
2
3
4
Transmission data type
User frame
User frame
Arbitrary data
User frame
User frame No.
2
H
( 2)
3E82
H
( 1000)
8000
H
(—32768)
400
H
( 1024)
Contents of sent/registered data
02
H
(STX)
00
H
, 3B
H
(station No., ":")
41
H
, 42
H
, 43
H
, 44
H
("ABCD")
03
H
, FF
H
, F6
H
, 0D
H,
0A
H
(ETX, Sum check, CR, LF)
Address
B6
H
B7
H
B8
H
B9
H
BA
H
BB
H
BC
H
BD
H
BE
H
BF
H
Buffer memory
0 or the following frame designation No
0
1
4
2
H
(1st)
3E8
H
(2nd)
8000
H
(3rd)
400
H
(4th)
0
H
(5th)
0
H
(6th)
1
(Transmission user frame designation area)
•••••User frame being transmitted designation No. area
•••••CR/LF output designation area
•••••Output head pointer designation area
•••••Output head pointer designation area
•••Output count designation area
400
401
402
H
H
H
2 or 4
42
H
(B) , 41
H
(A)
44
H
(D) , 43
H
(C)
(Transmission area)
•••••Transmission data count (word unit/byte unit)
•••Transmission data
1 When sending data that was written to the transmission area, 8000
H
is
used as a temporary user frame number. (Refer to (b) 5))
(When the ASCII-BIN conversion is not performed) User frame
User frame Arbitrary data User frame
1st
S
T
X
(2nd)
(;)
A B C D
E
T
X
(4th)
C
R
L
F
02
H
00
H
3B
H
41
H
42
H
43
H
44
H
03
H
4A
H
0D
H
0A
H
2
H
3E8
H
8000
H
Corresponding frame No.
400
H
Figure at left is for byte units.
For word units, the optional data section is sent in the sequence "ABCD."
11 - 34 11 - 34
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
(b) Transmission user frame designation
The following explains application of the buffer memory to be used when sending data using user frames, along with the designated and stored values.
1) User frame being transmitted storage area (addresses: B6
H
/156
H
)
What number of the output frame number designation area is being sent is stored in the data transmission via user frames.
Buffer memory address B6
H
156
H b15 to
0
H
to 64
H
0
H
to 64
H b0
(CH1 side)
(CH2 side)
0
H
( 0) : Not sent
1
H to 64
H
( 1 to 100) : User frame being transmitted designation No. (nth number)
2) CR/LF output designation area (addresses: B7
H
/157
H
)
When sending a user frame or arbitrary data that does not contain a CR/LF, designate whether a CR+LF will be sent each time a user frame or arbitrary data is sent.
Buffer memory address
B7
H
157
H b15 to
0 to 1
0 to 1 b0
(CH1 side)
(CH2 side)
0 : Do not send
1 : Send
3) Output head pointer designation area (addresses: B8
H
/158
H
)
Write the head position (nth number) in the output frame No.
designation area for writing the registration number of the user frame to be sent.
Buffer memory address
B8
H
158
H b15 to
0 to 100
0 to 100 b0
(CH1 side)
(CH2 side)
0 : No designation
1 : Send from the first to to
100: Send from the 100th
REMARK
Transmission using a user frame cannot be performed when the value of the output head pointer designation area is "0."
11 - 35 11 - 35
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
4) Output count designation area (addresses: B9
H
/159
H
)
Write the output count of the user frames to be sent from the position desingnate in the output head pointer designation area.
Buffer memory address
B9
H
159
H b15 to
0 to 100
0 to 100 b0
(CH1 side)
(CH2 side)
0 : No designation
1 : Transmit 1 frame to to
100: Transmit 100 frames
REMARK
The operation is completed normally without data transmission if the value for the output count designation area is "0."
5) Output frame No. designation area (addresses: BA
H
to 11D
H
/15A
H to 1BD
H
)
• Write the user frame No. to be sent in the order in which they are output from the position designated in the output head pointer designation area.
• When sending data that is written in the transmission area, use
8000
H
as a temporary user frame number.
• By designating user frame number 8000
H
, the Q series C24 transmits the data of the transmission data designation area for the data count designated in the transmission data count designation area.
Buffer memory address
BA
H to
11D
H
0
H
to 801F
H
(1st) to
0
H
to 801F
H
(100th)
(CH1 side)
15A
H to
1BD
H
0
H
to 801F
H
(1st) to
0
H
to 801F
H
(100th)
(CH2 side)
Specifies the following user frame No. for the data to be sent.
Note that the No. on the right side of the user frame No. below is the No. used for transmission without ASCII-BIN conversion for only the data of any frame section when transmission data is converted into ASCII-binary data and transmitted. See Chapters 12 and 13 for details.
0
H
: No transmission designation. (No additional transmission is allowed.)
1
H
to 3E7
H
/4001
H
to 43E7
H
: Transmits the default frame having the designated number.
3E8
H
to 4AF
H
/43E8
H
to 44AF
H
: Transmits the user frame having the designated number. (For flash ROM registration)
8000
H
/C000
H
: Transmits data in the transmission area of the buffer memory.
8001
H
to 801F
H
/C001
H
to C01F
H
: Transmits the user frame having the designated number. (For buffer memory registration)
POINT
The following transmission can be performed by adding 4000
H
to the registered user frame No. and specifying this number.
• When ASCII-BIN conversion is designated, a specified frame can be sent without the conversion. (See Section 13.3.)
• A specified frame can be transmitted without adding the additional code for the send transparent code designation. (See Section 12.3.)
11 - 36 11 - 36
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
11.5 Transmission program
The following are examples of a sequence program when the user frame (four) and transmission area data are transmitted.
In the description of the sample programs, data transmission using user frames is described for the following conditions case:
1) The Q series C24 I/O signals
The Q series C24 installed at QCPU I/O signal addresses X/Y80 to X/Y9F.
2) The Q series C24 interface used in data communications with the external device
The Q series C24 CH1 RS-232 interface
3) Switch setting using the GX Developer
Set the following setting values on the "Intelligent function module switch setting" screen in accordance with Section 4.5 of User's Manual (Basic).
Remarks
Switch 1
Setting item
CH1 Transmission setting
CH1 Communication rate setting
Switch 2 CH1 Communication protocol setting
Switch 3
CH2 Transmission setting
CH2 Communication rate setting
Switch 4 CH2 Communication protocol setting
Setting value
Set according to the external device
0006
H
0000
H
0000
H
—
Non procedure protocol
Not used
Switch 5 Station No. setting 0001
H
Q series C24 station number
(used in the user frame)
Item
Word/byte units designation
Send transparent code designation
ASCII-BIN conversion designation
Output frame No. designation 1st
Output frame No. designation 2nd
Output frame No. designation 3rd
Output frame No. designation 4th
Output frame No. designation 5th
4) Data to be registered on the GX Configurator-SC's "Transmission control and others system setting" screen and the "Non procedure system settings" screen for data communication via user frames
Change the default values for the items listed in the table below. Use default settings for other items.
In example (2), the output frame No. is not registered using the GX
Configurator-SC. (It is registered using a sequence program.)
Set contents
Byte
Buffer memory address to store registration value
96
H
Remarks
Explanation section
No 11F
H
—
Additional code: 10
H
(DLE)
Transparent code: 02
H
(STX)
—
Section 8.4.5 of
User's Manual
(Basic)
Disable
3F2
H
3F3
H
8001
H
8000
H
41B
H
121
H
BA
H
BB
H
BC
H
BD
H
BE
H
See the diagram in the application example.
Section 8.4.10 of
User's Manual
(Basic)
11 - 37 11 - 37
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
External device side
(1) Example of a sequence program when setting is done using the
GX Configurator-SC
See Chapter 17 of this manual for details on the PRR command.
PLC CPU side
Registration No. of the corresponding user frame
S
T
X
Q
02
H
51
H
0A
H
01
H
; T O T A L
3B
H
54
H
4F
H
;
(Total number)
41
H
4C
H
3B
H
(012D
H
2D
H
)
01
H
Transmission area data
(arbitrary data section)
(1234
H
)
34
H
12
H
(56AB
AB
H
H
)
56
H
E
T
X
03
H
37
H
3F2
H
(First specification)
3F3
H
(Second specification)
8001
H
(Third specification)
8000
H
(Fourth specification)
41B
H
(Fifth specification)
Transmission instruction
PLC CPU
Completion device
Status display device at completion
Four bytes of data in the transmission area are sent as is.
(4 byte units in the left diagram.)
11F
H
121
H
1 400
H
401
H
402
H
PRR
(Yes) (No)
1002
H
/ 0D
0
H
H
00
H
, 04
H
(1234
H
)
12
H
, 34
H
(56AB
H
)
56
H
, AB
H
Buffer memory
ON
ON
One scan
Abnormal completion
Normal completion
Send transparent code designation
Tarnsmission area
(transmission data count designation)
(transmission data)
C4
H
C5
H
C6
H
1: 0002
H
for word unit
B6
H
B7
H
B8
H
B9
H
BA
H
BB
H
BC
H
BD
H
BE
H
BF
H
C0
H
C1
H
C2
H
C3
H
C7
H
(Not transmitted)
(Sending)
0
H
/Other than 0
H
(Do not transmit)
0
H
(1st)
1
H
User frame No. being transmitted
CR/LF output designation
Output head pointer designation
5
H
Output count designation
3F2
H
Output frame No. designation (1st)
3F3
H
(2nd)
8001
H
(3rd)
8000
H
(4th)
41B
H
(5th)
0
H
(6th)
3F4
H
(7th)
8002
H
(8th)
3F5
H
(9th)
8003
H
(10th)
3F6
H
(11th)
8004
H
(12th)
41B
H
(13th)
(14th)
0
H
Buffer memory
Transmission instruction
Sets arbitrary transmission data in D1 to D2.
Sets arbitrary transmission data in the transmission area.
Sets CH1 to the transmission channel.
Sets the output head pointer
Sets the output head count
Executes transmission
Sets normal completion flag.
Sets abnormal completion flag.
11 - 38 11 - 38
11 DATA COMMUNICATIONS USING USER FRAMES
MELSEC-Q
(2) Example of a sequence program when setting is not done using the
GX Configurator-SC
The following is the method of data transmission without performing the output frame No. designation using the GX Configurator-SC.
For further details on the PRR instruction, see Chapter 17 of this manual.
Transmission instruction
Sets arbitrary transmission data.
Sets the number of transmitted data.
Sets the transmission user frames in D5 to D9.
Sets output frame No. in the buffer memory.
Sets CH1 to the transmission channel.
Clears the device in which transmission results are stored.
Sets to no CR/LF output.
Sets the output head pointer.
Sets the output counter.
Executes user frame transmission.
Sets normal completion flag.
Sets abnormal completion flag.
D11
D12
D13
D14
D15
D7
D8
D9
D10
D0
D1
Normal end
Send data count
D2
Send data
D5 Output frame No.
D6
Interface No.
(0001
H
)
Transmission result (0000
H
)
CR/LF output (0000
H
)
Output head pointer (0001
H
)
Output counter (0005
H
)
(0004
H
)
(3412
H
)
(AB56
H
)
(03F2
H
)
(03F3
H
)
(8001
H
)
(8000
H
)
(041B
H
)
(0000
H
)
Abnormal end
Send data count (0004
H
)
Send data
Output frame No.
(3412
H
)
(AB56
H
)
(03F2
H
)
(03F3
H
)
Interface No.
(8001
H
)
(8000
H
)
(041B
H
)
(0000
H
)
(0001
H
)
Transmission result (other than 0000
H
)
CR/LF output (0000
H
)
Output head pointer (0001
H
)
Output counter (0005
H
)
11 - 39 11 - 39
12 TRANSPARENT CODES AND ADDITIONAL CODES
MELSEC-Q
12 TRANSPARENT CODES AND ADDITIONAL CODES
Transparent codes and additional codes are used during data communication with an external device to send/receive one-byte data for transmission control on the external device side as user data.
Transparent codes and additional codes are handled in data communication using the non procedure or bidirectional protocol.
• Transparent code: One-byte data for transmission control.
• Additional code : During transmission, one-byte data added preceding the transparent code and additional code data.
During reception, one-byte data deleted (the immediately succeeding one-byte data is processed for reception).
12.1 Handling the Transparent Code and Additional Code Data
The following explains how the Q series C24 handles transparent codes and additional codes during data communication using the non procedure or bidirectional protocol.
The range of additional code data that is added or deleted is explained in Sections
12.3 and 12.5.
(1) During data transmission
Additional code data is added immediately before the transparent code and additional code data set for transmission.
(Example)
Buffer memory
Transparent code
Transparent code
Additional code
Send
(2) During data reception
When additional code data set for reception is detected, the additional code data is removed and the immediately succeeding one-byte data is processed for reception.
(Example)
Buffer memory
Arbitrary code
Additional code
Arbitrary code
Receive
(3) During data communication using the ASCII-BIN conversion
The handling of transparent codes and additional codes is done for data after
ASCII-BIN conversion during transmission and data immediately before the conversion during reception.
(Example) When communicating using an arbitrary format of the non procedure protocol
External device side
Head data
Arbitrary data section
1
31
H
2
32
H
0
30
H
2
32
H
3
33
H
D
L
E
10
H
A B C
41
H
42
H
43
H
Send
Receive
(For 41
H
)
(For 10
H
)
Transparent code
Additional code
Buffer memory (transmission area/reception area)
(H) (L)
(0002
00
H
H
)
, 02
H
(0212H)
02
H
, 12
H
(BC3A
BC
H
H
)
, 3A
H
Transmission data count/Receive data count
Transmission data/ receive data
(The data count is in word units)
12
12 - 1 12 - 1
12 TRANSPARENT CODES AND ADDITIONAL CODES
MELSEC-Q
12
12.2 Registering Transparent Codes and Additional Codes
To control transparent codes and additional codes for data to be sent/received with the non procedure or bidirectional protocol, it is necessary to perform settings in the Q series C24 prior to data communication.
The following explains the registration of transparent and additional codes.
(1) For each interface, 10 combinations and one combination of transparent codes and additional codes can be set for transmission and reception, respectively.
(2) Transparent and additional codes are registered on the GX Configurator-SC's
"Transmission control and others system setting" screen.
For details on the screen used for registration, see Section 8.4.5 of User's Manual
(Basic).
POINT
If additional data code is received during data reception, the Q series C24 will not treat the immediately succeeding one-byte data as the following control data:
• Data received as the first frame and last frame of the user frames
Therefore, do not set the following:
(The code of the data described above cannot be designated as additional codes for data reception).
1) A receive user frame that contains additional code data for data reception
2) The same reception complete code as the additional code data for data reception
12 - 2 12 - 2
12 TRANSPARENT CODES AND ADDITIONAL CODES
MELSEC-Q
12.3 Handling Transparent Codes and Additional Codes During Non Procedure Protocol
Data Communication
The following explains the handling of transparent codes and additional codes during non procedure protocol data communication.
(1) The data designated by the additional code will be added to or deleted from the data to be transmitted or received.
(2) The following shows the range of communication data for which processing of transparent codes and additional codes is performed.
Applicable range during transmission
Message during communication using arbitrary format
Arbitrary data section
Applicable range during reception
Applicable range during transmission
Message during communication using user frames
User frame
(first frame)
Arbitrary data section
User frame
(last frame)
Applicable range during reception
The Q series C24 performs the following processing during data transmission and reception:
(a) When an additional code set for reception is detected during data reception, the additional code data is removed and the immediately succeeding onebyte data is processed for reception as part of the receive data.
(b) When transparent code/additional code data set for transmission is detected during data transmission, the additional code designation data is added immediately before, and is then transmitted.
During data transmission using user frames, even if a transparent code or additional code has been specified in the send transparent code designation area, it is possible to transmit data without adding the additional code data to the user frame portion or arbitrary data.
When sending data without adding the additional code data specified by the send transparent code designation, specify the user frame No. using the following method.
• Specify the number obtained by adding 4000
H
to the registered user frame
No.
b15 b14 b13 to b0
Frame No.
0: Conversion enable 1: Conversion disable
0: Frame registered in flash ROM 1: Frame registered in the buffer memory
12 - 3 12 - 3
12 TRANSPARENT CODES AND ADDITIONAL CODES
MELSEC-Q
When sending the data for the section designated by 4001
H
to 44AF
H
and
C000
H
to C01F
H
, data will be sent without conversion even if "Enable" has been specified in the ASCII-BIN conversion designation area. (See Section
13.3.)
No. of the use frame to be sent
1
H
to 3E7
H
( 1 to 999)
3E8
H
to 4AF
H
( 1000 to 1199)
8000
H
to 801F
H
(-32768 to -32737)
Designation No. when sending data without adding the additional code specified by the send transparent code designation.
4001
H
to 43E7
H
( 16385 to 17383)
43E8
H
to 44AF
H
( 17384 to 17583)
C000
H
to C01F
H
(-16384 to -16353)
12 - 4 12 - 4
12 TRANSPARENT CODES AND ADDITIONAL CODES
MELSEC-Q
(3) The following describes the processing steps taken by the Q series C24 when performing communication with the transparent code designation and the ASCII-
BIN conversion enabled.
(a) Communication using arbitrary format
1) Receiving
• If a receive transparent code is designated, the additional code designation data is deleted (removed).
• The arbitrary data section is stored in the reception area of the buffer memory.
If the ASCII-BIN conversion is designated, the data section is stored in the buffer memory after it has been converted to binary code data.
• During reception of an arbitrary data section, if the reception-complete code data or the entire count of receive data has been stored, a reception-data read is requested of the PLC CPU.
2) Sending
• The transmission data designated from the PLC CPU (arbitrary data section of the transmission message) is sent.
If the ASCII-BIN conversion is designated, the transmission data section is sent after it has been converted to binary code data.
• If a send transparent code is designated, additional code data is added preceding the transparent code/additional code data, and is then transmitted.
External device
Data transmission
Q series C24
(Transparent code designation)
No
Adding additional code
Yes
(ASCII-BIN conversion designation)
No
ASCII-BIN conversion of transmission data
Yes
Buffer memory
Transmission area data
Data reception
No
Yes
Delete additional code
No
Yes
ASCII-BIN conversion of arbitrary data section
Check receive complete code and received data count
Data to be stored in the reception area
12 - 5 12 - 5
12 TRANSPARENT CODES AND ADDITIONAL CODES
MELSEC-Q
(Example) When ASCII-BIN conversion is not performed
External device
(Communicating in an arbitrary format)
Head data
Arbitrary data section
12
H
D
L
E
10
H
02
H
3A
H
BC
H
(For 02
H
)
(For 10
H
)
Send
Receive
Transparent code
Additional code
(Example) When ASCII-BIN conversion is performed
Q series C24
Buffer memory (transmission area/reception area)
(H) (L)
(0002
H
)
00
H
, 02
H
(0212
H
)
02
H
, 12
H
(BC3A
BC
H
H
)
, 3A
H
Transmission data count/Receive data count
Transmission data/ receive data
(The data count is in word units)
External device (Communicating in an arbitrary format)
Head data
Arbitrary data section
1 2 0
31
H
32
H
30
H
2 3
32
H
33
H
D
L
E A B C
10
H
41
H
42
H
43
H
(For 41
H
)
(For 10
H
)
Send
Receive
Transparent code
Additional code
Q series C24
Buffer memory (transmission area/reception area)
(H) (L)
(0002
00
H
H
)
, 02
H
(0212
H
)
02
H
, 12
H
(BC3A
H
)
BC
H
, 3A
H
Transmission data count/Receive data count
Transmission data/ receive data
(The data count is in word units)
12 - 6 12 - 6
12 TRANSPARENT CODES AND ADDITIONAL CODES
MELSEC-Q
(b) Communication using user frames
1) Receiving
• Reception check of user frames (first frame, last frame) is performed.
• If a receive transparent code is designated, the additional code designation data is deleted (removed) from the arbitrary data section.
• If a sum check code is designated in a user frame (last frame), the sum check code is calculated.
• The arbitrary data section is stored in the reception area of the buffer memory.
If the ASCII-BIN conversion is designated, the data section is stored in the buffer memory after it is converted to binary code data.
• During reception of an arbitrary data section, if the reception complete code or the entire count of received data has been stored, or when a user frame (last frame) has been received, a receive data read is requested of the PLC CPU.
2) Sending
• The transmission data designated by a user frame or the PLC CPU
(arbitrary data section of the transmission message) is sent in the order designated by the user.
• If the ASCII-BIN conversion is designated, the applicable range of data is sent after data is converted to ASCII code data.
Also, if a send transparent code is designated, the applicable range of data is sent after adding additional code data before the transparent code/additional code data.
External device
Data transmission
Q series C24
(Transparent code designation) (Sum check code designation) (ASCII-BIN conversion designation)
No No No
Adding additional code
Yes
Calculating sum check code using user frames
Yes
ASCII-BIN conversion of transmission data
Yes
Buffer memory
Data designated in the output frame No. designation area
For Output count designation
Data reception
Check and delete user frames
No No
Yes
Delete additional code
Yes
(Arbitrary data section only)
Calculate and check sum check code using user frames
No
Yes
ASCII-BIN conversion of arbitrary data section
Check reception complete code and received data count
Data stored in the reception area
POINT
Explained above is how the Q series C24 processes communication data when enabling and disabling the communication via the user-frame function, ASCII-BIN conversion function, and/or transparent code-designation communication function.
When communicating data to an external device, use this information as a reference in the selection of a communication method.
12 - 7 12 - 7
12 TRANSPARENT CODES AND ADDITIONAL CODES
MELSEC-Q
12.4 Example of Data Communication Using the Non Procedure Protocol
This section shows examples of data communication using the non procedure protocol when the following settings and registrations are made.
(1) Settings via GX Developer
Perform the following settings on the "Intelligent functional module switch setting" screen.
(See Section 4.5 of the User's Manual (Basic))
Remarks
Switch 1
Switch 2
Switch 3
Switch 4
Setting item
CH1 Transmission setting
CH1 Communication rate setting
CH1 Communication protocol setting
CH2 Transmission setting
CH2 Communication rate setting
CH2 Communication protocol setting
Setting value
Set according to the external device
0006
H
0000
H
0000
H
—
Non procedure protocol
Not used
Switch 5 Station No. setting 0000
H
Q series C24 station number
(2) Settings via GX Configurator-SC
Register the following on the "Transmission control and others system setting" screen and the "Non procedure system settings" screen.
(See Sections 8.4.5 and 8.4.7 of User's Manual (Basic))
For items other than those noted below, the default values are used.
Setting value Registration screen Setting item
Transmission control and other system settings
Send transparent code designation 1st combination
Send transparent code designation 2nd combination
Receive transparent code designation 1st combination
Non procedure system settings Received data count designation
1002
H
1003
H
1002
H
0006
H
Remarks
Transparent code : 02
H
(STX)
Additional code : 10
H
(DLE)
Transparent code : 03
H
(ETX)
Additional code : 10
H
(DLE)
Transparent code : 02
H
(STX)
Additional code : 10
H
(DLE)
—
12 - 8 12 - 8
12 TRANSPARENT CODES AND ADDITIONAL CODES
MELSEC-Q
12.4.1 Example of data reception
External device side
Head data
The following shows an example of storing receive data in the data register.
(1) Receiving based on the receive complete code
Additional code: 10
H
(DLE), transparent code: 02
H
(STX), complete code: 0D0A
H
(CR + LF)
Additional code (Q series C24 deletes)
Transparent code
0 1 2 3
D
L
E
S
T
X L
L
N
U A B
C
R
L
F
(1234
H
)
30
H
31
H
32
H
33
H
10
H
02
H
00
H
41
H
42
H
34
H
12
H
0D
H
0A
H
For word unit:
Received byte count excluding additional code (12)/2=6
For byte unit:
Received byte count excluding additional code (12)
PLC CPU side
Reception data read request
X83
PLC CPU
Completion device
M0
Status display device at completion
M1
INPUT
ON
ON
One scan
Received data count is stored
The following diagram is for word unit
Abnormal completion
Normal completion
600
H
601
H
602
H
603
H
604
H
605
H
606
H
00
H
, 06
H
(1) (0)
31
H
, 30
(3) (2)
H
33
H
, 32
H
(NULL) (STX)
00
H
, 02
H
(B) (A)
42
H
, 41
H
(1234
H
)
12
H
, 34
H
(LF) (CR)
0A
H
, 0D
H
Buffer memory
D3
D10
D11
D12
D13
D14
D15
00
H
, 06
H
(0) (0)
31
H
, 30
(3) (2)
H
33
H
, 32
H
(NULL) (STX)
00
H
, 02
H
(B) (A)
42
H
, 41
H
(1234
H
)
12
H
, 34
H
(LF) (CR)
0A
H
, 0D
H
Sequence program device memory
Reception data read request
Sets CH1 to the reception channel
Sets the allowable number of receive data to 6
Executes reception
Sets the normal completion flag
Sets the abnormal completion flag
POINT
When the receive transparent code designation is set to Enable and the ASCII-BIN conversion is set to Disable, the codes for receivable data and those for receive data that is stored in the buffer memory's reception area as follows:
Receive transparent code designation section
Additional code
Transparent code
Arbitrary data section (including complete code)
Receivable codes
01
H
to FF
H
00
H
to FF
H
00
H
to FF
H
Codes stored in the reception area
(Delete)
00
H
to FF
H
00
H
to FF
H
12 - 9 12 - 9
12 TRANSPARENT CODES AND ADDITIONAL CODES
MELSEC-Q
(2) Receiving based on the completed data count
Additional code: 10
H
(DLE), transparent code: 02
H
(STX),
Completed data count: Six words or 12 bytes
External device side
Head data
Additional code (Q series C24 deletes)
Transparent code
0 1 2 3
D
L
E
S
T
X L
L
N
U A B
C
R
L
F
(1234
H
)
30
H
31
H
32
H
33
H
10
H
02
H
00
H
41
H
42
H
34
H
12
H
0D
H
0A
H
For word unit:
Received byte count excluding additional code (12)/2=6
For byte unit:
Received byte count excluding additional code (12)
PLC CPU side
Reception data read request
X83
PLC CPU
Completion device M0
Status display device at completion
M1
Reception data read request
INPUT
ON
ON
One scan
Received data count is stored
The following diagram is for word unit
Abnormal completion
Normal completion
600
H
601
H
602
H
603
H
604
H
605
H
606
H
00
H
, 06
H
(1) (0)
31
H
, 30
H
(3) (2)
33
H
, 32
H
(NULL) (STX)
00
H
, 02
H
(B) (A)
42
H
, 41
H
(1234
H
)
12
H
, 34
H
(LF) (CR)
0A
H
, 0D
H
Buffer memory
D2
D10
D11
D12
D13
D14
D15
00
H
, 06
H
(0) (0)
31
H
, 30
H
(3) (2)
33
H
, 32
H
(NULL) (STX)
00
H
, 02
H
(B) (A)
42
H
, 41
H
(1234
H
)
12
H
, 34
H
(LF) (CR)
0A
H
, 0D
H
Sequence program device memory
0
Sets CH1 to the reception channel
Sets the allowable number of receive data to 6
Executes reception
Sets the normal completion flag
Sets the abnormal completion flag
POINT
When the receive transparent code designation is set to Enable and the ASCII-BIN conversion is set to Disable, the codes for receivable data and those for receive data that is stored in the buffer memory's reception area as follows:
Receive transparent code designation section
Additional code
Transparent code
Arbitrary data section (including complete code)
Receivable codes
01
H
to FF
H
00
H
to FF
H
00
H
to FF
H
Codes stored in the reception area
(Delete)
00
H
to FF
H
00
H
to FF
H
12 - 10 12 - 10
12 TRANSPARENT CODES AND ADDITIONAL CODES
MELSEC-Q
12.4.2 Example of data transmission
External device side
PLC CPU side
The following shows an example of data transmission.
1) Additional code: 10
H
(DLE), transparent code: 02
H
(STX)
Head data
Additional code (Q series C24 deletes)
Transparent code
0 1 2 3
D
L
E
S
T
X L
L
N
U A B
C
R
L
F
(1234
H
)
30
H
31
H
32
H
33
H
10
H
02
H
00
H
41
H
42
H
34
H
12
H
0D
H
0A
H
For word unit:
Received byte count excluding additional code (12)/2=6
For byte unit:
Received byte count excluding additional code (12)
Transmission command
PLC CPU
X50
Completion device
M0
Status display device at completion
M1
OUTPUT
Transmission instruction
ON
Transmission data count
ON
Abnormal completion
Normal completion
One scan
D3
D10
D11
D12
D13
D14
D15
00
H
, 06
H
(1) (0)
31
H
, 30
H
(3) (2)
33
H
, 32
H
(NULL) (STX)
00
H
, 02
H
(B) (A)
42
H
, 41
H
(1234
H
)
12
H
, 34
H
(LF) (CR)
0A
H
, 0D
H
Sequence program device memory
The following diagram is for word unit
400
401
402
403
404
405
H
H
H
H
H
H
406H
00
H
, 06
H
(1) (0)
31
H
, 30
H
(3) (2)
33
H
, 32
H
(NULL) (STX)
00
H
, 02
H
(B) (A)
42
H
, 41
H
(1234
H
)
12
H
, 34
H
(LF) (CR)
0A
H
, 0D
H
Buffer memory
Sets transmission data in D10 to D15
Sets CH1 to the transmission channel
Sets the allowable number of transmitting data to 6
Executes transmission
Sets normal completion flag
Sets abnormal completion flag
12 - 11 12 - 11
12 TRANSPARENT CODES AND ADDITIONAL CODES
External device side
PLC CPU side
MELSEC-Q
2) Additional code: 10
H
(DLE), transparent code: 02
H
(STX) (1st group)
Additional code: 10
H
(DLE), transparent code: 03
H
(ETX) (2nd group)
Head data
0 1 2 3
D
L
E
S
T
X
Additional code
(1st group)
L
L
N
U
Transparent code
(1st group)
A B
D
L
E
E
T
X
L
L
N
U
Additional code
(2nd group)
Transparent code
(1st group)
C
R
L
F
30
H
31
H
32
H
33
H
10
H
02
H
00
H
41
H
42
H
10
H
03
H
00
H
0D
H
0A
H
For word unit:
Received byte count excluding additional code (12)/2=6
For byte unit:
Received byte count excluding additional code (12)
Transmission command
PLC CPU
X50
Completion device
Status display device at completion
M0
M1
OUTPUT
Transmission instruction
ON
ON
Abnormal completion
Normal completion
One scan
D3
D10
D11
D12
D13
D14
D15
00
H
, 06
H
(1) (0)
31
H
, 30
H
(3) (2)
33
H
, 32
H
(NULL) (STX)
00
H
, 02
H
(B) (A)
42
H
, 41
H
(NULL) (ETX)
00
H
, 03
H
(LF) (CR)
0A
H
, 0D
H
Sequence program device memory
The following diagram is for word unit
400
401
402
403
404
405
406
H
H
H
H
H
H
H
Transmission data count
00
H
, 06
H
(1) (0)
31
H
, 30
H
(3) (2)
33
H
, 32
H
(NULL) (STX)
00
H
, 02
H
(B) (A)
42
H
, 41
H
(NULL) (ETX)
00
H
, 03
H
(LF) (CR)
0A
H
, 0D
H
Buffer memory
Sets transmission data in D10 to D15
Sets CH1 to the transmission channel
Sets the number of transmitting data to 6
Executes transmission
Sets normal completion flag
Sets abnormal completion flag
12 - 12 12 - 12
12 TRANSPARENT CODES AND ADDITIONAL CODES
MELSEC-Q
12.5 Handling Transparent Codes and Additional Codes During Bidirectional Protocol Data
Communication
The following explains the handling of transparent codes and additional codes during data communication using the bidirectional protocol.
(1) The additional code designation data will be added to or deleted from the data that is sent or received.
(2) Communication data for which transmission/reception processing of transparent codes and additional codes is performed includes the message data length, data section and error code.
Such processing is not performed for the head code (ENQ, ACK, NAK) and sum check code of a message.
(Example)
Transmission sequence
External device side
PLC CPU side
E
N
Q
Data length
L H
Data section
(Designated transmission data)
Sum check code
L H
A
C
K
(When normal)
N
A
K
L
Error code
(When abnormal)
H
Applicable data range
The Q series C24 performs the following processing during data transmission/reception.
(a) When an additional code set for reception is detected during data reception, the additional code data is removed and the immediately succeeding onebyte data is processed for reception as part of the receive data.
When transparent code/additional code data set for transmission is detected during transmission of a message in response to data reception, the additional code designation data is added immediately before, and is then transmitted.
(b) When transparent code/additional code data set for transmission is detected during data transmission, the additional code designation data is added immediately before, and is then transmitted.
When an additional code set for reception is detected while a message is being received in response to data transmission, the additional code data is removed and the immediately succeeding one-byte data is processed for reception as part of the receive data.
Message
E
N
Q
05
H
Data length
D
L
E
10
H
(c) Data having an additional code that is added or deleted cannot be included in the data length, nor will it be used for the sum check code.
(Example) When not using the ASCII-BIN conversion
Data section
(0002
H
)
L
02
H
H
00
H
12
H
D
L
E
10
H
Additional code
Transparent code
L
Sum check code
H
02
H
3A
H
BC
H
0C
H
01
H
Additional code: 10
H
Transparent code: 02
H
Buffer memory
(H) (L)
00
H
, 02
H
02
H
, 12
H
BC
H
, 3A
H
Transmission data count/
Receive data count
Transmission data/ receive data
12 - 13 12 - 13
12 TRANSPARENT CODES AND ADDITIONAL CODES
MELSEC-Q
(3) The following shows the processing steps taken by the Q series C24 when performing communication with the transparent code designation and ASCII-BIN conversion enabled.
POINT
Explained above is how the Q series C24 processes communication data, when enabling and disabling the ASCII-BIN conversion function and/or transparent code designation communication function.
When communicating data to an external device, use this information as a reference in the selection of a communication method.
(a) Receiving
1) If a receive transparent code is designated, the additional code designation data is deleted (removed) from the arbitrary data section.
2) The arbitrary data section is stored in the reception area of the buffer memory.
If the ASCII-BIN conversion is designated, the data section is stored in the buffer memory after it is converted to binary code data.
3) When the data section of the designated data length is received, a receive data read is requested of the PLC CPU.
If the sum check code is set to Enable in the transmission setting via GX
Developer switch settings, a reception data read is requested of the PLC
CPU upon reception of the sum check code.
External device
Data reception
Q series C24
(Transparent code designation)
No
(Arbitrary data section only)
Yes
Deleting additional code
Response transmission
Adding additional code
Yes
(Error code section only)
No
Deleting transmission control code (ENQ)
Adding transmission control code
(ACK/NAK)
(Sum check code setting)
No
Yes
Calculation and check of sum check code
(ASCII-BIN conversion designation)
No
Yes
ASCII-BIN conversion of data length, data section
ASCII-BIN conversion of error code
Yes
No
Buffer memory
Reception area
Reception result storage area
(b) Sending
1) The transmission control code data is added to the transmission data designated by the PLC CPU (arbitrary data section of the transmission message), and that transmission data is transmitted.
If ASCII-BIN conversion is designated, the transmission data is sent after it is converted to ASCII code data.
2) If the sum check code is set to Enable in the transmission setting via GX
Developer switch settings, the code will be calculated from the transmission message and added to the transmission message.
12 - 14 12 - 14
12 TRANSPARENT CODES AND ADDITIONAL CODES
MELSEC-Q
3) If a send transparent code is designated, additional code data is added preceding the transparent code/additional code data for the arbitrary data section, and is then sent.
External device
Data transmission
Q series C24
(Transparent code designation)
No
(Arbitrary data section only)
Adding additional code
Yes
Response reception
Yes
Deleting additional code
(Error code section only)
No
Adding transmission control code (ENQ)
Deleting transmission control code
(ACK/NAK)
(Sum check code setting)
No
Calculation and check of sum check code
Yes
(ASCII-BIN conversion designation)
No
ASCII-BIN conversion of transmission data count and transmission data
Yes
Yes
No
ASCII-BIN conversion of error code
Buffer memory
Transmission area
Transmission result storage area
(Example) The following example shows the data arrangement when data is sent and received. (The communication section of the response message is omitted).
(When the ASCII-BIN conversion is not performed)
External device
Head data
Arbitrary data section
E
N
Q
Data length
05
H
D
L
E
L
10
H
02
H
H
00
H
12
H
Data section
D
L
E
10
H
02
H
3A
H
BC
H
Sum check
code
L H
0C
H
01
H
(For 10
H
)
(For 02
H
)
Additional code
Transparent code
Send
Receive
Q series C24
Buffer memory (transmission area/reception area)
(H) (L)
(0002
H
)
00
H
, 02
H
(0212
H
)
02
H
, 12
H
(BC3A
H
)
BC
H
, 3A
H
Transmission data count/Receive data count
Transmission data/ receive data
(The data count is in word units)
(When the ASCII-BIN conversion is performed)
External device
Head data
Arbitrary data section
E
N
Q
05
H
0
L
Data length
2
30
H
32
H
H
0 0
30
H
30
H
1 2 0
31
H
32
H
30
H
Data section
2 3
32
H
33
H
D
L
E A B C
10
H
41
H
42
H
43
H
80
H
L
Sum check
code
H
02
H
Send
Receive
(For 41
H
)
(For 10
H
)
Transparent code
Additional code
Q series C24
Buffer memory (transmission area/reception area)
(H) (L)
(0002
H
)
00
H
, 02
H
(0212
H
)
02
H
, 12
H
(BC3A
H
)
BC
H
, 3A
H
Transmission data count/Receive data count
Transmission data/ receive data
(The data count is in word units)
12 - 15 12 - 15
12 TRANSPARENT CODES AND ADDITIONAL CODES
MELSEC-Q
12.6 Example of Data Communication Using the Bidirectional Protocol
This section shows examples of the bidirectional protocol data communication when the following settings and registrations are made.
(1) Settings via GX Developer
Perform the following settings on the "Switch setting" screen.
(See Section 4.5 of the User's Manual (Basic)).
Switch 1
Switch 2
Switch 3
Switch 4
Setting item
CH1 Transmission setting
CH1 Communication rate setting
CH1 Communication protocol setting
CH2 Transmission setting
CH2 Communication rate setting
CH2 Communication protocol setting
Setting value
Set according to the external device
0007
H
0000
H
0000
H
Remarks
—
Bidirectional protocol
Not used
Switch 5 Station No. setting 0000
H
Q series C24 station number
Registration screen
(2) Settings via GX Configurator-SC
Register the following settings on the "Transmission control and others system setting" screen.
(See Section 8.4.5 of User's Manual (Basic)).
For items other than those listed below, the default values are used.
Setting value
Transmission control and other system settings
Setting item
Send transparent code designation 1st combination
Send transparent code designation 2nd combination
Receive transparent code designation 1st combination
1002
H
1003
H
1002
H
Remarks
Transparent code : 02
H
(STX)
Additional code : 10
H
(DLE)
Transparent code : 03
H
(ETX)
Additional code : 10
H
(DLE)
Transparent code : 02
H
(STX)
Additional code : 10
H
(DLE)
12 - 16 12 - 16
12 TRANSPARENT CODES AND ADDITIONAL CODES
MELSEC-Q
12.6.1 Example of data reception
External device side
PLC CPU side
The following shows an example of storing receive data in the data register.
(1) When the receive transparent code designation is set to Enable and the ASCII-BIN conversion is set to Disable
Additional code: 10
H
(DLE), transparent code: 02
H
(STX)
Additional code (the Q series C24 deletes.)
Transparent code
E
N
Q
05
H
Data length
(0004
H
)
L H
04
H
00
H
D
L
E
10
H
Data section
C L
Sum check code
(1102
H
)
02
H
11
H
A
41
H
B
42
H
(1234
H
)
34
H
12
H
R
0D
H
F
0A
H
L H
F7
H
00
H
A
C
K
06
H
Reception data read request
X83
PLC CPU
Completion device
M0
Status display device at completion
M1
Reception data read request
BIDIN
Data length (receive data count):
Excluding additional codes
For word unit : 0004
H
ON
ON
Abnormal completion
The following diagram is for word unit
One scan
Normal completion
Data length 600
H
Data section
601
H
602
H
603
H
604
H
00
H
, 04
H
(1102
H
)
11
H
, 02
H
(B) (A)
42
H
, 41
H
(1234
H
)
12
H
, 34
H
(LF) (CR)
0A
H
, 0D
H
Buffer memory
D3
D10
00
H
, 04
H
(1102
H
)
11
H
, 02
H
(B) (A)
D11
D12
42
H
, 41
H
(1234
H
)
12
H
, 34
H
(LF) (CR)
D13
0A
H
, 0D
H
Sequence program device memory
Sets CH1 to the reception channel
Sets the allowable number of receive data to 6
Executes reception
Sets the normal completion flag
Sets the abnormal completion flag
POINT
(1) When the receive transparent code designation is set to Enable and ASCII-
BIN conversion is set to Disable, the codes for receivable arbitrary data sections and those for receive data that is stored in the buffer memory's reception area are as follows:
Receivable codes
Codes stored in the reception area
(Delete)
Receive transparent code designation section
Data length, data section
Additional code
Transparent code
01
H
to FF
H
00
H
to FF
H
00
H
to FF
H
(2) When the data length used is in byte units and the data length is an odd byte,
00
H
will be stored in the upper byte of the last data-storage position in the reception area.
12 - 17 12 - 17
12 TRANSPARENT CODES AND ADDITIONAL CODES
MELSEC-Q
External device side
PLC CPU side
Reception data read request
PLC CPU
X83
Completion device
Status display device at completion
M0
M1
(2) When the receive transparent code designation is set to Enable and the ASCII-BIN conversion is set to Enable
Additional code: 10
H
(DLE), transparent code: 02
H
(STX)
E
N
Q
Data length
(0004
H
)
Data section
Sum check
code
05
H
0
30
H
L
4
H
0 0
34
H
30
H
30
H
0
30
H
2 1
32
H
31
H
1
31
H
4
34
H
1
31
H
4 2
34
H
32
H
3
33
H
4 1
34
H
31
H
2
32
H
0
30
H
L H
D
44
H
0 A
30
H
41
H
02
H
04
H
Exclude the additional code and set to an even byte.
A
C
K
BIDIN
ON
ON
Abnormal completion
Normal completion
One scan
Data length
06
H
Two bytes of receive data are read to the
PLC CPU as one-byte data
(excluding the additional code).
Data length (No. of receive data):
Excluding additional code
For word unit;
Byte count after ASCII-BIN conversion (8)/2=4
For byte unit;
Byte count after ASCII-BIN conversion (4)
The following diagram is for word unit
Data section
600
H
00
H
, 04
H
601
H
11
H
, 02
H
602
H
42
H
, 41
H
603
H
12
H
, 34
H
604
H
0A
H
, 0D
H
Buffer memory
D3
00
H
, 04
H
D10
11
H
, 02
H
D11
42
H
, 41
H
D12
12
H
, 34
H
D13
0A
H
, 0D
H
Sequence program device memory
Transmission instruction
Sets CH1 to the reception channel
Sets the allowable number of receive data to 6
Executes reception
Sets the normal completion flag
Sets the abnormal completion flag
POINT
(1) When the receive transparent code designation is set to Enable and the ASCII-
BIN conversion is set to Enable, the codes for receivable arbitrary data section and those for receive data that is stored in the buffer memory's reception area as follows:
Receive transparent code designation section
Data length, data section
Additional code
Transparent code
Receivable codes
01
H
to FF
H
30
H
to 39
H
41
H
to 46
H
Codes stored in the reception area
(Delete)
0
H
to 9
H
A
H
to F
H
12 - 18 12 - 18
12 TRANSPARENT CODES AND ADDITIONAL CODES
MELSEC-Q
12.6.2 Example of data transmission
The following shows an example of data transmission.
(1) When the send transparent code designation is set to Enable and the ASCII-BIN conversion is set to Disable
Additional code: 10
H
(DLE), transparent code: 02
H
(STX) (1st group)
Additional code: 10
H
(DLE), transparent code: 03
H
(ETX) (2nd group)
A
C
K
External device side
PLC CPU side
Transparent code (2nd group)
Additional code (2nd group)
E
N
Q
05
H
Data length
(0004
H
)
L H
04
H
00
H
D
L
E
10
H
(1102
H
)
02
H
11
H
Data section
A B
41
H
42
H
D
L
E
10
H
Sum check code
C L
03
H
00
H
L H
(0003
H
) R F
0D
H
0A
H
B4
H
00
H
Transparent code (1st group)
Additional code (1st group)
06
H
Transmission command
X50
PLC CPU
Completion device
Status display device at completion
M0
M1
BIDOUT
ON
ON
One scan
Abnormal completion
Normal completion
Data length (transmission data count):
Excluding additional codes
For word unit : 0004
H
For byte unit : 0008
H
Transmission data
The following diagram is for word unit
D3
D10
D11
D12
D13
00
H
, 04
H
(1102
H
)
11
H
, 02
H
(B) (A)
42
H
, 41
H
(0003
H
)
00
H
, 03
H
(LF) (CR)
0A
H
, 0D
H
Sequence program device memory
Address
400
H
401
H
402
H
403
H
404
H
00
H
, 04
H
(1102
H
)
11
H
, 02
H
(B) (A)
42
H
, 41
H
(0003
H
)
00
H
, 03
H
(LF) (CR)
0A
H
, 0D
H
Buffer memory
Transmission instruction
Sets CH1 to the transmission channel
Sets transmission data count to 4
Sets the transmission data in D10 to D13
Executes transmission
Sets the normal completion flag
Sets the abnormal completion flag
12 - 19 12 - 19
12 TRANSPARENT CODES AND ADDITIONAL CODES
External device side
PLC CPU side
MELSEC-Q
(2) When the send transparent code designation is set to Enabled and the ASCII-BIN conversion is set to Enabled
Additional code: 10
H
(DLE), transparent code: 02
H
(STX) (1st group)
Additional cede: 10
H
(DLE), transparent code: 03
H
(ETX) (2nd group)
A
C
K
06
H
E
N
Q
Data length
(0004
H
)
Data section
Sum check code
0
05
H
30
H
L
34
H
30
H
30
H
0
30
H
2
32
H
1
31
H
1
31
H
4
34
H
1 4
31
H
34
H
2 0
32
H
30
H
3 0
33
H
30
H
0 0
30
H
30
H
D 0
44
H
30
H
L H
A
41
H
FB
H
03
H
Transmission command X50
PLC CPU
Completion device
Status display device at completion
M0
M1
Transmission instruction
BIDOUT
ON
Data length (No. of transmission data):
Excluding additional code
For word unit;
Byte count before ASCII-BIN conversion (8)/2=4
For byte unit;
Byte count before ASCII-BIN conversion (8)
ON
One scan
Abnormal completion
Normal completion
Transmission data
The following diagram is for word unit
D3
00
H
, 04
H
D10
11
H
, 02
H
D11
42
H
, 41
H
D12
00
H
, 03
H
D13
0A
H
, 0D
H
Sequence program device memory
Address
400
H
00
H
, 04
H
401
H
11
H
, 02
H
402
H
42
H
, 41
H
403
H
00
H
, 03
H
404
H
0A
H
, 0D
H
Buffer memory
Sets CH1 to the transmission channel
Sets transmission data count to 4
Sets the transmission data in D10 to D13
Executes transmission
Sets normal completion flag
Sets abnormal completion flag
POINT
One word of data designated from the PLC CPU is converted to four-byte data ("0" to "9", "A" to "F"), and is then transmitted.
12 - 20 12 - 20
13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION)
MELSEC-Q
13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION)
This chapter explains the binary-to-ASCII conversion (called ASCII-BIN conversion) in order to send/receive data in ASCII format to/from an external device.
13.1 ASCII-BIN Conversion
PLC CPU
Q25HCPU
MODE
RUN
ERR.
USER
BAT.
BOOT
ASCII-BIN conversion is a data conversion function that converts all data communicated between the Q series C24 and an external device to ASCII code data.
The ASCII-BIN conversion of communication data is performed by the Q series C24 according to the user settings.
External device
Q series C24
QJ71C24
CH1.
CH2.
CH1.
With ASCII-BIN conversion
32
H
31
H
34
H
33
H
1234
H
37
H
38
H
35
H
36
H
RS-232
13
USB
RS-232
5678
H
CH.2
SDA
SG
SDB
(FG)
RDA
(FG)
RDB
RS-422
/485
2
4
6
1
3
5
7
Without ASCII-BIN conversion
12
H
34
H
78
H
56
H
13.2 Settings for ASCII-BIN Conversion
In order to convert data to be sent/received via the non procedure protocol and bidirectional protocol from binary code to ASCII code, it is necessary to make specific settings for the Q series C24 before performing data communication.
The following describes the settings for the ASCII-BIN conversion:
(1) The ASCII-BIN conversion settings can be designated for each interface.
(2) The ASCII-BIN conversion settings are registered in the "Transmission control and others system setting" screen of GX Configurator-SC.
For the registration screen, see Section 8.4.5 of the User's Manual (Basic).
13 - 1 13 - 1
13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION)
MELSEC-Q
13
13.3 Performing ASCII-BIN Conversion for Data Communicated via Non Procedure Protocol
This section explains the ASCII-BIN conversion of data to be communicated using the non procedure protocol.
(1) The following shows the range of send/receive data for which ASCII-BIN conversion can be performed:
Applicable data range at transmission
Message at transmission/ reception in arbitrary format
Arbitrary data section
Applicable data range at reception
Applicable data range at transmission
Message at transmission/ reception using user frames
User frame
(first frame)
Arbitrary data section
User frame
(last frame)
Applicable data range at reception
When sending or receiving data, the Q series C24 processes data as follows:
1) Out of the data in the applicable data range shown above, the Q series C24 sends and receives data whose data code is in the range of 30
H
to 39
H
("0" to
"9") and 41
H
to 46
H
("A" to "F").
2) During data reception, the Q series C24 regards the arbitrary data section as
ASCII code data, converting it to binary code data for storage in the buffer memory.
The user frame section is received in the data format corresponding to the registration contents in the Q series C 24. During data transmission, the Q series C 24 regards data designated by the PLC CPU (an arbitrary data section in the transmission message) and user-frame sections as binary code data, converting them into ASCII code data and transmitting them.
External device (When communicated in an arbitrary format)
Head data
Arbitrary data section
Send
1
31
H
2 0
32
H
30
H
2 3
32
H
33
H
A B C
41
H
42
H
43
H
Receive
Buffer memory (transmission area/reception area)
(H) (L)
(0002
H
)
00
H
, 02
H
02
(0212
H
)
H
, 12
H
(BC3A
H
)
BC
H
, 3A
H
Trasmission data count/Rreceive data count
Transmission data/ receive data
(No. of data in word units)
13 - 2 13 - 2
13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION)
MELSEC-Q
Even if ASCII-BIN conversion is "enabled," it is possible to transmit data without converting the data in any user frame portion or buffer memory transmission area. When sending data without ASCII-BIN conversion, specify the user frame No. using the following method.
• Specify the number obtained by adding 4000H to the registered user frame No.
b15 b14 b13 to b0
Number of frames
0: Conversion enabled 1: Conversion disabled
0: Frame registered in Flash ROM 1: Frame registered in buffer memory
When sending data in the sections designated in 4001
H
to 44AF
H
, C000
H
to
C01F
H
, the additional codes by transmission transparent code designation will not be added. (See Section 12.3)
User frame No. to be sent
1
H
to 3E7
H
( 1 to 999)
3R8
H
to 4AF
H
( 1000 to 1199)
8000
H
to 801F
H
( -32768 to -32737)
Designated No. when transmitting without
ASCII-BIN conversion
4001
H
to 43E7
H
( 16385 to 17383)
43E8
H
to 44AF
H
( 17384 to 17583)
C000
H
to C01F
H
( -16384 to -16353)
(2) The processing steps taken by the Q series C24 when communicating with ASCII-
BIN conversion and transparent code designation enabled are explained in
Section 12.3.
• Transmission/reception in arbitrary formats
• Transmission/reception using user frames
13 - 3 13 - 3
13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION)
MELSEC-Q
13.4 Example of Data Communication Using the Non Procedure Protocol
This section shows examples of data communication using the non procedure protocol when the following settings/registrations are made.
(1) Settings via GX Developer
Perform the following settings on the "Intelligent function module switch setting" screen.
(See Section 4.5 of the User's Manual (Basic).)
Remarks
Switch 1
Switch 2
Switch 3
Switch 4
Setting item
CH1 Transmission setting
CH1 Communication rate setting
CH1 Communication protocol setting
CH2 Transmission setting
CH2 Communication rate setting
CH2 Communication protocol setting
Setting value
Set according to the external device
0006
H
0000
H
0000
H
Not used
—
Non procedure protocol
Switch 5 Station No. setting 0000
H
Station number of the Q series C24
(2) Settings via GX Configurator-SC
Register the following items on the "Transmission control and others system setting," "Non procedure system setting," and "Transmission user frame No.
designation system setting" screens.
(See Sections 8.4.5, 8.4.7 and 8.4.10 of the User's Manual (Basic).)
Registration screen
"Non procedure system setting" screen
For items other than those noted below, the default values are used.
"Transmission user frame No. designation system setting" screen
Setting item
Received data count designation
Receive complete code designation
Receive user frame designation
User frame use enable/disable designation
Receive user frame designation
First frame No. designation 1st
Receive user frame designation
First frame No. designation 2nd
Receive user frame designation
Last frame No. designation 1st
Receive user frame designation
Last frame No. designation 2nd
Transmission user frame designation
Output head pointer designation
Transmission user frame designation
Output count designation
Output frame No. designation 1st
Output frame No. designation 2nd
Output frame No. designation 3rd
Output frame No. designation 4th
Output frame No. designation 5th
Setting value
0003
H
0009
H
Enable
03E8
H
03E9
H
041B
H
041B
H
0001
H
0005
H
43F2
H
43F3
H
C001
H
8000
H
441B
H
"Transmission control and others system setting" screen
ASCII-BIN conversion designation Enable
13 - 4 13 - 4
13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION)
MELSEC-Q
13.4.1 Example of data reception
Head data
External device side
The following shows an example of data reception:
(1) Reception using the receive complete code
Complete code: 9
H
...... (the code after ASCII-BIN conversion)
0 1 2 3 4 5 A B C D E 9
Data corresponding to complete code
Number of bytes after
ASCII-BIN conversion:
((6)/2=3) when word units are used,
(6) when byte units are used
• Two bytes of receive data is read to
the PLC CPU as one-byte data.
• Send data from the external device so
that the converted complete code data is
arranged with data having an even
byte number.
30
H
31
H
32
H
33
H
34
H
35
H
41
H
42
H
43
H
44
H
45
H
39
H
Set to even byte
PLC CPU
Reception data read request
PLC CPU
X83
Completion device
Status display device at completion
M0
M1
INPUT
Store data received count
ON
ON
One scan
The diagram below is for when word units are used.
Abnormal completion
Normal completion
600
H
00
H
, 03
H
601
H
23
H
, 01
H
602
H
AB
H
, 45
H
603
H
E9
H
, CD
H
Buffer memory
3)
2)
D2
00
H
, 03
H
D10
23
H
, 01
H
D11
AB
H
, 45
H
D12
E9
H
, CD
H
Sequence program device memory
Reception data read request
Sets CH1 to the reception channel
Sets the allowable number of receive data to 6
Executes reception
Sets the normal completion flag
Sets the abnormal completion flag
POINT
(1) When ASCII-BIN conversion is enabled, the codes of receivable data and the codes of receive data that is stored in the reception area of the buffer memory are as follows:
Receivable codes Codes stored in the reception area
Arbitrary data section
(including complete code section)
30
H
to 39
H
, 41
H
to 46
H
0
H
to 9
H
, A
H
to F
H
If data codes other than 30
H
to 39
H
and 41
H
to 46
H
are received for an arbitrary data section, an error occurs after ASCII-BIN conversion processing by the Q series C24.
(2) To perform ASCII-BIN conversion, the complete code after conversion should be used.
13 - 5 13 - 5
13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION)
MELSEC-Q
External device
Head data
(2) Reception based on the received data count
Two bytes of reception data is read to the PLC CPU as one-byte data.
0 1 2 3 4 5 A B C D E 9
Number of bytes after
ASCII-BIN conversion:
((6)/2=3) when word units are used,
(6) when byte units are used
30
H
31
H
32
H
33
H
34
H
35
H
41
H
42
H
43
H
44
H
45
H
39
H
Set to even byte
PLC CPU side
Reception data read request
PLC CPU
Completion device
Status display device at completion
X83
M0
M1
Reception data read request
INPUT
Store data received count
ON
ON
One scan
The diagram below is for when word units are used.
Abnormal completion
Normal completion
600
H
00
H
, 03
H
601
H
23
H
, 01
H
602
H
AB
H
, 45
H
603
H
E9
H
, CD
H
Buffer memory
3)
2)
D2
00
H
, 03
H
D10
23
H
, 01
H
D11
AB
H
, 45
H
D12
E9
H
, CD
H
Sequence program device memory
Sets CH1 to the reception channel
Sets the allowable number of receiving data to 6
Executes reception
Sets the normal completion flag
Sets the abnormal completion flag
POINT
When the receive transparent code designation is set to Disable and ASCII-BIN conversion is enabled, the codes of receivable data and the codes of receive data that is stored in the reception area of the buffer memory are as follows:
Arbitrary data section
Receivable codes
30
H
to 39
H
, 41
H
to 46
H
Codes stored in the reception area
0
H
to 9
H
, A
H
to F
H
If data codes other than 30
H
to 39
H
and 41
H
to 46
H
are received for an arbitrary data section, an error occurs after ASCII-BIN conversion by the Q series C24.
13 - 6 13 - 6
13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION)
MELSEC-Q
External device
PLC CPU side
Reception data read request
PLC CPU
Head data
Completion device M0
Status display device at completion
M1
Reception data read request
X83
(3) Example of reception using user frames
S
T
X
Q
02
H
51
H
00
H
0A
H
3B
H
30
H
31
H
32
H
46
H
35
H
41
H
42
H
43
H
44
H
45
H
46
H
39
H
03
H
DE
H
First frame
(corresponds to register number 3E8
H
)
Arbitrary data section
Last frame
(corresponds to register number 41B
H
)
1)
;
0 1 2 F 5 A B C D E F 9
E
T
X
INPUT
ON
ON
One scan
Abnormal completion
Normal completion
Number of receive data
Number of bytes after ASCII-BIN conversion of receive data excluding frames and additional codes:
(6)/2=3 When word units are used,
(6) When byte units are used.
The diagram below is for when word units are used
AD
AE
AF
H
H
H
2
3E8
H
H
3E9
H
B0
H
B1
H
B2
H
B3
H
B4
H
B5
H
120
H
121
H
25B
H
600
H
601
H
602
H
3EA
H
(No designation)
0
H
41B
H
(3rd)
(4th)
Last frame No. designation
(1st)
41B
H
(No designation)
0
H
(No designation)
0
H
(Designate)
(No designation)
1002
H
/ 0
H
(Convert)
1
H
00
2F
BC
H
H
H
1
H
, 03
, 01
, 5A
H
H
H
(2nd)
(3rd)
(4th)
Receive transparent code designation
ASCII-BIN conversion designation
Receive user frame ( th)
Number of data received
To D0
To D3 data
(arbitrary data section)
D10 to
D12
603
H
User frame enable/ disable designation
First frame No. designation
(1st)
(2nd)
F9
H
, DE
H
Buffer memory
Reads combination of received user frames
Sets CH1 to the reception channel
Sets the allowable number of receive data to 6
Executes reception
Sets the normal completion flag
Sets the abnormal completion flag
13 - 7 13 - 7
13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION)
MELSEC-Q
13.4.2 Example of data transmission
The following shows an example of data transmission:
(1) Example of arbitrary data transmission
External device side
PLC CPU side
3
Data transmission area
(arbitrary data section)
4 1 2 A B 5 6
33
H
34
H
31
H
32
H
41
H
42
H
35
H
36
H
Eight characters of data in the transmission area are sent in two characters per byte through
ASCII-BIN conversion.
Transmission instruction
X50
PLC CPU
Completion device
Status display device at completion
M0
M1
Transmission instruction
OUTPUT
ON
ON
One scan
Abnormal completion
Normal completion
121
H
400
H
401
H
402
H
(Convert)
1
H
ASCII-BIN conversion designation
00
H
, 02
H
(1234
H
)
12
H
, 34
H
(56AB
H
)
56
H
, AB
H
Buffer memory
Transmission area
(Designation of no. of data sent)
(Transmission data)
0004
H
in byte units
Sets the arbitrary transmission data for D11 to D12
Sets CH1 to the transmission channel
Sets the number of data sent to 2
Execute the transmission
Sets normal completion flag
Sets abnormal completion flag
13 - 8 13 - 8
13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION)
MELSEC-Q
(2) Example of transmission by user frame
External device side
PLC CPU side
Register No. of corresponding user frame
S
T
X
Q
02
H
51
H
0A
H
C24
00
H
; T O T A L
;
3B
H
54
H
4F
H
54
H
41
H
4C
H
3B
H
(Total number)
(012D
2D
H
H
)
01
H
Data in transmission area
(arbitrary data section)
E
T
X
3 4 1 2 A B 5 6
33
H
34
H
31
H
32
H
41
H
42
H
35
H
36
H
03
H
A7
H
Corresponds to 3F2
H
(for first designated frame)
Corresponds to 3F3
H
(for second designated frame)
Corresponds to 8001
H
(for third designated frame)
8000
H
(for fourth designated frame)
Corresponds to 41B
H
(for fifth designated frame)
Transmission instruction
X50
PLC CPU
Completion device
Status display device at completion
M0
M1
Transmission instruction
OUTPUT
ON
ON
One scan
Abnormal completion
Normal completion
Eight characters of data in the transmission area are sent in two characters per byte through
ASCII-BIN conversion.
B6
H
B7
H
B8
H
(Not sent)(Sending)
0
H
/Other than 0
H
(Do not send)
0
H
(1st)
1
H
User frame No. being transmitted
CR/LF output designation
Output head pointer designation
B9
H
5
H
Output count designation
BA
H
3F2
H
Output frame no. designation (1st)
BB
H
3F3
H
(2nd)
BC
H
C001
H
(3rd)
BD
H
8000
H
(4th)
BE
H
441B
H
(5th)
BF
H
(6th)
121
H
0
H
(Convert)
1
H
400
401
402
H
H
H
00
H
, 02
(1234
H
)
H
12
H
, 34
H
(56AB
H
)
56
H
, AB
H
Buffer memory
ASCII-BIN conversion designation
Transmission area
(Designation of no. of data sent)
(Transmission data)
0004
H
in byte units
Sets CH1 to the transmission channel
Sets the number of data sent to 2
Sets the arbitrary transmission data for D11 to D12
Sets the arbitrary transmission data for transmission buffer
Executes user frame transmission
Sets normal completion flag
Sets abnormal completion flag
13 - 9 13 - 9
13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION)
MELSEC-Q
13.5 Performing ASCII-BIN Conversion for Data Communicated Via the Bidirectional
Protocol
This section explains the ASCII-BIN conversion of data to be communicated using the bidirectional protocol.
(1) The following shows the range of transmission/reception data for which ASCII-BIN conversion can be performed.
Applicable data range at transmission/reception
Message at data transmission/ reception
E
N
Q
(Arbitrary data section)
Data length Data section
Sum check code
Response message
Applicable data range at transmission/reception
A
C
K
N
A
K
Error code
When sending or receiving data, the Q series C24 processes data as follows:
1) Range of ASCII-BIN conversion
The Q series C24 performs the ASCII-BIN conversion for any data section
(data length and data section) and error code in a message.
2) Conversion of data length
• At transmission
The Q series C24 converts a transmission data count to 4-digit ASCII code data (hexadecimal), then sends it beginning with the lowest byte (L).
• At reception
The Q series C24 converts a received data length (4-digit ASCII code data
(hexadecimal)) to 2-byte binary code data and stores it in the reception data count storage area.
3) Conversion of data section
• At transmission
The Q series C24 converts transmission data for one address to 4-digit ASCII code data (hexadecimal), then sends it beginning with the lowest byte (L).
• At reception
The Q series C24 converts each two characters of a received data section
(2-digit ASCII code data (hexadecimal)) to 1-byte binary code data and stores it in the reception data storage area.
4) Conversion of error code
• At transmission
The Q series C24 converts an error code for a detected error to 4-digit ASCII code data (hexadecimal), then sends it beginning with the lowest byte (L).
(For 3412
H
, it is converted to "3412" and sent beginning with "12".)
• At reception
The Q series C24 converts the first 2 digits of a received error code (4-digit
ASCII code data (hexadecimal)) to 2-byte binary code data as the lower byte, and stores it in the transmission result storage area.
(For "1234" is received, it is converted to 3412
H
and stored.)
13 - 10 13 - 10
13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION)
MELSEC-Q
5) Treatment of sum check code
The data length and the data section after ASCII-BIN conversion are added together and the lowest two bytes of the resulting binary code data are treated as a sum check code.
• At transmission
The Q series C24 calculates a sum check code using the data length and data section after ASCII-BIN conversion, then adds it to the transmission message.
• At reception
The Q series C24 calculates a sum check code using the received data length and data section prior to ASCII-BIN conversion, then checks the received head of the sum-check code using the code as a lower byte.
(When word units are used) Message
1
E
N
Q
Data length
(0002)
Data section
Sum check code
L
0 2
05
H
30
H
32
H
H
0 0 1 2
30
H
30
H
3
31
H
32
H
33
H
4 5 A
34
H
35
H
41
H
L H
B C
42
H
43
H
87
H
02
H
Buffer memory
(H) (L)
00
H
, 02
H
34
H
, 12
H
BC
H
, 5A
H
Transmission data count/Receive data count
Transmission data/ receive data
ASCII-BIN conversion
1 Calculation of sum check code
30
H
+ 32
H
+ 30
H
+ 30
H
+ 31
H
+ 32
H
+ 33
H
+ 34
H
+ 35
H
+ 41
H
+ 42
H
+ 43
H
= 0287
(H) (L)
H
(2) Section 12.5 explains how Q series C24 processes data communicated when
ASCII-BIN conversion and transparent code designation are both enabled.
(Example)
External device
Head data
Arbitrary data section
(Data communication)
E
N
Q
Data length
05
H
L
0 2
30
H
32
H
H
0 0
30
H
30
H
Data section
1 2 0 2
31
H
32
H
30
H
32
H
3 A
33
H
41
H
Sum check
L code
H
B C
42
H
43
H
80
H
02
H
N
A
K
Starting data
Error code
Send
Receive
(Communication of response massage)
Send
Or
A
C
K
15
H
L
3 4
33
H
34
H
H
1 2
31
H
32
H
06
H
Receive
Q series C24
Buffer memory (transmission area/reception area)
(H) (L)
00
(0002
H
,
(0212
H
02
H
H
)
)
02
H
12
H
(BC3A
H
)
BC
H
,
,
3A
H
Trancmission data count/Receive data count
Transmission data/ receive data
At normal completion : 0000
H
At abnormal completion : 1234
H
Transmission result/ reception result
13 - 11 13 - 11
13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION)
MELSEC-Q
13.6 Example of Data Communication Using the Bidirectional Protocol
This section shows examples of data communication using the bidirectional protocol when the following settings and registrations are made.
(1) Settings via GX Developer
Perform the following settings on the "Intelligent function module switch setting" screen.
(See Section 4.5 of the User's Manual (Basic).
Remarks
Switch 1
Switch 2
Switch 3
Switch 4
Setting item
CH1 Transmission setting
CH1 Communication rate setting
CH1 Communication protocol setting
CH2 Transmission setting
CH2 Communication rate setting
CH2 Communication protocol setting
Setting value
Set according to the external device
0007
H
0000
H
0000
H
Not used
—
Bidirectional protocol
Switch 5 Station No. setting 0000
H
Station number of Q series C24
(2) Settings via GX Configurator-SC
Register the following items on the "Transmission control and others system setting" screen.
(See Sections 8.4.5 of the User's Manual (Basic).)
For items other than those noted below, the default values are used.
Setting item
Send transparent code designation
Receive transparent code designation
ASCII-BIN conversion designation
Setting value
1004
H
1004
H
Convert
13 - 12 13 - 12
13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION)
MELSEC-Q
13.6.1 Example of data reception
External device side
PLC CPU side
The following shows an example of data reception when ASCII-BIN conversion is enabled.
• When the receive transparent code designation is set to Enable and ASCII-BIN conversion is set to Enable
Additional code: 10
H
(DLE), transparent code: 04
H
(E0T)
E
N
Q
Data length
(0004
H
)
Data section
Sum check code
05
H
0 4 0 0
30
H
L
34
H
30
H
H
30
H
1
31
H
2
32
H
3 4 5
33
H
34
H
35
H
A B
41
H
42
H
C
43
H
D
44
H
E F
45
H
46
H
0
30
H
0
30
H
D
44
H
0 A
30
H
41
H
L H
6D
H
04
H
Set to even byte except for additional code
A
C
K
1)
06
H
Two bytes of reception data is read to the PLC CPU as one-byte data (excluding additional code).
Reception data read request
PLC CPU
Completion device
Status display device at completion
X83
M0
M1
Reception data read request
BIDIN
ON
ON
Data length (Number of data received) : Excluding additional code
Number of bytes after ASCII-BIN conversion: ( (8)/2=4) when word units are used
(8) when byte units are used
One scan
Abnormal completion
Normal completion
Data length
Data section
This diagram is for when word units are used.
600
H
00
H
, 04
H
601
H
34
H
, 12
H
602
H
BC
H
, 5A
H
603
H
F0
H
, DE
H
604
H
0A
H
, 0D
H
Buffer memory
3)
2)
D3
00
H
, 04
H
D10
34
H
, 12
H
D11
BC
H
, 5A
H
D12
F0
H
, DE
H
D13
0A
H
, 0D
H
Sequence program device memory
Sets CH1 to the reception channel
Sets the allowable number of receive data to 6
Executes reception
Sets the normal completion flag
Sets the abnormal completion flag
POINT
When the receive transparent code designation is set to Enable and ASCII-BIN conversion is set to Enable, the codes of receivable arbitrary data sections and the codes of receive data that is stored in the reception area of the buffer memory are as follows:
Receivable codes Codes stored in the reception area
Sections for which the reception transparent code designation is enabled
Additional code
Transparent code
Data length, data section
01
H
to FF
H
30
H
to 39
H
41
H
to 46
H
(Delete)
0
H
to 9
H
A
H
to F
H
13 - 13 13 - 13
13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION)
MELSEC-Q
13.6.2 Example of data transmission
The following shows an example of data transmission when ASCII-BIN conversion is enabled.
• When the send transparent code designation is set to Enable and ASCII-BIN conversion is set to Enable
Additional code: 10
H
(DLE), transparent code: 04
H
(E0T)
A
C
K
External device side
06
H
PLC CPU side
E
N
Q
Data length
(0004)
Data section
Sum check code
05
H
0 4 0 0
30
H
L
34
H
30
H
H
30
H
1
31
H
2
32
H
3 4 5
33
H
34
H
35
H
A B
41
H
42
H
C
43
H
D
44
H
E F
45
H
46
H
0
30
H
0
30
H
D
44
H
0 A
30
H
41
H
L H
6D
H
04
H
Transmission instruction
X50
PLC CPU
Completion device
Status display device at completion
M0
M1
Transmission instruction
BIDOUT
ON
ON
Abnormal completion
Normal completion
Data length (Number of data received) : Excluding additional code
Number of bytes after ASCII-BIN conversion: ( (8)/2=4) when word units are used
(8) when byte units are used
This diagram is for when word units are used.
One scan
Transmission data
D3
00
H
, 04
H
400
H
D10
34
H
, 12
H
401
H
D11
BC
H
, 5A
H
D12
F0
H
, DE
H
D13
0A
H
, 0D
H
Sequence program device memory
1) 2)
402
H
403
404
H
H
00
34
BC
F0
H
H
H
H
, 04
, 12
, 5A
, DE
H
H
H
H
0A
H
, 0D
H
Buffer memory
Sets CH1 to the transmission channel
Sets the number of data sent to 4
Sets the arbitrary transmission data to D10 to D13
Executes transmission
Sets normal completion flag
Sets abnormal completion flag
POINT
Data for one address (one word) in the buffer memory's transmission area is converted into four-byte ASCII code data ("0" to "9" and "A" to "F"), and is then transmitted.
13 - 14 13 - 14
14 DATA COMMUNICATIONS USING EXTERNAL DEVICE AND PLC CPU
M : N CONFIGURATION
MELSEC-Q
14 DATA COMMUNICATIONS USING EXTERNAL DEVICE AND PLC CPU
M : N CONFIGURATION
Always read this chapter when communicating data by using a multidrop link to connect the external devices and PLC CPU in an m: n system configuration.
You do not have to read this chapter when using a system configuration other than m: n to communicate data.
This section describes the case when data is communicated between external devices and the PLC CPU by connecting multiple external devices (m stations) and multiple Q series C24 (n stations) over a multidrop link. (The total number of m and n is up to 32 stations.)
With this m : n multidrop link, only MC protocol data communications by command transmission from the external devices can be performed.
14.1 Data Communications Precautions
(1) When communicating data by using an m: n system configuration, multiple external devices cannot communicate data with the PLC CPU at the same time.
Interlock the external devices so that the external device can communicate with the PLC CPU in a 1:1 configuration.
See Sections 14.2 and 14.3 for the items to be agreed upon and the interlock method to interlock the external devices.
(2) Communicate data between external devices and the PLC CPU by the following methods only.
• Full-duplex data communications (m : n data communications is impossible with half-duplex data communications)
• Data communications by command transmission from external device using an
MC protocol excluding the format 3 and format 5 control procedure (Data communications using the format 3 and format 5 control program and data transmission from sequence program using the on-demand function cannot be performed.)
(3) The data transmitted by one external device is received by all the other external devices, including the external device that transmitted the data. The send data from a PLC CPU is also received by all the external devices.
Therefore, it may be necessary for devices that received data not addressed to them (judged by station No. in the message) to ignore the receive data.
At the PLC CPU, Q series C24 also ignores the receive data other than that addressed to it.
(4) Connect to multiple external devices and connect the terminating resistor as described in Section 4.4.2 of User’s Manual (Basic).
14
14 - 1 14 - 1
14
14 DATA COMMUNICATIONS USING EXTERNAL DEVICE AND PLC CPU
M : N CONFIGURATION
MELSEC-Q
(5) When communicating data by using an m: n system configuration, designate the following station number at the [Station No.] and [Local station No.] items in the command message to be transmitted from an external device.
1) When accessing the PLC CPU
Station
No.
Local station
No.
Communications using QnA compatible 2C/3C/4C
Communications using A compatible 1C frame
Station No. of Q series C24 to be passed through (Station No. described in
"Contents of the data designation items" of each frame in the reference manual.
Station No. of access source external device
1
Designation unnecessary
(No [Local station No.] item)
2) When accessing another external device (interlock communications)
Communications using QnA compatible 2C/3C/4C
Communications using A compatible 1C frame
Station
No.
Local station
No.
Station No. of access destination external device
Station No. of access source external device
1
1
Designation unnecessary
(No [Local station No.] item)
1 A station No. with in the [0] to [31] (00
H
to 1F
H
) range not set in Q series
C24 at the PLC CPU is used as the external device No. in the [Station
No.] and [Local station No.] items in the message.
Select and designate the No. of each external device.
The designation method is described in "Contents of the data designation items" of each frame in the reference manual.
• Station No. ................ Designates the No. of the transmit destination external device.
• Local station No. ........ Designates the No. of the transmit source external device. (Does not have to be designated when A compatible 1C frame is used.)
14 - 2 14 - 2
14 DATA COMMUNICATIONS USING EXTERNAL DEVICE AND PLC CPU
M : N CONFIGURATION
MELSEC-Q
14.2 External Devices Interlock Conditions
When using a multidrop line to communicate data between external devices and the
PLC CPU in an m: n configuration, the external devices must be interlocked so that multiple external devices cannot communicate data with the PLC CPU at the same time.
This section describes the conditions for interlocking the external devices so that all of the external devices can communicate data with the PLC CPU.
(Conditions for priority use (obtaining line ownership) of the line from the start to the end of data communications with the PLC CPU.)
14.2.1 Maximum communications time per external device station
External device 1
External device 2 to
External device 5
This condition determines the maximum time each external device can communicate with the PLC CPU after obtaining line ownership. (Time in the illustration below.)
This is selected to prevent loss of data communications between other external devices and the PLC CPU by shutdown of the external device that obtained line ownership.
(Example)
Time
Start of data communications
Indicates the range within which the target device cannot obtain line ownership.
Indicates the range within which the target device can obtain line ownership and can have data communication with the PLC CPU.
POINT
(1) Make the maximum data communications time per external device station the maximum time of the external device that requires the most time to communicate data with the PLC CPU.
(2) After system starting, complete data communications from the external device that obtained line ownership and the PLC CPU within the maximum communications time.
(If data communications cannot be completed within this time, initialize the Q series C24 transmission sequence by transmitting the EOT/CL code to the objective PLC CPU within the maximum communications time. (See "Contents of data designation item" of each frame in the reference manual.))
(3) While an external device and the PLC CPU are communicating data, have the other external devices check the time so that they do not transmit data during this time.
14 - 3 14 - 3
14 DATA COMMUNICATIONS USING EXTERNAL DEVICE AND PLC CPU
M : N CONFIGURATION
MELSEC-Q
14.2.2 Message structure when communicating data between external devices
The message structure when communicating data between external devices is determined by any of the following.
This condition is determined to interlock the external devices so that they can exchange data with the PLC CPU in a 1:1 configuration.
(1) When making the message structure the same as that of each control procedure format frame
1) Use a number within the [0] to [31] (00
H
to 1F
H
) range not set in Q series C24 of the PLC CPU as the external device No. in the [Station No.] and [Local station No.] items in the message.
2) Select and designate the external device numbers.
The designation method is described in "Contents of data designation item" of each frame in the reference manual.
• Station No. ..................... Designates the number of the transmission destination external device.
• Local station No. ............. Designates the number of the transmission source external device. (Does not have to be designated when A compatible frame 1C is used.)
(Example) When m : n configuration is 5:27
The values in ( ) are the external device and Q series C24 station numbers. (decimal : hexadecimal).
(27: 1B
H
)
External device
-1-
(28: 1C
H
)
External device
-2-
(31: 1F
H
)
External device
-5-
(0: 00
H
)
CPU C24
(1: 01
H
)
CPU C24
(2: 02
H
)
CPU C24
(3: 03
H
)
CPU C24
(26: 1A
H
)
CPU C24
C24: Q series C24, QC24(N), UC24
(QnA Compatible 3C frame format 1)
E
N
Q ion No.
05
H
H
F
L
9
H
1
L
C
H
0
L
0
46
H
39
H
31
H
43
H
30
H
30
H
H
F
46
H
L
F
46
H
H
1
L
B
31
H
42
H
14 - 4 14 - 4
14 DATA COMMUNICATIONS USING EXTERNAL DEVICE AND PLC CPU
M : N CONFIGURATION
MELSEC-Q
(2) When message structure different from that of control procedure format frames can be used
1) Change the head data of each message to other arbitrary data.
• When selecting ASCII code format 1, format 2, or format 4, change ENQ
(05
H
).
2) Arbitrarily list the data following the head data of each message according to the user specifications.
(Example)
Head data
Arbitrary contents
External device 1
(station No. 1B
H
)
(;)
3B
H
(1C)
31
H
43
H
(1B)
31
H
42
H
(ZZ)
5A
H
5A
H
(2)
32
H
(CD)
43
H
44
H
External device 2
(station No. 1C
H
)
(:)
3A
H
(1C) (1B)
Arbitrary contents
Head data
POINT
Correspond the message structure for general reporting to all the other external devices except PLC CPU stations using unused station numbers or a message structure different from the Q series C24 control procedure format.
14 - 5 14 - 5
14 DATA COMMUNICATIONS USING EXTERNAL DEVICE AND PLC CPU
M : N CONFIGURATION
MELSEC-Q
14.3 Examples of Procedure for Data Communications with the PLC CPU
The following uses examples to describe the procedure when communicating data with a PLC CPU by interlocking the external devices.
14.3.1 Sequential data communications between external devices and the PLC CPU
The external devices sequentially obtain the line usage right and communicate data with the PLC CPU based on their station No..
(Example)
Time
Station No. 1B
H external device
Transmission to transfer the line usage right
Response
Station No. 1C
H external device
Data communications with the PLC CPU
Station No. (m-1) external device
The following uses an example to describe the procedure when external devices communicate data with the PLC CPU.
: External device that obtained the line usage right
External device
(Station No.:1B
H
)
1)
When communicating data with the station
No. 1
H
PLC CPU
2)-a)
External device
(Station No.:1C
H
)
3)
(Station No.:0
H
)
CPU C24
(Station No.:1
H
)
CPU C24
(Station No.:2
H
)
CPU C24
External device
(Station No.:1D
H
)
3)
External device
(Station No.:1E
H
)
3)
(Station No.:15
H
)
CPU C24
C24: Q series C24, QC24 (N), UC24
1) When the system starts, the external device with the lowest station No. (1B
H
) is given the line usage right.
2) The external device that obtained the line usage right, a) When communicating data with the PLC CPU, begins processing from 4) after communicating data with the PLC CPU within the maximum data communications time from among all the external devices.
b) When not communicating data with the PLC CPU, immediately begins processing from 4).
3) The external devices that have not obtained the line usage right check the line usage time of the external device that obtained the line usage right and ignore the receive data not addressed to their own station.
When the line usage time exceeds the maximum data communications time, each external device performs the processing of 7).
14 - 6 14 - 6
14 DATA COMMUNICATIONS USING EXTERNAL DEVICE AND PLC CPU
M : N CONFIGURATION
MELSEC-Q
: External device that obtained the line usage right
External device
(Station No.:1B
H
)
(Station No.:0
CPU
H
)
C24
4)
(Before 5)) (Before 5))
(Station No.:1
H
)
CPU
C24
External device
(Station No.:1C
H
)
5)
External device
(Station No.:1D
H
)
6)
Data communications with arbitary PLC CPU
(Station No.:2
H
)
CPU
C24
External device
(Station No.:1E
(Station No.:15
H
)
CPU C24
H
)
C24: Q series C24, QC24 (N), UC24
4) External devices that communicated data with the PLC CPU, or external devices that do not have to communicate data with the PLC CPU, transmit the data for transferring the line usage right to the external device of the next station No..
A message structure example is shown in 5.
When a response message (see 5)) is not received from the next external device to which the line usage right was passed, data transmission for transferring the line usage right to the external device of the next station No. is repeated until the line usage right is accepted.
5) The external device that accepts the line usage right transmits a response message to the external device that passed it the line usage right.
(Example)
Message of
4) above
1
External device that transfers line usage right (1B
H
) eck code
(;)
3B
H
(1C)
31
H
43
H
(1B)
31
H
42
H
(ZZ)
5A
H
5A
H
(2)
32
H
(CD)
43
H
44
H
1 Command "ZZ" is command for description purposes.
The user should select the command that transfers/accepts the line usage right.
External device passed line usage right (1C
H
)
(:)
3A
H
(1C)
31
H
43
H
(1B)
31
H
42
H
Message of 5)
6) The external device that accepted the line usage right by transmitting a response message performs processing beginning from 2).
14 - 7 14 - 7
14 DATA COMMUNICATIONS USING EXTERNAL DEVICE AND PLC CPU
M : N CONFIGURATION
MELSEC-Q
7) When line usage time of the external device that currently has the line usage right exceeds the maximum data communications time.
a) The external device of the next station No. transmits all external devices general report data and obtains the line usage right and performs step 2).
(Example)
1 2
External device that obtains the line usage right
(1C
H
)
(;)
3B
H
(1F)
31
H
46
H
(1C)
31
H
43
H
(ZZ)
5A
H
5A
H
(0)
30
H
(0A)
30
H
41
H
1
2
Station No. for all external devices general report.
See 1 of 5) above.
b) The other external devices check if all external devices general report data was received. If the data was received, the external device performs step 3).
If the data was not received, the next external device transmits all external devices general report data and obtains the line usage right and performs step
2). The other external devices perform b) of this item.
14 - 8 14 - 8
14 DATA COMMUNICATIONS USING EXTERNAL DEVICE AND PLC CPU
M : N CONFIGURATION
MELSEC-Q
14.3.2 Data communications between PLC CPU and external devices by designating a master station and slave stations
Master station external device
Communications request
Slave station external device 1
Slave station external device 2
One of the external devices is made the master station and the other external devices communicate data with the PLC CPU after obtaining permission from the master station.
(Example)
TIme
Permission granted response
Communications complete report
Response
Communications request
Permission granted response
General report to start and end data communications between master station and PLC
CPU
Communications request
Permission granted response
Start End
Communications complete report
Response
Data communications with PLC CPU
Slave station external device m-1
Data communications with PLC CPU
The following uses an example to describe the procedure when external devices communicate data with the PLC CPU.
In this example, after the start of data communications between external devices and the PLC CPU, the external devices perform a maximum data communications time time-out check. Slave station external devices that are not communicating data with the PLC CPU check if the external device that completed data communications with the PLC CPU transmitted a communications complete report.
In the following descriptions, the external device with the lowest station No. (1B
H
) is assumed to be the master station and the other external devices are assumed to be slave stations.
: External device that obtained the line usage right
Master station (Before 2)) (after 2))
External device
(Station No.:1B
H
)
External device
(Station No.:1C
H
)
External device
(Station No.:1D
H
)
External device
(Station No.:1E
H
)
2)
(Station No.:0
H
)
CPU
C24
(Station No.:1
H
)
CPU
C24
1)
(Station No.:2
H
)
CPU
C24
(Station No.:15
H
)
CPU
C24
C24: Q series C24, QC24 (N), UC24
14 - 9 14 - 9
14 DATA COMMUNICATIONS USING EXTERNAL DEVICE AND PLC CPU
M : N CONFIGURATION
MELSEC-Q
1) A slave station that wants to communicate data with the PLC CPU sends a communications request to the master station to obtain the line usage right.
A message structure example is shown in 2).
2) The master station transmits a permission granted response to the slave station that issued the communications request.
Massage of 1)
1
External device of slave station that wants to obtain the line usage right
(1C
H
) ission sou
(;)
3B
H
(1B)
31
H
42
H
(1C)
31
H
43
H
(ZX)
5A
H
58
H
(2)
32
H
(CB)
43
H
42
H
1 Command "ZX" is a communications request command for description purpose.
The user should select the command that requests communications.
Master station external device
(1B
H
) ission sou
(:)
3A
H
(1B)
31
H
42
H
(1C)
31
H
43
H
Massage of 2)
(Y)
59
H
Mater station (Before 6))
4)
External device
(Station No.:1B
H
)
: External device that obtained the line usage right
(After 6))
External device
(Station No.:1C
H
)
External device
(Station No.:1D
H
)
4)
External device
(Station No.:1E
H
)
4)
6)
(Station No.:0
H
)
CPU C24
(Station No.:1
H
)
CPU C24
5) 3)
(Station No.:2
H
)
CPU C24
(Station No.:15
H
)
CPU C24
C24: Q series C24, QC24 (N), UC24
3) After communicating data with the PLC CPU within the maximum data communications time from among the external devices, the slave station that received the "permission granted" response goes to step 5).
4) The master station that transmitted the "permission granted" response and the slave stations that did not obtain line usage right check the line usage time of the slave station that obtained the line usage right and ignore receive data other than that addressed to their local station.
If the line usage time exceeds the maximum communications time, the external devices perform the processing of step 7).
5) After data communications are complete, the slave station that exchanged data with the PLC CPU transmits a communications complete report to the master station. A message structure example is shown in 6).
Slave stations that do not communicate data with the PLC CPU check if a communications complete report was transmitted and do not communicate data with the master station during that time.
14 - 10 14 - 10
14 DATA COMMUNICATIONS USING EXTERNAL DEVICE AND PLC CPU
M : N CONFIGURATION
MELSEC-Q
6) The master station that received the communications complete report transmits a response to the slave station that transmitted the communications complete report.
(Example)
External device of slave station to perform the communications complete report
(1C
H
)
Massage of 5) ission sou
1
(;)
3B
H
(1B)
31
H
42
H
(1C)
31
H
43
H
(ZY)
5A
H
59
H
(2)
32
H
(CC)
43
H
43
H
1 Command "ZY" is a communications complete report command for description purpose. The user should select the communications complete report command.
Master station external device
(1B
H
) ission sou
(:) (1B) (1C)
3A
H
31
H
42
H
31
H
43
H
Massage of 6)
7) After completion of 6) above, or when the line usage time of the slave station that obtained the line usage right exceeds the maximum data communications time: a) The master station waits for a communications request from a slave station.
When the master station receives a communication request, it performs processing from step 2).
b) The slave stations do not communicate data with the master station until data communications with the PLC CPU is necessary.
When data communications with the PLC CPU becomes necessary, that slave station performs processing from step 1).
8) When the master station itself wants to exchange data with the PLC CPU and a slave stations does not have the line usage right, it transmits all external devices except PLC CPU a general report data and obtains the line usage right before communicating data with the PLC CPU.
After data communications with the PLC CPU is complete, the master station transmits all external devices general report data to inform the slave stations that data communications with the PLC CPU is complete.
During this time, the slave stations do not communicate data with the master station until master station data communications is complete.
(Example)
1 2
External device of master station that obtained the line usage right (1B
H
)
(;)
3B
H
(1F)
31
H
46
H
31
(1B)
H
42
H
5A
(ZX)
H
58
H
(0)
30
H
30
(07)
H
37
H
1 2
External device of master station that transmits communications complete report
(1B
H
)
(;)
3B
H
(1F)
31
H
46
H
(1B)
31
H
42
H
(ZY)
5A
H
59
H
(0)
30
H
(08)
30
H
38
H
1
2
Station No. for all external devices general report.
Commands "ZX" and "ZY" are commands for description purposes.
The user should select the command when the master station communicates data with slave stations.
14 - 11 14 - 11
15 SWITCHING THE MODE AFTER STARTING
MELSEC-Q
15
15 SWITCHING THE MODE AFTER STARTING
This function forcefully switches the current communication protocol and transmission specifications of the designated interface from an external device and the PLC CPU after the Q series C24 starts.
When the Q series C24 starts, it begins operation with the setting values of the GX
Developer switch setting.
POINT
The mode switching function is used to change the communication protocol of the specified interface and transmission specifications and continue data communications without restarting the QCPU.
(1) Mode switching from external device
(a) If the communication protocol of the interface connecting the external device is MC protocol, mode switching can be performed.
(b) The communication protocol can be changed from the MC protocol as shown below.
(Format switching)
MC protocol
(Formats 1 to 5)
Non procedure protocol Bidirectional protocol
GX Developer connection
(c) The transmission specifications set by the GX Developer switch setting can be changed.
(2) Mode switching from PLC CPU
(a) Regardless of the current communication protocol of the connected interface, the external device can perform mode switching from the PLC program.
(b) The communication protocol can be changed from the PLC program as shown below.
(Format switching)
MC protocol
(Formats 1 to 5)
Non procedure protocol Bidirectional protocol
GX Developer connection
(c) The transmission specifications set by the GX Developer switch setting can be changed.
POINT
When using the mode switching function, set the setting change of the communication setting to "enable" in the GX Developer switch setting.
(See the User’s Manual (Basic) Section 4.5.2.)
15 - 1 15 - 1
15 SWITCHING THE MODE AFTER STARTING
MELSEC-Q
15.1 Mode Switching Operation and Contents that can be Changed
This section describes the set contents that can be changed with mode switching and the operation of Q series C24 after mode switching.
15.1.1 Settings that can be changed with mode switching
The following describes the settings that can be changed with mode switching.
(1) Switching the communication protocol
(a) The communication protocol setting of each interface can be switched.
(b) The communication protocol after the mode switching is specified by the switching mode No. designation area of the buffer memory (address: 90
H
,
130
H
).
(2) Changing the transmission specifications
(a) The transmission setting of each interface can be switched.
(b) The transmission setting after the mode switching is specified by the transmission specification after switching designation area of the buffer memory (address: 91
H
, 131
H
).
POINT
Mode switching allows the user to change the settings corresponding to communication protocol and transmission switch settings of the GX developer.
15.1.2 Operation for mode switching
The following describes the Q series C24 operation for mode switching.
(1) Processing currently executing
(a) If there is a mode switching request, mode switching immediately starts.
(b) If one of the following processings was being performed when a mode switching request was issued, that processing is terminated.
1) Data communications using an MC protocol
• Command message receive processing and response message or ondemand data transmission processing are all terminated.
• The transmission complete end signal for an on-demand data transmission request is not turned on.
15
15 - 2 15 - 2
15 SWITCHING THE MODE AFTER STARTING
MELSEC-Q
2) Data communications using non procedure protocol and bidirectional protocol
• Data and response message transmit and receive processing are all terminated.
• All the input signals from the PLC CPU related to transmit and receive processing are turned off.
• If the receive data from the external device was being stored to the Q series C24, the receive data up to that point is ignored and the data is processed with the current receive data count as [0].
(2) Modification of buffer memory stored value
(a) Special applications area (addresses: 252
H
to 253
H
, 262
H
to 263
H
)
The communication protocol status and transmission specifications after mode switching is complete are stored.
The values stored to areas other than the above are not changed. The contents before switching are preserved.
(b) User free area (addresses: 400
H
to 1AFF
H
, 2600
H
to 3FFF
H
)
The stored values are not changed. The contents before mode switching are preserved.
15.2 Mode Switching Precautions
(1) Set-up between the external device and the PLC CPU
Make the following setting for the external device and the PLC CPU so that mode switching is not performed during data communications.
(a) Which side is to switch the mode, the PLC CPU or external device
(b) Timing for each mode switching pattern
(For mode switching patterns, see Chapter 15, Section (1)(2).)
(c) Interlocking of all connected devices in the case of mode switching
1) Method and message structure when all the connected stations are informed of the mode switching execution
2) Method and message structure when all the connected stations are informed of the mode switching completion
3) Device No. and meaning of the value when a PLC CPU word device is used
15 - 3 15 - 3
15 SWITCHING THE MODE AFTER STARTING
MELSEC-Q
(2) Mode switching from external device
(a) Once the mode has been changed to a mode other than MC protocol
(Formats 1 to 5), it cannot be changed from the external device.
In this case, change the mode on the PLC CPU.
(b) Only the Q series C24 (including multidrop link stations) connected to an external device is available for mode switching from the external device
(See the Reference Manual, Section 3.13.)
It is not available for other Q series C24 stations connected over a network system.
POINT
It is recommended to switch the mode on the PLC CPU side.
(3) Data communications after mode switching
The Q series C24 requires approximately 400 ms as processing time of mode switching only.
While the mode switching is being executed, the setting values cannot be stored into the buffer memory special applications area and data cannot be transmitted between the Q series C24 and the external device.
Approx. 400 ms
Mode switching processing
Mode switching signal
X6/XD
(4) Linked operation mode switching
Do not switch the mode when two interfaces of the Q series C24 are in linked operation.
Also, do not switch the mode for linked operation.
15 - 4 15 - 4
15 SWITCHING THE MODE AFTER STARTING
MELSEC-Q
15.3 I/O Signals for Handshake with PLC CPU and Buffer Memory
Mode switching
This section describes the I/O signals for handshake and the buffer memories used when mode switching is performed.
(1) I/O signals for handshake with PLC CPU
I/O signal
CH1 CH2
X6
Signal name
XD Mode switching in progress
Device turned ON/OFF
CPU C24
Y2 Y9 Mode switching request
Timing
(Switching)
Complete
REMARK
The following signals can also be used as I/O signals, in addition to the above.
See Section 3.8 of User’s Manual (Basic) for the PLC CPU I/O signals.
• Q series C24 ready signal (X1E)
...... Turned ON when the Q series C24 can be accessed from the PLC CPU
• Watchdog timer error signal (X1F) ... Turned ON when the Q series C24 does not operate normally
• CH1 ERR. signal (XE) ...................... Turned ON when the CH1 ERR. occurred
• CH2 ERR. signal (XF) ...................... Turned ON when the CH2 ERR. occurred
(2) Buffer memory
Address
(Decimal (hexadecimal))
CH1 CH2
Name Setting value/Stored value
144 (90
145 (91
H
H
)
) 304 (130
H
)
305 (131
H
)
515 (203
H
)
For specifying mode switching
For confirming mode switching and switch setting
Switching mode No. designation
(See (a).)
0001
H
: MC protocol (Format 1) to
0007
H
: Bidirectional protocol
00FF
H
: GX Developer connection
Transmission specification setting after switching
(See (b).)
0000
8000
H
H
: Matched to the settings at the GX Developer
to 8FFF
H
: Matched to the settings of this area
Switch setting error, mode switching error condition
0 : Normal
Other than 0: Switch setting error, mode switching error
(See the User’s Manual (Basic) Section 10.1.5)
(a) Switching mode No. designation area (addresses: 90
H
, 130
H
)
Write the desired mode No. (0001
H
to 0007
H
, 00FF
H
).
b15 to b0
Buffer memory address 90
H
/130
H
(Default 0000
H
)
0001
H
: MC protocol (Format 1)
0002
H
: MC protocol (Format 2)
0003
H
: MC protocol (Format 3)
0004
H
: MC protocol (Format 4)
0005
H
: MC protocol (Format 5)
0006
H
: Non procedure protocol
0007
H
: Bidirectional protocol
00FF
H
: GX Developer connection 1
1 The communication protocol is specified as "00
H
" when the GX Developer connection mode is set using the GX Developer switch setting. (See the User’s Manual (Basic) Section 4.5.2.)
15 - 5 15 - 5
15 SWITCHING THE MODE AFTER STARTING
MELSEC-Q
(b) Switching transmission specifications designation area (address: 91
H
, 131
H
)
1) Designates the transmission specifications after mode switching.
2) When the transmission specifications are returned to the contents set in
GX Developer, [0000
H
] is written to this area.
3) When setting arbitrary transmission specifications (other that the contents set in GX Developer), the value corresponding to ON/OFF of the relevant bit in the illustration shown below is written.
Relevant bit 1 (ON)/0 (OFF) is designated the same as transmission setting of GX Developer (See Section 4.5.2 of User’s Manual (Basic)).
b15 b14 to b8
1 b7 b6 b5 b4 b3 b2 b1 b0
00
H
to F
H
1/0 1/0 1/0 1/0 1/0 1/0 1/0 1/0
1 00
H
to F
H
1/0 1/0 1/0 1/0 1/0 1/0 1/0 1/0
CH1
CH2
Bit position b0 b4 b5 b6 b7 b1 b2 b3 b8 to b14 b15
Description
Operation setting
Data bit
Parity bit
Even/odd parity
Stop bit
Sum check code
Write during RUN
Setting modification
Communication rate
(Fixed to ON (1))
Setting
OFF(0) ON(1)
Independent
Linked
7
No
Odd
1
8
Yes
Even
2
No Yes
Prohibited Allowed
Prohibited Allowed
—
( 1)
—
Specify [8000
H
] when the "GX Developer connection" is selected for the switching mode No..
1 The specified values for the communication speed
Communication rate
(Unit: bps)
50
300
600
1200
2400
4800
9600
Bit position b14 to b8
0F
00
01
02
03
04
05
H
H
H
H
H
H
H
Communication rate
(Unit: bps)
14400
19200
28800
38400
57600
115200
230400
Bit position b14 to b8
06
07
08
09
0A
0B
0C
H
H
H
H
H
H
H
• Transmission speed of 230400 bps is available for only CH1 of the QJ71C24N (-R2/R4).
• When connecting external devices to both of two interfaces, the total of the communication speed should be
115200 bps of less (230400 bps or less if using QJ71C24N (-R2/R4)). When connecting an external device to either of two interfaces, the maximum of 115200 bps is available for the interface (a maximum of 230400 bps if using QJ71C24N (-R2/R4)). In this case, set 300 bps for the other interface to which no external device is connected.
• Set "00
H
" to the interface for which "GX Developer connection" is set in the communication protocol setting.
Serial communication module will operate at the communication speed set on the GX Developer.
REMARK
The PLC CPU must also be aware of the following I/O signals for handshake and buffer memories when the mode is switched from an external device.
• Mode switching in progress signal (X6/XD)
• Switch setting error, mode switching error storage area (address: 203
H
)
15 - 6 15 - 6
15 SWITCHING THE MODE AFTER STARTING
MELSEC-Q
15.4 Switching the Mode from the PLC CPU
This section shows how the Q series C24 mode is switched from the PLC CPU.
15.4.1 Mode switching procedure
Mode switching request
The following explains the procedure for switching the Q series C24 mode from the
PLC CPU.
1
Y2/Y9
Mode switching in progress X6/XD
CH ERR. communication error XE/XF
Q series C24 ready
X1E
Mode switching area
(address 90
H
to 91
H
/130
H
to 131
H
)
Switch setting error, mode switching error storage area
(address 203
H
)
Buffer memory special applications area
Data communications initialization setting areas described in
User's Manual (Basic) Section 3.9
Addresses 93
H
to 121
H
/133
H
to 1C1
H
)
Approx. 400 ms
2
TO
Data communications possible
FROM
(Only when normal)
TO
Data communications impossible
Default value change
(Performed only when necessary)
3 Data communications possible
1 Inform in advance all the connected device that data communications by mode switching cannot be performed.
2 When XE and XF were turned on, check the error contents as described in
Sections 10.1.2 of User's Manual (Basic) and take the corresponding action.
• Checking of mode switching designation contents for buffer memory mode switching area and writing of mode switching designation contents within the range that can be designated.
• Re-execution of mode switching.
3 After checking that mode switching was completed normally, inform all the connected devices that data communications are possible and restart data communications.
To check the Q series C24 mode (communication protocol, transmission specifications) after switching, read the buffer memories (addresses: 252
H
to
253
H
, 262
H
to 263
H
) described in Section 10.1.5 of User’s Manual (Basic).
15 - 7 15 - 7
15 SWITCHING THE MODE AFTER STARTING
MELSEC-Q
15.4.2 Mode switching sample program
The following shows a sample sequence program that switches the CH1 interface mode.
(The Q series C24 I/O signals X/Y00 to X/Y1F)
Mode switching instruction
Reception processing
Transmission processing
Reception read request
Abnormal reception detection
Modification of the setting values of the buffer memory special applications area
Changes the operation mode to
MC protocol format 1.
Sets the transmission specifications.
Writes the mode switching designation contents to the buffer memory.
Sets the mode switching request.
Resets the mode switching error signal.
Reads the mode switching request contents.
Mode switching complete.
Changes the setting value of the to the communication specification
Mode switching complete reset
Error processing (LED OFF, error code clear)
Mode switching request clear by clear command.
15 - 8 15 - 8
15 SWITCHING THE MODE AFTER STARTING
MELSEC-Q
15.5 Switching the Mode from an External Device
This section shows how the Q series C24 mode is switched from an external device.
15.5.1 Mode switching procedure
External device
PLC CPU
Mode switching in progress
The following explains the procedure for switching the Q series C24 mode from an external device.
1
Mode switching command message
See Section 3.13 of reference manual for message format
Mode switching response message
(Normal end)
Approx. 400 ms
X6/XD
2
CH ERR. communication error
XE/XF
Q series C24 ready
X1E
Switch setting error, mode switching error strage area (address 203
H
)
Buffer memory special applications area
Data communications initialization setitng area described in
Section 3.9 of User's Manual (Basic).
Addresses 93
H
to 121
H
/133
H
to 1C1
H
Data communications possible
3
FROM
(Only when normal)
3
TO
Data communications impossible default value modification
(Performed only when necessary)
4 Data communications possible
1 Inform in advance all the connected devices that data communications by mode switching cannot be performed.
2 When XE, XF was turned on, check the error contents described in Sections
10.1.2 and 10.1.5 of User’s Manual (Basic) and take the corresponding action.
• Checking of mode switching designation contents for buffer memory mode switching area and writing of mode switching designation contents within the range that can be designated.
• Re-execution of mode switching
3 When the mode was switched from an external device, after mode switching is complete, read and write the buffer memory special applications area shown below from the PLC CPU.
• Switch setting error, mode switching error storage area (address: 203
H
)
• Data communications initialization setting areas (addresses: 93
H
to
121
H
/133
H
to 1C1
H
) described in Section 3.9 of User's Manual (Basic).
4 After checking that mode switching was completed normally, inform all the connected devices that data communications are possible and restart data communications.
15 - 9 15 - 9
15 SWITCHING THE MODE AFTER STARTING
MELSEC-Q
REMARK
To check the Q series C24 mode (communication protocol, transmission specifications) after switching, read the buffer memory (addresses: 252
H
to 253
H
,
262
H
to 263
H
) described in Section 10.1.5 of User's Manual (Basic).
(To check the external device, read the buffer memory with the MC protocol buffer memory read function.)
15.5.2 Mode switching sample program
The following shows a PLC CPU sample sequence program that switches the CH1 interface mode from an external device.
(The Q series C24 I/O signals X/Y00 to X/Y1F)
Remodification of setting value of buffer memory special applications area
Reads the mode switching error contents.
Mode switching complete.
Changes the setting value of the communication protocol accoding to the communication specification.
Mode switching complete reset.
Error processing (LED OFF, error code clear)
15 - 10 15 - 10
16 USING COMMUNICATION DATA MONITORING FUNCTION
MELSEC-Q
16
16 USING COMMUNICATION DATA MONITORING FUNCTION
The following describes the QJ71C24N (-R2/R4) communication data monitoring function.
16.1 Communication Data Monitoring Function
16.1.1 Overview
Communication data monitoring function is a function to monitor communication data between the QJ71C24N (-R2/R4) and an external device on communication lines.
The system startup time can be reduced by analyzing the communication data on the communication lines when debugging the system.
The following two methods are for the communication data monitoring.
(1) Communication data monitoring by the PLC program (Explained in this section)
Monitoring is performed by the monitor start instruction written in the communication data monitoring specification area of the buffer memory.
(2) Communication data monitoring by GX Configurator-SC
The debugging support function of the GX Configurator-SC protocol FB support in used for monitoring (circuit trace).
See the Operating Manual (Protocol FB support function) for the debugging support function of the GX Configurator-SC protocol FB support.
This section describes the communication data monitoring by the PLC program.
16 - 1 16 - 1
16 USING COMMUNICATION DATA MONITORING FUNCTION
MELSEC-Q
16.1.2 Communication data monitoring operation
The following describes the communication data monitoring operation.
POINT
(1) When using the communication data monitoring function, the total transmission speed of the two interfaces should not exceed 115200 bps.
(2) The communication data monitoring function is effective when the communication protocol is assigned to 0
H
to 8
H
.
(1) Monitor start
(a) Monitor start instruction "0001
H
" is written in the communication data monitoring specification area (Address: 2018
H
/2118
H
). (Set by user)
(b) By the monitor start instruction, the monitor data pointer/monitor data size area are cleared to 0 and "0002
H
" is written in the communication data monitoring specification area which starts monitoring.
1
(Q series C24 is set.)
(c) When a monitor setting error occurs, "100F
H
" is written in the communication data monitoring specification area. (Q series C24 is set.)
Check the monitor buffer head address and the monitor buffer size setting range and perform monitoring again.
1 Monitor data area (Default address: 2602
H
to 32FF
H
/3302
H
to 3FFF
H
) is not cleared to 0.
(2) During monitoring
(a) After monitoring starts, data of reception, transmission, receiving error, and signal change are stored from the head address of the monitor data area in the order of occurrence.
(b) When the monitoring data exceeds the capacity of the monitor data area, monitoring is continued by writing new data over the oldest data.
However, monitoring may automatically stop according to the settings of the monitor option area (Address: 2019
H
/2119
H
). (See Section 16.2 (2) (b).)
(CH1)
2600
H
2601
H
2602
H
2603
H
2604
H
2605
H
2606
H
Buffer memory
0003
H
0CFE
H
Oldest data
+0
+1
+2
+3
Monitor data pointer storage area
Monitor data size storage area
Monitor data area to
16
32FF
H
(Default value)
16 - 2 16 - 2
16 USING COMMUNICATION DATA MONITORING FUNCTION
MELSEC-Q
(c) Each data is stored in the monitor data area using the following timing.
Data classification
Received data
Transmitted data
Receiving error data
RS, DSR signals
RS-232 line
CS, DSR,
CD signals
Data storage timing
When receiving data
When transmitting data
When detecting receiving errors
When changing the RS, ER signals
When signal changes are detected during the periodic processing
(Operation interval: 1 to 19 ms) as well as for the above timing
(Monitoring is not performed during the periodic processing)
(3) Monitor stop
Monitoring stops if any of the following conditions are satisfied.
(a) Monitor stop by user instructions
Monitoring stops if "0000
H
" is written in the communication data monitoring specification area of the buffer memory. (Set by user)
(b) Monitor stop by the system when the monitor data area is full
1) The full stop specification (bit 0) of the monitor option specification area of the buffer memory is set to "ON. "
2) When the monitor data area is full (monitor buffer size), monitoring is automatically stopped and "1002
H
" is written in the communication data monitoring specification area. (Q series C24 is set.)
(c) Monitor stop by the system when the timer 0 error occurs
1) The timer 0 error stop specification (bit 2) of the monitor option specification area of the buffer memory is set to "ON. "
2) When the timer 0 error (error code 7F40
H
) occurs, monitoring is automatically stopped and "1002
H
" is written in the communication data monitoring specification area. (Q series C24 is set.)
1
1 Part of the data immediately after the occurrence of a timer 0 error may be entered in the monitor data area.
16 - 3 16 - 3
16 USING COMMUNICATION DATA MONITORING FUNCTION
MELSEC-Q
16.2 Communication Data Monitoring Function Settings
Settings for the communication data monitoring function can be made on the
"Transmission control and other system setting" screen of the GX Configurator-SC, or by the PLC program.
(1) GX Configurator-SC setting for the communication data monitoring function
The setting items for the communication data monitoring function are shown below.
See (2) for setting details.
[Transmission control and other system setting screen]
Setting items
Send/Receive data monitoring designation
Action for buffer full
Stop by Timer 0 error
Monitor buffer head address
Monitor buffer size
[Setting items]
Setting values
No monitoring/Monitor stop
Monitor start
Continue/Stop
Continue/Stop
0400
H
to 1AFD
H
, 2600
H
to 3FFD
H
0003
H
to 1A00
H
Item details
Select "monitor start" for constant monitoring.
Select "stop" to stop monitoring when the monitor data area is full.
Select "stop" to stop monitoring when a timer 0 error occurs.
Enter a value to change the monitor buffer address.
(Default address: 2600
H
/3300
H
)
Enter a value the monitor buffer size.
(Default: 0D00
H
)
16 - 4 16 - 4
16 USING COMMUNICATION DATA MONITORING FUNCTION
MELSEC-Q
(2) Buffer memory for communication data monitoring function
(a) Communication data monitoring specification area (Address: 2018
H
/2118
H
)
Set start/stop of the communication data monitoring.
See Section 16.1.2 for communication data monitoring setting operation.
Buffer memory address 2018
H
/2118
H b15 to b0
(Default: 0000
H
)
Set the monitor start/stop.
0000
H
: No monitor/Monitor stop
0001
H
: Monitor start
0002
H
: Monitoring
1002
H
: Monitor stop
(Set by Q series C24)
(Set by Q series C24)
100F
H
: Monitor setting error (Set by Q series C24)
(b) Monitor option specification area (Address: 2019
H
/2119
H
)
Specify the options of the communication data monitoring function.
Buffer memory address 2019
H
/2119
H b15 to
0 b3 b2 b1
1/0 0 b0
1/0 (Default: 0000
H
)
Action for buffer full
0
H
: OFF
1
H
: ON
Stop by timer 0 error
0
H
: OFF
1
H
: ON
1) Action for buffer full (bit 0)
• When action for buffer full is OFF
When the monitoring data exceeds the capacity of the monitor data area, monitoring continues by writing the new data over the oldest data.
• When action for buffer full is ON
When the monitor data area is full (monitor buffer size), monitoring is automatically stopped and "1002
H
" is written in the communication data monitoring specification area. (set by Q series C24)
2) Stop by timer 0 error (bit 2)
• When the stop by timer 0 error is OFF
Monitoring continues even if the timer 0 error (error code 7F40
H
) occurs.
• When the stop by timer 0 error is ON
When the timer 0 error (error code 7F40
H
) occurs, monitoring is automatically stopped and "1002
H
" is written in the communication data monitoring specification area. (set by Q series C24)
(c) Monitor buffer head address specification area (Address: 201A
H
/211A
H
)
Specify the head address of the storage area (monitor data area) for the monitor data within the range of the user’s free area of the buffer memory.
Setting range: 0400
H
to 1AFD
H
, 2600
H
to 3FFD
H
(Default: 2600
H
/3300
H
)
16 - 5 16 - 5
16 USING COMMUNICATION DATA MONITORING FUNCTION
MELSEC-Q
(d) Monitor buffer size specification area (Address: 201B
H
/211B
H
)
Set the size of the monitor data area.
Setting range: 0003
H
to 1A00
H
(Default: 0D00
H
)
(e) Monitor data pointer storage area (Address: according to monitor buffer head address setting (Default: 2600
H
/3300
H
))
1) The oldest data position of the monitor data area is stored using the offset value from the head address of the monitor data area.
0 to (monitor buffer size specification (Default: 0D00
H
) –3): oldest data position
2) When the monitoring data exceeds the monitor buffer size, the new data is written over the oldest data. (Ring buffer type)
The oldest data position of the monitor data area can be confirmed from this area.
(Example) "2611
H
" becomes the oldest data when "000F
H
" is the monitor data pointer using "2602
H
" as the head address of the monitor data area.
+C
+D
+E
+F
+8
+9
+A
+B
+4
+5
+6
+7
+0
+1
+2
+3
Monitor data pointer storage area
Monitor data size storage area
Oldest data in the monitor data area
(f) Monitor data size area (Address: according to the monitor buffer head address setting (Default: 2601
H
/3301
H
))
The number of monitor data stored in the monitor data area is stored.
0 to (monitor buffer size specification (Default: 0D00
H
) –2): Number of monitor data
16 - 6 16 - 6
16 USING COMMUNICATION DATA MONITORING FUNCTION
MELSEC-Q
0
0
0 b15 b14 b13 b12
0 0 0 0
0
0
0
0
1
1
1
0
1
0 1 0 0
(g) The monitor data area (Default addresses: 2602
H
to 32FF
H
/3302
H
to
3FFF
H
)
The monitor data are stored in one-word units as shown in the configuration below.
See Section 16.3 for an example of the communication data monitoring.
b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0
CD CS DSR
Received data When receiving data
CD CS DSR
CD CS DSR
CD CS DSR
CD CS DSR
Transmitted data
0
0
0
When transmitting data
RS DTR
When the RS/DTR signal is changed
FE OVR PE
( 1)
When a reception error occurs
When detecting a CD to DSR signal change
Data classification
(b12 to b15)
0: When receiving data
1: When transmitting data
Signal condition (b8 to b11)
System area
2: When the RS/DTR
signal is changed
3: When a reception error occurs
4: When detecting a CD to DSR
signal change
1 FE: Framing error
OVR: Overrun error
PE: Parity error
16 - 7 16 - 7
16 USING COMMUNICATION DATA MONITORING FUNCTION
MELSEC-Q
16.3 Communication Data Monitoring Example
The following is an example of the data monitoring of nonprocedural protocol communication.
(1) System configuration
The system configuration for the sample program is as shown below.
The CH used for operation of this sample program is CH1 only.
CH1: Transmission channel
CH2: Reception channel
GX Developer QJ71C24N-R2
(2) Program condition
This is a program to monitor transmitted data from CH1 of the QJ71C24N-R2 with user instructions.
(a) GX Developer switch setting (See User’s Manual (Basic) Section 4.5.2.)
Switch number
Switch 1
Switch 2
Switch 3
Switch 4
Switch 5
Setting value
07C2
0006
07C2
0006
0000
(b) Devices used by the user
• Monitor start instruction signal .................. X20
• Monitor option specification signal ............ X21
• Monitor stop instruction signal .................. X22
• During monitor start instructions ............... M20
• During monitoring ..................................... M21
• During monitor stop instructions ............... M22
• Communication data monitoring specification area storage condition ......... D300
• Monitor option specification area storage condition....................................... D301
16 - 8 16 - 8
16 USING COMMUNICATION DATA MONITORING FUNCTION
(C) Sample program
<Monitor start (X20 is ON)>
<Monitor option (X21 is ON)>
<Monitor stop (X22 is ON)>
MELSEC-Q
Monitor data area is cleared to 0.
Monitor start being instructed
Monitoring (0002
H
)
Monitor setting error (100F
H
)
During monitor stop (1002
H
)
Monitor stop being instructed
Monitor stop (0000
H
)
16 - 9 16 - 9
16 USING COMMUNICATION DATA MONITORING FUNCTION
MELSEC-Q
(3) Confirming monitor data by GX Developer
The monitor data area for CH1 (Address: 2602
H
to 32FF
H
) is monitored on the buffer memory batch monitoring screen of the GX Developer.
See Section 16.2 (2) (g) for the data configuration of the monitor data area.
(Example) The following data are sent from CH1 using non procedure protocol.
Transmitted data; "ABCDEFGH" + 0D0A
H
(five-word) b15 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0
0 0 0 1 0 0 1 1 0 1 0 0 0 0 0 1 When transmitting data
System area
CD CS DSR
Data transmission
16 - 10 16 - 10
17 DEDICATED INSTRUCTIONS
MELSEC-Q
17
17 DEDICATED INSTRUCTIONS
Dedicated instructions are used to simplify programming when using the intelligent functional module functions. Among the dedicated instructions for the Q series C24 explained in this manual, this chapter focuses on the instructions that can be used for
QCPU.
17.1 Dedicated Instruction List
Application
For data transmission/reception
For setting the units of communication data count
For the PLC CPU monitoring function
For registration/reading of user frames to Flash
ROM
CSET
PUTE
GETE
The following table lists the dedicated instructions explained in this chapter.
Dedicated instruction
BUFRCVS
PRR
Functional description
Receives data by an interrupt program during data communication via the non procedure protocol or bidirectional protocol.
Employs user frames to perform data communication via the non procedure protocol according to the contents defined in the transmission user frame designation area.
Reference section
Section 17.2
Section 17.6
Sets the units (word/byte) of transmission/reception data count.
Registers/cancels PLC CPU monitoring in order to use the PLC CPU monitoring functions.
Registers a user frame.
Reads a user frame.
Section 17.4
Section 17.3
Section 17.7
Section 17.5
POINT
(1) The user should not change data (control data, request data, etc.) designated by a dedicated instruction until the execution of that instruction is completed.
(2) Dedicated instructions for the Q series C24 are executed based on the current setting values stored in the buffer memory when the module is started.
When it is necessary to change any of the setting values, change the desired setting value using GX Configurator-SC before starting up the respective module. Alternatively, setting values can be changed using a sequence program before starting up the PLC CPU.
1) Area of the buffer memory assigned for applicable functions of dedicated instructions.
2) Setting values for data communication
• Word/byte unit setting
• Receive complete code
• Received data count etc.
17 - 1 17 - 1
17 DEDICATED INSTRUCTIONS
MELSEC-Q
17.2 BUFRCVS Instruction
Setting data
(S)
(D)
Bit
—
Internal device
Word
File register
[Instruction code]
BUFRCVS
[Executing condition]
[Instruction format]
Applicable device
MELSECNET/H,
MELSECNET/10
Direct J \
Bit Word
Special module
U \G
—
—
Index register
Zn
Constant Others
Z.BUFRCVS
"Un" (S) (D)
Setting data
Setting data
"Un"
(S)
(D)
Description
Start I/O signal of the module
(00 to FE: The 2 upper digits of an input/output signal expressed in 3-digit.)
Reception channel number
1: Channel 1 (CH1 side)
2: Channel 2 (CH2 side)
Head number of the devices that store receive data
Receive data is read from the reception area of the buffer memory.
Setting range
0 to FE
H
1, 2
—
Set by
User
System
Data type
Binary 16 bits
Device name
The file registers of each of the local device and the program cannot be used as the setting data.
Receive data
Device
(D)+1 to
(D)+n
Receive data
Item
(D)+0 Receive data length
Setting data
Stores the number of data read from the receive data count storage area. (
1
)
Setting range
0 or more
Set by
System
Stores data read from the receive data count storage area in sequence, starting from the youngest address.
— System
1 According to the "Word/byte units designation" by GX Configurator-SC, the number of bytes is stored when byte is designated and the number of words is stored when word is designated.
17
REMARK
(1) For information about errors caused by incorrect data designated by the user, see the description in "Errors" on the next page.
When a reception error occurs, the error code can be read from the data reception result storage area (address: 258
H
/268
H
) in the buffer memory.
(2) The "Set by" column indicates the following:
• User : Data set by the user before executing the dedicated instruction.
• System: The PLC CPU stores execution results of the dedicated instruction.
17 - 2 17 - 2
17 DEDICATED INSTRUCTIONS
Functions
Errors
MELSEC-Q
(1) This instruction stores data received from an external device to a designated device.
(2) This instruction can identify the address of the reception area in the buffer memory and read relevant receive data.
(3) When this instruction is executed, reception is completed and the reception data read request signal (X3/XA) or the reception abnormal detection signal (X4/XB) is turned off automatically.
It is not necessary to turn on the reception data read completion signal (Y1/Y8) when receive data is read by this instruction.
(4) The BUFRCVS instruction is used by an interrupt program and its processing is completed in one scan.
[Operation when the BUFRCVS instruction is being executed]
Scan
Sequence program
Interrupt program
BUFRCVS instruction
Instruction execution
END processing
Data reception
Receive data storage
(1) When the dedicated instruction is completed abnormally, the error flag (SM0) turns on and the error code is stored in SD0.
See the following manuals regarding the error code, and check the errors and take corrective actions.
<Error codes>
4FFF
H
or less : QCPU (Q Mode) User's Manual (Hardware Design, Maintenance and Inspection)
7000
H
or higher: Section 10.2 of the User's Manual (Basic)
17 - 3 17 - 3
17 DEDICATED INSTRUCTIONS
MELSEC-Q
Precaution when using the BUFRCVS instruction
(1) Use the BUFRCVS instruction when receiving data via an interrupt program.
(2) If reading of data received is to be done for the same interface, data cannot be received by the main program when the receiving of data is done by an interrupt program.
Thus, the BUFRCVS instruction cannot be used together with the following instructions.
• INPUT instruction (instruction for receiving data using the non procedure protocol via the main program)
• BIDIN instruction (instruction for receiving data using the bidirectional protocol via the main program)
Data cannot be received using the FROM instruction and input/output signals.
(3) The CSET and BUFRCVS instructions cannot be executed at the same time.
(4) The device storing data received via the BUFRCVS instruction must have an area that is large enough to store the maximum size of data received from the external device.
If an area large enough to store the maximum size of data received from the external device is not secured, the data following the storage device will be overwritten.
Program example
An interrupt program that reads receive data.
(Setting)
• Interrupt pointer setting with GX Developer
CPU side: Interrupt pointer. Start No. = 50,
Interrupt pointer No. of units = 2 (fixed)
CH1 side interrupt pointer = I50,
CH2 side interrupt pointer = I51
Intelligent. module side: Start I/O No. = 0, Start SI No. = 0 (fixed)
• Interrupt program start enable/disable setting with GX Configurator-SC
CH1 side: Issues interrupt (performs communication via the non procedure protocol.)
CH2 side: Does not issue interrupt
When the input/output signals of the Q series C24 are X/Y00 to X/Y1F
<Interrupt program enabled >
In case of CH1 side
<Normal reception >
<Abnormal reception >
<Reception interrupt program execution>
Sets the checking flag for normal reception/abnormal reception via the main program.
Resets on the main program side
Receives data and stores in D200 and later.
D200: Receive data count
D201 and later: Receive data
17 - 4 17 - 4
17 DEDICATED INSTRUCTIONS
MELSEC-Q
17.3 CSET Instruction (PLC CPU Monitoring Register/Cancel)
Setting data
(S1)
(S2)
(D1)
(D2)
Bit
—
—
—
Internal device
Word
File register
Applicable device
MELSECNET/H,
MELSECNET/10
Direct J \
Bit Word
—
Special module
U \G
—
—
—
Index register
Zn
Constant
K, H
[Instruction code] [Executing condition]
CSET
[Instruction format]
ZP.CSET
"Un" (S1) (S2) (D1)
(D2)
Others
—
Setting data
Setting data
"Un"
(S1)
(S2)
(D1)
(D2)
Description
Start I/O signal of the module
(00 to FE: The 2 upper digits of an input/output signal expressed in 3-digit.)
Channel No. for sending the monitoring result
1: Channel 1 (CH1 side)
2: Channel 2 (CH2 side)
Head number of the devices that store control data
Dummy
Head bit device number of the local station that turns ON for one scan upon instruction completion.
(D2)+1 also turns ON if the instruction execution completes abnormally.
Set by
User
User,
System
—
System
Data type
Binary 16 bits
Device name
Device name
Bit
The file registers of each of the local device and the program cannot be used as the setting data.
Control data
Device Item
(S2)+0 Execution type
(S2)+1 Completion status
(S2)+2 Request type
(S2)+3 Cycle time units
(S2)+4 Cycle time
(1) Registering the PLC CPU monitoring
(S2)+5 PLC CPU monitoring function
Setting data
Designate 0.
Stores the result of execution upon completion of an instruction.
0 : Normal
Other than 0: Abnormal (error code)
Designate the request content.
2: Registers PLC CPU monitoring.
Designate the unit of cycle time.
0: 100 ms 1: s
Designate the cycle time.
1
H
to FFFF
H
: Cycle time
2: min
Designate the monitoring function.
1: Constant cycle transmission
2: Condition agreement transmission
Setting range
0
—
2
0 to 2
1
H
to FFFF
H
1, 2
Set by
User
System
User
17 - 5 17 - 5
17 DEDICATED INSTRUCTIONS
MELSEC-Q
Device
(S2)+6
(S2)+7
(S2)+8
(S2)+9
(S2)+12
(S2)+13
(S2)+14
(S2)+15
(S2)+16
(S2)+17
(S2)+18
(S2)+19
(S2)+20
(S2)+21
Constant cycle transmission
(S2)+10 Registered word blocks count
(S2)+11 Registered bit blocks count
PLC CPU monitoring setting
1 st.
first
block
Item
PLC CPU monitoring transmission measure
User frame output head pointer
User frame transmission count
Modem connection data No.
PLC CPU abnormal monitoring
(PLC CPU status monitoring)
Device code
Monitoring head device
Setting data
Designate the transmission measure.
0: Data transmission (device data, CPU abnormal information)
1: Notification
Designate the head pointer of the table setting the user frame numbers for constant cycle transmission.
0 : No designation (at condition agreement transmission and notification)
1 to 100: Head pointer
Designate the user frame transmission (output) counts for constant cycle transmission.
0 : No designation (at condition agreement transmission and notification)
1 to 100: Transmission count
Designate the data No. for connecting the modem function when sending notifications in constant cycle transmission.
0 : No designation (at data transmission and condition agreement transmission)
BB8
H
to BD5
H
: Data No. for connection (flash ROM)
8001
H
to 801F
H
: Data No. for connection (buffer memory)
Designate the number of blocks of a word device to be monitored.
Designate the number of blocks of a bit device to be monitored.
Designate whether or not to execute abnormal monitoring for the PLC CPU.
0: Do not monitor.
1: Monitor.
Designate the code of a device to be monitored.
0: Do not monitor device.
Other than 0: Device code.
Designate the head number of the monitoring device in this block.
Registration points
Condition agreement transmission
Monitoring condition
Monitoring condition value
User frame output head pointer
User frame transmission count
Modem connection data
No.
Designate the registration points (read points) for this block.
0: Do not monitor device. 1or more: Registration points
For a bit device, designate the points in word units.
Designate the monitoring condition for this block.
0: No designation (at constant cycle transmission)
1or more: Monitoring condition
Designate the monitoring condition value for this block.
0 or more: Monitoring condition
Designate 0 for constant cycle transmission.
Designate the head pointer of the table designating the user frame number for condition agreement transmission for this block.
0 : No designation (at constant cycle transmission and notification)
1 to 100: Head pointer
Designate the user frame transmission (output) count in condition agreement transmission for this block.
0 : No designation (at constant cycle transmission and notification)
1 to 100: Transmission count
Designate the data No. for connecting the modem function when sending notification in condition agreement transmission for this block.
0 : No designation (at data transmission and constant cycle transmission)
BB8
H
to BD5
H
: Data No. for connection (flash ROM)
8001
H
to 801F
H
: Data No. for connection (buffer memory)
Setting range
0, 1
0, 1 to 100
0, 1 to 100
0,
BB8
H
to BD5
H
8001
H
to 801F
H
0 to 10
0 to 10
0, 1
See Section
2.2.2 (4).
0 or more
0.1or more
See Section
2.2.2 (2).
0, 1 to 100
0, 1 to 100
0,
BB8
H
to BD5
H
8001
H
to 801F
H
Set by
User
17 - 6 17 - 6
17 DEDICATED INSTRUCTIONS
MELSEC-Q
Device
(S2)+22 to
(S2)+102
(S2)+103
(S2)+104
(S2)+105
(S2)+106
(S2)+107
(S2)+108
(S2)+109
(S2)+110
(S2)+111
Item
PLC CPU monitoring setting
Setting data Setting range
2nd to 10 th
* 2nd to 10th block
The same arrangement as the first PLC CPU monitoring setting item.
—
Fixed value
Designate the fixed value when the CPU status monitoring is performed.
0
1
1
0
5
1
CPU status monitoring setting
Abnormal
Condition agreement
monitoring
11 th
11th block transmissio n
User frame output head pointer
User frame transmissi on count
Modem connection data
No.
Designate the head pointer of the table designating the user frame number for condition agreement transmission for this block
0 : No designation (at constant cycle transmission and notification)
1 to 100: Head pointer
Designate the transmission (output) count of the user frames in condition agreement transmission for this block.
0 : No designation (at constant cycle transmission and notification)
1 to 100: Transmission count
Designate the data No. for connecting the modem function when sending notifications in condition agreement transmission for this block.
0 : No designation (at data transmission and constant cycle transmission)
BB8
H
to BD5
H
: Data No. for connection (flash ROM)
8001
H
to 801F
H
: Data No. for connection (buffer memory)
0, 1 to 100
0, 1 to 100
0,
BB8
H
to BD5
H,
8001
H
to 801F
H
Device Item
(S2)+0 Execution type
(S2)+1 Completion status
(S2)+2 Request type
(2) Canceling the PLC CPU monitoring
Setting data
Designate 0
H
.
Stores the result of execution upon completion of an instruction.
0 : Normal
Other than 0: Abnormal (error code)
Designate the request content.
3: Cancels the PLC CPU monitoring.
(S2)+3 to
(S2)+111
For system —
Set by
User
Setting range Set by (
0 User
1
)
—
3
—
System
User
System
REMARK
(1) For information about errors caused by incorrect data designated by the user, see the description in "Errors" on the next page.
(2) The "Set by" column indicates the following:
• User : Data set by the user before executing the dedicated instruction.
• System: The PLC CPU stores execution results of the dedicated instruction.
17 - 7 17 - 7
17 DEDICATED INSTRUCTIONS
MELSEC-Q
Functions
(1) To register the PLC CPU monitoring, this instruction registers data necessary for the Q series C24 to execute the PLC CPU monitoring function.
When the data registration to execute the PLC CPU monitoring function is completed normally, the Q series C24 begins monitoring the PLC CPU and transmitting monitoring results to an external device.
(2) To cancel the PLC CPU monitoring, this instruction ends the Q series C24's monitoring operation of the PLC CPU.
When canceling of the PLC CPU monitoring is completed normally, the Q series
C24 terminates the operation of the PLC CPU monitoring function.
(3) A maximum of 10 blocks can be designated for a word device or bit device to monitor the device memory.
To register the device memory to monitor, designate the word device blocks for the registered word blocks, then designate the bit device blocks for the registered bit blocks.
(4) Before sending the PLC CPU monitoring results to the external device, the user frame and user frame number should be registered with GX Configurator-SC in advance.
(5) To register the PLC CPU monitoring once again, cancel the PLC CPU monitoring before registration.
(6) Whether the CSET instruction is being executed or has been completed normally/abnormally can be checked by the completion device (D2) designated as a setting data.
(a) Completion device ((D2) + 0)
Turns on at the END processing of the scan where the CSET instruction is completed, and turns off at the next END processing.
(b) Completion device ((D2) + 1)
Turns on and off depending on the completion status of the CSET instruction.
• Normal completion : Stays off and does not change.
• Abnormal completion: Turns on at the END processing of the scan where the CSET instruction is completed, and turns off at the next END processing.
(7) When the PLC CPU monitoring registration is performed, the corresponding interface data communication protocol setting is only designated when non procedure protocol is used for the following data for designation in the control data.
• User frame output head pointer for constant cycle sending/ batch conditions sending.
• User frame transmission count for constant cycle sending/ batch conditions sending.
When the communication protocol setting for the corresponding interface is MC protocol, there is no need to designate the user frame output head pointer and the user frame transmission count. (It is ignored when being designated.)
17 - 8 17 - 8
17 DEDICATED INSTRUCTIONS
MELSEC-Q
Sequence program
CSET instruction
Completion device
Completion device + 1
Q series C24
[Operation when a CSET instruction is being executed]
Scan
END processing
Scan
Instruction execution
END processing
Scan
Setting processing
Abnormal completion
END processing
Errors
(1) When the dedicated instruction is completed abnormally, the error flag (SM0) turns on and the error code is stored in SD0.
See the following manuals regarding the error code, and check the errors and take corrective actions.
<Error codes>
4FFF
H
or less : QCPU (Q Mode) User's Manual (Hardware Design, Maintenance and Inspection)
7000
H
or higher: Section 10.2 of the User's Manual (Basic)
17 - 9 17 - 9
17 DEDICATED INSTRUCTIONS
MELSEC-Q
Program example
(1) A program that registers the PLC CPU monitoring
The following example shows how to register the PLC CPU monitoring and send the monitoring results from the interface on the CH1 side.
The following registration is done to send the contents of M0 to M15 and D100 to D109 to the external device on a constant cycle (cycle time is 3 min).
When the input/output signals of the Q series C24 are X/Y00 to X/Y1F
Converts registration command to pulses
Sets execution type
Sets request type (PLC CPU monitoring registration)
Sets cycle time unit to minutes
Sets cycle time to 3 (minutes)
Sets the monitoring function to constant cycle transmission
Sets the means of transmission to data transmission
Sets the output head pointer
Sets the transmission count of the user frame
Sets data set complete flag -1
Sets the number of registered word blocks to 1
Sets the number of registered bit blocks to 1
Registers the devices for
D100 to D109 as the first block
Registers the devices for M0 to M15 as the second block
Sets data setting complete flag -2
Executes PLC CPU monitoring registration
Normal completion
Abnormal completion
(2) A program that cancels the PLC CPU monitoring
This following example shows how to cancel the PLC CPU monitoring for the interface on CH1 side.
When the input/output signals of the Q series C24 are X/Y00 to X/Y1F.
Instruction pulse set
Execute canceling the PLC CPU monitoring
Normal completion
Abnormal completion
17 - 10 17 - 10
17 DEDICATED INSTRUCTIONS
MELSEC-Q
17.4 CSET Instruction (Initial Settings)
Setting data
(S1)
(S2)
(D1)
(D2)
Bit
—
—
—
Internal device
Word
[Instruction code]
CSET
[Executing condition]
File register
Applicable device
MELSECNET/H,
MELSECNET/10
Direct J \
Bit Word
—
Special module
U \G
—
—
—
Index register
Zn
Constant
K, H
[Instruction format]
ZP.CSET
"Un" (S1) (S2) (D1) (D2)
Others
—
Setting data
Setting data
"Un"
(S1)
(S2)
(D1)
(D2)
Control data
Device Item
(S2)+0 Execution type
(S2)+1 Completion status
(S2)+2 Request type
Description
Start I/O signal of the module
(00 to FE: The 2 upper digits of an input/output signal expressed in 3-digit.)
Channel No. for sending the monitoring result
1: Channel 1 (CH1 side)
2: Channel 2 (CH2 side)
Head number of the devices that store control data
Dummy
Head bit device number of the local station that turns ON for one scan upon instruction completion.
(D2)+1 also turns ON if the instruction execution completes abnormally.
Set by
User
User,
System
—
System
Data type
Binary 16 bits
Device name
Device name
Bit
The file registers of each of the local device and the program cannot be used as the setting data.
(S2)+3 Word/byte units designation
Setting data
Designate 0.
Stores the result of execution upon completion of an instruction.
0 : Normal
Other than 0: Abnormal (error code)
Designate the request content.
1: Setting of word/byte units and buffer memory assignment change
Designate the units of transmission/reception data count.
0: Current setting value
1: Word units
2: Bit units
Setting range
0
—
1
0, 1, 2
Set by
User
System
User
17 - 11 17 - 11
17 DEDICATED INSTRUCTIONS
MELSEC-Q
Device
(S2)+4
(S2)+5
(S2)+6
(S2)+7
On-demand function buffer memory head address
On-demand function buffer memory size
Transmission area head address
(S2)+8 Reception area head address
(S2)+9
Item
Transmission area size
Reception area size
Setting data
Designate the head address of the buffer memory used with the on-demand function.
0
H
: Use the current setting value
400
H
to 1AFF
H
, 2600
H
to 3FFF
H
: Head address
Designate the size (word number) of the buffer memory used with the on-demand function.
0
H
: Use the current setting value
1
H
to 1A00
H
: Size
Designate the head address of the transmission area used with the non procedure /bidirectional protocol.
0
H
: Use the current setting value
400
H
to 1AFF
H
, 2600
H
to 3FFF
H
: Head address
Designate the size (word number) of the transmission area used with the non procedure /bidirectional protocol.
0
H
: Use the current setting value
1
H
to 1A00
H
: Size
The head transmission area (1 word) is used as a transmission data count designation area.
Designate the head address of the reception area used with the non procedure /bidirectional protocol.
0
H
: Use the current setting value
400
H
to 1AFF
H
, 2600
H
to 3FFF
H
: Head address
Designate the size (word number) of the reception area used with the non procedure /bidirectional protocol.
0
H
: Use the current setting value
1
H
to 1A00
H
: Size
The head reception area (1 word) is used as a reception data count storage area.
Setting range
0
H
,
400
H
to 1AFF
H
,
2600
H
to
3FFF
H
1
H
0
H
,
to 1A00
H
0
H
,
400
H
to 1AFF
H
,
2600
H
to
3FFF
H
1
0
H
,
400
H
to 1AFF
H
,
2600
H
to
3FFF
H
1
H
H
0
to 1A00
0
H
H
,
,
to 1A00
H
H
(S2)+10 to
(S2)+111
For system — —
Set by
User
System
REMARK
(1) For information about errors caused by incorrect designated by the user, see the description in "Errors" on the next page.
(2) The "Set by" column indicates the following:
• User : Data set by the user before executing the dedicated instruction.
• System: The PLC CPU stores execution results of the dedicated instruction.
17 - 12 17 - 12
17 DEDICATED INSTRUCTIONS
MELSEC-Q
Functions
Sequence program
CSET instruction
Completion device
Completion device + 1
Q series C24
(1) This instruction changes the current values of the settings below to transmit/receive data using the following communication protocols:
• Data count unit (word/byte) of the data to be transmitted/received
• Transmission area in the buffer memory used by the on-demand function of the
MC protocol
• Transmission and reception areas in the buffer memory used with the nonprocedure protocol
• Transmission and reception areas in the buffer memory used with the bidirectional protocol
(2) To change the above setting values from the PLC CPU, execute the CSET instruction.
The CSET instruction must be executed before starting any data communication
(execute it before the first scan). Once data communication begins, the CSET instructions cannot be executed (the setting values cannot be changed).
More than one CSET instruction cannot be executed simultaneously to perform the initial settings.
(3) Whether the CSET instruction is being executed or has been completed normally/ abnormally can be checked with the completion device (D2) designated by the setting data.
(a) Completion device ((D2) + 0)
Turns on at the END processing of the scan where the CSET instruction is completed, and turns off at the next END processing.
(b) Completion device ((D2) + 1)
Turns on and off depending on the completion status of the CSET instruction.
• Normal completion : Stays off and does not change.
• Abnormal completion: Turns on at the END processing of the scan where the
CSET instruction is completed, and turns off at the next
END processing.
[Operation when the CSET instruction is being executed]
Scan
END processing
Scan
Instruction execution
END processing
Scan
END processing
Setting processing
Abnormal completion
17 - 13 17 - 13
17 DEDICATED INSTRUCTIONS
MELSEC-Q
Errors
Program example
(1) When the dedicated instruction is completed abnormally, the error flag (SM0) turns on and the error code is stored in SD0.
See the following manuals regarding the error code, and check the errors and take corrective actions.
<Error codes>
4FFF
H
or less : QCPU (Q Mode) User's Manual (Hardware Design, Maintenance and Inspection)
7000
H
or higher: Section 10.2 of the User's Manual (Basic)
A program that changes the transmission buffer area for interface on CH1 side
• Set the transmission buffer to C00
H
to FFF
H
.
• Set the reception buffer to 600
H
to 7FF
H
.
When the input/output signals of the Q series C24 are X/Y00 to X/Y1F
Clears D0 to D111
Sets the execution type
Sets the request type
Sets the word/byte units to word units
Sets the on-demand head address
Sets the on-demand buffer size
Sets the transmission buffer head address
Sets the transmission buffer size
Sets the reception buffer head address
Sets the reception buffer size
Executes the initial setting
17 - 14 17 - 14
17 DEDICATED INSTRUCTIONS
MELSEC-Q
17.5 GETE Instruction
Setting data
(S1)
(S2)
(D)
Bit
—
—
Internal device
Word
File register
Applicable device
MELSECNET/H,
MELSECNET/10
Direct J \
Bit Word
Special module
U \G
—
—
—
Index register
Zn
Constant Others
[Instruction code] [Executing condition]
GETE
GETE
Command
Command
G.GETE
GP.GETE
Un
Un
(S1)
(S1)
(S2)
(S2)
(D)
(D)
Setting data
Setting data
Un
(S1)
(S2)
(D)
Description
Start I/O signal of the module
(00 to FE: The 2 upper digits of an input/output signal expressed in 3-digit.)
Head number of the devices that store control data
Head number of the devices storing the registered data that has been read
Head bit device number of the local station that turns ON for one scan upon instruction completion.
(D)+1 also turns on if the execution completes abnormally.
Set by
User
User,
System
System
Data type
Binary 16 bits
Device name
Bit
The file registers of each of the local device and the program cannot be used as setting data.
Control data
Device
(S1)+0 Dummy
(S1)+1 Read result
(S1)+2 Directed frame No.
(S1)+3
Item
Allowable number of read bytes
Registered bytes count
Setting data
—
The result of reading via the GETE instruction is stored.
0 : Normal
Other than 0: Abnormal (error code)
Designate the user frame No.
Designate the maximum bytes of the user frame's registered data that can be stored in (S2).
The number of bytes of the user frame's registered data that has been read is stored.
Setting range
0
—
1000 to 1199
1 to 80
1 to 80
Set by
—
System
User
User
System
REMARK
(1) For information about errors caused by incorrect data designated by the user, see the description in "Errors" on the next page.
(2) The "Set by" column indicates the following:
• User : Data set by the user before executing the dedicated instruction.
• System: The PLC CPU stores execution results of the dedicated instruction.
17 - 15 17 - 15
17 DEDICATED INSTRUCTIONS
MELSEC-Q
Functions
(1) This instruction reads data from the user frame in the Q series C24 as designated by Un.
QCPU Q series C24
(S2) +0
+1
+2 b15 to
B
D
F b8b7 to
A
C
E b0
Read
User frame
A
B
E
F
C
D
Read byte length
Sequence program
(2) While the GETE instruction is being executed, no other GETE or PUTE instructions can be executed.
While a GETE instruction is already being executed, if another GETE instruction or a PUTE instruction is executed, the second instruction must wait until the execution of the current GETE instruction is completed.
(3) Whether the GETE instruction was completed normally/abnormally can be checked by the completion device (D) or status display device at completion
((D)+1).
(a) Completion device
Turns on at the END processing of the scan where the GETE instruction is completed, and turns off at the next END processing.
(b) Status display device at completion
Turns on and off depending on the completion status of the GETE instruction.
• Normal completion : Stays off and does not change.
• Abnormal completion: Turns on at the END processing of the scan where the GETE instruction is completed, and turns off at the next END processing.
[Operation when the GETE instruction is being executed]
END processing
END processing
GETE instruction execution
END processing
END processing
Completion of reading user frames by the GETE instruction
GETE instruction
Completion device
OFF
Status display
OFF device at completion
ON
ON
Abnormal completion
Normal completion
One scan
17 - 16 17 - 16
17 DEDICATED INSTRUCTIONS
MELSEC-Q
Errors
Program example
(1) When the dedicated instruction is completed with an error, the complete status display device at completion ((D)+1), turns on and the error code is stored in the control data read result ((S1)+1).
See the following manuals regarding the error code, and check the errors and take corrective actions.
<Error codes>
4FFF
H
or less : QCPU (Q Mode) User's Manual (Hardware Design, Maintenance and Inspection)
7000
H
or higher: Section 10.2 of the User's Manual (Basic)
A program that reads registered data of the user frame having registration number
3E8
H
to devices D4 and later.
When the input/output signals of the Q series C24 are X/Y80 to X/Y9F
Read request
Sets the frame No. to be read
Sets the allowable number of data to be read
Clears the device in which to store the read user frame data
Executes user frame reading
Normal completion
Abnormal completion
17 - 17 17 - 17
17 DEDICATED INSTRUCTIONS
MELSEC-Q
17.6 PRR Instruction
Setting data
(S)
(D)
Bit
—
Internal device
Word
File register
Applicable device
MELSECNET/H,
MELSECNET/10
Direct J \
Bit Word
Special module
U \G
—
—
Index register
Zn
Constant Others
[Instruction code] [Executing condition]
PRR
PRR
Command
Command
G.PRR
GP.PRR
Un
Un
(S)
(S)
(D)
(D)
Setting data
Setting data
Un
(S)
(D)
Description
Start I/O signal of the module
(00 to FE: The 2 upper digits of an input/output signal expressed in 3-digit.)
Set by
User
Data type
Binary 16 bits
Head number of the devices that store control data
User,
System
Device name
Head bit device number of the local station that turns ON for one scan upon instruction completion.
(D)+1 also turns on if the execution completes abnormally.
System Bit
The file registers of each of the local device and the program cannot be used as setting data.
Control data
Device Item
(S)+0 Transmission channel
Set by
User
(S)+1 Transmission result
(S)+2 CR/LF addition designation
(S)+3 Transmission pointer
(S)+4 Output count
Setting data
Designate the transmission channel.
1: Channel 1 (CH1 side)
2: Channel 2 (CH2 side)
The transmission completion result by the PRR instruction is stored.
0 : Normal
Other than 0: Abnormal (error code)
Designate whether or not to add CR/LF to the transmission data.
0: Do not add CR/LF.
1: Add CR/LF.
Transmission user frame designation area designates from which the frame number data may be transmitted.
Designate the number of user frames to be transmitted.
Setting range
1, 2
—
0, 1
1 to 100
1 to 100
System
User
User
User
REMARK
(1) For information about errors caused by incorrect data designated by the user, see the description in "Errors" on the next page.
(2) The "Set by" column indicates the following:
• User : Data set by the user before executing the dedicated instruction.
• System: The PLC CPU stores execution results of the dedicated instruction.
17 - 18 17 - 18
17 DEDICATED INSTRUCTIONS
MELSEC-Q
Functions
(1) This instruction transmits the user frame data using the non procedure protocol of the Q series C24 as designated by Un, according to the control data stored in the device designated by (S) and succeeding devices, as well as the transmission user frame designation area of the Q series C24.
(2) The following instructions cannot be executed on a channel on which a PRR instruction is being executed.
• OUTPUT instruction
• ONDEMAND instruction
• Other PRR instruction
• BIDOUT instruction
While a PRR instruction is already being executed, if one of the instructions above is executed, the second instruction must wait until the execution of the current
PRR instruction is completed.
(3) Whether the PRR instruction was completed normally or abnormally can be checked with the completion device (D) or status display device at completion
((D)+1).
(a) Completion device
Turns on at the END processing of the scan where the PRR instruction is completed, and turns off at the next END processing.
(b) Status display device at completion
Turns on and off depending on the completion status of the PRR instruction.
• Normal completion : Stays off and does not change.
• Abnormal completion: Turns on at the END processing of the scan where the PRR instruction is completed, and turns off at the next END processing.
[Operation when the PRR instruction is being executed]
Sequence program
END processing
END processing
PRR instruction execution
END processing
END processing
Completion of transmission by the PRR instruction
PRR instruction
ON
Completion device
OFF
ON
Abnormal completion
Status display
OFF device at completion
Normal completion
One scan
Errors
(1) When the dedicated instruction is completed with an error, the status display device at completion ((D)+1), turns on and the error code is stored in the control data transmission result ((S1)+1).
See the following manuals regarding the error code, and check the errors and take corrective actions.
<Error codes>
4FFF
H
or less : QCPU (Q Mode) User's Manual (Hardware Design, Maintenance and Inspection)
7000
H
or higher: Section 10.2 of the User's Manual (Basic)
17 - 19 17 - 19
17 DEDICATED INSTRUCTIONS
MELSEC-Q
Program example
A program that sends arbitrary data and the first to fifth user frames registered in the output frame setting.
When the input/output signals of the Q series C24 are X/Y80 to X/Y9F
Transmission instruction
Sets arbitrary transmission data.
Sets the number of transmitted data.
Sets the transmission user frames in D5 to D9.
Sets output frame No. in the buffer memory.
Sets CH1 to the transmission channel.
Clears the device in which transmission results are stored.
Sets to no CR/LF output.
Sets the output head pointer.
Sets the output counter.
Executes user frame transmission.
Sets normal completion flag.
Sets abnormal completion flag.
D0
D1
D2
Normal end
Send data count
Send data
(0004
H
)
(3412
H
)
(AB56
H
)
D5 Output frame No.
D6
D7
D8
D9
D10
D11
D12
D13
D14
D15
(03F2
H
)
(03F3
H
)
(8001
H
)
(8000
H
)
(041B
H
)
(0000
H
)
Interface No.
(0001
H
)
Transmission result (0000
H
)
CR/LF output (0000
H
)
Output head pointer (0001
H
)
Output counter (0005
H
)
Abnormal end
Send data count (0004
H
)
Send data
(3412
H
)
(AB56
H
)
Output frame No.
(03F2
H
)
(03F3
H
)
(8001
H
)
(8000
H
)
Interface No.
(041B
H
)
(0000
H
)
(0001
H
)
Transmission result (other than 0000
H
)
CR/LF output (0000
H
)
Output head pointer (0001
H
)
Output counter (0005
H
)
17 - 20 17 - 20
17 DEDICATED INSTRUCTIONS
MELSEC-Q
17.7 PUTE Instruction
Setting data
(S1)
(S2)
(D)
Bit
—
—
Internal device
Word
File register
Applicable device
MELSECNET/H,
MELSECNET/10
Direct J \
Bit Word
Special module
U \G
—
—
—
Index register
Zn
Constant Others
[Instruction code]
[Executing condition]
PUTE
PUTE
Command
Command
G.PUTE
GP.PUTE
Un
Un
(S1)
(S1)
(S2)
(S2)
(D)
(D)
Setting data
Setting data
Un
(S1)
(S2)
(D)
Description
Start I/O signal of the module
(00 to FE: The 2 upper digits of an input/output signal expressed in 3-digit.)
Head number of the devices that store control data
Head number of the devices storing the registered data that has been read
Head bit device number of the local station that turns ON for one scan upon instruction completion.
(D)+1 also turns on if the execution completes abnormally.
Set by
User
User,
System
System
Data type
Binary 16 bits
Device name
Bit
The file registers of each of the local device and the program cannot be used as setting data.
Control data
Device Item
(S1)+0 Register/delete designation
(S1)+1 Register/delete result
(S1)+2 Frame No.
(S1)+3 Registered bytes count
Setting data
Designate whether to register or delete the user frame having the number designated by (S1) +2.
Register: 1
Delete: 3
The registration/deletion result by the PUTE instruction is stored.
0 : Normal
Other than 0: Abnormal (error code)
Designate the user frame No.
1 to 80: Number of bytes of the user frame to be registered.
Designate 1 to 80 as dummy when deleting.
Setting range
1, 3
—
1000 to 1199
1 to 80
Set by
User
System
User
User
REMARK
(1) For information about errors caused by incorrect data designated by the user, see the description in "Errors".
(2) The "Set by" column indicates the following:
• User : Data set by the user before executing the dedicated instruction.
• System: The PLC CPU stores execution results of the dedicated instruction.
17 - 21 17 - 21
17 DEDICATED INSTRUCTIONS
Functions
MELSEC-Q
(1) This instruction registers or deletes the user frame for the Q series C24 as designated by Un.
(2) When registering a user frame
(a) When registering a user frame, set 1 to the device for (S1)+0.
Data in the device designated by (S2) and after will be registered according to the control data.
(b) The registered data should be stored in the device designated by (S2) and after as described below.
Thus, at least (registered data number)/2 devices will be necessary to store the registered data and they should be assigned beginning with the device designated by (S2).
For example, when registering 6 bytes of data, 3 devices beginning with the device designated by (S2) will be used.
QCPU Q series C24
(S2) +0
+1
+2 b15
D
F to
B b8b7
C
E to
A b0
Register
User frame
A
B
E
F
C
D
Registered byte length
(3) When deleting a user frame
(a) When deleting a user frame, set 3 to the device for (S1)+0.
The user frames of the frame numbers designated by (S1)+2 will be deleted.
(b) The registered byte number designated by (S1)+3 and registered data storage device designated by (S2) are not used by the PUTE instruction, but they are necessary for formatting it.
Designate 1 to 80 for (S1)+3 and a dummy device for (S2).
(4) While a PUTE instruction is being executed, another PUTE instruction or a GETE instruction cannot be executed.
While a PUTE instruction is already being executed, if another PUTE instruction or a GETE instruction is executed, the second instruction must wait until the execution of the current PUTE instruction is completed.
17 - 22 17 - 22
17 DEDICATED INSTRUCTIONS
MELSEC-Q
Sequence program
(5) Whether the PUTE instruction was completed normally or abnormally can be checked with the completion device (D) or status display device at completion
(D+1).
(a) Completion device
Turns on at the END processing of the scan where the PUTE instruction is completed, and turns off at the next END processing.
(b) Status display device at completion
Turns on and off depending on the completion status of the PUTE instruction.
• Normal completion : Stays off and does not change.
• Abnormal completion: Turns on at the END processing of the scan where the PUTE instruction is completed, and turns off at the next END processing.
[Operation when the PUTE instruction is being executed]
END processing
END processing
PUTE instruction execution
END processing
END processing
Completion of reading user frames by the PUTE instruction
PUTE instruction
Registration/ deletion request
Completion device
OFF
OFF
Status display
OFF device at completion
ON
ON
ON
Abnormal completion
Normal completion
One scan
Errors
(1) When the dedicated instruction is completed with an error, the status display device at completion ((D)+1), turns on and the error code is stored in the control data registration/deletion result ((S1)+1).
See the following manuals regarding the error code, and check the errors and take corrective actions.
<Error codes>
4FFF
H
or less : QCPU (Q Mode) User's Manual (Hardware Design, Maintenance and Inspection)
7000
H
or higher: Section 10.2 of the User's Manual (Basic)
17 - 23 17 - 23
17 DEDICATED INSTRUCTIONS
MELSEC-Q
Program example
A program that registers the user frame having registration number 3E8
H
.
When the input/output signals of the Q series C24 are X/Y80 to X/Y9F
Registration request
Sets the registration request
Sets the frame number to be registered
Sets the number of registration data bytes
Sets the registration data for the frame to be registered in D4 to D8
Sets the flash ROM write allow
Executes user frame registration
Normal completion
Abnormal completion
17 - 24 17 - 24
17 DEDICATED INSTRUCTIONS
MEMO
MELSEC-Q
17 - 25 17 - 25
INDEX
[A]
Additional codes ........................................ 12-1
ASCII-BIN conversion ............................... 13-1
[B]
[C]
Buffer memory (for modem)...................... 3-33
(for on-demand data transmission)...... 10-2
(for user frame)..................................... 9-14
BUFRCVS instruction................................ 17-2
Callback function ....................................... 3-22
Communication data monitoring ............... 16-1
Condition agreement transmission ............. 2-7
Constant cycle transmission ....................... 2-6
CR/LF output designation area............... 11-35
CSET instruction (initial setting).............. 17-11
CSET instruction
(PLC CPU monitoring register/cancel) ..... 17-5
[D]
Data communication using user frames ... 11-1
Deleting................................................. 9-18
Reading ................................................ 9-17
Registering............................................ 9-16
Registration status storage area.......... 9-15
Storage area......................................... 9-15
Type...................................................... 9-13
DC code transmission control..................... 7-1
DC1/DC3...................................................... 7-4
DC2/DC4...................................................... 7-5
Dedicated instruction list ........................... 17-1
Default registration frame............................ 9-7
DTR/DSR (ER/DR) signal control............... 7-2
[H]
[ I ]
[M]
[N]
Half-duplex communications .......................8-1
I/O signals for handshake
(for mode switching)...................................15-5
I/O signals with the PLC CPU
(modem function) .......................................3-31
Improper access............................... 3-16, 3-47
Information to be transmitted.....................2-11
Initialization commands (for modem) ........3-58
Initialization of modem/terminal adapter ...3-68
Interrupt program example ..........................4-4
Interrupt program startup timing ..................4-2 m : n............................................................14-1
Message wait time .....................................6-13
Mode switching ..........................................15-1
Modem function list ......................................3-5
Modern function system setting.................3-56
Monitoring condition.....................................2-8
Monitoring target device...............................2-4
Non-communication interval time designation area.............................................................3-38
No-reception monitoring time (timer 0)........6-2
Notification function....................................2-19
[F]
Format-0 and Format-1
(reception method) .................................... 11-9
Full-duplex communications........................ 8-1
[O]
On-demand data communication
(user frame)................................................10-1
On-demand data list...................................10-2
On-demand function control procedure
(ASCII code)...............................................10-4
On-demand function control procedure
(binary code) ..............................................10-6
Output count designation area ................11-36
Output frame No. designation area .........11-36
Output head pointer designation area.....11-35
[G]
GETE instruction ..................................... 17-15
GX Developer connection ..................3-9, 3-50
GX Developer connection designation area............................................................ 3-38
Index - 1 Index - 1
Ind
Ind
[P]
PLC CPU monitoring function..................... 2-1
PRR instruction........................................ 17-18
PUTE instruction...................................... 17-21
[R]
Receive procedure (user frame) ............. 11-14
Receiving data with an interrupt program... 4-1
Reception control method
(interrupt program)....................................... 4-3
Reception method
(Format-0 and Format-1)........................... 11-9
Register/read/delete of the data for connection
(for modem) ............................................... 3-63
Registration data byte count designation area ....................................... 9-15
Remote password check...........3-4, 3-16, 3-47
Remote password mismatch notification accumulated count designation ................ 3-43
Remote password mismatch notification count designation ...................................... 3-43
Response monitoring time (timer 1)............ 6-7
RS·CS control (for modem function)......... 3-38
[S]
Sample program (mode switching)........... 15-8
Sample programs (for modem function)... 3-87
Send data list (user frame)...................... 11-30
Setting for transmission user frames ...... 11-33
Start-up of the modem function................. 3-52
[T]
Timing for PLC CPU monitoring.................. 2-5
Timing of transmission of monitoring results.......................................................... 2-6
Transmission control ................................... 7-1
Transmission data arrangement
On-demand data .................................. 10-3
PLC CPU monitoring............................ 2-12
Non procedure protocol ..................... 11-33
Transmission monitoring time (timer 2) .... 6-10
Transmission procedure (User frames).. 11-32
Transmission program (user frames) ..... 11-37
Transmission specification........................ 3-12
Transparent codes..................................... 12-1
[U]
User frame....................................................9-1
User frame setting for reception ..............11-15
[V]
Variable data (User frame) ..........................9-2
[W]
Word/bytes units setting...............................5-1
Index - 2 Index - 2
WARRANTY
Please confirm the following product warranty details before starting use.
1. Gratis Warranty Term and Gratis Warranty Range
If any faults or defects (hereinafter "Failure") found to be the responsibility of Mitsubishi occurs during use of the product within the gratis warranty term, the product shall be repaired at no cost via the dealer or Mitsubishi Service Company.
Note that if repairs are required at a site overseas, on a detached island or remote place, expenses to dispatch an engineer shall be charged for.
[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 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 possible 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 chance loss and secondary loss from warranty liability
Regardless of the gratis warranty term, Mitsubishi shall not be liable for compensation to damages caused by any cause found not to be the responsibility of Mitsubishi, chance losses, lost profits incurred to the user by Failures of Mitsubishi products, damages and secondary damages caused from special reasons regardless of Mitsubishi's expectations, compensation for accidents, and compensation for damages to products other than Mitsubishi products and other duties.
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 general-purpose 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 National Defense purposes shall be excluded from the programmable logic controller applications.
Note that even with these applications, if the user approves that the application is to be limited and a special quality is not required, application shall be possible.
When considering use in aircraft, medical applications, railways, incineration and fuel devices, manned transport devices, equipment for recreation and amusement, and safety devices, in which human life or assets could be greatly affected and for which a particularly high reliability is required in terms of safety and control system, please consult with Mitsubishi and discuss the required specifications.
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 Incorporation.
Pentium and Celeron are trademarks of Intel Corporation in the United States and other countries.
Ethernet is a trademark of Xerox Co., Ltd. in the United States.
Other company names and product names used in this document are trademarks or registered trademarks of respective owners.
MITSUBISHI ELECTRIC
HEADQUARTERS
MITSUBISHI ELECTRIC
EUROPE B.V.
German Branch
Gothaer Straße 8
D-40880 Ratingen
EUROPE
Phone: +49 (0) 2102 / 486-0
Fax: +49 (0) 2102 / 486-1120 e mail: [email protected]
MITSUBISHI ELECTRIC
EUROPE B.V.
French Branch
25, Boulevard des Bouvets
FRANCE
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
EUROPE B.V.
Italian Branch
ITALY
Via Paracelso 12
I-20041 Agrate Brianza (MI)
Phone: +39 039 6053 1
Fax: +39 039 6053 312 e mail: [email protected]
MITSUBISHI ELECTRIC
EUROPE B.V.
Spanish Branch
Carretera de Rubí 76-80
E-08190 Sant Cugat del Vallés
SPAIN
Phone: +34 9 3 / 565 3131
Fax: +34 9 3 / 589 2948 e mail: [email protected]
MITSUBISHI ELECTRIC
EUROPE B.V.
UK Branch
Travellers Lane
GB-Hatfield Herts. AL10 8 XB
UK
Phone: +44 (0) 1707 / 27 61 00
Fax: +44 (0) 1707 / 27 86 95 e mail: [email protected]
MITSUBISHI ELECTRIC
CORPORATION
Office Tower “Z” 14 F
8-12,1 chome, Harumi Chuo-Ku
JAPAN
Tokyo 104-6212
Phone: +81 3 6221 6060
Fax: +81 3 6221 6075
MITSUBISHI ELECTRIC
AUTOMATION
500 Corporate Woods Parkway
Vernon Hills, IL 60061
Phone: +1 847 / 478 21 00
Fax: +1 847 / 478 22 83
USA
MIDDLE EAST REPRESENTATIVE
TEXEL Electronics Ltd.
Box 6272
IL-42160 Netanya
Phone: +972 (0) 9 / 863 08 91
ISRAEL
Fax: +972 (0) 9 / 885 24 30 e mail: [email protected]
EUROPEAN REPRESENTATIVES
GEVA
Wiener Straße 89
AUSTRIA
AT-2500 Baden
Phone: +43 (0) 2252 / 85 55 20
Fax: +43 (0) 2252 / 488 60 e mail: [email protected]
TEHNIKON
Oktjabrskaya 16/5, Ap 704
BY-220030 Minsk
Phone: +375 (0)17 / 22 75 704
BELARUS
Fax: +375 (0)17 / 22 76 669 e mail: [email protected]
Getronics b.v.
Control Systems
Pontbeeklaan 43
BELGIUM
B-1731 Asse-Zellik
Phone: +32 (0) 2 / 467 17 51
Fax: +32 (0) 2 / 467 17 45 e mail: [email protected]
TELECON CO.
4, A. Ljapchev Blvd.
BG-1756 Sofia
BULGARIA
Phone: +359 (0) 2 / 97 44 05 8
Fax: +359 (0) 2 / 97 44 06 1 e mail: —
INEA CR d.o.o.
Drvinje 63
HR-10000 Zagreb
Phone: +385 (0) 1 / 36 67 140
Fax: +385 (0) 1 / 36 67 140 e mail: —
CROATIA
AutoCont
Control Systems s.r.o.
Nemocnicni 12
CZ-702 00 Ostrava 2
CZECH REPUBLIC
Phone: +420 59 / 6152 111
Fax: +420 59 / 6152 562 e mail: [email protected]
louis poulsen 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]
DENMARK
UTU Elektrotehnika AS
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]
ESTONIA
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.
5, Mavrogenous Str.
GR-18542 Piraeus
Phone: +302 (0) 10 / 42 10 050
Fax: +302 (0) 10 / 42 12 033 e mail: [email protected]
GREECE
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
Lienes iela 28
LV-1009 Riga
Phone: +371 784 / 22 80
Fax: +371 784 / 22 81 e mail: [email protected]
LATVIA
EUROPEAN REPRESENTATIVES
UAB UTU POWEL
Savanoriu pr. 187
LT-2053 Vilnius
Phone: +370 (0) 52323-101
Fax: +370 (0) 52322-980 e mail: [email protected]
LITHUANIA
INTEHSIS SRL
Cuza-Voda 36/1-81
MD-2061 Chisinau
Phone: +373 (0)2 / 562 263
Fax: +373 (0)2 / 562 263 e mail: [email protected]
MOLDOVA
Getronics b.v.
Control Systems
Donauweg 2 B
NETHERLANDS
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
Teglverksveien 1
N-3002 Drammen
Phone: +47 (0) 32 / 24 30 00
Fax: +47 (0) 32 / 84 85 77 e mail: [email protected]
NORWAY
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.
Stegne 11
SI-1000 Ljubljana
Phone: +386 (0) 1-513 8100
Fax: +386 (0) 1-513 8170 e mail: [email protected]
SLOVENIA
Beijer Electronics AB
Box 426
S-20124 Malmö
Phone: +46 (0) 40 / 35 86 00
Fax: +46 (0) 40 / 35 86 02 e mail: [email protected]
SWEDEN
ECONOTEC AG
Postfach 282
CH-8309 Nürensdorf
SWITZERLAND
Phone: +41 (0) 1 / 838 48 11
Fax: +41 (0) 1 / 838 48 12 e mail: [email protected]
GTS
Darülaceze Cad. No. 43 Kat. 2
TURKEY
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]
EUROPEAN REPRESENTATIVES
Avtomatika Sever Ltd.
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]
RUSSIA
CONSYS
Promyshlennaya St. 42
RU-198099 St Petersburg
Phone: +7 812 / 325 36 53
Fax: +7 812 / 147 20 55 e mail: [email protected]
RUSSIA
Electrotechnical
Systems Siberia
Partizanskaya St. 27, Office 306
RUSSIA
RU-121355 Moscow
Phone: +7 095/ 416-4321
Fax: +7 095/ 416-4321 e mail: [email protected]
Electrotechnical
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]
RUSSIA
Elektrostyle ul. Garschina 11
RU-140070 Moscow
Phone: +7 095 / 514 9316
Fax: +7 095 / 514 9317 e mail: [email protected]
RUSSIA
Elektrostyle
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]
RUSSIA
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 ul. Sverdlova 11a
RU-620027 Ekaterinburg
Phone: +7 34 32 / 53 27 45
Fax: +7 34 32 / 53 27 45 e mail: [email protected]
RUSSIA
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 ul. Bajkalskaja 239, Office 2 - 23
RUSSIA
RU-664075 Irkutsk
Phone: +7 3952 / 24 38 16
Fax: +7 3952 / 23 02 98 e mail: [email protected]
STC Drive Technique
Poslannikov Per. 9, str.1
RU-107005 Moscow
Phone: +7 095 / 790-72-10
Fax: +7 095 / 790-72-12 e mail: [email protected]
RUSSIA
AFRICAN REPRESENTATIVE
CBI Ltd.
Private Bag 2016
SOUTH AFRICA
ZA-1600 Isando
Phone: +27 (0) 11/ 928 2000
Fax: +27 (0) 11/ 392 2354 e mail: [email protected]
MITSUBISHI ELECTRIC
INDUSTRIAL AUTOMATION
Gothaer Strasse 8 Phone: +49 2102 486-0 Fax: +49 2102 486-7170 www.mitsubishi-automation.de
D-40880 Ratingen Hotline: +49 1805 000-765 [email protected] www.mitsubishi-automation.com
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement
Table of contents
- 2 SAFETY PRECAUTIONS
- 6 REVISIONS
- 7 INTRODUCTION
- 7 CONTENTS
- 14 About the Manuals
- 15 The Manual's Use and Structure
- 17 About the Generic Terms and Abbreviations
- 19 Definitions and Descriptions of Terminology
- 21 1 OVERVIEW
- 21 1.1 Overview
- 26 1.2 Functions Added/Changed by Function Version B
- 27 2 USING THE PLC CPU MONITORING FUNCTION
- 27 2.1 Overview
- 29 2.2 About the PLC CPU Monitoring Function
- 29 2.2.1 Data registration for using the PLC CPU monitoring function
- 29 2.2.2 PLC CPU monitoring information
- 31 2.2.3 Timing for PLC CPU monitoring
- 32 2.2.4 Timings of transmission and notification of monitoring results to the external device
- 35 2.2.5 Transmission methods of monitoring results and transmission data to the external device
- 46 2.2.6 Execution sequence for using the PLC CPU monitoring function
- 47 2.3 Settings for Using the PLC CPU Monitoring Function
- 47 2.3.1 System setting items for the PLC CPU monitoring function
- 52 2.3.2 How to register and cancel the PLC CPU monitoring function
- 54 2.4 Precautionary Notes for Using the PLC CPU Monitoring Function
- 56 3 COMMUNICATIONS BY THE MODEM FUNCTION
- 56 3.1 Overview
- 57 3.1.1 Features
- 60 3.1.2 Function list
- 61 3.1.3 Comparisons with related devices
- 62 3.2 System Configuration
- 62 3.2.1 System configuration when performing data communication with an external device
- 63 3.2.2 System configuration when using the notification function
- 64 3.2.3 System configuration when connecting GX Developer
- 65 3.2.4 Precautions for system configurations
- 67 3.3 Specifications
- 67 3.3.1 Transmission specifications
- 68 3.3.2 Specification of connectable modems/terminal adapters
- 71 3.3.3 Compatibility with the QCPU remote password function
- 77 3.3.4 Compatibility with the callback function
- 86 3.3.5 I/O signals with the PLC CPU
- 88 3.3.6 Buffer memory
- 101 3.3.7 Precautions when using the modem function
- 107 3.4 Start-up of the Modem Function
- 107 3.4.1 Start-up procedures when communicating data with external devices
- 110 3.4.2 Initial settings of the serial communication module
- 113 3.4.3 Register/read/delete of the initialization data
- 118 3.4.4 Register/read/delete of the data for connection
- 123 3.4.5 Initialization of modem/terminal adapter
- 127 3.4.6 Line connection
- 133 3.4.7 Data communication and notification
- 139 3.4.8 Line disconnection
- 142 3.5 Sample Programs
- 143 3.5.1 Sample program for data communication-1
- 149 3.5.2 Sample program for data communication-2
- 158 3.5.3 Sample program for notification
- 161 4 RECEIVING DATA WITH AN INTERRUPT PROGRAM
- 162 4.1 Settings for Receiving Data Using an Interrupt Program
- 162 4.2 Interrupt Program Startup Timing
- 163 4.3 Reception Control Method Using an Interrupt Program
- 164 4.4 Programming
- 164 4.4.1 Program example
- 165 4.4.2 Precautions when receiving data with an interrupt program
- 167 5 CHANGING SEND AND RECEIVE DATA LENGTH UNITS TO BYTE UNITS (WORD/BYTES UNITS SETTING)
- 169 6 CHANGING THE DATA COMMUNICATIONS MONITORING TIMES
- 170 6.1 No-Reception Monitoring Time (timer 0) Setting
- 175 6.2 Response Monitoring Time (timer 1) Setting
- 178 6.3 Transmission Monitoring Time (timer 2) Setting
- 181 6.4 Message Wait Time Setting
- 182 7 DATA COMMUNICATIONS USING DC CODE TRANSMISSION CONTROL
- 183 7.1 Control Contents of DTR/DSR (ER/DR) Signal Control
- 185 7.2 Control Contents of DC Code Control
- 188 7.3 Precautions when Using the Transmission Control Functions
- 190 8 DATA COMMUNICATIONS USING HALF-DUPLEX COMMUNICATIONS
- 190 8.1 Half-duplex Communications
- 191 8.2 Data Transmission and Reception Timing
- 195 8.3 Changing the Communication System
- 196 8.4 Connector Connections for Half-duplex Communications
- 197 8.5 Half-duplex Communications Precautions
- 198 9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA COMMUNICATION
- 198 9.1 User Frame Types and Contents During Communication
- 198 9.1.1 User frames to be registered and used by the user
- 204 9.1.2 Default registration frame (read only)
- 205 9.2 Transmission/Reception Processing Using User Frame Register Data
- 208 9.3 Precautions when Registering, Reading, Deleting and Using User Frames
- 210 9.4 Register/Read/Delete User Frames
- 213 9.4.1 Registering user frames
- 214 9.4.2 Reading user frames
- 215 9.4.3 Deleting user frames
- 216 10 ON-DEMAND DATA COMMUNICATIONS USING USER FRAMES
- 216 10.1 User Frame Data Communications Function
- 217 10.2 User Frame Types and Registration
- 217 10.3 User Frame On-Demand Data Transmission and Buffer Memory Used
- 219 10.4 On-Demand Function Control Procedure During User Frame Use
- 219 10.4.1 Data communication using the ASCII code
- 221 10.4.2 Data communications using the binary code
- 223 10.5 Example of an On-Demand Data Transmission Program Using User Frames
- 225 11 DATA COMMUNICATIONS USING USER FRAMES
- 226 11.1 Overview of Data Communication Procedure
- 227 11.2 Data Reception
- 227 11.2.1 About reception data
- 234 11.2.2 Timing for start/completion of data reception
- 238 11.2.3 Receive procedure
- 239 11.2.4 User frame setting for reception
- 245 11.3 Receive Program
- 245 11.3.1 Sequence program example
- 246 11.3.2 Application example for data reception using a combination that specifies the first frame
- 252 11.3.3 Application example for data reception using a combination that does not specify the first frame
- 254 11.4 Data Transmission
- 254 11.4.1 Send data
- 256 11.4.2 Transmission procedure
- 257 11.4.3 Settings for transmission user frames
- 261 11.5 Transmission program
- 264 12 TRANSPARENT CODES AND ADDITIONAL CODES
- 264 12.1 Handling the Transparent Code and Additional Code Data
- 265 12.2 Registering Transparent Codes and Additional Codes
- 266 12.3 Handling Transparent Codes and Additional Codes During Non Procedure Protocol Data Communication
- 271 12.4 Example of Data Communication Using the Non Procedure Protocol
- 272 12.4.1 Example of data reception
- 274 12.4.2 Example of data transmission
- 276 12.5 Handling Transparent Codes and Additional Codes During Bidirectional Protocol Data Communication
- 279 12.6 Example of Data Communication Using the Bidirectional Protocol
- 280 12.6.1 Example of data reception
- 282 12.6.2 Example of data transmission
- 284 13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION)
- 284 13.1 ASCII-BIN Conversion
- 284 13.2 Settings for ASCII-BIN Conversion
- 285 13.3 Performing ASCII-BIN Conversion for Data Communicated via Non Procedure Protocol
- 287 13.4 Example of Data Communication Using the Non Procedure Protocol
- 288 13.4.1 Example of data reception
- 291 13.4.2 Example of data transmission
- 293 13.5 Performing ASCII-BIN Conversion for Data Communicated Via the Bidirectional Protocol
- 295 13.6 Example of Data Communication Using the Bidirectional Protocol
- 296 13.6.1 Example of data reception
- 297 13.6.2 Example of data transmission
- 298 14 DATA COMMUNICATIONS USING EXTERNAL DEVICE AND PLC CPU M : N CONFIGURATION
- 298 14.1 Data Communications Precautions
- 300 14.2 External Devices Interlock Conditions
- 300 14.2.1 Maximum communications time per external device station
- 301 14.2.2 Message structure when communicating data between external devices
- 303 14.3 Examples of Procedure for Data Communications with the PLC CPU
- 303 14.3.1 Sequential data communications between external devices and the PLC CPU
- 306 14.3.2 Data communications between PLC CPU and external devices by designating a master station and slave stations
- 309 15 SWITCHING THE MODE AFTER STARTING
- 310 15.1 Mode Switching Operation and Contents that can be Changed
- 310 15.1.1 Settings that can be changed with mode switching
- 310 15.1.2 Operation for mode switching
- 311 15.2 Mode Switching Precautions
- 313 15.3 I/O Signals for Handshake with PLC CPU and Buffer Memory
- 315 15.4 Switching the Mode from the PLC CPU
- 315 15.4.1 Mode switching procedure
- 316 15.4.2 Mode switching sample program
- 317 15.5 Switching the Mode from an External Device
- 317 15.5.1 Mode switching procedure
- 318 15.5.2 Mode switching sample program
- 319 16 USING COMMUNICATION DATA MONITORING FUNCTION
- 319 16.1 Communication Data Monitoring Function
- 319 16.1.1 Overview
- 320 16.1.2 Communication data monitoring operation
- 322 16.2 Communication Data Monitoring Function Settings
- 326 16.3 Communication Data Monitoring Example
- 329 17 DEDICATED INSTRUCTIONS
- 329 17.1 Dedicated Instruction List
- 330 17.2 BUFRCVS Instruction
- 333 17.3 CSET Instruction (PLC CPU Monitoring Register/Cancel)
- 339 17.4 CSET Instruction (Initial Settings)
- 343 17.5 GETE Instruction
- 346 17.6 PRR Instruction
- 349 17.7 PUTE Instruction
- 354 INDEX
- 356 WARRANTY